openstack team mailing list archive

[GMI M <gmi68745@xxxxxxxxx>]

Hi Christian,

I think you might be able to use the existing filters in Essex.
For example, you can add the following lines in the nova.conf of the
controller host (or where nova-scheduler runs) and restart nova-scheduler:

isolated_hosts="nova7"
isolated_images="sadsd1e35dfe63"

This will allow you to run the image with ID "sadsd1e35dfe63" only on the
compute host "nova7".
You can also pass a list of compute servers in the isolated_hosts, if you
have the need.

I certainly see the use-case for this feature, for example when you want to
run Windows based instances and you don't want to buy a Windows datacenter
license for each nova-compute host, but only for a few that will run
Windows instances.

I hope this helps you.





On Mon, Oct 15, 2012 at 7:45 PM, Christian Parpart <trapni@xxxxxxxxx> wrote:

> Hi all,
>
> I am looking for a (Essex) Nova scheduler plugin that parses the
> scheduler_hints to get a hostname of the
> hypervisor to spawn the actual VM on, rejecting any other node.
>
> This allows us to explicitely spawn a VM on a certain host (yes, there are
> really usecases where you want that). :-)
>
> I was trying to build my own and searching around since I couldn't believe
> I was the only one, but didn't find one yet.
>
> Does anyone of you maybe have the skills to actually write that simple
> plugin, or even maybe knows where such
> a plugin has already been developed?
>
> Many thanks in advance,
> Christian Parpart.
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
>