Open Stack

Dear all,

Below is our proposal. Look forward to your feedback.

--------------
Description 
This session focuses on how to improve networking performance at large scale deployment.
For example
- having many VMs, thousands to tens of thousands, in a single data center 
- very heavy traffic between VMs of different physical servers 
- large quantities of OpenFlow flow tables causing slow forwarding on OVS and high CPU usage on hypervisor 
- VMs belong to various tenants thus requiring traffic isolation and security and lots of configuration on OVS mainly overlay encapsulation and OpenFlow tables
- neutron server taking too long time to process requests

We are introducing a solution designed for the above scenario in this area.
The main idea is to deploy on the hypervisor a new monitor agent which will periodically check the CPU usage and network load of the NIC and inform SDN controller through plugin/API extension. If the OVS load goes very high, SDN controller can reactively off-load the traffic from OVS to TOR with minimum interruption. It means that initially, the overlay encapsulation might be done on OVS, but some feature rich TORs also provide this functionality which makes TOR capable of taking over whenever necessary. The same strategy will be applied for OpenFlow flow table. By doing this, OVS will have nothing to do other than sending the traffic to TOR. All the time-consuming jobs will be taken over by TOR dynamically. This more advanced strategy does require TOR to be feature-rich so it might cause more TCO.   

We believe this is worth doing for large scale deployment. 
--------------
 

Thank you,
Tina

-----Original Message-----
From: Thierry Carrez [mailto:thierry at openstack.org] 
Sent: Monday, March 31, 2014 8:07 PM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] Session suggestions for the Juno Design Summit now open

Thierry Carrez wrote:
> We have two *new* categories this time around:
> 
> "Cross-project workshops"
> Those will be used to discuss topics which affect all OpenStack 
> projects, and therefore increase convergence and collaboration across 
> program barriers.
> 
> "Other projects"
> Those will let unofficial, OpenStack-related, open source projects to 
> have a design discussion within the Design Summit area. We'll limit 
> this to one session per project to give room to as many projects as possible.
> 
> You have until *April 20* to suggest sessions. Proposed session topics 
> will be reviewed by PTLs afterwards, potentially merged with other 
> suggestions before being scheduled.

In order to facilitate travel organization, we've been asked to confirm which projects are accepted in the "Other projects" track ASAP. We'll therefore have a slightly shorter deadline for that track to give proposals a final answer before mid-April.

It's also useful for us to know which topics are covered in the "Cross-project workshops" before we go and schedule the program-specific categories, so we'll also have a shorter deadline for proposals on cross-project workshops as well.

For both categories, please submit suggestions before *April 10* if you want to be considered fairly. After that date, proposals may still be considered if any slots are left, but most likely all the slots will have been allocated.

Thanks,

--
Thierry Carrez (ttx)

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