83dd6a1c0e
In many cases, including devstack and TripleO, the swift account to use is based on the project_id of the 'service' project, so it makes sense to use it as a default. Similarly, the temporary URL key can be fetches from Swift, using HEAD on the account used to access it. In both cases it is assumed that the same project is used by Ironic and Glance to access Swift. Explicit values have to be provided otherwise. Finally, the endpoint URL can be fetched from the service catalog. Care is taken to strip the /v1/AUTH_<tenant ID> suffix. Closes-Bug: #1737714 Change-Id: I701899928f0f780939f17aabc59eb90593ba95f0
16 lines
748 B
YAML
16 lines
748 B
YAML
features:
|
|
- |
|
|
If the ``[glance]swift_account`` option is not set, the default value is
|
|
now calculated based on the ID of the project used to access the object
|
|
store. Previously this option was required. This change does not affect
|
|
using RadosGW as an object store backend.
|
|
- |
|
|
If the ``[glance]swift_temp_url_key`` option is not set, ironic now tries
|
|
to fetch the key from the project used to access swift (often
|
|
called ``service``). This change does not affect using RadosGW as an
|
|
object store backend.
|
|
- |
|
|
If the ``[glance]swift_endpoint_url`` option is not set, ironic now tries
|
|
to fetch the Object Store service URL from the service catalog. The
|
|
``/v1/AUTH_*`` suffix is stripped, if present.
|