how to tell nova-scheduler to redirect all windows instances to the hyper-v compute node

Asked by arturo lorenzo on 2011-04-07

I am running a small bexar cluster with three computers: the cloud controller that also runs object storage, network and scheduler; one compute node that is providing KVM linux images and one compute node running hyper-v providing windows images.
Most part of the times when I run a windows instance, they are redirected to the compute node running KVM instead of the one running Hyper-v. the windows images are residing inside the Hyper-v compute node.
I have tried the parameter -z on the euca-run-instances unsuccessfully.
how can redirect windows images to the Hyper-v computer node?
Thanks!

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Compute (nova) Edit question
Assignee:
No assignee Edit question
Solved by:
arturo lorenzo
Solved:
2011-04-07
Last query:
2011-04-07
Last reply:
2011-04-07
Vish Ishaya (vishvananda) said : #1

You will need to switch to one of the other schedulers to do this. You can set them up in different zones and use the zone scheduler. Or, as an admin, you can use SimpleScheduler and use -z zone:<host> to send it to a specific host.

--scheduler_driver='nova.scheduler.zone.ZoneScheduler

or

-scheduler_driver='nova.scheduler.zone.SimpleScheduler

On Apr 7, 2011, at 1:53 PM, arturo lorenzo wrote:

> New question #152025 on OpenStack Compute (nova):
> https://answers.launchpad.net/nova/+question/152025
>
> I am running a small bexar cluster with three computers: the cloud controller that also runs object storage, network and scheduler; one compute node that is providing KVM linux images and one compute node running hyper-v providing windows images.
> Most part of the times when I run a windows instance, they are redirected to the compute node running KVM instead of the one running Hyper-v. the windows images are residing inside the Hyper-v compute node.
> I have tried the parameter -z on the euca-run-instances unsuccessfully.
> how can redirect windows images to the Hyper-v computer node?
> Thanks!
>
> --
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Vish Ishaya (vishvananda) said : #2

wow typos there.

Should have said:

> --scheduler_driver=nova.scheduler.zone.ZoneScheduler
>
> or
>
> -scheduler_driver=nova.scheduler.simple.SimpleSchedule

On Apr 7, 2011, at 2:06 PM, Vish Ishaya wrote:

> Question #152025 on OpenStack Compute (nova) changed:
> https://answers.launchpad.net/nova/+question/152025
>
> Status: Open => Answered
>
> Vish Ishaya proposed the following answer:
> You will need to switch to one of the other schedulers to do this. You
> can set them up in different zones and use the zone scheduler. Or, as
> an admin, you can use SimpleScheduler and use -z zone:<host> to send it
> to a specific host.
>
> --scheduler_driver='nova.scheduler.zone.ZoneScheduler
>
> or
>
> -scheduler_driver='nova.scheduler.zone.SimpleScheduler
>
>
> On Apr 7, 2011, at 1:53 PM, arturo lorenzo wrote:
>
>> New question #152025 on OpenStack Compute (nova):
>> https://answers.launchpad.net/nova/+question/152025
>>
>> I am running a small bexar cluster with three computers: the cloud controller that also runs object storage, network and scheduler; one compute node that is providing KVM linux images and one compute node running hyper-v providing windows images.
>> Most part of the times when I run a windows instance, they are redirected to the compute node running KVM instead of the one running Hyper-v. the windows images are residing inside the Hyper-v compute node.
>> I have tried the parameter -z on the euca-run-instances unsuccessfully.
>> how can redirect windows images to the Hyper-v computer node?
>> Thanks!
>>
>> --
>> You received this question notification because you are a member of Nova
>> Core, which is an answer contact for OpenStack Compute (nova).
>
> You received this question notification because you are a member of Nova
> Core, which is an answer contact for OpenStack Compute (nova).

Vish,
thanks again! that solved the problem!