[openstack-dev] [neutron] Feature Proposal Freeze is 9 days away

Just a reminder that Neutron observes FPF [1], and it's 9 days away. We have an incredible amount of BPs which do not have code submitted yet. My suggestion to those who own one of these BPs would be to think hard about whether or not you can realistically land this code in Juno before jamming thin

Re: [openstack-dev] [nova] Retrospective veto revert policy

On Tue, Aug 12, 2014 at 9:56 AM, Mark McLoughlin wrote: > Hey > > (Terrible name for a policy, I know) > > From the version_cap saga here: > > https://review.openstack.org/110754 > > I think we need a better understanding of how to approach situations > like this. > > Here's my attempt at docume

Re: [openstack-dev] [neutron] Feature Proposal Freeze is 9 days away

not submit code for review? Would it be > better to also request a change in milestone? > > Thanks, > > Mohammad > > > [image: Inactive hide details for Kyle Mestery ---08/12/2014 09:15:03 > AM---Just a reminder that Neutron observes FPF [1], and it's 9 da]Kyle &

Re: [openstack-dev] [all] The future of the integrated release

On Wed, Aug 13, 2014 at 5:15 AM, Daniel P. Berrange wrote: > On Mon, Aug 11, 2014 at 10:30:12PM -0700, Joe Gordon wrote: >> On Fri, Aug 8, 2014 at 6:58 AM, Kyle Mestery wrote: >> > > I really like this idea, as Michael and others alluded to in above, we >> > are

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Wed, Aug 13, 2014 at 7:55 AM, Russell Bryant wrote: > On 08/13/2014 05:57 AM, Daniel P. Berrange wrote: >> On Wed, Aug 13, 2014 at 08:57:40AM +1000, Michael Still wrote: >>> Hi. >>> >>> One of the action items from the nova midcycle was that I was asked to >>> make nova's expectations of core r

[openstack-dev] [neutron] Rotating the weekly Neutron meeting

Per this week's Neutron meeting [1], it was decided that offering a rotating meeting slot for the weekly Neutron meeting would be a good thing. This will allow for a much easier time for people in Asia/Pacific timezones, as well as for people in Europe. So, I'd like to propose we rotate the weekly

[openstack-dev] [neutron] Canceling today's parity meeting

Sorry for the short notice, but lets cancel today's parity meeting. We're still circling the wagons around the migration story at this point, so hopefully next week we'll have more to discuss there. Thanks, Kyle ___ OpenStack-dev mailing list OpenStack-

Re: [openstack-dev] [neutron] Rotating the weekly Neutron meeting

On Wed, Aug 13, 2014 at 2:19 PM, Collins, Sean wrote: > On Wed, Aug 13, 2014 at 10:05:26AM EDT, Kyle Mestery wrote: >> Tuesday 1400UTC > > How do we want to handle the overlap with the IPv6 subteam meeting? > If we close out the IPV6 BPs in Juno, will we be at parity for IPV6?

Re: [openstack-dev] [neutron][ml2] Mech driver as out-of-tree add-on

I also feel like the drivers/plugins are currently BEYOND a tipping point, and are in fact dragging down velocity of the core project in many ways. I'm working on a proposal for Kilo where we move all drivers/plugins out of the main Neutron tree and into a separate git repository under the networki

[openstack-dev] [neutron] [third-party] What tests are required to be run

Folks, I'm not sure if all CI accounts are running sufficient tests. Per the requirements wiki page here [1], everyone needs to be running more than just Tempest API tests, which I still see most neutron third-party CI setups doing. I'd like to ask everyone who operates a third-party CI account for

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 10:13 AM, Sandy Walsh wrote: > On 8/14/2014 11:28 AM, Russell Bryant wrote: >> On 08/14/2014 10:04 AM, CARVER, PAUL wrote: >>> Daniel P. Berrange [mailto:berra...@redhat.com] wrote: >>> Depending on the usage needs, I think Google hangouts is a quite useful techno

Re: [openstack-dev] [nova][core] Expectations of core reviewers

On Thu, Aug 14, 2014 at 10:31 AM, CARVER, PAUL wrote: > Russell Bryant [mailto:rbry...@redhat.com] wrote: > >>An ideal solution would allow attendees to join as individuals from >>anywhere. A lot of contributors work from home. Is that sort of thing >>compatible with your system? > > In principl

Re: [openstack-dev] [neutron][ml2] Mech driver as out-of-tree add-on

time, but are there other ways that you think > they slow down the project? > > > On Thu, Aug 14, 2014 at 6:07 AM, Kyle Mestery wrote: >> >> I also feel like the drivers/plugins are currently BEYOND a tipping >> point, and are in fact dragging down velocity of the cor

Re: [openstack-dev] [neutron] [third-party] What tests are required to be run

put an agenda item on Monday's meeting to discuss this? I won't be at the meeting as I'm on PTO (Mark is running the meeting in my absence), but I'd like the team to discuss this and allow all third-party people a chance to be there and share their feelings here. Thanks, Kyle >

Re: [openstack-dev] [Neutron][L3] HA Router Review Help

> On Aug 18, 2014, at 3:41 PM, Carl Baldwin wrote: > > Hi all, > > This is intended for those readers interested in reviewing and soon > merging the HA routers implementation for Juno. Assaf Muller has > written a blog [1] about this new feature which serves as a good > overview. It will be usef

Re: [openstack-dev] [neutron]Performance of security group

tation ( I don't like NAT66, I prefer a `routed Floating IPv6` >> > version ) ? >> > * Metadata over IPv6 still using NAT(66) ( I don't like NAT66 ), single >> > implementation? >> > * Suricata-as-a-Service?! >> > >> > It sounds prett

Re: [openstack-dev] [neutron] Incubator concerns from packaging perspective

On Thu, Aug 21, 2014 at 5:12 AM, Ihar Hrachyshka wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > On 20/08/14 18:28, Salvatore Orlando wrote: >> Some comments inline. >> >> Salvatore >> >> On 20 August 2014 17:38, Ihar Hrachyshka > > wrote: >> >> Hi all, >

Re: [openstack-dev] [neutron][ml2] Mech driver as out-of-tree add-on

orward, and the level of involvement of most of these companies ends at their plugin. So something needs to change to make this scalable going forward. Kyle > 1. > https://github.com/openstack/neutron/blob/08529376f16837083c28b009411cc52e0e2a8d33/neutron/plugins/plumgrid/drivers/fake_plumli

Re: [openstack-dev] [all] The future of the integrated release

On Thu, Aug 21, 2014 at 4:09 AM, Thierry Carrez wrote: > Zane Bitter wrote: >> On 11/08/14 05:24, Thierry Carrez wrote: >>> This all has created a world where you need to be*in* OpenStack to >>> matter, or to justify the investment. This has created a world where >>> everything and everyone wants

Re: [openstack-dev] [neutron] [third-party] What tests are required to be run

gt;>>>>To: OpenStack Development Mailing List (not for usage questions) >>>>>Subject: RE: [openstack-dev] [neutron] [third-party] What tests are >>>>>required to be run >>>>> >>>>>Edgar: >>>>> >>>>>

Re: [openstack-dev] [Neutron][IPv6] Allowing Plugins in tree that explicitly do not support IPv6

On Sun, Aug 24, 2014 at 2:18 PM, Collins, Sean wrote: > Hi, > > The amount of tests that we are having to add skips to for the One > Convergence plugin has grown quite a bit lately. > > http://git.openstack.org/cgit/openstack/neutron/tree/neutron/tests/unit/oneconvergence/test_nvsd_plugin.py#n58 >

Re: [openstack-dev] [congress] policy summit

On Sun, Aug 24, 2014 at 7:01 PM, Sean Roberts wrote: > I am looking for policy overview/impact covering heat, neutron, nova, olso, > mistral, and rubric. Are there any others that want to join us and discuss > how policy impacts their project? I would welcome some discussion around > Opendaylight

Re: [openstack-dev] [all] [ptls] The Czar system, or how to scale PTLs

On Fri, Aug 22, 2014 at 8:19 PM, John Dickinson wrote: > I think Anne makes some excellent points about the pattern being proposed > being unlikely to be commonly implemented across all the programs (or, at > best, very difficult). Let's not try to formalize another "best practice" > that works

Re: [openstack-dev] [all] [ptls] The Czar system, or how to scale PTLs

On Mon, Aug 25, 2014 at 4:45 AM, Alan Kavanagh wrote: > That's a fair point Jay. The Czar does sound like a reasonable approach and > what would be useful and helpful would be to appoint additional PTL's and not > have the burden of everything falling on one individual which becomes over > load

Re: [openstack-dev] [all] [ptls] The Czar system, or how to scale PTLs

On Tue, Aug 26, 2014 at 9:48 AM, Doug Hellmann wrote: > > On Aug 26, 2014, at 10:10 AM, Kyle Mestery wrote: > >> On Fri, Aug 22, 2014 at 8:19 PM, John Dickinson wrote: >>> I think Anne makes some excellent points about the pattern being proposed >>> being un

Re: [openstack-dev] [neutron][OpenDayLight CI] Is this a real failure? The failure log is gone

Looking at the console output from the ODL Jenkins failure, it appears like Jenkins reaped this instance before everything was complete. I've copied Dave Tucker who may be able to provide some additional input from the ODL side as well. On Tue, Aug 26, 2014 at 3:13 PM, Milton Xu (mxu) wrote: >

[openstack-dev] [neutron] Juno-3 BP meeting

I'd like to propose a meeting at 1300UTC on Thursday in #openstack-meeting-3 to discuss Neutron BPs remaining for Juno at this point. We're taking specifically about medium and high priority ones, with a focus on these three: https://blueprints.launchpad.net/neutron/+spec/l3-high-availability) htt

[openstack-dev] [neutron] [nova] Parity meeting cancelled going forward

Due to low turnout and the fact we have a good hand on the parity work for Juno, I'm canceling this meeting going forward. If items pop up at the end of Juno which are parity related, please add them to the weekly Neutron meeting agenda [1] and we'll cover them there. Thanks! Kyle [1] https://wik

Re: [openstack-dev] [Neutron] Author tags

On Wed, Aug 27, 2014 at 8:24 AM, Gary Kotton wrote: > Hi, > A few cycles ago the Nova group decided to remove @author from copyright > statements. This is due to the fact that this information is stored in git. > After adding a similar hacking rule to Neutron it has stirred up some > debate. > Doe

Re: [openstack-dev] [all] Design Summit reloaded

On Wed, Aug 27, 2014 at 7:51 AM, Thierry Carrez wrote: > Hi everyone, > > I've been thinking about what changes we can bring to the Design Summit > format to make it more productive. I've heard the feedback from the > mid-cycle meetups and would like to apply some of those ideas for Paris, > withi

[openstack-dev] [neutron] Juno-3 BP Review Meeting Minutes

See below. As discussed in the meeting, lets focus on the medium/high priority BPs this week and try to merge them before FF next week. Thanks to all who attended! Kyle Minutes: http://eavesdrop.openstack.org/meetings/neutron_juno_3_bp_review/2014/neutron_juno_3_bp_review.2014-08-28-13.01.html

Re: [openstack-dev] [nova] [neutron] Specs for K release

On Thu, Aug 28, 2014 at 8:30 AM, Michael Still wrote: > For nova we haven't gotten around to doing this, but it shouldn't be a > big deal. I'll add it to the agenda for today's meeting. > > Michael > For Neutron, I have not gone through and removed specs which merged and haven't made it yet. I'll

Re: [openstack-dev] [neutron][lbaas][octavia]

On Thu, Aug 28, 2014 at 5:55 PM, Kevin Benton wrote: > I think we need some clarification here too about the difference between the > general OpenStack Incubation and the Neutron incubation. From my > understanding, the Neutron incubation isn't the path to a separate project > and independence fro

Re: [openstack-dev] [nova] [neutron] Specs for K release

ates, I have not removed the specs from Juno, I've left them there for now. What I was thinking of doing was creating an incubator directory in the specs repo and moving them there since they will be incubated in Juno. Thanks, Kyle > Thanks, > Brandon > > On Thu, 2014-08-28 at 08

Re: [openstack-dev] [neutron] python-neutronclient, launchpad, and milestones

On Fri, Aug 29, 2014 at 1:40 PM, Matt Riedemann wrote: > > > On 7/29/2014 4:12 PM, Kyle Mestery wrote: >> >> On Tue, Jul 29, 2014 at 3:50 PM, Nader Lahouti >> wrote: >>> >>> Hi Kyle, >>> >>> I have a BP listed in >>> https:

Re: [openstack-dev] [neutron][lbaas][octavia]

networking program. 3) We deprecate Neutron LBaaS v1. To deprecate, we need the new API stable and ready, and then once V1 is deprecated it takes 2 cycles for us to remove it. Hope that helps! Thanks, Kyle > Thanks, > German > > > -Original Message- > From: Kyle Mes

[openstack-dev] [neutron] New meeting rotation starting next week

Per discussion again today in the Neutron meeting, next week we'll start rotating the meeting. This will mean next week we'll meet on Tuesday (9-9-2014) at 1400 UTC in #openstack-meeting-alt. I've updated the Neutron meeting page [1] as well as the meeting wiki page [2] with the new details on the

Re: [openstack-dev] [third party][neutron] - OpenDaylight CI and -1 voting

On Mon, Sep 1, 2014 at 10:47 PM, Kevin Benton wrote: > Thank you YAMAMOTO. I didn't think to look at stackalytics. > > Kyle, can you list yourself on the wiki? I don't want to do it in case there > is someone else doing that job full time. > Also, is there a re-trigger phrase that you can document

Re: [openstack-dev] [neutron][lbaas][octavia]

On Tue, Sep 2, 2014 at 1:28 PM, Salvatore Orlando wrote: > Inline. > Salvatore > > On 2 September 2014 19:46, Stephen Balukoff wrote: >> >> For what it's worth in this discussion, I agree that the possible futures >> of Octavia already discussed (where it lives, how it relates to Neutron >> LBaaS

Re: [openstack-dev] [Neutron][IPv6] Moving meeting time to 1500 UTC on Tuesdays on #openstack-meeting-alt?

On Tue, Sep 2, 2014 at 4:05 PM, Collins, Sean wrote: > Any objection? We need to move the time since the main meeting conflicts > with our current time slot. > If you do that, I'll take over #openstack-meeting from you for the Neutron meeting, so let me know once this meeting moves and I'll update

[openstack-dev] [neutron] Status of Neutron at Juno-3

Given how deep the merge queue is (146 currently), we've effectively reached feature freeze in Neutron now (likely other projects as well). So this morning I'm going to go through and remove BPs from Juno which did not make the merge window. I'll also be putting temporary -2s in the patches to ensu

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

On Wed, Sep 3, 2014 at 10:19 AM, Mark McClain wrote: > > On Sep 3, 2014, at 11:04 AM, Brian Haley wrote: > >> On 09/03/2014 08:17 AM, Kyle Mestery wrote: >>> Given how deep the merge queue is (146 currently), we've effectively >>> reached feature freeze in

Re: [openstack-dev] [infra][qa][neutron] Neutron full job, advanced services, and the integrated gate

On Wed, Sep 3, 2014 at 3:22 PM, Sean Dague wrote: > On 08/26/2014 07:47 PM, Salvatore Orlando wrote: >> TL; DR >> A few folks are proposing to stop running tests for neutron advanced >> services [ie: (lb|vpn|fw)aas] in the integrated gate, and run them only >> on the neutron gate. >> >> Reason: pr

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

add this to the list of BPs to discuss with ttx tomorrow. Thanks, Kyle > Best regards, > Miguel Ángel. > > - Original Message - >> On Wed, Sep 3, 2014 at 10:19 AM, Mark McClain wrote: >> > >> > On Sep 3, 2014, at 11:04 AM, Brian Haley wrote: >>

Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On Thu, Sep 4, 2014 at 5:24 AM, Daniel P. Berrange wrote: > Position statement > == > > Over the past year I've increasingly come to the conclusion that > Nova is heading for (or probably already at) a major crisis. If > steps are not taken to avert this, the project is likely to l

Re: [openstack-dev] [neutron] New meeting rotation starting next week

Just an updated note here. The IPV6 sub-team has moved their meeting time, so I've claimed #openstack-meeting at 1400UTC on Tuesday's for the Neutron team meeting. I'll send a note reminding folks of the change on Monday. Thanks, Kyle On Mon, Sep 1, 2014 at 8:19 PM, Kyle Mester

Re: [openstack-dev] [neutron] Status of Neutron at Juno-3

lementation. > It's on the list for inclusion as an FFE. I hope to chat with ttx soon about these and we'll decide which ones get FFEs at that point. Thanks, Kyle > -Bob > > > On 9/3/14, 8:17 AM, Kyle Mestery wrote: >> >> Given how deep the merge queue is (146 curren

Re: [openstack-dev] [neutron] python-neutronclient, launchpad, and milestones

On Sat, Sep 6, 2014 at 8:43 AM, Matt Riedemann wrote: > > > On 8/29/2014 1:53 PM, Kyle Mestery wrote: >> >> On Fri, Aug 29, 2014 at 1:40 PM, Matt Riedemann >> wrote: >>> >>> >>> >>> On 7/29/2014 4:12 PM, Kyle Mestery wrote

[openstack-dev] New python-neutronclient release: 2.3.7

Hi: I've just pushed a new release of python-neutronclient out. The main feature in this release is keystone v3 auth support [1]. In addition, the following, changes are also a part of this release: f22dbd2 Updated from global requirements 9f3ffdf Remove unnecessary get_status_code wrapper functi

Re: [openstack-dev] [neutron] python-neutronclient, launchpad, and milestones

On Sat, Sep 6, 2014 at 9:08 PM, Kyle Mestery wrote: > On Sat, Sep 6, 2014 at 8:43 AM, Matt Riedemann > wrote: >> >> >> On 8/29/2014 1:53 PM, Kyle Mestery wrote: >>> >>> On Fri, Aug 29, 2014 at 1:40 PM, Matt Riedemann >>> wrote: >>&

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

Just a reminder since this is the first week we'll do the rotating meeting. Please add agenda items to the meeting here [1]. See you all tomorrow! Kyle [1] https://wiki.openstack.org/wiki/Network/Meetings ___ OpenStack-dev mailing list OpenStack-dev@l

[openstack-dev] [neutron] List of BPs with an FFE

The list of BPs for Neutron with an FFE are now targeted in the RC1 page here [1]. Please focus on reviewing these, we have a short window to merge this. I believe the window closes on Friday this week (9-12-2014), but I'll verify with Thierry in my 1:1 with him today. We'll also spend a good amou

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

On Wed, Sep 10, 2014 at 3:44 AM, Daniel P. Berrange wrote: > On Tue, Sep 09, 2014 at 05:14:43PM -0700, Stefano Maffulli wrote: >> > To me, this means you don't really want a sin bin where you dump >> > drivers and tell them not to come out until they're fit to be >> > reviewed by the core; You wan

Re: [openstack-dev] [release] client release deadline - Sept 18th

On Wed, Sep 10, 2014 at 10:01 AM, Matt Riedemann wrote: > > > On 9/9/2014 4:19 PM, Sean Dague wrote: >> >> As we try to stabilize OpenStack Juno, many server projects need to get >> out final client releases that expose new features of their servers. >> While this seems like not a big deal, each o

Re: [openstack-dev] Kilo Cycle Goals Exercise

On Wed, Sep 10, 2014 at 7:13 AM, Thierry Carrez wrote: > Joe Gordon wrote: >> To that end, I would like to propose an exercise as discussed in the TC >> meeting yesterday [1]: >> Have anyone interested (especially TC members) come up with a list of >> what they think the project wide Kilo cycle go

Re: [openstack-dev] [nova][neutron][cinder] Averting the Nova crisis by splitting out virt drivers

d anyway) will require probably one cycle, if not more. > > On 09/10/2014 09:07 AM, Kyle Mestery wrote: >> I would be cautious around sub-teams. Our experience in Neutron has >> been that we do a very good job of setting up sub-teams, but a >> terrible job at deciding when th

Re: [openstack-dev] [Neutron] keep old specs

On Mon, Sep 15, 2014 at 4:52 AM, Kevin Benton wrote: > I saw that the specs that didn't make the deadline for the feature freeze > were removed from the tree completely.[1] For easier reference, can we > instead revert that commit to restore them and then move them into a release > specific folder

[openstack-dev] [neutron] Weekly meeting is today at 2100 UTC

Just a note that per our new rotating meeting schedule, we'll hold the Neutron meeting today at 2100 UTC in #openstack-meeting. Please feel free to add items to the meeting agenda [1]. Thanks! Kyle [1] https://wiki.openstack.org/wiki/Network/Meetings _

[openstack-dev] [all] Release 2.3.8 release of python-neutronclient

I'm please to announce the latest release of python-neutronclient, version 2.3.8. This will be the last release before the Juno release of OpenStack. The main change we were waiting for was the CLI changes for L3 HA. In addition, the following changes are a part of this release: 19527c4 Narrow dow

Re: [openstack-dev] [neutron] Ipset, merge refactor for J?

On Tue, Sep 16, 2014 at 7:24 AM, Sean Dague wrote: > On 09/16/2014 03:57 AM, Thierry Carrez wrote: >> Miguel Angel Ajo Pelayo wrote: >>> During the ipset implementatio, we designed a refactor [1] to cleanup >>> the firewall driver a bit, and move all the ipset low-level knowledge >>> down into the

[openstack-dev] [neutron] Third party Neutron plugin testing meeting

Last week I took an action item to organize a meeting for everyone who is doing third-party testing in Neutron for plugins, whether this is vendor or Open Source based. The idea is to share ideas around setups and any issues people hit. I'd like to set this meeting up for this week, Thursday at 170

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

On Dec 10, 2013, at 10:45 AM, "Veiga, Anthony" wrote: > -Original Message- > From: Kyle Mestery > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > > Date: Tuesday, December 10, 2013 10:48 > To: "OpenStack Develo

Re: [openstack-dev] [neutron] Third party Neutron plugin testingmeeting

gating system. > >(This document is still draft version) > >https://docs.google.com/presentation/d/1WJInaSt_H2kVkjnhtPmiATP1F-0BVbuk1e > >efQalL5Q0/edit#slide=id.p > > > >2013/12/10 Ivar Lazzaro : > >> +1 for 1700UTC Thursday on IRC > >> > >&g

Re: [openstack-dev] [neutron] Third party Neutron plugin testing meeting

ing how to use openstack gating system. > >(This document is still draft version) > >https://docs.google.com/presentation/d/1WJInaSt_H2kVkjnhtPmiATP1F-0BVbuk1e > >efQalL5Q0/edit#slide=id.p > > > >2013/12/10 Ivar Lazzaro : > >> +1 for 1700UTC Thursday on IRC

[openstack-dev] [neutron] [third-party-testing] Meeting Minutes for our first meeting

Hi everyone: We had a meeting around Neutron Third-Party testing today on IRC. The logs are available here [1]. We plan to host another meeting next week, and it will be at 2200 UTC on Wednesday in the #openstack-meeting-alt channel on IRC. Please attend and update the etherpad [2] with any items

Re: [openstack-dev] [Nova] [Neutron] How do we know a host is ready to have servers scheduled onto it?

On Dec 12, 2013, at 11:44 AM, Jay Pipes wrote: > On 12/12/2013 12:36 PM, Clint Byrum wrote: >> Excerpts from Russell Bryant's message of 2013-12-12 09:09:04 -0800: >>> On 12/12/2013 12:02 PM, Clint Byrum wrote: I've been chasing quite a few bugs in the TripleO automated bring-up lately t

Re: [openstack-dev] [neutron] Re: [Blueprint vlan-aware-vms] VLAN aware VMs

On Dec 16, 2013, at 11:17 PM, Isaku Yamahata wrote: > Added openstack-dev > > On Mon, Dec 16, 2013 at 11:34:05PM +0100, > Erik Moe wrote: > >> Hi, >> >> I have added a new document to the launchpad. Document should now be more >> in line with what we discussed at the Icehouse summit. >> >> ht

[openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow

Just a reminder, we'll be meeting at 2200 UTC on #openstack-meeting-alt. We'll be looking at this etherpad [1] again, and continuing discussions from last week. Thanks! Kyle [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest ___ OpenStack-

[openstack-dev] [neutron] [ml2] Canceling next two weekly meetings

Since the next two Neutron ML2 meetings fall on Dec. 25 and Jan. 1, we'll cancel both and reconvene on Jan. 8. Thanks! Kyle ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-de

Re: [openstack-dev] [neutron] [third-party-testing] Reminder: Meeting tomorrow

t held on 2200 UTC on Wednesday (today). > > Do you mean 2200 UTC on Thursday ? > > Thanks. > > On Thu, 12 Dec 2013 11:43:03 -0600 > Kyle Mestery wrote: > > > Hi everyone: > > > > We had a meeting around Neutron Third-Party testing today on IRC. > >

Re: [openstack-dev] [Neutron][qa] Parallel testing update

he > neutron service and we might try to enable multiple workers on the gate to > this aim, or just increase the tempest timeout. On a slightly different note, > allow me to say that the way assertion are made on this test might be > improved a bit. So far one has to go through the code

Re: [openstack-dev] neutron plugin for opendaylight

On Jan 2, 2014, at 7:50 PM, Vijayendra BVS wrote: > > [Apologies if mesg is duplicated] > > > > Hi Kyle/Team, > > > > I’m looking at open daylight support in openstack and see the relevant > blueprint for the neutron plugin for ODL at > https://docs.google.com/document/d/1rdowsQSYBirS634R

Re: [openstack-dev] [neutron] [third-party-testing] Sharing information

another IRC meeting to discuss this > matter? > (Kyle, I am sure you are busy so I took the liberty to send this note. Please > let us know what you think.) > > Thanks, > > Mohammad > > > [1] https://etherpad.openstack.org/p/multi-node-neutron-tempest > > K

Re: [openstack-dev] [neutron] [third-party-testing] Sharing information

ontreal attending the sprint tempest session. > Hopefully we can all take it from there. > > Edgar > > > On Jan 14, 2014, at 6:31 AM, Kyle Mestery wrote: > > > > Thanks for sending this note Mohammad. I am all in favor of another > > 3rd party testing meetin

[openstack-dev] [nova] Issues with nova-compute on Fedora 20 around libvirt

So I upgraded some of my development hosts to Fedora 20 recently, and since then I’ve been hitting an issue where I cannot start nova-compute at all. The environment I am running this in is that the Fedora 20 hosts are running as VMs on a Macbook Pro under VMware Fusion. The same setup works fine w

Re: [openstack-dev] [neutron] [third-party-testing] Sharing information

update as we near the deadline next week. Thanks! Kyle [1] http://eavesdrop.openstack.org/meetings/networking_third_party_testing/2014/networking_third_party_testing.2014-01-15-22.00.log.html On Jan 14, 2014, at 10:34 AM, Kyle Mestery wrote: > Given the Tempest Sprint in Montreal, I still think

Re: [openstack-dev] [Neutron] auto configration of local_ip

On Jan 16, 2014, at 7:52 AM, Isaku Yamahata wrote: > On Thu, Jan 16, 2014 at 10:53:11PM +1300, > Robert Collins wrote: > >> On 16 January 2014 22:51, Robert Collins wrote: >> >>> I don't think 1 is a special case of 3 - interface based connections >>> are dependent on physical wiring, >>> >

Re: [openstack-dev] Hat Tip to fungi

On Jan 16, 2014, at 9:17 AM, Jay Pipes wrote: > On Thu, 2014-01-16 at 08:44 -0500, Anita Kuno wrote: >> Thank you, fungi. >> >> You have kept openstack-infra running for that last 2 weeks as the sole >> plate-spinner whilst the rest of us were conferencing, working on the >> gerrit upgrade or g

Re: [openstack-dev] [Neturon] firewall_driver and ML2 and vif_security discussion

On Jan 16, 2014, at 1:37 PM, Nachi Ueno wrote: > Hi Amir > > 2014/1/16 Amir Sadoughi : >> Hi all, >> >> I just want to make sure I understand the plan and its consequences. I’m on >> board with the YAGNI principle of hardwiring mechanism drivers to return >> their firewall_driver types for n

Re: [openstack-dev] [Neturon] firewall_driver and ML2 and vif_security discussion

On Jan 16, 2014, at 4:27 PM, Nachi Ueno wrote: > Hi Bob, Kyle > > I pushed (A) https://review.openstack.org/#/c/67281/. > so could you review it? > Just did, looks good Nachi, thanks! > 2014/1/16 Robert Kukura : >> On 01/16/2014 03:13 PM, Kyle Mestery wrote: >>&

[openstack-dev] [neutron] [ml2] The impending plethora of ML2 MechanismDrivers

Folks: As you can see from our meeting agent for today [1], we are tracking a large number of new ML2 MechanismDrivers at the moment. We plan to discuss these in the meeting again this week in the ML2 meeting [2] at 1600 UTC in #openstack-meeting-alt. Also, it would be great if each MechanismDrive

Re: [openstack-dev] [Nova][Neutron] nova-network in Icehouse and beyond

On Jan 29, 2014, at 12:04 PM, Russell Bryant wrote: > On 01/29/2014 12:45 PM, Daniel P. Berrange wrote: >> I was thinking of an upgrade path more akin to what users got when we >> removed the nova volume driver, in favour of cinder. >> >> https://wiki.openstack.org/wiki/MigrateToCinder >> >>

[openstack-dev] [neutron] [group-policy] Canceling tomorrows meeting

Folks: We’ve decided to cancel tomorrows IRC meeting. If you have action items around the POC we’re all working on, please continue down that path for now. We’ll sync up for a meeting the following week again. Thanks! Kyle ___ OpenStack-dev mailing list

Re: [openstack-dev] [Neutron] [ML2] l2-pop bugs review

On Feb 6, 2014, at 3:09 AM, Édouard Thuleau wrote: > Hi all, > > Just to point 2 reviews [1] & [2] I submitted to correct l2-pop > mechanism driver into the ML2 plugin. > I had some reviews and +1 but they doesn't progress anymore. > Could you check them ? > I also like to backport them for sta

Re: [openstack-dev] [neutron][ml2] Maintaining support for the Tail-f NCS mech driver in Icehouse

On Feb 6, 2014, at 8:52 AM, Luke Gorrie wrote: > Howdy! > > My name is Luke and I'm helping my friends at Tail-f Systems to > support Neutron with their NCS [1] product. This went really smoothly > for us on the Havana cycle, but lately we're having a harder time with > Icehouse. In particular,

Re: [openstack-dev] [Neutron] Support for multiple provider networks with same VLAN segmentation id

On Feb 6, 2014, at 5:24 PM, Vinay Bannai wrote: > Hello Folks, > > We are running into a situation where we are not able to create multiple > provider networks with the same VLAN id. We would like to propose a solution > to remove this restriction through a configuration option. This approach

Re: [openstack-dev] [neutron][ml2] Maintaining support for the Tail-f NCS mech driver in Icehouse

On Feb 9, 2014, at 4:10 PM, CARVER, PAUL wrote: > Kyle Mestery wrote: > >> So, in general I don't think this will fly because it's my understanding the >> OpenStack servers only test fully open source code. Allowing a third party >> vendor system to run on th

[openstack-dev] [neutron] [group-policy] Changing the meeting time

Folks: I’d like to propose moving the Neutron Group Policy meeting going forward, starting with this Thursday. The meeting has been at 1600 UTC on Thursdays, I’d like to move this to 1700UTC Thursdays on #openstack-meeting-alt. If this is a problem for anyone who regularly attends this meeting, pl

Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core

+1 On Feb 10, 2014, at 5:28 PM, Mark McClain wrote: > All- > > I’d like to nominate Oleg Bondarev to become a Neutron core reviewer. Oleg > has been valuable contributor to Neutron by actively reviewing, working on > bugs, and contributing code. > > Neutron cores please reply back with +1/0

Re: [openstack-dev] [neutron] [group-policy] Changing the meeting time

- Stephen >> >> >> >> On Mon, Feb 10, 2014 at 7:30 PM, Kyle Mestery >> wrote: >>> >>> Folks: >>> >>> I'd like to propose moving the Neutron Group Policy meeting going >>> forward, starting with this Thursday.

Re: [openstack-dev] [neutron] [group-policy] Changing the meeting time

t; > > https://wiki.openstack.org/wiki/Meetings/Neutron_Group_Policy > https://wiki.openstack.org/wiki/Meetings#Neutron_Group_Policy_Sub-Team_Meeting > > Thanks, > > On Tue, Feb 11, 2014 at 02:25:12PM -0600, > Kyle Mestery wrote: > > > FYI, I’ve made the chan

Re: [openstack-dev] [Neutron] Group Policy questions

Great, welcome to the team Carlos! Look forward to collaborating with you and we’ll see you at this Thursday’s IRC meeting! Kyle On Feb 17, 2014, at 11:19 AM, Carlos Gonçalves wrote: > Hi, > > Firstly, I would like to thank you all for your replies! > > I am very much interested in taking so

Re: [openstack-dev] [Openstack-dev] [neutron] [ml2] Neutron and ML2 - adding new network type

[Moving to -dev list] On Feb 18, 2014, at 9:12 AM, Sławek Kapłoński wrote: > Hello, > > I'm trying to make something with neutron and ML2 plugin. Now I need to add > my own external network type (as there are "Flat", "VLAN", "GRE" and so on). > I searched for manuals for that but I can't foun

[openstack-dev] [devstack] [neutron] OpenDaylight devstack support questions

So, I have this review [1] which attempts to add support for OpenDaylight to devstack. What this currently does, in Patch 7, is that it uses the "extras" functionality of devstack to program the OVS on the host so that OpenDaylight can control it. On teardown, it does the reverse. Simple and straig

Re: [openstack-dev] [neutron][policy] Blueprint document

On Feb 28, 2014, at 8:01 AM, Carlos Gonçalves wrote: > Hi all, > > As the blueprint document is write-protected, the “See revision history” > option is greyed out for viewers-only making it difficult to keep track of > changes. Hence, and if there is no way as a viewer to see the revision > h

Re: [openstack-dev] [devstack] [neutron] OpenDaylight devstack support questions

river rather than a plugin, > this solution won't work out of the box, but at first glance it should not be > to hard to adapt it. > > Salvatore > > > > On 26 February 2014 22:47, Kyle Mestery wrote: > So, I have this review [1] which attempts to add support for O

[openstack-dev] [devstack] [neutron] How to tell a compute host the control host is running Neutron

devstack folks: Per my review here [1] and comments in the review, I wanted to send this email to try and clarify what I think is being lost in the review comments. Currently, devstack has no way to configure a compute host running with Neutron on the control node which has no Neutron services on

Re: [openstack-dev] [devstack] [neutron] How to tell a compute host the control host is running Neutron

On Mon, Mar 3, 2014 at 10:32 PM, Dean Troyer wrote: > On Mon, Mar 3, 2014 at 8:36 PM, Kyle Mestery wrote: >> >> In all cases today with Open Source plugins, Neutron agents have run on >> the hosts. For OpenDaylight, this is not the case. OpenDaylight integrates >

Re: [openstack-dev] [devstack] [neutron] How to tell a compute host the control host is running Neutron

On Tue, Mar 4, 2014 at 5:46 AM, Sean Dague wrote: > On 03/03/2014 11:32 PM, Dean Troyer wrote: > > On Mon, Mar 3, 2014 at 8:36 PM, Kyle Mestery > <mailto:mest...@noironetworks.com>> wrote: > > > > In all cases today with Open Source plugins, Neutron agents h

[openstack-dev] [neutron] neutron-drivers meeting moved by 30 minutes

Due to a scheduling conflict, I moved the meeting. It's now from 1530-1630 UTC on Wednesdays [1]. Thanks! Kyle [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.ope

  1   2   3   4   5   6   7   8   >