Re: [Openstack-operators] Cinder API with multiple regions not working.

Hi, Still no luck. I have remove the “-“ from the names. [root@controller: ~/openstack] # openstack service list +--+---+--+ | ID | Name | Type | +--+

Re: [Openstack-operators] Galera setup testing

At this point, we use Keystone and UUID’s for our setup, but we don’t store the UUID tokens in the Database. We use Memcache to do that. Actually we use McRouter and Memcache to make sure any node in our control plane can validate that token. —Joe From: Ajaya Agrawal Date: Friday, Decemb

Re: [Openstack-operators] OpenStack Liberty automation script release.

Sure can! The goal of our Operators repo is to work the same way the rest of the OpenStack projects work. This means you can create blueprints, bugs, pull requests, etc. The operators room on IRC will also post when there are any new updates, so you can follow-up with anyone there as well.

Re: [Openstack-operators] Galera setup testing

On Fri, Dec 11, 2015 at 12:25 AM, Ajaya Agrawal wrote: > Thanks Matt. That surely is helpful. If you could share some numbers or > problems you faced when you were storing UUID tokens in database, it would > be awesome. In my test setup with Keystone Kilo, Fernet token creation and > validation w

Re: [Openstack-operators] Router associated with multiple l3 agents

We were hoping that upgrading to Kilo might magically fix this, but we've still seen it occurring, although it seems to be happening less. Is it a database constraint that's supposed to stop this being possible ? I'm wondering if somehow through multiple upgrades we're missing something in the data

Re: [Openstack-operators] Galera setup testing

On Fri, Dec 11, 2015 at 6:06 AM, Bajin, Joseph wrote: > At this point, we use Keystone and UUID’s for our setup, but we don’t store > the UUID tokens in the Database. We use Memcache to do that. Actually we > use McRouter and Memcache to make sure any node in our control plane can > validate tha

Re: [Openstack-operators] Galera setup testing

We do something similar: Instead of McRouter, we use the repcached patches to replicate data between two memcached nodes. We then use HAProxy as a single entry point for memcached requests. We've been doing this for 6+ months and it's been working great. It's effectively solved the issue I describ

Re: [Openstack-operators] Cinder API with multiple regions not working.

Hi Salman, I'm stumped. I was able to confirm that Keystone acts a little differently when you have multiple regional endpoints connected to the same "service_name" and "service_type" than if you have multiple regional endpoints, each with their own "service_name" but same "service_type"'s. For

Re: [Openstack-operators] OpenStack Liberty automation script release.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > On Fri, Dec 11, 2015 at 8:19 AM, Bajin, Joseph > wrote: > > These would make great additions to the OpenStack Operators github > repos that we have setup. It would probably fit under the > http://github.

[Openstack-operators] OpenStack Developer Mailing List Digest December 5-11

Perma Link: http://www.openstack.org/blog/2015/12/openstack-developer-mailing-list-digest-20151205/ Success Bot Says * AJaeger: With Juno End-of-Life, Python 2.6 testing has been removed from OpenStack CI. * Tell us yours via IRC with a message “#success [insert success]”. * Mo

Re: [Openstack-operators] Cinder API with multiple regions not working.

Hi, It is working by setting exact names of the services. [root@smog: ~] # openstack service list +--+--+--+ | ID | Name | Type | +--+--+-

[Openstack-operators] OpenStack Weekly Community Newsletter (Dec. 5-11)

Travel grants bring global community members to OpenStack Summit Key contributors from 15 countries attended the recent OpenStack Summit in Tokyo. The program for Austin is growing – find out more about the Travel Support Program. OpenStack Mitaka release: what’s next for

Re: [Openstack-operators] Cinder API with multiple regions not working.

Hi Salman, That's awesome news. Glad it's working. :) Joe On Fri, Dec 11, 2015 at 3:12 PM, Salman Toor wrote: > Hi, > > It is working by setting exact names of the services. > > > *[root@smog: ~]* # openstack service list > > +--+--+--+ >

[Openstack-operators] [nova] Live migration bug triage

Hi, I'm having a go at triaging live migration bugs in nova that hurt operators at https://etherpad.openstack.org/p/mitaka-nova-live-migration-bugs . This is building up to a bug triage day and an associated push to close live migration bugs. I'd be interested in feedback on if there are specific