openstack
/
glance
Code Issues Proposed changes

Update Interop doc 

The commit replaces DefCore committee (a former name) by
Interop Working Group (the current name) and updates a few
more old interop references.

Change-Id: I09c02f3adc2ba5acb2c325e462bc6e54dd23d0fb
This commit is contained in:
Martin Kopec 2021-11-08 10:47:05 +00:00
parent a693e066b3
commit fd36d6450e
2 changed files with 10 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/source/glossary.rst
View File

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

15
doc/source/user/glanceapi.rst
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
community to define the new functionality and provide its reference
implementation. Further, Glance falls under the "designated sections" provision
of the OpenStack DefCore Guidelines, which basically means that in order to
qualify as "OpenStack", a cloud exposing an OpenStack Images API must include
the Glance Images API implementation code. Thus, although conceptually
independent, the OpenStack Images APIs are intimately associated with Glance.
of the OpenStack Interop (formerly known as DefCore) Guidelines, which
basically means that in order to qualify as "OpenStack", a cloud exposing an
OpenStack Images API must include the Glance Images API implementation code.
Thus, although conceptually independent, the OpenStack Images APIs are
intimately associated with Glance.
**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>`_
* `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
-----------------------------------------------------