Hey! This might be fairly tricky to fix properly given the design of the devstack gate. I could be wrong, it might not be terrible now that we can release new client lib versions to PyPI more quickly. The devstack gate explicitly tests proposed change to trunk of one project against tip of trunk across all the other projects. That's great for the dev purpose, and can solidify through sequencing during the milestone-proposed period, but if we have people with standalone horizon installations that are tracking trunk more closely, we might need to do some more thinking.
Could I request that you drop by the CI meeting on Tuesday so we can chat about it interactively? I think this is important and that we should do everything we can to get this right. Monty On 07/29/2012 06:34 PM, Gabriel Hurley wrote: > Public bug reported: > > We patched this bug: https://bugs.launchpad.net/horizon/+bug/1027210 > > However, that fix worked for devstack and broke stand-alone > installations of horizon because devstack pulled the clients from Github > while Horizon's requirements file pulls them from PyPI. This is no good. > > Now anytime you try to list out images from glance (except when using > devstack) you get this error: > > list() got an unexpected keyword argument 'page_size' > > We need to reconcile devstack with Horizon, and in the future Horizon > will *only* accept changes that work with *released* client versions. _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
