search

AMWA-TV / is-06

AMWA IS-06 NMOS Network Control Specification (Deprecated)
https://specs.amwa.tv/is-06
Apache License 2.0
14 stars 10 forks source link

Clarify persistence of Network Device IDs #23

Closed garethsb closed 4 years ago

garethsb commented 5 years ago

We assume that when a Network Device (switch) is power-cycled, the ID included in the Network Control API /network-devices response must be persistent (and suggest that it is generated from the Chassis ID?). This would be consistent with the AMWA IS-04 Identifier Persistence & Generation specification.

If so, perhaps this could be added to the IS-06 spec?

garethsb commented 5 years ago

Similarly, also suggest how Network Control clients (e.g. Broadcast Controllers) could generate persistent id properties of the Endpoint and Network Flow resources they add.

vsachin33 commented 5 years ago

Yes. N/W controllers should persist these ID(s) and return the same on reboot/reload ..Sachin

vsachin33 commented 5 years ago

How clients/broadcast controller generates ID(s) is transparent to IS-06 API/network controller as long as it conforms to ID schema definition ..Sachin

garethsb commented 5 years ago

How clients/broadcast controller generates ID(s) is transparent to IS-06 API/network controller as long as it conforms to ID schema definition

That's true. However persistent IDs would make resync of the BC and/or NC after reboot/reload much simpler, right?

Has the effect of different ID generation and persistence specifications on use cases with multiple BCs (or NCs for different parts of the network?) been considered?

garethsb commented 4 years ago

Yes. N/W controllers should persist these ID(s) and return the same on reboot/reload ..Sachin

Are Endpoints, Network Flows, etc. also expected to be persisted by the network controller through reboot/reload?

vsachin33 commented 4 years ago

Yes, that is my understanding. In our implementation we do that ..Sachin