Re: [openstack-dev] [Neutron][Kuryr] - Bringing Dockers networking to Neutron

2015-07-23 Thread Yapeng Wu 
Gal, I vote for Monday 1600UTC.

Thanks,
Yapeng


From: Mohammad Banikazemi [mailto:m...@us.ibm.com]
Sent: Thursday, July 23, 2015 1:30 AM
To: OpenStack Development Mailing List (not for usage questions)
Cc: Eran Gampel; Irena Berezovsky; Antoni Segura Puimedon
Subject: Re: [openstack-dev] [Neutron][Kuryr] - Bringing Dockers networking to 
Neutron


Gal, This time conflicts with the Neutron ML2 weekly meeting time [1]. I 
realize there are several networking related weekly meetings, but I would like 
to see if we can find a different time. I suggest the same time, that is 1600 
UTC but either on Mondays or Thursdays.

Please note there is the Ironic/Neutron Integration meeting at the same time on 
Mondays but that conflict may be a smaller conflict. Looking at the meetings 
listed at [2] I do not see any other conflict.

Best,

Mohammad

[1] https://wiki.openstack.org/wiki/Meetings/ML2
[2] http://eavesdrop.openstack.org


[Inactive hide details for Gal Sagie ---07/22/2015 12:31:46 PM---Hello 
Everyone, Project Kuryr is now officially part of Neutron]Gal Sagie 
---07/22/2015 12:31:46 PM---Hello Everyone, Project Kuryr is now officially 
part of Neutron's big tent.

From: Gal Sagie 
To: "OpenStack Development Mailing List (not for usage questions)" 
, Eran Gampel 
, Antoni Segura Puimedon , 
Irena Berezovsky 
Date: 07/22/2015 12:31 PM
Subject: [openstack-dev] [Neutron][Kuryr] - Bringing Dockers networking to 
Neutron






Hello Everyone,

Project Kuryr is now officially part of Neutron's big tent.
Kuryr is aimed to be used as a generic docker remote driver that connects 
docker to Neutron API's
and provide containerised images for the common Neutron plugins.
We also plan on providing common additional networking services API's from 
other sub projects
in the Neutron big tent.

We hope to get everyone on board with this project and leverage this joint 
effort for the many different solutions out there (instead of everyone 
re-inventing the wheel for each different project).

We want to start doing a weekly IRC meeting to coordinate the different 
requierments and
tasks, so anyone that is interested to participate please share your time 
preference
and we will try to find the best time for the majority.

Remember we have people in Europe, Tokyo and US, so we won't be able to find 
time that fits
everyone.

The currently proposed time is  Wedensday at 16:00 UTC

Please reply with your suggested time/day,
Hope to see you all, we have an interesting and important project ahead of us

Thanks
Gal.__
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] [Policy][Group-based-policy] SFC USe Case

2015-03-04 Thread Yapeng Wu 
Venkat,

Service Function chaining ("redirect" action) is not supported right now.

Yapeng


From: groupbasedpolicy-dev-boun...@lists.opendaylight.org 
[mailto:groupbasedpolicy-dev-boun...@lists.opendaylight.org] On Behalf Of 
Venkatrangan G - ERS, HCL Tech
Sent: Wednesday, March 04, 2015 4:38 AM
To: openstack-dev@lists.openstack.org
Cc: groupbasedpolicy-...@lists.opendaylight.org
Subject: [groupbasedpolicy-dev] [Policy][Group-based-policy] SFC USe Case

Hi,
 I am trying out the procedure listed in this page 
https://wiki.openstack.org/wiki/GroupBasedPolicy/InstallODLIntegrationDevstack. 
I was looking for  an use case with Service Function chaining i.e. to use 
redirect with gbp command.
Can you please point me to some link that can help me out to try the same with 
GBP?

Regards,
Venkat G.



::DISCLAIMER::

The contents of this e-mail and any attachment(s) are confidential and intended 
for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information 
could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in 
transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on 
the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the 
author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, 
dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written 
consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please 
delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and 
other defects.

__
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] [Policy][Group-based-policy] ODL Policy Driver Specs

2015-01-13 Thread Yapeng Wu 
Hi, Sachi,

Please see my inlined replies.

Also, please refer to this link when you try to integrate OpenStack GBP and ODL 
GBP:
https://wiki.openstack.org/wiki/GroupBasedPolicy/InstallODLIntegrationDevstack


Yapeng

From: Sachi Gupta [mailto:sachi.gu...@tcs.com]
Sent: Tuesday, January 13, 2015 4:02 AM
To: OpenStack Development Mailing List (not for usage questions); 
groupbasedpolicy-...@lists.opendaylight.org; Yapeng Wu
Cc: bu...@noironetworks.com
Subject: Re: [openstack-dev] [Policy][Group-based-policy] ODL Policy Driver 
Specs

Hi,

While working on the integration of Openstack With ODL GBP, I have the below 
queries:

  1.  Endpoint-group Create: When I create a new policy-target-group from 
Openstack say "gbp target-policy-group-create group1", it internally creates a 
l2.policy which includes the creation of the network and subnet. Meaning 
creation of EPG will create Network and subnet implicitly in Openstack and also 
the corresponding EPG, subnet, l3-context, l2-flood-domain, l2-bridge-domain 
will be created in the ODL GBP. So during the above EPG creation, neutron 
network and subnet call will come to the neutron northbound of ODL or only to 
ODL GBP??
[Yapeng] First, when creating policy-target-group, you need to give 
“provided-policy-rule-sets” or “consumed-policy-rule-sets” parameter. Currently 
we don’t support policy-target-group update. Second, neutron network and subnet 
call won’t go to ODL.

  1.

  1.  In ODL, there is no Endpoint create API, instead there is an API to 
register the endpoints. So what is the sync between the OS and ODL for Endpoint 
create and register.?
[Yapeng] The current working scheme is as follow: ODL GBP has new APIs for 
openstack-endpoint register and unregister supports.[1][2] When Openstack GBP 
creates policy-target, a neutron port will be created by implicit driver, 
openstack-endpoint register API will be invoked and the OVS tap-port-id will be 
passed as parameter to ODL GBP. Later when VM is booted, the OVS tap-port-id 
will be populated on openvswitch, this will trigger ODL to update ovs flow 
tables.

[1] https://git.opendaylight.org/gerrit/#/c/13554/
[2] https://git.opendaylight.org/gerrit/#/c/13896/


Thanks & Regards
Sachi Gupta



From:    Yapeng Wu 
To:"OpenStack Development Mailing List (not for usage questions)" 

Date:01/12/2015 09:01 PM
Subject:Re: [openstack-dev] [Policy][Group-based-policy] ODL
PolicyDriverSpecs




Hello, Sachi,

They both works. “End point group” has been renamed to “policy target group”. 
It is recommended to use “gbp policy-target-group-create”.

Yapeng


From: Sachi Gupta [mailto:sachi.gu...@tcs.com]
Sent: Monday, January 12, 2015 7:03 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Policy][Group-based-policy] ODL Policy Driver 
Specs

Hi,

Can anyone explain the difference between gbp group-create and gbp 
policy-target-group-create??

I think both these are working same.

Thanks & Regards
Sachi Gupta




From:Sumit Naiksatam 
To:"OpenStack Development Mailing List (not for usage questions)" 

Date:11/26/2014 01:35 PM
Subject:Re: [openstack-dev] [Policy][Group-based-policy] ODL Policy 
DriverSpecs





Hi, This GBP spec is currently being worked on:
https://review.openstack.org/#/c/134285/

It will be helpful if you can add "[Policy][Group-based-policy]" in
the subject of your emails, so that the email gets characterized
correctly.

Thanks,
~Sumit.

On Tue, Nov 25, 2014 at 4:27 AM, Sachi Gupta  wrote:
> Hey All,
>
> I need to understand the interaction between the Openstack GBP and the
> Opendaylight GBP project which will be done by ODL Policy driver.
>
> Can someone provide me with specs of ODL Policy driver for making my
> understanding on call flow.
>
>
> Thanks & Regards
> Sachi Gupta
>
> =-=-=
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
> ___
> OpenStack-dev mailing list
> 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.o

Re: [openstack-dev] [Policy][Group-based-policy] ODL Policy Driver Specs

2015-01-12 Thread Yapeng Wu 
Hello, Sachi,

They both works. "End point group" has been renamed to "policy target group". 
It is recommended to use "gbp policy-target-group-create".

Yapeng


From: Sachi Gupta [mailto:sachi.gu...@tcs.com]
Sent: Monday, January 12, 2015 7:03 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Policy][Group-based-policy] ODL Policy Driver 
Specs

Hi,

Can anyone explain the difference between gbp group-create and gbp 
policy-target-group-create??

I think both these are working same.

Thanks & Regards
Sachi Gupta




From:Sumit Naiksatam 
To:"OpenStack Development Mailing List (not for usage questions)" 

Date:11/26/2014 01:35 PM
Subject:Re: [openstack-dev] [Policy][Group-based-policy] ODL Policy 
DriverSpecs




Hi, This GBP spec is currently being worked on:
https://review.openstack.org/#/c/134285/

It will be helpful if you can add "[Policy][Group-based-policy]" in
the subject of your emails, so that the email gets characterized
correctly.

Thanks,
~Sumit.

On Tue, Nov 25, 2014 at 4:27 AM, Sachi Gupta  wrote:
> Hey All,
>
> I need to understand the interaction between the Openstack GBP and the
> Opendaylight GBP project which will be done by ODL Policy driver.
>
> Can someone provide me with specs of ODL Policy driver for making my
> understanding on call flow.
>
>
> Thanks & Regards
> Sachi Gupta
>
> =-=-=
> Notice: The information contained in this e-mail
> message and/or attachments to it may contain
> confidential or privileged information. If you are
> not the intended recipient, any dissemination, use,
> review, distribution, printing or copying of the
> information contained in this e-mail message
> and/or attachments to it are strictly prohibited. If
> you have received this communication in error,
> please notify us by reply e-mail or telephone and
> immediately and permanently delete the message
> and any attachments. Thank you
>
>
> ___
> OpenStack-dev mailing list
> 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 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] Group Based Policy and the way forward

2014-08-06 Thread Yapeng Wu 
Hi, Salvatore,

Thanks listing out the options.

Can you elaborate more on your 2nd option? Do you mean merge the patches and 
mark the API as ‘experimental’?

Yapeng


From: Salvatore Orlando [mailto:sorla...@nicira.com]
Sent: Wednesday, August 06, 2014 1:44 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [Neutron] Group Based Policy and the way forward

As Ronak said, this thread is starting to move in a lot of different 
directions, ranging from correctness of the blueprint approval process to 
nova/neutron integration, which are rather off topic.

In particular it seems things are being skewed towards a discussion around nova 
parity, whereas actually some people have just chimed in with their honest 
opinion that with all the stuff still needed to finally be able to make neutron 
"THE" openstack networking solution, the effort towards adding a new tenant 
facing API appears to have a lesser priority.

I just want to reassure everybody that the majority of the core team and a 
large part of the community have actually made this their first priority. For 
what is worth, some of them have even delayed plugin/driver specific 
development to this aim.

So I would invite to go back to the original subject of the discussion, that is 
to say decide as a community what would the best way forward for this effort.
I see so far the following options:
- merge the outstanding patches, assuming there are no further technical 
concerns, and include GBP in Juno.
- consider GBP an 'experimental' V3 tenant API (this was mentioned somewhere in 
this thread) and treat it accordingly
- delay to the next release
- move the development of the service plugin to stackforge as suggested to this 
thread.

More options are obviously welcome!

Regards,
Salvatore

On 6 August 2014 19:40, Ivar Lazzaro 
mailto:ivarlazz...@gmail.com>> wrote:
Which kind of uncertainty are you referring to?

Given that the blueprint was approved long ago, and the code has been ready and 
under review following those specs... I think GBP is probably the patch with 
the least effort to be merged right now.

Ivar.

On Wed, Aug 6, 2014 at 7:34 PM, Joe Gordon 
mailto:joe.gord...@gmail.com>> wrote:

On Aug 6, 2014 10:21 AM, "Ronak Shah" 
mailto:ronak.malav.s...@gmail.com>> wrote:
>
> We have diverged our attention towards nova-network-> neutron parity on this 
> thread unnecessarily.
>
> Can we discuss and collectively decide on what is the way forward for GBP in 
> Juno release?
>
> Efforts have been made by the subteam starting from throwing PoC at last 
> summit to spec approval to code review.
>
> There are usefulness to this feature and I think everyone is on the same page 
> there.
>
> Let us not discourage the effort by bringing in existing neutron issue in 
> play.

> Yes, we has a neutorn community needs to fix that with highest priority.
> But this is orthogonal effort.

The efforts may be orthogonal, but the review team and bandwidth of said team 
is one and the same. Making nova-network the highest priority means pushing 
other blueprints back as needed.  And since there is still so much uncertainty 
around GPB this late in the cycle, IMHO it's a good candidate for getting 
deferred.
> If endpoint is not a likeable preferred name than lets propose more 
> meaningful alternative.
> Let us try to find a middle ground on how this feature can be made generally 
> available.
>
> Thanks,
> Ronak
>
> ___
> OpenStack-dev mailing list
> 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 mailing list
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

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

2013-10-23 Thread Yapeng Wu 
Hello, Swami,
I am interested in this topic. Please include me in the discussion.
Thanks,
Yapeng

From: Vasudevan, Swaminathan (PNB Roseville) 
[mailto:swaminathan.vasude...@hp.com]
Sent: Tuesday, October 22, 2013 2:50 PM
To: cloudbengo; Artem Dmytrenko; yong sheng gong (gong...@unitedstack.com); 
OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Neutron] Distributed Virtual Router Discussion

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 Dmytrenko
Date: 2013-10-22 02:51
To: yong sheng gong 
\(gong...@unitedstack.com\); 
cloudbe...@gmail.com; OpenStack Development 
Mailing List
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) 
mailto:swaminathan.vasude...@hp.com>> wrote:

 Subject: [openstack-dev] Distributed Virtual Router Discussion
 To: "yong sheng gong 
(gong...@unitedstack.com)" 
mailto:gong...@unitedstack.com>>, 
"cloudbe...@gmail.com" 
mailto:cloudbe...@gmail.com>>, "OpenStack Development 
Mailing List 
(openstack-dev@lists.openstack.org)" 
mailto: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.com







 -Inline Attachment Follows-

 ___
 OpenStack-dev mailing list
 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

Re: [openstack-dev] [Nova] can openstack compute manage both physical and machine machines?

2013-08-21 Thread Yapeng Wu 
Qing, you can take a look at this link: 
https://wiki.openstack.org/wiki/Baremetal

Yapeng

From: Qing He [mailto:qing...@radisys.com]
Sent: Wednesday, August 21, 2013 2:23 PM
To: OpenStack Development Mailing List
Subject: Re: [openstack-dev] [Nova] can openstack compute manage both physical 
and machine machines?

All,
>From the documents, It seems to me Nova can only manage virtual machines, but 
>not mixed with physical machines. Am I wrong?

Thanks,

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