Re: [openstack-dev] [neutron] proposing Miguel Lavalle as neutron core and Brian Haley as L3 Lt

+1! On Fri, Dec 16, 2016 at 11:05 AM, Andreas Scheuring < scheu...@linux.vnet.ibm.com> wrote: > +1 > -- > - > Andreas > IRC: andreas_s > > > > On Fr, 2016-12-16 at 00:14 +0100, Armando M. wrote: > > Hi neutrinos, > > > > > > Miguel Lavalle has been driving the project forward consistently

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

+1 On Fri, Dec 16, 2016 at 10:04 AM, reedip banerjee wrote: > +1 for both Ryan and Nate :) > > On Fri, Dec 16, 2016 at 10:03 AM, Vikram Choudhary > wrote: > >> +1 for Ryan! >> >> On Dec 16, 2016 7:23 AM, "Sridar Kandaswamy (skandasw)" < >>

Re: [openstack-dev] [neutron] proposing Miguel Lavalle as neutron core and Brian Haley as L3 Lt

+1 -- - Andreas IRC: andreas_s On Fr, 2016-12-16 at 00:14 +0100, Armando M. wrote: > Hi neutrinos, > > > Miguel Lavalle has been driving the project forward consistently and > reliably. I would like to propose him to be entrusted with +2/+A > rights in the areas he's been most prolific,

Re: [openstack-dev] [neutron] Proposing Abhishek Raut as neutronclient core

Congrats Abhishek ... On Fri, Dec 16, 2016 at 6:42 AM, Abhishek Raut wrote: > Thank you! > > From: "Armando M." > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: Thursday, December 15,

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

+1 for both Ryan and Nate :) On Fri, Dec 16, 2016 at 10:03 AM, Vikram Choudhary wrote: > +1 for Ryan! > > On Dec 16, 2016 7:23 AM, "Sridar Kandaswamy (skandasw)" < > skand...@cisco.com> wrote: > >> +1. From the neutron-fwaas perspective, Nate has been instrumental in >>

[openstack-dev] [meteos] Meteos Released !!

Hi all, I'm pleased to announce the release of Meteos. Meteos is Machine Learning as a Service (MLaaS) in Apache Spark. Meteos allows users to analyze huge amount of data and predict a value by data mining and machine learning algorithms. Meteos create a workspace of Machine Learning via

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

+1 for Ryan! On Dec 16, 2016 7:23 AM, "Sridar Kandaswamy (skandasw)" wrote: > +1. From the neutron-fwaas perspective, Nate has been instrumental in > driving our integration with neutron on the agent extension framework, > neutron-lib as well as on CI. > > Thanks > > Sridar

[openstack-dev] [Horizon] Weekly wrap-up

Hi folks, No Horizon meeting next week! I'll be around the week after (28th December) so if anyone else is around we can totally have a meeting then. Things that have happened this week, including in the team meeting[1] Ocata-2 was tagged! xstatic-angular-bootstrap 2.2.0.0 was released, which

Re: [openstack-dev] [OpenStack-Infra] [all][stable][ptls] Tagging liberty as EOL

On Thu, Dec 15, 2016 at 04:02:41PM +1100, Joshua Hesketh wrote: > On Thu, Dec 15, 2016 at 12:48 AM, Ian Cordasco > wrote: > > > -Original Message- > > From: Joshua Hesketh > > Reply: OpenStack Development Mailing List (not for usage

[openstack-dev] [nova] Upgrade readiness check notes

A few of us have talked about writing a command to tell when you're ready to upgrade (restart services with new code) for Ocata because we have a few things landing in Ocata which are going from optional to required, namely cells v2 and the placement API service. We already have the 030 API

Re: [openstack-dev] [OpenStack-Infra] [all][stable][ptls] Tagging liberty as EOL

On Wed, Dec 14, 2016 at 08:28:46PM -0800, Sumit Naiksatam wrote: > On Wed, Dec 14, 2016 at 4:54 AM, Joshua Hesketh > wrote: > > The repos listed[0] have had stable/liberty branch removed and replaced with > > a liberty-eol tag. Any open reviews have been abandoned. > > >

[openstack-dev] [daisycloud-core] Agenda for IRC meeting 0800UTC Dec. 16 2016

1) Roll Call 2) OPNFV: Daisy CI Progress 3) OpenStack Version management 4) AoB B.R., Zhijiang __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [zaqar] Next meeting in 2017

Hi team, Due to most of the team members will be on vacation in the next couple of weeks, so we will cancel the next 3 meetings. And the first meeting of 2017 will be 10th of Jan. And I also proposed the new meeting time based on our poll, see https://review.openstack.org/411564 If the patch is

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

+1. From the neutron-fwaas perspective, Nate has been instrumental in driving our integration with neutron on the agent extension framework, neutron-lib as well as on CI. Thanks Sridar From: Kevin Benton > Reply-To: OpenStack List

Re: [openstack-dev] [neutron] proposing Miguel Lavalle as neutron core and Brian Haley as L3 Lt

+1 From: Armando M. [mailto:arma...@gmail.com] Sent: Thursday, December 15, 2016 3:15 PM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [neutron] proposing Miguel Lavalle as neutron core and Brian Haley as L3 Lt Hi

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

+1 From: Kevin Benton [mailto:ke...@benton.pub] Sent: Thursday, December 15, 2016 5:00 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs +1 On

Re: [openstack-dev] [neutron] Proposing Abhishek Raut as neutronclient core

Thank you! From: "Armando M." > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Thursday, December 15, 2016 at 2:57 PM To: "OpenStack

Re: [openstack-dev] [release][ptl][all] self-service branch management

Hello, Doug, This is great. One question about the branch patches. In the past, when a new branch was created, we often have to update the devstack plugin to pull the code from correct branch. So if self-service branch management is available, will the devstack plugin will be updated with one

Re: [openstack-dev] [neutron] proposing Miguel Lavalle as neutron core and Brian Haley as L3 Lt

+1 On Dec 15, 2016 18:18, "Armando M." wrote: Hi neutrinos, Miguel Lavalle has been driving the project forward consistently and reliably. I would like to propose him to be entrusted with +2/+A rights in the areas he's been most prolific, which are L3 and DHCP. At the same

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

+1 On Dec 15, 2016 19:03, "Armando M." wrote: > Hi neutrinos, > > I would like to propose Ryan and Nate as the go-to fellows for > service-related patches. > > Both are core in their repos of focus, namely neutron-dynamic-routing and > neutron-fwaas, and have a good

Re: [openstack-dev] [tripleo] [ci] recheck impact on CI infrastructure

On Thu, Dec 15, 2016 at 12:22 PM, Sven Anderson wrote: > Hi all, > > while I was waiting again for the CI to be fixed and didn't want to > torture it with additional rechecks, I wanted to find out, how much of > our CI infrastructure we waste with rechecks. My assumption was that

[openstack-dev] [neutron] multinode CI jobs in the gate

Hi Neutrinos, Infra patch proposed in [1] got me thinking again about what we shall do when it comes to multinode testing in the gate and how to focus our testing and CI efforts upstream going forward. My line of thinking has always been that multinode resources should be devoted to

[openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

Hi neutrinos, I would like to propose Ryan and Nate as the go-to fellows for service-related patches. Both are core in their repos of focus, namely neutron-dynamic-routing and neutron-fwaas, and have a good understanding of the service framework, the agent framework and other bits and pieces.

Re: [openstack-dev] [architecture][api][Nova][Neutron][Cinder] nova-compute's architecture/API

On 16 December 2016 at 00:01, Clint Byrum wrote: > So, I've been quietly ranting in hallways about this for a while. I may > be way way off base here. I want to kick the discussion off, so I've > submitted a proposal to the arch-wg about it. Please if you're interested > in how

[openstack-dev] [neutron] proposing Miguel Lavalle as neutron core and Brian Haley as L3 Lt

Hi neutrinos, Miguel Lavalle has been driving the project forward consistently and reliably. I would like to propose him to be entrusted with +2/+A rights in the areas he's been most prolific, which are L3 and DHCP. At the same time, I'd like to propose Brian Haley as our next Chief L3 Officer.

[openstack-dev] [architecture][api][Nova][Neutron][Cinder] nova-compute's architecture/API

So, I've been quietly ranting in hallways about this for a while. I may be way way off base here. I want to kick the discussion off, so I've submitted a proposal to the arch-wg about it. Please if you're interested in how Nova/Neutron/Cinder interact with nova-compute, I think it might be

Re: [openstack-dev] [neutron] Proposing Abhishek Raut as neutronclient core

On 15 December 2016 at 09:50, Akihiro Motoki wrote: > +1 > Welcome to the team Abhishek! > > 2016-12-14 10:22 GMT+09:00 Armando M. : > >> Hi folks, >> >> Abhishek Raut's recent involvement in OSC and python-neutronclient has >> helped moving a few efforts

[openstack-dev] [architecture] Updates from the Architecture Working Group

Greetings! We've had a slow couple of months since Barcelona, and I expect we'll continue to go very slow for the rest of 2016, but we definitely don't want to lose momentum, so here is what we've been up to and where we're going in the immediate future: * arch-wg repo is live - This is the

Re: [openstack-dev] [TripleO] Network Configuration in TripleO UI

On 12/08/2016 08:05 AM, Jiri Tomasek wrote: Hi all, I've been investigating how to implement TripleO network configuration in TripleO UI. Based on my findings I'd like to propose a solution. tl;dr proposal: Slightly refactor Network environment files to match GUI usage, Use Jinja Templating

Re: [openstack-dev] [tripleo] [ci] recheck impact on CI infrastructure

Neat, thanks Sven! Here are the nova stats: http://paste.openstack.org/show/592551/ --diana On Thu, Dec 15, 2016 at 12:22 PM, Sven Anderson wrote: > Hi all, > > while I was waiting again for the CI to be fixed and didn't want to > torture it with additional rechecks, I

[openstack-dev] [glance] meeting schedule for next 3 weeks

The weekly IRC meetings for Glance are held in #openstack-meeting-4 on Thursdays at 14:00 UTC. The agenda [0] and transcripts [1] are publicly available. Given the upcoming holidays, here's what we decided today about the next 3 weeks: December 22: We will meet, but don't feel bad if you can't

Re: [openstack-dev] [kolla][tc] Video Meetings - input requested

Ok, let me reverse this discussion. We think hangouts are exclusive, and irc is not? I've seen multiple times when people were waaay into discussion, lines of text swarming the screen, somebody from outside speaks up, entirely reasonable and on topic thing, but is ignored because other actors in

Re: [openstack-dev] [kolla][tc] Video Meetings - input requested

On 14/12/16 18:18, Michał Jastrzębski wrote: I agree that meeting notes are crucial to this type of meeting.I just say that gerrit PoC/demo is valid form of 'notes' if meeting was about some implementional detail, which I assume is the case for this type of meetings. Do we agree that as hoc

Re: [openstack-dev] [kolla][tc] Video Meetings - input requested

  -Original Message- From: Michał Jastrzębski Reply: OpenStack Development Mailing List (not for usage questions) Date: December 14, 2016 at 17:20:21 To: OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [Neutron][DVR] - No IRC Meeting until 2017

Hi Folks, We will not have another DVR sub-team meeting until 2017, resuming on January 4th, to accommodate those that will be away. Enjoy the break! -Brian __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [nova] Let's kill quota classes (again)

> We're moving quotas to the API and we're going to stop doing the > reservation/commit/rollback race dance between API and compute nodes per > this spec: > > https://specs.openstack.org/openstack/nova-specs/specs/ocata/approved/cells-count-resources-to-check-quota-in-api.html It's very nice

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

On Thu, Dec 15, 2016 at 10:58 AM, Sean Dague wrote: > One of the big things to consider is which of these items directly > support one of the key PWG issues: "painless upgrades" > > The following items: movinging paste.ini out of config, new style > olso.policy (in code), and

Re: [openstack-dev] Golang technical requirements

On 2016-12-14 17:49:46 -0600 (-0600), Monty Taylor wrote: [...] > For things we generate in pbr - like AUTHORS and ChangeLog - assuming we > want to do the same thing in go, we could likely come up with something > similar. I also think we should consider that perhaps those two files > are not

[openstack-dev] [tripleo] [ci] recheck impact on CI infrastructure

Hi all, while I was waiting again for the CI to be fixed and didn't want to torture it with additional rechecks, I wanted to find out, how much of our CI infrastructure we waste with rechecks. My assumption was that every recheck is a waste of resources based on a false negative, because it

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Excerpts from Sean Dague's message of 2016-12-15 11:58:42 -0500: > One of the big things to consider is which of these items directly > support one of the key PWG issues: "painless upgrades" > > The following items: movinging paste.ini out of config, new style > olso.policy (in code), and

Re: [openstack-dev] [watcher] Next PTL elections

On Dec 15, 2016, at 8:15 AM, Antoine Cabot wrote: > Each of you are amazing and together you make an awesome team. > It has been an absolute pleasure to serve as PTL, thank you for letting me > do so. It was great to work with you, taking Watcher from an idea to a full

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

One of the big things to consider is which of these items directly support one of the key PWG issues: "painless upgrades" The following items: movinging paste.ini out of config, new style olso.policy (in code), and rootwrap -> privsep all eliminate files in /etc that dramatically impact code

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

Greetings OpenStack community, This week we have the pleasure of adding Ed Leafe as a core. Ed has been a consistent and positive presence for quite some time and he'll be good, by hook or crook. Our discussion today was focused in two areas: * The developing capabilities guideline (at

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

> On 15 Dec 2016, at 16:19, Doug Hellmann wrote: > > Excerpts from Jean-Philippe Evrard's message of 2016-12-15 09:11:12 +: >> Hello, >> >> Maybe this will sound dumb … >> >> I received this email on openstack-dev mailing list. I don’t know if it was >> sent to any

[openstack-dev] [neutron] drivers meeting cancellation today

Hi folks, Due to conflicts, we are unable to host the drivers meeting today. Apologies for the short notice. Thanks, Armando __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [glance] Propose Steve Lewis for Glance core

Having heard only affirmative responses, I've added Steve Lewis to the Glance core group, with all the rights and privileges pertaining thereto. Welcome to the Glance core team, Steve! On 12/13/16 5:05 PM, Brian Rosmaita wrote: > I'd like to propose Steve Lewis (stevelle on IRC) for Glance

[openstack-dev] [searchlight] End of 2017 meeting schedule

Hello everyone, Due to the upcoming holidays we have a modified meeting schedule the next few weeks. December 29th meeting is cancelled. December 22nd meeting is tentative. Kevin_Zheng, lei-zh, yingjun will coordinate deciding whether or not one is needed and if one of them will be

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Excerpts from Jean-Philippe Evrard's message of 2016-12-15 09:11:12 +: > Hello, > > Maybe this will sound dumb … > > I received this email on openstack-dev mailing list. I don’t know if it was > sent to any other place, because it’s basically agreeing on development to be > done, which

Re: [openstack-dev] [TripleO][Upgrade Squad syncup]

On 14/12/16 12:34, Marios Andreou wrote: > On 14/12/16 11:17, Julie Pichon wrote: >> On 14 December 2016 at 08:56, Dougal Matthews wrote: >>> On 13 December 2016 at 16:12, Emilien Macchi wrote: On Tue, Dec 13, 2016 at 10:58 AM, Marios Andreou

[openstack-dev] [sahara] Meetings schedule for next 3 weeks

Hello everyone, I’d lke to announce that next 3 meetings (Dec. 22, Dec. 29, Jan. 5) for Sahara project are cancelled due to future holidays (Christmas, New Year). Next meeting will be at Jan. 12. If you have something to discuss, bring your topics to #openstack-sahara channel or mailing

[openstack-dev] [watcher] Next PTL elections

Hi Watcher team, I would like to share with you that I do not intend to run for the PTL position of the Pike development cycle starting in March 2017. Next PTL elections will be held at the end of January 2017. I'm sending this now so I can work with people interested in the role, if you intend

[openstack-dev] [designate] Next IRC meeting in 2017

Hi All, As a lot of people are now going on vacation for the holiday season, we decided to pick up IRC meetings in 2017. So, our first meeting will be 4th Jan 2017 @ 17:00 UTC See everyone after the break Graham __

Re: [openstack-dev] [nova] Let's kill quota classes (again)

On 12/15/2016 3:11 AM, Andrey Volkov wrote: Hi, I totally agree with Matt than `os-quota-class-sets` is inconsistent. It has that hardcoded default class can't be changed. API call is documented neither Nova nor Cinder (has the same API for quotas). With defaults in the configuration I have

[openstack-dev] [nova] Next notification meeting in 2017

Hi, Due to the holiday season the next notification subteam meeting will be held on 3rd of January [1]. Cheers, gibi [1] https://www.timeanddate.com/worldclock/fixedtime.html?iso=20170103T17 __ OpenStack Development

Re: [openstack-dev] [infra][neutron] Intel NFV CI voting permission in Neutron

Waldemar wrote: Hi Ihar et al, Apologies for late reply. We were fighting couple of issues with the CI in last couple of days. The networking problem mentioned by Ihar was one of them. We're running fine as of yesterday [1]. To stay on the safe side let's

Re: [openstack-dev] [kolla] Bugs cleanup dashboard

This actually seems really useful, thanks Christian. On 15/12/16 11:35, Christian Berendt wrote: Hello everybody. Based on the dashboard which is used for the Nova project I have created one for Kolla. The dashboard gets updated hourly. http://kolla.betacloud.io/bugs-dashboard.html

[openstack-dev] [kolla] Bugs cleanup dashboard

Hello everybody. Based on the dashboard which is used for the Nova project I have created one for Kolla. The dashboard gets updated hourly. http://kolla.betacloud.io/bugs-dashboard.html Christian. -- Christian Berendt Chief Executive Officer (CEO) Mail: bere...@betacloud-solutions.de Web:

Re: [openstack-dev] [tripleo] Deep dive session about the UI - January 12

On Tue, Dec 13, 2016 at 5:05 PM, Emilien Macchi wrote: > On Mon, Dec 12, 2016 at 1:30 PM, Ana Krivokapic > wrote: > > Hi Everyone, > > > > On the 12th of January 2017, I'll lead a TripleO deep dive[1] session on > how > > to contribute to the TripleO UI.

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Jean-Philippe Evrard wrote: > Maybe this will sound dumb … > > I received this email on openstack-dev mailing list. I don’t know if it was > sent to any other place, because it’s basically agreeing on development to be > done, which makes sense to me. > So openstack-dev people (called further

[openstack-dev] [[neutron]how to contribute for "tunnel termination point as part of the binding details"

Hello, Kevin and others may be involved: After the discussion for "VxLAN L2 networking across Neutron"[1], Tricircle team wants to contribute on this point as mentioned in the recap mail[2]: "formalize the tunnel termination point by adding it to the port binding data model just like other

Re: [openstack-dev] [nova] Let's kill quota classes (again)

Hi, I totally agree with Matt than `os-quota-class-sets` is inconsistent. It has that hardcoded default class can't be changed. API call is documented neither Nova nor Cinder (has the same API for quotas). With defaults in the configuration I have some concerns: - As it was mentioned before,

Re: [openstack-dev] [all][ptls][tc][goals] community goals for Pike

Hello, Maybe this will sound dumb … I received this email on openstack-dev mailing list. I don’t know if it was sent to any other place, because it’s basically agreeing on development to be done, which makes sense to me. So openstack-dev people (called further “devs”) will push their company

Re: [openstack-dev] [neutron] Proposing Abhishek Raut as neutronclient core

+1 2016-12-14 10:22 GMT+09:00 Armando M. : > Hi folks, > > Abhishek Raut's recent involvement in OSC and python-neutronclient has > helped moving a few efforts along in the right direction. I would like to > suggest we double down on core firepower for the neutronclient repo >