[Nsi-wg] Discovery Service

[Hans Trompert]

I'm planning on implementing a multi domain path finder based on the new
topology description format and using the (probably experimental)
dynamic topology exchange in the first half of next year, and would
welcome the ability to have a health check mechanism in the first
version of the discovery service. So I vote to include this in 1.0.

    HansT.

On 10/12/12 5:01 PM, John MacAuley wrote:
>> What the heck is a restart token?
> System uptime really only applies to a single server, and becomes ambiguous when using multiple servers within a solution for either load balancing or redundancy.  I the last system I designed we introduced a token that was returned through our system monitoring WSDL.  If the token changed then there was either a system restart (in the unprotected case) or an activity switch in the protected case.  The token only needed to change if the activity switch resulted in the possibility of lost data such as notification registration or service requests.  The token was managed by the system and generated using whatever mechanism desired to provide uniqueness.
>
>> Please tell me this will be a perfectly normal RPC call without callback stuff.
> Yes, it would be a synchronous call just like discovery.
>
>> I think we should wait just a bit with adding this (now is better than never, but never is often better that right now).
> We have two options:
> 1. I add it to the discovery interface now so it is in version 1.0 and I never change it.
> 2. If we wait then it goes in a new service defined later.
>
> Currently the comments seem to be a 50-50 split on do it now or leave it until later.  It was nice this week to have an independent way to monitor NSA availability, but I am easy on what we do.
>
> John.
>
> _______________________________________________
> nsi-wg mailing list
> nsi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/nsi-wg