starlingx/docs
Code Issues Proposed changes

Fix step numbering

Browse Source 
Numbered list resets mid-list are fixed.
Resolved merge conflict.
Fixed 'greybar' issue.

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I748039fb2680ec60f69b2928da219aff1da6b816
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
This commit is contained in:
Ron Stone 2021-06-09 17:23:58 -04:00
parent ccb1d63cc2
commit 73acfbfdfb
4 changed files with 36 additions and 36 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
doc/source/dist_cloud/installing-a-subcloud-using-redfish-platform-management-service.rst
View File

@ -2,9 +2,9 @@
.. vbb1579292724479 .. vbb1579292724479
.. _installing-a-subcloud-using-redfish-platform-management-service: .. _installing-a-subcloud-using-redfish-platform-management-service:
=============================================================== ============================================================
Installing a Subcloud Using Redfish Platform Management Service Install a Subcloud Using Redfish Platform Management Service
=============================================================== ============================================================
For subclouds with servers that support Redfish Virtual Media Service \(version For subclouds with servers that support Redfish Virtual Media Service \(version
1.2 or higher\), you can use the Central Cloud's CLI to install the ISO and 1.2 or higher\), you can use the Central Cloud's CLI to install the ISO and
@ -76,18 +76,18 @@ subcloud, the subcloud installation has these phases:
.. note:: .. note::
Do not power off the servers. The host portion of the server can be Do not power off the servers. The host portion of the server can be
powered off, but the |BMC| portion of the server must be powered and powered off, but the |BMC| portion of the server must be powered and
accessible from the System Controller. accessible from the System Controller.
There is no need to wipe the disks. There is no need to wipe the disks.
.. note:: .. note::
The servers require connectivity to a gateway router that provides IP The servers require connectivity to a gateway router that provides IP
routing between the subcloud management subnet and the System Controller routing between the subcloud management subnet and the System Controller
management subnet, and between the subcloud |OAM| subnet and the management subnet, and between the subcloud |OAM| subnet and the
System Controller subnet. System Controller subnet.
.. include:: ../_includes/installing-a-subcloud-using-redfish-platform-management-service.rest .. include:: ../_includes/installing-a-subcloud-using-redfish-platform-management-service.rest
:start-after: begin-ref-1 :start-after: begin-ref-1

1
doc/source/dist_cloud/migrate-an-aiosx-subcloud-to-an-aiodx-subcloud.rst
View File

@ -138,6 +138,7 @@ using the ansible playbook.
.. include:: ../_includes/migrate-an-aiosx-subcloud-to-an-aiodx-subcloud.rest .. include:: ../_includes/migrate-an-aiosx-subcloud-to-an-aiodx-subcloud.rest
.. _manually-migrate-a-subcloud-from-AIO-SX-to-AIO-DX: .. _manually-migrate-a-subcloud-from-AIO-SX-to-AIO-DX:
================================================= =================================================

3
doc/source/dist_cloud/upgrading-the-systemcontroller-using-the-cli.rst
View File

@ -266,7 +266,8 @@ Follow the steps below to manually upgrade the System Controller:
#. Upgrade **controller-0**. #. Upgrade **controller-0**.
.. xbooklink For more information, see :ref:`|updates-doc| <software-updates-and-upgrades-software-updates>` guide. For more information, see :ref:`Updates and Upgrades
<software-updates-and-upgrades-software-updates>`.
#. Lock **controller-0**. #. Lock **controller-0**.

46
doc/source/storage/kubernetes/create-readwritemany-persistent-volume-claims.rst
View File

@ -23,35 +23,35 @@ accessMode.
.. _iqu1616951298602-steps-bdr-qnm-tkb: .. _iqu1616951298602-steps-bdr-qnm-tkb:
#. Create the **rwx-test-claim** Persistent Volume Claim. Create the **rwx-test-claim** Persistent Volume Claim.
#. Create a yaml file defining the claim and its attributes. #. Create a yaml file defining the claim and its attributes.
For example: For example:
.. code-block:: none .. code-block:: none
~(keystone_admin)]$ ~(keystone_admin)]$
cat <<EOF > rwx-claim.yaml cat <<EOF > rwx-claim.yaml
kind: PersistentVolumeClaim kind: PersistentVolumeClaim
apiVersion: v1 apiVersion: v1
metadata: metadata:
name: rwx-test-claim name: rwx-test-claim
spec: spec:
accessModes: accessModes:
- ReadWriteMany - ReadWriteMany
resources: resources:
requests: requests:
storage: 1Gi storage: 1Gi
storageClassName: cephfs storageClassName: cephfs
EOF EOF
2. Apply the settings created above. #. Apply the settings created above.
.. code-block:: none .. code-block:: none
~(keystone_admin)]$ kubectl apply -f rwx-claim.yaml ~(keystone_admin)]$ kubectl apply -f rwx-claim.yaml
persistentvolumeclaim/rwx-test-claim created persistentvolumeclaim/rwx-test-claim created
This results in 1GB |PVC| being created. You can view the |PVC| using the This results in 1GB |PVC| being created. You can view the |PVC| using the
@ -64,8 +64,6 @@ following command.
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS
rwx-test-claim Bound pvc-df9f.. 1Gi RWX cephfs rwx-test-claim Bound pvc-df9f.. 1Gi RWX cephfs
.. code-block:: none
~(keystone_admin)]$ kubectl get persistentvolume ~(keystone_admin)]$ kubectl get persistentvolume
NAME CAPACITY ACCESS.. RECLAIM.. STATUS CLAIM STORAGECLASS NAME CAPACITY ACCESS.. RECLAIM.. STATUS CLAIM STORAGECLASS
pvc-df9f.. 1Gi RWX Delete Bound default/rwx-test-claim cephfs pvc-df9f.. 1Gi RWX Delete Bound default/rwx-test-claim cephfs