This is exactly what I'm looking for, but don't know how! Would you please describe a bit more? Thanks ________________________________ From: Narayan Desai <narayan.desai at gmail.com> To: Ahmad Ahmadi <ahmadidamha at yahoo.com> Cc: "openstack-operators at lists.openstack.org" <openstack-operators at lists.openstack.org> Sent: Tuesday, July 2, 2013 3:30 PM Subject: Re: [Openstack-operators] Instance Scheduling on Hosts We accomplished with a scheduler filter that only routes big mem requests to nodes with large memory footprint and doesn't consider these for smaller instance types. -nld On Tue, Jul 2, 2013 at 3:55 PM, Ahmad Ahmadi <ahmadidamha at yahoo.com> wrote: I have two groups of hosts as compute nodes: > >BigGroup: a few machines with very big RAM >SmallGroup: a lot of machines with smaller RAM each. > > >My goal is to assigne bigger instances (from bigger flavors) to BigGroup and smaller instances to SmallGroup. >I tried the "AggregateInstanceExtraSpecsFilter" filtering with assigning different keys to instances and making aggregated hosts (http://docs.openstack.org/folsom/openstack-compute/admin/content/host-aggregates.html), but didn't work and all the instance boots will end up to error. >Any idea? > > >More over does anyone know how can I assign higher cost to bigger nodes for weighting? > > >Thanks, > >_______________________________________________ >OpenStack-operators mailing list >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/20130702/8702591b/attachment.html>