summaryrefslogtreecommitdiff
path: root/releasenotes/notes
Commit message (Collapse)AuthorAgeFilesLines
* Merge "Support Cinder multiple stores"Zuul2020-08-251-0/+10
|\
| * Support Cinder multiple storeswhoami-rajat2020-08-241-0/+10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds support for configuring multiple cinder stores. The following changes are part of this patch: 1) location URL format: previously cinder://<volume-id>, the format is now changed to cinder://<store-name>/<volume-id> 2) Check for configured volume types: During initialization of service, all volume types configured in the cinder store(s) will be checked if they exist in deployment or not, the store with the wrong type will be disabled. if cinder store is configured using traditional/old way (i.e. using 'stores' config option) then this validation will not be performed. 3) Update legacy images: This change is partially depedent on the glance changes[1] which trigger updating the URL for legacy images and the cinder store checks the configured stores volume type against the existing image-volume's type and update it respectively. [1] https://review.opendev.org/#/c/742373/ Implements: blueprint multiple-cinder-backend-support Change-Id: I0ba36d1095886fd1d96926af37a3a65a178c004f
* | Handle sparse images in glance_storeVictor Coutellier2020-08-211-0/+15
|/ | | | | | | | | | | | | | | | Add new configuration option ``rbd_thin_provisioning`` and ``filesystem_thin_provisioning`` to rbd and filesystem store to enable or not sparse upload. A sparse file means that we do not actually write null byte sequences but only the data itself at a given offset, the "holes" which can appear will automatically be interpreted by the storage backend as null bytes, and do not really consume your storage. Change-Id: I129e30f490e3920e9093c2b793f89b70ce310a50 Co-Authored-By: Grégoire Unbekandt <gregoire.unbekandt@gmail.com> Partially Implements: blueprint handle-sparse-image
* Merge "Don't allow image creation with encrypted nfs volumes"Zuul2020-06-261-0/+6
|\
| * Don't allow image creation with encrypted nfs volumesRajat Dhasmana2020-06-221-0/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | With change[1], we will enabled encrypted volume support for cinder nfs driver. Before enabling that, we require handling in cinder consuming projects (like glance_store) to not have unexpected behavior. This patch blocks image creation if the destination volume (in which the image will be written) is an encrypted nfs volume. [1] https://review.opendev.org/#/c/597148/ Closes-Bug: #1884482 Change-Id: I3b4c6782e561f22a7118624e26bf056cd6405a30
* | Release notes for Victoria Milestone 12.1.0Abhishek Kekane2020-06-221-0/+9
|/ | | | Change-Id: I8eadf775a17d9505ed5eafc54d1c4849de6f45f3
* Release note for 1.2.0Abhishek Kekane2020-03-301-0/+31
| | | | Change-Id: Id75209c172d881d90c85002bf6496cc1eef9c702
* Merge "Add S3 store support to glance_store"Zuul2020-03-271-0/+6
|\
| * Add S3 store support to glance_storeNaohiro Sameshima2020-03-261-0/+6
| | | | | | | | | | | | | | | | | | | | | | Revive the S3 driver that was supported up to Mitaka and add multiple store support to correspond with the features added to glance_store from Newton to U cycle. In addition, the use of the S3 SDK used by the Mitaka S3 driver has been deprecated, so this implementation will be changed to use the new version. Change-Id: I203134837319080ead96da69048baf90086d2117 Implements: blueprint re-support-s3-driver
* | Merge "Re-use swift_store_cacert for Keystone session"Zuul2020-03-261-0/+11
|\ \ | |/ |/|
| * Re-use swift_store_cacert for Keystone sessionPavlo Shchelokovskyy2020-01-141-0/+11
| | | | | | | | | | | | | | | | | | pass configured cacert for Swift to the keystoneauth's Session as well so that the swift endpoint can be resolved from the catalog when a custom CA bundle is used. Change-Id: I439f6b5af34c685f72c9b4933c7eb0c77cc92e14 Closes-Bug: #1820817
* | Drop python 2.7 support and testingGhanshyam Mann2020-01-221-0/+6
|/ | | | | | | | | | | | | | | OpenStack is dropping the py2.7 support in ussuri cycle. glance_store is ready with python 3 and ok to drop the python 2.7 support. Complete discussion & schedule can be found in - http://lists.openstack.org/pipermail/openstack-discuss/2019-October/010142.html - https://etherpad.openstack.org/p/drop-python2-support Ussuri Communtiy-wide goal - https://review.opendev.org/#/c/691178/ Change-Id: I6166a20610f77e0df7da75198e0c8273bb121d1f
* Release note for 1.0.1Abhishek Kekane2019-09-261-0/+15
| | | | Change-Id: Ib5a6891261be14ead6f358982d8181b075050188
* Release note and documentation for 1.0.0Brian Rosmaita2019-07-191-0/+48
| | | | Change-Id: Iac607e8ccd04f5a468b9ee09f10ea5800cf76480
* Deprecate Sheepdog driverBrian Rosmaita2019-07-191-0/+12
| | | | | | | | | | As there was no response to the ML announcement [0], proceed with deprecation of the Sheepdog driver, scheduled for removal in the 'U' cycle. [0] http://lists.openstack.org/pipermail/openstack-discuss/2019-May/006725.html Change-Id: Ie41b166e51e4d7b674f893c2b71d576e5a8b51a0
* Add 0.29.1 releasenotes0.29.1Erno Kuvaja2019-06-071-0/+17
| | | | Change-Id: Idbb1f8e7f4185d182c9f10ce6c7ea808a15f77c2
* Rethinking file system accessAbhishek Kekane2019-06-061-0/+9
| | | | | | | | | Made provision to load reserved_stores if it is specified in glance. Added keywrod argument to 'register_store_opts' and 'create_multi_stores' method. Change-Id: I965df1883639bfd5c900d2902884153d48988f6e Partial-Implements: blueprint rethinking-filesystem-access
* Merge "Add releasenote for option removal"Zuul2019-05-301-0/+6
|\
| * Add releasenote for option removalBrian Rosmaita2019-05-301-0/+6
| | | | | | | | | | | | | | Documents the removal of 'store_capabilities_update_min_interval' by change I1a6cfa45b5a37eacb4ba158b62fe619e1b1c9dff. Change-Id: Ia53034f5c1aff754dd500531f27b7c3705a17e19
* | Replace git.openstack.org URLs with opendev.org URLscaoyuan2019-05-052-7/+7
|/ | | | Change-Id: Ia0b66aac906b7920f246c4710ed06d63e11276d8
* Stein cycle Release Notes0.28.0Erno Kuvaja2019-02-281-0/+28
| | | | Change-Id: I1b234fb4ca9c8895e53d8063f72e3eb8e3b94efc
* Merge "Filesystem driver: add chunk size config option"Zuul2019-02-281-0/+5
|\
| * Filesystem driver: add chunk size config optionLucian Petrut2019-02-251-0/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | At the moment, the filesystem driver uses a hardcoded 64 KB chunk size, used when reading/writing image files. This can be extremely inefficient, especially when file shares are used. For this reason, this change will make it configurable. DocImpact Change-Id: I1559c03308d36ecf9305c7a72ad658ecd1f2dc76 Closes-Bug: #1792869
* | Update deprecation noticesBrian Rosmaita2018-12-201-0/+6
|/ | | | | | | Removal of 'stores' and 'default_store' has been postponed until Train; update the deprecation text and add a release note. Change-Id: Ib01be1746f9a1b414d6a9436032c34034a2e6f45
* Consider Cinder back-end as production readyErno Kuvaja2018-07-191-0/+9
| | | | | Closes-Bug: #1780764 Change-Id: I02153190d72bd861c509f61caad92c20a787f848
* Deprecate store_add_to_backend()Brian Rosmaita2018-07-181-0/+15
| | | | | | | | | A replacement, store_add_to_backend_with_multihash(), has been introduced in Rocky. The old function is kept in Rocky for backward compatability. This deprecation notice registers our intent to remove it in Stein. Change-Id: If09ae10ee160e3fbfafce94e4f3607994af63ec5
* Multihash Implementation for GlanceScott McClymont2018-07-181-0/+13
| | | | | | | | | | | | | | Adds the ability to compute a "multihash" (see the Glance spec for what this is exactly). To maintain backward compatability, a new store_add_to_backend_with_multihash function is added. Backward compatability for each store's add() method is achieved by a back_compat_add wrapper. Co-Authored-by: Scott McClymont <scott.mcclymont@verizonwireless.com> Co-Authored-by: Brian Rosmaita <rosmaita.fossdev@gmail.com> Change-Id: I063d0900b7dc7e0d94dfb685971eb9b17ed67c7b Partially-implements: blueprint multihash
* Add release notes for 0.25.0Erno Kuvaja2018-07-172-0/+26
| | | | Change-Id: I88ee7947d34512276ac5866bf1ada0666f2eaac9
* Deprecate store_capabilities_update_min_intervalBrian Rosmaita2018-06-201-0/+14
| | | | | | | Includes a release note. Change-Id: Ic25549ac022cf7fc93affc331f2379ea63bf6fb2 Implements: blueprint spec-lite-deprecate-update-min-interval
* process spelling errorchenjiao2018-01-231-1/+1
| | | | | | the word process is error Change-Id: I1afb9bc0c187b76c5b8b28f6819122eec328d53b
* Add Queens release notequeens-em0.23.0Brian Rosmaita2018-01-181-0/+52
| | | | Change-Id: Ib28982138d7c2cef98a667307a6a2a9fd64ab3cd
* Add release note for Pike.Brian Rosmaita2017-07-181-0/+45
| | | | Change-Id: I278fdb47e1643dae3ae8af71889105edf2f97dd1
* Merge "Raise exc when using multi-tenant and swift+config"0.19.0Jenkins2016-12-191-0/+9
|\
| * Raise exc when using multi-tenant and swift+configDharini Chandrasekar2016-12-161-0/+9
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When Swift multi-tenant store is used along with the scheme ``swift+config`` (the scheme that identifies the need to use the swift config), a reference to use swift objects from the swift config file set using the option ``swift_store_config_file`` is made resulting in the storage url for an accessible object being created from a swift auth_address. So is the case when the scheme is ``swift``. This behavior is suitable for single-tenant swift store and not multi-tenant store. The solution is to ensure that if deploying multi-tenant swift store, prohibit setting of swift_store_config_file. This patch does this by ensuring that multi-tenant and swift_store_config_file are not configured to work together. TODO: When somebody changes to multi-tenant from single-tenant store, and they were using the swift config for single-tenant, the operator will not be able to access those images any longer. Logic to ensure that multi-tenant uses the swift conf file if there is a need to access an image that was created using single-tenant and swift+config could be introduced. UpgradeImpact DocImpact Closes-Bug: 1625075 Change-Id: I8b5c31541d3c501ad7c2520b463f881599f4a28e Co-Authored-By: Hemanth Makkapati <hemanth.makkapati@rackspace.com> Co-Authored-By: Dharini Chandrasekar <dharini.chandrasekar@intel.com>
* | Move rootwrap config files from etc/* into etc/glance/*Tomoki Sekiyama2016-11-041-0/+5
|/ | | | | | | | To cleanly utilize devstack's configure_rootwrap function to install rootwrap config files, these should be placed in etc/glance/ directory as nova and cinder do. Change-Id: I6d4ee6929f3c3536424bb6790c958aa464860300
* Always return a sorted list of drivers for configsNikhil Komawar2016-09-011-0/+16
| | | | | | | | | | | | | | | | | | | | | glance.store entry point used in Glance for the store library is resulting in generating random order in each run of the ``tox -e genconfig`` command. This is because of the unsorted iterator returned by the stevedore extension manager [1, 2]. This commit fixes that and returs a deterministic, sorted list of drivers to generate the configs in Glance. Example scenario is at change Iea2c538b37182191445cc5c1f8b2d9dceed06343 Closes-Bug: 1619487 [1] https://github.com/openstack/glance_store/blob/22fa2b08e76a8ebc39ade92504aeafb0bf8d2f8c/glance_store/backend.py#L135 [2] http://docs.openstack.org/developer/stevedore/managers.html#stevedore.extension.ExtensionManager.__iter__ Co-Authored-By: Joshua Harlow <jxharlow@godaddy.com> Change-Id: I3146b8597a5d89da49b84d6653edacc3067c2c71
* Merge "Add release notes for 0.17.0"0.17.0Jenkins2016-08-181-0/+14
|\
| * Add release notes for 0.17.0Nikhil Komawar2016-08-171-0/+14
| | | | | | | | | | | | | | | | | | Besides the configuration help text enhancements, there has been removal of the deprecated exceptions. This commit adds a release note for the same. Change-Id: Ib0d6b67eaa03437daf819d52926aaded1a59fe19
* | Release note for glance_store configuration opts.Dharini Chandrasekar2016-08-171-0/+29
|/ | | | | | | | | | | Adding a release note stating the work on improving configuration options of Glance store for this release. Some of the configuration options in Glance store were set with a ``min``, preventing them to accept negative integers like in the previous release. This release note will give operators a heads up on this. Change-Id: I8db8764f84c92e987a774ce3650beb53d9635905
* Remove S3 driverNikhil Komawar2016-07-271-0/+15
| | | | | | | | | | | | | | | | | | | | | | | As per the deprecation indicated in change I139c36c2d591a55f0f91ea32efa963f80c28e444 , we are on track to removing the S3 driver from glance_store in Newton. The process of maintainers for individual drives was initiated in [1]. However, S3 doesn't have a maintainer and has been deprecated in Mitaka. This commit intends to remove the S3 driver completely from the glance_store source tree. If required, we recommend that this driver be maintained outside of the glance_store source tree until you or someone you know intend to support the code for long term. In the later case, we hope that you will welcome our spec process to help plan the project priorities. DocImpact UpgradeImpact [1] http://lists.openstack.org/pipermail/openstack-dev/2015-December/081966.html Change-Id: I032b0fc16400cbd2112687d38e010128be699221
* Fix releasenotes to pass reno gateskairat_kushaev2016-04-111-6/+6
| | | | | | | | | Release note for swift driver update cannot be generated because of intendation, so we need to fix that error. After that we can safely turn on reno gates for glance_store. Change-Id: I0293c247bc87d81218c4350393a8bfb4d769bc91 Closes-Bug: #1568767
* Merge "Implement re-authentication for swift driver"0.12.0Jenkins2016-03-011-0/+12
|\
| * Implement re-authentication for swift driverkairat_kushaev2016-02-261-0/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Enable re-authentication when downloading or uploading images. If single tenant store is used then request the new token for service user. If multi tenant store is used then request the new token with trusts. Note: Both features are available for Keystone V3 API only. If store.auth_version is not '3' then use old approach to receive Swift Connections. DocImpact: Describe how to enable/disable re-authentication and add notes about Keystone v3 support only. Implements bp prevention-of-401-in-swift-driver Change-Id: Id4e479e29ae8f71ff93f769246989b4b180f5c68
* | Fix misspelling in the releasenote support-cinder-uploadTomoki Sekiyama2016-02-291-1/+1
| | | | | | | | Change-Id: If4dcfec3175db960b4665404b1b341db60d84aac
* | Merge "Switch VMWare Datastore to use Requests"Jenkins2016-02-261-0/+6
|\ \
| * | Switch VMWare Datastore to use RequestsIan Cordasco2016-02-241-0/+6
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously the VMWare Datastore was using HTTPS Connections from httplib which do not verify the connection. Switching to requests allows the store to perform proper connection level verification for a secure connection. By switching to using requests, we will get several benefits: 1. Certificate verification when using HTTPS 2. Connection pooling when following redirects 3. Help handling redirects 4. Help with Chunked Encoding Partial-bug: 1436082 Co-authored-by: Sabari Kumar Murugesan <smurugesan@vmware.com> Change-Id: I8ff20b2f6bd0e05cd50e44a60ec89fd54f87e1b4
* | Implement get, add and delete for cinder storeTomoki Sekiyama2016-02-261-0/+8
|/ | | | | | | | | | | This implements get, add, delete methods for cinder storage driver to enable users to upload/download the images to/from the volumes. This also will be useful for users who want to utilize storage features such as copy-on-write cloning for creating a new volume from an image volume efficiently. Change-Id: Ie228d1d95365e81881691af4cb8b170335a73868 Implements: blueprint cinder-store-upload-download
* Merge "Set documented default directory for filesystem"Jenkins2016-01-211-0/+5
|\
| * Set documented default directory for filesystemIan Cordasco2016-01-181-0/+5
| | | | | | | | | | | | | | | | | | We document that the default value of filesystem_store_datadir is /var/lib/glance/images without ever actually setting that default. Co-Authored-By: kairat_kushaev <kkushaev@mirantis.com> Closes-bug: #1501662 Change-Id: If6ab4f727f205c7828f247c7588b1f9bad78d1e8
* | Remove the gridfs driverFlavio Percoco2016-01-181-0/+7
|/ | | | | | | The gridfs driver was marked as deprecated some releases ago. This patch removes the deprecated driver from the tree. Change-Id: I72785eb77447909fc67d42e17d805eaa77cf45a2
View Lorry Controller Status