openstack
/
openstack-manuals
Code Issues Proposed changes

[glance] Added metadata definitions concepts 

Change-Id: Ifbfc72ec45c453ef345dfd2241764ba03f28d3d7
Closes-Bug: #1378237
This commit is contained in:
njirap 2016-01-14 05:34:40 +03:00 committed by KATO Tomoyuki
parent e5e6bbd137
commit f1c70b647c
2 changed files with 67 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
doc/common-rst/get_started_image_service.rst
View File

@ -4,7 +4,7 @@ OpenStack Image service
The OpenStack Image service is central to Infrastructure-as-a-Service
(IaaS) as shown in :ref:`get_started_conceptual_architecture`. It accepts API
requests for disk or server images, and image metadata from end users or
requests for disk or server images, and metadata definitions from end users or
OpenStack Compute components. It also supports the storage of disk or server
images on various repository types, including OpenStack Object Storage.
@ -35,3 +35,11 @@ Storage repository for image files
Various repository types are supported including normal file
systems, Object Storage, RADOS block devices, HTTP, and Amazon S3.
Note that some repositories will only support read-only usage.
Metadata definition service
A common API for vendors, admins, services, and users to meaningfully
define their own custom metadata. This metadata can be used on
different types of resources like images, artifacts, volumes,
flavors, and aggregates. A definition includes the new property's key,
description, constraints, and the resource types which it can be
associated with.

58
doc/image-guide/source/image-metadata.rst
View File

@ -88,3 +88,61 @@ All associated properties for an image can be displayed using the
Amend ``glance_core_properties`` in the ``/etc/cinder/cinder.conf``
file on all controller nodes to match the core properties you have
set in the Image service.
Metadata definition service
~~~~~~~~~~~~~~~~~~~~~~~~~~~
With this service you can define:
Namespace
* Contains metadata definitons.
* Specifies the access controls for everything defined in the namespace.
These access controls determine who can define and use the definitions
in the namespace.
* Associates the definitions with different types of resources.
Property
A single property and its primitive constraints. Each property can only
be a primitive type. For example, string, integer, number, boolean, or array.
Object
Describes a group of one to many properties and their primitive
constraints. Each property in the group can only be a primitive type. For
example, string, integer, number, boolean, or array.
The object may optionally define required properties under the semantic
understanding that if you use the object, you should provide all required
properties.
Resource type association
Specifies the relationship between resource types and the namespaces
that are applicable to them. This information can be used to drive UI
and CLI views. For example, the same namespace of objects, properties,
and tags may be used for images, snapshots, volumes, and flavors.
Or a namespace may only apply to images.
The Image service has predefined namespaces for the metadata definitions
catalog. To load files from this directory into the database:
.. code-block:: console
$ glance-manage db_load_metadefs
To unload the files from the database:
.. code-block:: console
$ glance-manage db_unload_metadefs
To export the definitions in JSON format:
.. code-block:: console
$ glance-manage db_export_metadefs
.. note::
By default, files are loaded from and exported to the Image service's
``/etc/metadefs`` directory.