9e99cc0242
To use this feature, users need to pre-create the subnetpool and
pass the pool name to kuryr. For example:
$ docker network create -d kuryr --ipam-driver=kuryr ... \
-o neutron.pool.name=testpool \
--ipam-opt neutron.pool.name=testpool \
foo
Kuryr will look for the existing subnetpool in neutron instead of
creating a new subnetpool. If the network is deleted, the existing
subnetpool will not be deleted.
NOTE: the option 'neutron.pool.name' was used to specify an custom
name of subnetpool. This commit will the semantic of this option.
Implements: blueprint existing-subnetpool
Change-Id: I73f6c17e0e941ef9dbd20591002fdf96c59e6424
15 lines
608 B
YAML
15 lines
608 B
YAML
---
|
|
features:
|
|
- |
|
|
Support creating a Docker network with existing subnetpool. Users can use
|
|
the option "neutron.pool.name" to specify the name of existing neutron
|
|
subnetpool.
|
|
upgrade:
|
|
- |
|
|
The semantic of the option "neutron.pool.name" is changed. This option was
|
|
used to specify a custom name of the creating subnetpool, and now it is
|
|
used to specify the name of a pre-existing subnetpool. As a result,
|
|
subnetpools created with custom name in before are now treated as external
|
|
resources and won't be cleanup on deletion. Users need to cleanup the
|
|
resources manually.
|