[rhos-list] EXTERNAL: Re: Setting up Compute Nodes.

[Minton, Rich]

Thank you very much for the feedback. I didn't know of another way to test the multiple compute node function except to create a bunch of instances and watch the activity on the other compute nodes.

-----Original Message-----
From: Russell Bryant [mailto:rbryant at redhat.com] 
Sent: Wednesday, February 27, 2013 4:33 PM
To: Minton, Rich
Cc: rhos-list at redhat.com; Andrus, Gregory
Subject: Re: EXTERNAL: Re: [rhos-list] Setting up Compute Nodes.

On 02/27/2013 04:20 PM, Minton, Rich wrote:
> Yes, I try to force it to run on compute1 but it runs on controller.
> 
> From the command line I run...
> 
> nova boot --image <image-id> --flavor 3 --key_name test 
> --availability-zone=nova:compute1 server-name

Thanks for the command.

This method of forcing a host is only supported if you're an admin.  It would be ignored for a regular user.  Since the instance did actually start, I assume it was a regular user.  In that case, the 'compute1'
part would be ignored and just the availability zone of 'nova' would be honored.  Since both nodes are in the 'nova' zone, it happened to pick your controller.

There aren't any ways to force an instance to a specific host that don't require some level of admin interaction that I know of.  This really comes down to a core philosophy of this type of system, which is that the user of the cloud shouldn't have to know or care which specific node an instance runs on.  This is not to be confused with nodes having capabilities and requesting instances that have requirements for certain capabilities.  We have various features in that area.

--
Russell Bryant