Skip to content

Commit 93183fc

Browse files
fultonjclaude
authored andcommitted
Add network_routes to dcn1 and dcn2 stacks for ci-framework
Add network-specific routes to dcn_nostorage.yaml stack configurations to enable ci-framework's os-net-config template to render cross-site routes for DCN compute nodes. Problem: - ci-framework pre-generates /etc/os-net-config/tripleo_config.yaml via ansible template before TripleO Heat deployment runs - This bypasses TripleO Heat NIC templates completely - Routes defined in network_data.yaml.j2 are never rendered to compute nodes Solution: - Add network_routes configuration to dcn1 and dcn2 stacks in dcn_nostorage.yaml - ci-framework's os_net_config_overcloud.yml.j2 template will consume these routes and render them to /etc/os-net-config/tripleo_config.yaml Routes Added: - DCN1: Routes to central (172.17/18/19.0.0/24) and dcn2 (172.17/18/19.20.0/24) via appropriate gateways - DCN2: Routes to central (172.17/18/19.0.0/24) and dcn1 (172.17/18/19.10.0/24) via appropriate gateways This enables DCN compute nodes to reach OVN southbound DB and other services on central controllers using the correct source IP addresses. Related: Commit bfc6d4d added routes to network_data.yaml.j2, but those routes were never being used due to ci-framework bypassing Heat templates. Co-Authored-By: Claude <noreply@anthropic.com> Signed-off-by: John Fulton <fulton@redhat.com>
1 parent d53d409 commit 93183fc

1 file changed

Lines changed: 32 additions & 0 deletions

File tree

scenarios/dcn_nostorage.yaml

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -161,6 +161,22 @@ stacks:
161161
- ip_netmask: 0.0.0.0/0
162162
next_hop: 192.168.133.1
163163
default: true
164+
network_routes:
165+
internalapidcn1:
166+
- ip_netmask: 172.17.0.0/24
167+
next_hop: 172.17.10.1
168+
- ip_netmask: 172.17.20.0/24
169+
next_hop: 172.17.10.1
170+
storagedcn1:
171+
- ip_netmask: 172.18.0.0/24
172+
next_hop: 172.18.10.1
173+
- ip_netmask: 172.18.20.0/24
174+
next_hop: 172.18.10.1
175+
tenantdcn1:
176+
- ip_netmask: 172.19.0.0/24
177+
next_hop: 172.19.10.1
178+
- ip_netmask: 172.19.20.0/24
179+
next_hop: 172.19.10.1
164180
- stackname: dcn2
165181
args:
166182
- "--override-ansible-cfg /home/zuul/ansible_config.cfg"
@@ -190,3 +206,19 @@ stacks:
190206
- ip_netmask: 0.0.0.0/0
191207
next_hop: 192.168.144.1
192208
default: true
209+
network_routes:
210+
internalapidcn2:
211+
- ip_netmask: 172.17.0.0/24
212+
next_hop: 172.17.20.1
213+
- ip_netmask: 172.17.10.0/24
214+
next_hop: 172.17.20.1
215+
storagedcn2:
216+
- ip_netmask: 172.18.0.0/24
217+
next_hop: 172.18.20.1
218+
- ip_netmask: 172.18.10.0/24
219+
next_hop: 172.18.20.1
220+
tenantdcn2:
221+
- ip_netmask: 172.19.0.0/24
222+
next_hop: 172.19.20.1
223+
- ip_netmask: 172.19.10.0/24
224+
next_hop: 172.19.20.1

0 commit comments

Comments
 (0)