e5fe9d6e43
Currently, there is no support in the NSX-V plugin to create a
network on a specified transport zone. One transport zone is
configured in the nsx.ini file and all networks are created on this
transport zone.
This commit adds the ability to specify a transport zone ID during
network create operation using providernet APIs.
Admin can now create a provider network of type VXLAN and specify
the transport zone ID in the physical network attribute.
Eg. CLI:
neutron net-create vxlan-net --provider:network_type=vxlan
--provider:physical_network=vdn-scope-1
If no transport zone ID is specified in physical_network attribute,
the default value for transport zone ID will be picked up from
nsx.ini
This change also splits the HEADS file in database migrations into
EXPAND and CONTRACT HEAD files. This reduces the chances of merge
conflicts.
A new migration script is generated to update binding
type in NsxvTzNetworkBinding table to accept vxlan as a valid
provider network type.
Change-Id: I388c83c044f114755a5a3bcbca1381d64aaa14d5
|
||
|---|---|---|
| .. | ||
| alembic_migrations | ||
| models | ||
| __init__.py | ||