Service Separation

asked 2015-10-22 06:01:27 -0500

TimHas gravatar image

Hey y'all,

I've been doing a lot of research on OpenStack lately. I'm trying to figure out what would be the best way to set up an OpenStack environment for my company. One of the first stepts would be to give advice about the hardware to buy. Currently we have 2 nodes. The specs of these nodes are:

  • 2x Intel Xeon CPU E5-2620 0 @2.00 GHz
  • 32 GB RAM
  • 600 GB HDD
  • 4 NIC

For now my company is thinking about setting up a cloud for maybe up to a hundred VMs. Later they might want to scale this up a lot. They want this cloud to be High Available, so I was thinking about a minimum of 6-8 nodes (2 controllers, 2 network nodes, 2 compute nodes + possibly nodes for Cinder/Swift storage).

Would this work for a setup that might have to scale out a lot? I've seen a couple of topologies where people would separate even more services, like separate Database or Load Balancer nodes for High-Availability. Sometimes they'd even set up 2 nodes for things like the Keystone or AMQP services.

So my question is: Would 6-8 nodes work for a HA-OpenStack environment that might have to scale out a lot later? And what is the best way to separate services on the nodes? As in, when do you put API's or the Database on a separate node or when do you put every service on a single controller node?

Thanks a bunch!

edit retag flag offensive close merge delete