Change 'Image Service' to 'Image service'
Follow the Documentation Conventions: https://wiki.openstack.org/wiki/Documentation/Conventions Change-Id: I595d7154efa33df41aa532a5dfea59a1abcaa36f
This commit is contained in:
@@ -164,7 +164,7 @@ The following Launchpad Bugs areas are available:
|
||||
- `Bugs: OpenStack Identity
|
||||
(keystone) <https://bugs.launchpad.net/keystone>`__
|
||||
|
||||
- `Bugs: OpenStack Image Service
|
||||
- `Bugs: OpenStack Image service
|
||||
(glance) <https://bugs.launchpad.net/glance>`__
|
||||
|
||||
- `Bugs: OpenStack Networking
|
||||
|
@@ -146,7 +146,7 @@ for each client. The following values are valid:
|
||||
|
||||
- ``cinder`` - Block Storage API and extensions
|
||||
|
||||
- ``glance`` - Image Service API
|
||||
- ``glance`` - Image service API
|
||||
|
||||
- ``heat`` - Orchestration API
|
||||
|
||||
|
@@ -6,7 +6,7 @@ The cloud operator assigns roles to users. Roles determine who can
|
||||
upload and manage images. The operator might restrict image upload and
|
||||
management to only cloud administrators or operators.
|
||||
|
||||
You can upload images through the ``glance`` client or the Image Service
|
||||
You can upload images through the ``glance`` client or the Image service
|
||||
API. Besides, you can use the ``nova`` client for the image management.
|
||||
The latter provides mechanisms to list and delete images, set and delete
|
||||
image metadata, and create images of a running instance of snapshot and
|
||||
@@ -102,7 +102,7 @@ list, as follows::
|
||||
"mountpoint": "/var/lib/glance/images/"
|
||||
}]
|
||||
|
||||
After you restart the Image Service, you can use the following syntax to view the image's location information::
|
||||
After you restart the Image service, you can use the following syntax to view the image's location information::
|
||||
|
||||
$ glance --os-image-api-version 2 image-show imageID
|
||||
|
||||
@@ -127,7 +127,7 @@ To update an image by name or ID, use ``glance image-update``:
|
||||
|
||||
The following table lists the optional arguments that you can use with
|
||||
the ``create`` and ``update`` commands to modify image properties. For
|
||||
more information, refer to Image Service chapter in the `OpenStack
|
||||
more information, refer to Image service chapter in the `OpenStack
|
||||
Command-Line Interface
|
||||
Reference <http://docs.openstack.org/cli-reference/content/index.html>`__.
|
||||
|
||||
@@ -256,7 +256,7 @@ in the following tables.
|
||||
Troubleshoot image creation
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
If you encounter problems in creating an image in Image Service or
|
||||
If you encounter problems in creating an image in Image service or
|
||||
Compute, the following information may help you troubleshoot the
|
||||
creation process.
|
||||
|
||||
|
@@ -46,7 +46,7 @@ service with its package name and description.
|
||||
| | | |endpoints, and |
|
||||
| | | |credentials. |
|
||||
+----------------+----------+-----------------------+------------------------+
|
||||
|Image Service |glance |python-glanceclient |Create and manage |
|
||||
|Image service |glance |python-glanceclient |Create and manage |
|
||||
| | | |images. |
|
||||
+----------------+----------+-----------------------+------------------------+
|
||||
|Networking |neutron |python-neutronclient |Configure networks for |
|
||||
|
@@ -65,7 +65,7 @@ Before you can launch an instance, gather the following parameters:
|
||||
After you gather the parameters that you need to launch an instance, you
|
||||
can launch it from an image_ or a :ref:`volume`. You can launch an instance directly
|
||||
from one of the available OpenStack images or from an image that you have
|
||||
copied to a persistent volume. The OpenStack Image Service provides a
|
||||
copied to a persistent volume. The OpenStack Image service provides a
|
||||
pool of images that are accessible to members of different projects.
|
||||
|
||||
Gather parameters to launch an instance
|
||||
|
@@ -4,7 +4,7 @@ Launch and manage instances
|
||||
Instances are virtual machines that run inside the cloud. You can launch
|
||||
an instance from the following sources:
|
||||
|
||||
- Images uploaded to the OpenStack Image Service.
|
||||
- Images uploaded to the OpenStack Image service.
|
||||
|
||||
- Image that you have copied to a persistent volume. The instance
|
||||
launches from the volume, which is provided by the ``cinder-volume``
|
||||
@@ -33,7 +33,7 @@ copy of the image on the compute node where the instance starts.
|
||||
#. Log in to the dashboard, choose a project, and click :guilabel:`Images`.
|
||||
|
||||
The dashboard shows the images that have been uploaded to OpenStack
|
||||
Image Service and are available for this project.
|
||||
Image service and are available for this project.
|
||||
|
||||
For details on creating images, see `Creating images
|
||||
manually <http://docs.openstack.org/image-guide/content/ch_creating_images_manually.html>`__
|
||||
|
@@ -2,10 +2,10 @@
|
||||
:linenothreshold: 5
|
||||
|
||||
==============================================
|
||||
Authenticate against an Image Service endpoint
|
||||
Authenticate against an Image service endpoint
|
||||
==============================================
|
||||
|
||||
To authenticate against an Image Service endpoint, instantiate a
|
||||
To authenticate against an Image service endpoint, instantiate a
|
||||
`glanceclient.v2.client.Client <http://docs.openstack.org/developer/python-glanceclient/api/glanceclient.v2.client.html#glanceclient.v2.client.Client>`__ object:
|
||||
|
||||
.. code-block:: python
|
||||
|
@@ -102,7 +102,7 @@ To retrieve an image object from its ID, call the
|
||||
Get image by name
|
||||
~~~~~~~~~~~~~~~~~
|
||||
|
||||
The Image Service Python bindings do not support the retrieval of an
|
||||
The Image service Python bindings do not support the retrieval of an
|
||||
image object by name. However, the Compute Python bindings enable you to
|
||||
get an image object by name. To get an image object by name, call the
|
||||
``novaclient.v1\_1.images.ImageManager.find`` method:
|
||||
|
Reference in New Issue
Block a user