Hi, Neil, >From theoretic, Neutron is like a "broadcast" domain, for example, enforcement >of DVR and security group has to touch each regarding host where there is VM >of this project resides. Even using SDN controller, the "touch" to regarding >host is inevitable. If there are plenty of physical hosts, for example, 10k, >inside one Neutron, it's very hard to overcome the "broadcast storm" issue >under concurrent operation, that's the bottleneck for scalability of Neutron.
We need layered architecture in Neutron to solve the "broadcast domain" bottleneck of scalability. The test report from OpenStack cascading shows that through layered architecture "Neutron cascading", Neutron can supports up to million level ports and 100k level physical hosts. You can find the report here: http://www.slideshare.net/JoeHuang7/test-report-for-open-stack-cascading-solution-to-support-1-million-v-ms-in-100-data-centers "Neutron cascading" also brings extra benefit: One cascading Neutron can have many cascaded Neutrons, and different cascaded Neutron can leverage different SDN controller, maybe one is ODL, the other one is OpenContrail. ----------------Cascading Neutron------------------- / \ --cascaded Neutron-- --cascaded Neutron----- | | ---------ODL------ ----OpenContrail-------- And furthermore, if using Neutron cascading in multiple data centers, the DCI controller (Data center inter-connection controller) can also be used under cascading Neutron, to provide NaaS ( network as a service ) across data centers. ---------------------------Cascading Neutron-------------------------- / | \ --cascaded Neutron-- -DCI controller- --cascaded Neutron----- | | | ---------ODL------ | ----OpenContrail-------- | --(Data center 1)-- --(DCI networking)-- --(Data center 2)-- Is it possible for us to discuss this in OpenStack Vancouver summit? Best Regards Chaoyi Huang ( Joe Huang ) -----Original Message----- From: Neil Jerram [mailto:neil.jer...@metaswitch.com] Sent: Thursday, April 09, 2015 12:27 AM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [neutron] Neutron scaling datapoints? My team is working on experiments looking at how far the Neutron server will scale, with increasing numbers of compute hosts and VMs. Does anyone have any datapoints on this that they can share? Or any clever hints? I'm already aware of the following ones: https://javacruft.wordpress.com/2014/06/18/168k-instances/ Icehouse 118 compute hosts 80 Neutron server processes (10 per core on each of 8 cores, on the controller node) 27,000 VMs - but only after disabling all security/iptables http://www.opencontrail.org/openstack-neutron-at-scale/ 1000 hosts 5000 VMs 3 Neutron servers (via a load balancer) But doesn't describe if any specific configuration is needed for this. (Other than using OpenContrail! :-)) Many thanks! Neil __________________________________________________________________________ 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
