On 11/13/2014 07:14 AM, Ihar Hrachyshka wrote:
> On 12/11/14 15:17, Sean Dague wrote:
>
>> 1) just delete the trove exercise so we can move forward -
>> https://review.openstack.org/#/c/133930 - that will need to be
>> backported as well.
>
> The patch is merged. Do we still need to backport it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 12/11/14 15:17, Sean Dague wrote:
>
> 1) just delete the trove exercise so we can move forward -
> https://review.openstack.org/#/c/133930 - that will need to be
> backported as well.
The patch is merged. Do we still need to backport it baring
> | Sent: Wednesday, November 12, 2014 9:22 AM
> | To: OpenStack Development Mailing List (not for usage questions)
> | Subject: Re: [openstack-dev] [all] python-troveclient keystone v3 support
> | breaking the world
> |
> | On 11/12/2014 09:17 AM, Sean Dague wrote:
> | &
)
| Subject: Re: [openstack-dev] [all] python-troveclient keystone v3 support
| breaking the world
|
| On 11/12/2014 09:17 AM, Sean Dague wrote:
| > https://review.openstack.org/#/c/102315/ was merged yesterday, it
| > creates a non functional trove python client. (There are currently no
| &g
On 11/12/2014 09:17 AM, Sean Dague wrote:
> https://review.openstack.org/#/c/102315/ was merged yesterday, it
> creates a non functional trove python client. (There are currently no
> tests in python trove client to see if the commands even run after a
> code change).
>
> This means the trove devs
https://review.openstack.org/#/c/102315/ was merged yesterday, it
creates a non functional trove python client. (There are currently no
tests in python trove client to see if the commands even run after a
code change).
This means the trove devstack exercise can't work.
Which means everything test
