openstack/glance
Code Issues Proposed changes

Clarify language used in glanceapi future section

Browse Source 
As per the comments and agreement on
Iede37e61784b6a8a974ce0ae29ccfab510d8cc53 , this patch proposes the
concerned changes. The former patch was merged as the consensus on the
idea of the Images API future section was converged. This is merely a
simplification to the grammatical tone on the respective sections.

Change-Id: Iefbdeadb78b2a7b866495d4a8f3e7a84cee46fe2
This commit is contained in:
Nikhil Komawar 2016-05-10 17:42:21 -04:00
parent aab90f4727
commit f5c10879a0
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
doc/source/glanceapi.rst
View File

@ -25,12 +25,12 @@ developed alongside Glance, but is not considered part of the Glance project."
That's only partially true (or completely false, depending upon how strict you
are about these things). Conceptually, the OpenStack Images API is an
independent definition of a REST API. In practice, however, the only way
further to develop 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
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.
**References**
@ -55,9 +55,9 @@ Images v1 API
*************
The v1 API was originally designed as a service API for use by Nova and other
OpenStack services. Its current status is SUPPORTED. The Images v1 API is
closed to further development, and the Glance code implementing the v1 API
accepts only serious bugfixes.
OpenStack services. In the Kilo release, the v1.1 API was downgraded from
CURRENT to SUPPORTED. The Images v1 API is closed to further development, and
the Glance code implementing the v1 API accepts only serious bugfixes.
It's possible to deploy OpenStack without exposing the Images v1 API to end
users. The Compute v2 API contains image-related API calls allowing users to