Update old contents

Author: seunghun1ee

doc/source/operations/control-plane-operation.rst

@@ -294,27 +294,61 @@ node is powered back on.
 Software Updates
 ================
 
-Update Packages on Control Plane
---------------------------------
+Update Host Packages on Control Plane
+-------------------------------------
 
-OS packages can be updated with:
+The host packages and Kolla container images are distributed from `StackHPC Release Train
+<https://stackhpc.github.io/stackhpc-release-train/>`__ to ensure tested and reliable
+software releases are provided.
+
+Syncing new StackHPC Release Train contents to local Pulp server is needed before updating
+host packages and/or Kolla services.
+
+To sync host packages:
+
+.. code-block:: console
+
+   kayobe# kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-sync.yml
+   kayobe# kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-publish.yml
+
+If the system is production environment and want to use packages tested in test/staging
+environment, you can promote them by:
+
+.. code-block:: console
+
+   kayobe# kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-repo-promote-production.yml
+
+To sync container images:
 
 .. code-block:: console
 
-   kayobe# kayobe overcloud host package update --limit <Hypervisor node> --packages '*'
-   kayobe# kayobe overcloud seed package update --packages '*'
+   kayobe# kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-container-sync.yml
+   kayobe# kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/pulp-container-publish.yml
+
+Once sync with StackHPC Release Train is done, new contents will be accessible from local
+Pulp server.
+
+Host packages can be updated with:
+
+.. code-block:: console
+
+   kayobe# kayobe overcloud host package update --limit <node> --packages '*'
+   kayobe# kayobe seed host package update --packages '*'
 
 See https://docs.openstack.org/kayobe/latest/administration/overcloud.html#updating-packages
 
-Minor Upgrades to OpenStack Services
-------------------------------------
+Upgrading OpenStack Services
+----------------------------
+
+* Update tags for the images in ``etc/kayobe/kolla-image-tags.yml`` to use the new value of ``kolla_openstack_release``
+* Pull container images to overcloud hosts with ``kayobe overcloud container image pull``
+* Run ``kayobe overcloud service upgrade``
+
+You can update the subset of containers or hosts by
+
+.. code-block:: console
 
-* Pull latest changes from upstream stable branch to your own ``kolla`` fork (if applicable)
-* Update ``kolla_openstack_release`` in ``etc/kayobe/kolla.yml`` (unless using default)
-* Update tags for the images in ``etc/kayobe/kolla/globals.yml`` to use the new value of ``kolla_openstack_release``
-* Rebuild container images
-* Pull container images to overcloud hosts
-* Run kayobe overcloud service upgrade
+   kayobe# kayobe overcloud service upgrade --kolla-tags <service> --limit <hostname> --kolla-limit <hostname>
 
 For more information, see: https://docs.openstack.org/kayobe/latest/upgrading.html
 
@@ -339,7 +373,7 @@ To boot an instance on a specific hypervisor
 
 .. code-block:: console
 
-   openstack server create --flavor <Flavour name>--network <Network name> --key-name <key> --image <Image name> --availability-zone nova::<Hypervisor name> <VM name>
+   openstack server create --flavor <flavour name>--network <network name> --key-name <key> --image <Image name> --os-compute-api-version 2.74 --host <hypervisor hostname> <vm name>
 
 Cleanup Procedures
 ==================

doc/source/operations/customising-horizon.rst

@@ -46,79 +46,35 @@ Further reading:
 * https://docs.openstack.org/horizon/latest/configuration/themes.html
 * https://docs.openstack.org/horizon/latest/configuration/branding.html
 
-Building a Horizon container image with custom theme
-----------------------------------------------------
+Adding the custom theme
+-----------------------
 
-Building a custom container image for Horizon can be done by modifying
-``kolla.yml`` to fetch the custom theme and include it in the image:
+Create a directory and transfer custom theme files to it ``$KAYOBE_CONFIG_PATH/kolla/config/horizon/themes/<custom theme name>``.
 
-.. code-block:: yaml
-
-   kolla_sources:
-     horizon-additions-theme-<custom theme name>:
-       type: "git"
-       location: <custom theme repository url>
-       reference: master
-
-   kolla_build_blocks:
-     horizon_footer: |
-       # Binary images cannot use the additions mechanism.
-       {% raw %}
-       {% if install_type == 'source' %}
-       ADD additions-archive /
-       RUN mkdir -p /etc/openstack-dashboard/themes/<custom theme name> \
-         && cp -R /additions/horizon-additions-theme-<custom theme name>-archive-master/* /etc/openstack-dashboard/themes/<custom theme name>/ \
-         && chown -R horizon: /etc/openstack-dashboard/themes
-       {% endif %}
-       {% endraw %}
-
-If using a specific container image tag, don't forget to set:
+Define the custom theme in ``etc/kayobe/kolla/globals.yml``
 
 .. code-block:: yaml
-
-   kolla_tag: mytag
-
-Build the image with:
-
-.. code-block:: console
-
-   kayobe overcloud container image build horizon -e kolla_install_type=source --push
-
-Pull the new Horizon container to the controller:
-
-.. code-block:: console
-
-   kayobe overcloud container image pull --kolla-tags horizon
+   horizon_custom_themes:
+      - name: <custom theme name>
+        label: <custom theme label> # This will be the visible name to users
 
 Deploy and use the custom theme
 -------------------------------
 
-Switch to source image type in ``${KAYOBE_CONFIG_PATH}/kolla/globals.yml``:
-
-.. code-block:: yaml
-
-   horizon_install_type: source
-
-You may also need to update the container image tag:
-
-.. code-block:: yaml
-
-   horizon_tag: mytag
-
 Configure Horizon to include the custom theme and use it by default:
 
 .. code-block:: console
 
-   mkdir -p ${KAYOBE_CONFIG_PATH}/kolla/config/horizon/
+   mkdir -p $KAYOBE_CONFIG_PATH/kolla/config/horizon/
 
-Add to ``${KAYOBE_CONFIG_PATH}/kolla/config/horizon/custom_local_settings``:
+Create file ``$KAYOBE_CONFIG_PATH/kolla/config/horizon/custom_local_settings`` and add followings
 
 .. code-block:: console
 
    AVAILABLE_THEMES = [
        ('default', 'Default', 'themes/default'),
        ('material', 'Material', 'themes/material'),
-       ('<custom theme name>', '<custom theme visible name>', '/etc/openstack-dashboard/themes/<custom theme name>'),
+       ('<custom theme name>', '<custom theme label>', 'themes/<custom theme name>'),
    ]
    DEFAULT_THEME = '<custom theme name>'
 
@@ -137,9 +93,6 @@ Deploy with:
 Troubleshooting
 ---------------
 
-Make sure you build source images, as binary images cannot use the addition
-mechanism used here.
-
 If the theme is selected but the logo doesn’t load, try running these commands
 inside the ``horizon`` container:
 

doc/source/operations/openstack-reconfiguration.rst

@@ -138,48 +138,3 @@ And then to enable a hypervisor again:
 
    admin# openstack compute service set --enable \
           <Hypervisor name> nova-compute
-
-Managing Space in the Docker Registry
-=====================================
-
-If the Docker registry becomes full, this can prevent container updates and
-(depending on the storage configuration of the seed host) could lead to other
-problems with services provided by the seed host.
-
-To remove container images from the Docker Registry, follow this process:
-
-* Reconfigure the registry container to allow deleting containers. This can be
-  done in ``docker-registry.yml`` with Kayobe:
-
-.. code-block:: yaml
-
-   docker_registry_env:
-     REGISTRY_STORAGE_DELETE_ENABLED: "true"
-
-* For the change to take effect, run:
-
-.. code-block:: console
-
-   kayobe seed host configure
-
-* A helper script is useful, such as https://github.com/byrnedo/docker-reg-tool
-  (this requires ``jq``). To delete all images with a specific tag, use:
-
-.. code-block:: console
-
-   for repo in `./docker_reg_tool http://registry-ip:4000 list`; do
-        ./docker_reg_tool http://registry-ip:4000 delete $repo $tag
-   done
-
-* Deleting the tag does not actually release the space. To actually free up
-  space, run garbage collection:
-
-.. code-block:: console
-
-   seed# docker exec docker_registry bin/registry garbage-collect /etc/docker/registry/config.yml
-
-The seed host can also accrue a lot of data from building container images.
-The images stored locally in the seed host can be seen using ``docker image ls``.
-
-Old and redundant images can be identified from their names and tags, and
-removed using ``docker image rm``.