Merge "Fix variable markup (r6,r7,r8,dsR7,dsR8)"
This commit is contained in:
commit
a98975e929
@ -57,7 +57,7 @@ Deletes subcloud group details from the database.
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)]$ dcmanager subcloud-group add --name <<group>>
|
||||
~(keystone_admin)]$ dcmanager subcloud-group add --name <group>
|
||||
usage: dcmanager subcloud-group add [-h] [-f {json,shell,table,value,yaml}]
|
||||
[-c COLUMN] [--max-width <integer>]
|
||||
[--fit-width] [--print-empty] [--noindent]
|
||||
|
@ -31,7 +31,7 @@ command to fix it.
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)]$ dcmanager subcloud update <<subcloud-name>> --install-values <<subcloud-install-values-yaml>>
|
||||
~(keystone_admin)]$ dcmanager subcloud update <subcloud-name> --install-values <subcloud-install-values-yaml>
|
||||
|
||||
This type of failure is recoverable and you can retry the orchestrated
|
||||
upgrade for each of the failed subclouds using the following procedure:
|
||||
@ -50,7 +50,7 @@ upgrade for each of the failed subclouds using the following procedure:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)]$ dcmanager upgrade-strategy create <<subcloud-name>> --force <<additional options>>
|
||||
~(keystone_admin)]$ dcmanager upgrade-strategy create <subcloud-name> --force <additional options>
|
||||
|
||||
.. note::
|
||||
|
||||
|
@ -41,7 +41,7 @@ orchestrated upgrade after addressing the cause of failure:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)]$ dcmanager upgrade-strategy create <<additional options>>
|
||||
~(keystone_admin)]$ dcmanager upgrade-strategy create <additional options>
|
||||
|
||||
.. note::
|
||||
|
||||
|
@ -133,7 +133,7 @@ fails, delete subclouds, and monitor or change the managed status of subclouds.
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)]$ dcmanager subcloud reconfig <subcloud-id/name> --deploy-config \
|
||||
<filepath> --sysadmin-password <<password>>
|
||||
<filepath> --sysadmin-password <password>
|
||||
|
||||
|
||||
where ``--deploy-config`` must reference the deployment configuration file.
|
||||
|
@ -207,11 +207,11 @@ To delete a pool, use the following command:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)$ ceph osd pool delete <pool-name> <<pool-name>>
|
||||
~(keystone_admin)$ ceph osd pool delete <pool-name> <pool-name>
|
||||
|
||||
To create a pool, use the parameters from ceph osd dump, and run the following command:
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)$ ceph osd pool create {pool-name}{pg-num} {pgp-num} {replicated} <<crush-ruleset-name>>
|
||||
~(keystone_admin)$ ceph osd pool create {pool-name}{pg-num} {pgp-num} {replicated} <crush-ruleset-name>
|
||||
|
||||
|
@ -59,7 +59,7 @@ Adding a New Filesystem for Image-Conversion
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)]$ system host-fs-add <<hostname or id>> <<fs-name=size>>
|
||||
~(keystone_admin)]$ system host-fs-add <hostname or id> <fs-name=size>
|
||||
|
||||
Where:
|
||||
|
||||
@ -143,7 +143,7 @@ Removing the File System
|
||||
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)]$ system host-fs-delete <<hostname or id>> <<fs-name>>
|
||||
~(keystone_admin)]$ system host-fs-delete <hostname-or-id> <fs-name>
|
||||
|
||||
#. When the **image-conversion** file system is removed from the system, the
|
||||
/opt/conversion partition is also removed.
|
||||
|
@ -114,7 +114,7 @@ You can use this command to obtain information about a Glance image.
|
||||
.. code-block:: none
|
||||
|
||||
~(keystone_admin)$ OS_AUTH_URL=http://keystone.openstack.svc.cluster.local/v3
|
||||
~(keystone_admin)$ openstack image-show <<image-id>>
|
||||
~(keystone_admin)$ openstack image-show <image-id>
|
||||
+------------------+--------------------------------------+
|
||||
| Property | Value |
|
||||
+------------------+--------------------------------------+
|
||||
|
Loading…
x
Reference in New Issue
Block a user