[user guides] Change nova filenames to reference os commands

This patch adjusts filenames to remove the word `nova`, which
suggests users will run nova commands. Instead, adding `os`
indicates users will run OpenStack commands.

The patch also includes minor adjustments to wording, and
section references.

Change-Id: I04a96d982a404bdaf94ecfcfa7c0ef1205106ed0
Closes-Bug: #1666294
This commit is contained in:
RobiJoe 2017-03-15 10:17:13 +10:00
parent b9c3636f66
commit 2d5db66283
3 changed files with 10 additions and 10 deletions

View File

@ -10,7 +10,7 @@ This section includes tasks specific to the OpenStack environment.
cli-nova-specify-host.rst
cli-nova-numa-libvirt.rst
cli-nova-evacuate.rst
cli-nova-migrate.rst
cli-nova-migrate-cfg-ssh.rst
cli-os-migrate.rst
cli-os-migrate-cfg-ssh.rst
cli-admin-manage-ip-addresses.rst
cli-admin-manage-stacks.rst

View File

@ -1,4 +1,4 @@
.. _clinovamigratecfgssh:
.. _cli-os-migrate-cfg-ssh:
===================================
Configure SSH between compute nodes
@ -76,4 +76,3 @@ complete the following steps:
# systemctl restart libvirtd.service
# systemctl restart openstack-nova-compute.service

View File

@ -9,7 +9,7 @@ not assume that the instance has shared storage available on the
target host. If you are using SSH tunneling, you must ensure that
each node is configured with SSH key authentication so that the
Compute service can use SSH to move disks to other nodes.
For more information, see :ref:`clinovamigratecfgssh`.
For more information, see :ref:`cli-os-migrate-cfg-ssh`.
#. To list the VMs you want to migrate, run:
@ -62,8 +62,8 @@ For more information, see :ref:`clinovamigratecfgssh`.
.. note::
If you see this error, it means you are either
trying the command with the wrong credentials,
If you see the following error, it means you are either
running the command with the wrong credentials,
such as a non-admin user, or the ``policy.json``
file prevents migration for your user:
@ -72,12 +72,13 @@ For more information, see :ref:`clinovamigratecfgssh`.
.. note::
If you see an error similar to this message, SSH tunneling
was not set up between the compute nodes:
If you see the following error, similar to this message, SSH
tunneling was not set up between the compute nodes:
``ProcessExecutionError: Unexpected error while running command.``
``Stderr: u Host key verification failed.\r\n``
The instance is booted from a new host, but preserves its configuration
including its ID, name, any metadata, IP address, and other properties.
including instance ID, name, IP address, any metadata, and other
properties.