Chapter 2. Configuring and deploying a multi-cell environment with the same networks

Procedure

1. Log in to the undercloud as the stack user.

2. Source the stackrc file:

   [stack@director ~]$ source ~/stackrc

3. Export the cell configuration and password information from the default cell in the overcloud stack to a new common environment file for the multi-cell deployment:

   (undercloud)$ sudo --preserve-env openstack overcloud cell export \
    --output-file common/default_cell_export.yaml

   This command exports the EndpointMap, HostsEntry, AllNodesConfig, GlobalConfig parameters, and the password information, to the common environment file.

   Tip

   If the environment file already exists, enter the command with the --force-overwrite or -f option.

Procedure

1. Create the cellcontroller overcloud flavor for the cell controller node:

   (undercloud)$ openstack flavor create --id auto \
    --ram <ram_size_mb> --disk <disk_size_gb> \
    --vcpus <no_vcpus> cellcontroller

   • Replace <ram_size_mb> with the RAM of the bare metal node, in MB.
   • Replace <disk_size_gb> with the size of the disk on the bare metal node, in GB.

   • Replace <no_vcpus> with the number of CPUs on the bare metal node.

     Note

     These properties are not used for scheduling instances. However, the Compute scheduler does use the disk size to determine the root partition size.

2. Retrieve a list of your nodes to identify their UUIDs:

   (undercloud)$ openstack baremetal node list

3. Tag each bare metal node that you want to designate as a cell controller with a custom cell controller resource class:

   (undercloud)$ openstack baremetal node set \
    --resource-class baremetal.CELL-CONTROLLER <node>

   Replace <node> with the ID of the bare metal node.

4. Associate the cellcontroller flavor with the custom cell controller resource class:

   (undercloud)$ openstack flavor set \
    --property resources:CUSTOM_BAREMETAL_CELL_CONTROLLER=1 \
     cellcontroller

   To determine the name of a custom resource class that corresponds to a resource class of a Bare Metal service node, convert the resource class to uppercase, replace each punctuation mark with an underscore, and prefix with CUSTOM_.

   Note

   A flavor can request only one instance of a bare metal resource class.

5. Set the following flavor properties to prevent the Compute scheduler from using the bare metal flavor properties to schedule instances:

   (undercloud)$ openstack flavor set \
    --property resources:VCPU=0 --property resources:MEMORY_MB=0 \
    --property resources:DISK_GB=0 cellcontroller

Procedure

1. Create a new directory for the new cells:

   (undercloud)$ mkdir cells

2. Create a new environment file for each additional cell in the cell directory, cells, for cell-specific parameters, for example, /cells/cell1.yaml.

3. Add the following parameters to each environment file, updating the parameter values for each cell in your deployment:

   resource_registry:
     OS::TripleO::Network::Ports::OVNDBsVipPort: /usr/share/openstack-tripleo-heat-templates/network/ports/noop.yaml
     OS::TripleO::Network::Ports::RedisVipPort: /usr/share/openstack-tripleo-heat-templates/network/ports/noop.yaml
   
   parameter_defaults:
     # Disable network creation in order to use the `network_data.yaml` file from the overcloud stack,
     # and create ports for the nodes in the separate stacks on the existing networks.
     ManageNetworks: false
   
     # Specify that this is an additional cell
     NovaAdditionalCell: True
   
     # The DNS names for the VIPs for the cell
     CloudName: cell1.ooo.test
     CloudNameInternal: cell1.internalapi.ooo.test
     CloudNameStorage: cell1.storage.ooo.test
     CloudNameStorageManagement: cell1.storagemgmt.ooo.test
     CloudNameCtlplane: cell1.ctlplane.ooo.test
   
     # Map the flavors to use for the CellController and Compute roles
     OvercloudCellControllerFlavor: cellcontroller
     OvercloudComputeFlavor: compute
   
     # Number of controllers/computes in the cell
     CellControllerCount: 3
     ComputeCount: 1
   
     # Node names must be unique across all cells
     ComputeHostnameFormat: 'cell1-compute-%index%'
     CellControllerHostnameFormat: 'cell1-cellcontroller-%index%'

4. To allocate a network resource to the cell and register cells to the network, add the following parameters to each environment file:

   resource_registry:
     OS::TripleO::CellController::Net::SoftwareConfig: /home/stack/templates/nic-configs/cellcontroller.yaml
     OS::TripleO::Compute::Net::SoftwareConfig: /home/stack/templates/nic-configs/compute.yaml

5. Add the environment files to the stack with your other environment files and deploy the cell stack:

   (undercloud)$ openstack overcloud deploy --templates \
    --stack cell1 \
    -e [your environment files] \
    -r $HOME/common/cell_roles_data.yaml \
    -e $HOME/common/default_cell_export.yaml \
    -e $HOME/cells/cell1.yaml

   Repeat this step for each cell stack until all your cell stacks are deployed.