kuryr-libnetwork/kuryr_libnetwork
Hongbin Lu 68cb29267a Handle single ip port on dual-stack
In the case of dual-stack network, users might create a container
with existing neutron port. In before, kuryr assumes the
existing port is a dual-port (with both v4 and v6 addresses)
but this assumption is not always true. In face, it is
possible to create a v4 only port in a dual-stack network and
use it as an existing port.

This commit handle the case that the container is created from
a dual-net with a specified v4-only port. In this case, kuryr
will create a v6 port in ipam_request_address as a place holder.
The v6 port will be removed at network_driver_create_endpoint.

Related-Bug: #1800375
Change-Id: Id988abf1b6560332b18a60d99658a8768d46c343
2018-10-29 04:42:41 +00:00
..
port_driver Merge "Introduce sriov port driver" 2018-01-08 11:36:10 +00:00
schemata Allow new network ID pattern 2017-07-31 08:05:55 +00:00
tests Handle single ip port on dual-stack 2018-10-29 04:42:41 +00:00
__init__.py versioning: let pbr handle versioning from tags 2016-08-18 10:50:14 +02:00
config.py Allow skip processing exposed ports 2018-04-22 17:11:24 +00:00
constants.py Introduce sriov port driver 2018-01-03 07:51:05 +00:00
controllers.py Handle single ip port on dual-stack 2018-10-29 04:42:41 +00:00
opts.py auth: Add keystonev3 support 2016-09-13 08:18:53 +02:00
server.py Check for `standard-attr-tag` Neutron extension 2018-03-19 15:06:56 +01:00
utils.py Add fullstack test for release overlap address 2018-07-23 03:11:17 +00:00
version.py Add reno support to kuryr-libnetwork 2017-02-06 09:30:43 -06:00