openstack/openstack-manuals
Code Issues Proposed changes

Use the openstack command to replace the glance

Browse Source 
Change-Id: I2fb726c03af85b6b5a247bf182ab9e539a5d5506
Implements: blueprint use-openstack-command
This commit is contained in:
caoyuan 2016-12-01 00:45:44 +08:00
parent 75b81a175e
commit 5431442b51
5 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/admin-guide/source/compute-images-instances.rst
View File

@ -453,7 +453,7 @@ be set to ``uefi`` when the image is created. For example:
.. code-block:: console
$ glance image-create --container-format bare --disk-format qcow2 \
$ openstack image create --container-format bare --disk-format qcow2 \
--property hw_firmware_type=uefi --file /tmp/cloud-uefi.qcow --name uefi
After that, you can launch instances from this UEFI image.

4
doc/cli-reference/source/glance-property-keys.rst
View File

@ -4,12 +4,12 @@ Image service property keys
The following keys, together with the components to which they are specific,
can be used with the property option for both the
:command:`glance image-update` and :command:`glance image-create` commands.
:command:`openstack image set` and :command:`openstack image create` commands.
For example:
.. code-block:: console
$ glance image-update IMG-UUID --property architecture=x86_64
$ openstack image set IMG-UUID --property architecture=x86_64
.. note::

2
doc/common/cli-manage-images.rst
View File

@ -203,7 +203,7 @@ model:
When you use OpenStack with VMware vCenter Server, you need to specify
the ``vmware_disktype`` and ``vmware_adaptertype`` properties with
:command:`glance image-create`.
:command:`openstack image create`.
Also, we recommend that you set the ``hypervisor_type="vmware"`` property.
For more information, see `Images with VMware vSphere
<http://docs.openstack.org/newton/config-reference/compute/hypervisor-vmware.html#images-with-vmware-vsphere>`_

4
doc/config-reference/source/compute/hypervisor-hyper-v.rst
View File

@ -385,11 +385,11 @@ on Hyper-V can be found here:
http://technet.microsoft.com/en-us/library/cc772480.aspx
Once you have successfully created a virtual machine, you can then upload
the image to glance using the native glance-client:
the image to glance using the openstack-client:
.. code-block:: powershell
PS C:\> glance image-create --name "VM_IMAGE_NAME" --is-public False
PS C:\> openstack image create --name "VM_IMAGE_NAME" --public \
--container-format bare --disk-format vhd
.. note::

6
doc/ops-guide/source/ops-monitoring.rst
View File

@ -230,9 +230,9 @@ this by doing a quick image upload:
. /root/openrc
wget http://download.cirros-cloud.net/0.3.4/cirros-0.3.4-x86_64-disk.img
glance image-create --name='cirros image' --is-public=true
--container-format=bare --disk-format=qcow2 < cirros-0.3.4-x8
6_64-disk.img
openstack image create --name='cirros image' --public \
--container-format=bare --disk-format=qcow2 \
--file cirros-0.3.4-x86_64-disk.img
By taking this script and rolling it into an alert for your monitoring
system (such as Nagios), you now have an automated way of ensuring that