yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #74959
[Bug 1794919] [NEW] [RFE] To decide create port with specific IP version
Public bug reported:
Recently bug:
https://bugs.launchpad.net/neutron/+bug/1752903
and the fix https://review.openstack.org/#/c/599494/
are trying to create floating IP only including IPv4 version.
For now, if the public network has both IPv4 and IPv6 subnet
the floating IP (port) may have both v4 and v6 addresses.
Furthermore, not only the public network, for tenant network
the default behavior is also to create one port with both v4 and v6 IP addr.
Here are some test:
http://paste.openstack.org/show/731054/
So, this RFE raises a new approach to the port create API,
when user try to create the port, they can decide which IP version to use.
something like this:
curl POST http://neutron_url/ports -d
'{"port": {
"subnet_id": <a-subnet-id>,
"ip_version": <one of [both, v4, v6]>
}
}'
So for the ml2 plugin, the IPAM can pick both/only v4/only v6 version of
subnet to use.
** Affects: neutron
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1794919
Title:
[RFE] To decide create port with specific IP version
Status in neutron:
New
Bug description:
Recently bug:
https://bugs.launchpad.net/neutron/+bug/1752903
and the fix https://review.openstack.org/#/c/599494/
are trying to create floating IP only including IPv4 version.
For now, if the public network has both IPv4 and IPv6 subnet
the floating IP (port) may have both v4 and v6 addresses.
Furthermore, not only the public network, for tenant network
the default behavior is also to create one port with both v4 and v6 IP addr.
Here are some test:
http://paste.openstack.org/show/731054/
So, this RFE raises a new approach to the port create API,
when user try to create the port, they can decide which IP version to use.
something like this:
curl POST http://neutron_url/ports -d
'{"port": {
"subnet_id": <a-subnet-id>,
"ip_version": <one of [both, v4, v6]>
}
}'
So for the ml2 plugin, the IPAM can pick both/only v4/only v6 version
of subnet to use.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1794919/+subscriptions
Follow ups