Rodolfo,
This is not enforced in OVS either as I pointed out in #9. The system-id is a string value in the OVS database schema. [4][5]
It is used by OVN for the chassis name [6][7], which is also a string value in the OVN database scheme.
Why does Neutron need to impose this check when it clearly breaks multiple existing users? What does this enforcement gain us?
How would you feel if you had to issue SSL certificates with UUID's as CN's? Would you feel that was a useful thing of a system have you do?
6: https://github.com/ovn-org/ovn/blob/8fd4cecf3034848d222e023a68a03e9a8eadf621/ovn-sb.ovsschema#L29 7: https://github.com/ovn-org/ovn/blob/8fd4cecf3034848d222e023a68a03e9a8eadf621/ovn-sb.xml#L241-L250
Rodolfo,
This is not enforced in OVS either as I pointed out in #9. The system-id is a string value in the OVS database schema. [4][5]
It is used by OVN for the chassis name [6][7], which is also a string value in the OVN database scheme.
Why does Neutron need to impose this check when it clearly breaks multiple existing users? What does this enforcement gain us?
How would you feel if you had to issue SSL certificates with UUID's as CN's? Would you feel that was a useful thing of a system have you do?
6: https:/ /github. com/ovn- org/ovn/ blob/8fd4cecf30 34848d222e023a6 8a03e9a8eadf621 /ovn-sb. ovsschema# L29 /github. com/ovn- org/ovn/ blob/8fd4cecf30 34848d222e023a6 8a03e9a8eadf621 /ovn-sb. xml#L241- L250
7: https:/