[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

Martinx - ジェームズ thiagocmartinsc at gmail.com
Wed May 14 21:54:03 UTC 2014


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> 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>
> 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>
> 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
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140514/5814aa58/attachment.html>


More information about the OpenStack-dev mailing list