ip_allocation attribute is not accessible over REST requests
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Confirmed
|
Wishlist
|
Unassigned | ||
Bug Description
Currently, one can set the ip_allocation attribute to "none" on a port with the neutron API [1] or the python-
This is useful for instantiating a VM that doesn't have an IP, and fixing [3]
However, to be able to read this attribute, the ip_allocation extension must be enabled, which is not mandatory to set this attribute to "none".
The only way to enable this extension seems to activate the segments service plugin. However, enabling this service plugin just to be able to instantiate a VM without an IP is cumbersome.
Moreover, while using the API, the fact that the ip_allocation attribute can be set to "none", but cannot be read afterward is inconsistent.
[1] https:/
[2] https:/
[3] https:/
| tags: | added: l3-ipam-dhcp |
| Changed in neutron: | |
| status: | New → Confirmed |
| importance: | Undecided → Wishlist |
| Hirofumi Ichihara (ichihara-hirofumi) wrote | #1 |
| Mathieu Rohon (mathieu-rohon) wrote | #2 |
I can understand the requirement but ip_allocation is originally subset of segments extension. Although it seems that we can use ip_allocation of port without the extension now. I guess that we should use the feature with segments extension.
I'd like to know L3 Lieutenant(Miguel Lavalle)'s opinion.