[openstack-dev] [oslo][keystone] Trying to get openstack.common.wsgi in keystoneclient

Doug Hellmann doug.hellmann at dreamhost.com
Wed Apr 24 19:58:45 UTC 2013

On Wed, Apr 24, 2013 at 8:52 AM, Dean Troyer <dtroyer at gmail.com> wrote:

> On Wed, Apr 24, 2013 at 10:07 AM, Chmouel Boudjnah <chmouel at enovance.com>
> wrote:
> > Hello,
> > I am trying to move the s3_token and ec2_token middleware to
> > python-keystoneclient I thought it would be a good idea to make them
> > using openstack.common.wsgi instead of {swift,keystone,nova}.wsgi
> >
> > It seems that adding wsgi trying to import the full set of modules
> > from openstack.common as a dependency which doesn't seem to please
> > (and for good reasons) the other reviewers.
> I can't speak to the wisdom of adding these to keystonelcient but let
> me express a concern about adding more non-client dependencies to it.
> Remember that every CLI user will be installing all of these deps even
> if they are only used in middleware.  Hopefully the packagers can
> split them out to their own sub-package?

We could help them by making the middleware its own project, with its own
version number. I'm sure putting the middleware in the client library was
pragmatic at the time, but it seems like a poor fit for a real client
library. Does it still make sense to keep it there?


> dt
> --
> Dean Troyer
> dtroyer at gmail.com
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130424/d6141733/attachment.html>

More information about the OpenStack-dev mailing list