Self Resolved
since no memory resources are available, this error is shown.
On Thu, Jul 12, 2012 at 11:06 AM, Trinath Somanchi
trinath.soman...@gmail.com wrote:
Hi-
I have set up two machine a Controller (All Openstack Modules) and Node
(Only Nova-Compute).
In the first instance,
Hi Neo-
I have configured Nova network to use FLATDHCPMANAGER driver.
I'm able to start the instances at NODES.
But some times these instances run at Controller it self. I'm investigating
the terms on how to restrict this.
Hence posted the issue in the list.
On Thu, Jul 12, 2012 at 12:28 PM,
Thanks a lot for the help in replies...
have disabled Nova-compute in Controller. It worked fine..
On Thu, Jul 12, 2012 at 3:48 PM, Kiall Mac Innes ki...@managedit.ie wrote:
Are you saying you don't want instances to run on the controller?
If so, remove nova-compute from the controller and
Hi-
I have set up two machine a Controller (All Openstack Modules) and Node
(Only Nova-Compute).
In the first instance, the VM is getting created in the Controller and is
Active and able to a login.
In the Second Instance the VM is getting created in the Node but stops with
an Spawning error.
4 matches
Mail list logo
