Keystone V3 Support

Bug #1962763 reported by Gareth Woolridge
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Daisy
Fix Released
Undecided
Unassigned

Bug Description

In starting to look at redeploying error-tracker to PS5 it was discovered that the charms and services do not support Keystone v3 which is a hard requirement for deployment on a modern OpenStack.

At a minimum the charms for fetching code from Swift, and the apps pushing/fetching cores from Swift/RadosGW are missing:

OS_PROJECT_NAME
OS_IDENTITY_API_VERSION

A novarc for such a cloud would likely set these:

OS_PROJECT_NAME=${OS_TENANT_NAME}
OS_IDENTITY_API_VERSION=3

Revision history for this message
Brian Murray (brian-murray) wrote :

I'm not terribly familiar with swift but given that --os-identity-api-version "defaults to env[ST_AUTH_VERSION], env[OS_AUTH_VERSION], env[OS_IDENTITY_API_VERSION] or 1.0". Are any changes actually necessary when calling /usr/bin/swift?

Revision history for this message
Brian Murray (brian-murray) wrote :

daisy/submit_core.py and daisy/retracer.py both set auth_version to 2.0 so that'll need changing.

Revision history for this message
Brian Murray (brian-murray) wrote :

The switch to keystone v3 has been deployed.

Changed in daisy:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.