what is the output of "euca-get-console-output $instancename" and the nova-compute.log on the running node
On Tue, Aug 30, 2011 at 1:55 AM, bhaskar kotha <kothabhas...@gmail.com>wrote: > Dear All, > > I was able to run the instances but the problem I am facing is that the > instances are in shutdown state. > 1. > #euca-run-instances ami-00000003 -k test -t m1.tiny > # euca-describe-instances > RESERVATION r-6t4mze5l admin default > INSTANCE i-00000002 ami-00000003 10.0.0.4 > 10.0.0.4 shutdown test (admin, nova-dx2480-MT) > 0 m1.tiny 2011-08-30T04:29:16Z nova aki-00000001 > ari-00000002 > > how can I make the instance to be in running state. Please suggest. > > Thanks, > Bhaskar > > > > > > > > On Mon, Aug 29, 2011 at 8:21 PM, Leo van den Bulck <lvdbu...@gmail.com>wrote: > >> Mauricio, >> >> This is the one that I used: >> >> http://cloudbuilders.github.com/deploy.sh/hacking-nova.html >> >> It pulls the sources from Bazaar/Launchpad or from Git/Github (you can >> choose which one you want to use by setting environment variables). >> Then you use nova.sh to build, install and run nova/openstack. >> >> I liked the "nova.sh" approach because nova.sh gives you plenty control >> and flexibility over the process. For instance, apart from the GIT variable >> there are some other environment variables that you can tweak, e.g. you can >> have the Dashboard (web based management console) running under Apache httpd >> instead of just as a standalone Django server. >> >> Compared to the other installation approach which uses 'Chef', I liked the >> nova.sh approach better because (1) the Chef procedure requires you to >> become familiar with yet another tool (Chef), (2) the Chef procedure threw >> an error which I had to fix in the Chef "cookbooks" before being able to >> proceed. Nova.sh on the other hand is just a shell script and therefore much >> more accessible if you don't know Chef. The nova,.sh script is even >> documented somewhere in a blog. >> >> Anyway, so you also get this Dashboard, which is nice, but I had to do >> quite a bit of tweaking/hacking to get that part working. For instance I had >> to create some symlinks to get Dashboard/Apache working and had to tweak a >> few Python sources to get rid of some errors. For the rest it worked fine >> (or almost so) out of the box (I believe there was one error thrown by the >> Nova API process which required tweaking a Python module, otherwise only the >> EC2 api runs and not the Nova API - which causes authentication to fail in >> the Dashboard to begin with). >> >> I'm running it within a VirtualBox/Vagrant session (Ubuntu) under Max OS >> X, but that isn't important really, you should be able to use the same >> procedure directly under Ubuntu if you have a Linux box. >> >> I could do a little writeup of what I did exactly to get all of it >> working. >> >> --Leo-- >> >> >> On Aug 29, 2011, at 4:21 PM, Mauricio Arango wrote: >> >> Leo, >> >> Could you please send the link to the Openstack setup that worked for >> you. >> Thanks, >> >> Mauricio >> >> >> >> On Mon, Aug 29, 2011 at 9:45 AM, bhaskar kotha <kothabhas...@gmail.com>wrote: >> >>> >>> Dear Leo van den Bulck , >>> When i am doing ./nova.sh install >>> i am getting following error >>> " Downloading/unpacking glance from bzr+https://launchpad.net/glance(from >>> -r /root/dash/openstack-dashboard/tools/pip-requires (line 19)) >>> Checking out https://launchpad.net/glance to >>> ./.dashboard-venv/build/glance >>> bzr: ERROR: Connection error: curl connection error (server certificate >>> verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: >>> none) >>> " >>> i am having restriction with curl but if i know from where the curl >>> commond runs i can put -k option. >>> But here this is from line 19: pip-requires file bzr+ >>> https://launchpad.net/glance#egg=glance >>> >>> so here i am not getting how to disable curl certification fail. >>> >>> >>> >>> please can any one help me to resolve this issue. >>> >>> Thanks, >>> Bhaskar.K >>> >>> >>> On Mon, Aug 29, 2011 at 4:22 PM, Leo van den Bulck >>> <lvdbu...@gmail.com>wrote: >>> >>>> Hi, >>>> >>>> Why don't you use this guide to set up Openstack (nova//glance): >>>> >>>> >>>> I tried numerous procedures that I found all over the internet (it's >>>> REALLY confusing which is which and what's the status of all those >>>> documents) and permutations thereof, but finally this one worked for me and >>>> it's really easy. >>>> (the other ones include complete Ubuntu images from Stackops, complete >>>> manual installation, automated installation with Vagrant/Chef etc etc - >>>> none >>>> of them really worked for me) >>>> >>>> It even includes installation of the Dashboard (web-based management >>>> interface for Nova) integrated with Keystone (unified authentication >>>> service). >>>> However to get Dashboard/Keystone working I had to do some hacking >>>> because this didn't work out of the box. I can send you my notes on that if >>>> you want to get Dashboard working as well. >>>> >>>> Cheers, >>>> Leo >>>> >>>> >>>> On Aug 29, 2011, at 12:13 PM, KothaBhaskar wrote: >>>> >>>> > Dear All, >>>> >>>> > I am interested in Openstack development, >>>> > i started installation setup, i am getting some errors like >>>> > when i am doing "uec-publish-tarball ubuntu-10.10-server-uec- >>>> > amd64.tar.gz mybucket " step , >>>> > i am getting unknown error "Unable to run euca-describe-images. Is >>>> > euca200ls environment set up? ", >>>> > but i have installed euca200ls setup. >>>> > when i started manual setup " euca-register >>>> > mybucket/machine.manifest.xml " its giving >>>> > "Unknown error, please try again" error. >>>> > >>>> > Please can any one help me to resolve this issue. >>>> > i have tried steps again and again with the help of >>>> > >>>> > http://wiki.openstack.org/RunningNova >>>> > http://wiki.openstack.org/RunningNova/ManualImageRegistration >>>> > >>>> > Thanks, >>>> > Bhaskar.K >>>> > -- >>>> >>>> > This message was sent from Launchpad by >>>> > KothaBhaskar (https://launchpad.net/~kothabhaskar) >>>> > to each member of the OpenStack Team team using the "Contact this >>>> team" link >>>> > on the OpenStack Team team page (https://launchpad.net/~openstack). >>>> > For more information see >>>> > https://help.launchpad.net/YourAccount/ContactingPeople >>>> >>>> >>> >>> >>> -- >>> Thanks, >>> Bhaskar.K >>> >>> _______________________________________________ >>> Mailing list: https://launchpad.net/~openstack >>> Post to : openstack@lists.launchpad.net >>> Unsubscribe : https://launchpad.net/~openstack >>> More help : https://help.launchpad.net/ListHelp >>> >>> >> >> > > > -- > Thanks, > Bhaskar.K > > _______________________________________________ > Mailing list: https://launchpad.net/~openstack > Post to : openstack@lists.launchpad.net > Unsubscribe : https://launchpad.net/~openstack > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
