Re: [openstack-dev] [keystone]PKI token VS Fernet token

Excerpts from Lance Bragstad's message of 2017-02-25 13:07:58 -0600: > Since both token formats rebuild the authorization context at validation > time, we can remove some revocation events that are no longer needed. This > means we won't be storing as many revocation events on role removal from >

Re: [openstack-dev] [neutron] - Neutron team social Pictures

Thanks for putting these up! On Fri, Feb 24, 2017 at 8:39 AM, Vasudevan, Swaminathan (PNB Roseville) < swaminathan.vasude...@hpe.com> wrote: > Hi Folks, > > Here is the link to the pictures that I took during the Neutron Social in > Atlanta. > > > >

Re: [openstack-dev] [QA]Refactoring Scenarios manager.py

Hi, Thank you for bringing this up. Yeah, I understand your frustration. We already have the document about our stable interface[1]. It says -- Stability Any code that lives in tempest/lib will be treated as a stable interface. This means that any public interface under the tempest/lib

Re: [openstack-dev] [tripleo] PTG + Release status

Sent from my iPhone > On Feb 25, 2017, at 11:14 AM, Emilien Macchi wrote: > >> On Fri, Feb 24, 2017 at 8:52 PM, Emilien Macchi wrote: >> Before leaving in week-end, I thought useful to share some infos with the >> team. >> >> First of all, it was

Re: [openstack-dev] [keystone][api] Changing devstack to not set up keystone on :5000 and :35357

Nice! Thanks for revisiting this, Brant. Was this a cross-project goal/discussion at the PTG? On Fri, Feb 24, 2017 at 9:24 AM, Brant Knudson wrote: > > At the PTG there was some discussion about changing services to not listen > on ports[0]. I'd been working on this for devstack

Re: [openstack-dev] [keystone]PKI token VS Fernet token

On Sat, Feb 25, 2017 at 12:47 AM, Clint Byrum wrote: > Excerpts from joehuang's message of 2017-02-25 04:09:45 +: > > Hello, Matt, > > > > Thank you for your reply, just as what you mentioned, for the slow > changed data, aync. replication should work. My concerns is that

Re: [openstack-dev] [monasca] cassandra support in Monasca

Hi Pradeep Basic Cassandra support is already implemented. But there are some performance problems. These performance problems are difficult to enhance. So we are planning to switch other DB and will let Cassandra deprecated. KariosDB is one of candidates and not implemented yet. KariosDB is

Re: [openstack-dev] [tripleo] PTG + Release status

On Fri, Feb 24, 2017 at 8:52 PM, Emilien Macchi wrote: > Before leaving in week-end, I thought useful to share some infos with the > team. > > First of all, it was awesome to meet people face to face, really. I'm > already looking forward to the next time. > > About Ocata

Re: [openstack-dev] [ceilometer][gnocchi] How to push compute node metrics to gnocchi?

On Sat, Feb 25 2017, Pradeep Singh wrote: > I installed devstack and enabled compute node's cpu utilization collection > in nova.conf, but seeing below error in notification agent's log. > > 2017-02-25 08:40:15.515 22662 WARNING ceilometer.dispatcher.gnocchi [-] > metric

Re: [openstack-dev] [ceilometer][gnocchi] getting extra keys not allowed @ data[flavor name']

On Sat, Feb 25 2017, Pradeep Singh wrote: > Hello, > > I installed latest devstack, and ceilometer dispatcher is not able to > dispatch the instance data in gnocchi, in logs i am seeing: > > 'extra keys not allowed @ data[flavor_name']' > > When i deleted line 'flavor_name:

Re: [openstack-dev] [nova][cinder] Schedule Instances according to Local disk based Volume?

On 2/23/2017 9:27 PM, Zhenyu Zheng wrote: BTW, I think this can be done using new placement service, using the custom resource provider? correct? This came up briefly on Friday at the PTG but unfortunately jaypipes and cdent had already left. You should talk to them about this for more

[openstack-dev] [QA]Refactoring Scenarios manager.py

Hi guys, So I have a problem with these 2 patches here [1] and here [2]. You basically are blocking any attempt of refactoring manager.py. Refactoring that file has been our number one priority for 2 cycles, and so far hardly no one stepped up really to do the work, except me with these 2 patches.

[openstack-dev] [ceilometer][gnocchi] How to push compute node metrics to gnocchi?

Hello, I installed devstack and enabled compute node's cpu utilization collection in nova.conf, but seeing below error in notification agent's log. 2017-02-25 08:40:15.515 22662 WARNING ceilometer.dispatcher.gnocchi [-] metric compute.node.cpu.frequency is not handled by Gnocchi 2017-02-25

[openstack-dev] [ceilometer][gnocchi] getting extra keys not allowed @ data[flavor name']

Hello, I installed latest devstack, and ceilometer dispatcher is not able to dispatch the instance data in gnocchi, in logs i am seeing: 'extra keys not allowed @ data[flavor_name']' When i deleted line 'flavor_name: resource_metadata.(instance_type|( flavor.name))' from