There is also nothing stopping you from using both. For example, you could
use the OpenStack SDK for most things but if you hit an edge case where you
need something specific you can then import the particular client lib.
Cheers,
Josh
On Thu, Apr 19, 2018 at 1:05 AM, Chris Friesen
wrote:
> I sh
Hello Ian,
My understanding of it is that you need to receive a new link. Monty is
slowly sending those out in batches and he hasn't finished. I expect he'll
email the list once he has finished to confirm so I'd suggest holding off
until then to check.
Cheers,
Josh
On Mon, Jul 18, 2016 at 1:58 P
Yep and that patch was backported into kilo last month[0]. If others are
experiencing pain, they could try the head of stable/kilo.
Given this is possibly causing some operator pain, it might be worth
cutting a bug-fix release, or updating the installation instructions.
[0] https://review.opensta
affected) and
remove them bringing the databases inline with 133_folsom users.
I'll propose this for backporting into Havana after it is merged.
Cheers,
Josh
Rackspace Australia
On 10/30/13 11:42 AM, Blair Zajac wrote:
On 10/29/2013 05:16 PM, Joshua Hesketh wrote:
Hi Blair,
Thanks for the c
emove them bringing the databases inline with 133_folsom users.
I'll propose this for backporting into Havana after it is merged.
Cheers,
Josh
Rackspace Australia
On 10/30/13 11:42 AM, Blair Zajac wrote:
On 10/29/2013 05:16 PM, Joshua Hesketh wrote:
Hi Blair,
Thanks for the clarifications,
RC's or upstream etc.
Thanks,
Josh
Rackspace Australia
On 10/30/13 10:10 AM, Blair Zajac wrote:
On 10/29/2013 04:04 PM, Joshua Hesketh wrote:
Hi Blair,
So from your dump a few weeks ago you have both fkeys
'instance_info_caches_ibfk_1' and
'instance_info_caches_instanc
o be why you can't see the old fkey.
Thanks,
Josh
Rackspace Australia
On 10/29/13 3:50 PM, Blair Zajac wrote:
On 10/28/13 6:17 PM, Joshua Hesketh wrote:
Hi guys,
I have a patch in the works against this that will hopefully fix your
problems:
https://review.openstack.org/#/c/54212/
One o
Hi guys,
I have a patch in the works against this that will hopefully fix your
problems:
https://review.openstack.org/#/c/54212/
One of the gotchas though will be if you have already ran migration 185
you can't run it again (even if it failed because it'll try and do
operations that it got p
