Skip to content

Commit

Permalink
Remove outdated information
Browse files Browse the repository at this point in the history
  • Loading branch information
seunghun1ee committed Dec 5, 2024
1 parent 1788f7b commit a6872b5
Show file tree
Hide file tree
Showing 3 changed files with 2 additions and 38 deletions.
2 changes: 1 addition & 1 deletion doc/source/operations/ceph-management.rst
Original file line number Diff line number Diff line change
Expand Up @@ -120,7 +120,7 @@ Ceph can report details about failed OSDs by running:
sudo cephadm shell
ceph health detail
.. note ::
.. note::

Remember to run ceph/rbd commands from within ``cephadm shell``
(preferred method) or after installing Ceph client. Details in the
Expand Down
9 changes: 1 addition & 8 deletions doc/source/operations/control-plane-operation.rst
Original file line number Diff line number Diff line change
Expand Up @@ -81,12 +81,6 @@ Then, create another silence to match ``hostname=<hostname>`` (this is
required because, for the OpenStack exporter, the instance is the host running
the monitoring service rather than the host being monitored).

.. note::

After creating the silence, you may get redirected to a 404 page. This is a
`known issue <https://github.com/prometheus/alertmanager/issues/1377>`__
when running several Alertmanager instances behind HAProxy.

Control Plane Shutdown Procedure
================================

Expand Down Expand Up @@ -353,8 +347,7 @@ Deploying to a Specific Hypervisor
----------------------------------

To test creating an instance on a specific hypervisor, *as an admin-level user*
you can specify the hypervisor name as part of an extended availability zone
description.
you can specify the hypervisor name.

To see the list of hypervisor names:

Expand Down
29 changes: 0 additions & 29 deletions doc/source/operations/gpu-in-openstack.rst
Original file line number Diff line number Diff line change
Expand Up @@ -190,35 +190,6 @@ Configure the VGPU devices:
- mdev_type: nvidia-697
index: 1
Running the playbook
^^^^^^^^^^^^^^^^^^^^

The playbook defined in the :ref:`previous step<NVIDIA OS Configuration>`
should be run after `kayobe overcloud host configure` has completed. This will
ensure the host has been fully bootstrapped. With default settings, internet
connectivity is required to download `MIG Partition Editor for NVIDIA GPUs`. If
this is not desirable, you can override the one of the following variables
(depending on host OS):

.. code-block:: yaml
:caption: $KAYOBE_CONFIG_PATH/inventory/group_vars/compute_vgpu/vgpu
vgpu_nvidia_mig_manager_rpm_url: "https://github.com/NVIDIA/mig-parted/releases/download/v0.5.1/nvidia-mig-manager-0.5.1-1.x86_64.rpm"
vgpu_nvidia_mig_manager_deb_url: "https://github.com/NVIDIA/mig-parted/releases/download/v0.5.1/nvidia-mig-manager_0.5.1-1_amd64.deb"
For example, you may wish to upload these artifacts to the local pulp.

Run the playbook that you defined earlier:

.. code-block:: shell
kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/host-configure.yml
Note: This will reboot the hosts on first run.

The playbook may be added as a hook in ``$KAYOBE_CONFIG_PATH/hooks/overcloud-host-configure/post.d``; this will
ensure you do not forget to run it when hosts are enrolled in the future.

.. _NVIDIA Kolla Ansible Configuration:

Kolla-Ansible configuration
Expand Down

0 comments on commit a6872b5

Please sign in to comment.