openstack
/
glance
Code Issues Proposed changes

Train final release notes 

Change-Id: Id1034c76a890d8f6a4d1f028ce01c3bc78a0c7a3
This commit is contained in:
Erno Kuvaja 2019-10-10 14:56:37 +01:00
parent d8e59b0d15
commit f87464e022
2 changed files with 41 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
releasenotes/notes/rethinking-filesystem-access-120bc46064b3d40a.yaml
View File

@ -1,19 +1,17 @@
---
features:
- |
With the introduction of the Glance multiple stores feature, introduced
on an experimental basis in Rocky and now established as a full feature
in the Train release, it is now possible for Glance to use backends
accessed via the glance_store library for the temporary storage of
data that previously required access to the local filesystem. Please
note the following:
It is now possible for Glance to use backends accessed via the
glance_store library for the temporary storage of data that previously
required access to the local filesystem. Please note the following:
* In this release, the use of stores (instead of local directories) is
optional, but it will become mandatory for the 'U' release.
* In this release, the use of stores (instead of configuring the path
directly) is optional, but it will become mandatory for the 'U'
release.
* In this release, the stores used *must* be the filesystem store type.
Our goal is that in a future release, operators will be able to
configure a store of their choice for these functions. In Train,
configure a store type from other selected drivers as well. In Train,
however, each of these *must* be a filesystem store.
Please see the Upgrades section of this document and the "Multi Store

34
releasenotes/notes/train-final-e09f3fe40592a478.yaml Normal file
View File

@ -0,0 +1,34 @@
---
prelude: |
Train release includes multiple important milestones in Glance development
priorities.
* Stabilization of multi-store feature; from Train onwards multi-store
is considered stable feature in glance, glance_store and
python-glanceclient. The community encourages everyone to adopt this new
way of configuring backend stores at earliest convenience as the old
configuration options are deprecated for removal to ease the burden of
maintaining underlying code. Users are able to select the store they
want their images to be stored during import process.
* ``glance-cache-manage`` and precaching is back; during the cycle we
fixed issues that caused cache management being impossible. The
prefetcher code was moved into glance-api to break the dependency to
glance-registry and does not run under cron anymore.
* Documentation examples were changed from ``openstack`` commands back to
``glance``. This should help avoid the frustration of glance-community
maintaining different client than what is referred in examples.
'python-glanceclient' is and will be the reference implementation of
Images API and the team will implement all API changes to the relevant
client version of the cycle as well.
* This release also bumps the Images API CURRENT version to 2.9
fixes:
- |
* Bug 1808868_: Add SEV-related extra spec and image properties
* Bug 1802587_: Make location API compatible with multiple store
.. _1808868: https://code.launchpad.net/bugs/1808868
.. _1802587: https://code.launchpad.net/bugs/1802587