[openstack-dev] [neutron] Neutron CI team meeting

2017-01-31 Thread Armando M.
Hi folks, Recently [1], a new meeting has been setup to give the neutron team a dedicated time to discuss any upstream CI matter (gate issues, testing strategies, etc), as well as an overflow space to be used after the main team meeting section [3]. Kudos to Ihar for being our first chair.

Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

2017-02-08 Thread Armando M.
On 2 February 2017 at 16:09, Armando M. <arma...@gmail.com> wrote: > Hi neutrinos, > > I have put a number of patches in the merge queue for a few sub-projects. > We currently have a number of these that are on an independent release > schedule. In particular: > &

Re: [openstack-dev] [neutron] [stadium] subprojects on independent release cycle

2017-02-08 Thread Armando M.
ase not too far after Openstack. > The date of March 10th looks reasonable as a target, and we'll stick to > that. > > Excellent, thanks for the update. Cheers, Armando Best, > > -Thomas > > > > On 2 February 2017 at 16:09, Armando M. <arma...@gmail.com> wrote

Re: [openstack-dev] [requirements][neutron] bot bumping patches off gate queue

2017-02-01 Thread Armando M.
On 1 February 2017 at 07:29, Ihar Hrachyshka wrote: > Hi all, > > lately I see the requirements bot proposing new rebases for its > patches (and bumping existing patch sets from the gate queue) every > second hour, at least for Neutron [1], which makes it impossible to >

Re: [openstack-dev] [neutron] Neutron CI team meeting

2017-01-31 Thread Armando M.
k-infra/project-config/blob/ > master/jenkins/jobs/python-jobs.yaml#L17 > > > PS: Congrats Ihar for your new role > > > > From: "Armando M." <arma...@gmail.com> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > op

Re: [openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

2017-02-02 Thread Armando M.
On 2 February 2017 at 08:40, Sean Dague wrote: > On 02/02/2017 11:16 AM, Matthew Treinish wrote: > > > > > > > We definitely aren't saying running a single worker is how we recommend > people > > run OpenStack by doing this. But it just adds on

[openstack-dev] [neutron] grenade failures in the gate

2017-01-23 Thread Armando M.
Hi neutrinos, We spotted [1] in the gate. Please wait for its resolution until pushing patches into the merge queue. Thanks, Armando [1] https://bugs.launchpad.net/neutron/+bug/1658806 __ OpenStack Development Mailing List

Re: [openstack-dev] [neutron] grenade failures in the gate

2017-01-23 Thread Armando M.
On 23 January 2017 at 13:50, Jeremy Stanley <fu...@yuggoth.org> wrote: > On 2017-01-23 13:38:58 -0800 (-0800), Armando M. wrote: > > We spotted [1] in the gate. Please wait for its resolution until pushing > > patches into the merge queue. > > https://review

Re: [openstack-dev] [Neutron] PTL Candidacy

2017-01-24 Thread Armando M.
On 24 January 2017 at 12:46, Jeremy Stanley wrote: > On 2017-01-24 10:51:39 -0800 (-0800), Ihar Hrachyshka wrote: > > On Tue, Jan 24, 2017 at 12:50 AM, Kevin Benton wrote: > > > I'm on board with getting visibility into the drivers with > improvements to > >

Re: [openstack-dev] [neutron] Ocata Feature Freeze

2017-01-26 Thread Armando M.
On 26 January 2017 at 12:53, Dariusz Śmigiel wrote: > Dear Neutrinos, > Feature Freeze day arrived! Ocata-3 has been released, so it means > that no new features will be allowed to current release... The only > patches approved to be merged should be: release critical

[openstack-dev] [neutron] Ocata postmortem

2017-02-23 Thread Armando M.
Hi folks, Now that Ocata is officially releases, I'd like to get a moment of your time to double check our postmortem document [1], and provide as much information as you can on the state of work assigned to you or work you have been involved with during the Ocata timeframe. Your old PTL and

Re: [openstack-dev] [Neutron] Alternative approaches for L3 HA

2017-02-22 Thread Armando M.
On 13 February 2017 at 23:23, Kosnik, Lubosz wrote: > So from my perspective I can tell that problem is completely in > architecture and even without something outside of Neutron we cannot solve > that. > Two releases ago I started to work on hardening that feature but

Re: [openstack-dev] [All] IRC Mishaps

2017-02-09 Thread Armando M.
On 9 February 2017 at 07:43, Morales, Victor wrote: > One of my favorites is the usage of #undo command during the meetings for > fixing a quick copy & paste link. Should be necessary to include more > information in this wiki entry[1] > Yes, I can't count the number

Re: [openstack-dev] [release][all] HELP NEEDED: test failures blocking requirements ocata branch and opening of pike

2017-02-09 Thread Armando M.
On 9 February 2017 at 05:16, Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2017-02-08 23:54:06 -0500: > > The patch to update the XStatic package versions [1] is blocked by a > > patch to remove nova-docker from the requirements project sync list [2], > >

[openstack-dev] [neutron] PTL Candidacy

2017-01-24 Thread Armando M.
Hi neutrinos, No, it's not what you might be thinking...I am just delighted to see two excellent candidates willing to take the reins of the project going forward [1,2]. I couldn't hope for more enthusiasm; best of luck to both candidates and anyone else who is going to step up! This is

Re: [openstack-dev] (dis)Continuation of Neutron VPNaaS

2017-01-19 Thread Armando M.
On 19 January 2017 at 13:41, Bruno L wrote: > Hi, > > November last year the Neutron team has announced that VPN as a Service > will be no longer part of Neutron[1]. > > We run a public cloud based in New Zealand called Catalyst Cloud[2]. Our > customers find the VPN

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Armando M.
On 5 August 2016 at 05:59, Sean Dague <s...@dague.net> wrote: > On 08/04/2016 09:15 PM, Armando M. wrote: > > So glad we are finally within the grasp of this! > > > > I posted [1], just to err on the side of caution and get the opportunity > > to see how

Re: [openstack-dev] [all] devstack changing to neutron by default RSN

2016-08-05 Thread Armando M.
On 5 August 2016 at 07:39, Brian Haley <brian.ha...@hpe.com> wrote: > On 08/05/2016 08:59 AM, Sean Dague wrote: > >> On 08/04/2016 09:15 PM, Armando M. wrote: >> >>> So glad we are finally within the grasp of this! >>> >>> I posted [1], just to

Re: [openstack-dev] [Neutron] Intermittent gate failures

2016-08-24 Thread Armando M.
On 24 August 2016 at 10:30, Armando M. <arma...@gmail.com> wrote: > > > On 22 August 2016 at 18:25, Armando M. <arma...@gmail.com> wrote: > >> >> >> On 22 August 2016 at 09:51, Armando M. <arma...@gmail.com> wrote: >> >>> Neutrinos,

Re: [openstack-dev] [Neutron][networking-sfc] need help on requesting release for networking-sfc

2016-08-31 Thread Armando M.
On 31 August 2016 at 17:31, Cathy Zhang wrote: > CC OpenStack alias. > > > > *From:* Cathy Zhang > *Sent:* Wednesday, August 31, 2016 5:19 PM > *To:* Armando Migliaccio; Ihar Hrachyshka; Cathy Zhang > *Subject:* need help on requesting release for networking-sfc > > > >

[openstack-dev] [Neutron] Team meeting cancelled

2016-09-02 Thread Armando M.
Neutrinos, Because of holidays in US, it's probably safer to cancel the meeting for the week starting Monday 5th. Ask for your FFE, as needed on [1] [1] https://review.openstack.org/#/c/360207/ Cheers, Armando __ OpenStack

[openstack-dev] [Neutron] Cutting milestone 3 deliverables

2016-09-01 Thread Armando M.
Neutrinos, We are in the process of releasing the deliverables for Newton 3. This means we are in feature freeze and nothing should be approved for merging unless it is release critical, gate blocker, targeted for RC1[1] or has been granted a feature freeze exception [2] on the postmortem. For

Re: [openstack-dev] [Neutron] Cutting milestone 3 deliverables

2016-09-01 Thread Armando M.
/neutron/policies/release-checklist.html [3] https://bugs.launchpad.net/neutron/+bugs?field.tag=doc On 1 September 2016 at 11:45, Armando M. <arma...@gmail.com> wrote: > Neutrinos, > > We are in the process of releasing the deliverables for Newton 3. This > means we are in feature

[openstack-dev] [Neutron] Feature Freeze and Feature Freeze exceptions

2016-09-07 Thread Armando M.
Hi folks, We are about a week away from cutting our first release candidate [0]. In preparation for that event, we need to make sure our postmortem [1] and FFE requests are in good order. For those of you have not had the chance of commenting on [1], please go ahead and provide your input.

[openstack-dev] [Neutron][Nova][Infra] Linuxbridge job bump

2016-09-08 Thread Armando M.
Folks, This morning we merged the switch to Xenial for the Linuxbridge job. However, we overlooked the fact that the job configuration hardcodes eth0 as one of the variables needed by the Neutron linux bridge driver [2]. That led to failures like [3]. We have a number of changes in the works to

[openstack-dev] [Neutron] Preparing to cut RC1

2016-09-15 Thread Armando M.
Neutrinos, In the next 24 hours we will be cutting RC1. Unfortunately we're battling with a nasty bug, that's causing some instability and we're trying to find the root cause. Please back off rechecking and merging until we figured out what's happening. In the meantime, do not be surprised if

Re: [openstack-dev] [neutron][stadium] Query regarding procedure for inclusion in Neutron Stadium

2016-09-23 Thread Armando M.
On 22 September 2016 at 22:36, Takashi Yamamoto <yamam...@midokura.com> wrote: > hi, > > On Fri, Sep 23, 2016 at 4:20 AM, Armando M. <arma...@gmail.com> wrote: > > > > > > On 22 September 2016 at 00:46, reedip banerjee <reedi...@gmail.com> > wrote:

[openstack-dev] [Neutron] Preparing RC2

2016-09-26 Thread Armando M.
Neutrinos, A this point, please consider the list of fixes for RC2 [1] final. We are no longer considering adding anything to the list unless it's critical and preventing merges. Zuul is pretty backed up so we need to clear the currently backlog before considering adding anything else. We have a

Re: [openstack-dev] [Neutron][Nova] Expose trunk details over metadata API

2016-10-07 Thread Armando M.
On 7 October 2016 at 06:43, Bence Romsics wrote: > Hi, > > To follow up on the complications of bringing up trunk subports [1] I > have written up a small proposal for a tiny new feature affecting > neutron and nova. That is how to expose trunk details over metadata >

[openstack-dev] [Neutron] Stadium evolution - final stage

2016-10-07 Thread Armando M.
Neutrinos, As some of you may have noticed, there has been a fresh batch of patches on topic [1]. After having worked on [2][3] during the span of Newton, we are approaching now the final stage of this consolidation effort, where I attempt to define a procedure for transparently letting the

[openstack-dev] [Neutron] Newton Postmortem

2016-09-16 Thread Armando M.
Neutrinos, Now that Ocata is with us, we can almost regain our ability to pronounce Neutron without confusing it with Newton (at least I know I can). Before doing that, there is still the postmortem to finalize [1]. I will keep on touching it between now and the day of the official release to

Re: [openstack-dev] [nova][neutron] summit cross-project session

2016-09-19 Thread Armando M.
On 18 September 2016 at 11:46, Matt Riedemann wrote: > I want to confirm whether or not we're going to have a nova/neutron > cross-project fishbowl session in Barcelona, I think we are. Since Thierry > has the draft slots out I wanted to start looking at what time is

Re: [openstack-dev] [neutron][stadium] Query regarding procedure for inclusion in Neutron Stadium

2016-09-22 Thread Armando M.
On 22 September 2016 at 00:46, reedip banerjee wrote: > Dear Neutron Core members, > > I have a query regarding the procedure for inclusion in the Neutron > Stadium. > I wanted to know if a project can apply for Big Tent and Neutron Stadium > together ( means can a project be

Re: [openstack-dev] [Neutron] Broken port rule masking: let's have it fixed?

2016-09-22 Thread Armando M.
On 22 September 2016 at 05:50, Inessa Vasilevskaya < ivasilevsk...@mirantis.com> wrote: > Hello, > > Apologies for multiple posts, forgot to set proper subject in previous one. > > I'd like to turn attention to the broken port rule masking problem [1], > which affects 2 projects so far: > neutron

[openstack-dev] Fwd: [release][Neutron] Neutron Newton RC1 available

2016-09-16 Thread Armando M.
Neutrinos, As per announcement below, we are now past RC1. I'll be going over the changes that were blocked during the past week and lift the -2s. Even though master development is open, please consider focusing on Newton with a great deal of attention [1]. Make sure to give review priority to

[openstack-dev] [Neutron] Adding ihrachys to the neutron-drivers team

2016-09-17 Thread Armando M.
Hi folks, I would like to propose Ihar to become a member of the Neutron drivers team [1]. Ihar wide knowledge of the Neutron codebase, and his longstanding duties as stable core, downstream package whisperer, release and oslo liaison (I am sure I am forgetting some other capacity he is in) is

[openstack-dev] [Neutron][Nova] Neutron mid-cycle summary report

2016-08-26 Thread Armando M.
Hi Neutrinos, For those of you who couldn't join in person, please find a few notes below to capture some of the highlights of the event. I would like to thank everyone one who helped me put this report together, and everyone who helped make this mid-cycle a fruitful one. I would also like to

[openstack-dev] [nova] [os-vif] [neutron] Race in setting up linux bridge

2016-08-26 Thread Armando M.
Folks, Today I spotted [1]. It turns out Neutron and Nova might be racing trying to set up the bridge to provide VM with connectivity/dhcp. In the observed failure mode, os-vif fails in [2]. I suppose we might need to protect the bridge creation and make it handle the potential exception. We

[openstack-dev] [Neutron] Intermittent gate failures

2016-08-22 Thread Armando M.
Neutrinos, Since the merge of test [1], a race has surfaced, which leads to failure as reported in [2]. A number of Neutron's jobs are affected, and even though the failure is only intermittent, it is particularly bad for the linux bridge job. If I can ask you to hold your +2/+W until [3] puts

Re: [openstack-dev] [Neutron] Intermittent gate failures

2016-08-22 Thread Armando M.
On 22 August 2016 at 09:51, Armando M. <arma...@gmail.com> wrote: > Neutrinos, > > Since the merge of test [1], a race has surfaced, which leads to failure > as reported in [2]. A number of Neutron's jobs are affected, and even > though the failure is only intermittent, i

[openstack-dev] [Neutron] Drivers team cancelled

2016-08-25 Thread Armando M.
Hi folks, We have a few absences today, apologies for the short notice but I am going to cancel the meeting. If there is anything release related you'd like to discuss please reach out to me on this thread or IRC. Cheers, Armando

[openstack-dev] [Neutron] Wrapping up Newton

2016-08-25 Thread Armando M.
Hi Neutrinos, Newton-3 is almost upon us. We are now in non-client requirement freeze, and a week away from client requirement/feature freeze. This is the time where we switch gear...for real: - Start focusing on testing and documentation, if you have not done so already; - Apply for

Re: [openstack-dev] [Neutron] Intermittent gate failures

2016-08-24 Thread Armando M.
On 22 August 2016 at 18:25, Armando M. <arma...@gmail.com> wrote: > > > On 22 August 2016 at 09:51, Armando M. <arma...@gmail.com> wrote: > >> Neutrinos, >> >> Since the merge of test [1], a race has surfaced, which leads to failure >> as reported

[openstack-dev] [Neutron] Driver meeting cancelled for Thur Sept 29

2016-09-28 Thread Armando M.
__ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Neutron] Ocata Design Summit ideas kick-off

2016-09-27 Thread Armando M.
Hi folks, The summit is less than a month away and it's the time of the year where we need to plan for design summit sessions. This time we are going for 10 fishbowl sessions, plus Friday [0]. We will break down sessions in three separate tracks as we did the last two summits. Each track will

[openstack-dev] [Neutron] Retiring stale stadium projects

2016-09-27 Thread Armando M.
Hi Neutrinos, I wanted to double check with you the state of these following projects: - networking-ofagent - python-neutron-pd-driver It's my understanding that they are ready for retirement or thereabouts. Please confirm, and I'll kick off the countdown sequence [1]. Cheers, Armando [1]

Re: [openstack-dev] dhcp 'Address already in use' errors when trying to start a dnsmasq

2016-09-27 Thread Armando M.
On 27 September 2016 at 11:29, Miguel Angel Ajo Pelayo wrote: > Ack, and thanks for the summary Ihar, > > I will have a look on it tomorrow morning, please update this thread > with any progress. > > > > On Tue, Sep 27, 2016 at 8:22 PM, Ihar Hrachyshka

Re: [openstack-dev] [nova][neutron] When are subnets needed on a network to create ports?

2016-11-08 Thread Armando M.
On 8 November 2016 at 18:35, Matt Riedemann wrote: > I've been looking at this nova bug: > > https://bugs.launchpad.net/nova/+bug/1637118 > > And the neutronv2 API code in nova and need some help from the neutron > team on how this should actually work. > If I am not

Re: [openstack-dev] [neutron] [lbaas] [octavia] Ocata LBaaS retrospective and next steps recap

2016-11-09 Thread Armando M.
On 9 November 2016 at 05:50, Gary Kotton wrote: > Hi, > What about neutron-lbaas project? Is this project still alive and kicking > to the merge is done or are we going to continue to maintain it? I feel > like we are between a rock and a hard place here. LBaaS is in

[openstack-dev] [Neutron] Transition to Ubuntu Xenial in the gate

2016-11-10 Thread Armando M.
Hi Neutrinos, Some of you may be aware of our CI jobs have been transitioning to Xenial. There are a few jobs still left and taking into account mail [1] we need to accelerate the process a bit, especially for those jobs that affect our gate queue or are voting. Ajo put together [2], I also

[openstack-dev] [Neutron] retiring python-neutron-pd-driver

2016-10-19 Thread Armando M.
To whom it may concern, I have started the procedure [1] to retire project [2]. If you are affected by this, this is the last opportunity to provide feedback. That said, users should be able to use the in tree version of dibbler as documented in [3]. Cheers, Armando [1]

[openstack-dev] [Neutron] Team meeting this Monday at 2100 UTC + forthcoming schedule

2016-10-17 Thread Armando M.
Hi neutrinos, A kind reminder for this week's meeting. More on the agenda [1]. Also, due to the summit, the next occurrences will be cancelled. - Oct 25, Tuesday - Oct 31, Monday Cheers, Armando [1] https://wiki.openstack.org/wiki/Network/Meetings

[openstack-dev] [Neutron] Drivers meeting cancelled Oct 27

2016-10-20 Thread Armando M.
Folks, Just a reminder that due to the ongoing Summit, the drivers team is cancelled for the week. We'll meet regularly in the next few hours. Cheers, Armando __ OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [neutron] next upgrades meeting is Nov 7th

2016-10-17 Thread Armando M.
On 17 October 2016 at 12:29, Ihar Hrachyshka wrote: > Hi all, > > due to the summit we cancel the next two upgrades subteam meetings. > > We will get back Nov 7th, just in time to close any remaining gaps before > the world as we know it is destroyed by US elections the next

Re: [openstack-dev] [Neutron] Transition to Ubuntu Xenial in the gate

2016-11-23 Thread Armando M.
On 10 November 2016 at 17:36, Armando M. <arma...@gmail.com> wrote: > Hi Neutrinos, > > Some of you may be aware of our CI jobs have been transitioning to Xenial. > There are a few jobs still left and taking into account mail [1] we need to > accelerate the process a bit,

Re: [openstack-dev] [neutron] neutron-lib impact

2016-11-23 Thread Armando M.
w playing out. >> >> Thanks >> >> [1] >> https://github.com/openstack/neutron-lib/blob/master/doc/sou >> rce/contributing.rst >> [2] >> https://github.com/openstack/neutron-lib/blob/master/doc/sou >> rce/contributing.rst#phase-4-consume &

Re: [openstack-dev] [neutron][tacker] Trunk ports in Tacker?

2016-11-23 Thread Armando M.
On 23 November 2016 at 01:47, zhi wrote: > Hi, all > > Recently I did some research about trunk port in neutron by following > document[1]. By creating a trunk port, I can use this port ( aka " parent > port " ) to create a VM. So I can add or remove subports on this

Re: [openstack-dev] [neutron] neutron-lib impact

2016-11-24 Thread Armando M.
would have been jobs from all sub projects voting >> on each neutron change. >> >> On Nov 24, 2016 10:02, "Armando M." <arma...@gmail.com> wrote: >> >> >> >> On 24 November 2016 at 05:27, Neil Jerram <n...@tigera.io> wrote: >> >

Re: [openstack-dev] [neutron] stable/newton 'broken'

2016-11-24 Thread Armando M.
> 2. Tap-as-a-service is added to the stadium and tent. > How is this relevant to this discussion? > > A luta continua > > > > *From: *"Armando M." <arma...@gmail.com> > *Reply-To: *OpenStack List <openstack-dev@lists.openstack.org> > *Date: *Thur

Re: [openstack-dev] [neutron] neutron-lib impact

2016-11-24 Thread Armando M.
eady. >> >> In particular the 'Phase 4: Consume' section [2] provides some tips on >> how we see this workflow playing out. >> >> Thanks >> >> [1] >> https://github.com/openstack/neutron-lib/blob/master/doc/ >> source/contributing.rst >>

Re: [openstack-dev] [neutron] stable/newton 'broken'

2016-11-24 Thread Armando M.
On 24 November 2016 at 02:38, Thierry Carrez wrote: > Gary Kotton wrote: > > Please see - http://logs.openstack.org/82/401882/1/check/gate-vmware- > nsx-python27-db-ubuntu-xenial/1ac0686/console.html#_2016-11- > 24_06_58_38_520273 > > Here we are pulling trunk as there is

[openstack-dev] [neutron] neutron-lib impact

2016-11-23 Thread Armando M.
Hi neutrinos, In the last few hours a couple of changes landed [1,2] that caused a bit of a jam in the neutron subproject gates, as they overlapped with another change [3] having impact on the subprojects. This is why it is important to communicate during team meetings and/or ML that patches

Re: [openstack-dev] [neutron] neutron-lib impact

2016-11-24 Thread Armando M.
projects voting > on each neutron change. > Right, and that's never gonna happen otherwise we might as well put all the code back into one tree. > > On Nov 24, 2016 10:02, "Armando M." <arma...@gmail.com> wrote: > >> >> >> On 24 November 2016 at 05:27, N

[openstack-dev] [neutron] oslo liasion

2016-11-22 Thread Armando M.
Hi neutrinos, I would like to announce Victor Morales, aka electrocucaracha as our oslo liasion [1]. If you would like to be help in any of the liasion capacities available, please review [1] and reach out to me. Cheers, Armando [1] https://wiki.openstack.org/wiki/CrossProjectLiaisons#Oslo

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

2016-11-22 Thread Armando M.
On 22 November 2016 at 06:09, Znoinski, Waldemar < waldemar.znoin...@intel.com> wrote: > > > >-Original Message- > >From: Jeremy Stanley [mailto:fu...@yuggoth.org] > >Sent: Monday, November 14, 2016 3:40 PM > >To: openstack-in...@lists.openstack.org; openstack-dev@lists.openstack. >

[openstack-dev] [neutron] Drivers meeting on Nov 24th cancelled

2016-11-22 Thread Armando M.
Happy Thanksgiving! Armando __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [neutron] neutron-lib impact

2016-11-16 Thread Armando M.
e project and that they too should be engaged. > What's this thread for then if not engaging/inviting people to review? Your point seems moot. > Thanks > > Gary > > > > *From: *"Armando M." <arma...@gmail.com> > *Reply-To: *OpenStack List <openstack-d

[openstack-dev] [neutron] neutron-lib impact

2016-11-15 Thread Armando M.
Hi neutrinos, As mentioned during the last team meeting [1], there is a change [2] in the works aimed at adopting the neutron plugins directory as provided in neutron-lib 1.0.0 [3]. As shown in [2], the switch to using the directory is relatively straightforward. I leave the rest of the affected

Re: [openstack-dev] [neutron] neutron-lib impact

2016-11-16 Thread Armando M.
A. [1] https://review.openstack.org/#/q/topic:plugin-directory [2] https://bugs.launchpad.net/vmware-nsx/+bug/1640319 > Thanks > > Gary > > > > *From: *"Armando M." <arma...@gmail.com> > *Reply-To: *OpenStack List <openstack-dev@lists.openstack.org

[openstack-dev] [neutron] rally failure in the gate

2016-11-17 Thread Armando M.
Hi folks, Please do not recheck rally failures. There was a breaking change introduced by aodh [0] that prevented rally to work on trusty. We are switching to xenial as we speak anyway [1], so the glitch should be short lived. Thanks, Armando [0] https://review.openstack.org/#/c/372586/ [1]

Re: [openstack-dev] [devstack][neutron] - dropping direct route to VMs (FIXED_RANGE)

2016-11-15 Thread Armando M.
On 15 November 2016 at 15:04, Kevin Benton wrote: > Hi all, > > > Right now, we do something in devstack that does not reflect how > deployments are normally done. We setup a route on the parent host to the > private tenant network that routes through the tenant's router[1].

[openstack-dev] [neutron] [vpnaas] vpnaas no longer part of the neutron governance

2016-11-15 Thread Armando M.
Hi As of today, the project neutron-vpnaas is no longer part of the neutron governance. This was a decision reached after the project saw a dramatic drop in active development over a prolonged period of time. What does this mean in practice? - From a visibility point of view, release notes

[openstack-dev] [Neutron] Summit design summary - a heads up

2016-10-31 Thread Armando M.
Hi folks, For those of you who missed the summit, I wanted to give a heads up that I am working with session chairs to provide here a distilled version of any conclusion/agreement/proposal reached in Barcelona during the Neutron track. In the meantime, some networking related conference sessions

[openstack-dev] [Neutron] summit sessions - feedback

2016-11-03 Thread Armando M.
Hi Neutrinos, You will be noticing a few emails getting into your inbox with subject summit recap or similar. Watch out for those if you're interested in making sense of the discussions as captured on etherpads [1]. Many thanks to the session chairs for the effort! Cheers and happy hacking!

Re: [openstack-dev] [Neutron] Centralizing some config options will break many stadium projects

2016-10-28 Thread Armando M.
On 27 October 2016 at 22:18, Brandon Logan wrote: > Hello Neutrinos, > I've come across an issue that I'd like to get input/opinions on. I've > been reviewing some of the centralize config options reviews and have > come across a few that would cause issues with

Re: [openstack-dev] [neutron] Cloud Provider Security Groups

2016-11-01 Thread Armando M.
On 31 October 2016 at 22:28, David G. Bingham wrote: > Yo Neutron devs :-) > > I was wondering if something like the following subject has come up: > "Cloud-provider Security Groups”. > > *Goal of this email*: Gauge the community’s need and see if this has come > up in

Re: [openstack-dev] Multinode testing with devstack and neutron broken

2016-10-11 Thread Armando M.
On 11 October 2016 at 17:05, Clark Boylan <cboy...@sapwetik.org> wrote: > On Tue, Oct 11, 2016, at 05:01 PM, Armando M. wrote: > > On 11 October 2016 at 16:54, Clark Boylan <cboy...@sapwetik.org> wrote: > > > > > On Tue, Oct 11, 2016, at 04:51 PM, Armando

Re: [openstack-dev] Multinode testing with devstack and neutron broken

2016-10-11 Thread Armando M.
On 11 October 2016 at 16:43, Clark Boylan <cboy...@sapwetik.org> wrote: > On Tue, Oct 11, 2016, at 04:32 PM, Armando M. wrote: > > On 11 October 2016 at 14:09, Clark Boylan <cboy...@sapwetik.org> wrote: > > > > > Hello everyone, > > > > >

Re: [openstack-dev] Multinode testing with devstack and neutron broken

2016-10-11 Thread Armando M.
On 11 October 2016 at 16:54, Clark Boylan <cboy...@sapwetik.org> wrote: > On Tue, Oct 11, 2016, at 04:51 PM, Armando M. wrote: > > On 11 October 2016 at 16:43, Clark Boylan <cboy...@sapwetik.org> wrote: > > > > > On Tue, Oct 11, 2016, at 04:32 PM, Armando

[openstack-dev] [Neutron] Design summit schedule

2016-10-11 Thread Armando M.
Neutrinos, The design summit schedule for Neutron is getting live and into shape at [1][2]. For questions/suggestions please feel free to reach out. Cheers, Armando [1] https://www.openstack.org/summit/barcelona-2016/summit-schedule/global-search?t=Neutron%3A [2]

Re: [openstack-dev] Multinode testing with devstack and neutron broken

2016-10-11 Thread Armando M.
On 11 October 2016 at 18:20, Sean M. Collins <s...@coreitpro.com> wrote: > Armando M. wrote: > > At this point I feel that changing the pool range is even less justified. > > If I had seen bug [4], I would have been against its fix, because you're > > absolutel

Re: [openstack-dev] Multinode testing with devstack and neutron broken

2016-10-11 Thread Armando M.
On 11 October 2016 at 14:09, Clark Boylan wrote: > Hello everyone, > > Currently multinode testing + neutron is broken in clouds that use > portions of 10.0.0.0/8 for their networking due to route conflicts with > devstack + neutron deployments.

Re: [openstack-dev] [Neutron] Team meeting this Monday at 2100 UTC + forthcoming schedule

2016-10-17 Thread Armando M.
bjects. > > 2016-10-17 13:28 GMT-05:00 Armando M. <arma...@gmail.com>: > > Hi neutrinos, > > > > A kind reminder for this week's meeting. More on the agenda [1]. Also, > due > > to the summit, the next occurrences will be cancelled. > > > &g

[openstack-dev] [neutron] broken linuxbridge gate

2016-11-29 Thread Armando M.
Hi folks, A recent devstack set of changes [0,1] accidentally broke the linuxbridge job in that bridge_mappings are no longer applied correct. To add insult to injury, this got applied to both stable and master (with the stable fix landing first). See [2,3] for a difference. This is not the

Re: [openstack-dev] [neutron] broken linuxbridge gate

2016-11-29 Thread Armando M.
On 29 November 2016 at 15:46, Armando M. <arma...@gmail.com> wrote: > Hi folks, > > A recent devstack set of changes [0,1] accidentally broke the linuxbridge > job in that bridge_mappings are no longer applied correct. To add insult to > injury, this got applied to b

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-10 Thread Armando M.
On 8 December 2016 at 20:55, Armando M. <arma...@gmail.com> wrote: > > > On 5 December 2016 at 07:59, Bence Romsics <bence.roms...@gmail.com> > wrote: > >> Hi, >> >> I measured how the new trunk API scales with lots of subports. You can >> find

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

2016-12-13 Thread 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 alongside Akihiro [1]. This not only will help speed up our transition to

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

2016-12-15 Thread Armando M.
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] [neutron] Proposing Abhishek Raut as neutronclient core

2016-12-15 Thread Armando M.
On 15 December 2016 at 09:50, Akihiro Motoki <amot...@gmail.com> wrote: > +1 > Welcome to the team Abhishek! > > 2016-12-14 10:22 GMT+09:00 Armando M. <arma...@gmail.com>: > >> Hi folks, >> >> Abhishek Raut's recent involvement in OSC and python-neu

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

2016-12-15 Thread Armando M.
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

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

2016-12-15 Thread Armando M.
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 Ryan Tidwell and Nate Johnston as service LTs

2016-12-15 Thread Armando M.
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.

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

2016-12-15 Thread Armando M.
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.

Re: [openstack-dev] [neutron] Vlan aware VMs or trunking

2016-12-06 Thread Armando M.
On 6 December 2016 at 08:49, Vasyl Saienko wrote: > Hello Neutron Community, > > > I've found that nice feature vlan-aware-vms was implemented in Newton [0]. > However the usage of this feature for regular users is impossible, unless > I'm missing something. > > As I

Re: [openstack-dev] [neutron] broken rally gate

2016-12-08 Thread Armando M.
On 8 December 2016 at 16:40, Armando M. <arma...@gmail.com> wrote: > Hi folks > > Chasing down why [1] accidentally broke rally. Please do not recheck, and > the failure is persistent. > > Thanks, > Armando > > [1] https://review.openstack.org/#/c/408020 > htt

[openstack-dev] [neutron] broken rally gate

2016-12-08 Thread Armando M.
Hi folks Chasing down why [1] accidentally broke rally. Please do not recheck, and the failure is persistent. Thanks, Armando [1] https://review.openstack.org/#/c/408020 __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [neutron] trunk api performance and scale measurments

2016-12-08 Thread Armando M.
On 5 December 2016 at 07:59, Bence Romsics wrote: > Hi, > > I measured how the new trunk API scales with lots of subports. You can > find the results here: > > https://wiki.openstack.org/wiki/Neutron_Trunk_API_Performance_and_Scaling > > Hope you find it useful. There

[openstack-dev] [neutron] networking-sfc stable/newton branch broken

2017-01-11 Thread Armando M.
Hi, Please have a look at [1]. The branch has been broken for some time now. Thanks, Armando [1] https://review.openstack.org/#/q/status:open+project:openstack/networking-sfc+branch:stable/newton __ OpenStack Development

Re: [openstack-dev] [neutron] Confusion around the complexity

2017-01-13 Thread Armando M.
On 13 January 2017 at 10:47, Clint Byrum wrote: > Excerpts from Joshua Harlow's message of 2017-01-12 22:38:46 -0800: > > Kevin Benton wrote: > > > If you don't want users to specify network details, then use the get me > > > a network extension or just have them boot to a

Re: [openstack-dev] [neutron] Confusion around the complexity

2017-01-13 Thread Armando M.
On 13 January 2017 at 15:01, Clint Byrum <cl...@fewbar.com> wrote: > Excerpts from Armando M.'s message of 2017-01-13 11:39:33 -0800: > > On 13 January 2017 at 10:47, Clint Byrum <cl...@fewbar.com> wrote: > > > > > Excerpts from Joshua Harlow's message of 2017

<    1   2   3   4   5   6   7   >