Enable v2 API
Bug #1447156 reported by
Jorge Niedbalski
This bug affects 4 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| glance (Juju Charms Collection) |
Expired
|
High
|
Unassigned | ||
Bug Description
The charm by default just exposes v1 api/registry endpoints. We should enable
an option for activate v2 endpoints by default.
| Changed in glance (Juju Charms Collection): | |
| assignee: | nobody → Jorge Niedbalski (niedbalski) |
| Changed in glance (Juju Charms Collection): | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: hitlist openstack sts |
| Changed in glance (Juju Charms Collection): | |
| assignee: | Jorge Niedbalski (niedbalski) → nobody |
Revision history for this message
| Billy Olsen (billy-olsen) wrote | #1 |
| Changed in glance (Juju Charms Collection): | |
| status: | Triaged → Incomplete |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in glance (Juju Charms Collection): | |
| status: | Incomplete → Expired |
To post a comment you must log in.
Hmm, is there a specific use case for this? The glance API is able to handle multiple versions simultaneously, whereas other services (such as cinder) require additional endpoints to be registered for version 1 and version 2. The glance API is somewhat nicer in that it simply requires one endpoint (the image endpoint) and can handle multiple versions.
Additionally, the default for the enable_v2 api setting has been True at least as far back as havana (I didn't go further), so by default the v2 api is enabled and activated.