Age | Commit message (Collapse) | Author | Files | Lines |
|
This patch allows to :
- disable the gateway ip for non routable network
- use the first ip in the subnet
- set the correct gateway on the external network
Change-Id: Idc816c782856e93ecd339b3aca2a7f53c1564b1d
Closes-bug: #1588379
Depends-On: I8ea6733fe46902e1baeff4ccfbcd42ecc5a1825f
|
|
The ManagementNetValueSpecs param type is currently set to string.
This change sets the param to the correct type of json, allowing the
network value specs to correctly parse.
Example Management Network value spec:
{'provider:physical_network': 'management', 'provider:network_type': 'flat'}
Change-Id: I5b12c7251690368d79a4d00725a9d6e0d5e75af8
Closes-Bug: #1573649
|
|
Multiple files in t-h-t were having small typos.
Fixed in this patchset.
.
Change-Id: I82d7071747f47544990ed46e2be22931190406b3
|
|
This change adds a system management network to all overcloud
nodes. The purpose of this network is for system administration,
for access to infrastructure services like DNS or NTP, or for
monitoring. This allows the management network to be placed on a
bond for redundancy, or for the system management network to be
an out-of-band network with no routing in or out. The management
network might also be configured as a default route instead of the
provisioning 'ctlplane' network.
This change does not enable the management network by default. An
environment file named network-management.yaml may be included to
enable the network and ports for each role. The included NIC config
templates have been updated with a block that may be uncommented
when the management network is enabled.
This change also contains some minor cleanup to the NIC templates,
particularly the multiple nic templates.
Change-Id: I0813a13f60a4f797be04b34258a2cffa9ea7e84f
|