docs/doc/source/deploy_install_guides/release/openstack/install.rst

Install StarlingX OpenStack

These instructions assume that you have completed the following OpenStack-specific configuration tasks that are required by the underlying StarlingX Kubernetes platform:

• All nodes have been labeled appropriately for their OpenStack role(s).
• The vSwitch type has been configured.
• The nova-local volume group has been configured on any node's host, if running the compute function.

Install application manifest and helm-charts

1. Modify the size of the docker_lv filesystem. By default, the size of the docker_lv filesystem is 30G, which is not enough for -openstack installation. Use the host-fs-modify CLI to increase the filesystem size.

   The syntax is:

   $ system host-fs-modify <hostname or id> <fs name=size>

   Where:

   • hostname or id is the location where the file system will be added.
   • fs name is the file system name.
   • size is an integer indicating the file system size in Gigabytes.

   For example:

   $ system host-fs-modify controller-0 docker=60

2. Get the latest application (-openstack) manifest and helm charts. Use one of the following options:

   • Public download from the StarlingX mirror.
   • After you select a release, helm charts are located in release/latest_release/debian/openstack/outputs/helm-charts.

3. Load the -openstack application's package into . The tarball package contains -openstack's manifest and -openstack's set of helm charts. For example:

   $ system application-upload |prefix|-openstack-<version>-debian-stable-versioned.tgz

   This will:

   • Load the manifest and helm charts.
   • Internally manage helm chart override values for each chart.
   • Automatically generate system helm chart overrides for each chart based on the current state of the underlying StarlingX Kubernetes platform and the recommended StarlingX configuration of OpenStack services.

   By default, -openstack is configured to support Rook-Ceph deployments. For host-based Ceph deployments, the following script needs to be executed to override the ceph-config-helper image used by -openstack helm charts:

   NAMESPACE=openstack
   APP_NAME=|prefix|-openstack
   DOCKER_REGISTRY_URL=<your docker registry url> # e.g., myprivateregistry.abc.com:9001/docker.io
   HOST_CEPH_IMAGE=${DOCKER_REGISTRY_URL}/openstackhelm/ceph-config-helper:ubuntu_bionic-20201223
   OVERRIDE_CHARTS=(
      "cinder" "cinder"
      "glance"
      "libvirt"
      "nova" "nova"
   )
   
   OVERRIDE_IMAGES=(
      "cinder_backup_storage_init" "cinder_storage_init"  # Cinder images
      "glance_storage_init"                               # Glance image
      "ceph_config_helper"                                # libvirt image 
      "nova_service_cleaner" "nova_storage_init"          # Nova images
   )
   
   for ((i=0; i<${#OVERRIDE_CHARTS[@]}; i++)); do
      CHART=${OVERRIDE_CHARTS[$i]}
      IMAGE=${OVERRIDE_IMAGES[$i]}
      echo "Overriding ${IMAGE} image of ${CHART} chart"
      system helm-override-update ${APP_NAME} ${CHART} ${NAMESPACE} \
         --reuse-values --set images.tags.${IMAGE}=${HOST_CEPH_IMAGE}
   done 

4. Apply the -openstack application in order to bring into service. If your environment is preconfigured with a proxy server, then make sure HTTPS proxy is set before applying -openstack.

   Note

   To set the HTTPS proxy at bootstrap time, refer to ansible_bootstrap_configs_r7.

   To set the HTTPS proxy after installation, refer to docker_proxy_config.

   Note

   To install in a subcloud, it is not possible to create all the resources automatically. More specifically, a ldap group called openstack with the gid 1001 should be created in the system controller for the installation to proceed properly. To do this, in the system controller:

   $ ldapaddgroup openstack 1001

   $ system application-apply |prefix|-openstack

5. Wait for the activation of -openstack to complete.

   This can take 5-10 minutes depending on the performance of your host machine.

   Monitor progress:

   $ watch -n 5 system application-list

Your OpenStack cloud is now up and running.

See access for details on how to access .