| 1 |
--- |
| 2 |
features: |
| 3 |
- | |
| 4 |
This release includes support for Glance multiple stores. An |
| 5 |
operator may now specify which Glance store will be used when |
| 6 |
a volume is uploaded to Glance as an image. Some details |
| 7 |
about this feature: |
| 8 |
|
| 9 |
* This feature is not directly user-facing. To enable it, an |
| 10 |
operator must add the field ``image_service:store_id`` in the |
| 11 |
volume-type extra-specs. The value of the field is a valid |
| 12 |
store identifier (``id``) configured in Glance, which may be |
| 13 |
discovered by making a ``GET /v2/info/stores`` call to the |
| 14 |
Image Service API. |
| 15 |
* If ``image_service:store_id`` is not set in the extra-specs for a |
| 16 |
volume-type, then any volume of that type uploaded as an image will |
| 17 |
be uploaded to the default store in Glance. |
| 18 |
* The ``image_service:store_id`` can only be set in the extra-specs |
| 19 |
for a volume-type when multiple glance stores are configured. |
| 20 |
* Cinder validates proposed Glance store identifiers by contacting |
| 21 |
Glance at the time the ``image_service:store_id`` is added to a |
| 22 |
volume-type's extra-specs. Thus the Image Service API must be |
| 23 |
available when a volume-type is updated. |