Yes, this is quite annoying. We are still shipping the old network-scripts, even with CentOS9 precisely because of this limitation. Unfortunately, there just hasn't been much progress on the NetworkManager and OVS integration that would sufficiently cover our use case in TripleO.
It's something we have tried to work around using nmstate configuration of the interfaces and OVS bridges, but so far we haven't had it working reliably enough to ship a solution with TripleO:
Long story short is that this is a work in progress. There will be some limitations to using nmstate vs the legacy network-scripts, but it's something we're working towards nonetheless.
Hey Crisitan,
Yes, this is quite annoying. We are still shipping the old network-scripts, even with CentOS9 precisely because of this limitation. Unfortunately, there just hasn't been much progress on the NetworkManager and OVS integration that would sufficiently cover our use case in TripleO.
It's something we have tried to work around using nmstate configuration of the interfaces and OVS bridges, but so far we haven't had it working reliably enough to ship a solution with TripleO:
Noting: /review. opendev. org/c/openstack /os-net- config/ +/786323 /review. opendev. org/c/openstack /os-net- config/ +/642975 /review. opendev. org/c/openstack /os-net- config/ +/791409/ 4
https:/
https:/
https:/
Long story short is that this is a work in progress. There will be some limitations to using nmstate vs the legacy network-scripts, but it's something we're working towards nonetheless.