Fix address ranges for openstack computes in cicd deploys
- fix ranges for deploy, control and tenant networks in:
cookied-cicd-pike-ovs-sl
cookied-cicd-pike-dvr-sl
cookied-cicd-pike-dpdk
- remove 'openstack_compute_backend_address_ranges' to avoid
misunderstanding. It is definitely not a tenant network.
To use an additional L2/L3 network for ceph, it should
be described in underlay.yaml address pools and l2 network
devices first.
Change-Id: I0d2fcbc27efb3d6c415dd223dd35fca6a23b59e1
diff --git a/tcp_tests/templates/cookied-cicd-pike-dpdk/cookiecutter-context-pike-ovs-dpdk.yaml b/tcp_tests/templates/cookied-cicd-pike-dpdk/cookiecutter-context-pike-ovs-dpdk.yaml
index fdef434..8b0bd00 100644
--- a/tcp_tests/templates/cookied-cicd-pike-dpdk/cookiecutter-context-pike-ovs-dpdk.yaml
+++ b/tcp_tests/templates/cookied-cicd-pike-dpdk/cookiecutter-context-pike-ovs-dpdk.yaml
@@ -95,12 +95,11 @@
openstack_cluster_size: compact
openstack_compute_count: '2'
openstack_compute_rack01_hostname: cmp
- openstack_compute_rack01_single_subnet: 172.16.10
- openstack_compute_rack01_tenant_subnet: 10.1.0
- openstack_compute_single_address_ranges: 172.16.10.105-172.16.10.106
- openstack_compute_deploy_address_ranges: 192.168.10.105-192.168.10.106
- openstack_compute_tenant_address_ranges: 10.1.0.105-10.1.0.106
- openstack_compute_backend_address_ranges: 10.1.0.105-10.1.0.106
+ openstack_compute_rack01_single_subnet: 10.167.4
+ openstack_compute_rack01_tenant_subnet: 10.167.6
+ openstack_compute_single_address_ranges: 10.167.4.105-10.167.4.106
+ openstack_compute_deploy_address_ranges: 10.167.5.105-10.167.5.106
+ openstack_compute_tenant_address_ranges: 10.167.6.105-10.167.6.106
openstack_control_address: 10.167.4.100
openstack_control_hostname: ctl
openstack_control_node01_address: 10.167.4.101