4fa9872510
When using the glance v2 API the glance-registry service is optional, and the intention is to remove the glance-registry service in the S cycle. The glance v1 API is scheduled to be removed in Queens. This patch therefore disables the v1 API by default to give us as much time as possible to identify the impact of that and to get the issues resolved before it is removed from the code-base. The patch also cleans up the glance-registry init files to handle the transition in an existing environment. Tests are added to validate that enabling the v1 API still works, and enabling the v2 registry still works. Change-Id: I4c27aa0ca5b649e4fa76cfd0f326d80f50074db1
23 lines
946 B
YAML
23 lines
946 B
YAML
---
|
|
upgrade:
|
|
- |
|
|
The glance v1 API is now disabled by default as the API is scheduled
|
|
to be removed in Queens.
|
|
- |
|
|
The glance registry service is now disabled by default as it is not
|
|
required for the v2 API and is scheduled to be removed in the future.
|
|
The service can be enabled by setting ``glance_enable_v2_registry``
|
|
to ``True``.
|
|
deprecations:
|
|
- |
|
|
The ``glance_enable_v1_registry`` variable has been removed. When using
|
|
the glance v1 API the registry service is required, so having a variable
|
|
to disable it makes little sense. The service is now enabled/disabled
|
|
for the v1 API using the ``glance_enable_v1_api`` variable.
|
|
fixes:
|
|
- |
|
|
When the ``glance_enable_v2_registry`` variable is set to ``True`` the
|
|
corresponding ``data_api`` setting is now correctly set. Previously it
|
|
was not set and therefore the API service was not correctly informed
|
|
that the registry was operating.
|