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

[Minton, Rich]

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


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

On 02/27/2013 01:55 PM, Minton, Rich wrote:
> Hi all,
> 
>  
> 
> Does anyone know of a check-list type document that can be used to 
> setup a compute node that includes nova-network and cinder?  I have a 
> two node openstack deployment-created basically from scratch without 
> the use of packstack. The primary controller node, which also contains 
> nova-compute, works fine. I can launch instances all day, connect to 
> the network, I can do everything I need to do. My second node is 
> compute, network and cinder-volume. I can see it when I run 
> "nova-manage service list" and all is happy. When I try to force an 
> instance to start up on compute1, it starts up fine but it attaches to 
> the controller node. I have included my nova.conf file just in case 
> anyone sees something I've missed.

When you say "but it attaches to the controller node", do you mean the instance starts on the controller?

How are you trying to force the instance to start on compute1?

--
Russell Bryant