openstack/openstack-manuals
Code Issues Proposed changes

[admin-guide] Replace "nova boot" with "openstack server create"

Browse Source 
Change-Id: I9d7d44e98487a230103b532ee55283a49d93229f
Implements: blueprint use-openstack-command
This commit is contained in:
chenxing 2016-12-02 05:55:21 +00:00 committed by chen.xing
parent 89cbcef840
commit 058326648e
3 changed files with 9 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/admin-guide/source/compute-networking-nova.rst
View File

@ -391,7 +391,7 @@ retrieve the metadata, make a GET request to
Instances also retrieve user data (passed as the ``user_data`` parameter Instances also retrieve user data (passed as the ``user_data`` parameter
in the API call or by the :option:`--user_data` flag in the in the API call or by the :option:`--user_data` flag in the
:command:`nova boot` command) through the metadata service, by making a :command:`openstack server create` command) through the metadata service, by making a
GET request to ``http://169.254.169.254/openstack/2012-08-10/user_data``: GET request to ``http://169.254.169.254/openstack/2012-08-10/user_data``:
.. code-block:: console .. code-block:: console
@ -739,7 +739,8 @@ Save the file, and restart ``nova-network``
.. note:: .. note::
If this option is enabled, but all floating IP addresses have If this option is enabled, but all floating IP addresses have
already been allocated, the :command:`nova boot` command will fail. already been allocated, the :command:`openstack server create`
command will fail.
Remove a network from a project Remove a network from a project
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
@ -834,11 +835,12 @@ Edit the ``/etc/network/interfaces`` file:
If the Virtual Network Service Neutron is installed, you can specify the If the Virtual Network Service Neutron is installed, you can specify the
networks to attach to the interfaces by using the :option:`--nic` flag with networks to attach to the interfaces by using the :option:`--nic` flag with
the :command:`nova boot` command: the :command:`openstack server create` command:
.. code-block:: console .. code-block:: console
$ nova boot --image ed8b2a37-5535-4a5f-a615-443513036d71 --flavor 1 --nic net-id=NETWORK1_ID --nic net-id=NETWORK2_ID test-vm1 $ openstack server create --image ed8b2a37-5535-4a5f-a615-443513036d71 \
--flavor 1 --nic net-id=NETWORK1_ID --nic net-id=NETWORK2_ID test-vm1
Troubleshooting Networking Troubleshooting Networking
~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~

3
doc/admin-guide/source/compute-security.rst
View File

@ -134,7 +134,8 @@ settings:
.. code-block:: console .. code-block:: console
$ nova boot --flavor m1.tiny --key-name myKeypairName --image myImageID newInstanceName $ openstack server create --flavor m1.tiny \
--key-name myKeypairName --image myImageID newInstanceName
.. figure:: figures/OpenStackTrustedComputePool2.png .. figure:: figures/OpenStackTrustedComputePool2.png

2
doc/admin-guide/source/telemetry-measurements.rst
View File

@ -53,7 +53,7 @@ modified boot command look like the following:
.. code-block:: console .. code-block:: console
$ nova boot --meta metering.custom_metadata=a_value my_vm $ openstack server create --property metering.custom_metadata=a_value my_vm
The other option is to set the ``reserved_metadata_keys`` to the list of The other option is to set the ``reserved_metadata_keys`` to the list of
metadata keys that you would like to be included in metadata keys that you would like to be included in