Re: [openstack-dev] [oslo] pbr and warnerrors status

2017-02-07 Thread Andreas Jaeger
On 2017-02-08 00:56, Ian Cordasco wrote: > > > On Feb 7, 2017 5:47 PM, "Joshua Harlow" > wrote: > > Likely just never pulled the trigger. > > Seems like we should pull it though. > > > > Will have to wait until Pike given the

[openstack-dev] [tripleo] Blueprints for DPDK in OvS2.6

2017-02-07 Thread Saravanan KR
Hello, We have raised 2 BP for OvS2.6 integration with DPDK support. Basic Migration - https://blueprints.launchpad.net/tripleo/+spec/ovs-2.6-dpdk (Targeted for March) OvS 2.6 Features - https://blueprints.launchpad.net/tripleo/+spec/ovs-2.6-features-dpdk (Targeted for Pike) We find the changes

Re: [openstack-dev] [neutron][taas] ocata

2017-02-07 Thread Soichi Shigeta
Hi Yamamoto, We discussed this on today's IRC and agreed to make an ocata release. Best regards, Soichi tap-as-a-service folks, unless anyone objects, i'll make a ocata release and thus stable branch this week. (otherwise the CI of consuming subprojects will break)

[openstack-dev] [tricircle]weekly meeting of Feb. 8

2017-02-07 Thread joehuang
Hello, team, Let's resume weekly meeting after breaks for Chinese New Year. Agenda of Feb. 8 weekly meeting: 1. Ocata release dates 2. Pike meetup before PTG: https://etherpad.openstack.org/p/tricircle-pike-design-topics 3. Representative and topics to PTG 4. Open Discussion How

[openstack-dev] [Blazar] bug list before next release

2017-02-07 Thread Masahito MUROI
Hello Blazar folks, I listed all tasks needed to do by 0.2.0 release. Let's pick up bugs and don't forget to add you as an Assignee. https://launchpad.net/blazar/+milestone/0.2.0 best regards, Masahito __ OpenStack

Re: [openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

2017-02-07 Thread ChangBo Guo
Thanks Doug and amoralej, we should avoid this :(. One more thought about mox3: Is it used outside of OpenStack? If yes, Maybe we can retire mox3 if all projects move mox to mock. 2017-02-07 23:00 GMT+08:00 Doug Hellmann : > The stable/ocata branch for mox3 was created

Re: [openstack-dev] Refstack - final mascot

2017-02-07 Thread Rochelle Grober
Looks great to me. --Rocky From: Catherine Cuong Diep [mailto:cd...@us.ibm.com] Sent: Monday, February 06, 2017 4:25 PM To: OpenStack Dev Mailer Subject: [openstack-dev] Refstack - final mascot Hello RefStack team, Please see RefStack mascot in Heidi's note

[openstack-dev] [tricircle]Ocata branch creation

2017-02-07 Thread joehuang
Hello, Tricircle Ocata branch will be created after these two patches are merged before this Friday: 1. https://review.openstack.org/#/c/429457/ 2. https://review.openstack.org/#/c/424601/ Best Regards Chaoyi Huang (joehuang)

Re: [openstack-dev] [tricircle] Example EVPN question/use-case

2017-02-07 Thread joehuang
Hello, Curtis and Greg, This is a quite good use case. Thanks for the sharing. Tricircle is working on VxLAN based L2 network across OpenStack clouds for different backends (non-SDN, SDN, L2 GW or non L2 GW). The spec is in review: https://review.openstack.org/#/c/429155/. Currently only SDN

Re: [openstack-dev] [requirements] [Horizon][Karbor][Magnum] Requesting FFE for xstatic packages

2017-02-07 Thread Richard Jones
It looks like Magnum-UI only has one xstatic package in their requirements that isn't already in Horizon's requirements (and therefore is superfluous), and that's xstatic-magic-search, which has been replaced in Horizon by pulling magic search into the Horizon tree (we forked because maintaining

[openstack-dev] [all][elections] Project Team Lead Election Conclusion and Results

2017-02-07 Thread Kendall Nelson
Thank you to the electorate, to all those who voted and to all candidates who put their name forward for Project Team Lead (PTL) in this election. A healthy, open process breeds trust in our decision making capability thank you to all those who make this process possible. Now for the results of

Re: [openstack-dev] [oslo] pbr and warnerrors status

2017-02-07 Thread Ian Cordasco
On Feb 7, 2017 5:47 PM, "Joshua Harlow" wrote: Likely just never pulled the trigger. Seems like we should pull it though. Will have to wait until Pike given the library release freeze __ OpenStack

Re: [openstack-dev] [oslo] pbr and warnerrors status

2017-02-07 Thread Joshua Harlow
Likely just never pulled the trigger. Seems like we should pull it though. -Josh Ben Nemec wrote: Someone just spent a bunch of effort fixing all the warnings in our docs project and I'd like to turn on warnerrors so we keep it that way. Unfortunately, I discovered that warnerrors is still

[openstack-dev] [oslo] pbr and warnerrors status

2017-02-07 Thread Ben Nemec
Someone just spent a bunch of effort fixing all the warnings in our docs project and I'd like to turn on warnerrors so we keep it that way. Unfortunately, I discovered that warnerrors is still not effective in setup.cfg. After digging a little more, I see we never released pbr after the

[openstack-dev] [tacker] Tacker Mascot

2017-02-07 Thread Sridhar Ramaswamy
Tackers, I received a draft version of our project logo, using the mascot we selected together. A final version will be ready for us before the Project Team Gathering in February. Before they make our logo final, they want to be sure we're happy with our mascot. Let me know if anyone have

[openstack-dev] [fuel][release] Opting out of Ocata?

2017-02-07 Thread Davanum Srinivas
Dear Fuel Team, There have been no releases for fuel-* projects in the Ocata time frame: https://git.openstack.org/cgit/openstack/releases/tree/deliverables/ocata Fuel projects under governance are supposed to be following the "cycle-trailing" schedule:

[openstack-dev] [manila] manila 4.0.0.0rc1 (ocata)

2017-02-07 Thread no-reply
Hello everyone, A new release candidate for manila for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/manila/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally

[openstack-dev] [Congress] PTG Activities options

2017-02-07 Thread Tim Hinrichs
Hi all, At the last IRC I volunteered to pick out a couple of group activities for the upcoming PTG. First cut is below. I could imagine dinner, an outing, or both. Restaurants --- Two options jumped out at me. If neither of these seems good I can keep looking. 1. Desta

Re: [openstack-dev] [all][api] POST /api-wg/news

2017-02-07 Thread Everett Toews
On Feb 6, 2017, at 3:28 PM, Ken'ichi Ohmichi > wrote: 2017-02-06 6:45 GMT-08:00 Brian Rosmaita >: On 2/6/17 5:51 AM, Jordan Pittier wrote: [super-enormous snip -- Chris, Ken, and

Re: [openstack-dev] [all][api] POST /api-wg/news

2017-02-07 Thread Ken'ichi Ohmichi
2017-02-07 10:31 GMT-08:00 Ed Leafe : > On Feb 6, 2017, at 3:28 PM, Ken'ichi Ohmichi wrote: >> >>> To summarize, my point is that we shouldn't be worried that this case is >>> going to set a precedent. It would be worrisome if it were going to set >>> a

Re: [openstack-dev] [all][api] POST /api-wg/news

2017-02-07 Thread Ken'ichi Ohmichi
2017-02-07 6:56 GMT-08:00 Brian Rosmaita : > On 2/6/17 4:28 PM, Ken'ichi Ohmichi wrote: >> 2017-02-06 6:45 GMT-08:00 Brian Rosmaita : >>> On 2/6/17 5:51 AM, Jordan Pittier wrote: >>> [super-enormous snip -- Chris, Ken, and Jordan make good

[openstack-dev] DEADLINE EXTENDED––CFP for Openstack Summit Boston

2017-02-07 Thread Erin Disney
Huge thanks to everyone who has already submitted presentations for the upcoming OpenStack Summit in Boston. Great news for those that missed the deadline last night––we will now be accepting submissions until February 8th at 11:59pm PST (February 9th at 7:59 UTC)! You can submit/edit

Re: [openstack-dev] [all][api] POST /api-wg/news

2017-02-07 Thread Ed Leafe
On Feb 6, 2017, at 3:28 PM, Ken'ichi Ohmichi wrote: > >> To summarize, my point is that we shouldn't be worried that this case is >> going to set a precedent. It would be worrisome if it were going to set >> a *bad* precedent, but when you look at the details of the

[openstack-dev] [tricircle] Example EVPN question/use-case

2017-02-07 Thread Curtis
Hi, I'm not sure if this is useful at all, but there is a blog post [1] from one of the people behind the PacketPushers podcast regarding connecting two OpenStack clouds with a EVPN. They are wondering how to do it. They want to connect an NSX based cloud with a OpenContrail based cloud and do

Re: [openstack-dev] [release] Support phase clarification

2017-02-07 Thread Andreas Jaeger
On 2017-02-07 18:52, Jay S Bryant wrote: > > On 2/7/2017 11:41 AM, Sean McGinnis wrote: >> Just looking for clarification on our support phase timing now with the >> shorter release cycle for Ocata. >> >> According to our published support phase schedule [1], each phase is in >> 6 month

Re: [openstack-dev] [release] Support phase clarification

2017-02-07 Thread Jay S Bryant
On 2/7/2017 11:41 AM, Sean McGinnis wrote: Just looking for clarification on our support phase timing now with the shorter release cycle for Ocata. According to our published support phase schedule [1], each phase is in 6 month increments from the release date. In the past, this had lined up

[openstack-dev] [release] Support phase clarification

2017-02-07 Thread Sean McGinnis
Just looking for clarification on our support phase timing now with the shorter release cycle for Ocata. According to our published support phase schedule [1], each phase is in 6 month increments from the release date. In the past, this had lined up nicely so that when N was release, N-1 and N-2

[openstack-dev] [kuryr] Resource management videoconf meeting

2017-02-07 Thread Antoni Segura Puimedon
Hi all, In the last weekly IRC meeting it was agreed to hold a videoconf meeting about resource management. For those unaware, the topic revolves around the reutilization of Neutron resources like ports and subports as well and virtual devices like veths. This allows for things like batching

[openstack-dev] [PWG] mid-cycle venue option

2017-02-07 Thread Arkady.Kanevsky
Team, I finally checked on my side for the venue. The address of my available venue is Company: Dell Street: Viale Piero e Alberto Pirelli 6 City: Milano That is about 15 min drive or 20 min on public transport from coworking place. I reserved 2 conf rooms for mon-tue. While on Tue you'll

[openstack-dev] [ux] Poll for next team meeting

2017-02-07 Thread Shamail Tahir
Hi everyone, Per the discussion on the dev mailing list last week[1], I am sending out a poll to determine when the UX working group should meet. Please indicate your time preference(s) in the poll if you are interested in participating in the OpenStack UX efforts. Agenda will be sent out after

Re: [openstack-dev] [nova][ceilometer][postgresql][gate][telemetry] PostgreSQL gate failure (again)

2017-02-07 Thread Chris Friesen
On 02/07/2017 07:09 AM, Rui Chen wrote: Actually, some users used postgresql in production deployment(8%), the following photo extract from user survey report of April 2016. Technically the 8% includes both production (4%) as well as dev/QA (3%), and proof-of-concept (1%). Chris

Re: [openstack-dev] [nova] Config option cleanup burndown

2017-02-07 Thread Szankin, Maciej
On 2/7/17, 4:18 AM, "Markus Zoeller" wrote: >On 03.02.2017 21:37, Szankin, Maciej wrote: >> On 2/3/17 2:26 PM, Singh, Sarafraj wrote: >>> Matt, >>> This chart is quite accurate. We are almost finished with this work. We >>> have ~10 outstanding patches that did

Re: [openstack-dev] [nova] Nova API sub-team meeting

2017-02-07 Thread Matt Riedemann
On 2/7/2017 8:14 AM, Alex Xu wrote: Hi, We have weekly Nova API meeting tomorrow. And it is the time to talk about the plan of Pike. I created an etherpad for Pike ideas https://etherpad.openstack.org/p/nova-api-pike, please free feel to add ideas and comments. Thanks. I've added some things

Re: [openstack-dev] [FFE][requirements][murano][murano-pkg-check]pdate constraint for murano-pkg-check to new release 0.3.0

2017-02-07 Thread Jeffrey Zhang
upper-constraints.txt is enough. let merge the following patch in the next cycle. thanks tonyb. On Tue, Feb 7, 2017 at 1:46 PM, Tony Breeds wrote: > On Tue, Feb 07, 2017 at 11:32:28AM +0800, Rong Zhu wrote: > > The Bot Gerrit link is:

[openstack-dev] [puppet] No meeting Feb 7, 2017, next meeting Feb 14, 2017

2017-02-07 Thread Alex Schultz
Hey all, The agenda etherpad[0] was empty so we're skipping today's meeting. The next meeting will be on Feb 14th, 2017. If you have something to discuss, please add it to the agenda etherpad[1]. Thanks, -Alex [0] https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20170207 [1

[openstack-dev] [release][oslo] recreating the stable/ocata branch for mox3

2017-02-07 Thread Doug Hellmann
The stable/ocata branch for mox3 was created from 0.19.0 and then 0.20.0 was released from master. Because that repository sees a very low rate of changes, and because the current stable/ocata branch only contained the patch to update the .gitreview file, we decided to recreate the branch to

Re: [openstack-dev] [nova] Next notification meeting on 02.14.

2017-02-07 Thread Matt Riedemann
On 2/7/2017 7:40 AM, Balazs Gibizer wrote: Hi, As we agreed last week's meeting there won't be meeting this week. The next notification subteam meeting will be held on 2017.02.14 17:00 UTC [1] on #openstack-meeting-4. Cheers, gibi [1]

Re: [openstack-dev] [all][api] POST /api-wg/news

2017-02-07 Thread Brian Rosmaita
On 2/6/17 4:28 PM, Ken'ichi Ohmichi wrote: > 2017-02-06 6:45 GMT-08:00 Brian Rosmaita : >> On 2/6/17 5:51 AM, Jordan Pittier wrote: >> [super-enormous snip -- Chris, Ken, and Jordan make good points, I >> encourage you to read the entire thread; I just want to

Re: [openstack-dev] [QA] Announcing my candidacy for PTL of the Pike cycle

2017-02-07 Thread Rodrigo Duarte
On Tue, Feb 7, 2017 at 7:34 AM, Andrea Frittoli wrote: > > On Tue, Feb 7, 2017 at 1:55 AM Ghanshyam Mann > wrote: > >> Hi Jordan, >> >> Thanks for bring it up. I know we had both side of argument on those >> changes. >> >> IMO in general, its

[openstack-dev] [nova] Nova API sub-team meeting

2017-02-07 Thread Alex Xu
Hi, We have weekly Nova API meeting tomorrow. And it is the time to talk about the plan of Pike. I created an etherpad for Pike ideas https://etherpad.openstack.org/p/nova-api-pike, please free feel to add ideas and comments. The meeting is being held Wednesday UTC1300 and irc channel is

Re: [openstack-dev] [ansible]Octavia ansible script

2017-02-07 Thread Major Hayden
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 02/07/2017 12:00 AM, Santhosh Fernandes wrote: > Can we know the status of octavia ansible script ? > > Link :- https://blueprints.launchpad.net/~german-eichberger > > > Is there any

[openstack-dev] [nova] Next notification meeting on 02.14.

2017-02-07 Thread Balazs Gibizer
Hi, As we agreed last week's meeting there won't be meeting this week. The next notification subteam meeting will be held on 2017.02.14 17:00 UTC [1] on #openstack-meeting-4. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170214T17

Re: [openstack-dev] [Oslo][all] Pike PTG idea & discussion

2017-02-07 Thread Sean McGinnis
On Mon, Feb 06, 2017 at 01:48:59PM -0600, Lance Bragstad wrote: > Not sure how much time it would require at the PTG - but I'd really like to > discuss the ability to add in-code descriptions of oslo.policy objects, and > eventually whatever we need to advertise new defaults. I'm hoping this will

Re: [openstack-dev] [tripleo][ui] Now with translations :)

2017-02-07 Thread Julie Pichon
On 6 February 2017 at 16:03, Ben Nemec wrote: > On 02/06/2017 05:38 AM, Julie Pichon wrote: >> >> Hi folks, >> >> You may have noticed a new type of patch in our queue this morning >> [1]. There's a nice link in the commit message [2][3] that describes >> what to do with

Re: [openstack-dev] [QA] Announcing my candidacy for PTL of the Pike cycle

2017-02-07 Thread Andrea Frittoli
On Tue, Feb 7, 2017 at 1:55 AM Ghanshyam Mann wrote: > Hi Jordan, > > Thanks for bring it up. I know we had both side of argument on those > changes. > > IMO in general, its all QA team responsibility to verify the requirement > very strictly and make sure no changes

Re: [openstack-dev] [nova] Config option cleanup burndown

2017-02-07 Thread Markus Zoeller
On 03.02.2017 21:37, Szankin, Maciej wrote: > On 2/3/17 2:26 PM, Singh, Sarafraj wrote: >> Matt, >> This chart is quite accurate. We are almost finished with this work. We have >> ~10 outstanding patches that did not land in Ocata. There are few more >> TODO’s left in the code to clean up and

Re: [openstack-dev] [telemetry][panko] status of pankoclient

2017-02-07 Thread Julien Danjou
On Tue, Feb 07 2017, Sheng Liu wrote: Hi, > As we have moved events related APIs to Panko and deprecated Ceilometer's > API, the Panko will be the unique entry of event data. But I cannot find > pankoclient in git.openstack.org and launchpad, instead, there is a > pankoclient package in Pypi[1].

Re: [openstack-dev] [cinder] cinder 10.0.0.0rc1 (ocata)

2017-02-07 Thread Dulko, Michal
Hi, With Cinder master being open for Pike development I ask not to merge any changes with DB schema migrations before sanity check migration [1] gets in. It's supposed to block going forward until all of the Ocata's data migrations were executed and should be the first migration in Pike. [1]