Chapter 8. Deploying multiple overclouds

Procedure

1. Create a new directory for the additional overcloud that you want to deploy:

   $ mkdir ~/overcloud-two

   Copy to Clipboard Toggle word wrap

2. In the new directory, create new environment files specific to the requirements of the additional overcloud, and copy any relevant environment files from the existing overcloud:

   $ cp network-data.yaml ~/overcloud-two/network-data.yaml
   $ cp network-environment.yaml ~/overcloud-two/network-environment.yaml

   Copy to Clipboard Toggle word wrap

3. Modify the environment files according to the specification of the new overcloud. For example, the existing overcloud has the name overcloud-one and uses the VLANs that you define in the network-data.yaml environment file:

   - name: InternalApi
     name_lower: internal_api_cloud_1
     service_net_map_replace: internal_api
     vip: true
     vlan: 20
     ip_subnet: '172.17.0.0/24'
     allocation_pools: [{'start': '172.17.0.4', 'end': '172.17.0.250'}]
     ipv6_subnet: 'fd00:fd00:fd00:2000::/64'
     ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:2000::10', 'end': 'fd00:fd00:fd00:2000:ffff:ffff:ffff:fffe'}]
     mtu: 1500
   - name: Storage
     ...

   Copy to Clipboard Toggle word wrap

   The new overcloud has the name overcloud-two and uses different VLANs. Edit the ~/overcloud-two/network-data.yaml environment file and include the new VLAN IDs for each subnet. You must also define a unique name_lower value, and set the service_net_map_replace attribute to the name of the network that you want to replace:

   - name: InternalApi
     name_lower: internal_api_cloud_2
     service_net_map_replace: internal_api
     vip: true
     vlan: 21
     ip_subnet: '172.21.0.0/24'
     allocation_pools: [{'start': '172.21.0.4', 'end': '172.21.0.250'}]
     ipv6_subnet: 'fd00:fd00:fd00:2001::/64'
     ipv6_allocation_pools: [{'start': 'fd00:fd00:fd00:2001::10', 'end': 'fd00:fd00:fd00:2001:ffff:ffff:ffff:fffe'}]
     mtu: 1500
   - name: Storage
     ...

   Copy to Clipboard Toggle word wrap

4. Modify the following parameters in the ~/overcloud-two/network-environment.yaml file:

   • Enter a unique value in the {'provider:physical_network'} attribute of the ExternalNetValueSpecs parameter so that overcloud-two has a distinct external network, and define the network type with the 'provider:network_type' attribute.
   • Set the ExternalInterfaceDefaultRoute parameter to the IP address of the gateway for the external network so that the overcloud has external access.

   • Set the DnsServers parameter to the IP address of your DNS server so that the overcloud can reach the DNS server.

     parameter_defaults:
       ...
       ExternalNetValueSpecs: {'provider:physical_network': 'external_2', 'provider:network_type': 'flat'}
       ExternalInterfaceDefaultRoute: 10.0.10.1
       DnsServers:
         - 10.0.10.2
       ...

     Copy to Clipboard Toggle word wrap

5. Run the openstack overcloud deploy command. Specify the core heat template collection with the --templates option, a new stack name with the --stack option, and any new environment files from the ~/overcloud-two directory:

   $ openstack overcloud deploy --templates \
       --stack overcloud-two \
       ...
       -n ~/overcloud-two/network-data.yaml \
       -e ~/overcloud-two/network-environment.yaml \
       -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml \
       -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml \
       ...

   Copy to Clipboard Toggle word wrap