Open Stack

On 13/03/2023 19:46, Tobias Urdin wrote:
> Interesting thread!

+1

Most installations run into this issue of wondering when a network node 
is really ready / fully synced. While the tooling that Mohammed or Felix 
does work in "observing" or "determining" the sync state independently, 
I strongly believe a network agent should report it's sync state back to 
the control plane.

Orchestration of e.g. rolling upgrades of agents should be possible with 
state information provided by neutron itself and not require external 
tooling.

By implementing the state data structure and then having the drivers 
(OVN, OVS, linuxbridge) report this back, this is independent from the 
particular implementation details (network NS, certain processes 
running, ...).

Looking at this problem the taints and tolerations model use for node 
"readiness" from Kubernetes come to mind 
(https://kubernetes.io/docs/reference/labels-annotations-taints/#node-kubernetes-io-network-unavailable).


Regards

Christian