[openstack-dev] [zun][zun-ui] Priorities of new feature on Zun UI

2018-06-26 Thread Shu M.
Hi folks, Could you let me know your thoughts for priorities of new features on Zun UI. Could you jump to following pad, and fill your opinions? https://etherpad.openstack.org/p/zun-ui Best regards, Shu __ OpenStack

Re: [openstack-dev] [requirements][stable][docs] updating openstackdocstheme in stable branches

2018-06-26 Thread Tony Breeds
On Tue, Jun 26, 2018 at 09:03:40AM -0400, Doug Hellmann wrote: > Requirements team, > > At some point in the next few months we're going to want to raise > the constraint on openstackdocstheme in all of the old branches so > we can take advantage of a new feature for showing the supported >

[openstack-dev] [nova] Nova API Office Hour

2018-06-26 Thread Ghanshyam Mann
Hi All, From today, we will be hosting the office hour for Nova API discussions which will cover the Nova API priority and API Bug triage things. I have updated the information about agenda and time in wiki page [1]. All are welcome to join. We will continue this on every Wedneday 06.00 UTC

Re: [openstack-dev] [tc] [all] TC Report 18-26

2018-06-26 Thread Zane Bitter
On 26/06/18 09:12, Jay Pipes wrote: Is (one of) the problem(s) with our community that we have too small of a scope/footprint? No. Not in the slightest. Incidentally, this is an interesting/amusing example of what we talked about this morning on IRC[1]: you say your concern is that the scope

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Ghanshyam Mann
On Tue, 26 Jun 2018 19:32:59 +0900 Mehdi Abaakouk wrote > Hi, > > I have never understood the branchless tempest thing. Making Tempest > release is a great news for me. > > But about plugins... Tempest already provides a API for plugins. If you > are going to break

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Ghanshyam Mann
On Tue, 26 Jun 2018 19:12:33 +0900 Dmitry Tantsur wrote > On 06/26/2018 11:57 AM, Ghanshyam Mann wrote: > > > > > > > > On Tue, 26 Jun 2018 18:37:42 +0900 Dmitry Tantsur > > wrote > > > On 06/26/2018 11:18 AM, Ghanshyam Mann wrote: > > > > Hello

Re: [openstack-dev] [Openstack-operators] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Ghanshyam Mann
On Wed, 27 Jun 2018 10:19:17 +0900 Ghanshyam Mann wrote > ++ operator ML > > On Wed, 27 Jun 2018 10:17:33 +0900 Ghanshyam Mann > wrote > > > > > > > > On Tue, 26 Jun 2018 23:12:30 +0900 Doug Hellmann > wrote > > > Excerpts from

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Ghanshyam Mann
++ operator ML On Wed, 27 Jun 2018 10:17:33 +0900 Ghanshyam Mann wrote > > > > On Tue, 26 Jun 2018 23:12:30 +0900 Doug Hellmann > wrote > > Excerpts from Matthew Treinish's message of 2018-06-26 09:52:09 -0400: > > > On Tue, Jun 26, 2018 at 08:53:21AM

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Ghanshyam Mann
On Tue, 26 Jun 2018 23:12:30 +0900 Doug Hellmann wrote > Excerpts from Matthew Treinish's message of 2018-06-26 09:52:09 -0400: > > On Tue, Jun 26, 2018 at 08:53:21AM -0400, Doug Hellmann wrote: > > > Excerpts from Andrea Frittoli's message of 2018-06-26 13:35:11 +0100: > > >

[openstack-dev] [infra] Behavior change in Zuul post pipeline

2018-06-26 Thread James E. Blair
Hi, We recently changed the behavior* of the post pipeline in Zuul to only run jobs for the most recently merged changes on each project's branches. If you were relying on the old behavior where jobs ran on every merged change, let us know, we can make a new pipeline for that. But for the

[openstack-dev] [all][ci][infra] Small network interface MTUs on test nodes

2018-06-26 Thread Clark Boylan
Hello everyone, We now have more than one cloud provider giving us test node resources where we can expect network interfaces to have MTUs less that 1500. This is a side effect of running Neutron with overlay networking in the cloud providing the test resources. Considering we've largely made

Re: [openstack-dev] [tc] [all] TC Report 18-26

2018-06-26 Thread Zane Bitter
On 26/06/18 09:12, Jay Pipes wrote: On 06/26/2018 08:41 AM, Chris Dent wrote: Meanwhile, to continue [last week's theme](/tc-report-18-25.html), the TC's role as listener, mediator, and influencer lacks definition. Zane wrote up a blog post explaining the various ways in which the OpenStack

Re: [openstack-dev] [python3] building tools for the transition

2018-06-26 Thread Doug Hellmann
Excerpts from Doug Hellmann's message of 2018-06-20 11:34:10 -0400: > I want to thank Nguyễn Trí Hải, Ma Lei, and Huang Zhiping for > agreeing to be a part of the goal champion team for the python3 > goal for Stein. > > The next step for us is to build some tools to make the process a > little

Re: [openstack-dev] [tc] [all] TC Report 18-26

2018-06-26 Thread Fox, Kevin M
"What is OpenStack" From: Jay Pipes [jaypi...@gmail.com] Sent: Tuesday, June 26, 2018 6:12 AM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [tc] [all] TC Report 18-26 On 06/26/2018 08:41 AM, Chris Dent wrote: > Meanwhile, to

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Doug Hellmann
Excerpts from Doug Hellmann's message of 2018-06-26 11:19:05 -0400: > 29 out of 40 repos that have "tempest" in the name have not been > tagged via the releases repo. Not all of those are plugins. Here's > a list: > > $ for repo in $(grep openstack/ reference/projects.yaml | grep tempest | > cut

[openstack-dev] [neutron] neutron-lib consumption patches for the Neutron Stadium and networking projects

2018-06-26 Thread Miguel Lavalle
Dear Neutron Community, As we are all aware, over the past few cycles we have been re-homing from Neutron to neutron-lib all the common functionality that is shared with the OpenStack Networking family of projects. In a nutshell, the process is the following: 1. Shared functionality is

Re: [openstack-dev] [kolla] Removing old / unused images

2018-06-26 Thread Andy Smith
Also commented as tripleo is using qdrouterd. It's use in kolla-ansible https://github.com/openstack/kolla-ansible/tree/master/ansible/roles/qdrouterd and bp https://blueprints.launchpad.net/kolla/+spec/dispatch-router-messaging-component Thanks, Andy On Tue, Jun 26, 2018 at 10:52 AM Alex

Re: [openstack-dev] [requirements][stable][docs] updating openstackdocstheme in stable branches

2018-06-26 Thread Matthew Thode
On 18-06-26 09:03:40, Doug Hellmann wrote: > Requirements team, > > At some point in the next few months we're going to want to raise > the constraint on openstackdocstheme in all of the old branches so > we can take advantage of a new feature for showing the supported > status of each version of

Re: [openstack-dev] [requirements][stable][docs] updating openstackdocstheme in stable branches

2018-06-26 Thread Sean McGinnis
> > The theme is released under an independent release model and does > not currently have stable branches. It depends on pbr and dulwich, > both of which should already be in the requirements and constraints > lists (dulwich is a dependency of reno). > > I think that means the simplest thing

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Doug Hellmann
Excerpts from Matthew Treinish's message of 2018-06-26 10:37:54 -0400: > On Tue, Jun 26, 2018 at 10:12:30AM -0400, Doug Hellmann wrote: > > Excerpts from Matthew Treinish's message of 2018-06-26 09:52:09 -0400: > > > On Tue, Jun 26, 2018 at 08:53:21AM -0400, Doug Hellmann wrote: > > > > Excerpts

Re: [openstack-dev] [kolla] Removing old / unused images

2018-06-26 Thread Alex Schultz
On Tue, Jun 26, 2018 at 8:05 AM, Paul Bourke wrote: > Hi all, > > At the weekly meeting a week or two ago, we mentioned removing some old / > unused images from Kolla in the interest of keeping the gate run times down, > as well as general code hygiene. > > The images I've determined that are

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Matthew Treinish
On Tue, Jun 26, 2018 at 10:12:30AM -0400, Doug Hellmann wrote: > Excerpts from Matthew Treinish's message of 2018-06-26 09:52:09 -0400: > > On Tue, Jun 26, 2018 at 08:53:21AM -0400, Doug Hellmann wrote: > > > Excerpts from Andrea Frittoli's message of 2018-06-26 13:35:11 +0100: > > > > On Tue, 26

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

2018-06-26 Thread Vladyslav Drok
On Tue, Jun 26, 2018 at 5:14 PM Vladyslav Drok wrote: > > On Tue, Jun 26, 2018 at 4:58 PM Takashi Yamamoto > wrote: > >> On Tue, Jun 26, 2018 at 10:13 PM, Doug Hellmann >> wrote: >> > Excerpts from Lance Bragstad's message of 2018-06-25 22:51:37 -0500: >> >> Thanks a bunch for digging into

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

2018-06-26 Thread Vladyslav Drok
On Tue, Jun 26, 2018 at 4:58 PM Takashi Yamamoto wrote: > On Tue, Jun 26, 2018 at 10:13 PM, Doug Hellmann > wrote: > > Excerpts from Lance Bragstad's message of 2018-06-25 22:51:37 -0500: > >> Thanks a bunch for digging into this, Tony. I'll follow up with the > >> oauthlib maintainers and see

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

2018-06-26 Thread Lance Bragstad
On 06/26/2018 08:57 AM, Takashi Yamamoto wrote: > On Tue, Jun 26, 2018 at 10:13 PM, Doug Hellmann wrote: >> Excerpts from Lance Bragstad's message of 2018-06-25 22:51:37 -0500: >>> Thanks a bunch for digging into this, Tony. I'll follow up with the >>> oauthlib maintainers and see if they'd be

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Doug Hellmann
Excerpts from Matthew Treinish's message of 2018-06-26 09:52:09 -0400: > On Tue, Jun 26, 2018 at 08:53:21AM -0400, Doug Hellmann wrote: > > Excerpts from Andrea Frittoli's message of 2018-06-26 13:35:11 +0100: > > > On Tue, 26 Jun 2018, 1:08 pm Thierry Carrez, > > > wrote: > > > > > > > Dmitry

[openstack-dev] [kolla] Removing old / unused images

2018-06-26 Thread Paul Bourke
Hi all, At the weekly meeting a week or two ago, we mentioned removing some old / unused images from Kolla in the interest of keeping the gate run times down, as well as general code hygiene. The images I've determined that are either no longer relevant, or were simply never made use of in

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

2018-06-26 Thread Takashi Yamamoto
On Tue, Jun 26, 2018 at 10:13 PM, Doug Hellmann wrote: > Excerpts from Lance Bragstad's message of 2018-06-25 22:51:37 -0500: >> Thanks a bunch for digging into this, Tony. I'll follow up with the >> oauthlib maintainers and see if they'd be interested in these changes >> upstream. If so, I can

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Matthew Treinish
On Tue, Jun 26, 2018 at 08:53:21AM -0400, Doug Hellmann wrote: > Excerpts from Andrea Frittoli's message of 2018-06-26 13:35:11 +0100: > > On Tue, 26 Jun 2018, 1:08 pm Thierry Carrez, wrote: > > > > > Dmitry Tantsur wrote: > > > > [...] > > > > My suggestion: tempest has to be compatible with

[openstack-dev] [nova]Notification update week 26

2018-06-26 Thread Balázs Gibizer
Hi, Here is the latest notification subteam update. Bugs [Undecided] "IndexError: list index out of range" in ExceptionPayload.from_exception during resize failure https://bugs.launchpad.net/nova/+bug/1777540 I failed to reproduce and based on the newly provided logs in the parent bug

Re: [openstack-dev] [all][requirements][docs] sphinx update to 1.7.4 from 1.6.5

2018-06-26 Thread Doug Hellmann
Excerpts from Lance Bragstad's message of 2018-06-25 22:51:37 -0500: > Thanks a bunch for digging into this, Tony. I'll follow up with the > oauthlib maintainers and see if they'd be interested in these changes > upstream. If so, I can chip away at it. For now we'll have to settle for > not

Re: [openstack-dev] [tc] [all] TC Report 18-26

2018-06-26 Thread Jay Pipes
On 06/26/2018 08:41 AM, Chris Dent wrote: Meanwhile, to continue [last week's theme](/tc-report-18-25.html), the TC's role as listener, mediator, and influencer lacks definition. Zane wrote up a blog post explaining the various ways in which the OpenStack Foundation is

[openstack-dev] [requirements][stable][docs] updating openstackdocstheme in stable branches

2018-06-26 Thread Doug Hellmann
Requirements team, At some point in the next few months we're going to want to raise the constraint on openstackdocstheme in all of the old branches so we can take advantage of a new feature for showing the supported status of each version of a project. That feature isn't implemented yet, but I

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Doug Hellmann
Excerpts from Andrea Frittoli's message of 2018-06-26 13:35:11 +0100: > On Tue, 26 Jun 2018, 1:08 pm Thierry Carrez, wrote: > > > Dmitry Tantsur wrote: > > > [...] > > > My suggestion: tempest has to be compatible with all supported releases > > > (of both services and plugins) OR be branched. >

[openstack-dev] [tc] [all] TC Report 18-26

2018-06-26 Thread Chris Dent
HTML: https://anticdent.org/tc-report-18-26.html All the bits and pieces of OpenStack are interconnected and interdependent across the many groupings of technology and people. When we plan or make changes, wiggling something _here_ has consequences over _there_. Some intended, some unintended.

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Andrea Frittoli
On Tue, 26 Jun 2018, 1:08 pm Thierry Carrez, wrote: > Dmitry Tantsur wrote: > > [...] > > My suggestion: tempest has to be compatible with all supported releases > > (of both services and plugins) OR be branched. > > [...] > I tend to agree with Dmitry... We have a model for things that need >

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Thierry Carrez
Dmitry Tantsur wrote: [...] My suggestion: tempest has to be compatible with all supported releases (of both services and plugins) OR be branched. [...] I tend to agree with Dmitry... We have a model for things that need release alignment, and that's the cycle-bound series. The reason tempest

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Mehdi Abaakouk
Hi, I have never understood the branchless tempest thing. Making Tempest release is a great news for me. But about plugins... Tempest already provides a API for plugins. If you are going to break this API, why not using stable branches and deprecation process like any other software ? If you

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Dmitry Tantsur
On 06/26/2018 11:57 AM, Ghanshyam Mann wrote: On Tue, 26 Jun 2018 18:37:42 +0900 Dmitry Tantsur wrote > On 06/26/2018 11:18 AM, Ghanshyam Mann wrote: > > Hello Everyone, > > > > In Queens cycle, community goal to split the Tempest Plugin has been completed [1] and i

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Rabi Mishra
On Tue, Jun 26, 2018 at 2:48 PM, Ghanshyam Mann wrote: > Hello Everyone, > > In Queens cycle, community goal to split the Tempest Plugin has been > completed [1] and i think almost all the projects have separate repo for > tempest plugin [2]. Which means each tempest plugins are being separated

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Luigi Toscano
On Tuesday, 26 June 2018 11:52:53 CEST Ghanshyam Mann wrote: > On Tue, 26 Jun 2018 18:28:03 +0900 Luigi Toscano > wrote > > On Tuesday, 26 June 2018 11:18:52 CEST Ghanshyam Mann wrote: > > > Hello Everyone, > > > > > > In Queens cycle, community goal to split the Tempest Plugin

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Ghanshyam Mann
On Tue, 26 Jun 2018 18:37:42 +0900 Dmitry Tantsur wrote > On 06/26/2018 11:18 AM, Ghanshyam Mann wrote: > > Hello Everyone, > > > > In Queens cycle, community goal to split the Tempest Plugin has been > > completed [1] and i think almost all the projects have separate repo

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Ghanshyam Mann
On Tue, 26 Jun 2018 18:28:03 +0900 Luigi Toscano wrote > On Tuesday, 26 June 2018 11:18:52 CEST Ghanshyam Mann wrote: > > Hello Everyone, > > > > In Queens cycle, community goal to split the Tempest Plugin has been > > completed [1] and i think almost all the projects

Re: [openstack-dev] [cinder] making volume available without stopping VM

2018-06-26 Thread Volodymyr Litovka
Hi Sean, thanks for the responce, my questions and comments below. On 6/25/18 9:42 PM, Sean McGinnis wrote: Not sure if it's an option for you, but in the Pike release support was added to be able to extend attached volumes. There are several caveats with this feature though. I believe it

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Dmitry Tantsur
On 06/26/2018 11:18 AM, Ghanshyam Mann wrote: Hello Everyone, In Queens cycle, community goal to split the Tempest Plugin has been completed [1] and i think almost all the projects have separate repo for tempest plugin [2]. Which means each tempest plugins are being separated from their

Re: [openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Luigi Toscano
On Tuesday, 26 June 2018 11:18:52 CEST Ghanshyam Mann wrote: > Hello Everyone, > > In Queens cycle, community goal to split the Tempest Plugin has been > completed [1] and i think almost all the projects have separate repo for > tempest plugin [2]. Which means each tempest plugins are being

[openstack-dev] [qa][tempest-plugins][release][tc][ptl]: Coordinated Release Model proposal for Tempest & Tempest Plugins

2018-06-26 Thread Ghanshyam Mann
Hello Everyone, In Queens cycle, community goal to split the Tempest Plugin has been completed [1] and i think almost all the projects have separate repo for tempest plugin [2]. Which means each tempest plugins are being separated from their project release model. Few projects have started