Re: [openstack-dev] [neutron] - Neutron team social Pictures

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
Here is the link to the pictures that I took during the Neutron Social in 
Atlanta.

https://souminathan.smugmug.com/OpenStack-Neutron-PTG-Atlanta-2017/

Thanks
Swami

From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Thursday, February 23, 2017 4:09 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on 
Thursday

Hi everyone,

We will meet tonight at Mellow Mushroom at 6PM. It's about a 10-15 minute walk 
from the venue.

Here is the location:

https://goo.gl/maps/FAnmVEVEUSE2

On Feb 23, 2017 13:27, "Duarte Cardoso, Igor" 
<igor.duarte.card...@intel.com<mailto:igor.duarte.card...@intel.com>> wrote:
+1

Best regards,
Igor.

From: Vasudevan, Swaminathan (PNB Roseville) 
[mailto:swaminathan.vasude...@hpe.com<mailto:swaminathan.vasude...@hpe.com>]
Sent: Friday, February 17, 2017 8:30 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on 
Thursday

Count me in.

From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Friday, February 17, 2017 11:19 AM
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

Hi all,

I'm organizing a Neutron social event for Thursday evening in Atlanta somewhere 
near the venue for dinner/drinks. If you're interested, please reply to this 
email with a "+1" so I can get a general count for a reservation.

Cheers,
Kevin Benton

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

[Vasudevan, Swaminathan (PNB Roseville)]

+1

From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Thursday, February 23, 2017 4:09 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on 
Thursday

Hi everyone,

We will meet tonight at Mellow Mushroom at 6PM. It's about a 10-15 minute walk 
from the venue.

Here is the location:

https://goo.gl/maps/FAnmVEVEUSE2

On Feb 23, 2017 13:27, "Duarte Cardoso, Igor" 
<igor.duarte.card...@intel.com<mailto:igor.duarte.card...@intel.com>> wrote:
+1

Best regards,
Igor.

From: Vasudevan, Swaminathan (PNB Roseville) 
[mailto:swaminathan.vasude...@hpe.com<mailto:swaminathan.vasude...@hpe.com>]
Sent: Friday, February 17, 2017 8:30 PM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on 
Thursday

Count me in.

From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Friday, February 17, 2017 11:19 AM
To: openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>
Subject: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

Hi all,

I'm organizing a Neutron social event for Thursday evening in Atlanta somewhere 
near the venue for dinner/drinks. If you're interested, please reply to this 
email with a "+1" so I can get a general count for a reservation.

Cheers,
Kevin Benton

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

[Vasudevan, Swaminathan (PNB Roseville)]

Count me in.

From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Friday, February 17, 2017 11:19 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [neutron] - Neutron team social in Atlanta on Thursday

Hi all,

I'm organizing a Neutron social event for Thursday evening in Atlanta somewhere 
near the venue for dinner/drinks. If you're interested, please reply to this 
email with a "+1" so I can get a general count for a reservation.

Cheers,
Kevin Benton
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [docs] Stepping down from core

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Matt,
Thanks for all your efforts in documenting.
It was pleasure working with you.
Looking forward to see you contribute back to OpenStack.

Thanks
Swami

From: Matt Kassawara [mailto:mkassaw...@gmail.com]
Sent: Wednesday, December 21, 2016 8:11 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: [openstack-dev] [docs] Stepping down from core

Howdy!

After several years of contributing to OpenStack documentation, a significant 
change in my career path warrants resigning from my role as a core reviewer. 
Working with the OpenStack community was a great experience and I hope it 
continues to grow... with sufficient documentation, of course.

Cheers,
Matt
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Vasudevan, Swaminathan (PNB Roseville)]

+1

From: Armando M. [mailto:arma...@gmail.com]
Sent: Thursday, December 15, 2016 3:15 PM
To: OpenStack Development Mailing List (not for usage questions) 

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

Hi neutrinos,

Miguel Lavalle has been driving the project forward consistently and reliably. 
I would like to propose him to be entrusted with +2/+A rights in the areas he's 
been most prolific, which are L3 and DHCP.

At the same time, I'd like to propose Brian Haley as our next Chief L3 Officer. 
Both of them have worked with Carl Baldwin extensively and that can only be a 
guarantee of quality.

Cheers,
Armando

[1] https://review.openstack.org/#/c/411531/
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston as service LTs

[Vasudevan, Swaminathan (PNB Roseville)]

+1

From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Thursday, December 15, 2016 5:00 PM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: Re: [openstack-dev] [neutron] proposing Ryan Tidwell and Nate Johnston 
as service LTs

+1

On Dec 15, 2016 19:03, "Armando M." 
> wrote:
Hi neutrinos,

I would like to propose Ryan and Nate as the go-to fellows for service-related 
patches.

Both are core in their repos of focus, namely neutron-dynamic-routing and 
neutron-fwaas, and have a good understanding of the service framework, the 
agent framework and other bits and pieces. At this point, entrusting them with 
the responsibility is almost a formality.

Cheers,
Armando

[1] https://review.openstack.org/#/c/411536/

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

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

[Vasudevan, Swaminathan (PNB Roseville)]

+1

From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Tuesday, December 13, 2016 6:57 PM
To: OpenStack Development Mailing List (not for usage questions) 

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

+1

On Dec 13, 2016 17:27, "Armando M." 
> wrote:
Hi folks,

Abhishek Raut's recent involvement in OSC and python-neutronclient has helped 
moving a few efforts along in the right direction. I would like to suggest we 
double down on core firepower for the neutronclient repo alongside Akihiro [1].

This not only will help speed up our transition to OSC CLI, but also improve 
the number of folks who can effectively liasion with the OSC team, and look 
after the needs of neutron's client repo.

Many thanks,
Armando

[1] https://review.openstack.org/#/c/410485/

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

Re: [openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Assaf,
Sorry to hear that you are stepping down. Thanks for your contribution to 
neutron and making the test suite more stable.
Wish you all success in your current job.

Thanks
Swami

-Original Message-
From: Assaf Muller [mailto:as...@redhat.com] 
Sent: Monday, November 28, 2016 10:59 AM
To: OpenStack Development Mailing List (not for usage questions) 

Subject: [openstack-dev] [neutron] Stepping down as testing lieutenant and from 
the core & drivers teams

Hi all,

For the past few months I've been gaining more responsibilities within Red Hat. 
I have less time to dedicate to personal contribution and it's had a 
considerable tole on my ability to perform my duties upstream to the degree of 
effectiveness I am satisfied with. To that end, I've decided that the right 
thing to do is to hand over my testing lieutenant responsibilities to Jakub 
Libosvar, and to step down from the core and drivers team.

This is a bitter sweet moment. I'm enormously proud to see the progress Neutron 
as a platform, community and as a reference implementation have made over the 
last 3 years and I'm thrilled to have taken part in that. It's grown from an 
experiment to a ubiquitous OpenStack project with a proven, robust and scalable 
batteries-included implementation used at the largest retail, insurance, 
banking, web and telco (And more!) companies in the world.
My focus will remain on OpenStack networking but my contributions will be 
indirect through my amazing team members. The people leading Quantum when I 
joined are nearly all gone and luckily we've seen a continuous influx of fresh 
talent ready to take over leadership responsibilities. I'm confident the wheel 
will keep on spinning and the project will continue stepping down the right 
path.

I'll still be on IRC and I'll be working over the upcoming couple of weeks to 
hand off any specific tasks I had going on. Have fun folks.

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

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

Re: [openstack-dev] [Neutron] Stepping down from core

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Carl,
Sorry to hear that you are stepping down as core.
Hope to see you back in OpenStack neutron and thanks for all the work and 
reviews that you have done.
Wish you all success.

Thanks
Swami

From: Carl Baldwin [mailto:c...@ecbaldwin.net]
Sent: Thursday, November 17, 2016 10:43 AM
To: OpenStack Development Mailing List 
Subject: [openstack-dev] [Neutron] Stepping down from core

Neutron (and Openstack),

It is with regret that I report that my work situation has changed such that 
I'm not able to keep up with my duties as a Neutron core reviewer, L3 
lieutenant, and drivers team member. My participation has dropped off 
considerably since Newton was released and I think it is fair to step down and 
leave an opening for others to fill. There is no shortage of talent in Neutron 
and Openstack and I know I'm leaving it in good hands.

I will be more than happy to come back to full participation in Openstack and 
Neutron in the future if things change again in that direction. This is a great 
community and I've had a great time participating and learning with you all.

Well, I don't want to drag this out. I will still be around on IRC and will be 
happy to help out where I am able. Feel free to ping me.

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

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

[Vasudevan, Swaminathan (PNB Roseville)]

Congrats! Ihar.

From: Armando M. [mailto:arma...@gmail.com]
Sent: Saturday, September 17, 2016 9:41 AM
To: OpenStack Development Mailing List (not for usage questions) 

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

Hi folks,

I would like to propose Ihar to become a member of the Neutron drivers team [1].

Ihar wide knowledge of the Neutron codebase, and his longstanding duties as 
stable core, downstream package whisperer, release and oslo liaison (I am sure 
I am forgetting some other capacity he is in) is going to put him at great 
comfort in the newly appointed role, and help him grow and become wise even 
further.

Even though we have not been meeting regularly lately we will resume our 
Thursday meetings soon [2], and having Ihar onboard by then will be highly 
beneficial.

Please, join me in welcome Ihar to the team.

Cheers,
Armando

[1] 
http://docs.openstack.org/developer/neutron/policies/neutron-teams.html#drivers-team
[2] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Neutron: Octavia: LBaaS: RFE created for DVR support for unbound allowed_address_pair port with FIP which are associated with multiple VMs that are active.

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
There has been recently a lot of requests for Neutron DVR to support unbound 
allowed_address_pair port with FIP which are associated with multiple VMs that 
are ACTIVE to provide High Availability to the VMs.

This use case is being heavily used by Octavia.

Based on the request and the current DVR design I have put together an RFE and 
I need the community input to proceed further with your feedback and thoughts.

https://bugs.launchpad.net/neutron/+bug/1583694

Please provide your feedback on thoughts on the RFE.

Thanks.

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.com


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

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

[Vasudevan, Swaminathan (PNB Roseville)]

+1 for both.

From: Kevin Benton [mailto:ke...@benton.pub]
Sent: Tuesday, May 17, 2016 11:06 AM
To: OpenStack Development Mailing List (not for usage questions) 

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

+1 for both

On Tue, May 17, 2016 at 5:57 AM, Kyle Mestery 
> wrote:
+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; liberty: 68 reviews (3rd place in the top); kilo: 16 
> reviews.
>
> Brian helped the project with stabilizing liberty neutron/DVR jobs, and with 
> other L3 related stable matters. In his stable reviews, he shows attention to 
> details.
>
> If Brian is added to the team, I will make sure he is aware of all stable 
> policy intricacies.
>
> Side note: recently I added another person to the team (Cedric Brandilly), 
> and now I realize that I haven’t followed the usual approval process. That 
> said, the person also has decent stable review stats, and is aware of the 
> policy. If someone has doubts about that addition to the team, please ping me 
> and we will discuss how to proceed.
>
> Ihar
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

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

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

[Vasudevan, Swaminathan (PNB Roseville)]

Count me in. +1.

Thanks
Swami

-Original Message-
From: Kyle Mestery [mailto:mest...@mestery.com] 
Sent: Monday, April 25, 2016 11:07 AM
To: OpenStack Development Mailing List (not for usage questions) 

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

OK, there is enough interest, I'll find a place on 6th Street for us and get a 
reservation for Thursday around 7 or so.

Thanks folks!

On Mon, Apr 25, 2016 at 12:30 PM, Zhou, Han  wrote:
> +1 :)
>
> Han Zhou
> Irc: zhouhan
>
>
> On Monday, April 25, 2016, Korzeniewski, Artur 
>  wrote:
>>
>> Sign me up :)
>>
>> Artur
>> IRC: korzen
>>
>> -Original Message-
>> From: Darek Smigiel [mailto:smigiel.dari...@gmail.com]
>> Sent: Monday, April 25, 2016 7:19 PM
>> To: OpenStack Development Mailing List (not for usage questions) 
>> 
>> Subject: Re: [openstack-dev] [neutron] Social at the summit
>>
>> Count me in!
>> Will be good to meet all you guys!
>>
>> Darek (dasm) Smigiel
>>
>> > On Apr 25, 2016, at 12:13 PM, Doug Wiegley 
>> >  wrote:
>> >
>> >
>> >> On Apr 25, 2016, at 12:01 PM, Ihar Hrachyshka 
>> >> 
>> >> wrote:
>> >>
>> >> WAT???
>> >>
>> >> It was never supposed to be core only. Everyone is welcome!
>> >
>> > +2
>> >
>> > irony intended.
>> >
>> > Socials are not controlled by gerrit ACLs.  :-)
>> >
>> > doug
>> >
>> >>
>> >> Sent from my iPhone
>> >>
>> >>> On 25 Apr 2016, at 11:56, Edgar Magana 
>> >>> wrote:
>> >>>
>> >>> Would you extend it to ex-cores?
>> >>>
>> >>> Edgar
>> >>>
>> >>>
>> >>>
>> >>>
>>  On 4/25/16, 10:55 AM, "Kyle Mestery"  wrote:
>> 
>>  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 for usage
>>  questions)
>>  Unsubscribe:
>>  openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>  http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-de
>>  v
>> >>> _
>> >>> ___ __ OpenStack Development Mailing List (not for usage 
>> >>> questions)
>> >>> Unsubscribe:
>> >>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >>
>> >> __
>> >> ___ _ OpenStack Development Mailing List (not for usage 
>> >> questions)
>> >> Unsubscribe:
>> >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>> >
>> >
>> > ___
>> > ___  OpenStack Development Mailing List (not for usage 
>> > questions)
>> > Unsubscribe:
>> > openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>> _
>> _ OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>> _
>> _ OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe: 
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __
>  OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>

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

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

[openstack-dev] Neutron: No DVR meeting for this week and week after.

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
We will not be having our regular DVR meeting this week and for next week.

We will resume our meeting on May 4th 2016.

Thanks.

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.com


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

Re: [openstack-dev] [Neutron] - DVR L3 data plane performance results and scenarios

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Gal Sagie,
Let me try to pull in the data and will provide you the information.
Thanks
Swami

From: Gal Sagie [mailto:gal.sa...@gmail.com]
Sent: Thursday, February 18, 2016 9:36 PM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Yuli Stremovsky; Shlomo Narkolayev; Eran Gampel
Subject: Re: [openstack-dev] [Neutron] - DVR L3 data plane performance results 
and scenarios

Hi Swami,

Thanks for the reply, is there any detailed links that describe this that we 
can look at?

(Of course that having results without the full setup (hardware/ NIC, CPU and 
threads for OVS and so on..) details
and without the full scenario details is a bit hard, regardless however i hope 
it will give us at least
an estimation where we are at)

Thanks
Gal.

On Thu, Feb 18, 2016 at 9:34 PM, Vasudevan, Swaminathan (PNB Roseville) 
<swaminathan.vasude...@hpe.com<mailto:swaminathan.vasude...@hpe.com>> wrote:
Hi Gal Sagie,
Yes there was some performance results on DVR that we shared with the community 
during the Liberty summit in Vancouver.

Also I think there was a performance analysis that was done by Oleg Bondarev on 
DVR during the Paris summit.

We have done lot more changes to the control plane to improve the scale and 
performance in DVR during the Mitaka cycle and will be sharing some performance 
results in the upcoming summit.

Definitely we can align on our approach and have all those results captured in 
the upstream for the reference.

Please let me know if you need any other information.

Thanks
Swami

From: Gal Sagie [mailto:gal.sa...@gmail.com<mailto:gal.sa...@gmail.com>]
Sent: Thursday, February 18, 2016 6:06 AM
To: OpenStack Development Mailing List (not for usage questions); Eran Gampel; 
Shlomo Narkolayev; Yuli Stremovsky
Subject: [openstack-dev] [Neutron] - DVR L3 data plane performance results and 
scenarios

Hello All,

We have started to test Dragonflow [1] data plane L3 performance and was 
wondering
if there is any results and scenarios published for the current Neutron DVR
that we can compare and learn the scenarios to test.

We mostly want to validate and understand if our results are accurate and also 
join the
community in defining base standards and scenarios to test any solution out 
there.

For that we also plan to join and contribute to openstack-performance [2] 
efforts which to me
are really important.

Would love any results/information you can share, also interested in control 
plane
testing and API stress tests (either using Rally or not)

Thanks
Gal.

[1] http://docs.openstack.org/developer/dragonflow/distributed_dragonflow.html
[2] https://github.com/openstack/performance-docs

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



--
Best Regards ,

The G.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

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

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
Great Job!

Thanks
Swami

From: Armando M. [mailto:arma...@gmail.com]
Sent: Friday, February 19, 2016 9:07 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial 
upgrade - Nova metadata failure



On 19 February 2016 at 04:43, Sean Dague 
> wrote:
On 02/18/2016 09:50 PM, Armando M. wrote:
>
>
> On 18 February 2016 at 08:41, Sean M. Collins 
> 
> >> wrote:
>
> This week's update:
>
> Armando was kind enough to take a look[1], since he's got a fresh
> perspective. I think I've been suffering from Target Fixation[1]
> where I failed to notice a couple other failures in the logs.
>
>
> It's been fun, and I am glad I was able to help. Once I validated the
> root cause of the metadata failure [1], I got run [2] and a clean pass
> in [3] :)
>
> There are still a few things to iron out, ie. choosing metadata over
> config-drive, testing both in the gate etc. But that's for another day.
>
> Cheers,
> Armando
>
> [1] https://bugs.launchpad.net/nova/+bug/1545101/comments/4
> [2] 
> http://logs.openstack.org/00/281600/6/experimental/gate-grenade-dsvm-neutron-multinode/40e16c8/
> [3] 
> http://logs.openstack.org/00/281600/6/experimental/gate-grenade-dsvm-neutron-multinode/40e16c8/logs/testr_results.html.gz

I want to thank everyone that's been working on this issue profusely.
This exposed a release critical bug in Nova that we would not have
caught otherwise. Finding that before milestone 3 is a huge win and
gives us a lot more options in fixing it correctly.

I think we've got the proper fix now -
https://review.openstack.org/#/c/279721/ (fingers crossed). The metadata
server is one of the least tested components we've got on the Nova side,
so I'll be looking at ways to fix that problem and hopefully avoid
situations like this again.

Now that the blocking issue has been identified, I filed project-config change 
[1] to enable us to test the Neutron Grenade multinode more thoroughly.

[1] https://review.openstack.org/#/c/282428/


-Sean

--
Sean Dague
http://dague.net

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

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

Re: [openstack-dev] [Neutron] - DVR L3 data plane performance results and scenarios

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Gal Sagie,
Yes there was some performance results on DVR that we shared with the community 
during the Liberty summit in Vancouver.

Also I think there was a performance analysis that was done by Oleg Bondarev on 
DVR during the Paris summit.

We have done lot more changes to the control plane to improve the scale and 
performance in DVR during the Mitaka cycle and will be sharing some performance 
results in the upcoming summit.

Definitely we can align on our approach and have all those results captured in 
the upstream for the reference.

Please let me know if you need any other information.

Thanks
Swami

From: Gal Sagie [mailto:gal.sa...@gmail.com]
Sent: Thursday, February 18, 2016 6:06 AM
To: OpenStack Development Mailing List (not for usage questions); Eran Gampel; 
Shlomo Narkolayev; Yuli Stremovsky
Subject: [openstack-dev] [Neutron] - DVR L3 data plane performance results and 
scenarios

Hello All,

We have started to test Dragonflow [1] data plane L3 performance and was 
wondering
if there is any results and scenarios published for the current Neutron DVR
that we can compare and learn the scenarios to test.

We mostly want to validate and understand if our results are accurate and also 
join the
community in defining base standards and scenarios to test any solution out 
there.

For that we also plan to join and contribute to openstack-performance [2] 
efforts which to me
are really important.

Would love any results/information you can share, also interested in control 
plane
testing and API stress tests (either using Rally or not)

Thanks
Gal.

[1] http://docs.openstack.org/developer/dragonflow/distributed_dragonflow.html
[2] https://github.com/openstack/performance-docs
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [neutron][dvr]

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Sudhakar,
I don’t think there was any specific reason behind this.
But we can definitely check for the config flag and then add the topic 
‘dvr_update’.
Go ahead and file a bug and we can address it.

Thanks
Swami

From: Sudhakar Gariganti [mailto:sudhakar.gariga...@gmail.com]
Sent: Wednesday, January 27, 2016 10:00 PM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev][neutron][dvr]

Hi all,

One basic question related to DVR topic 'dvr_update'. In OVS Neutron agent, I 
see that the dvr_update topic is being added to the consumer list irrespective 
of DVR being enabled or not. Because of this, even though I have disabled DVR 
in my environment, I still see the agent subscribe and listen on dvr_update 
topic.

Is there any reason for enabling the DVR topic by default, unlike l2_pop which 
makes the agent subscribe to the l2_pop topic only when l2_pop is enabled??

Thanks,
Sudhakar.
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron]{l2-gateway] is this project alive

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Gary,
I think it is still active.
What are your concerns, I can talk to the team.
Thanks
Swami

From: Gary Kotton [mailto:gkot...@vmware.com]
Sent: Tuesday, January 12, 2016 6:14 AM
To: OpenStack List
Subject: [openstack-dev] [Neutron]{l2-gateway] is this project alive

Its like a desert out here trying to get a review…
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Nova/Neutron Folks,
Are we with an agreement on the Nova/Neutron related changes for addressing the 
Live Migration issues.
We started this thread couple of weeks back and it went silent.
The discussion is still active and being discussed as part of the bug.
https://bugs.launchpad.net/neutron/+bug/1456073

Please add in your comments if you have any issues or concerns.

Thanks
Swami

From: Vasudevan, Swaminathan (PNB Roseville)
Sent: Friday, December 18, 2015 10:15 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

Hi Oleg/Sean M Collins/Carl_baldwin/Kevin Benton/GaryK,

Here is my thought. I have updated the bug report with the details. But this is 
for your information.


Oleg in my opinion, the right time to create the floatingip infrastructure 
would be before the vm actually migrates and is planning to migrate.

1. If we get the "future_host" for migration information from the nova, we can 
prepare the host for the fip migration - like
   Create Router namespace
   Create FIP namespace
   Associate the Router and FIP Namespace.
  I have made some headway with this on this patch.
 https://review.openstack.org/#/c/259171/

2. In order for this to be there, we have to track the port with respect to the 
"old_host", "cur_host" and "new_host" or "future_host".
   For this I would suggest that we make changes to the port-binding table to 
handle all "host" changes.
  In this case the old_host and the cur_host can be the same. The new_host 
denotes where the port is intended to move. Once we get this information, the 
server can pre-populate the details and send it to the agent to create the fip 
namespace.
  In order to address this I have already created a patch.
  https://review.openstack.org/#/c/259299/

3. The thing that we need more should we need to have a different type of 
"event_notifier" such as "MIGRATE_START" or "MIGRATE_END" for the port, or else 
are we going to make use of the same "UPDATE_PORT", "BEFORE_UPDATE" for this. 
-- This should be considered.

4. With all this infrastructure, when "NOVA" provides us a notification before 
"pre-migration" to setup the L3, then we can go ahead and create it.

5. If there are any other issues on the neutron side, we can notify 'NOVA" that 
network-is-not-ready for migration and NOVA should take necessary action.

6. If everything is fine, we send a "OK" message, and NOVA will proceed with 
the migration.

7. If NOVA errors out, it should send a reply back to us and about its state 
and we should revert the state on our side.

Please let me know if you have any other questions.


Thanks
Swami

From: Oleg Bondarev [mailto:obonda...@mirantis.com]
Sent: Friday, December 18, 2015 2:16 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

I think it might be a bit early to start a cross-project discussion on this.
I'd suggest to first figure out what questions do we have, what would we like 
to get from nova.
So I think it'd be more constructive if we first think on it within neutron 
team.
I left some questions on the bug [1], please see comment #8

[1] https://bugs.launchpad.net/neutron/+bug/1456073

Thanks,
Oleg

On Fri, Dec 18, 2015 at 12:14 AM, Vasudevan, Swaminathan (PNB Roseville) 
<swaminathan.vasude...@hpe.com<mailto:swaminathan.vasude...@hpe.com>> wrote:
Hi Sean M. Collins,
Thanks for the information.
It would be great if we can bring in the right people from both sides to 
discuss and solve this problem
Please let me know if you can pull in the right people from the nova side and I 
can get the people from the neutron side.

Thanks
Swami

-Original Message-
From: Sean M. Collins [mailto:s...@coreitpro.com<mailto:s...@coreitpro.com>]
Sent: Thursday, December 17, 2015 1:04 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

On Thu, Dec 17, 2015 at 02:08:42PM EST, Vasudevan, Swaminathan (PNB Roseville) 
wrote:
> Hi Folks,
> I would like organize a meeting between the Nova and Neutron team to work 
> refining the Nova/Neutron notificiations for the Live Migration.
>
> Today we only have Notification from Neutron to Nova on any port status 
> update.
>
> But we don't have any similar notification from Nova on any Migration state 
> change.
> Neutron L3 will be interested in knowing the state change for vm migration 
> and can take necessary action pro-actively to create the necessary L3 related 
> plumbing that is required.
>
> Here are some of the bugs that are currently filed with respect to nova live 
> migration and neutron.
> htt

Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Oleg/Sean M Collins/Carl_baldwin/Kevin Benton/GaryK,

Here is my thought. I have updated the bug report with the details. But this is 
for your information.


Oleg in my opinion, the right time to create the floatingip infrastructure 
would be before the vm actually migrates and is planning to migrate.

1. If we get the "future_host" for migration information from the nova, we can 
prepare the host for the fip migration - like
   Create Router namespace
   Create FIP namespace
   Associate the Router and FIP Namespace.
  I have made some headway with this on this patch.
 https://review.openstack.org/#/c/259171/

2. In order for this to be there, we have to track the port with respect to the 
"old_host", "cur_host" and "new_host" or "future_host".
   For this I would suggest that we make changes to the port-binding table to 
handle all "host" changes.
  In this case the old_host and the cur_host can be the same. The new_host 
denotes where the port is intended to move. Once we get this information, the 
server can pre-populate the details and send it to the agent to create the fip 
namespace.
  In order to address this I have already created a patch.
  https://review.openstack.org/#/c/259299/

3. The thing that we need more should we need to have a different type of 
"event_notifier" such as "MIGRATE_START" or "MIGRATE_END" for the port, or else 
are we going to make use of the same "UPDATE_PORT", "BEFORE_UPDATE" for this. 
-- This should be considered.

4. With all this infrastructure, when "NOVA" provides us a notification before 
"pre-migration" to setup the L3, then we can go ahead and create it.

5. If there are any other issues on the neutron side, we can notify 'NOVA" that 
network-is-not-ready for migration and NOVA should take necessary action.

6. If everything is fine, we send a "OK" message, and NOVA will proceed with 
the migration.

7. If NOVA errors out, it should send a reply back to us and about its state 
and we should revert the state on our side.

Please let me know if you have any other questions.


Thanks
Swami

From: Oleg Bondarev [mailto:obonda...@mirantis.com]
Sent: Friday, December 18, 2015 2:16 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

I think it might be a bit early to start a cross-project discussion on this.
I'd suggest to first figure out what questions do we have, what would we like 
to get from nova.
So I think it'd be more constructive if we first think on it within neutron 
team.
I left some questions on the bug [1], please see comment #8

[1] https://bugs.launchpad.net/neutron/+bug/1456073

Thanks,
Oleg

On Fri, Dec 18, 2015 at 12:14 AM, Vasudevan, Swaminathan (PNB Roseville) 
<swaminathan.vasude...@hpe.com<mailto:swaminathan.vasude...@hpe.com>> wrote:
Hi Sean M. Collins,
Thanks for the information.
It would be great if we can bring in the right people from both sides to 
discuss and solve this problem
Please let me know if you can pull in the right people from the nova side and I 
can get the people from the neutron side.

Thanks
Swami

-Original Message-
From: Sean M. Collins [mailto:s...@coreitpro.com<mailto:s...@coreitpro.com>]
Sent: Thursday, December 17, 2015 1:04 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

On Thu, Dec 17, 2015 at 02:08:42PM EST, Vasudevan, Swaminathan (PNB Roseville) 
wrote:
> Hi Folks,
> I would like organize a meeting between the Nova and Neutron team to work 
> refining the Nova/Neutron notificiations for the Live Migration.
>
> Today we only have Notification from Neutron to Nova on any port status 
> update.
>
> But we don't have any similar notification from Nova on any Migration state 
> change.
> Neutron L3 will be interested in knowing the state change for vm migration 
> and can take necessary action pro-actively to create the necessary L3 related 
> plumbing that is required.
>
> Here are some of the bugs that are currently filed with respect to nova live 
> migration and neutron.
> https://bugs.launchpad.net/neutron/+bug/1456073
> https://bugs.launchpad.net/neutron/+bug/1414559
>
> Please let me know who will be interested in participating in the discussion.
> It would be great if we get some cores attention from "Nova and Neutron".
>
> Thanks.
> Swaminathan Vasudevan
> Systems Software Engineer (TC)


Cool. Brent and I are inter-project liaisons between Neutron and Nova, so let 
us know what we can do to help raise awareness on both sides.

https://wiki.openstack.org/wiki/CrossProjectLiaisons#Inter-project_Liaisons

--
Sean M. Collins

___

Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Sean M. Collins,
Thanks for the information.
It would be great if we can bring in the right people from both sides to 
discuss and solve this problem
Please let me know if you can pull in the right people from the nova side and I 
can get the people from the neutron side.

Thanks
Swami

-Original Message-
From: Sean M. Collins [mailto:s...@coreitpro.com] 
Sent: Thursday, December 17, 2015 1:04 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

On Thu, Dec 17, 2015 at 02:08:42PM EST, Vasudevan, Swaminathan (PNB Roseville) 
wrote:
> Hi Folks,
> I would like organize a meeting between the Nova and Neutron team to work 
> refining the Nova/Neutron notificiations for the Live Migration.
> 
> Today we only have Notification from Neutron to Nova on any port status 
> update.
> 
> But we don't have any similar notification from Nova on any Migration state 
> change.
> Neutron L3 will be interested in knowing the state change for vm migration 
> and can take necessary action pro-actively to create the necessary L3 related 
> plumbing that is required.
> 
> Here are some of the bugs that are currently filed with respect to nova live 
> migration and neutron.
> https://bugs.launchpad.net/neutron/+bug/1456073
> https://bugs.launchpad.net/neutron/+bug/1414559
> 
> Please let me know who will be interested in participating in the discussion.
> It would be great if we get some cores attention from "Nova and Neutron".
> 
> Thanks.
> Swaminathan Vasudevan
> Systems Software Engineer (TC)


Cool. Brent and I are inter-project liaisons between Neutron and Nova, so let 
us know what we can do to help raise awareness on both sides.

https://wiki.openstack.org/wiki/CrossProjectLiaisons#Inter-project_Liaisons

--
Sean M. Collins

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

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

[openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
I would like organize a meeting between the Nova and Neutron team to work 
refining the Nova/Neutron notificiations for the Live Migration.

Today we only have Notification from Neutron to Nova on any port status update.

But we don't have any similar notification from Nova on any Migration state 
change.
Neutron L3 will be interested in knowing the state change for vm migration and 
can take necessary action pro-actively to create the necessary L3 related 
plumbing that is required.

Here are some of the bugs that are currently filed with respect to nova live 
migration and neutron.
https://bugs.launchpad.net/neutron/+bug/1456073
https://bugs.launchpad.net/neutron/+bug/1414559

Please let me know who will be interested in participating in the discussion.
It would be great if we get some cores attention from "Nova and Neutron".

Thanks.
Swaminathan Vasudevan
Systems Software Engineer (TC)


Hewlett Packard Enterprise
Networking Business Unit
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hpe.com


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

[openstack-dev] [Neutron][DVR] - No IRC Meeting for the next two weeks.

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
We will not be having our DVR sub-team meeting for the next two weeks.

Dec 23rd 2015
Dec 30th 2015.

We will resume our meeting on "Jan 6th 2016".

If you have any questions please ping us in IRC or send an email to the 
distribution list.

https://wiki.openstack.org/wiki/Meetings/Neutron-DVR


Wish you all Happy Holidays and Happy New Year.

Thanks
Swami

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

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

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Armando/Carl,
Yes based on Carl’s recommendation I have categorized the bugs in the Wiki 
below right now. If you think adding an Etherpad will be more appropriate, we 
can add one.

https://wiki.openstack.org/wiki/Meetings/Neutron-DVR


Thanks
Swami
From: Armando M. [mailto:arma...@gmail.com]
Sent: Friday, December 11, 2015 3:12 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron][DVR]



On 3 December 2015 at 10:46, Carl Baldwin 
> wrote:
I was going to bring this up in the meeting this morning but IRC
troubles prevented it.

After chatting with Armando, I'd like to suggest a few enhancements to
how we're tackling DVR during this cycle.  I'm hoping that these
changes help us to get things done faster and more efficiently.  Let
me know if you think otherwise.

First, I'd like to suggest adding DvrImpact to the comment of any
patches that are meant to improve DVR in some way.  People have asked
me about reviewing DVR changes.  I can show them the DVR backlog [1]
in launchpad but it would be nice to have a DVR specific dashboard.
With DvrImpact in the subject, we can make it even more convenient to
find reviews.

The other change I'd like to propose is to categorize our DVR backlog
in to three categories:  broken, scale (loadimpact), and new features.
I'd propose that we prioritize in that order.  Anyone have any
suggestions for how to tag or otherwise categorize and tackle these?
I know there is a loadimpact (or similar) tag those.  Should we come
up with a couple more tags to divide the rest?

Thoughts?

Another alternative would be to capture the list of stuff to review in an 
etherpad like [1]. It looks like Nova relies on a similar mechanism [2], and it 
sounds it works for them, so it's worth pursuing to see if review velocity 
improves.

Thoughts?
Cheers,
Armando

[1] https://etherpad.openstack.org/p/neutron-dvr
[2] https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking


Carl

[1] https://goo.gl/M5SwfS

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

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

Re: [openstack-dev] Announcing the OpenStack Health Dashboard

[Vasudevan, Swaminathan (PNB Roseville)]

Cool!.

From: Paul Michali [mailto:p...@michali.net]
Sent: Friday, December 04, 2015 12:45 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] Announcing the OpenStack Health Dashboard

Sweet!


On Fri, Dec 4, 2015 at 3:40 PM Matthew Treinish 
> wrote:
Hi Everyone,

As some people may have seen already we've been working on creating a test
results dashboard up and running to visualize the state of the tests running in
the gate. You can get to the dashboard here:

http://status.openstack.org/openstack-health/#/

It's still early for this project (we only started on it back in Sept.), so not
everything is really polished yet and there are still a couple of issues and
limitations.

The biggest current limitation is based on the data store. We're using
subunit2sql as the backend for all the data and right now we only are collecting
results for tempest and grenade runs in the gate and periodic queues. This is
configurable, as any job that emits a subunit stream can use the same mechanism,
and it is something we will likely change in the future.

We also don't have any results for runs that fail before tempest starts running,
since we need a subunit stream to populate the DB with results. However, we have
several proposed paths to fix this, so it's just a matter of time. But for right
now if a job fails before tests start running it isn't counted on the dashboard.

The code for everything lives here:

http://git.openstack.org/cgit/openstack/openstack-health/

If you find an issue feel free to file a bug here:

https://bugs.launchpad.net/openstack-health

We're eager to see this grow to enable the dashboard to suit the needs of anyone
looking at the gate results.

We're tracking work items that need to be done here:

https://etherpad.openstack.org/p/openstack-health-tracking

Please feel free to contribute if you have an idea on how to improve the
dashboard, or want to take on one of the existing TODO items. The only way we'll
be able to grow this into something that fits everyone's needs is if more people
get involved in improving it.

Thanks,

Matthew Treinish
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] DVR + L3 HA + L2pop - Mapping out the work

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Assaf,
Thanks for putting the list together.
We can help to get the pending patches to be reviewed, if that would help.

Thanks
Swami

-Original Message-
From: Assaf Muller [mailto:amul...@redhat.com] 
Sent: Friday, December 04, 2015 2:46 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Neutron] DVR + L3 HA + L2pop - Mapping out the work

There's a patch up for review to integrate DVR and L3 HA:
https://review.openstack.org/#/c/143169/

Let me outline all of the work that has to happen before that patch would be 
useful:

In order for DVR + L3 HA to work in harmony, each feature would have to be 
stable on its own. DVR has its share of problems, and this is being tackled 
full on, with more folks joining the good fight soon. L3 HA also has its own 
problems:

* https://review.openstack.org/#/c/238122/
* https://review.openstack.org/#/c/230481/
* https://review.openstack.org/#/c/250040/

DVR requires l2pop, and l2pop on its own is also problematic (Regardless if DVR 
or L3 HA is turned on). One notable issue is that it screws up live migration:
https://bugs.launchpad.net/neutron/+bug/1443421.
I'd really like to see more focus on Vivek's patch that attempts to resolve 
this issue:
https://review.openstack.org/#/c/175383/

Finally the way L3 HA integrates with l2pop is not something I would recommend 
in production, as described here:
https://bugs.launchpad.net/neutron/+bug/1522980. If I cannot find an owner for 
this work I will reach out to some folks soon.

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

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

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

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Carl,
Sounds reasonable suggestion.
Thanks
Swami

-Original Message-
From: Carl Baldwin [mailto:c...@ecbaldwin.net] 
Sent: Thursday, December 03, 2015 10:47 AM
To: OpenStack Development Mailing List
Subject: [openstack-dev] [Neutron][DVR]

I was going to bring this up in the meeting this morning but IRC troubles 
prevented it.

After chatting with Armando, I'd like to suggest a few enhancements to how 
we're tackling DVR during this cycle.  I'm hoping that these changes help us to 
get things done faster and more efficiently.  Let me know if you think 
otherwise.

First, I'd like to suggest adding DvrImpact to the comment of any patches that 
are meant to improve DVR in some way.  People have asked me about reviewing DVR 
changes.  I can show them the DVR backlog [1] in launchpad but it would be nice 
to have a DVR specific dashboard.
With DvrImpact in the subject, we can make it even more convenient to find 
reviews.

The other change I'd like to propose is to categorize our DVR backlog in to 
three categories:  broken, scale (loadimpact), and new features.
I'd propose that we prioritize in that order.  Anyone have any suggestions for 
how to tag or otherwise categorize and tackle these?
I know there is a loadimpact (or similar) tag those.  Should we come up with a 
couple more tags to divide the rest?

Thoughts?

Carl

[1] https://goo.gl/M5SwfS

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

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

Re: [openstack-dev] [stable][neutron] Kilo is 'security-supported'. What does it imply?

[Vasudevan, Swaminathan (PNB Roseville)]

+1

-Original Message-
From: Carl Baldwin [mailto:c...@ecbaldwin.net] 
Sent: Thursday, November 05, 2015 10:20 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [stable][neutron] Kilo is 'security-supported'. 
What does it imply?

On Thu, Nov 5, 2015 at 8:17 AM, Ihar Hrachyshka  wrote:
> - Releases page on wiki [2] calls the branch ‘Security-supported’ (and 
> it’s not clear what it implies)

I saw this same thing yesterday when it was pointed out in the DVR IRC meeting 
[1].  I have a hard time believing that we want to abandon bug fix support for 
Kilo especially given recent attempts to be more proactive about it [2] (which 
I applaud).  I suspect that there has simply been a mis-communication and we 
need to get the story straight in the wiki pages which Ihar pointed out.

> - StableBranch page though requires that we don’t merge non-critical 
> bug fixes there: "Only critical bugfixes and security patches are acceptable”

Seems a little premature for Kilo.  It is little more than 6 months old.

> Some projects may want to continue backporting reasonable (even though
> non-critical) fixes to older stable branches. F.e. in neutron, I think 
> there is will to continue providing backports for the branch.

+1  I'd like to reiterate my support for backporting appropriate and
sensible bug fixes to Kilo.

> I wonder though whether we would not break some global openstack rules 
> by continuing with those backports. Are projects actually limited 
> about what types of bug fixes are supposed to go in stable branches, 
> or we embrace different models of stable maintenance and allow for 
> some freedom per project?

Carl

[1] 
http://eavesdrop.openstack.org/meetings/neutron_dvr/2015/neutron_dvr.2015-11-04-15.00.log.html
[2] http://lists.openstack.org/pipermail/openstack-dev/2015-October/077236.html

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

[openstack-dev] Neutron DVR Subteam Meeting Resumes from Nov 4th 2015.

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
We would like to resume the Neutron DVR Subteam Meeting starting November 4th 
2015.
If you are an active technical contributor in openstack and would like to 
discuss any DVR related items feel free to join the meeting.

Here are the meeting details.

IRC channel:  #openstack-meeting-alt
Time: 1500 UTC on Wednesdays.

For Agenda and topics to be discussed look at the Wiki below.
https://wiki.openstack.org/wiki/Meetings/Neutron-DVR

Thanks.
Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.com


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

[openstack-dev] [neutron][ml2] - generic port binding for ml2 and dvr

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Rob Kukura,
We are seeing an issue in the ML2 device_context that was modified by you in a 
recent patch to get everything from the PortContext instead of the DVR context.
Right now the PortContext does not seem to return the DVRbinding status, but 
just returns the PortContext and it errors out, since the PortContext does not 
have the attribute status.

https://bugs.launchpad.net/neutron/+bug/1465434

The error is seen when you try to update a distributed virtual router 
interface.

It errors out in port_update_postcommit.

You have mentioned in your TODO comments that it would be addressed by the 
bug 1367391, but I still see a patch in WIP waiting for review.

Can you take a look at this bug please.

Thanks.


Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


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

[openstack-dev] [Neutron]: DVR Presentation slides from the Vancouver summit

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
Unfortunately our presentation video is missing from the OpenStack Vancouver 
summit website.
But there was a lot more request for the slides that we presented in the summit.

Here is the link to the slides that we presented in the OpenStack Vancouver 
summit.
https://drive.google.com/file/d/0B4kh-7VVPWlPYXNaQWxXd1NDdm8/view?usp=sharing

Please let me know if you have any questions.

thanks

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


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

[openstack-dev] Let us make the DVR job voting at the gate.

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
The DVR single node job has been in the check queue for more than a cycle and 
it is pretty stable now and seems to closely follow the neutron-full job.
So this would be the right time to make this job voting.

https://review.openstack.org/#/c/180230/

In the mean-time we also have an experimental multi-node job for the DVR and we 
are working on stabilizing the job in upstream and once stabilized we can make 
that job ( check/voting).

Meanwhile we will also be working on updating the developer guide for people to 
learn more on the DVR.

Thanks.
Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


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

Re: [openstack-dev] [Neutron] service chaining feature development

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Cathy,
Thanks for the information.
Waiting for the invite.
Thanks
Swami


From: Cathy Zhang [mailto:cathy.h.zh...@huawei.com]
Sent: Thursday, April 30, 2015 6:17 PM
To: adolfo.duar...@hp.com; Vikram Choudhary; Isaku Yamahata; Yamahata, Isaku; 
Vasudevan, Swaminathan (PNB Roseville); Anand, Ritesh; 
vishswanan...@hotmail.com; Gal Sagie; Subrahmanyam Ongole; Manish Godara; 
ybaben...@gmail.com; vishwana...@hotmail.com; Palanisamy, Ila (HP Networking); 
Li, Lynn; Vasudevan, Swaminathan (PNB Roseville); adrian.ho...@intel.com; 
Carlos; jdand...@research.att.com; Dirk; ronen.a...@intel.com; 
sram...@brocade.com; A, Keshava; Wu, Hong-Guang 
(ES-Best-Shore-Services-China-BJ); yuriy.babe...@telekom.de; 
ralf.trezec...@telekom.de; ybaben...@gmail.com; Jay-s-b; 
mathieu.rohon@orange.coSum; Migliaccio, Armando; mest...@mestery.com; 
openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Neutron] service chaining feature development

Hello everyone,

Some of you have reached out to me asking questions about when we will start 
meeting discussion on the service chaining feature BPs in OpenStack.

I have set up agoto meeting for an audio meeting discussion so that we can 
sync up thought and bring everyone on the same page in a more efficient way. 
The meeting will be 10am~11am May 5th pacific time. Anyone who has interest in 
this feature development is welcome to join the meeting and contribute together 
to the service chain feature in OpenStack. Hope the time is good for most 
people.


OpenStack BP discussion for service chaining
Please join the meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/199553557, meeting password: 199-553-557
You can also dial in using your phone.
United States +1 (224) 501-3212
Access Code: 199-553-557

-
Following are the links to the Neutron related service chain specs and the bug 
IDs. Feel free to sign up and add you comments/input to the BPs.
https://review.openstack.org/#/c/177946
https://bugs.launchpad.net/neutron/+bug/1450617
https://bugs.launchpad.net/neutron/+bug/1450625



Just FYI. There is an approved service chain project in OPNFV. Here is the link 
to the project page. It will be good to sync up the service chain work between 
the two communities. 
https://wiki.opnfv.org/requirements_projects/openstack_based_vnf_forwarding_graph



Thanks,

Cathy



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

[openstack-dev] No DVR meeting this week

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
No DVR meeting this week.
Thanks

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


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

[openstack-dev] No DVR Meeting today.

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
There will not be DVR meeting this week.
See you all next week.

Thanks.

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


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

Re: [openstack-dev] About DVR limit

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Joehuang,
Thanks for your input and description of the problem.
What you are stating is just have DVR functionality for East-West traffic and 
all North-South traffic should go through the Centralized Router.
The North-South distributed reduces the burden in the Centralized Node. We 
eventually need to get away from the centralized node model.
I am not sure why there would be a use case to go back to the centralized model.

We were even initially planning to distribute the SNAT, but we just left it 
there centralized just to support the legacy services such as VPN.
Once we have service insertion and service chaining then we can distribute the 
SNAT functionality.

If you have a use case and willing to work on it and contribute code upstream, 
please let me know.

Thanks
Swami

From: joehuang [mailto:joehu...@huawei.com]
Sent: Wednesday, January 14, 2015 7:07 PM
To: 龚永生; Vasudevan, Swaminathan (PNB Roseville)
Cc: OpenStack Development Mailing List (not for usage questions)
Subject: RE: Re:RE: [openstack-dev] About DVR limit

Hello,

Yongseng, correct, your description is much more concise, we need a 
configuration:

east-west, DVR
south-north, legacy mode.

Best Regards
Chaoyi Huang ( Joe Huang )

From: 龚永生 [mailto:gong.yongsh...@99cloud.net]
Sent: Thursday, January 15, 2015 10:18 AM
To: Vasudevan, Swaminathan (PNB Roseville)
Cc: joehuang; OpenStack Development Mailing List (not for usage questions)
Subject: Re:RE: [openstack-dev] About DVR limit


Hi, Swami, Joehuang,
in dvr compute nodes, it is 1:1 NAT FIP, means the floatingip for VM, and  it 
is in the namespace of qrouter-.
but in dvr_snat node, it is 1:N NAT IP, it is for neutron router, and for the 
VMs which have no 1:1 FIP, implemented in namesapce snat-xxx.

Joehuang's case can be implemented in legacy mode, I.E. non DVR,
but for the east-west traffic, we should consider the DVR, So I think there is 
a case:
east-west, DVR
south-north, legacy mode.


Thanks
yong sheng gong


在 2015-01-14 13:40:32，Vasudevan, Swaminathan (PNB Roseville) 
swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com 写道：
Hi Joehuang,
FIP today as of Juno can be both in centralized node (dvr_snat) and distributed 
“dvr” compute nodes.
Thanks
Swami

From: joehuang [mailto:joehu...@huawei.commailto:joehu...@huawei.com]
Sent: Tuesday, January 13, 2015 7:49 PM
To: OpenStack Development Mailing List (not for usage questions); 龚永生
Cc: Vasudevan, Swaminathan (PNB Roseville)
Subject: RE: [openstack-dev] About DVR limit

Hi, Swami,

I would like to know whether the FIP under DVR could be configured to 
distributed mode or central mode in Kilo, not find relevant information from 
http://specs.openstack.org/openstack/neutron-specs/.

For example, it will be helpful for following FIP use cases: 1) FIP will be 
addressed centrally by dedicated hardware 2) not all compute nodes have public 
address.

Best Regards
Chaoyi Huang ( Joe Huang )

From: Stamina than Valued an [mailto:souminat...@yahoo.com]
Sent: Wednesday, January 14, 2015 11:05 AM
To: 龚永生
Cc: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com; 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] About DVR limit

Hi yong Zheng,
Yes your understanding is right.
We only support ovs driver.
Regarding HA and multi network support, it will be available in kilo.

Public address consumption for north south traffic for compute node is also 
true. But to address this issue we do have a proposal that is worked out by the 
l3 sub team.

I hope this clarifies your doubts.

Please let me know if I can help you with anything else.

Thanks
Swami

Sent from my iPad

On Jan 13, 2015, at 6:01 PM, 龚永生 
gong.yongsh...@99cloud.netmailto:gong.yongsh...@99cloud.net wrote:
Hi,
 I am yong sheng gong, I want to know if the DVR has these limits besides the 
documented at http://docs.openstack.org/networking-guide/content/ha-dvr.html:

1. one subnet can be connected to DVR router only once, which is confirmed by 
BP https://blueprints.launchpad.net/neutron/+spec/neutron-ovs-dvr-multigateway
2. one network cannot have more than one subnet connecting to DVR routers


So the DVR limits the neutron model to:
one network has just one subnet, and one subnet cannot connect to more than one 
DVR routers.


ps.
req and limits documented at 
http://docs.openstack.org/networking-guide/content/ha-dvr.html::
 DVR requirements

*You must use the ML2 plug-in for Open VSwitch (OVS) to enable DVR.

*Be sure that your firewall or security groups allows UDP traffic over 
the VLAN, GRE, or VXLAN port to pass between the compute hosts.

 DVR limitations

*Distributed virtual router configurations work with the Open vSwitch 
Modular Layer 2 driver only for Juno.

*In order to enable true north-south bandwidth between hypervisors 
(compute nodes), you must use public IP addresses for every compute node and 
enable floating IPs.

*For now, based on the current

Re: [openstack-dev] About DVR limit

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Joehuang,
FIP today as of Juno can be both in centralized node (dvr_snat) and distributed 
“dvr” compute nodes.
Thanks
Swami

From: joehuang [mailto:joehu...@huawei.com]
Sent: Tuesday, January 13, 2015 7:49 PM
To: OpenStack Development Mailing List (not for usage questions); 龚永生
Cc: Vasudevan, Swaminathan (PNB Roseville)
Subject: RE: [openstack-dev] About DVR limit

Hi, Swami,

I would like to know whether the FIP under DVR could be configured to 
distributed mode or central mode in Kilo, not find relevant information from 
http://specs.openstack.org/openstack/neutron-specs/.

For example, it will be helpful for following FIP use cases: 1) FIP will be 
addressed centrally by dedicated hardware 2) not all compute nodes have public 
address.

Best Regards
Chaoyi Huang ( Joe Huang )

From: Stamina than Valued an [mailto:souminat...@yahoo.com]
Sent: Wednesday, January 14, 2015 11:05 AM
To: 龚永生
Cc: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com; 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] About DVR limit

Hi yong Zheng,
Yes your understanding is right.
We only support ovs driver.
Regarding HA and multi network support, it will be available in kilo.

Public address consumption for north south traffic for compute node is also 
true. But to address this issue we do have a proposal that is worked out by the 
l3 sub team.

I hope this clarifies your doubts.

Please let me know if I can help you with anything else.

Thanks
Swami

Sent from my iPad

On Jan 13, 2015, at 6:01 PM, 龚永生 
gong.yongsh...@99cloud.netmailto:gong.yongsh...@99cloud.net wrote:
Hi,
 I am yong sheng gong, I want to know if the DVR has these limits besides the 
documented at http://docs.openstack.org/networking-guide/content/ha-dvr.html:

1. one subnet can be connected to DVR router only once, which is confirmed by 
BP https://blueprints.launchpad.net/neutron/+spec/neutron-ovs-dvr-multigateway
2. one network cannot have more than one subnet connecting to DVR routers


So the DVR limits the neutron model to:
one network has just one subnet, and one subnet cannot connect to more than one 
DVR routers.


ps.
req and limits documented at 
http://docs.openstack.org/networking-guide/content/ha-dvr.html::
 DVR requirements

·You must use the ML2 plug-in for Open VSwitch (OVS) to enable DVR.

·Be sure that your firewall or security groups allows UDP traffic over 
the VLAN, GRE, or VXLAN port to pass between the compute hosts.

 DVR limitations

·Distributed virtual router configurations work with the Open vSwitch 
Modular Layer 2 driver only for Juno.

·In order to enable true north-south bandwidth between hypervisors 
(compute nodes), you must use public IP addresses for every compute node and 
enable floating IPs.

·For now, based on the current neutron design and architecture, DHCP 
cannot become distributed across compute nodes.

thanks,
Yong sheng gong
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] DVR Meeting is cancelled for this week.

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
The DVR Meeting will be cancelled this week.
If there is any agenda we can talk during the L3 sub-team meeting.

Thanks.
Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Topic: Reschedule Router to a different agent with multiple external networks.

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,

Reschedule router if new external gateway is on other network
An L3 agent may be associated with just one external network.
If router's new external gateway is on other network then the router
needs to be rescheduled to the proper l3 agent

This patch was introduced when there was no support for L3-agent to handle 
multiple external networks.

Do we think we should still retain this original behavior even if we have 
support for multiple external networks by single L3-agent.

Can anyone comment on this.

Thanks

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] DVR meeting tomorrow - will be cancelled.

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
There will be not DVR meeting tomorrow.
See you all next week.

Thanks
Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] ./run_tests.sh fails to create the .venv environment for neutron

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,

./run_tests.sh fails to create the .venv with the latest neutron repo.
It fails at MySQL-python.
Does anyone know what is broken.

Downloading/unpacking oslotest=1.1.0 (from -r 
/home/stack/neutron/test-requirements.txt (line 20))
  Downloading oslotest-1.1.0-py2.py3-none-any.whl
Downloading/unpacking psycopg2 (from -r 
/home/stack/neutron/test-requirements.txt (line 21))
  Downloading psycopg2-2.5.4.tar.gz (682kB): 682kB downloaded
  Running setup.py (path:/home/stack/neutron/.venv/build/psycopg2/setup.py) 
egg_info for package psycopg2

Downloading/unpacking MySQL-python (from -r 
/home/stack/neutron/test-requirements.txt (line 22))
  Downloading MySQL-python-1.2.5.zip (108kB): 108kB downloaded
  Running setup.py (path:/home/stack/neutron/.venv/build/MySQL-python/setup.py) 
egg_info for package MySQL-python
sh: 1: mysql_config: not found
Traceback (most recent call last):
  File string, line 17, in module
  File /home/stack/neutron/.venv/build/MySQL-python/setup.py, line 17, in 
module
metadata, options = get_config()
  File setup_posix.py, line 43, in get_config
libs = mysql_config(libs_r)
  File setup_posix.py, line 25, in mysql_config
raise EnvironmentError(%s not found % (mysql_config.path,))
EnvironmentError: mysql_config not found
Complete output from command python setup.py egg_info:
sh: 1: mysql_config: not found

Traceback (most recent call last):

  File string, line 17, in module

  File /home/stack/neutron/.venv/build/MySQL-python/setup.py, line 17, in 
module

metadata, options = get_config()

  File setup_posix.py, line 43, in get_config

libs = mysql_config(libs_r)

  File setup_posix.py, line 25, in mysql_config

raise EnvironmentError(%s not found % (mysql_config.path,))

EnvironmentError: mysql_config not found


Cleaning up...
Command python setup.py egg_info failed with error code 1 in 
/home/stack/neutron/.venv/build/MySQL-python
Storing debug log for failure in /home/stack/.pip/pip.log
Command tools/with_venv.sh pip install --upgrade -r 
/home/stack/neutron/test-requirements.txt failed.
None
stack@ubuntu:~/neutron$

Thanks.

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] DVR meeting cancelled for Sept 17th 2014

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
Neutron DVR meeting will be cancelled on Sept 17th 2014.
We will resume next week.


Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] No DVR Meeting today

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
DVR IRC Meeting for Today is Cancelled.
We will meet next week.
Thanks

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] DVR IRC Meeting for June 18th 2014. - Cancelled.

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
The DVR IRC Meeting for June 18th 2014 will be cancelled.
I will be travelling on these dates so will not be able to run the meeting.
Some of our team members are also busy during this time slot.
So I will be cancelling this meeting.

The reviews are still in progress.


Thanks

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Distributed Virtual Router Meeting Cancelled for May 28th 2014

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
Tomorrow's ( May 28th 2014)  Distributed Virtual Router will be cancelled. ( 
Since most of our team will be in an internal meeting).
We will resume our meeting next week.

Thanks

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] We will start the DVR meeting around 8.20a.m today.

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
I will start the meeting around 8.20a.m today.

Thanks


Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] DVR blueprint document locked / private

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Assaf,
Thanks for letting me know.
This document was completely open and accessible by everyone till last week.
Someone might have changed the settings on this document.

I don't remember that I changed any settings on this document.
The Powerpoint slides link that I forwarded yesterday also captures the same 
details and still that is accessible.

I have opened it again for the public.

If it would have caused any trouble for you to participate in the upstream 
discussions for the last two days, I feel sorry for it.

Feel free to send an email to me, if you have any other issues or concerns.

Thanks
Swami

-Original Message-
From: Assaf Muller [mailto:amul...@redhat.com] 
Sent: Tuesday, February 18, 2014 2:33 AM
To: openstack-dev@lists.openstack.org
Cc: Vasudevan, Swaminathan (PNB Roseville); Baldwin, Carl (HPCS Neutron); 
mmccl...@yahoo-inc.com; Livnat Peer; Sylvain Afchain
Subject: [Neutron] DVR blueprint document locked / private

Regarding the DVR blueprint [1], I noticed that its corresponding Google Doc 
[2] has been private / blocked for nearly a week now. It's very difficult to 
participate in upstream design discussions when the document is literally 
locked.

I would appreciate the re-opening of the document, especially considering the 
recent face to face meeting and the contested discussion points that were 
raised.

[1] https://blueprints.launchpad.net/neutron/+spec/neutron-ovs-dvr
[2] 
https://docs.google.com/document/d/1iXMAyVMf42FTahExmGdYNGOBFyeA4e74sAO3pvr_RjA/edit


Thank you,
Assaf Muller, Cloud Networking Engineer Red Hat 
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Neutron-Distributed Virtual Router Face-to-Face Discussion at Palo Alto, CA - update

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
I have postponed this meeting to the week of February 10th  on Thursday Feb 
13th, so that there is enough time for people to plan to attend this meeting.

Meeting details will be discussed in the neutron meeting and will send out the 
details.

Thanks
Swami

From: Vasudevan, Swaminathan (PNB Roseville)
Sent: Thursday, January 23, 2014 10:21 AM
To: OpenStack Development Mailing List (openstack-dev@lists.openstack.org)
Cc: sylvain.afch...@enovance.com; James Clark, (CES BU) (james.cl...@kt.com); 
cloudbe...@gmail.com; Mark McClain (mark.mccl...@dreamhost.com); sumit 
naiksatam (sumitnaiksa...@gmail.com); Nachi Ueno (na...@ntti3.com)
Subject: Neutron-Distributed Virtual Router Face-to-Face Discussion at Palo 
Alto, CA

Hi Folks,
I would like to invite you all for a Face-to-Face Meeting next week at Palto 
Alto-CA to go over our DVR proposal for Neutron.
The current plan is to have the meeting next week on Thursday, January 30th.

We will be also having a virtual room and conference bridge for remote people 
to join in.

Please send me an email if you are interested and let me know your preferred 
time-slot.

For reference again I am including the google doc links with the proposal 
details.

https://docs.google.com/document/d/1iXMAyVMf42FTahExmGdYNGOBFyeA4e74sAO3pvr_RjA/edit

https://docs.google.com/drawings/d/1GGwbLa72n8c2T3SBApKK7uJ6WLTSRa7erTI_3QNj5Bg/edit


Thanks

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Neutron-Distributed Virtual Router Face-to-Face Discussion at Palo Alto, CA

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
I would like to invite you all for a Face-to-Face Meeting next week at Palto 
Alto-CA to go over our DVR proposal for Neutron.
The current plan is to have the meeting next week on Thursday, January 30th.

We will be also having a virtual room and conference bridge for remote people 
to join in.

Please send me an email if you are interested and let me know your preferred 
time-slot.

For reference again I am including the google doc links with the proposal 
details.

https://docs.google.com/document/d/1iXMAyVMf42FTahExmGdYNGOBFyeA4e74sAO3pvr_RjA/edit

https://docs.google.com/drawings/d/1GGwbLa72n8c2T3SBApKK7uJ6WLTSRa7erTI_3QNj5Bg/edit


Thanks

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Neutron - run_tests.sh fails while creating a Virtual environment

[Vasudevan, Swaminathan (PNB Roseville)]

Hi folks,
Does anyone have an idea why the run_tests.sh script fails when I run it with 
a run_tests.sh -v in Ubuntu.

I have provided the output of the run_tests.sh -V.
It tries to install python-mimeparse and then it raises an exception. See the 
exception below:

Console log:
Requirement already up-to-date: six in ./.venv/lib/python2.7/site-packages 
(from hacking=0.5.6,0.8--r /opt/stack/neutron/test-requirements.txt (line 1))
Requirement already up-to-date: cmd2=0.6.7 in 
./.venv/lib/python2.7/site-packages (from cliff=1.4.3--r 
/opt/stack/neutron/test-requirements.txt (line 3))
Requirement already up-to-date: PrettyTable=0.6,0.8 in 
./.venv/lib/python2.7/site-packages (from cliff=1.4.3--r 
/opt/stack/neutron/test-requirements.txt (line 3))
Requirement already up-to-date: pyparsing=2.0.1 in 
./.venv/lib/python2.7/site-packages (from cliff=1.4.3--r 
/opt/stack/neutron/test-requirements.txt (line 3))
Requirement already up-to-date: stevedore in 
./.venv/lib/python2.7/site-packages (from cliff=1.4.3--r 
/opt/stack/neutron/test-requirements.txt (line 3))
Downloading/unpacking extras (from python-subunit--r 
/opt/stack/neutron/test-requirements.txt (line 9))
  Downloading extras-0.0.3.tar.gz
  Running setup.py (path:/opt/stack/neutron/.venv/build/extras/setup.py) 
egg_info for package extras

Downloading/unpacking Pygments=1.2 (from sphinx=1.1.2,1.2--r 
/opt/stack/neutron/test-requirements.txt (line 10))
  Downloading Pygments-1.6.tar.gz (1.4MB): 1.4MB downloaded
  Running setup.py (path:/opt/stack/neutron/.venv/build/Pygments/setup.py) 
egg_info for package Pygments

Requirement already up-to-date: Jinja2=2.3 in 
./.venv/lib/python2.7/site-packages (from sphinx=1.1.2,1.2--r 
/opt/stack/neutron/test-requirements.txt (line 10))
Downloading/unpacking docutils=0.7 (from sphinx=1.1.2,1.2--r 
/opt/stack/neutron/test-requirements.txt (line 10))
  Downloading docutils-0.11.tar.gz (1.6MB): 1.6MB downloaded
  Running setup.py (path:/opt/stack/neutron/.venv/build/docutils/setup.py) 
egg_info for package docutils

warning: no files found matching 'MANIFEST'
warning: no files found matching '*' under directory 'extras'
warning: no previously-included files matching '.cvsignore' found under 
directory '*'
warning: no previously-included files matching '*.pyc' found under 
directory '*'
warning: no previously-included files matching '*~' found under directory 
'*'
warning: no previously-included files matching '.DS_Store' found under 
directory '*'
Downloading/unpacking python-mimeparse (from testtools=0.9.34--r 
/opt/stack/neutron/test-requirements.txt (line 12))
Cleaning up...
Exception:
Traceback (most recent call last):
  File 
/opt/stack/neutron/.venv/local/lib/python2.7/site-packages/pip/basecommand.py,
 line 122, in main
status = self.run(options, args)
  File 
/opt/stack/neutron/.venv/local/lib/python2.7/site-packages/pip/commands/install.py,
 line 274, in run
requirement_set.prepare_files(finder, force_root_egg_info=self.bundle, 
bundle=self.bundle)
  File /opt/stack/neutron/.venv/local/lib/python2.7/site-packages/pip/req.py, 
line 1173, in prepare_files
self.unpack_url(url, location, self.is_download)
  File /opt/stack/neutron/.venv/local/lib/python2.7/site-packages/pip/req.py, 
line 1320, in unpack_url
retval = unpack_http_url(link, location, self.download_cache, 
self.download_dir, self.session)
  File 
/opt/stack/neutron/.venv/local/lib/python2.7/site-packages/pip/download.py, 
line 555, in unpack_http_url
resp = session.get(target_url, stream=True)
  File 
/opt/stack/neutron/.venv/local/lib/python2.7/site-packages/pip/_vendor/requests/sessions.py,
 line 395, in get
return self.request('GET', url, **kwargs)
  File 
/opt/stack/neutron/.venv/local/lib/python2.7/site-packages/pip/download.py, 
line 237, in request
return super(PipSession, self).request(method, url, *args, **kwargs)
  File 
/opt/stack/neutron/.venv/local/lib/python2.7/site-packages/pip/_vendor/requests/sessions.py,
 line 383, in request
resp = self.send(prep, **send_kwargs)
  File 
/opt/stack/neutron/.venv/local/lib/python2.7/site-packages/pip/_vendor/requests/sessions.py,
 line 486, in send
r = adapter.send(request, **kwargs)
  File 
/opt/stack/neutron/.venv/local/lib/python2.7/site-packages/pip/_vendor/requests/adapters.py,
 line 391, in send
raise Timeout(e)
Timeout: 
(pip._vendor.requests.packages.urllib3.connection.VerifiedHTTPSConnection 
instance at 0x261c7a0, 'Connection to pypi.python.org timed out. (connect 
timeout=15)')

Storing debug log for failure in /tmp/tmpMNihy6
Command tools/with_venv.sh pip install --upgrade -r 
/opt/stack/neutron/test-requirements.txt failed.
None


Thanks.
Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___

[openstack-dev] Distributed Virtual Router Blueprint - Review ( North-South/East West with Services)

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
In the Icehouse summit design session we presented a DVR( Distributed Virtual 
Router) Proposal that was targeted only for East-West Communication and was 
based on a DVR datapath Kernel Driver.

We discussed three different Use cases such as East-West, North-South and 
East-West/North-South with Services.
The feedback that we received from the community was 50% of the audience 
requirement was for North-South and the other 50% was ok with the East-West.
So the action item was to work on East-West and if we have enough sub-team 
members then we can also address the North-South.
Also there were concerns raised about the Kernel Module usage for the DVR 
Datapath.

Based on the feedback that we received and the community interest, we went back 
and re-designed the DVR to support both the East-West and North-South without 
the Kernel Module driver and just using the existing namespace support.
And also will support the existing Services in a hybrid mode.

The updated blueprint is available for review as a google doc.

https://docs.google.com/document/d/1iXMAyVMf42FTahExmGdYNGOBFyeA4e74sAO3pvr_RjA/edit

I would appreciate if you could provide your valuable feedback on the proposal.

Thanks
Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Neutron Distributed Virtual Router

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Nachi,
Yes you are right, NSX deals with (local or distributed) routers and Service 
Routers.
Thanks
Swami


Hi Yong



NSX have two kind of router.

Edge and distributed router.



Edge node will work as some VPN services and advanced service nodes.



Actually, VPNaaS OSS impl is running in l3-agent.

so IMO, we need l3-agent also for basis of some edge services.











2013/12/9 Yongsheng Gong gong...@unitedstack.com:

 If distributed router is good enough, why do we still need non-distributed

 router?





 On Tue, Dec 10, 2013 at 9:04 AM, Ian Wells ijw.ubu...@cack.org.uk wrote:



 I would imagine that, from the Neutron perspective, you get a single

 router whether or not it's distributed.  I think that if a router is

 distributed - regardless of whether it's tenant-tenant or tenant-outside -

 it certainly *could* have some sort of SLA flag, but I don't think a simple

 'distributed' flag is either here or there; it's not telling the tenant

 anything meaningful.





 On 10 December 2013 00:48, Mike Wilson geekinu...@gmail.com wrote:



 I guess the question that immediately comes to mind is, is there anyone

 that doesn't want a distributed router? I guess there could be someone out

 there that hates the idea of traffic flowing in a balanced fashion, but

 can't they just run a single router then? Does there really need to be some

 flag to disable/enable this behavior? Maybe I am oversimplifying things...

 you tell me.



 -Mike Wilson





 On Mon, Dec 9, 2013 at 3:01 PM, Vasudevan, Swaminathan (PNB Roseville)

 swaminathan.vasude...@hp.com wrote:



 Hi Folks,



 We are in the process of defining the API for the Neutron Distributed

 Virtual Router, and we have a question.







 Just wanted to get the feedback from the community before we implement

 and post for review.







 We are planning to use the distributed flag for the routers that are

 supposed to be routing traffic locally (both East West and North South).



 This distributed flag is already there in the neutronclient API, but

 currently only utilized by the Nicira Plugin.



 We would like to go ahead and use the same distributed flag and add an

 extension to the router table to accommodate the distributed flag.







 Please let us know your feedback.







 Thanks.







 Swaminathan Vasudevan



 Systems Software Engineer (TC)











 HP Networking



 Hewlett-Packard



 8000 Foothills Blvd



 M/S 5541



 Roseville, CA - 95747



 tel: 916.785.0937



 fax: 916.785.1815



 email: swaminathan.vasude...@hp.com




Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] Neutron Distributed Virtual Router

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Nachi/Akihiro motoki,

I am not clear.

Today the L3 Service Plugin does not support the service_type attribute to 
define the provider option.



Are we suggesting that we need to include the service_type for the L3 Service 
Plugin and then we can make use of the service_type attribute to distinguish 
between the edge and distributed.





So if I understand correctly, a provider router will be an Edge router and a 
non-provider router will be a distributed router.



Thanks

Swami



I'm +1 for 'provider'.



2013/12/9 Akihiro Motoki mot...@da.jp.nec.com:

 Neutron defines provider attribute and it is/will be used in advanced

 services (LB, FW, VPN).

 Doesn't it fit for a distributed router case? If we can cover all services

 with one concept, it would be nice.



 According to this thread, we assumes at least two types edge and

 distributed.

 Though edge and distributed is a type of implementations, I think they

 are some kind of provider.



 I just would like to add an option. I am open to provider vs distirbute

 attributes.



 Thanks,

 Akihiro



 (2013/12/10 7:01), Vasudevan, Swaminathan (PNB Roseville) wrote:

 Hi Folks,



 We are in the process of defining the API for the Neutron Distributed

 Virtual Router, and we have a question.



 Just wanted to get the feedback from the community before we implement and

 post for review.



 We are planning to use the distributed flag for the routers that are

 supposed to be routing traffic locally (both East West and North South).

 This distributed flag is already there in the neutronclient API, but

 currently only utilized by the Nicira Plugin.

 We would like to go ahead and use the same distributed flag and add an

 extension to the router table to accommodate the distributed flag.



 Please let us know your feedback.



 Thanks.



 Swaminathan Vasudevan

 Systems Software Engineer (TC)

 HP Networking

 Hewlett-Packard

 8000 Foothills Blvd

 M/S 5541

 Roseville, CA - 95747

 tel: 916.785.0937

 fax: 916.785.1815

 email: swaminathan.vasude...@hp.com mailto:swaminathan.vasude...@hp.com


Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Neutron Distributed Virtual Router

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
We are in the process of defining the API for the Neutron Distributed Virtual 
Router, and we have a question.

Just wanted to get the feedback from the community before we implement and post 
for review.

We are planning to use the distributed flag for the routers that are supposed 
to be routing traffic locally (both East West and North South).
This distributed flag is already there in the neutronclient API, but 
currently only utilized by the Nicira Plugin.
We would like to go ahead and use the same distributed flag and add an 
extension to the router table to accommodate the distributed flag.

Please let us know your feedback.

Thanks.

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Neutron] Distributed Virtual Router Discussion

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
Thanks for your interests in the DVR feature.
We should get together to start discussing the details in the DVR.
Please let me know who else is interested, probably the time slot and we can 
start nailing down the details.
 https://blueprints.launchpad.net/neutron/+spec/neutron-ovs-dvr
https://wiki.openstack.org/wiki/Distributed_Router_for_OVS
Thanks
Swami

From: Robin Wang [mailto:cloudbe...@gmail.com]
Sent: Tuesday, October 22, 2013 11:45 AM
To: Artem Dmytrenko; yong sheng gong (gong...@unitedstack.com); OpenStack 
Development Mailing List; Vasudevan, Swaminathan (PNB Roseville)
Subject: Re: Re: [openstack-dev] [Neutron] Distributed Virtual Router Discussion

Hi Artem,

Very happy to see more stackers working on this feature. : )

Note that the images in your document are badly corrupted - maybe my questions 
could already be answered by your diagrams. 
I met the same issue at first. Downloading the doc and open it locally may 
help. It works for me.

Also, a wiki page for DVR/VDR feature is created, including some interesting 
performance test output. Thanks.
https://wiki.openstack.org/wiki/Distributed_Router_for_OVS

Best,
Robin Wang

From: Artem Dmytrenkomailto:nexton...@yahoo.com
Date: 2013-10-22 02:51
To: yong sheng gong 
\(gong...@unitedstack.com\)mailto:gong...@unitedstack.com; 
cloudbe...@gmail.commailto:cloudbe...@gmail.com; OpenStack Development 
Mailing Listmailto:openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] Distributed Virtual Router Discussion
Hi Swaminathan.

I work for a virtual networking startup called Midokura and I'm very interested 
in joining the discussion. We currently have distributed router implementation 
using existing Neutron API. Could you clarify why distributed vs centrally 
located routing implementation need to be distinguished? Another question is 
that are you proposing distributed routing implementation for tenant routers or 
for the router connecting the virtual cloud to the external network? The reason 
that I'm asking this question is because our company would also like to propose 
a router implementation that would eliminate a single point uplink failures. We 
have submitted a couple blueprints on that topic 
(https://blueprints.launchpad.net/neutron/+spec/provider-router-support, 
https://blueprints.launchpad.net/neutron/+spec/bgp-dynamic-routing) and would 
appreciate an opportunity to collaborate on making it a reality.

Note that the images in your document are badly corrupted - maybe my questions 
could already be answered by your diagrams. Could you update your document with 
legible diagrams?

Looking forward to further discussing this topic with you!

Sincerely,
Artem Dmytrenko


On Mon, 10/21/13, Vasudevan, Swaminathan (PNB Roseville) 
swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com wrote:

 Subject: [openstack-dev] Distributed Virtual Router Discussion
 To: yong sheng gong 
(gong...@unitedstack.commailto:gong...@unitedstack.com) 
gong...@unitedstack.commailto:gong...@unitedstack.com, 
cloudbe...@gmail.commailto:cloudbe...@gmail.com 
cloudbe...@gmail.commailto:cloudbe...@gmail.com, OpenStack Development 
Mailing List 
(openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
 Date: Monday, October 21, 2013, 12:18 PM









 Hi Folks,
 I am currently working on a
 blueprint for Distributed Virtual Router.
 If anyone interested in
 being part of the discussion please let me know.
 I have put together a first
 draft of my blueprint and have posted it on Launchpad for
 review.
 https://blueprints.launchpad.net/neutron/+spec/neutron-ovs-dvr



 Thanks.

 Swaminathan Vasudevan
 Systems Software Engineer
 (TC)


 HP Networking
 Hewlett-Packard
 8000 Foothills Blvd
 M/S 5541
 Roseville, CA - 95747
 tel: 916.785.0937
 fax: 916.785.1815
 email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com







 -Inline Attachment Follows-

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] Distributed Virtual Router Discussion

[Vasudevan, Swaminathan (PNB Roseville)]

Hi Folks,
I am currently working on a blueprint for Distributed Virtual Router.
If anyone interested in being part of the discussion please let me know.
I have put together a first draft of my blueprint and have posted it on 
Launchpad for review.
https://blueprints.launchpad.net/neutron/+spec/neutron-ovs-dvr


Thanks.

Swaminathan Vasudevan
Systems Software Engineer (TC)


HP Networking
Hewlett-Packard
8000 Foothills Blvd
M/S 5541
Roseville, CA - 95747
tel: 916.785.0937
fax: 916.785.1815
email: swaminathan.vasude...@hp.commailto:swaminathan.vasude...@hp.com


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev