Re: [openstack-dev] [Openstack-i18n] DocImpact Changes

On 24 November 2015 at 13:11, Lana Brindley wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi Akihiro, > > Judging by most of the bugs we see in the openstack-manuals queue, the > bugs that will be raised in projects' own queues will usually be against

Re: [openstack-dev] [Neutron] Evolving the stadium concept

dy when we will want our processes (at least > in the Neutron world) to be similar and > complimenting. > > Just the way i see things right now.. > > Gal. > > > > > On Tue, Dec 1, 2015 at 9:10 AM, Armando M. <arma...@gmail.com> wrote: > >> >&g

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 1 December 2015 at 03:03, Neil Jerram <neil.jer...@metaswitch.com> wrote: > On 01/12/15 10:42, Thierry Carrez wrote: > > Armando M. wrote: > >> [...] > >> So my question is: would revisiting/clarifying the concept be due after > >> some time we have s

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 1 December 2015 at 02:40, Thierry Carrez <thie...@openstack.org> wrote: > Armando M. wrote: > > [...] > > So my question is: would revisiting/clarifying the concept be due after > > some time we have seen it in action? I would like to think so. > >

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 1 December 2015 at 02:40, Neil Jerram wrote: > On 01/12/15 05:16, Doug Wiegley wrote: > > Part of the issue is that in a year, we added all the repos above. And > > all of said repos were all heading over to infra with the same newbie > > questions/mistakes. Not a

Re: [openstack-dev] [Neutron] Evolving the stadium concept

On 30 November 2015 at 20:47, Doug Wiegley <doug...@parksidesoftware.com> wrote: > > On Nov 30, 2015, at 5:56 PM, Armando M. <arma...@gmail.com> wrote: > > Hi folks, > > The stadium concept was introduced more or less formally since April of > this year. At t

Re: [openstack-dev] [Neutron] Evolving the stadium concept

nstack.org/#/c/244736/ > > Add the Astara driver: > https://review.openstack.org/#/c/230699/ > > Add tap-as-a-service: > https://review.openstack.org/#/c/229869/ > > On 11/30/2015 07:56 PM, Armando M. wrote: > > I would like to suggest that we evolve the st

Re: [openstack-dev] [Neutron] Call for review focus

On 25 November 2015 at 03:09, Rossella Sblendido <rsblend...@suse.com> wrote: > > > On 11/24/2015 06:53 PM, Armando M. wrote: > >> >> >> On 24 November 2015 at 04:13, Rossella Sblendido <rsblend...@suse.com >> <mailto:rsblend...@suse.com>> wr

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 25 November 2015 at 08:42, Sean M. Collins wrote: > The first run for the multinode grenade job completed. > > > http://logs.openstack.org/35/187235/11/experimental/gate-grenade-dsvm-neutron-multinode/011124b/logs/ > > I'm still getting my bearings in the grenade log

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 25 November 2015 at 09:49, Sean M. Collins wrote: > Yeah looks like I read it wrong - the failure occurred during the > initial resource creation phase, based on comparing the logs that Artur > posted. > I see. I got confused by this:

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

reitpro.com] > Sent: Wednesday, November 25, 2015 7:03 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode > partial upgrade > > On Wed, Nov 25, 2015 at 12:53:56PM EST, Armando M. wrote: &

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 25 November 2015 at 10:03, Sean M. Collins <s...@coreitpro.com> wrote: > On Wed, Nov 25, 2015 at 12:53:56PM EST, Armando M. wrote: > > On 25 November 2015 at 09:49, Sean M. Collins <s...@coreitpro.com> > wrote: > > > > > Yeah looks like I read

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 25 November 2015 at 11:33, Armando M. <arma...@gmail.com> wrote: > > > On 25 November 2015 at 10:15, Korzeniewski, Artur < > artur.korzeniew...@intel.com> wrote: > >> Yes, this file is complete fine. The Grenade is running smoke test before >> res

Re: [openstack-dev] [Horizon][Neutron] dashboard repository for neutron subprojects

On 24 November 2015 at 21:46, Akihiro Motoki wrote: > Hi, > > Neutron has now various subprojects and some of them would like to > implement Horizon supports. Most of them are additional features. > I would like to start the discussion where we should have horizon support. > >

Re: [openstack-dev] [Neutron] Call for review focus

On 24 November 2015 at 04:13, Rossella Sblendido <rsblend...@suse.com> wrote: > > > On 11/23/2015 06:38 PM, Armando M. wrote: > >> >> >> On 23 November 2015 at 04:02, Rossella Sblendido <rsblend...@suse.com >> <mailto:rsblend...@suse.com>> wr

Re: [openstack-dev] [release] process change for closing bugs when patches merge

On 23 November 2015 at 13:58, Doug Hellmann wrote: > As part of completing the release automation work and deprecating our > use of Launchpad for release content tracking, we also want make some > changes to the way patches associated with bugs are handled. > > Right now,

Re: [openstack-dev] [Neutron] Call for review focus

On 23 November 2015 at 09:22, Carl Baldwin wrote: > On Mon, Nov 23, 2015 at 5:02 AM, Rossella Sblendido > wrote: > > To cross-reference we can use the bug ID or the blueprint name. > > > > I created a script that queries launchpad to get: > > 1) Bug

Re: [openstack-dev] [Neutron] Call for review focus

On 23 November 2015 at 04:02, Rossella Sblendido <rsblend...@suse.com> wrote: > > > On 11/20/2015 03:54 AM, Armando M. wrote: > >> >> >> On 19 November 2015 at 18:26, Assaf Muller <amul...@redhat.com >> <mailto:amul...@redhat.com>> wrote

Re: [openstack-dev] [Neutron] Bug update

On 19 November 2015 at 23:10, Gary Kotton wrote: > Hi, > There are a ton of old and ancient bugs that have not been trained. If you > guys have some time then please go over them. In most cases some are not > even bugs and are just questions. I have spent the last few days

Re: [openstack-dev] [Neutron] Bug update

On 19 November 2015 at 23:20, Gary Kotton wrote: > Hi, > One extra thing. A large chunk of the latest bugs opened are RFE’s. These > are tagged with ‘rfe’. In addition to this I would suggest changing the > title of the bug to have [RFE]. This will at least help those who are

Re: [openstack-dev] [Neutron] Bug update

On 20 November 2015 at 09:47, John Belamaric <jbelama...@infoblox.com> wrote: > I think Gary got auto-corrected: > > training = triaging > brace = rbac > ah! > > On Nov 20, 2015, at 12:41 PM, Armando M. <arma...@gmail.com> wrote: > > > > On

Re: [openstack-dev] [Neutron] Call for review focus

On 20 November 2015 at 14:07, Kyle Mestery <mest...@mestery.com> wrote: > On Wed, Nov 18, 2015 at 8:14 PM, Armando M. <arma...@gmail.com> wrote: > >> Hi Neutrites, >> >> > Neutrinos? > I am still experimenting to see what sticks...So far I got Neutrin

Re: [openstack-dev] [Neutron] Call for review focus

On 19 November 2015 at 18:26, Assaf Muller <amul...@redhat.com> wrote: > On Wed, Nov 18, 2015 at 9:14 PM, Armando M. <arma...@gmail.com> wrote: > > Hi Neutrites, > > > > We are nearly two weeks away from the end of Mitaka 1. > > > > I am writing this

[openstack-dev] [Neutron] Call for review focus

Hi Neutrites, We are nearly two weeks away from the end of Mitaka 1. I am writing this email to invite you to be mindful to what you review, especially in the next couple of weeks. Whenever you have the time to review code, please consider giving priority to the following: - Patches that

[openstack-dev] [Neutron] Team meeting this Tuesday at 1400 UTC

Hi folks, A kind reminder for tomorrow's meeting. Please add agenda items to the meeting here [1]. Cheers, Armando [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development Mailing List (not for usage

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 13 November 2015 at 11:46, Sean Dague wrote: > On 11/13/2015 01:16 PM, Sean M. Collins wrote: > > On Fri, Nov 13, 2015 at 07:42:12AM EST, Sean Dague wrote: > >> Ok, I top responded with the details of the job, honestly I think it's > >> just a project-config change to get up

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 12 November 2015 at 11:41, Korzeniewski, Artur < artur.korzeniew...@intel.com> wrote: > Hi Sean, > > I’m interested in introducing to Neutron the multinode partial upgrade job > in Grenade. > Great to hear! > > > Can you explain how multinode is currently working in Grenade and how Nova >

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On 12 November 2015 at 20:24, Sean M. Collins wrote: > On Thu, Nov 12, 2015 at 05:55:51PM EST, Ihar Hrachyshka wrote: > > I also believe that the first step to get the job set is making neutron > own > > its grenade future, by migrating to grenade plugin maintained in neutron

Re: [openstack-dev] [Neutron] Stop pushing stuff to the gate queue

On 10 November 2015 at 12:13, Armando M. <arma...@gmail.com> wrote: > Neutron Cores, > > We have high failure rate (see [1] for more context). We have an initial > bug report [2] filed, and more triaged is happening. > > Let's hold on before we push stuff to the gate q

[openstack-dev] [Neutron] Priority management for new features

Hi neutronians, Whilst I recover from the gate failure binge eating...I wanted to put out there a couple of process changes that should help the drivers team and the PTL to improve their ability to justify priority assignments for new features. Comments welcome. Cheers, Armando [1]

Re: [openstack-dev] [Neutron] Priority management for new features

On 11 November 2015 at 13:58, Kyle Mestery <mest...@mestery.com> wrote: > On Wed, Nov 11, 2015 at 4:19 PM, Armando M. <arma...@gmail.com> wrote: > >> Hi neutronians, >> >> Whilst I recover from the gate failure binge eating...I wanted to put out >> the

Re: [openstack-dev] [neutron] [gate] 35% failure rate for neutron tempest jobs

On 10 November 2015 at 09:49, Sean Dague wrote: > The neutron tempest jobs are now at a 35% failure rate: > http://tinyurl.com/ne3ex4v (note, 35% is basically the worst possible > fail rate, because it's just passing enough to land patches that cause > that kind of fail on two

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

On 10 November 2015 at 10:33, Matt Riedemann wrote: > Let me qualify by saying I'm not a Neutron person. > > We know that gate-tempest-dsvm-neutron-full is failing hard as of the last > 24 hours [1]. > > An error that's been showing up in tempest runs with neutron a

Re: [openstack-dev] [neutron] [gate] 35% failure rate for neutron tempest jobs

On 10 November 2015 at 11:11, Sean Dague <s...@dague.net> wrote: > On 11/10/2015 01:37 PM, Armando M. wrote: > > > > > > On 10 November 2015 at 09:49, Sean Dague <s...@dague.net > > <mailto:s...@dague.net>> wrote: > > > > The neutron

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

On 10 November 2015 at 11:12, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > > > On 11/10/2015 1:10 PM, Matt Riedemann wrote: > >> >> >> On 11/10/2015 12:51 PM, Armando M. wrote: >> >>> >>> >>> On 10 November 2015

Re: [openstack-dev] Can we get some sanity in the Neutron logs please?

On 10 November 2015 at 11:10, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > > > On 11/10/2015 12:51 PM, Armando M. wrote: > >> >> >> On 10 November 2015 at 10:33, Matt Riedemann <mrie...@linux.vnet.ibm.com >> <mailto:mrie...@linux.vnet.ibm

[openstack-dev] [Neutron] Stop pushing stuff to the gate queue

Neutron Cores, We have high failure rate (see [1] for more context). We have an initial bug report [2] filed, and more triaged is happening. Let's hold on before we push stuff to the gate queue. Once [2] is solved and the fire is put out, we'll resume the merge frenzy. As a general reminder,

[openstack-dev] [Neutron] Reminder: Team meeting on Monday at 2100 UTC

A kind reminder for next week's meeting. Please add agenda items to the meeting here [1]. Cheers, Armando [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development Mailing List (not for usage questions)

[openstack-dev] [Neutron] Mid-cycle meetup for Mitaka

Hi folks, After some consideration, I am proposing a change for the Mitaka release cycle in relation to the mid-cycle meetup event. My proposal is to defer the gathering to later in the release cycle [1], and assess whether we have it or not based on the course of events in the cycle. If we feel

Re: [openstack-dev] [Neutron][IPAM] Arbitrary JSON blobs in ipam db tables

On 4 November 2015 at 13:21, Shraddha Pandhe wrote: > Hi Salvatore, > > Thanks for the feedback. I agree with you that arbitrary JSON blobs will > make IPAM much more powerful. Some other projects already do things like > this. > > e.g. In Ironic, node has

Re: [openstack-dev] [neutron][stable] should we open gate for per sub-project stable-maint teams?

On 3 November 2015 at 08:49, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi all, > > currently we have a single neutron-wide stable-maint gerrit group that > maintains all stable branches for all stadium subprojects. I believe > that in lots

Re: [openstack-dev] [Infra][Nova][Neutron] 6WIND Networking CI - approval for posting comments

On 30 October 2015 at 23:59, Matt Riedemann <mrie...@linux.vnet.ibm.com> wrote: > > > On 10/30/2015 7:41 AM, Armando M. wrote: > >> >> >> On 30 October 2015 at 18:41, Francesco Santoro >> <francesco.sant...@6wind.com <mailto:francesco.sa

Re: [openstack-dev] [Infra][Nova][Neutron] 6WIND Networking CI - approval for posting comments

; neutron as well? > I would be ok to have this voting for now. Having said that, Mike (cc-ed here) will be working closely with the Neutron team to re-align/improve Neutron 3rd party CI support, so stay tuned for progresses on this front. Cheers, Armando > > Regards, > France

[openstack-dev] [Neutron] IRC weekly meeting

A reminder that we won't have the meeting next week. Safe journey back from Tokyo, for who has travelled to the Summit. Cheers, Armadno __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Infra][Nova][Neutron] 6WIND Networking CI - approval for posting comments

On 30 October 2015 at 02:49, Matt Riedemann wrote: > > > On 10/29/2015 12:13 PM, Francesco Santoro wrote: > >> Dear Infra team, >> >> According to the requirements specified in [1] posting comments on >> patches needs approval from core maintainers of projects. >> >>

Re: [openstack-dev] [neutron][sriov] SRIOV-VM could not work well with normal VM

On 22 October 2015 at 01:21, yujie wrote: > I used ixgbe and vlan, passthrough a VF to vm. > After the VM created, it could not connect to VM on the same compute node > without use sriov. > > Not sure if this is the same conversation happening on Launchpad, but if not, this

[openstack-dev] [Neutron] Summit session on Lighting talks

Hi folks, We currently have the submissions and only 6 slots. There's still some time left before the end of this week. Whoever put an entry in the etherpad [1], please consider adding your name, otherwise we don't know who to reach out during the session [2]. If all things stay the same, we'll

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

Neutron spec process. > No, unless what you are asking are changes to the core. Do you have a reference for me to look at? > > Any opinions on that? > > Gal. > > On Tue, Oct 20, 2015 at 11:10 PM, Armando M. <arma...@gmail.com> wrote: > >> Hi folks, >

Re: [openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

On 21 October 2015 at 02:01, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > > > On 21 Oct 2015, at 05:14, Armando M. <arma...@gmail.com> wrote: > > > > Hi folks, > > > > Henry has been instrumental in many areas of the projects and his crazy >

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On 21 October 2015 at 10:29, Kyle Mestery <mest...@mestery.com> wrote: > On Wed, Oct 21, 2015 at 12:08 PM, Armando M. <arma...@gmail.com> wrote: > >> >> >> On 21 October 2015 at 09:53, Kyle Mestery <mest...@mestery.com> wrote: >> >>> On Wed

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On 21 October 2015 at 09:53, Kyle Mestery <mest...@mestery.com> wrote: > On Wed, Oct 21, 2015 at 11:37 AM, Armando M. <arma...@gmail.com> wrote: > >> >> >> On 21 October 2015 at 04:12, Gal Sagie <gal.sa...@gmail.com> wrote: >> &g

Re: [openstack-dev] [Neutron] Gerrit permissions and Merge rights

On 21 October 2015 at 09:52, Gal Sagie <gal.sa...@gmail.com> wrote: > > > On Wed, Oct 21, 2015 at 7:37 PM, Armando M. <arma...@gmail.com> wrote: > >> >> >> On 21 October 2015 at 04:12, Gal Sagie <gal.sa...@gmail.com> wrote: >&

Re: [openstack-dev] [Neutron][Nova] Trunk port feature (VLAN aware VMs)

On 21 October 2015 at 15:40, Ildikó Váncsa wrote: > Hi Folks, > > During Liberty we started the implementation of the VLAN aware VMs > blueprint (https://review.openstack.org/#/c/94612/). We had quite a good > progress, although we could use some extra hands on

[openstack-dev] [Neutron] Gerrit permissions and Merge rights

Hi folks, During revision of the Neutron teams [1], we made clear that the neutron-specs repo is to be targeted by specs for all the Neutron projects (core + *-aas). For this reason I made sure that the neutron-specs-core team +2 right was extended to all the core teams. Be mindful, use your +2

[openstack-dev] [Neutron] HenryG addition to the Neutron Drivers team

Hi folks, Henry has been instrumental in many areas of the projects and his crazy working hours makes even Kevin and I bow in awe. Jokes aside, I would like to announce HenryG as a new member of the Neutron Drivers team. Having a propension to attendance, and desire to review of RFEs puts you

Re: [openstack-dev] [Neutron] Do not merge until further notice

On 20 October 2015 at 19:46, Takashi Yamamoto <yamam...@midokura.com> wrote: > i missed the "further notice"? > No, you didn't. RC3 released, Liberty released, the world moved on and I didn't think of sending an email. Sorry. > > On Wed, Oct 14, 2015 at 4:07 AM, A

[openstack-dev] [Neutron] Mitaka Design Summit schedule for Neutron

Hi folks, The schedule for the Neutron project is published in [1]. We are still going through/ironing out some details, but for the most part (especially the order of sessions) we should be all set. See you in Tokyo! Cheers, Armando [1]

Re: [openstack-dev] [Neutron] Design Summit Session - Containers Orchestration platforms Integration with Neutron

by bullet, we'll need an entire summit :) Cheers, Armando On 18 October 2015 at 09:14, Armando M. <arma...@gmail.com> wrote: > Gal, > > [2] is not meant to be edited by anyone just yet. This will lead to chaos > and an unproductive session. Once the link is out is obvious that

Re: [openstack-dev] [Neutron] Design Summit Session - Containers Orchestration platforms Integration with Neutron

Gal, [2] is not meant to be edited by anyone just yet. This will lead to chaos and an unproductive session. Once the link is out is obvious that anyone can edit, but welcoming input is a recipe for disaster! I appreciate the initiative, but please consider running thoughts by me for advice.

Re: [openstack-dev] [neutron][stable] proactive backporting

On 16 October 2015 at 10:09, Sean M. Collins wrote: > On Fri, Oct 16, 2015 at 11:36:13AM EDT, Salvatore Orlando wrote: > > It might also make sense to ask contributors to resume the habit of > tagging > > bugs with 'backport-potential' even if not in the RC period. > > I like

[openstack-dev] [Neutron] Design Summit Lighting talks

Folks, The session [1] is planned for Thursday at 3.30pm. If you're interested, please sign up. The time to submit ideas is running out. Cheers, Armando [1] https://etherpad.openstack.org/p/mitaka-neutron-labs-lighting-talks

[openstack-dev] [Neutron] Reminder: Team meeting on Tuesday at 1400 UTC

A kind reminder for next week's meeting. Please add agenda items to the meeting here [1]. We'll cancel the meeting of the week of the summit and the one after that. Also, do not get caught in the switch from daylight savings when we get back to them. Cheers, Armando [1]

Re: [openstack-dev] [Neutron] Revision of the RFE/blueprint submission process

A follow-up... On 13 October 2015 at 18:38, Armando M. <arma...@gmail.com> wrote: > Hi neutrinos, > > From last cycle, the team has introduced the concept of RFE bugs [0]. I > have suggested a number of refinements over the past few days [1,2,3] to > streamline/clarify the

Re: [openstack-dev] [Neutron] Revision of the RFE/blueprint submission process

On 14 October 2015 at 00:17, Flavio Percoco <fla...@redhat.com> wrote: > On 13/10/15 18:38 -0700, Armando M. wrote: > >> Hi neutrinos, >> >> From last cycle, the team has introduced the concept of RFE bugs [0]. I >> have >> suggested a number of

Re: [openstack-dev] [release] establishing release liaisons for mitaka

On 14 October 2015 at 08:25, Doug Hellmann wrote: > As with the other cross-project teams, the release management team > relies on liaisons from each project to be available for coordination of > work across all teams. It's the start of a new cycle, so it's time to > find

[openstack-dev] [Neutron] Functional job instability

Hi folks, There are a number of outstanding stability issues that affect the functional job [1]. No particular bug is a major offender, but taken all together they hurt quite a bit. If we don't get a good handle on this (even on a 'good' day there is a wide gap between the job failure rate and

[openstack-dev] [Neutron] Do not merge until further notice

Hi folks, We are in the last hours of Liberty, let's pause for a second and consider merging patches only if absolutely necessary. The gate is getting clogged and we need to give priority to potential RC3 fixes or gate stability fixes. Thanks, Armando

Re: [openstack-dev] [Neutron] Do not merge until further notice

On 13 October 2015 at 16:55, Hirofumi Ichihara < ichihara.hirof...@lab.ntt.co.jp> wrote: > > > > On 2015/10/14, at 4:07, Armando M. <arma...@gmail.com> wrote: > > > > Hi folks, > > > > We are in the last hours of Liberty, let's pause for a second a

[openstack-dev] [Neutron] Revision of the RFE/blueprint submission process

Hi neutrinos, >From last cycle, the team has introduced the concept of RFE bugs [0]. I have suggested a number of refinements over the past few days [1,2,3] to streamline/clarify the process a bit further, also in an attempt to deal with the focus and breadth of the project [4,5]. Having said

[openstack-dev] [Neutron] liberty stable branch development

Hi folks, A heads-up: we are currently experiencing a number of failures on the stable/liberty for neutron [1]. Bear with us whilst we go through the painstaking process of fixing the dependency issues that caused the recent grief. Thanks, Armando [1]

[openstack-dev] [Neutron] Reminder: Team meeting on Monday at 2100 UTC

A kind reminder for today's meeting. Please add agenda items to the meeting here [1]. See you all in a few hours! Armando [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development Mailing List (not for

[openstack-dev] [neutron] Design Summit schedule - update

Hi folks, As some of you may know, this summit we have 12 fishbowl sessions between Wednesday and Thursday, and a full day on Friday for team get-together. We broke down the 12 sessions in three separate tracks: - https://etherpad.openstack.org/p/mitaka-neutron-core-track -

Re: [openstack-dev] [Neutron] [openstack-infra] stable changes to python-neutronclient unable to merge

On 6 October 2015 at 20:06, Armando M. <arma...@gmail.com> wrote: > Hi folks, > > We are unable to merge stable changes to python-neutronclient (as shown in > [1,2]) because of the missing master fixes [3,4]. We should be able to > untangle Liberty with [5], but to unb

Re: [openstack-dev] [Neutron] Prepare for expiration bugs without activity

On 7 October 2015 at 07:50, Ihar Hrachyshka wrote: > > On 06 Oct 2015, at 19:26, ZZelle wrote: > > > > Hi everyone, > > > > > > As decided during last neutron meeting[1], we try to let Launchpad > expire outdated bugs. > > > > The status of every bug

[openstack-dev] [Neutron] [openstack-infra] stable changes to python-neutronclient unable to merge

Hi folks, We are unable to merge stable changes to python-neutronclient (as shown in [1,2]) because of the missing master fixes [3,4]. We should be able to untangle Liberty with [5], but to unblock Kilo, I may need to squash [6] with a cherry pick of [3] and wait [5] to merge. Please bear with

Re: [openstack-dev] [Neutron] Defect management

On 6 October 2015 at 06:10, Ihar Hrachyshka wrote: > > On 06 Oct 2015, at 10:36, Miguel Angel Ajo wrote: > > > > Hi, I was trying to help a bit, for now, but I don't have access in > launchpad to update importance, > > etc. > > > > I will add comments

[openstack-dev] [Neutron] Effective guide

Hi neutrinos, One of the areas I would like to work on during the Mitaka cycle is 'consistency' [1]. We've grown quite a bit during the last cycle and we need to make sure we are on the same page when it comes to code quality and reviews, and at the same time speeding up review velocity without

[openstack-dev] [Neutron] Remdiner: Team meeting on Tuesday at 1400 UTC

A kind reminder for tomorrow's meeting. Please add agenda items to the meeting here [1]. See you all tomorrow! Armando [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development Mailing List (not for

Re: [openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

see the >> etherpad here [1]. We talked about the idea of creating a validation suite, >> and it sounds like that's something we should again discuss in Tokyo for >> the Mitaka cycle. I think a validation suite would be a great step forward >> for Neutron third-party CI systems

Re: [openstack-dev] [Neutron] Defect management

On 5 October 2015 at 03:14, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > > On 02 Oct 2015, at 02:37, Armando M. <arma...@gmail.com> wrote: > > > > Hi neutrinos, > > > > Whilst we go down the path of revising the way we manage/process bugs in > Neu

Re: [openstack-dev] [Neutron] AZ Support

On 4 October 2015 at 09:19, Gary Kotton wrote: > Hi, > It appears that the addition has broken the vmware_nsx plugin ( > https://review.openstack.org/183369). We are still debugging. Would it be > worthwhile considering adding this support as a feature branch and then > when

Re: [openstack-dev] [Neutron] AZ Support

ut waiting for a reply to message ID f4ed0bd26feb462c9b7b49a6d85caeae > > Now when I use the stable/liberty branch everything is OK > > Ah, I suspect that's your culprit: https://review.openstack.org/#/c/226362/ instead of AZ's initial support. > Thanks > Gary > > From: &q

Re: [openstack-dev] [Neutron] Stable/liberty branches for decomposed plugins

On 4 October 2015 at 09:31, Gary Kotton wrote: > Hi, > When should we start to create a stable/liberty branch for the decomposed > plugins? My understanding is that the plugin should be in line with > Neutron. Changes in Neutron master (now Mitaka) may require plugin changes.

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

On 1 October 2015 at 06:45, Ihar Hrachyshka wrote: > Hi all, > > I talked recently with several contributors about what each of us plans > for the next cycle, and found it’s quite useful to share thoughts with > others, because you have immediate yay/nay feedback, and maybe

Re: [openstack-dev] [neutron] New cycle started. What are you up to, folks?

On 1 October 2015 at 08:42, Sean M. Collins wrote: > On Thu, Oct 01, 2015 at 11:05:29AM EDT, Kyle Mestery wrote: > > On Thu, Oct 1, 2015 at 9:57 AM, Sean M. Collins > wrote: > > > > > On Thu, Oct 01, 2015 at 10:02:24AM EDT, Ihar Hrachyshka wrote: > > > >

Re: [openstack-dev] [Neutron] Defect management

and Google sheets Insights to see how well (or bad) we've done this week. Cheers, Armando [1] https://review.openstack.org/#/c/228733/ [2] https://docs.google.com/spreadsheets/d/1UpxSOsFKQWN0IF-mN0grFJJap-j-8tnZHmG4f3JYmIQ/edit#gid=1296831500 On 28 September 2015 at 23:06, Armando M. <a

Re: [openstack-dev] [neutron] pypi packages for networking sub-projects

On 30 September 2015 at 16:02, Cathy Zhang wrote: > Hi Kyle, > > > > Is this only about the sub-projects that are ready for release? I do not > see networking-sfc sub-project in the list. Does this mean we have done the > pypi registrations for the networking-sfc

[openstack-dev] [Neutron] Defeact management

Hi folks, One of the areas I would like to look into during the Mitaka cycle is 'stability' [1]. The team has done a great job improving test coverage, and at the same time increasing reliability of the product. However, regressions are always around the corner, and there is a huge backlog of

Re: [openstack-dev] [neutron] congrats to armax!

On 25 September 2015 at 17:03, Ryan Moats wrote: > First, congratulations to armax on being elected PTL for Mitaka. Looking > forward to Neutron improving over the next six months. > > Second thanks to everybody that voted in the election. Hopefully we had > something close to

Re: [openstack-dev] [Openstack-operators] [neutron] [nova] Nova Network/Neutron Migration Survey - need response from folks currently using Nova Networks in their deployments

On 28 September 2015 at 18:01, Kruithof, Piet wrote: > There has been a significant response to the Nova Network/Neutron > migration survey. However, the responses are leaning heavily on the side > of deployments currently using Neutron. As a result, we would like

Re: [openstack-dev] [cinder][neutron][all] New third-party-ci testing requirements for OpenStack Compatible mark

On 25 September 2015 at 15:40, Chris Hoge wrote: > In November, the OpenStack Foundation will start requiring vendors > requesting > new "OpenStack Compatible" storage driver licenses to start passing the > Cinder > third-party integration tests. The new program was

Re: [openstack-dev] [neutron][networking-ovn][vtep] Proposal: support for vtep-gateway in ovn

On 24 September 2015 at 09:12, Russell Bryant wrote: > On 09/24/2015 10:18 AM, Salvatore Orlando wrote: > > One particular issue is that the project implements the ovsdb > protocol > > from scratch. The ovs project provides a Python library for this. > Both > >

[openstack-dev] [Neutron] Effective Neutron

Hi fellow developers and reviewers, Some of you may have noticed that I put together patch [1] up for review. The intention of this initiative is to capture/share 'pills of wisdom' when it comes to Neutron development and reviewing. In fact, there are a number of common patterns (or

[openstack-dev] [gate] requirement conflict on Babel breaks grenade jobs

https://bugs.launchpad.net/grenade/+bug/1496650 HTH Armando __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On 15 September 2015 at 16:01, Monty Taylor <mord...@inaugust.com> wrote: > On 09/15/2015 06:16 PM, Armando M. wrote: > >> >> >> On 15 September 2015 at 08:27, Mike Spreitzer <mspre...@us.ibm.com >> <mailto:mspre...@us.ibm.com>> wrote: >>

[openstack-dev] [Neutron] PTL Candidacy

I would like to propose my candidacy for the Neutron PTL. If you are reading this and you know me, then you probably know what I have been up to up until now, what I have done for the project, and what I may continue to do. If you do not know me, and you are still interested in reading, then I

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On 15 September 2015 at 16:08, Monty Taylor <mord...@inaugust.com> wrote: > On 09/15/2015 06:30 PM, Armando M. wrote: > >> >> >> On 15 September 2015 at 08:04, Monty Taylor <mord...@inaugust.com >> <mailto:mord...@inaugust.com>> wrote: >> &g

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On 15 September 2015 at 14:04, Mike Spreitzer <mspre...@us.ibm.com> wrote: > "Armando M." <arma...@gmail.com> wrote on 09/15/2015 03:50:24 PM: > > > On 15 September 2015 at 10:02, Doug Hellmann <d...@doughellmann.com> > wrote: > > Excerpts from

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On 15 September 2015 at 15:11, Mathieu Gagné wrote: > On 2015-09-15 2:00 PM, Fox, Kevin M wrote: > > We run several clouds where there are multiple external networks. the > "just run it in on THE public network" doesn't work. :/ > > > > I also strongly recommend to users to

Re: [openstack-dev] [nova][neutron][devstack] New proposed 'default' network model

On 15 September 2015 at 08:04, Monty Taylor wrote: > Hey all! > > If any of you have ever gotten drunk with me, you'll know I hate floating > IPs more than I hate being stabbed in the face with a very angry fish. > > However, that doesn't really matter. What should matter

<    1   2   3   4   5   6   7   >