[openstack-dev] [neutron] [third-party] Cisco NXOS is not tested anymore

Cisco Folks, I don't see the CI for Cisco NX-OS anymore. Is this being deprecated? Edgar ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] [third-party] Cisco NXOS is not tested anymore

Kuno" wrote: >On 08/11/2014 06:31 PM, Henry Gessau wrote: >> On 8/11/2014 7:56 PM, Anita Kuno wrote: >>> On 08/11/2014 05:46 PM, Henry Gessau wrote: >>>> Anita Kuno wrote: >>>>> On 08/11/2014 05:05 PM, Edgar Magana wrote: >>>>>>

Re: [openstack-dev] [neutron] [third-party] Cisco NXOS is not tested anymore

04 PM, Jeremy Stanley wrote: >> On 2014-08-12 16:35:18 +0000 (+), Edgar Magana wrote: >>> If this plugin will be deprecated in Juno it means that the code >>> will be there for this release, I will expect to have the CI still >>> running for until the code i

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

Go for it commander! Edgar On 8/13/14, 7:05 AM, "Kyle Mestery" wrote: >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,

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

Team, I did a quick audit on the Neutron CI. Very sad results. Only few plugins and drivers are running properly and testing all Neutron commits. I created a report here: https://wiki.openstack.org/wiki/Neutron_Plugins_and_Drivers#Existing_Plugin _and_Drivers We will discuss the actions to take

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

Correction The right links are: https://review.openstack.org/#/c/114629/ https://review.openstack.org/#/c/114393/ Not this one: https://review.openstack.org/#/c/40296/ Edgar On 8/15/14, 3:35 PM, "Edgar Magana" wrote: >Team, > >I did a quick audit on the Neutron CI. Ver

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

Neutron patches. Some may have missed your call just because of their filters (see [0] section 'what changes to run against'). Cheers, Ivar. [0] https://wiki.openstack.org/wiki/NeutronThirdPartyTesting On Sat, Aug 16, 2014 at 12:35 AM, Edgar Magana mailto:edgar.mag...@workday.com&g

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

your responses. Thanks, Edgar On 8/15/14, 3:35 PM, "Edgar Magana" wrote: >Team, > >I did a quick audit on the Neutron CI. Very sad results. Only few plugins >and drivers are running properly and testing all Neutron commits. >I created a report here: &g

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

Thank you Akihiro. I will propose a better organization for this section. Stay tune! Edgar On 8/17/14, 10:53 PM, "Akihiro Motoki" wrote: > >On 2014/08/18 0:12, Kyle Mestery wrote: >> On Fri, Aug 15, 2014 at 5:35 PM, Edgar Magana >> wrote: >>> Team, >&

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

d like to confirm this is the issue, will resolve this. Thanks, -hemanth On Mon, Aug 18, 2014 at 8:35 AM, Edgar Magana mailto:edgar.mag...@workday.com>> wrote: Thank you Akihiro. I will propose a better organization for this section. Stay tune! Edgar On 8/17/14, 10:53 PM, "Akihiro

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

ents to nova) - neutron/db/.* - neutron/services/${thepluginsyouruninyourci_eveniftheyrenotyours} - your plugin patch Salvatore PS: Openstack proposal bot submission's checks have been suspended for vmware minesweeper about 2 days ago. They will resume soon. On 16 August 2014 01:02, Edgar Magana mailto:edgar.mag...@

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

why >you did not see it voting for the test change ref. > Also, you can add me as a contact person and alias >networking-cloudinteg...@citrix.com as email contact point for the >NetScaler CI. > > Please let me know if you have any questions. > >Thanks, >Pariksh

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

> >On 2014/08/18 0:12, Kyle Mestery wrote: >> On Fri, Aug 15, 2014 at 5:35 PM, Edgar Magana >>mailto:edgar.mag...@workday.com>> wrote: >>> Team, >>> >>> I did a quick audit on the Neutron CI. Very sad results. Only few >>>plugins

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

t;> >> Freescale CI is reporting the results for ML2 Mechanism driver (J-1) and >> FWaaS Plugin (to be approved for J-3). >> I'm the owner for this CI. >> >> The Wiki page for this CI is >> https://wiki.openstack.org/wiki/ThirdPartySystems

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

esults are only valid for APIC-related >commits"? I think this more accurately represents our current results >(for reasons we chatted about on another thread). > >Thanks, >Dane > >-Original Message- >From: Edgar Magana [mailto:edgar.mag...@workday.com] >Sen

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

3). >I'm the owner for this CI. > >The Wiki page for this CI is >https://wiki.openstack.org/wiki/ThirdPartySystems/Freescale_CI. > >-- >Trinath Somanchi - B39208 >trinath.soman...@freescale.com | extn: 4048 > >-Original Message- >From: Edgar Magana [mailt

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

Plugin, Shiv Haris is the owner. >Please let me know if you have any questions. > >Thanks, >Karthik > >-----Original Message- >From: Edgar Magana [mailto:edgar.mag...@workday.com] >Sent: Friday, August 15, 2014 3:59 PM >To: OpenStack Development Mailing List (n

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

lter so that CI run for ALL changes include documents. Thanks, Hirofumi 2014-08-16 7:35 GMT+09:00 Edgar Magana mailto:edgar.mag...@workday.com>>: Team, I did a quick audit on the Neutron CI. Very sad results. Only few plugins and drivers are running properly and testing al

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

esults are only valid for APIC-related >commits"? I think this more accurately represents our current results >(for reasons we chatted about on another thread). > >Thanks, >Dane > >-Original Message- >From: Edgar Magana [mailto:edgar.mag...@workday.com] >Sen

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

stem is backed by about 100 patches to push responses out ~22 hours. This does bring up an old discussion that was never resolved. What is the minimum expected response time for CI systems? On Fri, Aug 15, 2014 at 3:35 PM, Edgar Magana mailto:edgar.mag...@workday.com>> wrote: Team,

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

c/114629/ >https://review.openstack.org/#/c/114393/ > >-Original Message- >From: Edgar Magana [mailto:edgar.mag...@workday.com] >Sent: Tuesday, August 19, 2014 12:28 PM >To: Dane Leblanc (leblancd); OpenStack Development Mailing List (not for >usage questions) >Subject: Re: [openstack

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

-Dane > >-Original Message- >From: Dane Leblanc (leblancd) >Sent: Tuesday, August 19, 2014 3:05 PM >To: 'Edgar Magana'; OpenStack Development Mailing List (not for usage >questions) >Subject: RE: [openstack-dev] [neutron] [third-party] What tests are >requ

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

on the wiki? On Aug 19, 2014 9:39 AM, "Edgar Magana" mailto:edgar.mag...@workday.com>> wrote: Kevin, I just verified, Thanks a lot. Edgar From: Kevin Benton mailto:blak...@gmail.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailt

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

at 12:41 PM, Kevin Benton mailto:blak...@gmail.com>> wrote: Our system would get backed up with patches and sometimes take up to 10 hours to respond with results for a change. We should establish some maximum acceptable time to get the results for a patch. On Thu, Aug 21, 2014 at 11:59 AM, E

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

Sorry my bad but I just changed. Edgar On 8/21/14, 2:13 PM, "Dane Leblanc (leblancd)" wrote: >Edgar: > >I'm still seeing the comment "Results are not accurate. Needs >clarification..." > >Dane > >-Original Message- >From: Edgar Maga

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

3rd >> party CI status wiki, e.g.: >> >> Vendor Plugin/Driver Name Contact Name >> Status Notes >> My Vendor Name My Plugin CIMy Contact Person T >> Throttled / Partially blocked / Awaiting Intial Commits >> >>

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

I do agree with Kyle. There is no rush for having this code merged in order to a void multiple rebase work for the other patches. Edgar On 8/27/14, 9:25 AM, "Kyle Mestery" wrote: >On Wed, Aug 27, 2014 at 8:24 AM, Gary Kotton wrote: >> Hi, >> A few cycles ago the Nova group decided to remove @a

Re: [openstack-dev] [neutron] [third-party] collecting recheck command to re-trigger third party CI

rstands the requirements, rather than simply throwing it on the mailing list and assuming it is accepted by everybody. This is what leads to the confusion. Some people will take it as a marching orders, others may miss the thread and completely miss the communication. Kyle Mestry (Neutron PTL) a

Re: [openstack-dev] Documentation on writing a neutron plugin/driver

Daniel, You can start with: https://wiki.openstack.org/wiki/NeutronDevelopment You can also take a look to one of the latest plugins in being merged: https://review.openstack.org/#/c/96630/ If you are looking into a ML2 driver: https://review.openstack.org/#/c/64944/ Cheers, Edgar From: opens

Re: [openstack-dev] [Neutron] Race condition between DB layer and plugin back-end implementation

wrote: > >> On 11/18/2013 03:25 PM, Edgar Magana wrote: >> > Developers, >> > >> > This topic has been discussed before but I do not remember if we have >>a >> > good solution or not. >> >> The ML2 plugin addresses this by calling ea

Re: [openstack-dev] [Neutron] Race condition between DB layer and plugin back-end implementation

Let me take a look and circle back to you in a bit. This is a very sensitive part of the code, so we need to Handle properly any change. Thanks, Edgar On 11/20/13 5:46 AM, "Isaku Yamahata" wrote: >On Tue, Nov 19, 2013 at 08:59:38AM -0800, >Edgar Magana wrote: > >>

Re: [openstack-dev] [Neutron] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

lly if you >> are planning on staying less that 1 week, you won't need one. But >> contact the embassy and be sure. >> >> Thanks, >> Anita. >> >> On 11/13/2013 01:25 PM, Edgar Magana wrote: >>> Will do ASAP. >>> >>&

[openstack-dev] FW: [Bug 1257788] Re: nova-network doesn't handle large amount of concurrent booting instances well

FYI. Concurrent calls are a problem all around in OpenStack! Edgar On 12/10/13 8:47 AM, "Abhishek Chanda" wrote: >** Changed in: nova > Status: New => Triaged > >-- >You received this bug notification because you are subscribed to >neutron. >https://bugs.launchpad.net/bugs/1257788 > >Tit

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

Also joining! Looking forward to hearing your ideas folks! Edgar On 12/10/13 10:16 AM, "Nachi Ueno" wrote: >+1 ! I'll join. >I'm also working on investigating how to use openstack gating system. >(This document is still draft version) >https://docs.google.com/presentation/d/1WJInaSt_H2kVkjnhtPm

[openstack-dev] [Neutron] Fix to agents race condition creates another issue

In commit: https://review.openstack.org/#/c/58814/ There is an assumption that all "plugins" creates the plumgrid_neutron.agents which is not the case. I just tested big switch and plumgrid and they are failing: INFO [alembic.migration] Running upgrade havana -> e197124d4b9, add unique constrain

Re: [openstack-dev] [Neutron] Fix to agents race condition creates another issue

, 2013 at 10:38 PM, Eugene Nikanorov wrote: > Hi, Edgar, > > Please file a bug on this. Obviously this was introduced by that commit. > > Thanks, > Eugene. > > > On Thu, Dec 12, 2013 at 7:45 AM, Edgar Magana wrote: > >> In commit: >> https://review.

Re: [openstack-dev] [Neutron] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

Anita, Fawad and Myself will be also attending. BTW. Fawad will require an invitation letter for visa. He will email you directly with that request. Thanks, Edgar On Wed, Dec 18, 2013 at 1:17 PM, Anita Kuno wrote: > Okay time for a recap. > > What: Neutron Tempest code sprint > Where: Montr

Re: [openstack-dev] [Neutron] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

Anita, Did you get my email with my confirmation? Thanks, Edgar On Thu, Dec 19, 2013 at 4:02 PM, Edgar Magana wrote: > Anita, > > Fawad and Myself will be also attending. > > BTW. Fawad will require an invitation letter for visa. He will email you > directly with that r

Re: [openstack-dev] [Neutron] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

e’ll have manpower to onboard new contributors (3 days > is a really short time). While I’m happy to welcome more workers there, I > do not want to waste his time or PLUMgrid’s resources. > > mark > > On Dec 19, 2013, at 7:02 PM, Edgar Magana wrote: > > Anita, > >

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

I like it and I am in favor. Some of us, will be in Montreal 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 mee

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

Wouldn't be easier just to check if: cidr is 32? I believe it is a good idea to not allow /32 network but this is just my opinion Edgar From: Paul Ward Reply-To: OpenStack List Date: Tuesday, January 21, 2014 12:35 PM To: OpenStack List Subject: [openstack-dev] [neutron] Neutron should

Re: [openstack-dev] [Fwd: Change in openstack/neutron[master]: Kill dnsmasq and ns-meta softly]

No doubt about it!!! Edgar On 1/28/14 8:45 AM, "Jay Pipes" wrote: >This might just be the most creative commit message of the year. > >-jay >___ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman

Re: [openstack-dev] [neutron] Neutron should disallow /32 CIDR

Well say Carl! I am sorry I did not get back to you on this topic before. In general and after thinking about it, it makes sense to leave could admin to adage the /32 cases if any. Edgar On 1/28/14 1:46 PM, "Carl Baldwin" wrote: >I think I agree. The new check isn't adding much value and we co

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

+1 of course! Edgar Sent from my iPhone > On Feb 11, 2014, at 8:28 AM, 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. >

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

Congratulations Oleg!!! No need for welcoming you to the team, you were already part of ;-) Edgar From: Oleg Bondarev Reply-To: OpenStack List Date: Thursday, February 20, 2014 6:43 AM To: OpenStack List Subject: Re: [openstack-dev] [Neutron] Nominate Oleg Bondarev for Core Thanks Mark

Re: [openstack-dev] [Nova][Neutron] Error message when Neutron network is running out of IP addresses

at. It looks like it might be as easy as adding the NoMoreFixedIps exception to the list where FixedIpLimitExceeded is caught in nova/network/manager.py Vish On Nov 18, 2014, at 8:13 AM, Edgar Magana mailto:edgar.mag...@workday.com>> wrote: Hello Community, When a network subnet runs out

Re: [openstack-dev] [Nova][Neutron] Error message when Neutron network is running out of IP addresses

oks like this has not been reported so a bug would be great. It looks like it might be as easy as adding the NoMoreFixedIps exception to the list where FixedIpLimitExceeded is caught in nova/network/manager.py Vish On Nov 18, 2014, at 8:13 AM, Edgar Magana mailto:edgar.mag...@workday.com>&

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

Great progress! Thanks for this huge effort. Edgar From: Eugene Nikanorov mailto:enikano...@mirantis.com>> Reply-To: OpenStack Development Mailing List mailto:openstack-dev@lists.openstack.org>> Date: Monday, November 24, 2014 at 1:52 AM To: OpenStack Development Mailing List mailto:openstack-d

Re: [openstack-dev] [neutron] Changes to the core team

I give +2 to Henry and Kevin. So, Congratulations Folks! I have been working with both of them and great quality reviews are always coming out from them. Many thanks to Nachi and Bob for their hard work! Edgar On 12/2/14, 7:59 AM, "Kyle Mestery" wrote: >Now that we're in the thick of working h

Re: [openstack-dev] [neutron] Services are now split out and neutron is open for commits!

Great Work Team! Congratulations.. Edgar From: Kyle Mestery mailto:mest...@mestery.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Wednesday, December 10, 2014 at 3:10 PM To: "OpenStack Development Mailing List (not

Re: [openstack-dev] #PERSONAL# : Git checkout command for Blueprints submission

It is git checkout -b bp/ Edgar From: Swati Shukla1 mailto:swati.shuk...@tcs.com>> Reply-To: "openstack-dev@lists.openstack.org" mailto:openstack-dev@lists.openstack.org>> Date: Tuesday, December 16, 2014 at 10:53 PM To: "openstack-dev@lists.openstack.

Re: [openstack-dev] [neutron] Changes to the core team

+1 For adding Doug as Core in Neutron! I have seen his work on the services part and he is a great member of the OpenStack community! Edgar From: Kyle Mestery mailto:mest...@mestery.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openst

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

Nader, I would encourage you to first discuss the possible extension with the ML2 team. Rober and Kyle are leading this effort and they have a IRC meeting every week: https://wiki.openstack.org/wiki/Meetings#ML2_Network_sub-team_meeting Bring your concerns on this meeting and get the right feedba

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

Kyle, Please, point me to the wiki with the documentation for testing the devstack patch! This work seems to be very interesting. Yeah!!! I love to have one more agent less but let's have all agents gone once for all. :-) Edgar On 3/6/14 8:24 AM, "Akihiro Motoki" wrote: >Hi Kyle, > >I am happ

Re: [openstack-dev] [Neutron] Developer documentation

I agree this is a valid request. As a team we should consider this special request and help is possible. Specially on Documentation!! :-) Edgar On 3/7/14 10:12 AM, "Collins, Sean" wrote: >Hi, > >I know everyone is very busy working on the I-3 release, but I wanted >solicit feedback on my devel

Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?

Team, I found that having a mini-summit with a very short notice means excluding a lot of developers of such an interesting topic for Neutron. The OpenStack summit is the opportunity for all developers to come together and discuss the next steps, there are many developers that CAN NOT afford anoth

Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?

ul detail level. What would be your suggestions to make this more inclusive? I think the time and place is the key here - hence Atlanta and few days prior OS summit. Thanks, Eugene. On Mon, Mar 10, 2014 at 10:59 PM, Edgar Magana wrote: > Team, > > I found that having a mini-summit

Re: [openstack-dev] [Neutron] Docs for new plugins

You should be able to add your plugin here: http://docs.openstack.org/havana/config-reference/content/networking-options -plugins.html Thanks, Edgar From: Mohammad Banikazemi Date: Monday, March 10, 2014 2:40 PM To: OpenStack List Cc: Edgar Magana Subject: Re: [openstack-dev] [Neutron

Re: [openstack-dev] [Neutron] Docs for new plugins

Hi There, Basically, we just wanted to be sure that the pre-populated information is accurate and if there is nothing else to add you can close the bug. Thanks, Edgar From: Mohammad Banikazemi Date: Wednesday, March 12, 2014 8:53 PM To: OpenStack List Cc: Edgar Magana , OpenStack List

Re: [openstack-dev] [Neutron][LBaaS] Mini-summit Interest?

That sounds like a good idea Mark! Yes, please do not do it during the World Cup at least the meeting is in Brazil :-) Edgar On 3/13/14 2:11 PM, "Mark McClain" wrote: > >On Mar 13, 2014, at 4:22 PM, Jay Pipes wrote: > >> >> >> I personally would not be able to attend a mini-summit days befo

Re: [openstack-dev] [Neutron] Docs for new plugins

echanismDriver added here yet, even though the code was checked in well over a week ago. How long does it take to autogenerate this page from the code? Thanks! Kyle On Wed, Mar 12, 2014 at 5:10 PM, Edgar Magana mailto:emag...@plumgrid.com> > wrote: > You should be able to add your plugin

Re: [openstack-dev] [Neutron] Docs for new plugins

Thanks for the input Anne! Kyle, Please file the proper bugs in the manual projects to be able to track the progress of this topic. Thanks, Edgar From: Anne Gentle Date: Wednesday, March 19, 2014 4:54 AM To: Edgar Magana Cc: OpenStack List Subject: Re: [openstack-dev] [Neutron] Docs

Re: [openstack-dev] [OpenStack-docs] Neutron documentation to update about new vendor plugin, but without code in repository?

Hi, IMHO we should have a proper way to reference external vendor specific plugins/drivers mostly because at least in Neutron we are considering to move ALL vendor specific code out-of-tree, again it is just a consideration not a fact. So, having a place holder for that will make sense. Thank

Re: [openstack-dev] [Neutron] Neutron documentation to update about new vendor plugin, but without code in repository?

I second Anne’s and Kyle comments. Actually, I like very much the wiki part to provide some visibility for out-of-tree plugins/drivers but not into the official documentation. Thanks, Edgar From: Anne Gentle mailto:a...@openstack.org>> Reply-To: "OpenStack Development Mailing List (not for usa

Re: [openstack-dev] [Neutron] Neutron documentation to update about new vendor plugin, but without code in repository?

maintaining that wiki and I would like to keep just for upstreamed vendor-specific plugins/drivers. Edgar From: Edgar Magana mailto:edgar.mag...@workday.com>> Date: Thursday, October 23, 2014 at 9:46 AM To: "OpenStack Development Mailing List (not for usage questions)" mail

Re: [openstack-dev] [neutron] Neutron mid-cycle announcement

I cant attend it if it moves to the week of Dec 15th. I have already booked a trip for that week and even other commitments. Is there any chance to push it back to Dec 8th? Thanks, Edgar > On Nov 13, 2014, at 2:18 AM, Kyle Mestery wrote: > >> On Tue, Nov 11, 2014 at 7:04 AM, Kyle Mestery w

[openstack-dev] [Nova][Neutron] Error message when Neutron network is running out of IP addresses

Hello Community, When a network subnet runs out of IP addresses a request to create a VM on that network fails with the Error message: "No valid host was found. There are not enough hosts available." In the nova logs the error message is: NoMoreFixedIps: No fixed IP addresses available for ne

Re: [openstack-dev] [Nova][Neutron][Technical Committee] nova-network -> Neutron. Throwing a wrench in the Neutron gap analysis

Jay, I do agree with you on the focus areas. I believe Neutron should focus on the nova-parity (DVR) and DB migrations more than ever, instead of increasing the priority to new API such as the GBP. Actually, yesterday Neutron IRC showed the need of having a more focused work instead of picking in

Re: [openstack-dev] [Neutron] Group Based Policy and the way forward

This is the consequence of a proposal that is not following the standardized terminology (IETF - RFC) for any Policy-based System: http://tools.ietf.org/html/rfc3198 Well, I did bring this point during the Hong Kong Summit but as you can see my comments were totally ignored: https://docs.google

Re: [openstack-dev] [Neutron] Group Based Policy and the way forward

That is the beauty of the open source projects, there is always a smartest reviewer catching out the facts that you don¹t. Edgar On 8/6/14, 10:55 AM, "Sumit Naiksatam" wrote: >Edgar, you seemed to have +2'ed this patch on July 2nd [1]: > >" >Edgar Magana >

Re: [openstack-dev] [Neutron] Group Based Policy and the way forward

ou +2'ed a patch, by stating >that "All looks good to me!". > >On Wed, Aug 6, 2014 at 11:19 AM, Edgar Magana >wrote: >> That is the beauty of the open source projects, there is always a >>smartest >> reviewer catching out the facts that you don¹t. &g

Re: [openstack-dev] [Neutron] Group Based Policy and the way forward

viewers saw that name clash, and still thought it was ok to use the same terminology in such a different context. BP reviews are a community effort right? So of course someones' idea may be different from yours. Regards, Ivar. On Wed, Aug 6, 2014 at 10:29 PM, Edgar Magana mailto:edgar.

Re: [openstack-dev] [Neutron] Group Based Policy and the way forward

ocking the patch feels really unfair. Ivar. On Aug 6, 2014 11:00 PM, "Edgar Magana" mailto:edgar.mag...@workday.com>> wrote: Ivar, Of course and this is why we are having this conversation, in order to merge our different opinions. Edgar From: Ivar Lazzaro mailto:ivarlazz...@gm

Re: [openstack-dev] [Neutron] Bug squashing day

I will be around today. I can help on bug triaging.. Catch me on IRC (emagana) Thank for coordinating this Eugene! Edgar On 8/7/14, 9:19 AM, "Akihiro Motoki" wrote: >Thanks Eugene for initiating Neutron bug squashing day! >I would like to focus on bug triaging and checking bug status rather >t

Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming

I am sorry that I could not attend the GBP meeting. Is there any reason why the IEFT standard is not considered? http://tools.ietf.org/html/rfc3198 I would like to understand the argument why we are creating new names instead of using the standard ones. Edgar From: Ronak Shah mailto:ronak.malav

Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming

in my mind at least (and having been involved in the work that led up to 3198), the members of the groups being discussed here are not PEPs. As 3198 states, being a PEP implies running COPS and I don't see that as necessary for membership in GBP groups. Ryan Moats Edgar Magana mailto:edga

Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming

you are expressing your intent of >doing enforcement at both points you do care then. >18:37:09 regXboi: Edgar Magana suggested using the IETF >phrasing -- enforcement point >18:37:31 i was thinking “edgar point” would be good. and we >won’t have to change our slides from EP. &g

Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming

enStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack-dev] [Neutron][policy] Group Based Policy - Renaming Edgar Magana mailto:edgar.mag...@workday.com>> wrote on 08/07/2014 04:37:39 PM: > From: Edga

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

Big Plus 1 for Mark! Great PTL and Excellent Job in Neutron! Edgar On Fri, Sep 20, 2013 at 1:44 PM, Mark McClain wrote: > > Hi- > > I writing to announce my candidacy for the OpenStack Networking (Neutron) > PTL. > > I am the current Neutron PTL. Our team continued to grow during the > Havana

Re: [openstack-dev] Curvature and Donabe repos are now public!

Debo, Congratulations on this move! The entire Cisco team is doing an awesome work around OpenStack. Cheers, Edgar On 10/3/13 11:43 AM, "Debojyoti Dutta" wrote: >Hi! > >We @Cisco just made the following repos public >https://github.com/CiscoSystems/donabe >https://github.com/CiscoSystems/curv

Re: [openstack-dev] [Neutron][Client] How do I list interfaces on a router?

Jay, You need to find out if the router has ports active, for instance take a look to this code: def delete(self, request, obj_id): try: router_id = self.table.kwargs['router_id'] port = api.neutron.port_get(request, obj_id) if port['device_

Re: [openstack-dev] [Neutron] Common requirements for services' discussion

Hello all, Is anyone working on NATaaS? I know we have some developer working on Router as a Service and they probably want to include NAT functionality but I have some interest in having NAT as a Service. Please, response is somebody is interested in having some discussions about it. Thanks,

Re: [openstack-dev] [Neutron] Common requirements for services' discussion

t;> >> On 10 October 2013 09:55, Bob Melander (bmelande) wrote: >>> Hi Edgar, >>> >>> I'm also interested in a broadening of NAT capability in Neutron using the >>> evolving service framework. >>> >>> Thanks, >>> B

Re: [openstack-dev] [GIT] Reset a commit in Gerrit

Floren, Just just need to send a patch to gerrit. >From you local repo, do the necessary fixes and be sure everything is just as you want. Then simply run: #git commit -a --amend #git review Thanks, Edgar On 10/20/13 11:26 AM, "Floren Llanos" wrote: >Hello, > >I'm a newbie contributor in Ope

[openstack-dev] [Heat] Network topologies

Heat Developers, I am one of the core developers for Neutron who is lately working on the concept of "Network Topologies". I want to discuss with you if the following blueprint will make sense to have in heat or neutron code: https://blueprints.launchpad.net/neutron/+spec/network-topologies-api B

Re: [openstack-dev] [Heat] Network topologies

to having a broader discussion. Thanks, Edgar On 10/28/13 9:47 AM, "Clint Byrum" wrote: >Excerpts from Steven Hardy's message of 2013-10-28 07:47:06 -0700: >> On Sun, Oct 27, 2013 at 08:37:15AM -0700, Edgar Magana wrote: >> > Heat Developers, >> >

Re: [openstack-dev] [Heat] Network topologies

sources then that might >be duplicated effort but if don't need Heat to do that then this blueprint >belongs in Neutron. > >Thanks, >Tim > > > > > >On 10/29/13 1:32 AM, "Steven Hardy" wrote: > >>On Mon, Oct 28, 2013 at 01:19:13PM -0700, Edga

Re: [openstack-dev] [Heat] Network topologies

to do orchestration as you're topology manager will have to call the neutron api in order to create the topology and tear it down. Best, Aaron On Tue, Oct 29, 2013 at 11:33 AM, Edgar Magana wrote: > Tim, > > You statement "building an api that manages a network topology mo

Re: [openstack-dev] [Heat] Network topologies

ing an existing deployment and generating a template file). Also, I >> wanted to point out that in a way you will have to do orchestration as >> you're topology manager will have to call the neutron api in order to >> create the topology and tear it down. >> >> Be

Re: [openstack-dev] [Heat] Design summit etherpads

Steve, Can we meet to talk about the network topologies BP? If you have an open spot I want to chat about it with Heat team Sent from my iPhone > On Nov 5, 2013, at 9:19 AM, Steve Baker wrote: > > Placeholder etherpads have now been created for Heat's design summit sessions > on Thursday and

Re: [openstack-dev] [Neutron] IPv6 sub-team?

Absolutely! +1 Edgar On 11/5/13 3:50 PM, "Collins, Sean (Contractor)" wrote: >Hi, > >Is there any interest in organizing a IPv6 sub-team, similar to how >there are sub-teams for FwaaS, VPNaas, ML2, etc? > >-- >Sean M. Collins >AIM: seanwdp >___ >Ope

[openstack-dev] [Neutron] New plug-ins requirements

Team, It has been decided during the Icehouse summit that all vendor specific plug-ins should enforce remote tempest tests: http://ci.openstack.org/third_party.html I would like to understand if we will apply this rule for any new plug-in during Icehouse or we will start applying this new require

Re: [openstack-dev] [neutron] Group-based Policy Sub-team Meetings

I do agree with need to sometime to recovery from HK and get the meetings started next week! Edgar On 11/13/13 9:57 AM, "Kyle Mestery (kmestery)" wrote: >On Nov 13, 2013, at 10:36 AM, Stephen Wong > wrote: > >> Hi Kyle, >> >>So no meeting this Thursday? >> >I am inclined to skip this wee

Re: [openstack-dev] [Neutron] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

Anita, Could you prepare the invitation letters for the ones that will require a visa?, which is my case. Thanks, Edgar On 11/13/13 8:10 AM, "Anita Kuno" wrote: >Neutron Tempest code sprint > >In the second week of January in Montreal, Quebec, Canadathere will be a >Neutron Tempest code sprin

Re: [openstack-dev] [Neutron] Neutron Tempest code sprint - 2nd week of January, Montreal, QC, Canada

se notify me ASAP if you do, even if you aren't sure you can attend >so I can get the paperwork you need. > >Edgar, can you email me your address to my personal email anteaya at >anteaya dot info so I can work on this for you. > >Thanks, >Anita. > >On 11/13/2013

Re: [openstack-dev] [Neutron] New plug-ins requirements

:15, Kyle Mestery (kmestery) wrote: > >> On Nov 12, 2013, at 2:46 AM, Robert Collins >> wrote: >> > On 12 November 2013 21:15, Edgar Magana wrote: >> >> Team, >> >> >> >> It has been decided during the Icehouse summit that all vendor speci

Re: [openstack-dev] [Neutron] Port mirroring

Hello Rossella, Kyle has a very good point and I wanted to add the documentation request. Be sure you have a wiki/document (not a technical one) that we can easily transfer into the OpenStack Docs. This is a great feature, any idea of the overhead that it will cause? I assume that this is going t

Re: [openstack-dev] [Neutron] Blueprint -- Floating IP Auto Association

Thanks Steven for working on this topic! I would prefer the second approach, although there were some discussions during the summit about moving all calls to Neutron instead of having nova involved. Anyway, just providing my two cents Thanks, Edgar From: Salvatore Orlando Reply-To: OpenStack

Re: [openstack-dev] [Neutron] Port mirroring

n Thu, Nov 14, 2013 at 7:15 PM, Edgar Magana wrote: > Hello Rossella, > > Kyle has a very good point and I wanted to add the documentation request. > Be sure you have a wiki/document (not a technical one) that we can easily > transfer into the OpenStack Docs. > > This is a grea

[openstack-dev] [Neutron] Race condition between DB layer and plugin back-end implementation

Developers, This topic has been discussed before but I do not remember if we have a good solution or not. Basically, if concurrent API calls are sent to Neutron, all of them are sent to the plug-in level where two actions have to be made: 1. DB transaction ­ No just for data persistence but also

  1   2   3   >