Re: [openstack-dev] Session suggestions for the Juno Design Summit now open
Dear Thierry, Thanks for your suggestion. It is submitted as below. http://summit.openstack.org/cfp/create Topic Title (Click to view/edit) Proposer Status Neutron Scaling Network Performance for Large Clouds<http://summit.openstack.org/cfp/details/270> Tina Tsou U Unreviewed Thank you, Tina -Original Message- From: Thierry Carrez [mailto:thie...@openstack.org] Sent: Wednesday, April 09, 2014 6:36 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] Session suggestions for the Juno Design Summit now open Tina TSOU wrote: > 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. > -- You should file it at summit.openstack.org so that it can be considered for inclusion in the schedule. Regards, -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org<mailto: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] Session suggestions for the Juno Design Summit now open
Tina TSOU wrote: > 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. > -- You should file it at summit.openstack.org so that it can be considered for inclusion in the schedule. Regards, -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Session suggestions for the Juno Design Summit now open
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:thie...@openstack.org] Sent: Monday, March 31, 2014 8:07 PM To: openstack-dev@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@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] 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@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Session suggestions for the Juno Design Summit now open
Sergey Lukjanov wrote: > thanks for opening sessions suggestions for Design Summit. Could you, > please, rename Savanna topic to "Sahara (ex. Savanna)"? Done! -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] Session suggestions for the Juno Design Summit now open
Hi Thierry, thanks for opening sessions suggestions for Design Summit. Could you, please, rename Savanna topic to "Sahara (ex. Savanna)"? On Fri, Mar 7, 2014 at 1:17 PM, Thierry Carrez wrote: > Hi everyone, > > TL;DR: > The session suggestion website for the Juno Design Summit (which will > happen at the OpenStack Summit in Atlanta) is now open at: > http://summit.openstack.org/ > > Long version: > > The "Juno Design Summit" is a specific event part of the overall > "OpenStack Summit" in Atlanta. It is different from classic tracks in > a number of ways. > > * It starts on Tuesday morning and ends on Friday evening. > > * There are *no formal presentations or speakers*. The sessions at the > design summit are open discussions between contributors on a specific > development topic for the upcoming development cycle, generally > moderated by the PTL or the person who proposed the session. While it is > possible to prepare a few slides to introduce the current status and > kick-off the discussion, these should never be formal > speaker-to-audience presentations. If that's what you're after, the > presentations in the other tracks of the OpenStack Summit are for you. > > * There is no community voting on the content. The Juno Design Summit is > split into multiple topics (one for each official OpenStack Program), > and the elected program PTL will be ultimately responsible for selecting > the content he deems important for the upcoming cycle. If you want to be > PTL in place of the PTL, we'll be holding elections for that in the > coming weeks :) > > With all this in mind, please feel free to suggest topics of discussion > for this event. The website to do this is open at: > > http://summit.openstack.org/ > > You'll need to go through Launchpad SSO to log on that site (same auth > we use for review.openstack.org and all our core development > infrastructure). If you're lost, try the Help link at the bottom of the > page. If all else fails, send me an email. > > Please take extra care when selecting the topic your suggestion belongs > in. You can see the complete list of topics at: > > https://wiki.openstack.org/wiki/Summit/Juno > > 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. > > You can also comment on proposed sessions to suggest scheduling > constraints or sessions it could be merged with. > > More information about the Juno Design Summit can be found at: > https://wiki.openstack.org/wiki/Summit > > Cheers, > > -- > Thierry Carrez (ttx) > > ___ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Sincerely yours, Sergey Lukjanov Savanna Technical Lead Mirantis Inc. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] Session suggestions for the Juno Design Summit now open
Hi everyone, TL;DR: The session suggestion website for the Juno Design Summit (which will happen at the OpenStack Summit in Atlanta) is now open at: http://summit.openstack.org/ Long version: The "Juno Design Summit" is a specific event part of the overall "OpenStack Summit" in Atlanta. It is different from classic tracks in a number of ways. * It starts on Tuesday morning and ends on Friday evening. * There are *no formal presentations or speakers*. The sessions at the design summit are open discussions between contributors on a specific development topic for the upcoming development cycle, generally moderated by the PTL or the person who proposed the session. While it is possible to prepare a few slides to introduce the current status and kick-off the discussion, these should never be formal speaker-to-audience presentations. If that's what you're after, the presentations in the other tracks of the OpenStack Summit are for you. * There is no community voting on the content. The Juno Design Summit is split into multiple topics (one for each official OpenStack Program), and the elected program PTL will be ultimately responsible for selecting the content he deems important for the upcoming cycle. If you want to be PTL in place of the PTL, we'll be holding elections for that in the coming weeks :) With all this in mind, please feel free to suggest topics of discussion for this event. The website to do this is open at: http://summit.openstack.org/ You'll need to go through Launchpad SSO to log on that site (same auth we use for review.openstack.org and all our core development infrastructure). If you're lost, try the Help link at the bottom of the page. If all else fails, send me an email. Please take extra care when selecting the topic your suggestion belongs in. You can see the complete list of topics at: https://wiki.openstack.org/wiki/Summit/Juno 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. You can also comment on proposed sessions to suggest scheduling constraints or sessions it could be merged with. More information about the Juno Design Summit can be found at: https://wiki.openstack.org/wiki/Summit Cheers, -- Thierry Carrez (ttx) ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
