[Openstack] a problem with nova scheduler
skywalker.nick at gmail.com
Thu Oct 17 02:36:00 UTC 2013
Thanks for the hint. I'll try it later.
On Thu, Oct 17, 2013 at 9:29 AM, Mike Wilson <geekinutah at gmail.com> wrote:
> There is a scheduler hint called 'force_hosts' for this sort of thing. I
> believe the command line looks like this:
> Nova boot <server_name> --hints force_hosts=host1 <everything else>
> Does that work for you?
> This does not bypass the scheduler, but it is built into the scheduler to
> allow you to explicitly place new instances on a subset of hardware.
> -Mike Wilson
> Sent from my iPhone
> On Oct 16, 2013, at 6:35 PM, Li Ma <skywalker.nick at gmail.com> wrote:
> Hi all,
> I encountered a problem with nova-scheduler. Given that I have 20
> different compute nodes, I need to run several instances on a certain
> compute node for testing or verification. I go through all the scheduling
> algorithms and find out I can achieve this by availability zone.
> But this is a little bit weird to create more than 20 availability zone
> with only one compute node temporarily. Is there any other solutions for
> In my opinion, there should be a certain parameter with nova CLI to
> specify which compute node this instance should be placed directly without
> any scheduling. Using this method, I can bypass the scheduling options
> defined in the nova.conf and do what we want to meet the specific
> Li Ma (Nick)
> Email: skywalker.nick at gmail.com
> Mailing list:
> Post to : openstack at lists.openstack.org
> Unsubscribe :
Li Ma (Nick)
Architect of Stackinsider
Email: skywalker.nick at gmail.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Openstack