We have the same basic problems. We have 4 different types of systems integrated into our system. They all have different ratios of cpu to memory, and we have some specialized hardware on one class of nodes.
We ended up setting up a series of chassis specific instance definitions. We then use the filter scheduler to only accept hosts with a particular configuration for the associated instance types. (for example, our large memory nodes will only run instances with the mem. prefix, and won't run generic instance types or ones for other hardware types -- it seemed silly to waste large memory resources on 1GB ram vms) It is pretty simple to write filter rules for the filter scheduler to set this up. You just need instance types and a hostname convention that you can use to matchmake. While this seems a little hacky, it works well. -nld On Tue, Jan 22, 2013 at 6:47 AM, Danilo Perogil <dpero...@dualtec.com.br> wrote: > Hello everybody, > > Do you know of a way to set to work with OpenStack Computes Nodes containing > different hardware? > In my case, I did tests with different hardware, example 1 compute node with > 24 processors and 128GB memory VS 1 compute node with 8 processors and 16GB > of memory. In the test I saw he only makes division number of instances > between total compute nodes, but it does a calculation for use by node. > > It is possible to make it work with some kind of calculation to not overload > a node? > > Sorry my english google translate hahahah > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
