You can just stop nova-compute on the essex-1 node.
2012/7/12 Trinath Somanchi trinath.soman...@gmail.com
Hi-
I have installed Openstack on a Machine ESSEX-1 which is the controller
and Nova-Compute on another machine ESSEX-2 which acts as an agent/node.
When ever I start an new instance,
$ sudo nova-manage service disable --host=ESSEX-1 --service nova-compute
It's also good to read the documentation before asking questions.
http://docs.openstack.org/essex/openstack-compute/admin/content/managing-the-cloud.html#d6e6254
Cheers.
On Thu, Jul 12, 2012 at 9:14 AM, Christian Wittwer
Thanks for the reply.
If I stop the Nova-Compute in Essex-1 machine. then How will Controller and
Nodes communicate via libvirt where in turn Nova-compute handles it.?
On Thu, Jul 12, 2012 at 1:00 PM, Sébastien Han han.sebast...@gmail.comwrote:
$ sudo nova-manage service disable
Oh don't worry.
The nova-scheduler and other nova components will take care all of it.
Just run the disable nova-compute command and run another instance. You'll see.
On Thu, Jul 12, 2012 at 4:16 PM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Thanks for the reply.
If I stop the
Hi-
I have installed Openstack on a Machine ESSEX-1 which is the controller and
Nova-Compute on another machine ESSEX-2 which acts as an agent/node.
When ever I start an new instance, the VM instance is getting created in
the CONTROLLER (ESSEX-1) machine not in the ESSEX-2 machine, the
5 matches
Mail list logo