Install and Provision the Central Cloud

Installing the Central Cloud is similar to installing a standalone StarlingX system.

About this task

The Central Cloud supports the following deployment configurations:

• AIO-DX with 0 or more Worker Nodes deployment, see All-in-one (AIO) Duplex Configuration

• Standard with dedicated internal Storage Nodes and 1 or more Worker Nodes, see Worker Function Performance Profiles

• Standard with dedicated external Netapp Storage backend and 1 or more Worker Nodes, see Standard Configuration with Dedicated Storage

• Standard with Controller Storage, see Standard Configuration with Controller Storage

Procedure

Complete the StarlingX procedure for your deployment scenario with the modifications noted below.

• When creating the user configuration overrides for the Ansible bootstrap playbook in /home/sysadmin/localhost.yml

  • Add the distributed_cloud_role parameter (as shown below) to your /home/sysadmin/localhost.yml Ansible bootstrap override file to indicate that this cloud will play the role of the Central Cloud / System Controller.

  • Restrict the range of addresses for the management network (using management_start_address and management_end_address, as shown below) to exclude the IP addresses reserved for gateway routers that provide routing to the subclouds’ management subnets.

• Also, include the container images shown below in additional_local_registry_images, required for support of subcloud installs with the Redfish Platform Management Service, and subcloud installs using a Ceph storage backend.

system_mode: duplex
distributed_cloud_role: systemcontroller


management_start_address: <X.Y.Z>.2
management_end_address: <X.Y.Z>.50



additional_local_registry_images:
    - quay.io/external_storage/rbd-provisioner:v2.1.1-k8s1.11
    - docker.io/openstackhelm/ceph-config-helper:ubuntu_jammy_18.2.2-1-20240312

where <X.Y.Z> are replaced with the correct values for your environment.