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 remove its record from > the compute_nodes table, and its nova-compute row from the services table. > > That will prevent nova from launching instances on that server. > > Thanks, > Kiall > > Sent from my mobile... > On Jul 12, 2012 10:17 AM, "Trinath Somanchi" <trinath.soman...@gmail.com> > wrote: > >> 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, Nguyen Son Tung >> <tungns....@gmail.com>wrote: >> >>> Hi Trinath, >>> >>> I'm Neo. >>> I am trying to install nova in 2 nodes like you, but I stuck with >>> nova-network config. >>> How about your installation? >>> >>> Could you run the instances on compute-nodes? >>> How about your nova network setup? >>> >>> Thank you! >>> Regrads, >>> >>> Neo >>> >>> On Thu, Jul 12, 2012 at 1:50 PM, Trinath Somanchi >>> <trinath.soman...@gmail.com> wrote: >>> > 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, 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. "Libvirt error: unable to read from monitor : >>> >> connection reset by peer." >>> >> >>> >> To check this error, I have moved the existing and active instance >>> file >>> >> set to the NODE machine and from the VIRSH console, started the same. >>> This >>> >> particular instance which started and active in the Controller >>> machine gave >>> >> an error in the NODE machine "Libvirt error: unable to read from >>> monitor : >>> >> connection reset by peer." >>> >> >>> >> Is this error Machine specific or Installation specific. >>> >> >>> >> How libvirt communicate in both Controller and Node. >>> >> >>> >> Please help me in resolving the issue. >>> >> >>> >> >>> >> >>> >> -- >>> >> Regards, >>> >> ---------------------------------------------- >>> >> Trinath Somanchi, >>> >> +91 9866 235 130 >>> >> >>> > >>> > >>> > >>> > -- >>> > Regards, >>> > ---------------------------------------------- >>> > Trinath Somanchi, >>> > +91 9866 235 130 >>> > >>> > >>> > _______________________________________________ >>> > Mailing list: https://launchpad.net/~openstack >>> > Post to : openstack@lists.launchpad.net >>> > Unsubscribe : https://launchpad.net/~openstack >>> > More help : https://help.launchpad.net/ListHelp >>> > >>> >>> >>> >>> -- >>> Nguyen Son Tung >>> Cellphone: 0942312007 >>> Skype: neophilo >>> >> >> >> >> -- >> Regards, >> ---------------------------------------------- >> Trinath Somanchi, >> +91 9866 235 130 >> >> >> _______________________________________________ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> -- Regards, ---------------------------------------------- Trinath Somanchi, +91 9866 235 130
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp