Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

2018-01-18 Thread Ghanshyam Mann
On Thu, Jan 18, 2018 at 11:22 PM, Graham Hayes wrote: > On 18/01/18 16:25, Doug Hellmann wrote: >> Excerpts from Graham Hayes's message of 2018-01-18 15:33:12 +: > > > >> >> In the past the QA team agreed to accept trademark-related tests from >> all projects in the tempest

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

2018-01-18 Thread Ghanshyam Mann
On Thu, Jan 11, 2018 at 10:06 PM, Colleen Murphy wrote: > Hi everyone, > > We have governance review under debate[1] that we need the community's help > on. > The debate is over what recommendation the TC should make to the Interop team > on where the tests it uses for the

Re: [openstack-dev] [ResMgmt SIG]Proposal to form Resource Management SIG

2018-01-18 Thread Zhipeng Huang
Feel free to add your name to the wiki :) On Fri, Jan 19, 2018 at 10:14 AM, Alex Xu wrote: > ++, I also want to join this party :) > > 2018-01-09 8:40 GMT+08:00 Zhipeng Huang : > >> Agree 100% to avoid regular meeting and it is better to have bi-weekly

Re: [openstack-dev] [ResMgmt SIG]Proposal to form Resource Management SIG

2018-01-18 Thread Alex Xu
++, I also want to join this party :) 2018-01-09 8:40 GMT+08:00 Zhipeng Huang : > Agree 100% to avoid regular meeting and it is better to have bi-weekly > email report. Meeting should be arranged event based, and I think given the > status of OpenStack community's work on

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

2018-01-18 Thread Ken'ichi Ohmichi
2018-01-18 12:36 GMT-08:00 Doug Hellmann : > Excerpts from Doug Hellmann's message of 2018-01-18 15:21:12 -0500: >> Excerpts from Graham Hayes's message of 2018-01-18 19:25:02 +: >> > >> > On 18/01/18 18:52, Doug Hellmann wrote: >> > > Excerpts from Graham Hayes's

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

2018-01-18 Thread Mathieu Gagné
On Thu, Jan 18, 2018 at 5:19 PM, Jay Pipes wrote: > On 01/18/2018 03:54 PM, Mathieu Gagné wrote: >> >> Hi, >> >> On Tue, Jan 16, 2018 at 4:24 PM, melanie witt wrote: >>> >>> Hello Stackers, >>> >>> This is a heads up to any of you using the

Re: [openstack-dev] [gate][devstack][neutron][qa][release] Switch to lib/neutron in gate

2018-01-18 Thread Ihar Hrachyshka
On Thu, Jan 18, 2018 at 8:33 AM, Michael Johnson wrote: > This sounds great Ihar! > > Let us know when we should make the changes to the neutron-lbaas projects. > > Michael Hi Michael! You can already start, by introducing new service names without q-* for your services.

Re: [openstack-dev] [requirements] requirements-tox-validate-projects FAILURE

2018-01-18 Thread Clark Boylan
On Thu, Jan 18, 2018, at 1:54 PM, Kwan, Louie wrote: > Would like to add the following module to openstack.masakari project > > https://github.com/pytransitions/transitions > > https://review.openstack.org/#/c/534990/ > > requirements-tox-validate-projects failed: > >

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

2018-01-18 Thread Jay Pipes
On 01/18/2018 03:54 PM, Mathieu Gagné wrote: Hi, On Tue, Jan 16, 2018 at 4:24 PM, melanie witt wrote: Hello Stackers, This is a heads up to any of you using the AggregateCoreFilter, AggregateRamFilter, and/or AggregateDiskFilter in the filter scheduler. These filters have

[openstack-dev] [requirements] requirements-tox-validate-projects FAILURE

2018-01-18 Thread Kwan, Louie
Would like to add the following module to openstack.masakari project https://github.com/pytransitions/transitions https://review.openstack.org/#/c/534990/ requirements-tox-validate-projects failed:

Re: [openstack-dev] [ironic] FFE - Requesting FFE for Routed Networks support.

2018-01-18 Thread Harald Jensås
On Wed, 2018-01-17 at 16:05 +0100, Dmitry Tantsur wrote: > Hi! > > I'm essentially +1 on granting this FFE, as it's a low-risk work for > a great  > feature. See one comment inline. > > On 01/17/2018 10:54 AM, Harald Jensås wrote: > > Requesting FFE for Routed Network support in

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

2018-01-18 Thread Mathieu Gagné
Hi, On Tue, Jan 16, 2018 at 4:24 PM, melanie witt wrote: > Hello Stackers, > > This is a heads up to any of you using the AggregateCoreFilter, > AggregateRamFilter, and/or AggregateDiskFilter in the filter scheduler. > These filters have effectively allowed operators to set

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

2018-01-18 Thread Jay Pipes
On 01/18/2018 03:06 PM, Logan V. wrote: We have used aggregate based scheduler filters since deploying our cloud in Kilo. This explains the unpredictable scheduling we have seen since upgrading to Ocata. Before this post, was there some indication I missed that these filters can no longer be

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

2018-01-18 Thread Doug Hellmann
Excerpts from Doug Hellmann's message of 2018-01-18 15:21:12 -0500: > Excerpts from Graham Hayes's message of 2018-01-18 19:25:02 +: > > > > On 18/01/18 18:52, Doug Hellmann wrote: > > > Excerpts from Graham Hayes's message of 2018-01-18 17:52:39 +: > > >> On 18/01/18 16:25, Doug Hellmann

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

2018-01-18 Thread Doug Hellmann
Excerpts from Graham Hayes's message of 2018-01-18 19:25:02 +: > > On 18/01/18 18:52, Doug Hellmann wrote: > > Excerpts from Graham Hayes's message of 2018-01-18 17:52:39 +: > >> On 18/01/18 16:25, Doug Hellmann wrote: > >>> Excerpts from Graham Hayes's message of 2018-01-18 15:33:12

Re: [openstack-dev] [nova] heads up to users of Aggregate[Core|Ram|Disk]Filter: behavior change in >= Ocata

2018-01-18 Thread Logan V.
We have used aggregate based scheduler filters since deploying our cloud in Kilo. This explains the unpredictable scheduling we have seen since upgrading to Ocata. Before this post, was there some indication I missed that these filters can no longer be used? Even now reading the Ocata release

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

2018-01-18 Thread Graham Hayes
On 18/01/18 18:52, Doug Hellmann wrote: > Excerpts from Graham Hayes's message of 2018-01-18 17:52:39 +: >> On 18/01/18 16:25, Doug Hellmann wrote: >>> Excerpts from Graham Hayes's message of 2018-01-18 15:33:12 +: >> >> >> >>> >>> In the past the QA team agreed to accept

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

2018-01-18 Thread Doug Hellmann
Excerpts from Graham Hayes's message of 2018-01-18 17:52:39 +: > On 18/01/18 16:25, Doug Hellmann wrote: > > Excerpts from Graham Hayes's message of 2018-01-18 15:33:12 +: > > > > > > > In the past the QA team agreed to accept trademark-related tests from > > all projects in the

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

2018-01-18 Thread Graham Hayes
On 18/01/18 16:25, Doug Hellmann wrote: > Excerpts from Graham Hayes's message of 2018-01-18 15:33:12 +: > > In the past the QA team agreed to accept trademark-related tests from > all projects in the tempest repo. Has that changed? > There has not been an explict rejection but in all

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

2018-01-18 Thread Doug Hellmann
Excerpts from Doug Hellmann's message of 2018-01-18 11:45:28 -0500: > Excerpts from Saverio Proto's message of 2018-01-18 14:49:21 +0100: > > Hello all, > > > > well this oslo.log library looks like a core thing that is used by > > multiple projects. I feel scared hearing that bugs opened on that

Re: [openstack-dev] [ptg] Dublin PTG proposed track schedule

2018-01-18 Thread Emilien Macchi
On Thu, Jan 18, 2018 at 2:20 AM, Thierry Carrez wrote: [...] > We'd like to publish this schedule on the event website ASAP, so please > check that it still matches your needs (number of days, room size vs. > expected attendance) and does not create too many conflicts.

Re: [openstack-dev] [kuryr] Rocky PTG planning

2018-01-18 Thread Daniel Mellado
On 01/18/2018 05:49 PM, Daniel Mellado wrote: > Hi everyone! > > Unlike winter, PTG is coming! I've created an etherpad to track the > topics and attendees, so please add your attendance information in the > there. > > Besides work items, maybe we can also use it to try to organize some > kind

[openstack-dev] [kuryr] Rocky PTG planning

2018-01-18 Thread Daniel Mellado
Hi everyone! Unlike winter, PTG is coming! I've created an etherpad to track the topics and attendees, so please add your attendance information in the there. Besides work items, maybe we can also use it to try to organize some kind of social event in Dublin. Looking forward to see you all

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

2018-01-18 Thread Doug Hellmann
Excerpts from Saverio Proto's message of 2018-01-18 14:49:21 +0100: > Hello all, > > well this oslo.log library looks like a core thing that is used by > multiple projects. I feel scared hearing that bugs opened on that > project are probably just ignored. > > should I reach out to the current

[openstack-dev] [all][api] POST /api-sig/news

2018-01-18 Thread Ed Leafe
Greetings OpenStack community, A very quiet meeting today [7], which you would expect with the absence of cdent and elmiko. The main discussion was about the guideline on exposing microversions in SDKs [8] by dtantsur. The focus of the discussion was about how to handle the distinction between

Re: [openstack-dev] [gate][devstack][neutron][qa][release] Switch to lib/neutron in gate

2018-01-18 Thread Michael Johnson
This sounds great Ihar! Let us know when we should make the changes to the neutron-lbaas projects. Michael On Wed, Jan 17, 2018 at 11:26 AM, Ihar Hrachyshka wrote: > Hi all, > > tl;dr I propose to switch to lib/neutron devstack library in Queens. I > ask for buy-in to the

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

2018-01-18 Thread Doug Hellmann
Excerpts from Graham Hayes's message of 2018-01-18 15:33:12 +: > I had hoped for more of a discussion on this before I jumped back into > this debate - but it seams to be stalled still, so here it goes. > > I proposed this initially as we were unclear on where the tests should > go - we had

[openstack-dev] [glance] priorities for the coming week (18 Jan - 24 Jan)

2018-01-18 Thread Brian Rosmaita
As discussed at today's Glance meeting, the Q-3 milestone is next week. Please focus on the following: (1) image metadata injection https://review.openstack.org/#/c/527635/ (2) interoperable image import https://review.openstack.org/532502 https://review.openstack.org/532501 may be some more,

Re: [openstack-dev] [ptg] Dublin PTG proposed track schedule

2018-01-18 Thread Matthew Thode
On 18-01-18 11:20:21, Thierry Carrez wrote: > Hi everyone, > > Here is the proposed pre-allocated track schedule for the Dublin PTG: > > https://docs.google.com/spreadsheets/d/e/2PACX-1vRmqAAQZA1rIzlNJpVp-X60-z6jMn_95BKWtf0csGT9LkDharY-mppI25KjiuRasmK413MxXcoSU7ki/pubhtml?gid=1374855307=true >

Re: [openstack-dev] Many timeouts in zuul gates for TripleO

2018-01-18 Thread Emilien Macchi
On Thu, Jan 18, 2018 at 6:34 AM, Or Idgar wrote: > Hi, > we're encountering many timeouts for zuul gates in TripleO. > For example, see > http://logs.openstack.org/95/508195/28/check-tripleo/tripleo-ci-centos-7-ovb-ha-oooq/c85fcb7/. > > rechecks won't help and sometimes

Re: [openstack-dev] [release] Release countdown for week R-5, January 20 - 26

2018-01-18 Thread Sean McGinnis
On Thu, Jan 18, 2018 at 08:56:55AM -0600, Sean McGinnis wrote: > Development Focus > - > > Teams should be focused on implementing planned work. Work should be wrapping > up on client libraries to meet the client lib deadline Thursday, the 25th. > > General Information >

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

2018-01-18 Thread Graham Hayes
On 11/01/18 16:36, Colleen Murphy wrote: > Hi everyone, > > We have governance review under debate[1] that we need the community's help > on. > The debate is over what recommendation the TC should make to the Interop team > on where the tests it uses for the OpenStack trademark program should

[openstack-dev] [cliff][osc][barbican][oslo][sdk][all] avoiding option name conflicts with cliff and OSC plugins

2018-01-18 Thread Doug Hellmann
We've been working this week to resolve an issue between cliff and barbicanclient due to a collision in the option namespace [0]. Barbicanclient was using the -s option, and then cliff's lister command base class added that option as an alias for sort-columns. The first attempt at resolving the

[openstack-dev] [release] Release countdown for week R-5, January 20 - 26

2018-01-18 Thread Sean McGinnis
Development Focus - Teams should be focused on implementing planned work. Work should be wrapping up on client libraries to meet the client lib deadline Thursday, the 25th. General Information --- Next Thursday is the final client library release. Releases will

Re: [openstack-dev] [all][tc] Clarifying testing recommendation for interop programs

2018-01-18 Thread Graham Hayes
On 12/01/18 09:49, Luigi Toscano wrote: > On Thursday, 11 January 2018 23:52:00 CET Matt Riedemann wrote: >> On 1/11/2018 10:36 AM, Colleen Murphy wrote: >>> 1) All trademark-related tests should go in the tempest repo, in >>> accordance >>> >>> with the original resolution. This would mean

[openstack-dev] [designate] Meeting Next Week + Other Highlights

2018-01-18 Thread Graham Hayes
Hi All, I am going to be on vacation next week, and will not be able to run the weekly IRC meeting. We can either skip, or if someone steps up to run it we can go ahead. I will be around enough to do the q3 release. Also a reminder that the etherpad for planning the PTG in Dublin is available

Re: [openstack-dev] [security] Won't be able to make todays meeting

2018-01-18 Thread Jeremy Stanley
On 2018-01-18 10:05:19 + (+), Luke Hinds wrote: > I won't be able to attend the security project meeting today, and as there > are no hot topics I suggest we postpone until next week (if there are, then > feel free to #startmeeting and I will catch up tomorrow through meetbot > logs).

[openstack-dev] Many timeouts in zuul gates for TripleO

2018-01-18 Thread Or Idgar
Hi, we're encountering many timeouts for zuul gates in TripleO. For example, see http://logs.openstack.org/95/508195/28/check-tripleo/tripleo-ci-centos-7-ovb-ha-oooq/c85fcb7/ . rechecks won't help and sometimes specific gate is end successfully and sometimes not. The problem is that after recheck

Re: [openstack-dev] [keystone] adding Gage Hugo to keystone core

2018-01-18 Thread Rodrigo Duarte
Congrats, Gage. Well deserved! On Tue, Jan 16, 2018 at 6:16 PM, Harry Rybacki wrote: > +100 -- congratulations, Gage! > > > On Tue, Jan 16, 2018 at 2:24 PM, Raildo Mascena de Sousa Filho < > rmasc...@redhat.com> wrote: > >> +1 >> >> Congrats Gage, very well deserved! >> >>

[openstack-dev] [craton] Retirement of craton and python-cratonclient

2018-01-18 Thread Andreas Jaeger
Craton development is frozen since around March 2017, I've discussed with Sulochan and will start the retirement process now, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

2018-01-18 Thread Saverio Proto
Hello all, well this oslo.log library looks like a core thing that is used by multiple projects. I feel scared hearing that bugs opened on that project are probably just ignored. should I reach out to the current PTL of OSLO ?

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

2018-01-18 Thread Sean Dague
A bug would be fine. I'm not sure how many people are keeping an eye on oslo.log bugs at this point, so be realistic in when it might get looked at. On 01/18/2018 03:06 AM, Saverio Proto wrote: > Hello Sean, > after the brief chat we had on IRC, do you think I should open a bug > about this issue

Re: [openstack-dev] [neutron][l2gw] Preventing DB out-of-sync

2018-01-18 Thread Ricardo Noriega De Soto
Just for awareness on this subject. Peng has proposed an initial patch to tackle this issue: https://review.openstack.org/#/c/529009/6 On Tue, Dec 12, 2017 at 11:20 AM, Ricardo Noriega De Soto < rnori...@redhat.com> wrote: > Peng, I think you are right. We should have a common behavior among

Re: [openstack-dev] [QA] [all] QA Rocky PTG Planning

2018-01-18 Thread Andrea Frittoli
and the link [1] [1] https://etherpad.openstack.org/p/qa-rocky-ptg On Thu, Jan 18, 2018 at 10:28 AM Andrea Frittoli wrote: > Dear all, > > I started the etherpad for planning the QA work in Dublin. > Please add your ideas / proposals for sessions and intention of

[openstack-dev] [QA] [all] QA Rocky PTG Planning

2018-01-18 Thread Andrea Frittoli
Dear all, I started the etherpad for planning the QA work in Dublin. Please add your ideas / proposals for sessions and intention of attending. We have a room for the QA team for three full days Wed-Fri. This time I also included a "Request for Sessions" - if anyone would like to discuss a QA

[openstack-dev] [ptg] Dublin PTG proposed track schedule

2018-01-18 Thread Thierry Carrez
Hi everyone, Here is the proposed pre-allocated track schedule for the Dublin PTG: https://docs.google.com/spreadsheets/d/e/2PACX-1vRmqAAQZA1rIzlNJpVp-X60-z6jMn_95BKWtf0csGT9LkDharY-mppI25KjiuRasmK413MxXcoSU7ki/pubhtml?gid=1374855307=true The proposed allocation takes into account the estimated

[openstack-dev] [api-wg] [api] [cinder] [nova] Support specify action name in request url

2018-01-18 Thread TommyLike Hu
Hey all, Recently We found an issue related to our OpenStack action APIs. We usually expose our OpenStack APIs by registering them to our API Gateway (for instance Kong [1]), but it becomes very difficult when regarding to action APIs. We can not register and control them seperately because

[openstack-dev] [security] Won't be able to make todays meeting

2018-01-18 Thread Luke Hinds
Hello, I won't be able to attend the security project meeting today, and as there are no hot topics I suggest we postpone until next week (if there are, then feel free to #startmeeting and I will catch up tomorrow through meetbot logs). Cheers, Luke

Re: [openstack-dev] [tripleo] Ocata to Pike upgrade job is working as of today.

2018-01-18 Thread Javier Pena
- Original Message - > Hi, > > So join us (upgrade squad) to celebrate the working ocata->pike upgrade > job[1], without any depends-on whatsoever. > > We would like it to be voting as soon as possible. It has been a > rather consuming task to revive that forgotten but important jobs,

[openstack-dev] [nova] about rebuild instance booted from volume

2018-01-18 Thread 李杰
Hi,all This is the spec about rebuild a instance booted from volume, anyone who is interested in booted from volume can help to review this. Any suggestion is welcome. The link is here. Re:the rebuild spec:https://review.openstack.org/#/c/532407/

Re: [openstack-dev] [tc][masakari][api] masakari service-type, docs, api-ref and releasenotes

2018-01-18 Thread Sam P
Hi Monty, Thanks for the patches. Agree that 'ha' is a pretty broad service-type for Masakari. compute-ha or instance-ha are both OK, as Andreas proposed, I would like to change it to instance-ha. If no objections, I will fix the python-masakariclient, devstack pulgin etc.. from masakari

Re: [openstack-dev] [oslo][oslo.log] JSON logs are missing the request ID

2018-01-18 Thread Saverio Proto
Hello Sean, after the brief chat we had on IRC, do you think I should open a bug about this issue ? thank you Saverio On 13.01.18 07:06, Saverio Proto wrote: >> I don't think this is a configuration problem. >> >> Which version of the oslo.log library do you have installed? > > Hello Doug, >