Open Stack

Hi,

I wish to make use of the Ec2Signer class in keystone.common.utils, to
generate pre-signed URLs which are later used for authentication via the
keystone EC2 auth extension.

I'm obviously keen to avoid directly importing an internal keystone class,
and would prefer to avoid a direct cut/paste, so was considering where it
could be moved such that it's a user-visible utility class?

Initial thought was that moving the class to either python-keystoneclient or
possibly oslo, wanted to get feedback as to the most acceptable option from
the keystone devs before proceeding?

My proposal:
- Move Ec2Signer into keystoneclient.utils (or create an authutils module?)
- Make keystone.contrib.ec2.core import Ec2Signer from keystoneclient

Before spending time generating some patches doing this - would such an
approach be acceptable to the keystone team?

Thanks!

Steve

--
Steve Hardy
Red Hat Engineering, Cloud