OpenStack Kilo Design Summit

As part of the work to stabilize the interfaces which should be externally consumable one of particular note is the auth layer in tempest. Currently it's designed to be fairly modular and has 2 implementations for either keystone v2 or v3, but it is still has some underlying assumptions about how the auth is setup. However, as part of the migration to tempest-lib this interface arguably should be created in a way which doesn't assume keystone is the auth mechanism being used. The in-tree implemenations of the interface will still be keystone specific, but it will allow external consumers to use whatever auth system they need.(for example swift auth) This session will discuss how we should implement the to-be auth interface in tempest-lib (by considering some use cases) to make it work for most use cases.