diff --git a/doc/admin-guide/source/compute-images-instances.rst b/doc/admin-guide/source/compute-images-instances.rst index 310db438a2..296fcae38e 100644 --- a/doc/admin-guide/source/compute-images-instances.rst +++ b/doc/admin-guide/source/compute-images-instances.rst @@ -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. diff --git a/doc/cli-reference/source/glance-property-keys.rst b/doc/cli-reference/source/glance-property-keys.rst index 44e93aa8a0..52e376425b 100644 --- a/doc/cli-reference/source/glance-property-keys.rst +++ b/doc/cli-reference/source/glance-property-keys.rst @@ -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:: diff --git a/doc/common/cli-manage-images.rst b/doc/common/cli-manage-images.rst index bc90ff4e21..5159968617 100644 --- a/doc/common/cli-manage-images.rst +++ b/doc/common/cli-manage-images.rst @@ -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 `_ diff --git a/doc/config-reference/source/compute/hypervisor-hyper-v.rst b/doc/config-reference/source/compute/hypervisor-hyper-v.rst index ee0c811767..9c4da92861 100644 --- a/doc/config-reference/source/compute/hypervisor-hyper-v.rst +++ b/doc/config-reference/source/compute/hypervisor-hyper-v.rst @@ -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:: diff --git a/doc/ops-guide/source/ops-monitoring.rst b/doc/ops-guide/source/ops-monitoring.rst index f9b05dc97e..f414f188ca 100644 --- a/doc/ops-guide/source/ops-monitoring.rst +++ b/doc/ops-guide/source/ops-monitoring.rst @@ -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