Skip to content

Commit a6872b5

Browse files
committed
Remove outdated information
1 parent 1788f7b commit a6872b5

File tree

3 files changed

+2
-38
lines changed

3 files changed

+2
-38
lines changed

doc/source/operations/ceph-management.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -120,7 +120,7 @@ Ceph can report details about failed OSDs by running:
120120
sudo cephadm shell
121121
ceph health detail
122122
123-
.. note ::
123+
.. note::
124124

125125
Remember to run ceph/rbd commands from within ``cephadm shell``
126126
(preferred method) or after installing Ceph client. Details in the

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

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -81,12 +81,6 @@ Then, create another silence to match ``hostname=<hostname>`` (this is
8181
required because, for the OpenStack exporter, the instance is the host running
8282
the monitoring service rather than the host being monitored).
8383

84-
.. note::
85-
86-
After creating the silence, you may get redirected to a 404 page. This is a
87-
`known issue <https://github.com/prometheus/alertmanager/issues/1377>`__
88-
when running several Alertmanager instances behind HAProxy.
89-
9084
Control Plane Shutdown Procedure
9185
================================
9286

@@ -353,8 +347,7 @@ Deploying to a Specific Hypervisor
353347
----------------------------------
354348

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

359352
To see the list of hypervisor names:
360353

doc/source/operations/gpu-in-openstack.rst

Lines changed: 0 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -190,35 +190,6 @@ Configure the VGPU devices:
190190
- mdev_type: nvidia-697
191191
index: 1
192192
193-
Running the playbook
194-
^^^^^^^^^^^^^^^^^^^^
195-
196-
The playbook defined in the :ref:`previous step<NVIDIA OS Configuration>`
197-
should be run after `kayobe overcloud host configure` has completed. This will
198-
ensure the host has been fully bootstrapped. With default settings, internet
199-
connectivity is required to download `MIG Partition Editor for NVIDIA GPUs`. If
200-
this is not desirable, you can override the one of the following variables
201-
(depending on host OS):
202-
203-
.. code-block:: yaml
204-
:caption: $KAYOBE_CONFIG_PATH/inventory/group_vars/compute_vgpu/vgpu
205-
206-
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"
207-
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"
208-
209-
For example, you may wish to upload these artifacts to the local pulp.
210-
211-
Run the playbook that you defined earlier:
212-
213-
.. code-block:: shell
214-
215-
kayobe playbook run $KAYOBE_CONFIG_PATH/ansible/host-configure.yml
216-
217-
Note: This will reboot the hosts on first run.
218-
219-
The playbook may be added as a hook in ``$KAYOBE_CONFIG_PATH/hooks/overcloud-host-configure/post.d``; this will
220-
ensure you do not forget to run it when hosts are enrolled in the future.
221-
222193
.. _NVIDIA Kolla Ansible Configuration:
223194

224195
Kolla-Ansible configuration

0 commit comments

Comments
 (0)