Generally configuration options that alter API behaviour are rejected due to interoperability concerns. We already do some basic validation. This isn’t the simplest thing to do, but we are trying to be safe while keep backwards compatibility as the approach has evolved over the years.
It’s unclear to me what the likely problem is here, but hopefully the above will help others check my thinking on the topic.
So this is what we do today, we use the sanitised instance.hostname: /github. com/openstack/ nova/blob/ da155cb49597972 6943806630eff1b ed146b8605/ nova/compute/ api.py# L1817
https:/
You can see the sanitise logic here: /github. com/openstack/ nova/blob/ da155cb49597972 6943806630eff1b ed146b8605/ nova/utils. py#L351
https:/
I think we assume neutron does a double check here: /github. com/openstack/ nova/blob/ da155cb49597972 6943806630eff1b ed146b8605/ nova/network/ neutron. py#L1624
https:/
It’s worth noting the api re-write added some validation here: /github. com/openstack/ nova/blob/ da155cb49597972 6943806630eff1b ed146b8605/ nova/api/ openstack/ compute/ schemas/ servers. py#L155 /github. com/openstack/ nova/blob/ da155cb49597972 6943806630eff1b ed146b8605/ nova/api/ validation/ parameter_ types.py# L268
https:/
https:/
Generally configuration options that alter API behaviour are rejected due to interoperability concerns. We already do some basic validation. This isn’t the simplest thing to do, but we are trying to be safe while keep backwards compatibility as the approach has evolved over the years.
It’s unclear to me what the likely problem is here, but hopefully the above will help others check my thinking on the topic.