[Openstack-operators] restricting which flavors or instances a compute node will run?
Narayan Desai
narayan.desai at gmail.com
Tue Jun 11 19:14:01 UTC 2013
We implemented this with a custom filter that only chooses the nodes for
the proper instance types.
-nld
On Tue, Jun 11, 2013 at 12:33 PM, Jonathan Proulx <jon at jonproulx.com> wrote:
>
> I remember having seen something somewhere in the the docs once about
> restricting what instances or possibly what flavors a compute node will
> run, but that was a long time ago and now that I want to do it I can't seem
> to find it, and pointers?
>
> what I'm going for:
>
> I have (or will have) a set of systems that I only want to run a VMs. I
> don't want anything but those VMs on the nodes and I don't want the VMs on
> any other nodes. It's not for GPUs but is similar to the GPU case the
> instance need the specific resource and I don't want to waste the limite
> resource on more generic images that don't require it.
>
> I can implement this as either a set of images or flavors. Flavors seem
> more likely since using host aggregates and instance types it seems pretty
> clear how to make the flavor(s) run on a given set of nodes, but it's not
> so clear home (if?) I can prevent other flavors from running on them.
>
> Currently I'm running Folsom but this need will be implemented along with
> or after my Grizzly upgrade.
>
> Thanks,
> -Jon
>
> _______________________________________________
> 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/20130611/f27c9152/attachment.html>
More information about the OpenStack-operators
mailing list