starlingx/docs
Code Issues Proposed changes

Add info for installing openstack in a subcloud

Browse Source 
Also fix the EOL used to be unique. This file was using a mixture of
CRLF and LF. This was probably edited by some misconfigured editor but
as we're in Linux/Unix, it should only use LF as EOL.

Closes-Bug: 2075514

Change-Id: If48223ddc2a052168cd0af1e926dadf81abe184b
Signed-off-by: Daniel Bolgheroni <Daniel.Bolgheroni@windriver.com>
This commit is contained in:
Daniel Bolgheroni 2024-09-30 14:23:53 -03:00 committed by Daniel Bolgheroni
parent 8ba09ff4d7
commit 560b98e786
1 changed files with 111 additions and 99 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

76
doc/source/deploy_install_guides/release/openstack/install.rst
View File

@ -2,14 +2,16 @@
Install StarlingX OpenStack Install StarlingX OpenStack
=========================== ===========================
.. rubric:: |prereq|
These instructions assume that you have completed the following These instructions assume that you have completed the following
OpenStack-specific configuration tasks that are required by the underlying OpenStack-specific configuration tasks that are required by the underlying
StarlingX Kubernetes platform: StarlingX Kubernetes platform:
* All nodes have been labeled appropriately for their OpenStack role(s). * All nodes have been labeled appropriately for their OpenStack role(s).
* The vSwitch type has been configured. * The vSwitch type has been configured.
* The nova-local volume group has been configured on any node's host, if running * The nova-local volume group has been configured on any node's host, if
the compute function. running the compute function.
-------------------------------------------- --------------------------------------------
Install application manifest and helm-charts Install application manifest and helm-charts
@ -17,13 +19,14 @@ Install application manifest and helm-charts
#. Modify the size of the docker_lv filesystem. By default, the size of the #. Modify the size of the docker_lv filesystem. By default, the size of the
docker_lv filesystem is 30G, which is not enough for |prefix|-openstack docker_lv filesystem is 30G, which is not enough for |prefix|-openstack
installation. Use the ``host-fs-modify`` CLI to increase the filesystem size. installation. Use the ``host-fs-modify`` CLI to increase the filesystem
size.
The syntax is: The syntax is:
:: .. code-block:: none
system host-fs-modify <hostname or id> <fs name=size> $ system host-fs-modify <hostname or id> <fs name=size>
Where: Where:
@ -34,27 +37,27 @@ Install application manifest and helm-charts
For example: For example:
:: .. code-block:: none
system host-fs-modify controller-0 docker=60 $ system host-fs-modify controller-0 docker=60
#. Get the latest StarlingX OpenStack application (|prefix|-openstack) manifest and #. Get the latest |prod-os| application (|prefix|-openstack) manifest
helm charts. Use one of the following options: and helm charts. Use one of the following options:
* Public download from the * Public download from the `StarlingX mirror
`StarlingX mirror <https://mirror.starlingx.windriver.com/mirror/starlingx/>`_. <https://mirror.starlingx.windriver.com/mirror/starlingx/>`_.
After you select a release, helm charts are located in * After you select a release, helm charts are located in
``release/latest_release/debian/openstack/outputs/helm-charts``. ``release/latest_release/debian/openstack/outputs/helm-charts``.
#. Load the |prefix|-openstack application's package into StarlingX. The tarball #. Load the |prefix|-openstack application's package into |prod|. The
package contains |prefix|-openstack's manifest and tarball package contains |prefix|-openstack's manifest and
|prefix|-openstack's set of helm charts. For example: |prefix|-openstack's set of helm charts. For example:
.. parsed-literal:: .. code-block:: none
system application-upload |prefix|-openstack-<version>-debian-stable-versioned.tgz $ system application-upload |prefix|-openstack-<version>-debian-stable-versioned.tgz
This will: This will:
@ -64,36 +67,45 @@ Install application manifest and helm-charts
the current state of the underlying StarlingX Kubernetes platform and the the current state of the underlying StarlingX Kubernetes platform and the
recommended StarlingX configuration of OpenStack services. recommended StarlingX configuration of OpenStack services.
#. Apply the |prefix|-openstack application in order to bring StarlingX OpenStack into #. Apply the |prefix|-openstack application in order to bring |prod-os| into
service. If your environment is preconfigured with a proxy server, then service. If your environment is preconfigured with a proxy server, then make
make sure HTTPS proxy is set before applying |prefix|-openstack. sure HTTPS proxy is set before applying |prefix|-openstack.
.. parsed-literal::
system application-apply |prefix|-openstack
.. note:: .. note::
To set the HTTPS proxy at bootstrap time, refer to To set the HTTPS proxy at bootstrap time, refer to
`Ansible Bootstrap Configurations <https://docs.starlingx.io/deploy_install_guides/r7_release/ansible_bootstrap_configs.html#docker-proxy>`_. :ref:`ansible_bootstrap_configs_r7`.
To set the HTTPS proxy after installation, refer to To set the HTTPS proxy after installation, refer to
`Docker Proxy Configuration <https://docs.starlingx.io/configuration/docker_proxy_config.html>`_. :ref:`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:
.. code-block:: none
$ ldapaddgroup openstack 1001
.. code-block:: none
$ system application-apply |prefix|-openstack
#. Wait for the activation of |prefix|-openstack to complete. #. Wait for the activation of |prefix|-openstack to complete.
This can take 5-10 minutes depending on the performance of your host machine. This can take 5-10 minutes depending on the performance of your host machine.
Monitor progress with the command: Monitor progress:
:: .. code-block:: none
watch -n 5 system application-list $ watch -n 5 system application-list
---------- .. rubric:: |result|
Next steps
----------
Your OpenStack cloud is now up and running. Your OpenStack cloud is now up and running.
See :doc:`access` for details on how to access StarlingX OpenStack. See :doc:`access` for details on how to access |prod-os|.