Chapter 2. Configuring the undercloud

Procedure

1. Log into the undercloud as the stack user.

2. If you do not already have an undercloud.conf, copy the sample template file:

   [stack@director ~]$ cp /usr/share/instack-undercloud/undercloud.conf.sample ~/undercloud.conf

   Copy to Clipboard Toggle word wrap
3. Edit your undercloud.conf.

4. In the [DEFAULT] section:

   1. Set local_ip to the undercloud IP on leaf0:

      local_ip = 192.168.10.1/24

      Copy to Clipboard Toggle word wrap

   2. Set undercloud_public_vip to the externally facing IP address of the undercloud:

      undercloud_public_vip = 10.1.1.1

      Copy to Clipboard Toggle word wrap

   3. Set undercloud_admin_vip to the administration IP address of the undercloud. This IP address is usually on leaf0:

      undercloud_admin_vip = 192.168.10.2

      Copy to Clipboard Toggle word wrap

   4. Set local_interface to the interface to bridge for the local network:

      local_interface = eth1

      Copy to Clipboard Toggle word wrap

   5. Set enable_routed_networks to true:

      enable_routed_networks = true

      Copy to Clipboard Toggle word wrap

   6. Define your list of subnets using the subnets parameter. Define one subnet for each layer 2 segment in the routed spine and leaf:

      subnets = leaf0,leaf1,leaf2

      Copy to Clipboard Toggle word wrap

   7. Specify the subnet associated with the physical layer 2 segment local to the undercloud using the local_subnet parameter:

      local_subnet = leaf0

      Copy to Clipboard Toggle word wrap

5. Create a new section per each subnet defined with the subnets parameter:

   [leaf0]
   cidr = 192.168.10.0/24
   dhcp_start = 192.168.10.10
   dhcp_end = 192.168.10.90
   inspection_iprange = 192.168.10.100,192.168.10.190
   gateway = 192.168.10.1
   masquerade = False
   
   [leaf1]
   cidr = 192.168.11.0/24
   dhcp_start = 192.168.11.10
   dhcp_end = 192.168.11.90
   inspection_iprange = 192.168.11.100,192.168.11.190
   gateway = 192.168.11.1
   masquerade = False
   
   [leaf2]
   cidr = 192.168.12.0/24
   dhcp_start = 192.168.12.10
   dhcp_end = 192.168.12.90
   inspection_iprange = 192.168.12.100,192.168.12.190
   gateway = 192.168.12.1
   masquerade = False

   Copy to Clipboard Toggle word wrap
6. Save the undercloud.conf file.

7. Run the undercloud installation command:

   [stack@director ~]$ openstack undercloud install

   Copy to Clipboard Toggle word wrap

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Create flavors for each custom role:

   $ ROLES="control0 compute_leaf0 compute_leaf1 compute_leaf2 ceph-storage_leaf0 ceph-storage_leaf1 ceph-storage_leaf2"
   $ for ROLE in $ROLES; do openstack flavor create --id auto --ram 4096 --disk 40 --vcpus 1 $ROLE ; done
   $ for ROLE in $ROLES; do openstack flavor set --property "cpu_arch"="x86_64" --property "capabilities:boot_option"="local" --property "capabilities:profile"="$ROLE" $ROLE ; done

   Copy to Clipboard Toggle word wrap

3. Tag nodes to their respective leaf networks. For example, run the following command to tag a node with UUID 58c3d07e-24f2-48a7-bbb6-6843f0e8ee13 to the compute role on Leaf2:

   $ openstack baremetal node set --property capabilities='profile:compute_leaf2,boot_option:local' 58c3d07e-24f2-48a7-bbb6-6843f0e8ee13

   Copy to Clipboard Toggle word wrap

4. Create an environment file (~/templates/node-data.yaml) that contains the mapping of flavors to roles:

   parameter_defaults:
     OvercloudController0Flavor: control0
     Controller0Count: 3
     OvercloudCompute0Flavor: compute_leaf0
     Compute0Count: 3
     OvercloudCompute1Flavor: compute_leaf1
     Compute1Count: 3
     OvercloudCompute2Flavor: compute_leaf2
     Compute2Count: 3
     OvercloudCephStorage0Flavor: ceph-storage_leaf0
     CephStorage0Count: 3
     OvercloudCephStorage1Flavor: ceph-storage_leaf1
     CephStorage1Count: 3
     OvercloudCephStorage2Flavor: ceph-storage_leaf2
     CephStorage2Count: 3

   Copy to Clipboard Toggle word wrap

   You can also set the number of nodes to deploy in the overcloud using each respective *Count` parameter.

Procedure

1. Source the stackrc file:

   $ source ~/stackrc

   Copy to Clipboard Toggle word wrap

2. Check the bare metal nodes:

   $ openstack baremetal node list

   Copy to Clipboard Toggle word wrap

3. Ensure the bare metal nodes are either in enroll or manageable state. If the bare metal node is not in one of these states, the command used to set the physical_network property on the baremetal port will fail. To set all nodes to manageable state run the following command:

   $ for node in $(openstack baremetal node list -f value -c Name); do openstack baremetal node manage $node --wait; done

   Copy to Clipboard Toggle word wrap

4. Check which baremetal ports are associated with which baremetal node. For example:

   $ openstack baremetal port list --node <node-uuid>

   Copy to Clipboard Toggle word wrap

5. Set the physical-network parameter for the ports. In the example below, three subnets are defined in the configuration: leaf0, leaf1, and leaf2. The local_subnet is leaf0. Since the physical network for the local_subnet is always ctlplane, the baremetal port connected to leaf0 uses ctlplane. The remaining ports use the other leaf names:

   $ openstack baremetal port set --physical-network ctlplane <port-uuid>
   $ openstack baremetal port set --physical-network leaf1 <port-uuid>
   $ openstack baremetal port set --physical-network leaf2 <port-uuid>
   $ openstack baremetal port set --physical-network leaf2 <port-uuid>

   Copy to Clipboard Toggle word wrap

6. Make sure the nodes are in available state before deploying the overcloud:

   $ openstack overcloud node provide --all-manageable

   Copy to Clipboard Toggle word wrap