Yes, as Sean commented, there are some inconsistencies in Neutron API.
None has several meanings depending on the context :-(
* None is an actual value of an attribute (e.g., "gateway_ip" of subnet)
* Sending None in API clears the attribute (e.g., "session_persistence" in LBaaS VIP)
* Sending None in API has the same meaning of sending an empty list/dict
We need to have a consistent way when we discuss a new version of API,
but it is what we have now.
In IPv6 attribute case, there are several ways to handle this bug:
- to have more detail documentation on what operations are allowed (and not to change the current behavior)
- to disallow updating IPv6 modes completely
- to add a way to clear IPv6 modes (the proposed patch tries to do this)
Yes, as Sean commented, there are some inconsistencies in Neutron API.
None has several meanings depending on the context :-(
* None is an actual value of an attribute (e.g., "gateway_ip" of subnet) persistence" in LBaaS VIP)
* Sending None in API clears the attribute (e.g., "session_
* Sending None in API has the same meaning of sending an empty list/dict
We need to have a consistent way when we discuss a new version of API,
but it is what we have now.
In IPv6 attribute case, there are several ways to handle this bug:
- to have more detail documentation on what operations are allowed (and not to change the current behavior)
- to disallow updating IPv6 modes completely
- to add a way to clear IPv6 modes (the proposed patch tries to do this)