Re: [openstack-dev] [security] [salt] Removal of Security and OpenStackSalt project teams from the Big Tent

On Wed, Sep 21, 2016 at 3:35 PM, Thierry Carrez wrote: > Chivers, Doug wrote: >> My concern is with the original wording “The suggested way forward there >> would be to remove the "Security project team"”. >> >> This seems like a move to instantly reduce investment in

Re: [openstack-dev] [all][tc] Require a level playing field for OpenStack projects

On Tue, Jun 14, 2016 at 9:15 AM, Doug Hellmann wrote: > Excerpts from Thierry Carrez's message of 2016-06-14 15:57:10 +0200: >> Hi everyone, >> >> I just proposed a new requirement for OpenStack "official" projects, >> which I think is worth discussing beyond the governance

Re: [openstack-dev] [neutron][networking-ovn] OVN vs. OpenDayLight

On Thu, Jun 9, 2016 at 4:19 PM, Assaf Muller <as...@redhat.com> wrote: > On Thu, Jun 9, 2016 at 5:06 PM, Kyle Mestery <mest...@mestery.com> wrote: >> On Thu, Jun 9, 2016 at 2:11 PM, Assaf Muller <as...@redhat.com> wrote: >>> On Thu, Jun 9, 2016 at 1:4

Re: [openstack-dev] [neutron][networking-ovn] OVN vs. OpenDayLight

On Thu, Jun 9, 2016 at 2:11 PM, Assaf Muller wrote: > On Thu, Jun 9, 2016 at 1:48 PM, Ben Pfaff wrote: >> On Thu, Jun 09, 2016 at 10:28:31AM -0700, rezroo wrote: >>> I'm trying to reconcile differences and similarities between OVN and >>> OpenDayLight in my head.

Re: [openstack-dev] [Neutron][Release] Changing release model for *-aas services

On Tue, May 31, 2016 at 1:12 PM, Armando M. wrote: > Hi folks, > > Having looked at the recent commit volume that has been going into the *-aas > repos, I am considering changing the release model for neutron-vpnaas, > neutron-fwaas, neutron-lbaas from

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

gt;> The IETF is already last call and open source support ??? >> >> Thx >> >> Uri (“Oo-Ree”) >> C: 949-378-7568 >> >> >> -Original Message- >> From: Kyle Mestery [mailto:mest...@mestery.com] >> Sent: Wednesday, May 25, 2016 1:00

Re: [openstack-dev] [Neutron] support of NSH in networking-SFC

On Wed, May 25, 2016 at 2:29 PM, Elzur, Uri wrote: > Armando > > > > I’m asking for a clear answer “I think the position here is as follows: if a > technology is not mainstream, i.e. readily available via distros and the > various channels, it can only be integrated via an

Re: [openstack-dev] [neutron][stable] proposing Brian Haley for neutron-stable-maint

+1 (Also +1 for Cedric). On Tue, May 17, 2016 at 6:07 AM, Ihar Hrachyshka wrote: > Hi stable-maint-core and all, > > I would like to propose Brian for neutron specific stable team. > > His stats for neutron stable branches are (last 120 days): > > mitaka: 19 reviews;

Re: [openstack-dev] [neutron][devstack] State of the refactor

On Thu, May 5, 2016 at 11:12 AM, Monty Taylor wrote: > On 05/05/2016 10:57 AM, Sean M. Collins wrote: >> >> During the Austin summit, there was a discussion in the QA meetings >> about the future of Neutron's support in DevStack. It's been an ongoing >> effort, and I'd like

Re: [openstack-dev] [neutron][tc] Neutron stadium evolution from Austin

On Mon, May 2, 2016 at 12:22 PM, Armando M. wrote: > > > On 30 April 2016 at 14:24, Fawad Khaliq wrote: >> >> Hi folks, >> >> Hope everyone had a great summit in Austin and got back safe! :) >> >> At the design summit, we had a Neutron stadium evolution

Re: [openstack-dev] [neutron] Social at the summit

nding the > perfect venue for your event.” > > Are we trying to find some other spot, or just keep Bangers and we will see? > > Darek > >> On Apr 26, 2016, at 8:27 PM, Kyle Mestery <mest...@mestery.com> wrote: >> >> I propose we meet at Bangers on Raine

Re: [openstack-dev] [neutron] Social at the summit

I propose we meet at Bangers on Rainey St. at 6PM. I don't have a reservation but it should be able to hold 50+ people. See y'all at 6PM Thursday! Kyle > On Apr 25, 2016, at 1:07 PM, Kyle Mestery <mest...@mestery.com> wrote: > > OK, there is enough interest, I'll find a plac

Re: [openstack-dev] [neutron] Social at the summit

>> >> WAT??? >> >> >> >> It was never supposed to be core only. Everyone is welcome! >> > >> > +2 >> > >> > irony intended. >> > >> > Socials are not controlled by gerrit ACLs. :-) >> > >> >

[openstack-dev] [neutron] Social at the summit

Ihar, Henry and I were talking and we thought Thursday night makes sense for a Neutron social in Austin. If others agree, reply on this thread and we'll find a place. Thanks! Kyle __ OpenStack Development Mailing List (not

Re: [openstack-dev] [neutron][api] advanced search criteria

On Mon, Apr 4, 2016 at 7:36 PM, Armando M. wrote: > > > On 4 April 2016 at 17:08, Jay Pipes wrote: >> >> On 04/04/2016 06:57 PM, Ihar Hrachyshka wrote: >>> >>> - why do we even need to control those features with configuration >>> options? can we deprecate

Re: [openstack-dev] [Neutron][networking-ovn] Changing OVN plugin release model for Newton

On Mon, Apr 4, 2016 at 8:15 AM, Russell Bryant wrote: > Hello, everyone. > > While bootstrapping networking-ovn, the release model has been > "release:independent" [1], though we haven't actually made any releases. > This follows the state of OVN itself, which is still fast

Re: [openstack-dev] [neutron] Mitaka Mid-Cycle Coding Sprint Registration

On Mon, Feb 15, 2016 at 10:33 AM, Anita Kuno <ante...@anteaya.info> wrote: > On 02/15/2016 04:06 PM, Kyle Mestery wrote: >> Hi folks! >> >> The mid-cycle is almost upon us. IBM, as the sponsor company, is >> requesting some information from everyone is regist

[openstack-dev] [neutron] Mitaka Mid-Cycle Coding Sprint Registration

Hi folks! The mid-cycle is almost upon us. IBM, as the sponsor company, is requesting some information from everyone is registered (name, email, company, US citizen or not), so please make sure to register on the Eventbrite site I've created here [1]. If everyone who's attending could please do

Re: [openstack-dev] [neutron][stable] Request to do stable point releases more often if there are going to be a lot of backports

On Tue, Feb 9, 2016 at 10:10 AM, Matt Riedemann wrote: > While reviewing the neutron 7.0.2 stable/liberty point release, I noticed > there were a lot of changes since 7.0.1. [1] > > There are 48 non-merge commits by my count. > > While there is no rule about how many

Re: [openstack-dev] [neutron][ipam][networking-infoblox][release] release:independent branching strategies

On Fri, Feb 5, 2016 at 10:50 AM, John Belamaric wrote: > Hi all, > > Back in November, there was a discussion [1] on the mailing list around > release:independent projects, which was wrapped up by Thierry in [2]. > However, I have a couple lingering questions that have

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

On Thu, Feb 4, 2016 at 1:33 AM, Gal Sagie wrote: > As i have commented on the patch i will also send this to the mailing list: > > I really dont see why Dragonflow is not part of this list, given the > criteria you listed. > > Dragonflow is fully developed under

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

On Tue, Jan 19, 2016 at 10:14 AM, Ihar Hrachyshka wrote: > Rossella Sblendido wrote: > >> >> >> On 01/19/2016 04:36 PM, Miguel Angel Ajo Pelayo wrote: >>> >>> Thinking of this, I had another idea, a bit raw yet. >>> >>> But how does it sound to have two

Re: [openstack-dev] [release] Release countdown for week R-11, Jan 18-22, Mitaka-2 milestone

On Fri, Jan 15, 2016 at 7:55 AM, Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2016-01-14 16:20:54 -0500: > > Focus > > - > > > > Next week is the second milestone for the Mitaka cycle. Major feature > > work should be making good progress or be

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

On Wed, Jan 13, 2016 at 12:01 PM, Armando M. <arma...@gmail.com> wrote: > > > On 12 January 2016 at 20:07, Kyle Mestery <mest...@mestery.com> wrote: > >> On Tue, Jan 12, 2016 at 5:28 PM, Doug Wiegley < >> doug...@parksidesoftware.com> wrote: >>

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

On Tue, Jan 12, 2016 at 5:28 PM, Doug Wiegley wrote: > I don’t think it ninja merged. It had plenty of reviews, and was open > during international hours. I don’t have any issue there. > > I don’t like the crazy early meeting, so I set out to prove it didn’t >

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

On Mon, Jan 11, 2016 at 12:57 PM, Kyle Mestery <mest...@mestery.com> wrote: > On Mon, Jan 11, 2016 at 12:45 PM, Armando M. <arma...@gmail.com> wrote: > >> Disregard the email subject. >> >> I stand corrected. Let's meet today. >> >> > Something

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

On Mon, Jan 11, 2016 at 12:45 PM, Armando M. wrote: > Disregard the email subject. > > I stand corrected. Let's meet today. > > Something is wrong, I have the meeting on my google calendar, and it shows up as tomorrow for this week. I've had these setup as rotating for a while

Re: [openstack-dev] [devstack] [neutron] Procedure for back-porting a bug fix to stable/liberty branch of a Neutron script in DevStack?

On Sun, Jan 3, 2016 at 5:22 PM, Mike Spreitzer <mspre...@us.ibm.com> wrote: > > From: Kyle Mestery <mest...@mestery.com> > > To: "OpenStack Development Mailing List (not for usage questions)" > > <openstack-dev@lists.openstack.org> > > Date:

Re: [openstack-dev] [devstack] [neutron] Procedure for back-porting a bug fix to stable/liberty branch of a Neutron script in DevStack?

On Sun, Jan 3, 2016 at 4:01 PM, Mike Spreitzer wrote: > I would like to back-port https://review.openstack.org/#/c/242721/--- > which fixed https://bugs.launchpad.net/devstack/+bug/1469596--- to > stable/liberty. I have contributed to main line development before, but > not

Re: [openstack-dev] [neutron][taas] neutron ovs-agent deletes taas flows

On Tue, Dec 15, 2015 at 9:11 AM, Assaf Muller wrote: > SFC are going to hit this issue as well. Really any out of tree > Neutron project that extends the OVS agent and expects things to work > :) > > Yes, this is the case. > On Tue, Dec 15, 2015 at 9:30 AM, Ihar Hrachyshka

[openstack-dev] [kuryr] Release Notes for Kuryr

Howdy Kuryr developers! Like other OpenStack projects, I've added the functionality to use release notes with Kuryr. Once [1] merges, we can add release notes in the "releasenotes/notes" directory. I encourage everyone who has added a feature item to Kuryr to please add a release note for that

Re: [openstack-dev] Fwd: [Neutron] Team meeting this Monday at 2100 UTC

On Tue, Dec 8, 2015 at 1:54 AM, Smigiel, Dariusz wrote: > > > -Original Message- > > From: Kevin Benton [mailto:blak...@gmail.com] > > > > I liked using the meeting for it because it was a nice way for everyone > to get > > a snapshot of where each thing was

Re: [openstack-dev] [Neutron] Rename tenant to project: discussion

On Fri, Dec 4, 2015 at 1:28 PM, Henry Gessau wrote: > Kevin Benton wrote: > > So obviously the stuff in the client can be updated since most of that is > > user-facing. However, on the server side maybe we can start out by > keeping all > > of the internal

Re: [openstack-dev] [neutron][all] when can we drop XML support in neutronclient? Now?

On Thu, Dec 3, 2015 at 7:59 AM, Akihiro Motoki wrote: > Hi, > > python-neutronclient still has XML support of Neutron API. > I would like to discuss when we drop XML support in neutronclient. > > Neutron API XML suppoort was marked as deprecated in Icehouse and Juno > and was

Re: [openstack-dev] [neutron] Release Notes for *aaS projects

OK, thanks for the input. I'll get the patches out to enable this by Friday this week, once Mitaka-1 is cut for Neutron. On Wed, Dec 2, 2015 at 11:34 AM, Brandon Logan <brandon.lo...@rackspace.com> wrote: > Makes complete sense. > > On Wed, 2015-12-02 at 10:38 -0600, Kyl

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

On Wed, Nov 25, 2015 at 1:06 AM, Armando M. wrote: > > > 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

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

On Wed, Nov 18, 2015 at 8:14 PM, Armando M. wrote: > Hi Neutrites, > > Neutrinos? > 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

Re: [openstack-dev] [neutron][networking-sfc] Deploying current networking-sfc

On Mon, Nov 16, 2015 at 4:03 PM, Russell Bryant wrote: > On 11/16/2015 01:42 PM, Sean M. Collins wrote: > > On Mon, Nov 16, 2015 at 04:11:42PM EST, Paul Carver wrote: > >> This is a challenge. Personally, I haven't been able to get it all > working > >> yet. But we're in a

Re: [openstack-dev] [neutron][vpnaas] VPNaaS project status

On Thu, Nov 12, 2015 at 9:56 AM, Paul Michali wrote: > Neutron community, > > During the past several releases, while leading the VPNaaS project, I've > seen many great enhancements and features added to the VPNaaS project by > the community, including support for StrongSwan,

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

On Wed, Nov 11, 2015 at 4:19 PM, Armando M. wrote: > 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

Re: [openstack-dev] [neutron] [networking-powervm] Please create networking-powervm on PyPI

ct is now up [1] with the openstackci > user set > appropriately. Let me know if you need anything else. > > [1] https://pypi.python.org/pypi/networking-powervm > > Regards, > > Adam Reznechek > > > From: Kyle Mestery <mest...@mestery.com> > To: &qu

Re: [openstack-dev] [networking-onos]: Proposing new cores for networking-onos

+1 for both. On Thu, Nov 5, 2015 at 7:00 AM, Gal Sagie wrote: > +1 for both from me > > On Thu, Nov 5, 2015 at 2:53 PM, Vikram Choudhary > wrote: > >> Hi All, >> >> I would like to propose Mr. Ramanjaneya Reddy Palleti and Mr. Dongfeng as >> new cores

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

On Thu, Nov 5, 2015 at 10:55 AM, Jay Pipes wrote: > On 11/04/2015 04:21 PM, 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 >>

Re: [openstack-dev] [neutron] [networking-powervm] Please createnetworking-powervm on PyPI

I can remove the WIP on the patch below. Thanks! > > Thanks! > > Drew Thorstensen > Power Systems / Cloud Software > > > > From:Kyle Mestery <mest...@mestery.com> > To:"OpenStack Development Mailing List (not for usage questions)&quo

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

On Tue, Nov 3, 2015 at 10:49 AM, 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

[openstack-dev] [neutron] [networking-powervm] Please create networking-powervm on PyPI

I'm reaching out to whoever owns the networking-powervm project [1]. I have a review out [2] which updates the PyPI publishing jobs so we can push releases for networking-powervm. However, in looking at PyPI, I don't see a networking-powervm project, but instead a neutron-powervm project. Is there

Re: [openstack-dev] Neutron sub-project release association with Liberty?

On Fri, Oct 30, 2015 at 4:05 AM, Vadivel Poonathan < vadivel.openst...@gmail.com> wrote: > Hi, > > Once the Neutron's sub-project is released to pyPI, where does it show > that this sub-project release is associated with Liberty release of > Openstack?.. I tried to see it in the Liberty Release

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

On Wed, Oct 21, 2015 at 11:37 AM, Armando M. wrote: > > > On 21 October 2015 at 04:12, Gal Sagie wrote: > >> Do we also want to consider Project Kuryr part of this? >> > > No, why would we? > > The reason to consider it is because Kuryr is a sub-project

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

On Wed, Oct 21, 2015 at 12:34 PM, Armando M. <arma...@gmail.com> wrote: > > > 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: >> >>> >

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

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, Oct 21, 2015 at 11:37 AM, Armando M. <arma...@gmail.com> wrote: >> >>> >

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

On Wed, Oct 21, 2015 at 4:01 AM, Ihar Hrachyshka wrote: > > > On 21 Oct 2015, at 05:14, Armando M. wrote: > > > > 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.

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

On Wed, Oct 21, 2015 at 6:12 AM, Gal Sagie wrote: > Do we also want to consider Project Kuryr part of this? > We already started sending Kuryr spec to the Neutron repository and I > think it would make sense to manage it > as part of Neutron spec process. > > Any opinions on

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

On Sun, Oct 18, 2015 at 1:54 PM, Murali R wrote: > Will there be an irc opened for these sessions to join remotely? > > We will have people in the room who will be on IRC, yes, just use #openstack-neutron. Even better, you can comment on the etherpad live while the session

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

On Fri, Oct 16, 2015 at 7:33 AM, Ihar Hrachyshka wrote: > Hi all, > > I’d like to introduce a new initiative around stable branches for neutron > official projects (neutron, neutron-*aas, python-neutronclient) that is > intended to straighten our backporting process and make

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

On Thu, Oct 15, 2015 at 7:03 AM, Neil Jerram wrote: > On 02/10/15 12:33, Neil Jerram wrote: > > On 02/10/15 11:42, Neil Jerram wrote: > >> Thanks Kyle! I'm looking at this now for networking-calico. > > Done, please see https://pypi.python.org/pypi/networking-calico.

Re: [openstack-dev] From where will start particiption in Neutron Component?

On Tue, Oct 13, 2015 at 1:41 AM, Neil Jerram wrote: > On 13/10/15 08:45, chandraprakash mishra wrote: > > Hi Folks, > > > > I have just started looking OpenStack ,As of now i would like to start > > participation for neutron component . So where can i start

Re: [openstack-dev] [all] Recording little everyday OpenStack successes

On Fri, Oct 9, 2015 at 8:52 AM, Russell Bryant wrote: > On 10/09/2015 05:42 AM, Thierry Carrez wrote: > > Hello everyone, > > > > OpenStack has become quite big, and it's easier than ever to feel lost, > > to feel like nothing is really happening. It's more difficult than

Re: [openstack-dev] [Neutron] L2 gateway project

On Fri, Oct 9, 2015 at 10:13 AM, Gary Kotton wrote: > Hi, > Who will be creating the stable/liberty branch? > Thanks > Gary > > I'll be doing this once someone from the L2GW team lets me know a commit SHA to create it from. Thanks, Kyle >

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

On Fri, Oct 2, 2015 at 6:33 AM, Neil Jerram wrote: > On 02/10/15 11:42, Neil Jerram wrote: > > Thanks Kyle! I'm looking at this now for networking-calico. > > Done, please see https://pypi.python.org/pypi/networking-calico. > > When you release, how will the version

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

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: > > - more changes with less infra tinkering! neutron devs should not need > to go to infra projects so often to make an impact; > > -- make our little neat

Re: [openstack-dev] [Neutron] Release of a neutron sub-project

On Tue, Sep 29, 2015 at 8:04 PM, Kyle Mestery <mest...@mestery.com> wrote: > On Tue, Sep 29, 2015 at 2:36 PM, Vadivel Poonathan < > vadivel.openst...@gmail.com> wrote: > >> Hi, >> >> As per the Sub-Project Release process - i would like to tag and relea

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

Folks: In trying to release some networking sub-projects recently, I ran into an issue [1] where I couldn't release some projects due to them not being registered on pypi. I have a patch out [2] which adds pypi publishing jobs, but before that can merge, we need to make sure all projects have

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

rista in the second > category? > Please advise. > > Thanks > -Sukhdev > > > [1] - jenkins/jobs/projects.yaml > <https://review.openstack.org/#/c/229564/1/jenkins/jobs/projects.yaml> > [2] - zuul/layout.yaml > <https://review.openstack.org/#/c/229564/1/zu

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

on. The release of networking-sfc would appear to be pretty early at this point. Once the patches land and the team has some confidence in the API and it's testing status, we'll look at releasing it. Thanks! Kyle > Cheers, > Armando > > [1] > https://review.openstack.org/#/q/status:ope

[openstack-dev] [election] [TC] TC Candidacy

the TC for the next two cycles! Thank you! -- Kyle Mestery IRC: mestery [1] http://docs.openstack.org/project-team-guide/ [2] http://www.meetup.com/Minnesota-OpenStack-Meetup/ [3] http://docs.openstack.org/project-team-guide/in

Re: [openstack-dev] [Neutron] Release of a neutron sub-project

On Tue, Sep 29, 2015 at 2:36 PM, Vadivel Poonathan < vadivel.openst...@gmail.com> wrote: > Hi, > > As per the Sub-Project Release process - i would like to tag and release > the following sub-project as part of upcoming Liberty release. > The process says talk to one of the member of

Re: [openstack-dev] [all] -1 due to line length violation in commit messages

On Mon, Sep 28, 2015 at 4:00 PM, Assaf Muller wrote: > > > On Mon, Sep 28, 2015 at 12:40 PM, Zane Bitter wrote: > >> On 28/09/15 05:47, Gorka Eguileor wrote: >> >>> On 26/09, Morgan Fainberg wrote: >>> As a core (and former PTL) I just ignored commit

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

The Neutron team also discussed this in Vancouver, you can 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

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On Thu, Sep 17, 2015 at 10:26 AM, Monty Taylor wrote: > On 09/17/2015 04:50 PM, Anita Kuno wrote: > >> On 09/17/2015 08:22 AM, Matt Riedemann wrote: >> >>> >>> >>> On 9/17/2015 8:25 AM, Tristan Cacqueray wrote: >>> PTL Nomination is now over. The official candidate

Re: [openstack-dev] [Neutron] Effective Neutron

On Thu, Sep 17, 2015 at 10:20 AM, Armando M. wrote: > 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

Re: [openstack-dev] [all][elections] PTL nomination period is now over

On Thu, Sep 17, 2015 at 3:19 PM, Anne Gentle wrote: > > > On Thu, Sep 17, 2015 at 3:15 PM, John Griffith > wrote: > >> >> >> On Thu, Sep 17, 2015 at 2:00 PM, Doug Hellmann >> wrote: >> >>> Excerpts from Morgan

Re: [openstack-dev] [relmgt] PTL non-candidacy

On Wed, Sep 16, 2015 at 4:33 AM, Thierry Carrez wrote: > Hi everyone, > > I have been handling release management for OpenStack since the > beginning of this story, well before Release Management was a program or > a project team needing a proper elected PTL. Until

Re: [openstack-dev] [neutron][lbaas] Proposing Michael Johnson for neutron-lbaas core team

+1 On Wed, Sep 16, 2015 at 5:33 PM, Doug Wiegley wrote: > Hi all, > > As the Lieutenant of the advanced services, I nominate Michael Johnson to > be a member of the neutron-lbaas core reviewer team. > > Review stats are in line with other cores[2], and Michael has

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

That's exactly right, and we need to get this merged early in Mitaka. We'll discuss this in a design summit session in Tokyo in fact to ensure it's resourced correctly and continues to address the evolving needs in this space. On Tue, Sep 15, 2015 at 10:47 AM, Doug Wiegley

Re: [openstack-dev] [neutron] PTL Non-Candidacy

On Sat, Sep 12, 2015 at 12:32 PM, Ben Pfaff <b...@nicira.com> wrote: > Are you planning to remain involved with OpenStack? > > Yes, that's the plan! > On Fri, Sep 11, 2015 at 2:12 PM, Kyle Mestery <mest...@mestery.com> wrote: > > I'm writing to let everyone

Re: [openstack-dev] [Neutron] Allow for per-subnet dhcp options

On Fri, Sep 11, 2015 at 2:04 PM, Jonathan Proulx wrote: > I'm hurt that this blue print has seen no love in 18 months: > https://blueprints.launchpad.net/neutron/+spec/dhcp-options-per-subnet > > This BP has no RFE bug or spec filed for it, so it's hard to be on anyone's

[openstack-dev] [neutron] PTL Non-Candidacy

I'm writing to let everyone know that I do not plan to run for Neutron PTL for a fourth cycle. Being a PTL is a rewarding but difficult job, as Morgan recently put it in his non-candidacy email [1]. But it goes further than that for me. As Flavio put it in his post about "Being a PTL" [2], it's a

Re: [openstack-dev] [all] Something about being a PTL

Flavio, thanks for sending this out. I agree with everything you've written below. Having served as PTL for 3 cycles now, I can say it's very rewarding, but it's also very exhausting and takes an incredibly thick skin. Before jumping in and throwing your hat into the ring (especially for a large

[openstack-dev] [neutron] Mitaka Design Summit ideas

Folks: It's that time of the cycle again! Lets start collecting ideas for our design summit in Tokyo at the etherpad located here [1]. We'll discuss these a bit in some upcoming meetings and ensure we have a solid schedule to fill our 12 fishbowl slots in Tokyo. Thanks! Kyle [1]

Re: [openstack-dev] [neutron] pushing changes through the gate

I would like to second everything Armando has said below. Please, Neutron core reviewers, follow the advice below for the rest of the Liberty cycle as we work to merge patches targeted at Liberty. I'd also like to thank Armando for jumping in and running things the past week while I was on a

[openstack-dev] [neutron] FFE process for Liberty

Folks, Armando did a great job targeting things which missed Liberty-3 towards Liberty-RC1 here [1]. For the most part, I hope most of those will land in the coming week or so, so lets work as a team to land those. For things which are not already targeted there (or were targeted by someone else,

Re: [openstack-dev] [neutron][sfc] Neutron stadium distribution and/or packaging

On Fri, Aug 28, 2015 at 8:07 AM, Ihar Hrachyshka ihrac...@redhat.com wrote: On 28 Aug 2015, at 14:08, Paul Carver pcar...@paulcarver.us wrote: Has anyone written anything up about expectations for how Big Tent or Neutron Stadium projects are expected to be installed/distributed/packaged?

[openstack-dev] [neutron] Core Reviewer participation in the weekly meeting

I'm sending out this email to encourage Neutron core reviewers to attend and participate in the weekly Neutron team meeting [1]. Attendance from core reviewers has been very low for a while now, and this is the one time each week (or bi-weekly if you attend only one of the rotating meeting) I have

[openstack-dev] [neutron] Pecan and Liberty-3

Folks: Kevin wants to merge the pecan stuff, and I agree with him. I'm on vacation next week during Liberty-3, so Armando, Carl and Doug are running the show while I'm out. I would guess that if Kevin thinks it's ok to merge it in before Liberty-3, I'd go with his opinion and let it happen. If

Re: [openstack-dev] [neutron][api] - attaching arbitrary key/value pairs to resources

On Mon, Aug 24, 2015 at 2:43 PM, Russell Bryant rbry...@redhat.com wrote: On 08/24/2015 05:25 PM, Doug Wiegley wrote: I took advantage of it to prototype a feature her That right there is the crux of the objections so far. Don’t get me wrong, I’d love this, and would abuse it within an

Re: [openstack-dev] [neutron] RFE for DHCP agent changes for networking-calico

Thanks Neil, we'll review this during the drivers meeting this week. It's getting late in the Liberty cycle, but if you can get Brian, Cedric and Carl to review this and ensure they are onboard, this is the best way to move forward. Ensuring the L3 team is ok with the direction would make me

Re: [openstack-dev] [neutron] I am pleased to propose two new Neutron API/DB/RPC core reviewers!

It's been over a week, so I'd like to welcome Brandon and Russell to the API/DB/RPC team in Neutron! Kyle On Wed, Aug 12, 2015 at 6:45 AM, Kyle Mestery mest...@mestery.com wrote: It gives me great pleasure to propose Russell Bryant and Brandon Logan as core reviewers in the API/DB/RPC area

Re: [openstack-dev] [nova] [libvirt-vif] Extend vhost-user interface to support Cisco Nexus 1000v.

On Tue, Aug 18, 2015 at 11:48 AM, Kiran Chunduri kiran.askl...@gmail.com wrote: Hello All, We would like to extend the nova 'vhost-user' plug API to attach the port to Cisco Nexus 1000v, which supports vhost-user interface. Currently the plug-API supports attaching to OVS. The code I'm

Re: [openstack-dev] [Neutron] revert default review branch to master

On Mon, Aug 17, 2015 at 5:58 PM, Jeremy Stanley fu...@yuggoth.org wrote: On 2015-08-17 22:39:56 + (+), Mooney, Sean K wrote: [...] Assuming this was not intentional I have opened a bug and submitted a patch to revert this change. [...] Fix https://review.openstack.org/213843 is

Re: [openstack-dev] [neutron][vmware][stable] vmware-nsx has no releases

On Mon, Aug 17, 2015 at 7:42 AM, Jeremy Stanley fu...@yuggoth.org wrote: On 2015-08-17 14:05:38 +0200 (+0200), Ihar Hrachyshka wrote: [...] I tried to follow the dumb way of generating a tarball from github, but pbr complains about lack of sdist or git when I call to 'setup.py build'.

Re: [openstack-dev] [neutron][qos] request to merge feature/qos back into master

I've pushed the patch into the merge queue now. Any nits people find at this point we'll address post merge. Awesome work QoS team! On Mon, Aug 17, 2015 at 9:56 AM, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 So the patch in question sit there

Re: [openstack-dev] [neutron][vmware][stable] vmware-nsx has no releases

On Mon, Aug 17, 2015 at 7:05 AM, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi VmWare folks, I wonder whether we can get some actual release tags for stable/kilo branch of the repo. Lack of any consumable tarballs does not help packagers

Re: [openstack-dev] [neutron] What does being a neutron-core member mean? [WAS: Re: [neutron] I am pleased to propose two new Neutron API/DB/RPC core reviewers!]

with the current nomination run, so I spin it into a separate thread. Absolutely! I think it's super healthy to have these discussions, it's what healthy open source communities do. I'll answer your specific concerns below. Some comments inline. On 08/12/2015 07:16 PM, Kyle Mestery wrote: [1] http

Re: [openstack-dev] [neutron] What does being a neutron-core member mean? [WAS: Re: [neutron] I am pleased to propose two new Neutron API/DB/RPC core reviewers!]

be if this very public thread involved myself. That being said, please know that from my perspective this is *not* personal, rather I see this as a general discussion about the precedent that we are creating here. Responses in-line. On Fri, Aug 14, 2015 at 9:32 AM, Kyle Mestery mest...@mestery.com

Re: [openstack-dev] [neutron] What does being a neutron-core member mean? [WAS: Re: [neutron] I am pleased to propose two new Neutron API/DB/RPC core reviewers!]

said, please know that from my perspective this is *not* personal, rather I see this as a general discussion about the precedent that we are creating here. Responses in-line. On Fri, Aug 14, 2015 at 9:32 AM, Kyle Mestery mest...@mestery.com wrote: On Fri, Aug 14, 2015 at 6:29 AM, Ihar

Re: [openstack-dev] [neutron][kuryr][magnum] Design Specification for Kuryr

On Thu, Aug 13, 2015 at 1:56 PM, Adrian Otto adrian.o...@rackspace.com wrote: Kyle, Can we please arrange for an official design specification for Kuyyr so members of the Magnum team can relay input to be sure that our mutual interests in this work are addressed? I agree 100%. See Gals

Re: [openstack-dev] [neutron] Liberty-3 BPs and gerrit topics

something? You will be required to login to gerrit to view it, the dashboard makes use of your login ID, for example to not show you patches which you have proposed. :) Cheers, Dani On Tue, Aug 11, 2015 at 2:44 PM, Kyle Mestery mest...@mestery.com wrote: Folks: To make reviewing all approved

Re: [openstack-dev] [neutron] Liberty-3 BPs and gerrit topics

On Tue, Aug 11, 2015 at 8:44 AM, Kyle Mestery mest...@mestery.com wrote: Folks: To make reviewing all approved work for Liberty-3 in Neutron easier, I've created a handy dandy gerrit dashboard [1]. What will make this even more useful is if everyone makes sure to set their topics

[openstack-dev] [neutron] I am pleased to propose two new Neutron API/DB/RPC core reviewers!

It gives me great pleasure to propose Russell Bryant and Brandon Logan as core reviewers in the API/DB/RPC area of Neutron. Russell and Brandon have both been incredible contributors to Neutron for a while now. Their expertise has been particularly helpful in the area they are being proposed in.

Re: [openstack-dev] [neutron] I am pleased to propose two new Neutron API/DB/RPC core reviewers!

On Wed, Aug 12, 2015 at 10:54 AM, Ihar Hrachyshka ihrac...@redhat.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 08/12/2015 03:45 PM, Kyle Mestery wrote: It gives me great pleasure to propose Russell Bryant and Brandon Logan as core reviewers in the API/DB/RPC area

  1   2   3   4   5   6   7   >