Tree:
9932c2841c
master
stable/train
stable/wallaby
0.0.1
0.1.0
0.1.1
0.2.0
0.3.0
0.3.1
0.3.2
0.3.3
0.3.4
0.4.0
0.4.1
0.4.2
0.4.3
0.4.4
0.5.0
0.5.1
0.5.2
0.5.3
0.5.4
0.5.5
0.5.6
0.6.0
0.6.1
0.6.2
0.6.3
0.6.4
0.7.0
0.7.1
0.7.2
0.7.3
0.7.4
0.7.5
0.7.6
0.7.7
0.7.8
0.7.9
0.8.0
0.8.1
0.8.10
0.8.11
0.8.12
0.8.13
0.8.14
0.8.2
0.8.3
0.8.4
0.8.5
0.8.6
0.8.7
0.8.8
0.8.9
1.0.0
10.0.0
10.1.0
10.2.0
10.3.0
10.4.0
10.5.0
10.6.0
10.6.1
10.6.2
11.0.0
11.1.0
11.2.0
11.3.0
11.3.1
11.4.0
11.5.0
11.6.0
12.0.0
12.1.0
12.2.0
12.3.0
12.4.0
12.4.1
12.4.2
12.4.3
12.4.4
12.4.5
12.4.6
12.5.0
12.6.0
12.7.0
13.0.0
13.1.0
13.2.0
13.3.0
13.4.0
13.5.0
13.6.0
14.0.0
14.1.0
14.1.1
14.1.2
14.2.0
14.3.0
15.0.0
15.1.0
16.0.0
2.0.0
2.1.0
2.2.0
5.0.0
5.0.0.0b1
5.0.0.0b2
5.0.0.0b3
5.0.0.0rc1
5.0.0.0rc2
5.0.0.0rc3
5.1.0
5.2.0
5.3.0
5.3.1
5.3.10
5.3.11
5.3.12
5.3.13
5.3.2
5.3.3
5.3.4
5.3.5
5.3.6
5.3.7
5.3.8
5.3.9
6.0.0
6.0.0.0b1
6.0.0.0b2
6.0.0.0rc1
6.0.0.0rc2
6.1.0
6.2.0
6.2.1
6.2.10
6.2.11
6.2.12
6.2.13
6.2.14
6.2.15
6.2.16
6.2.2
6.2.3
6.2.4
6.2.5
6.2.6
6.2.7
6.2.8
6.2.9
7.0.0
7.0.0.0b1
7.0.0.0b2
7.0.0.0b3
7.0.0.0rc1
7.0.0.0rc2
7.0.1
7.0.10
7.0.11
7.0.12
7.0.13
7.0.14
7.0.15
7.0.16
7.0.17
7.0.18
7.0.2
7.0.3
7.0.4
7.0.5
7.0.6
7.0.7
7.0.8
7.0.9
8.0.0
8.0.0.0b1
8.0.0.0b2
8.0.0.0b3
8.0.0.0rc1
8.0.1
8.0.2
8.0.3
8.0.4
8.0.5
8.0.6
8.0.7
8.1.0
8.2.0
8.3.0
8.3.1
8.4.0
8.4.1
9.0.0
9.0.0.0b1
9.0.0.0b2
9.0.0.0b3
9.0.0.0b4
9.0.0.0rc1
9.0.0.0rc2
9.1.0
9.2.0
9.3.0
9.4.0
9.4.1
liberty-eol
mitaka-eol
newton-eol
ocata-em
ocata-eol
pike-em
pike-eol
queens-em
queens-eol
rocky-em
rocky-eol
stein-em
stein-eol
train-em
ussuri-em
ussuri-eol
victoria-em
victoria-eol
${ noResults }
6 Commits (9932c2841cd37598b5407279f3eae80ad8e3bdea)
| Author | SHA1 | Message | Date |
|---|---|---|---|
Marius Cornea
|
9932c2841c |
Enable management network in network_data
This change enables the management network in network_data to allow upgrading environments that were initially deployed with this optional network enabled. Change-Id: I39b1a70f0a27bdab4d6280d54107ff209d4bb67d Closes-bug: 1765547 |
4 years ago |
Dan Sneddon
|
1dec175241 |
Render NIC config templates with jinja2
This change converts the existing NIC templates to jinja2 in order to dynamically render the ports and networks according to the network_data.yaml. If networks are added to the network_data.yaml file, parameters will be added to all NIC templates. The YAML files (as output from jinja with the default network_data.yaml) are present as an example. The roles in roles_data.yaml are used to produce NIC configs for the standard and custom composable roles. In order to keep the ordering of NICs the same in the multiple-nics templates, the order of networks was changed in the network_data.yaml file. This is reflected in the network templates, and in some of the files that is the only change. The roles and roles_data.yaml were modified to include a legacy name for the NIC config templates for the built-in roles Controller, Compute, Object Storage, Block Storage, Ceph Storage, Compute-DPDK, and Networker roles. There will now be a file produced with the legacy name, but also one produced with the <role>-role.j2.yaml format (along with environment files to help use the new filenames). Note this change also fixes some typos as well as a number of templates that had VLANs with device: entries which were ignored. Closes-Bug: 1737041 Depends-On: I49c0245c36de3103671080fd1c8cfb3432856f35 Change-Id: I3bdb7d00dab5a023dd8b9c94c0f89f84357ae7a4 |
5 years ago |
Christian Schwede
|
65d38fa8de |
Fix networking settings for ObjectStorage role
The role name is actually "ObjectStorage", not "SwiftStorage". This leads do failing deployments if one or more ObjectStorage nodes are deployed on the overcloud. Closes-Bug: 1727475 Change-Id: I96fd27bdad5d417f23550ecc3387d81fd3c5418a |
5 years ago |
|
Dan Sneddon
|
15bb67261a |
Add Management Network For System Administration.
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 |
7 years ago |
Dan Prince
|
5834964154 |
Support network isolation without external nets
This patch adds extra heat environments that can be used to enable network isolation without using the external network. Instead of a separate external network the ctlplane will be used for all of the external/public traffic. Change-Id: Ia542cee02121771d7d57ac701b62d7608e8d1855 |
7 years ago |
|
Dan Prince
|
b982219b65 |
os-net-config templates to configure vlans on bond
This patch adds 5 new role templates to help configure an OVS bond with vlans on top for each of the overcloud roles. These are meant to represent a more production network which might use isolated nets, and should help facilitate create a CI job which configures a bond w/ vlans on it. The patch also includes an environment file to enable configuration of bonded vlans by simply sourcing this file. Change-Id: Ibe4c9d933445014ce3bec5fb3d7e3139fc40cb32 |
7 years ago |