Merge "Update Interop doc"

This commit is contained in:
Zuul 2022-01-18 18:45:54 +00:00 committed by Gerrit Code Review
commit 909597c434
2 changed files with 10 additions and 9 deletions

View File

@ -912,7 +912,7 @@ C
core service core service
An official OpenStack service defined as core by An official OpenStack service defined as core by
DefCore Committee. Currently, consists of Interop Working Group. Currently, consists of
Block Storage service (cinder), Compute service (nova), Block Storage service (cinder), Compute service (nova),
Identity service (keystone), Image service (glance), Identity service (keystone), Image service (glance),
Networking service (neutron), and Object Storage service (swift). Networking service (neutron), and Object Storage service (swift).
@ -2762,7 +2762,7 @@ O
optional service optional service
An official OpenStack service defined as optional by An official OpenStack service defined as optional by
DefCore Committee. Currently, consists of Interop Working Group. Currently, consists of
Dashboard (horizon), Telemetry service (Telemetry), Dashboard (horizon), Telemetry service (Telemetry),
Orchestration service (heat), Database service (trove), Orchestration service (heat), Database service (trove),
Bare Metal service (ironic), and so on. Bare Metal service (ironic), and so on.

View File

@ -30,20 +30,21 @@ independent definition of a REST API. In practice, however, the only way
to participate in the evolution of the Images API is to work with the Glance to participate in the evolution of the Images API is to work with the Glance
community to define the new functionality and provide its reference community to define the new functionality and provide its reference
implementation. Further, Glance falls under the "designated sections" provision implementation. Further, Glance falls under the "designated sections" provision
of the OpenStack DefCore Guidelines, which basically means that in order to of the OpenStack Interop (formerly known as DefCore) Guidelines, which
qualify as "OpenStack", a cloud exposing an OpenStack Images API must include basically means that in order to qualify as "OpenStack", a cloud exposing an
the Glance Images API implementation code. Thus, although conceptually OpenStack Images API must include the Glance Images API implementation code.
independent, the OpenStack Images APIs are intimately associated with Glance. Thus, although conceptually independent, the OpenStack Images APIs are
intimately associated with Glance.
**References** **References**
* `Designated sections (definition) <https://github.com/openstack/interop/blob/master/doc/source/process/Lexicon.rst>`_ * `Designated sections (definition) <https://docs.opendev.org/openinfra/interop/latest/process/Lexicon.html>`_
* `2014-04-02 DefCore Designated Sections Guidelines <https://governance.openstack.org/resolutions/20140402-defcore-designated-sections-guidelines.html>`_ * `2014-04-02 DefCore Designated Sections Guidelines <https://governance.openstack.org/resolutions/20140402-defcore-designated-sections-guidelines.html>`_
* `OpenStack Core Definition <https://github.com/openstack/interop/blob/master/doc/source/process/CoreDefinition.rst>`_ * `OpenStack Core Definition <https://docs.opendev.org/openinfra/interop/latest/process/CoreDefinition.html>`_
* `DefCore Guidelines Repository <https://github.com/openstack/interop>`_ * `Interop Guidelines Repository <https://opendev.org/openinfra/interop>`_
Glance and the Images APIs: Past, Present, and Future Glance and the Images APIs: Past, Present, and Future
----------------------------------------------------- -----------------------------------------------------