We run cells, but when we reached about 250 hv in a cell we needed to add another cell api (went from 2 to 3) to help with the cpu load caused by novaconductor. Nova-conductor was/is constantly crushing the cpu on those servers. ___________________________________________________________________ Kris Lindgren Senior Linux Systems Engineer GoDaddy From: David Medberry <openstack at medberry.net<mailto:openstack at medberry.net>> Date: Tuesday, March 15, 2016 at 8:54 AM To: Gustavo Randich <gustavo.randich at gmail.com<mailto:gustavo.randich at gmail.com>> Cc: "openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>" <openstack-operators at lists.openstack.org<mailto:openstack-operators at lists.openstack.org>> Subject: Re: [Openstack-operators] nova-conductor scale out How many compute nodes do you have (that is triggering your controller node limitations)? We run nova-conductor on multiple control nodes. Each control node runs "N" conductors where N is basically the HyperThreaded CPU count. On Tue, Mar 15, 2016 at 8:44 AM, Gustavo Randich <gustavo.randich at gmail.com<mailto:gustavo.randich at gmail.com>> wrote: Hi, Simple question: can I deploy nova-conductor across several servers? (Icehouse) Because we are reaching a limit in our controller node.... _______________________________________________ OpenStack-operators mailing list OpenStack-operators at lists.openstack.org<mailto:OpenStack-operators at lists.openstack.org> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160315/45e7d59d/attachment.html>