openstack
/
operations-guide
Code Issues Proposed changes

[ops-guide] Deprecate the nova-manage sub-command 

Remove all instances of the nova-manage sub-command in the ops-guide
and replace it with nova command-line client commands.

Change-Id: Ibb3f0be68ccd165ce7a8ad7746fbd20b45f0ff6a
Partial-Bug: #1517322
Co-Authored-By: daz <dazzachan@yahoo.com.au>
This commit is contained in:
SaiKiran 2015-12-16 12:52:11 +05:30 committed by Darren Chan
parent 32c07afa22
commit 875d979d0d
6 changed files with 60 additions and 64 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/openstack-ops/app_crypt.xml
View File

@ -368,9 +368,8 @@
again in a title.</para> again in a title.</para>
<para>This past Valentine's Day, I received an alert that a <para>This past Valentine's Day, I received an alert that a
compute node was no longer available in the cloud&mdash;meaning, compute node was no longer available in the cloud&mdash;meaning,
<screen><prompt>$</prompt><userinput>nova-manage service list</userinput></screen> <screen><prompt>$</prompt><userinput>nova service-list</userinput></screen>
showed this particular node with a status of showed this particular node in down state.</para>
<code>XXX</code>.</para>
<para>I logged into the cloud controller and was able to both <para>I logged into the cloud controller and was able to both
<command>ping</command> and SSH into the problematic compute node which <command>ping</command> and SSH into the problematic compute node which
seemed very odd. Usually if I receive this type of alert, seemed very odd. Usually if I receive this type of alert,

4
doc/openstack-ops/ch_arch_scaling.xml
View File

@ -584,10 +584,6 @@
<listitem> <listitem>
<para>euca-describe-availability-zones verbose</para> <para>euca-describe-availability-zones verbose</para>
</listitem> </listitem>
<listitem>
<para><literal>nova-manage</literal> service list</para>
</listitem>
</itemizedlist>The internal availability zone is hidden in </itemizedlist>The internal availability zone is hidden in
euca-describe-availability_zones (nonverbose).</para> euca-describe-availability_zones (nonverbose).</para>

51
doc/openstack-ops/ch_ops_lay_of_land.xml
View File

@ -163,10 +163,6 @@
</indexterm> separately:</para> </indexterm> separately:</para>
<itemizedlist role="compact"> <itemizedlist role="compact">
<listitem>
<para><literal>nova-manage</literal></para>
</listitem>
<listitem> <listitem>
<para><literal>glance-manage</literal></para> <para><literal>glance-manage</literal></para>
</listitem> </listitem>
@ -464,28 +460,31 @@ http://203.0.113.10:8774/v2/98333aba48e756fa8f629c83a818ad57/servers | jq .</pro
<para>First, you can discover what servers belong to your OpenStack <para>First, you can discover what servers belong to your OpenStack
cloud by running:</para> cloud by running:</para>
<programlisting><?db-font-size 60%?><prompt>#</prompt> nova-manage service list | sort</programlisting> <programlisting><?db-font-size 60%?><prompt>#</prompt> nova service-list</programlisting>
<para>The output looks like the following:</para> <para>The output looks like the following:</para>
<programlisting><?db-font-size 60%?>Binary Host Zone Status State Updated_At <programlisting><?db-font-size 60%?>
nova-cert cloud.example.com nova enabled :-) 2013-02-25 19:32:38 +----+------------------+-------------------+------+---------+-------+----------------------------+-----------------+
nova-compute c01.example.com nova enabled :-) 2013-02-25 19:32:35 | Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
nova-compute c02.example.com nova enabled :-) 2013-02-25 19:32:32 +----+------------------+-------------------+------+---------+-------+----------------------------+-----------------+
nova-compute c03.example.com nova enabled :-) 2013-02-25 19:32:36 | 1 | nova-cert | cloud.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-compute c04.example.com nova enabled :-) 2013-02-25 19:32:32 | 2 | nova-compute | c01.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-compute c05.example.com nova enabled :-) 2013-02-25 19:32:41 | 3 | nova-compute | c01.example.com. | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-conductor cloud.example.com nova enabled :-) 2013-02-25 19:32:40 | 4 | nova-compute | c01.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-consoleauth cloud.example.com nova enabled :-) 2013-02-25 19:32:36 | 5 | nova-compute | c01.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-network cloud.example.com nova enabled :-) 2013-02-25 19:32:32 | 6 | nova-compute | c01.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-scheduler cloud.example.com nova enabled :-) 2013-02-25 19:32:33</programlisting> | 7 | nova-conductor | cloud.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
| 8 | nova-cert | cloud.example.com | nova | enabled | up | 2016-01-05T17:20:42.000000 | - |
| 9 | nova-scheduler | cloud.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
| 10 | nova-consoleauth | cloud.example.com | nova | enabled | up | 2016-01-05T17:20:35.000000 | - |
+----+------------------+-------------------+------+---------+-------+----------------------------+-----------------+
</programlisting>
<para>The output shows that there are five compute nodes and one cloud <para>The output shows that there are five compute nodes and one cloud
controller. You see a smiley face, such as <code>:-)</code>, which controller. You can see all the services are in up state, which
indicates that the services are up and running. If a service is no indicates that the services are up and running. If a service is no
longer available, the <code>:-)</code> symbol changes to longer available, then service state changes to down state. This is an indication
<code>XXX</code>. This is an indication that you should troubleshoot why that you should troubleshoot why the service is down.</para>
the service is down.</para>
<para>If you are using cinder, run the following command to see a <para>If you are using cinder, run the following command to see a
similar listing:</para> similar listing:</para>
@ -542,8 +541,8 @@ cloud.example.com nova</programlisting>
network traffic segregation.</para> network traffic segregation.</para>
<para>You can find the version of the Compute installation by using the <para>You can find the version of the Compute installation by using the
<literal>nova-manage</literal> <phrase <literal>nova</literal> <phrase
role="keep-together">command</phrase>: <screen><prompt>#</prompt> <userinput>nova-manage version</userinput></screen></para> role="keep-together">client command</phrase>: <screen><prompt>#</prompt> <userinput>nova version-list</userinput></screen></para>
</section> </section>
<section xml:id="diagnose-compute"> <section xml:id="diagnose-compute">
@ -634,10 +633,10 @@ cloud.example.com nova</programlisting>
| 8283efb2-e53d-46e1-a6bd-bb2bdef9cb9a | test02 | 10.1.1.0/24 | | 8283efb2-e53d-46e1-a6bd-bb2bdef9cb9a | test02 | 10.1.1.0/24 |
+--------------------------------------+--------+--------------+</computeroutput></screen></para> +--------------------------------------+--------+--------------+</computeroutput></screen></para>
<para>The <literal>nova-manage</literal> tool can provide some additional <para>The <literal>nova</literal> command-line client can provide some additional
details:</para> details:</para>
<screen><prompt>#</prompt> <userinput>nova-manage network list</userinput> <screen><prompt>#</prompt> <userinput>nova network-list</userinput>
<computeroutput>id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid&#160; <computeroutput>id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid&#160;
1 10.1.0.0/24 None 10.1.0.3 None None 300 2725bbd beacb3f2 1 10.1.0.0/24 None 10.1.0.3 None None 300 2725bbd beacb3f2
2 10.1.1.0/24 None 10.1.1.3 None None 301 none d0b1a796</computeroutput></screen> 2 10.1.1.0/24 None 10.1.1.3 None None 301 none d0b1a796</computeroutput></screen>
@ -651,7 +650,7 @@ cloud.example.com nova</programlisting>
<para>To find out whether any floating IPs are available in your cloud, <para>To find out whether any floating IPs are available in your cloud,
run:</para> run:</para>
<programlisting><?db-font-size 60%?><prompt>#</prompt> nova-manage floating list</programlisting> <programlisting><?db-font-size 60%?><prompt>#</prompt> nova floating-ip-list</programlisting>
<programlisting><?db-font-size 55%?>2725bb...59f43f 1.2.3.4 None nova vlan20 <programlisting><?db-font-size 55%?>2725bb...59f43f 1.2.3.4 None nova vlan20
None 1.2.3.5 48a415...b010ff nova vlan20</programlisting> None 1.2.3.5 48a415...b010ff nova vlan20</programlisting>

4
doc/ops-guide/source/app_crypt.rst
View File

@ -341,9 +341,9 @@ no longer available in the cloud—meaning,
.. code-block:: console .. code-block:: console
$ nova-manage service list $ nova service-list
showed this particular node with a status of ``XXX``. showed this particular node in a down state.
I logged into the cloud controller and was able to both ``ping`` and SSH I logged into the cloud controller and was able to both ``ping`` and SSH
into the problematic compute node which seemed very odd. Usually if I into the problematic compute node which seemed very odd. Usually if I

16
doc/ops-guide/source/arch_scaling.rst
View File

@ -339,22 +339,22 @@ change all flavor types relating to them.
When you run any of the following operations, the services appear in When you run any of the following operations, the services appear in
their own internal availability zone their own internal availability zone
(CONF.internal\_service\_availability\_zone): (CONF.internal_service_availability_zone):
- nova host-list (os-hosts) - :command:`nova host-list` (os-hosts)
- euca-describe-availability-zones verbose - :command:`euca-describe-availability-zones verbose`
- ``nova-manage`` service list - :command:`nova service-list`
The internal availability zone is hidden in The internal availability zone is hidden in
euca-describe-availability\_zones (nonverbose). euca-describe-availability_zones (nonverbose).
CONF.node\_availability\_zone has been renamed to CONF.node_availability_zone has been renamed to
CONF.default\_availability\_zone and is used only by the CONF.default_availability_zone and is used only by the
``nova-api`` and ``nova-scheduler`` services. ``nova-api`` and ``nova-scheduler`` services.
CONF.node\_availability\_zone still works but is deprecated. CONF.node_availability_zone still works but is deprecated.
Scalable Hardware Scalable Hardware
~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~

44
doc/ops-guide/source/ops_lay_of_the_land.rst
View File

@ -88,7 +88,6 @@ installed with the project's services on the cloud controller and do not
need to be installed\*-manage command-line toolscommand-line tools need to be installed\*-manage command-line toolscommand-line tools
administrative separately: administrative separately:
* :command:`nova-manage`
* :command:`glance-manage` * :command:`glance-manage`
* :command:`keystone-manage` * :command:`keystone-manage`
* :command:`cinder-manage` * :command:`cinder-manage`
@ -300,28 +299,31 @@ running:
.. code-block:: console .. code-block:: console
# nova-manage service list | sort # nova service-list
The output looks like the following: The output looks like the following:
.. code-block:: console .. code-block:: console
Binary Host Zone Status State Updated_At +----+------------------+-------------------+------+---------+-------+----------------------------+-----------------+
nova-cert cloud.example.com nova enabled :-) 2013-02-25 19:32:38 | Id | Binary | Host | Zone | Status | State | Updated_at | Disabled Reason |
nova-compute c01.example.com nova enabled :-) 2013-02-25 19:32:35 +----+------------------+-------------------+------+---------+-------+----------------------------+-----------------+
nova-compute c02.example.com nova enabled :-) 2013-02-25 19:32:32 | 1 | nova-cert | cloud.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-compute c03.example.com nova enabled :-) 2013-02-25 19:32:36 | 2 | nova-compute | c01.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-compute c04.example.com nova enabled :-) 2013-02-25 19:32:32 | 3 | nova-compute | c01.example.com. | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-compute c05.example.com nova enabled :-) 2013-02-25 19:32:41 | 4 | nova-compute | c01.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-conductor cloud.example.com nova enabled :-) 2013-02-25 19:32:40 | 5 | nova-compute | c01.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-consoleauth cloud.example.com nova enabled :-) 2013-02-25 19:32:36 | 6 | nova-compute | c01.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-network cloud.example.com nova enabled :-) 2013-02-25 19:32:32 | 7 | nova-conductor | cloud.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
nova-scheduler cloud.example.com nova enabled :-) 2013-02-25 19:32:33 | 8 | nova-cert | cloud.example.com | nova | enabled | up | 2016-01-05T17:20:42.000000 | - |
| 9 | nova-scheduler | cloud.example.com | nova | enabled | up | 2016-01-05T17:20:38.000000 | - |
| 10 | nova-consoleauth | cloud.example.com | nova | enabled | up | 2016-01-05T17:20:35.000000 | - |
+----+------------------+-------------------+------+---------+-------+----------------------------+-----------------+
The output shows that there are five compute nodes and one cloud The output shows that there are five compute nodes and one cloud
controller. You see a smiley face, such as ``:-)``, which indicates that controller. You see all the services in the up state, which indicates that
the services are up and running. If a service is no longer available, the services are up and running. If a service is in a down state, it is
the ``:-)`` symbol changes to ``XXX``. This is an indication that you no longer available. This is an indication that you
should troubleshoot why the service is down. should troubleshoot why the service is down.
If you are using cinder, run the following command to see a similar If you are using cinder, run the following command to see a similar
@ -373,11 +375,11 @@ be done for different reasons, such as endpoint privacy or network
traffic segregation. traffic segregation.
You can find the version of the Compute installation by using the You can find the version of the Compute installation by using the
:command:`nova-manage` command: nova client command:
.. code-block:: console .. code-block:: console
# nova-manage version # nova version-list
Diagnose Your Compute Nodes Diagnose Your Compute Nodes
--------------------------- ---------------------------
@ -453,11 +455,11 @@ the :command:`nova` command-line client to get the IP ranges:
| 8283efb2-e53d-46e1-a6bd-bb2bdef9cb9a | test02 | 10.1.1.0/24 | | 8283efb2-e53d-46e1-a6bd-bb2bdef9cb9a | test02 | 10.1.1.0/24 |
+--------------------------------------+--------+--------------+ +--------------------------------------+--------+--------------+
The :command:`nova-manage` tool can provide some additional details: The nova command-line client can provide some additional details:
.. code-block:: console .. code-block:: console
# nova-manage network list # nova network-list
id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid id IPv4 IPv6 start address DNS1 DNS2 VlanID project uuid
1 10.1.0.0/24 None 10.1.0.3 None None 300 2725bbd beacb3f2 1 10.1.0.0/24 None 10.1.0.3 None None 300 2725bbd beacb3f2
2 10.1.1.0/24 None 10.1.1.3 None None 301 none d0b1a796 2 10.1.1.0/24 None 10.1.1.3 None None 301 none d0b1a796
@ -472,7 +474,7 @@ To find out whether any floating IPs are available in your cloud, run:
.. code-block:: console .. code-block:: console
# nova-manage floating list # nova floating-ip-list
2725bb...59f43f 1.2.3.4 None nova vlan20 2725bb...59f43f 1.2.3.4 None nova vlan20
None 1.2.3.5 48a415...b010ff nova vlan20 None 1.2.3.5 48a415...b010ff nova vlan20