Tree:
19be98ba07
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 }
1 Commits (19be98ba07d9c8881d67a359b9c1a424f824e2ac)
| Author | SHA1 | Message | Date |
|---|---|---|---|
Dan Sneddon
|
dd299f08bd |
Remove ipv6 specific network templates
This change renders the IPv6 versions of the isolated networks using j2. To allow for backward compatibility, there will be 2 versions of the network definitions, <network>.yaml and <network>_v6.yaml. If the ip_subnet contains an IPv6 address, or if ipv6: true is set on the network definition in network_data.yaml, then the <network>.yaml version will contain an IPv6 definition, otherwise the <network>.yaml will be IPv4, and the <network>_v6.yaml will be IPv6. In a future follow-up patch, we will probably only create the required versions of the networks, either IPv4, IPv6, not both. The ipv6_subnet, ipv6_allocation_pools, and ipv6_gateway settings in the network_data.yaml definition file are used for the <network>_v6.yaml network definition. Note that these subnet/cidr/gateway definitions only set the defaults, which can be overridden with parameters set in an environment file. Since the parameters for IP and subnet range are the same (e.g. InternalApiNetCidr applies to both IPv4/v6), only one version can be used at a time. If an operator wishes to use dual-stack IPv4/IPv6, then two different networks should be created, and both networks can be applied to a single interface. Note that the workflow for the operator is the same as before this change, but a new example template has been added to environments/network-environment-v6.yaml. Change-Id: I0e674e4b1e43786717ae6416571dde3a0e11a5cc Partially-Implements: blueprint composable-networks Closes-bug: 1714115 |
5 years ago |
Steven Hardy
|
700b82bf20 |
Render port templates via j2
Remove these from the j2 excludes and instead render all the networks to avoid duplication. Change-Id: Id8e14e06ffe959c50456b4c88fef306046a8b478 Partially-Implements: blueprint composable-networks |
5 years ago |