[openstack-dev] [forum] [keystone] default roles etherpad

2018-05-11 Thread Lance Bragstad
Hey everyone, I've created an etherpad for the default roles discussion in Vancouver [0]. It currently contains basic context and some session goals. If you have any input or additional session goals, please don't hesitate to add to the etherpad. Thanks and hope to see you there, Lance [0]

[openstack-dev] [forum] [keystone] unified limits etherpad

2018-05-11 Thread Lance Bragstad
Hi all, I've created an etherpad for the unified limits session at the forum [0]. I've bootstrapped it with some basic context so that we can spend as much time as possible on the session goals. If you have questions, comments, or additional session goals, please feel free to add them to the

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

2018-05-11 Thread Matt Riedemann
On 5/11/2018 2:00 PM, Fox, Kevin M wrote: Currently the isolation between the Projects and the thing that the users use, the Constellation allows for user needs to easily slip through the cracks. Cause "Project X: we agree that is a problem, but its Y projects problem. Project Y: we agree

Re: [openstack-dev] [keystone] keystoneauth version auto discovery for internal endpoints in queens

2018-05-11 Thread Morgan Fainberg
Typically speaking if we broke a behavior via a change in KeystoneAuth (not some behavior change in openstackclient or the way osc processes requests), we are in the wrong and we will need to go back through and fix the previous behavior. I'll spend some time going through this to verify if this

[openstack-dev] [keystone] keystoneauth version auto discovery for internal endpoints in queens

2018-05-11 Thread Vlad Gusev
Hello. We faced a bug in keystoneauth, which haven't existed before Queens. In our OpenStack deployments we use urls like http://controller:5000/v3 for internal and admin endpoints and urls like https://api.example.org/identity/v3 for public endpoints. We set option public_endpoint in [default]

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

2018-05-11 Thread Lance Bragstad
On 05/11/2018 02:00 PM, Fox, Kevin M wrote: > Who are your users, what do they need, are you meeting those needs, and what > can you do to better things? > > If that can't be answered, how do you know if you are making progress or > staying relevant? > > Lines of code committed is not a metric

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

2018-05-11 Thread Jimmy McArthur
Fox, Kevin M wrote: Who are your users, what do they need, are you meeting those needs, and what can you do to better things? IMO, OpenStack really needs some Leadership at a higher level. It seems to be lacking some things: 1. A group that performs... lacking a good word

[openstack-dev] [keystone] Keystone Team Update - Week of 7 May 2018

2018-05-11 Thread Colleen Murphy
# Keystone Team Update - Week of 7 May 2018 ## News ### Patrole in CI With all the work that has been happening around fixing policy, it would be good to have better policy validation in CI[1]. However, there are some concerns that using Patrole in a voting gate job will lock us in to

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

2018-05-11 Thread Fox, Kevin M
Who are your users, what do they need, are you meeting those needs, and what can you do to better things? If that can't be answered, how do you know if you are making progress or staying relevant? Lines of code committed is not a metric of real progress. Number of reviews isn't. Feature

Re: [openstack-dev] [horizon] Scheduling switch to django >= 2.0

2018-05-11 Thread Doug Hellmann
Excerpts from Akihiro Motoki's message of 2018-05-12 00:14:33 +0900: > Hi zigo and horizon plugin maintainers, > > Horizon itself already supports Django 2.0 and horizon unit test covers > Django 2.0 with Python 3.5. > > A question to all is whether we change the upper bound of Django from <2.0

Re: [openstack-dev] [kolla] Building Kolla containers with 3rd party vendor drivers

2018-05-11 Thread Sandhya Dasu (sadasu)
Hi Paul, I am happy to use the changes you proposed to https://github.com/openstack/kolla/blob/master/kolla/common/config.py I was under the impression that this was disallowed for drivers that weren’t considered “reference drivers”. If that is no longer the case, I am happy to go this route

[openstack-dev] [requirements][glare][mogan][solum][compute-hyperv][kingbird][searchlight][swauth][networking-powervm][rpm-packaging][os-win] uncaping eventlet

2018-05-11 Thread Matthew Thode
Please review your particular uncaping patch (all but rpm-packaging are passing gate it looks like). We'd like to move on to a newer eventlet for rocky. https://review.openstack.org/#/q/topic:uncap-eventlet+status:open -- Matthew Thode (prometheanfire) signature.asc Description: PGP

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

2018-05-11 Thread Jay Pipes
On 05/11/2018 12:21 PM, Zane Bitter wrote: On 11/05/18 11:46, Jay Pipes wrote: On 05/10/2018 08:12 PM, Zane Bitter wrote: On 10/05/18 16:45, Matt Riedemann wrote: On 5/10/2018 3:38 PM, Zane Bitter wrote: How can we avoid (or get out of) the local maximum trap and ensure that OpenStack will

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

2018-05-11 Thread Zane Bitter
On 11/05/18 11:46, Jay Pipes wrote: On 05/10/2018 08:12 PM, Zane Bitter wrote: On 10/05/18 16:45, Matt Riedemann wrote: On 5/10/2018 3:38 PM, Zane Bitter wrote: How can we avoid (or get out of) the local maximum trap and ensure that OpenStack will meet the needs of all the users we want to

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

2018-05-11 Thread Jay Pipes
On 05/10/2018 08:12 PM, Zane Bitter wrote: On 10/05/18 16:45, Matt Riedemann wrote: On 5/10/2018 3:38 PM, Zane Bitter wrote: How can we avoid (or get out of) the local maximum trap and ensure that OpenStack will meet the needs of all the users we want to serve, not just those whose needs are

Re: [openstack-dev] [horizon] Scheduling switch to django >= 2.0

2018-05-11 Thread Akihiro Motoki
Hi zigo and horizon plugin maintainers, Horizon itself already supports Django 2.0 and horizon unit test covers Django 2.0 with Python 3.5. A question to all is whether we change the upper bound of Django from <2.0 to <2.1. My proposal is to bump the upper bound of Django to <2.1 in Rocky-2.

Re: [openstack-dev] [edge][keystone][forum]: Keystone edge brainstorming etherpad

2018-05-11 Thread Csatari, Gergely (Nokia - HU/Budapest)
Hi, Thanks for your comments I've added some reactions. Also thanks for the advertisement. Br, Gerg0 From: Lance Bragstad [mailto:lbrags...@gmail.com] Sent: Friday, May 11, 2018 4:48 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [edge][keystone][forum]: Keystone edge

Re: [openstack-dev] [edge][keystone][forum]: Keystone edge brainstorming etherpad

2018-05-11 Thread Lance Bragstad
On 05/10/2018 06:30 AM, Csatari, Gergely (Nokia - HU/Budapest) wrote: > > Hi, > >   > > I’ve added some initial text to the Etherpad [1 > ] of > the Possible edge architectures for Keystone Forum session [2 >

Re: [openstack-dev] [ironic][stable] Re-adding Jim Rollenhagen to ironic stable maintenance team?

2018-05-11 Thread Ruby Loo
On Fri, May 11, 2018 at 7:50 AM, Julia Kreger wrote: > Greetings folks, > > Is there any objection if we re-add Jim to the ironic-stable-maint > team? He was a member prior to his brief departure and I think it > would be good to have another set of hands that can

Re: [openstack-dev] Should we add a tempest-slow job?

2018-05-11 Thread Matthew Treinish
On Fri, May 11, 2018 at 08:45:39AM -0500, Matt Riedemann wrote: > The tempest-full job used to run API and scenario tests concurrently, and if > you go back far enough I think it also ran slow tests. Well it's a bit more subtle than that. Skipping slow tests was added right before we introduced

[openstack-dev] Should we add a tempest-slow job?

2018-05-11 Thread Matt Riedemann
The tempest-full job used to run API and scenario tests concurrently, and if you go back far enough I think it also ran slow tests. Sometime in the last year or so, the full job was changed to run the scenario tests in serial and exclude the slow tests altogether. So the API tests run

[openstack-dev] [placement] low hanging bug for a new contributor

2018-05-11 Thread Jay Pipes
Hi Stackers, Here's a small bug that would be ideal for a new contributor to pick up: https://bugs.launchpad.net/nova/+bug/1770636 Come find us on #openstack-placement on Freenode if you'd like to pick it up and run with it. Best, -jay

Re: [openstack-dev] [ironic][stable] Re-adding Jim Rollenhagen to ironic stable maintenance team?

2018-05-11 Thread Julia Kreger
On Fri, May 11, 2018 at 8:20 AM, Dmitry Tantsur wrote: > Hi, [trim] >> If there are no objections, I'll re-add him next week. > > > I don't remember if we actually can add people to these teams or it has to > be done by the main stable team. > I'm fairly sure I'm the person

Re: [openstack-dev] [ironic][stable] Re-adding Jim Rollenhagen to ironic stable maintenance team?

2018-05-11 Thread Dmitry Tantsur
Hi, Funny, I was just about to ask you about it :) Jim is a former PTL, so I cannot see why we wouldn't add him to the stable team. On 05/11/2018 01:50 PM, Julia Kreger wrote: Greetings folks, Is there any objection if we re-add Jim to the ironic-stable-maint team? He was a member prior to

[openstack-dev] [ironic][stable] Re-adding Jim Rollenhagen to ironic stable maintenance team?

2018-05-11 Thread Julia Kreger
Greetings folks, Is there any objection if we re-add Jim to the ironic-stable-maint team? He was a member prior to his brief departure and I think it would be good to have another set of hands that can approve the changes as three doesn't seem like quite enough when everyone is busy. If there

[openstack-dev] [nova] [placement] placement update 18-19

2018-05-11 Thread Chris Dent
HTML: https://anticdent.org/placement-update-18-19.html This is placement update 18-19. 18 was skipped because I was on holiday. With this issue I'm going to start cross-posting to my blog to increase exposure, double up the archiving, and get the content showing up on the OpenStack

Re: [openstack-dev] [neutron][ml2 plugin] unit test errors

2018-05-11 Thread Neil Jerram
On Fri, May 11, 2018 at 10:09 AM Andreas Scheuring < scheu...@linux.vnet.ibm.com> wrote: > So what you need to do first is to make a patch for networking-onos that > does ONLY the following > > > replace all occurrences of > > * neutron.callbacks by neutron_lib.callbacks > *

[openstack-dev] [kolla] Building Kolla containers with 3rd party vendor drivers

2018-05-11 Thread Paul Bourke
Hi Sandhya, Thanks for starting this thread. I've moved it to the mailing list so the discussion can be available to anyone else who is interested, I hope you don't mind. If your requirement is to have third party plugins (such as Cisco) that are not available on tarballs.openstack.org,

Re: [openstack-dev] [neutron][ml2 plugin] unit test errors

2018-05-11 Thread Andreas Scheuring
So what you need to do first is to make a patch for networking-onos that does ONLY the following replace all occurrences of * neutron.callbacks by neutron_lib.callbacks * neutron.plugins.ml2.driver_api by neutron_lib.plugins.ml2.api Push this patch for review. After that tests should

Re: [openstack-dev] [all][monasca] pysnmp autogenerated code

2018-05-11 Thread Stefano Canepa
On 11 May 2018 at 08:26, Ilya Etingof wrote: > On 05/10/2018 05:01 PM, Stefano Canepa wrote: > > > > On 10 May 2018 at 10:55, Ilya Etingof > > wrote: > > > > > > Hi Stefano, > > > > The best solution would be of

Re: [openstack-dev] [all] Topics for the Board+TC+UC meeting in Vancouver

2018-05-11 Thread Thierry Carrez
Zane Bitter wrote: > [...] > How can we avoid (or get out of) the local maximum trap and ensure that > OpenStack will meet the needs of all the users we want to serve, not > just those whose needs are similar to those of the users we already have? It'a a good question, and a topic I raised a

Re: [openstack-dev] [all][monasca] pysnmp autogenerated code

2018-05-11 Thread Ilya Etingof
On 05/10/2018 05:01 PM, Stefano Canepa wrote: > > On 10 May 2018 at 10:55, Ilya Etingof > wrote: > > > Hi Stefano, > > The best solution would be of course to fix pysmi code generator [1] to > behave. ;-) > > > ​This is something