[openstack-dev] [Neutron] B203 table 6 for Neutron//Re: SDN NBI Core APIs consumed by OpenStack: Wednesday May 14th at 10:30-11am in the developer lounge at 3rd floor

Tina TSOU Tina.Tsou.Zouting at huawei.com
Thu May 15 20:28:31 UTC 2014


Dear Manish,

Salvatore asked about yesterday's SDN NBI core APIs - L3 VPN we discussed yesterday afternoon, AT&T's use case.

The use case you described below is another separate thread we discuss this morning.


Thank you,
Tina

On May 15, 2014, at 3:53 PM, "Manish Godara" <manishg at yahoo-inc.com<mailto:manishg at yahoo-inc.com>> wrote:

Hi Salvatore,

The use-case was this:
There are lot of tunnels and they are straining HV resources (cpu). The operator is upgrading hardware (TOR) and would like to offload some of this by moving the tunnel endpoints to the TOR (from HV) based on either the policy for the client (some pay less and some pay more!).

The outcome was that all of this has nothing to do with neutron as such because once the ports are wired it's up to the drivers / controllers to do some of the things that were requested (neutron is out of picture).  Their expectation was that neutron should be monitoring and based on resource usage should work with controller to migrated the tunnel endpoints to TOR (I.e. Encapsulation should happen at the TOR and not at the HV).

Others can correct if I missed something.

Thanks,
manish



From: Salvatore Orlando <sorlando at nicira.com<mailto:sorlando at nicira.com>>
Reply-To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Date: Thursday, May 15, 2014 8:43 AM
To: "OpenStack Development Mailing List (not for usage questions)" <openstack-dev at lists.openstack.org<mailto:openstack-dev at lists.openstack.org>>
Subject: Re: [openstack-dev] B203 table 6 for Neutron//Re: SDN NBI Core APIs consumed by OpenStack: Wednesday May 14th at 10:30-11am in the developer lounge at 3rd floor

Hi,

frankly this picture is not worth a lot to people which did not attend this meetings.
At least the dumb ones like me.

I've tried to bring myself up to speed on NBI APIs; however  It is not clear where the mnentioned trust relationship module resides, and how it interacts with the other components in the picture.
Also, the role of MPLS/WAN cloud is also a bit obscure at the moment.

It would be probably not such a bad idea to create a wiki page describing architecture/design and action items.

However, I seem to understand that an Openstack based cloud is actually a energised nebula which is attracting a tie fighter whose pilot is crying for help shouting NBI APIs!
Sorry about the irony, I did not mean to be rude.

Regards,
Salvatore


On 15 May 2014 17:19, Tina TSOU <Tina.Tsou.Zouting at huawei.com<mailto:Tina.Tsou.Zouting at huawei.com>> wrote:
Dear all,

A picture is worth 1000 words.

Here is what we had in our meeting, AT&T scanario regarding trust relationship modle between cloud operator and network operator, and core APIs between OpenStack and SDN Controller for L3 VPN.

<image001.jpg>


Thank you,
Tina

From: Martinx - ジェームズ [mailto:thiagocmartinsc at gmail.com<mailto:thiagocmartinsc at gmail.com>]
Sent: Wednesday, May 14, 2014 5:54 PM

To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] B203 table 6 for Neutron//Re: SDN NBI Core APIs consumed by OpenStack: Wednesday May 14th at 10:30-11am in the developer lounge at 3rd floor

Hello!

This is very an interesting topic!

I would like to talk about one idea I had, which is related to: "1.9. API for VPN".

I think it would be awesome, for example, when dealing with IPv6-Only "Projects (Tenants) Networks", the VPNs should use `Opportunistic Encryption`, this way, the VPNs will be established "by default" without any user interaction. Then, IPSec VPN for `IPv6 <-> IPv6` subnets will be always there, safely interconnecting the subnets, everywhere, even across different "Regions" or across different "Projects" (old "Tenants" terminology).

I already started a topic about this but, I'm a bit busy these days... I'll reply there and I'm drawing a blueprint for it...

Best!
Thiago

On 14 May 2014 12:16, Tina TSOU <Tina.Tsou.Zouting at huawei.com<mailto:Tina.Tsou.Zouting at huawei.com>> wrote:
Dear all,

Below is the main conclusion from this meeting.

We will work on the following SDN NBI Core APIs at the priority per Neutron's interest.
2, 7, 10, 9, 11.

1.2 APIs for connection between OpenStack Neutron and controller

OpenStack is widely used and deployed in cloud scenarios.OpenStack-based data center is becoming mainstream.

There should be APIs for connection between SDN controller and OpenStack Neutron.



1.7 APIs for Virtual-Tenant-Network (VTN)

VTN allows users and developers to design and deploy virtual networks without the need to know the physical network. This is very useful in data center.

There should be APIs for virtual tenant network.



1.10 APIs for QoS

QoS is usually for end user application. For example, the UC-SDN-Use-Case needs the network to guarantee its flow QoS to improve the user’s QoE.

There should be APIs for QoS.



1.9 APIs for VPN

VPN is also widely use in enterprise network, interconnectionbetween data centers and mobile environments.

The management and operation of VPN are necessary. There should be APIs for VPN.

The VPN may include the following type

L2 VPN

L3 VPN



1.11 APIs for network stats/state

The network stats/state is needed by application so that the application can react with the corresponding policy.

There should be APIs for network stats/state.


Thank you,
Tina

On May 14, 2014, at 10:00 AM, "Tina TSOU" <Tina.Tsou.Zouting at huawei.com<mailto:Tina.Tsou.Zouting at huawei.com>> wrote:
Dear all,

Place is changed to B203 table 6 for Networking (Neutron), Design Summit Pod area.


Thank you,
Tina

On May 13, 2014, at 10:00 PM, "Tina TSOU" <Tina.Tsou.Zouting at huawei.com<mailto:Tina.Tsou.Zouting at huawei.com>> wrote:
Dear Stackers,

We are setting up a meeting to SDN NBI Core APIs consumed by OpenStack. Attached is the material for your reading pleasure.

The meeting is planned for:
                Wednesday May 14th at 10:30-11am in the developer lounge at 3rd floor .
Look forward to meeting many of you then.


Thank you,
Tina

<NBI Core APIs.docx>

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org<mailto:OpenStack-dev at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


<image001.jpg>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140515/ed641dea/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 69002 bytes
Desc: image001.jpg
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140515/ed641dea/attachment.jpg>


More information about the OpenStack-dev mailing list