Add physical network awareness #3
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Ironic added support for physical network awareness [1] in the pike
release. With multiple physical networks it is possible that each
physical network extends over a subset of the devices in a network.
Further, the segmentation ID space on different physical networks may
overlap.
This change adds support for configuration of a set of physical networks
on each switch. On neutron network creation and deletion, NGS will only
(de)provision VLANs on devices tagged with that network's physical
network. If a device is not tagged with any physical networks, the old
behaviour of provisioning all networks on all devices is used.
Configuration of physical networks is be via a new per-device config
option, ngs_physical_networks:
[genericswitch:switch1]
device_type = acme
ip = 1.2.3.4
username = bob
password = drowssap
ngs_physical_networks = physnet1,physnet2
[1]
https://specs.openstack.org/openstack/ironic-specs/specs/not-implemented/physical-network-awareness.html
Change-Id: I77a8247f6152fd0133c8f5a325ca20cd35fa669d
Closes-Bug: #1735394