Re: [Openstack] can't install ubuntu from iso..
where are you trying to install Ubuntu? Do you want to use it via glance to OpenStack Nova instance? On 25 June 2013 10:55, imran wrote: > if i try to install ubuntu 12.04 from ISO it does not recognize Root > Disk. It only detects Ephemeral Disk. > what is difference in both.. please help? > > ___ > 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,* * * *Pranav Salunke* *Jr. Cloud Engineer* *Aptira India* +91 97129 29850 +612 8030 2333 1800 APTIRA aptira.com Follow @aptira <https://twitter.com/#!/aptira> ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Slow Instances
it may be due to some configuration errors or also due to lack of physical resources (servers which host compute nodes). It happened to me with less h/w resources on compute. Regards, Pranav On Wed, May 15, 2013 at 6:15 PM, Reza Bakhshayeshi wrote: > Hi > > I have installed Folsom on one ubuntu server 12.04 > my question is why instances are so slow and there is no difference > between tiny and large flavors? > Is this something normal or it depends on my configuration? (if so, please > tell me which configuration?) > > Regards, > Reza > > > > ___ > 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
Re: [Openstack] Grizzly fails on ubuntu server 13.04
but NAT wont make the VM accessible from outside world ... will it? Regards, Pranav On Fri, May 10, 2013 at 5:16 PM, Nikhil Mittal wrote: > Nope, assigning a floating IP is not required. The VM can be accessed with > whatever IP that is assigned as the NAT'ng will take care of that. > > On Fri, May 10, 2013 at 4:50 PM, Pranav wrote: > >> you need to expose the VM's internal network to an external network by >> allocating it floating IP address. >> >> Regards, >> Pranav >> >> >> On Thu, May 9, 2013 at 10:47 PM, Nikhil Mittal wrote: >> >>> I am seeing this email after a long time. Quite recently I tried >>> installing Grizzly on Ubuntu 13.04 on x86 64 machine. It installed fine >>> except that i am facing some network configuration issues after the VMs >>> start running. >>> >>> >>> On Fri, Apr 26, 2013 at 12:05 AM, skible.openst...@gmail.com < >>> skible.openst...@gmail.com> wrote: >>> >>>> Hi, >>>> >>>> So the ubuntu 13.04 has just been released. Everything is fine except >>>> for the virtualization using KVM. >>>> >>>> After installing nova-compute-kvm, nova-compute does not start and this >>>> is what i found in my log file: >>>> >>>> Connection to libvirt failed: Failed to connect socket to >>>> '/var/run/libvirt/libvirt-**sock': No such file or directory >>>> >>>> which is obvious because there is no more KVM in ubuntu 13.04, instead >>>> a qemu-kvm package. >>>> >>>> Anyone got Grizzly on ubuntu 13.04 ? >>>> >>>> >>>> regards, >>>> Bilel >>>> >>>> __**_ >>>> Mailing list: >>>> https://launchpad.net/~**openstack<https://launchpad.net/~openstack> >>>> Post to : openstack@lists.launchpad.net >>>> Unsubscribe : >>>> https://launchpad.net/~**openstack<https://launchpad.net/~openstack> >>>> More help : >>>> https://help.launchpad.net/**ListHelp<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 >>> >>> >> > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Grizzly fails on ubuntu server 13.04
you need to expose the VM's internal network to an external network by allocating it floating IP address. Regards, Pranav On Thu, May 9, 2013 at 10:47 PM, Nikhil Mittal wrote: > I am seeing this email after a long time. Quite recently I tried > installing Grizzly on Ubuntu 13.04 on x86 64 machine. It installed fine > except that i am facing some network configuration issues after the VMs > start running. > > > On Fri, Apr 26, 2013 at 12:05 AM, skible.openst...@gmail.com < > skible.openst...@gmail.com> wrote: > >> Hi, >> >> So the ubuntu 13.04 has just been released. Everything is fine except for >> the virtualization using KVM. >> >> After installing nova-compute-kvm, nova-compute does not start and this >> is what i found in my log file: >> >> Connection to libvirt failed: Failed to connect socket to >> '/var/run/libvirt/libvirt-**sock': No such file or directory >> >> which is obvious because there is no more KVM in ubuntu 13.04, instead a >> qemu-kvm package. >> >> Anyone got Grizzly on ubuntu 13.04 ? >> >> >> regards, >> Bilel >> >> __**_ >> Mailing list: >> https://launchpad.net/~**openstack<https://launchpad.net/~openstack> >> Post to : openstack@lists.launchpad.net >> Unsubscribe : >> https://launchpad.net/~**openstack<https://launchpad.net/~openstack> >> More help : >> https://help.launchpad.net/**ListHelp<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 > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] fail to connect to server (novnc problem)
I agree with Julio 0.0.0.0 seems to be a better idea, since its on the private network (hopefully) it wont be a problem. Regards, Pranav On Sun, Apr 14, 2013 at 3:06 PM, Julio Molina Soler wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi Ralph, > > based on your configuration you are listening on the locahost ip > address (127.0.0.1), I dunno how vnc owrks exactly, but looks more > logic to use: > > - --vncserver_listen=0.0.0.0 > > that would listen on all incoming connections, > and for the proxy client, just don't add it unless is necessary. > > If you are in Linux, can you check if you have any open port for the vnc? > try > # netstat -antop > > Normally it would give you a list of programs and open ports. > > On 13/04/13 14:39, Ralph lewis wrote: > > Hi guys i've problem with my vnc console!! when i launch one > > instance, i can access with ssh but i think it will be preferable > > to access with console!! but my vnc still not working. message: > > fail to connect to server (novnc problem). we installed novnc and > > vnc-consoleauth here's the configuration we did for vnc: > > --novnc_enable=true > > --novnc_proxy_base_url=http://192.168.1.11/vnc_auto.html > > --vncserver_proxyclient_address=127.0.0.1 > > --vncserver_listen=127.0.0.1 > > > > please tell me if i forgot to install a specific thing to make this > > console working!! > > > > PS: i followed stackgeek tutorial. > > > > > > > > KAN MELEDJE RALPH LEWIS > > ---Master RT Université > > de SavoieElève-ingénieur Réseau & Télécom ESTEM-Casablanca > > > > > > > > > > ___ Mailing list: > > https://launchpad.net/~openstack Post to : > > openstack@lists.launchpad.net Unsubscribe : > > https://launchpad.net/~openstack More help : > > https://help.launchpad.net/ListHelp > > > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with undefined - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJRaniZAAoJEAPMPRdDXhBMh+IH/R+bQfezps4VAc+mmNhhYBum > 6FF40jyon3afllXh75uNG8/Y3A9WkNw79RB+tIIFNJlFIyHnZC6PuZc1UYfHPJdD > 9YTpL/9m0bFNZSrxkIVj/SHqTzqooP+frDDMnk1/ayBqsaFabEIueMPsp+4ikhQt > Pxn/k0cc/ZmURvbC4T/e/2oab43iWTGJqkuKoMznj5A7xHSXo2J6mBDI7hOwTyuW > BrsjzlBOy3Z8pzF0/kj3RzvvKxRTzGvbUbhv4iyMxu4oWpajElUl/77VDfEBlU1e > ZueUia4vTXRpDgXwxtXjBS/awTNTsnvgefIXV1uf6z/LJ6JKxNGkrmzhkP2xiEg= > =LKvK > -END PGP SIGNATURE- > > ___ > 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
Re: [Openstack] fail to connect to server (novnc problem)
--vncserver_proxyclient_address=127.0.0.1 --vncserver_listen=127.0.0.1 are you sure about these two Ip addresses? Regards, Pranav On Sun, Apr 14, 2013 at 12:36 AM, Razique Mahroua wrote: > Hey Ralph, > could you have a look at the two following files: > /var/log/nova/novnc.log > /var/log/nova/nova-consoleauth.log > > cheers! > *Razique Mahroua** - **Nuage & Co* > razique.mahr...@gmail.com > Tel : +33 9 72 37 94 15 > > > Le 13 avr. 2013 à 14:39, Ralph lewis a écrit : > > Hi guys > i've problem with my vnc console!! when i launch one instance, i can > access with ssh but i think it will be preferable to access with console!! > but my vnc still not working. message: fail to connect to server (novnc > problem). > we installed novnc and vnc-consoleauth > here's the configuration we did for vnc: > --novnc_enable=true > --novnc_proxy_base_url=http://192.168.1.11/vnc_auto.html > --vncserver_proxyclient_address=127.0.0.1 > --vncserver_listen=127.0.0.1 > > please tell me if i forgot to install a specific thing to make this > console working!! > > PS: i followed stackgeek tutorial. > > > > *KAN MELEDJE RALPH LEWIS * > --**- > Master RT Université de Savoie > Elève-ingénieur Réseau & Télécom ESTEM-Casablanca > ___ > 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 > > <>___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] controller and network node, same machine?
VM's bridged connections are also good ... for both VM to VM and otherwise. I have two compute nodes in my university and the network node and control node are Virtual Box VM instances on my Laptop. Regards, Pranav On Sat, Apr 13, 2013 at 12:34 AM, Steve Heistand wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > well its me playing around with openstack so I wouldnt say "production" > environment. > but certainly on a dedicated rack full of nodes that just do openstack. > running ubuntu 12.04lts on everything. > > the controller+network is on its own box with a boatload of ethernet > connections > around to various places including the dual ethernet dual switch compute > nodes. > > vm to vm is good, vm to anywhere else not so much. > > s > > > On 04/12/2013 10:32 AM, Pranav wrote: > > oops clicked send too soon ... Do you mean production environment by > same physical > > box? Because I have tried it and it worked for me but it was on a ubuntu > desktop > > which is kind of like a hybrid of server + desktop now. > > > > Regards, Pranav > > > > > > On Fri, Apr 12, 2013 at 11:01 PM, Pranav > <mailto:pps.pra...@gmail.com>> wrote: > > > > Do you mean production environment by same physical box? Because I have > tried it and > > it worked for me. > > > > Regards, Pranav > > > > > > On Fri, Apr 12, 2013 at 10:35 PM, Guilherme Russi < > luisguilherme...@gmail.com > > <mailto:luisguilherme...@gmail.com>> wrote: > > > > Hello Steve, I had a lot of troubles deploying my openstack and putting > my controller > > node at the same physical machine with my network node, I have 2 NICs in > my > > controller + network node, if you need help, I can help you. > > > > Regards. > > > > Guilherme. > > > > > > 2013/4/12 Steve Heistand steve.heist...@nasa.gov>> > > > > mostly Im concerned about the quantum/OVS/qre settings. there are > distinct difference > > in the values in the ovs_quantum_plugin.ini file depending on what type > of node the > > agent is running on. I wasnt sure if it going to work. The problems Ive > been having > > are all network related all centered around getting VMs on compute nodes > to be able > > to see something besides another VM in their tenant. ie the outside > world. But my > > network/ovs-fu is limited so its entirely possible its my fault. just > wanted to see > > if it was even possible in the first place. > > > > s > > > > > > On 04/12/2013 06:05 AM, Mohammed Amine SAYA wrote: > >> Hi Steve, > > > >> Why do you say that? I am curious to learn about the difficulties you > have had. > > > >> I also tried to have controller node and network node running on the > same machine > >> but I have never managed to ping a running VM in this configuration > with FOLSOM > >> release. Everything was working fine but impossible to ping a VM. > > > >> Amine. > > > > > >> On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand < > steve.heist...@nasa.gov > >> <mailto:steve.heist...@nasa.gov> <mailto:steve.heist...@nasa.gov > >> <mailto:steve.heist...@nasa.gov>>> wrote: > > > >> so Im beginning to think my attempts at getting a controller node and a > network > >> node to be on the same physical machines/OS are doomed. > > > >> is it even possible to have all the controller and network node > features on the > >> same box? Aside from one of them being in a VM that is. > > > >> thanks > > > >> s > > > >> -- > > Steve > >> Heistand NASA Ames Research Center SciCon > Group Mail Stop > >> 258-6steve.heist...@nasa.gov <mailto:steve.heist...@nasa.gov> > > <mailto:steve.heist...@nasa.gov <mailto:steve.heist...@nasa.gov>> (650) > >> 604-4369 Moffett Field, CA 94035-1000 > >> > > "Any > >> opinions expressed are those of our alien overlords, not my own." > > > >> # For Remedy# #Action: Resolve ># > >> #Resolution: Resolved # #Reason: No Further Action > Required # > >> #Tier1: User Code # #Tier2: Other > # > >> #Tier3: Assistance # #Notification: None > # > > > > > > >
Re: [Openstack] controller and network node, same machine?
oops clicked send too soon ... Do you mean production environment by same physical box? Because I have tried it and it worked for me but it was on a ubuntu desktop which is kind of like a hybrid of server + desktop now. Regards, Pranav On Fri, Apr 12, 2013 at 11:01 PM, Pranav wrote: > Do you mean production environment by same physical box? Because I have > tried it and it worked for me. > > Regards, > Pranav > > > On Fri, Apr 12, 2013 at 10:35 PM, Guilherme Russi < > luisguilherme...@gmail.com> wrote: > >> Hello Steve, I had a lot of troubles deploying my openstack and putting >> my controller node at the same physical machine with my network node, I >> have 2 NICs in my controller + network node, if you need help, I can help >> you. >> >> Regards. >> >> Guilherme. >> >> >> 2013/4/12 Steve Heistand >> >>> -BEGIN PGP SIGNED MESSAGE- >>> Hash: SHA1 >>> >>> mostly Im concerned about the quantum/OVS/qre settings. >>> there are distinct difference in the values in the ovs_quantum_plugin.ini >>> file depending on what type of node the agent is running on. >>> I wasnt sure if it going to work. >>> The problems Ive been having are all network related all centered around >>> getting VMs on compute nodes to be able to see something besides another >>> VM in their tenant. ie the outside world. >>> But my network/ovs-fu is limited so its entirely possible its my fault. >>> just wanted to see if it was even possible in the first place. >>> >>> s >>> >>> >>> On 04/12/2013 06:05 AM, Mohammed Amine SAYA wrote: >>> > Hi Steve, >>> > >>> > Why do you say that? I am curious to learn about the difficulties you >>> have had. >>> > >>> > I also tried to have controller node and network node running on the >>> same machine but >>> > I have never managed to ping a running VM in this configuration with >>> FOLSOM release. >>> > Everything was working fine but impossible to ping a VM. >>> > >>> > Amine. >>> > >>> > >>> > On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand < >>> steve.heist...@nasa.gov >>> > <mailto:steve.heist...@nasa.gov>> wrote: >>> > >>> > so Im beginning to think my attempts at getting a controller node and >>> a network node >>> > to be on the same physical machines/OS are doomed. >>> > >>> > is it even possible to have all the controller and network node >>> features on the same >>> > box? Aside from one of them being in a VM that is. >>> > >>> > thanks >>> > >>> > s >>> > >>> > -- >>> >>> Steve >>> > Heistand NASA Ames Research Center SciCon >>> Group >>> > Mail Stop 258-6 steve.heist...@nasa.gov >> steve.heist...@nasa.gov> (650) >>> > 604-4369 Moffett Field, CA 94035-1000 >>> > >>> >>> "Any >>> > opinions expressed are those of our alien overlords, not my own." >>> > >>> > # For Remedy# #Action: Resolve >>># >>> > #Resolution: Resolved # #Reason: No Further Action >>> Required # #Tier1: >>> > User Code # #Tier2: Other # >>> #Tier3: >>> > Assistance # #Notification: None # >>> > >>> > >>> > >>> > ___ Mailing list: >>> > https://launchpad.net/~openstack Post to : >>> openstack@lists.launchpad.net >>> > <mailto:openstack@lists.launchpad.net> Unsubscribe : >>> > https://launchpad.net/~openstack More help : >>> https://help.launchpad.net/ListHelp >>> > >>> > >>> >>> - -- >>> >>> Steve Heistand NASA Ames Research Center >>> email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 >>> ph: (650) 604-4369 Bldg. 258, Rm. 232-5 >>> Scientific & HPC ApplicationP.O. Box 1 >>>
Re: [Openstack] controller and network node, same machine?
Do you mean production environment by same physical box? Because I have tried it and it worked for me. Regards, Pranav On Fri, Apr 12, 2013 at 10:35 PM, Guilherme Russi < luisguilherme...@gmail.com> wrote: > Hello Steve, I had a lot of troubles deploying my openstack and putting my > controller node at the same physical machine with my network node, I have 2 > NICs in my controller + network node, if you need help, I can help you. > > Regards. > > Guilherme. > > > 2013/4/12 Steve Heistand > >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> mostly Im concerned about the quantum/OVS/qre settings. >> there are distinct difference in the values in the ovs_quantum_plugin.ini >> file depending on what type of node the agent is running on. >> I wasnt sure if it going to work. >> The problems Ive been having are all network related all centered around >> getting VMs on compute nodes to be able to see something besides another >> VM in their tenant. ie the outside world. >> But my network/ovs-fu is limited so its entirely possible its my fault. >> just wanted to see if it was even possible in the first place. >> >> s >> >> >> On 04/12/2013 06:05 AM, Mohammed Amine SAYA wrote: >> > Hi Steve, >> > >> > Why do you say that? I am curious to learn about the difficulties you >> have had. >> > >> > I also tried to have controller node and network node running on the >> same machine but >> > I have never managed to ping a running VM in this configuration with >> FOLSOM release. >> > Everything was working fine but impossible to ping a VM. >> > >> > Amine. >> > >> > >> > On Fri, Apr 12, 2013 at 2:40 PM, Steve Heistand < >> steve.heist...@nasa.gov >> > <mailto:steve.heist...@nasa.gov>> wrote: >> > >> > so Im beginning to think my attempts at getting a controller node and a >> network node >> > to be on the same physical machines/OS are doomed. >> > >> > is it even possible to have all the controller and network node >> features on the same >> > box? Aside from one of them being in a VM that is. >> > >> > thanks >> > >> > s >> > >> > -- >> >> Steve >> > Heistand NASA Ames Research Center SciCon >> Group >> > Mail Stop 258-6 steve.heist...@nasa.gov <mailto:steve.heist...@nasa.gov> >> (650) >> > 604-4369 Moffett Field, CA 94035-1000 >> > >> >> "Any >> > opinions expressed are those of our alien overlords, not my own." >> > >> > # For Remedy# #Action: Resolve >># >> > #Resolution: Resolved # #Reason: No Further Action >> Required # #Tier1: >> > User Code # #Tier2: Other # >> #Tier3: >> > Assistance # #Notification: None # >> > >> > >> > >> > ___ Mailing list: >> > https://launchpad.net/~openstack Post to : >> openstack@lists.launchpad.net >> > <mailto:openstack@lists.launchpad.net> Unsubscribe : >> > https://launchpad.net/~openstack More help : >> https://help.launchpad.net/ListHelp >> > >> > >> >> - -- >> >> Steve Heistand NASA Ames Research Center >> email: steve.heist...@nasa.gov Steve Heistand/Mail Stop 258-6 >> ph: (650) 604-4369 Bldg. 258, Rm. 232-5 >> Scientific & HPC ApplicationP.O. Box 1 >> Development/OptimizationMoffett Field, CA 94035-0001 >> >> "Any opinions expressed are those of our alien overlords, not my own." >> >> # For Remedy# >> #Action: Resolve# >> #Resolution: Resolved # >> #Reason: No Further Action Required # >> #Tier1: User Code # >> #Tier2: Other # >> #Tier3: Assistance # >> #Notification: None # >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v2.0.14 (GNU/Linux) >> >> iEYEARECAAYF
Re: [Openstack] [Nova] How To Print Console OutPut Dynamically
I may be thinking totally wrong but I think that if you want to do a small hack which calls the same method/api (every x seconds) which is called to display the console log message on horizon dash. But I cant say this will work or even if this does, whether it is a good hack or not. Regards, Pranav On Sun, Apr 7, 2013 at 4:15 PM, Jiang Jim wrote: > I am a user of nova, I found that the console log nova output can just > refresh manually. > I think if i can see dynamic output, I will happy with that. > I found pty and file type in virt/libvirt/driver.py, file can just output > logs static, but I don't know how to use pty to output console dynamically. > I implement a websocket server in the front just like the same novnc > does. And I code a module in nova.contrib to get host and path of > console.log by nova-api. > > I have two choice now, one is to tail console.log in every compute node, > every instance will open a port. > Another is to do something with pty. > > I am confused and in trouble, I would be grateful if anyone could help me > about that. > > ___ > 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
Re: [Openstack] Unable to successfully create instances with horizon
Hi, First of all congratulations on your progress.
I believe that you have to access your VNC from the same network that your
VNC Proxy has been configured on. I believe that this is not related to the
fact that your Server Node is a VM instance itselves.
What I do is for Host Only Connections configure one of the hosts networks
such that it matches the one with the VNC proxy or for bridged networks its
pretty much similar to how it is actually done.
Regards,
Pranav
On Fri, Apr 5, 2013 at 11:31 PM, AJ Schroeder wrote:
> Hello Pranav,
>
> ** **
>
> Thank you for the response and the links. I setup a machine with ESXi for
> testing everything out. You were right, the lack of VT support inside the
> VMs was one issue, as well as me (foolishly) using an x86_64 cirros image.
> Once I got the right cirros image I am able to spawn instances without an
> issue. I am not however able to VNC to any of the instances, I am getting
> the dreaded 1006 error code. I did quite a bit of googling on this error
> and the issues were mostly reachability or misconfiguration of the
> nova.conf file. Is there anything I can look at to troubleshoot this or is
> there any messages I can post that would help fix this?
>
> ** **
>
> Not sure if I should start a new thread on this or not.
>
> ** **
>
> Thank you,****
>
> ** **
>
> AJ Schroeder
>
> ** **
>
> *From:* Pranav [mailto:pps.pra...@gmail.com]
> *Sent:* Saturday, March 16, 2013 7:40 AM
> *To:* ajschroe...@hotmail.com
> *Cc:* openstack@lists.launchpad.net
> *Subject:* Re: [Openstack] Unable to successfully create instances with
> horizon
>
> ** **
>
> Hi,
>
> I have a similar setup and I spawn Nova Instances inside OpenStack
> deployed on VirtuaBox VM instances. Make sure that your VM's are configured
> to Qemu and not KVM as KVM will not work inside VM's. Also check this out
> it has complete steps to setup OpenStack on VM's.
> https://github.com/dguitarbite/OpenStack-Folsom-VM-SandBox-Guide
>
> Regards,
> Pranav
>
> ** **
>
> On Sat, Mar 16, 2013 at 5:47 AM, AJ Schroeder
> wrote:
>
> Hello list,
>
>
>
> I’ve been following along with these instructions to get an openstack
> environment setup:
> http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.html-
> I am a total newbie with openstack.
>
>
>
>
> I am using virtualbox with Ubuntu 12.04 LTS guests and I have all three
> nodes setup and operational. After some troubleshooting I was finally able
> to create volumes in cinder, but now I can’t successfully create any
> instances. I use horizon and navigate through the process of setting up the
> instance, and when I click launch the instance shows up in the list, but
> the status is always “error”. I’m not sure what to post that would be
> relevant, but here are some log entries and output:
>
>
>
> # -- nova-scheduler.log --#
>
> 2013-03-15 09:40:13 1475 DEBUG nova.openstack.common.rpc.amqp [-] received
> {u'_context_roles': [u'Member', u'admin'], u'_context_request_id':
> u'req-cccd3bed-8a37-4166-be5d-02f74221a2b6', u'_context_quota_class': None,
> u'_context_project_name': u'demo', u'_context_service_catalog':
> [{u'endpoints': [{u'adminURL': u'
> http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a', u'region':
> u'RegionOne', u'internalURL': u'
> http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a', u'id':
> u'110f0468149c42c88256f02a01aa54d0', u'publicURL': u'
> http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a'}],
> u'endpoints_links': [], u'type': u'compute', u'name': u'nova'},
> {u'endpoints': [{u'adminURL': u'http://192.168.1.1:9696/', u'region':
> u'RegionOne', u'internalURL': u'http://192.168.1.1:9696/', u'id':
> u'45faf59eb6c747daaae2ef16a68e7eef', u'publicURL': u'
> http://192.168.1.1:9696/'}], u'endpoints_links': [], u'type': u'network',
> u'name': u'quantum'}, {u'endpoints': [{u'adminURL': u'
> http://192.168.1.1:9292/v2', u'region': u'RegionOne', u'internalURL': u'
> http://192.168.1.1:9292/v2', u'id': u'16938ca8049446688ce57f7f98a71c32',
> u'publicURL': u'http://192.168.1.1:9292/v2'}], u'endpoints_links': [],
>
Re: [Openstack] Gerrit Review + SSH
+1 Regards, Pranav On Fri, Apr 5, 2013 at 12:07 AM, Jay Pipes wrote: > On 04/04/2013 02:23 PM, Jeremy Stanley wrote: > > On 2013-04-04 10:51:20 -0700 (-0700), Ronak Shah wrote: > >> As OS dev cycle involves Gerrit review tool which requires ssh > >> into the gerrit server, I was wondering if any of you guys face > >> problems where your company/org does not allow ssh to external > >> hosts. > > [...] > > > > It usually involves the uphill battle of convincing whoever manages > > network security/firewalls/proxies for your employer that the > > Internet is more than just a bunch of Web pages. Companies which > > exclusively limit their employees to only browsing the Web are > > basically cutting themselves off from innovations which rely on a > > myriad of other protocols. For non-technology companies that might > > be fine, but for a technology company that's often a sign that it's > > going out of business pretty soon. > > +1000 > > ___ > 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
Re: [Openstack] Error while trying to login to Devstack dashboard
Hi, This guide is tested and good for similar setups in Virtual Box https://github.com/dguitarbite/OpenStack-Folsom-VM-SandBox-Guide Regards, Pranav On Wed, Mar 20, 2013 at 8:29 AM, Dolph Mathews wrote: > Make sure that the certs created by pki_setup are readable by the user > running keystone-all > > > -Dolph > > > On Tue, Mar 19, 2013 at 12:19 PM, Abhishek Chanda < > abhishek.li...@gmail.com> wrote: > >> I actually did that and when I ran keystone-all again, I got the same >> error. The console log in my first mail shows this. Sorry for being vague >> about this. >> >> *abhishek@abhishek-VirtualBox:~$ sudo keystone-manage pki_setup* >> abhishek@abhishek-VirtualBox:~$ keystone-all >> /usr/local/lib/python2.7/dist-packages/sqlalchemy/pool.py:703: >> SADeprecationWarning: The 'listeners' argument to Pool (and >> create_engine()) is deprecated. Use event.listen(). >> Pool.__init__(self, creator, **kw) >> /usr/local/lib/python2.7/dist-packages/sqlalchemy/pool.py:160: >> SADeprecationWarning: Pool.add_listener is deprecated. Use event.listen() >> self.add_listener(l) >> 2013-03-18 13:30:55ERROR [keystone.common.cms] Signing error: Unable >> to load certificate - ensure you've configured PKI with 'keystone-manage >> pki_setup' >> 2013-03-18 13:30:55 WARNING [keystone.common.wsgi] Unable to sign token. >> >> Thanks >> >> >> On Tue, Mar 19, 2013 at 4:53 AM, Chmouel Boudjnah wrote: >> >>> On Mon, Mar 18, 2013 at 7:03 PM, Abhishek Chanda >>> wrote: >>> > 2013-03-18 13:30:55ERROR [keystone.common.cms] Signing error: >>> Unable to >>> > load certificate - ensure you've configured PKI with 'keystone-manage >>> > pki_setup' >>> >>> >>> perhaps by doing this? >>> >>> Chmouel. >>> >>> ___ >>> 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 >> >> > > ___ > 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
Re: [Openstack] Openstack Metadata Service
thanks will try that asap Regards, Pranav On Tue, Mar 19, 2013 at 8:53 PM, bruno sendas wrote: > Hi, > > I had tried every sollution posted on the openstack archives and it simply > wouldn't work. > Until I had the wrong idea and installed the nova-api-metadata on the > controller node and it removed the nova-api, which corrupted the openstack > deployment. So when I re-installed all the nova components (the > nova-api-metadata was removed), one reboot later and the metadata server > was running. :))) > > Also, I added a route to the Private Network ( for the VM) using the > router external gateway. > > The problem must have been from a bad installation of nova-api int the > controller node. > > best regards, > Bruno > > > 2013/3/18 Pranav > >> I think this should solve the metadata issue, but there is one more >> issue, the instances do not seem to get IP address and also it is not so >> clear weather to use L2 with L3. >> Regards, >> Pranav >> >> >> On Tue, Mar 19, 2013 at 1:18 AM, Anne Gentle wrote: >> >>> Hi all, >>> >>> I've got a doc bug against the Basic Install guide that I've been trying >>> to understand. [1] >>> >>> The first issue is that the Basic Install guide doesn't tell the user to >>> install the nova-api-metadata service. But there's more to it than just >>> that, I believe. Two doc comments have noted that there's a routing issue >>> as well: >>> >>> "there seems to be a step left out of this guide on the controller setup >>> ...once you create the tenant subnets you need to add the route from the >>> internal ips in this case route add -n 10.5.5.0/24 gw (the external >>> router project IP ) once i did this on the controller node it pulls the >>> metadata perfectly" >>> >>> Does this routing sound like the solution in your cases? >>> >>> Anne >>> >>> 1. https://bugs.launchpad.net/openstack-manuals/+bug/1108040 >>> >>> >>> On Mon, Mar 18, 2013 at 2:11 PM, Pranav wrote: >>> >>>> Having similar issues... someone please do help us if poss. >>>> Regards, >>>> Pranav >>>> >>>> >>>> On Tue, Mar 19, 2013 at 12:35 AM, Gui Maluf wrote: >>>> >>>>> >>>>> >>From what I understood, without the retrieval of the metadata from the >>>>> >server, the keys are not downloaded to the VM, is this correct? >>>>> >>>>> Yes. This is correct. >>>>> >>>>> AFAIK in Essex, the metadata service was pointed out through iptables. So >>>>> there was a rule that DNAT the metadata service to the CC machine. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I had this metadata problem too, but I couldn't find out a proper >>>>> solution. >>>>> My guess is that this problem is related to the Gateway/Router in >>>>> Folsom+Quantum installation. Or maybe in the metadata_host in the >>>>> nova.conf file. >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> I hope someone could clarify this things for us. >>>>> >>>>> >>>>> regards. >>>>> >>>>> >>>>> >>>>> On Mon, Mar 18, 2013 at 7:32 AM, Bruno Parreira wrote: >>>>> >>>>>> >>>>>> Hi, >>>>>> >>>>>> >>>>>> >>>>>> We have deployed OpenStack using the guide provided at the OpenStack >>>>>> webpage: >>>>>> >>>>>> Host A : controller node >>>>>> >>>>>> Host B : network node >>>>>> >>>>>> Host C : compute node >>>>>> >>>>>> >>>>>> >>>>>> Everything went fine during the installation process, but when we try to >>>>>> instantiate a VM, the logs show that the VMs are unable to connect to the >>>>>> metadata service (169.254.169.254). >>>>>> >>>>>> We've tried this with the Ubuntu image and the Cirr
Re: [Openstack] Openstack Metadata Service
I think this should solve the metadata issue, but there is one more issue, the instances do not seem to get IP address and also it is not so clear weather to use L2 with L3. Regards, Pranav On Tue, Mar 19, 2013 at 1:18 AM, Anne Gentle wrote: > Hi all, > > I've got a doc bug against the Basic Install guide that I've been trying > to understand. [1] > > The first issue is that the Basic Install guide doesn't tell the user to > install the nova-api-metadata service. But there's more to it than just > that, I believe. Two doc comments have noted that there's a routing issue > as well: > > "there seems to be a step left out of this guide on the controller setup > ...once you create the tenant subnets you need to add the route from the > internal ips in this case route add -n 10.5.5.0/24 gw (the external > router project IP ) once i did this on the controller node it pulls the > metadata perfectly" > > Does this routing sound like the solution in your cases? > > Anne > > 1. https://bugs.launchpad.net/openstack-manuals/+bug/1108040 > > > On Mon, Mar 18, 2013 at 2:11 PM, Pranav wrote: > >> Having similar issues... someone please do help us if poss. >> Regards, >> Pranav >> >> >> On Tue, Mar 19, 2013 at 12:35 AM, Gui Maluf wrote: >> >>> >>> >>From what I understood, without the retrieval of the metadata from the >>> >server, the keys are not downloaded to the VM, is this correct? >>> >>> Yes. This is correct. >>> >>> AFAIK in Essex, the metadata service was pointed out through iptables. So >>> there was a rule that DNAT the metadata service to the CC machine. >>> >>> >>> >>> >>> >>> >>> I had this metadata problem too, but I couldn't find out a proper solution. >>> My guess is that this problem is related to the Gateway/Router in >>> Folsom+Quantum installation. Or maybe in the metadata_host in the nova.conf >>> file. >>> >>> >>> >>> >>> >>> >>> >>> I hope someone could clarify this things for us. >>> >>> >>> regards. >>> >>> >>> >>> On Mon, Mar 18, 2013 at 7:32 AM, Bruno Parreira wrote: >>> >>>> >>>> Hi, >>>> >>>> >>>> >>>> We have deployed OpenStack using the guide provided at the OpenStack >>>> webpage: >>>> >>>> Host A : controller node >>>> >>>> Host B : network node >>>> >>>> Host C : compute node >>>> >>>> >>>> >>>> Everything went fine during the installation process, but when we try to >>>> instantiate a VM, the logs show that the VMs are unable to connect to the >>>> metadata service (169.254.169.254). >>>> >>>> We've tried this with the Ubuntu image and the Cirros image, but the result >>>> is the same. >>>> >>>> >>>> >>>> >From what I understood, without the retrieval of the metadata from the >>>> server, the keys are not downloaded to the VM, is this correct? >>>> >>>> Because we can ping the IP address assigned to the VM from the network >>>> node, >>>> and if we assign a floating IP to the VM, the public IP also responds to >>>> ping replys. >>>> >>>> But we are unable to ssh into the VMs, with the error: "Read from socket >>>> failed: Connection reset by peer" >>>> >>>> If we try to telnet into the public IP this is the result: >>>> >>>> >>>> >>>> controller@controller:~$ telnet x.x.x.x 22 >>>> >>>> Trying x.x.x.x... >>>> >>>> Connected to x.x.x.x. >>>> >>>> Escape character is '^]'. >>>> >>>> SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 >>>> >>>> >>>> >>>> Protocol mismatch. >>>> >>>> Connection closed by foreign host. >>>> >>>> >>>> >>>> Questions: >>>> >>>> In which node is the metadata service supposed to be running (compute, >>>> network or controller)? >>>> >>>> Should the IP address 169.254.169.254 be reachable outside the VM? >>>> >>>> Is there an alternative to the metadata service? >>>> >>>> >>>> >>>> Kind regards, >>>> >>>> Bruno Parreira >>>> >>>> >>>> >>>> ___ >>>> Mailing list: https://launchpad.net/~openstack >>>> Post to : openstack@lists.launchpad.net >>>> Unsubscribe : https://launchpad.net/~openstack >>>> More help : https://help.launchpad.net/ListHelp >>>> >>>> >>> >>> >>> -- >>> *guilherme* \n >>> \t *maluf* >>> >>> ___ >>> 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 >> >> > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Openstack Metadata Service
Having similar issues... someone please do help us if poss. Regards, Pranav On Tue, Mar 19, 2013 at 12:35 AM, Gui Maluf wrote: > > >>From what I understood, without the retrieval of the metadata from the > >server, the keys are not downloaded to the VM, is this correct? > > Yes. This is correct. > > AFAIK in Essex, the metadata service was pointed out through iptables. So > there was a rule that DNAT the metadata service to the CC machine. > > > I had this metadata problem too, but I couldn't find out a proper solution. > My guess is that this problem is related to the Gateway/Router in > Folsom+Quantum installation. Or maybe in the metadata_host in the nova.conf > file. > > > > I hope someone could clarify this things for us. > > > regards. > > > > On Mon, Mar 18, 2013 at 7:32 AM, Bruno Parreira wrote: > >> >> Hi, >> >> >> >> We have deployed OpenStack using the guide provided at the OpenStack >> webpage: >> >> Host A : controller node >> >> Host B : network node >> >> Host C : compute node >> >> >> >> Everything went fine during the installation process, but when we try to >> instantiate a VM, the logs show that the VMs are unable to connect to the >> metadata service (169.254.169.254). >> >> We've tried this with the Ubuntu image and the Cirros image, but the result >> is the same. >> >> >> >> >From what I understood, without the retrieval of the metadata from the >> server, the keys are not downloaded to the VM, is this correct? >> >> Because we can ping the IP address assigned to the VM from the network node, >> and if we assign a floating IP to the VM, the public IP also responds to >> ping replys. >> >> But we are unable to ssh into the VMs, with the error: "Read from socket >> failed: Connection reset by peer" >> >> If we try to telnet into the public IP this is the result: >> >> >> >> controller@controller:~$ telnet x.x.x.x 22 >> >> Trying x.x.x.x... >> >> Connected to x.x.x.x. >> >> Escape character is '^]'. >> >> SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 >> >> >> >> Protocol mismatch. >> >> Connection closed by foreign host. >> >> >> >> Questions: >> >> In which node is the metadata service supposed to be running (compute, >> network or controller)? >> >> Should the IP address 169.254.169.254 be reachable outside the VM? >> >> Is there an alternative to the metadata service? >> >> >> >> Kind regards, >> >> Bruno Parreira >> >> >> >> ___ >> Mailing list: https://launchpad.net/~openstack >> Post to : openstack@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~openstack >> More help : https://help.launchpad.net/ListHelp >> >> > > > -- > *guilherme* \n > \t *maluf* > > ___ > 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
Re: [Openstack] [Quantum] Access problem to Metadata server
there is a problem with Quantum Network you need to use L2 and L3 agents. Or Nova-Networks. Regards, Pranav On Fri, Mar 15, 2013 at 1:55 PM, Sylvain Bauza wrote: > > > Le 15/03/2013 08:20, Sammy Fung a écrit : > > I am following this nice guide to configure Quantum. > > > https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/GRE/2NICs/OpenStack_Folsom_Install_Guide_WebVersion.rst > > > > I got timeout on HTTP request to 169.254.169.254 connecting from VM. > > $ wget http://169.254.169.254/2009-04-04/meta-data/instance-id > Connecting to 169.254.169.254 (169.254.169.254:80) > wget: can't connect to remote host (169.254.169.254): Connection timed out > > But I got 404 Not Found if I connect to public IP port 8775 connecting > from VM. > > $ wget http://1.2.3.4:8775/2009-04-04/meta-data/instance-id > > Connecting to 1.2.3.4:8775 (1.2.3.4:8775) > wget: server returned error: HTTP/1.1 404 Not Found > > > >Anything I can try for debug/solving it ? > > > As said in the guide, make sure your host running nova-api (incl. > metadata, ie. 1.2.3.4) does have a route to the public IPs of your VMs. > > -Sylvain > > ___ > 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
Re: [Openstack] Unable to successfully create instances with horizon
Hi,
I have a similar setup and I spawn Nova Instances inside OpenStack deployed
on VirtuaBox VM instances. Make sure that your VM's are configured to Qemu
and not KVM as KVM will not work inside VM's. Also check this out it has
complete steps to setup OpenStack on VM's.
https://github.com/dguitarbite/OpenStack-Folsom-VM-SandBox-Guide
Regards,
Pranav
On Sat, Mar 16, 2013 at 5:47 AM, AJ Schroeder wrote:
> Hello list,
>
> ** **
>
> I’ve been following along with these instructions to get an openstack
> environment setup:
> http://docs.openstack.org/folsom/basic-install/content/basic-install_intro.html-
> I am a total newbie with openstack.
>
>
> ** **
>
> I am using virtualbox with Ubuntu 12.04 LTS guests and I have all three
> nodes setup and operational. After some troubleshooting I was finally able
> to create volumes in cinder, but now I can’t successfully create any
> instances. I use horizon and navigate through the process of setting up the
> instance, and when I click launch the instance shows up in the list, but
> the status is always “error”. I’m not sure what to post that would be
> relevant, but here are some log entries and output:
>
> ** **
>
> # -- nova-scheduler.log --#
>
> 2013-03-15 09:40:13 1475 DEBUG nova.openstack.common.rpc.amqp [-] received
> {u'_context_roles': [u'Member', u'admin'], u'_context_request_id':
> u'req-cccd3bed-8a37-4166-be5d-02f74221a2b6', u'_context_quota_class': None,
> u'_context_project_name': u'demo', u'_context_service_catalog':
> [{u'endpoints': [{u'adminURL': u'
> http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a', u'region':
> u'RegionOne', u'internalURL': u'
> http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a', u'id':
> u'110f0468149c42c88256f02a01aa54d0', u'publicURL': u'
> http://192.168.1.1:8774/v2/ef28e5b6b9d143c4baa15b271440586a'}],
> u'endpoints_links': [], u'type': u'compute', u'name': u'nova'},
> {u'endpoints': [{u'adminURL': u'http://192.168.1.1:9696/', u'region':
> u'RegionOne', u'internalURL': u'http://192.168.1.1:9696/', u'id':
> u'45faf59eb6c747daaae2ef16a68e7eef', u'publicURL': u'
> http://192.168.1.1:9696/'}], u'endpoints_links': [], u'type': u'network',
> u'name': u'quantum'}, {u'endpoints': [{u'adminURL': u'
> http://192.168.1.1:9292/v2', u'region': u'RegionOne', u'internalURL': u'
> http://192.168.1.1:9292/v2', u'id': u'16938ca8049446688ce57f7f98a71c32',
> u'publicURL': u'http://192.168.1.1:9292/v2'}], u'endpoints_links': [],
> u'type': u'image', u'name': u'glance'}, {u'endpoints': [{u'adminURL': u'
> http://192.168.1.1:8776/v1/ef28e5b6b9d143c4baa15b271440586a', u'region':
> u'RegionOne', u'internalURL': u'
> http://192.168.1.1:8776/v1/ef28e5b6b9d143c4baa15b271440586a',
> u'serviceName': u'cinder', u'id': u'f7a1448a776c4aa2b6a5843f38c33022',
> u'publicURL': u'
> http://192.168.1.1:8776/v1/ef28e5b6b9d143c4baa15b271440586a'}],
> u'endpoints_links': [], u'type': u'volume', u'name': u'cinder'},
> {u'endpoints': [{u'adminURL': u'http://192.168.1.1:8773/services/Admin',
> u'region': u'RegionOne', u'internalURL': u'
> http://192.168.1.1:8773/services/Cloud', u'id':
> u'0bb938dbb76d44ae94fa24998c3c8a94', u'publicURL': u'
> http://192.168.1.1:8773/services/Cloud'}], u'endpoints_links': [],
> u'type': u'ec2', u'name': u'ec2'}, {u'endpoints': [{u'adminURL': u'
> http://192.168.1.1:8080/v1', u'region': u'RegionOne', u'internalURL': u'
> http://192.168.1.1:8080/v1/AUTH_ef28e5b6b9d143c4baa15b271440586a', u'id':
> u'169ad8d8a930442ba189b626e1f574f7', u'publicURL': u'
> http://192.168.1.1:8080/v1/AUTH_ef28e5b6b9d143c4baa15b271440586a'}],
> u'endpoints_links': [], u'type': u'object-store', u'name': u'swift'},
> {u'endpoints': [{u'adminURL': u'h
Re: [Openstack] ssh from VM to VM
I think you need not exchange key pairs for Cirros image. Regards, Pranav On Sat, Mar 16, 2013 at 4:32 PM, Chathura M. Sarathchandra Magurawalage < 77.chath...@gmail.com> wrote: > Thanks for your reply. > > I have inserted PasswordAuthentication yes to the ssh config file. All > VMs have the same metadata including the ssh public key of the controller. > So I cant see why only cirros vms can do this. > > Still does not work. > > > > On 16 March 2013 06:24, Aaron Rosen wrote: > >> I suspect that that host 10.5.5.6 has ssh configured for >> PasswordAuthentication set to no and you don't have your public key of the >> host you are on, in the authorized_key file of 10.5.5.6. >> >> Aaron >> >> On Fri, Mar 15, 2013 at 7:26 PM, Chathura M. Sarathchandra Magurawalage >> <77.chath...@gmail.com> wrote: >> >>> Hello, >>> >>> I can't ssh from Ubuntu cloud VM to other VM. I get following >>> >>> ubuntu@master:~$ ssh cirros@10.5.5.6 -v >>> OpenSSH_5.9p1 Debian-5ubuntu1, OpenSSL 1.0.1 14 Mar 2012 >>> debug1: Reading configuration data /etc/ssh/ssh_config >>> debug1: /etc/ssh/ssh_config line 19: Applying options for * >>> debug1: Connecting to 10.5.5.6 [10.5.5.6] port 22. >>> debug1: Connection established. >>> debug1: identity file /home/ubuntu/.ssh/id_rsa type -1 >>> debug1: identity file /home/ubuntu/.ssh/id_rsa-cert type -1 >>> debug1: identity file /home/ubuntu/.ssh/id_dsa type -1 >>> debug1: identity file /home/ubuntu/.ssh/id_dsa-cert type -1 >>> debug1: identity file /home/ubuntu/.ssh/id_ecdsa type -1 >>> debug1: identity file /home/ubuntu/.ssh/id_ecdsa-cert type -1 >>> debug1: Remote protocol version 2.0, remote software version >>> OpenSSH_5.9p1 Debian-5ubuntu1 >>> debug1: match: OpenSSH_5.9p1 Debian-5ubuntu1 pat OpenSSH* >>> debug1: Enabling compatibility mode for protocol 2.0 >>> debug1: Local version string SSH-2.0-OpenSSH_5.9p1 Debian-5ubuntu1 >>> debug1: SSH2_MSG_KEXINIT sent >>> debug1: SSH2_MSG_KEXINIT received >>> debug1: kex: server->client aes128-ctr hmac-md5 none >>> debug1: kex: client->server aes128-ctr hmac-md5 none >>> debug1: sending SSH2_MSG_KEX_ECDH_INIT >>> debug1: expecting SSH2_MSG_KEX_ECDH_REPLY >>> debug1: Server host key: ECDSA >>> 7b:8f:6a:ee:ba:e5:0a:c5:04:01:ca:bd:e5:38:69:55 >>> debug1: Host '10.5.5.6' is known and matches the ECDSA host key. >>> debug1: Found key in /home/ubuntu/.ssh/known_hosts:4 >>> debug1: ssh_ecdsa_verify: signature correct >>> debug1: SSH2_MSG_NEWKEYS sent >>> debug1: expecting SSH2_MSG_NEWKEYS >>> debug1: SSH2_MSG_NEWKEYS received >>> debug1: Roaming not allowed by server >>> debug1: SSH2_MSG_SERVICE_REQUEST sent >>> debug1: SSH2_MSG_SERVICE_ACCEPT received >>> debug1: Authentications that can continue: publickey >>> debug1: Next authentication method: publickey >>> debug1: Trying private key: /home/ubuntu/.ssh/id_rsa >>> debug1: Trying private key: /home/ubuntu/.ssh/id_dsa >>> debug1: Trying private key: /home/ubuntu/.ssh/id_ecdsa >>> debug1: No more authentication methods to try. >>> Permission denied (publickey). >>> >>> But I can ssh from to my Cirros VMs. Also I can ssh from Ubuntu VM to >>> Cirros VM. >>> >>> Any Idea? >>> >>> Thanks. >>> >>> ___ >>> 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 > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] using vlan tagged ports in cluster
It is common to loose your network in 3 NIC setup that is why the third NIC card, its ok if you cant ping your public IP directly. But this work around wont hurt either. This work around has been implemented in two nic VLAN method in the same git repo. Regards, Pranav On Fri, Mar 15, 2013 at 10:08 PM, JR wrote: > Rain, I owe you a beer! That did the trick. Thanks. > > JR > > On 3/15/2013 11:32 AM, Rain Li wrote: > > Hi, JR, > > > > You should check your route. Before "ovs-vsctl add-port br-ex p1p1.4", > > you should have the route entry like: > > 192.168.251.0 0.0.0.0 255.255.255.0 U 0 0 0 p1p1.4 > > But after that, since p1p1.4 is plugged in br-ex, you should change the > > above route to go through br-ex, and may also change other (default > > route) to this interface as well, if they originally go through p1p1.4. > > > > Regards, > > Rain > > > > > > On Thu, Mar 14, 2013 at 5:22 AM, JR > <mailto:botem...@gmail.com>> wrote: > > > > Greetings, > > > > I'm setting up openstack on some machines using > > > https://github.com/mseknibilel/OpenStack-Folsom-Install-guide/blob/master/OpenStack_Folsom_Install_Guide_WebVersion.rst > . > > > > I'm using 3 nodes: a controller, network node and compute node. All > the > > network interfaces are VLAN tagged use the same underlying physical > 10G, > > e.g., > > > > controller: p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management > > net: 10.10.10.*/24) > > network:p1p1.4 (public net: 192.168.251.*/24), p1p1.5 (management > > net: 10.10.10.*/24), p1p1.6 (vm net: 10.20.20.*/24) > > > > # I haven't gotten to the compute node yet but it should be > > compute: p1p1.5 (management net: 10.10.10.*/24), p1p1.6 (vm net: > > 10.20.20.*/24) > > > > When I bring up my openvswitch bridges on the network node, I can not > > longer get out to the public net (see *MORE* below). > > > > I'm running ubuntu 12.10 and have run apt-get dist-upgrade. The 10G > > nics are intel 82599EB. ubuntu seems a bit flakey; initially I'd > > created /etc/udev/rules/70-persistent-net.rules to map p1p1 to eth2, > > however, the config was ignored and eth2 wound up being a 1G NIC. > > > > Is it not allowed to use VLAN interfaces for my networks? > > > > If I remove, say, the br-ex bridge I can get out again: > > root@nebula03:~# ping 192.168.251.1 > > PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data. > > ^C > > --- 192.168.251.1 ping statistics --- > > 1 packets transmitted, 0 received, 100% packet loss, time 0ms > > > > root@nebula03:~# ovs-vsctl del-port p1p1.4 > > root@nebula03:~# ovs-vsctl del-br br-ex > > root@nebula03:~# ping 192.168.251.1 > > PING 192.168.251.1 (192.168.251.1) 56(84) bytes of data. > > 64 bytes from 192.168.251.1 <http://192.168.251.1>: icmp_req=1 > > ttl=64 time=0.650 ms > > ^C > > --- 192.168.251.1 ping statistics --- > > 1 packets transmitted, 1 received, 0% packet loss, time 0ms > > rtt min/avg/max/mdev = 0.650/0.650/0.650/0.000 ms > > root@nebula03:~# > > > > > > Thanks for any help, > > JR > > > > > > *MORE* > > > > root@nebula03:~# ovs-vsctl show > > 1bdf2f73-1a5d-4893-b745-7501557acaea > > Bridge br-int > > Port br-int > > Interface br-int > > type: internal > > Bridge br-ex > > Port br-ex > > Interface br-ex > > type: internal > > Port "p1p1.4" > > Interface "p1p1.4" > > Bridge br-vm > > Port br-vm > > Interface br-vm > > type: internal > > Port "p1p1.6" > > Interface "p1p1.6" > > ovs_version: "1.4.3" > > root@nebula03:~# ifconfig p1.4 > > p1.4: error fetching interface information: Device not found > > root@nebula03:~# ifconfig p1p1.4 > > p1p1.4Link encap:Ethernet HWaddr 90:e2:ba:2c:8a:08 > > inet addr:192.168.251.92 Bcast:192.168.251.255 > > Mask:255.255.255.0 > > inet6 addr: fe80::92e2:baff:fe2c:8a08/64 Scope:Link > > UP BROADCAST RUNNING MULTICAST
Re: [Openstack] Call for help on Grizzly documentation
Hi, Even I'm interested. Ill be working on this for sure. Regards, Pranav On Fri, Mar 15, 2013 at 7:42 PM, Michael Basnight wrote: > Of course... I spaced. I'd love to review the doc for this. > > Sent from my digital shackles > > On Mar 15, 2013, at 5:47 AM, "Anne Gentle" wrote: > > Yes, go ahead. Use the guidelines we have for Doc bug triage. [1] > > Hey Bas, a DocImpact would have been ideal on that commit message so we > could already have a doc bug logged. [2] > > Thanks, > Anne > > 1. > https://wiki.openstack.org/wiki/Documentation/HowTo#Doc_Bug_Triaging_Guidelines > 2. > https://wiki.openstack.org/wiki/Documentation/HowTo#Using_the_DocImpact_Flag_in_a_Commit_Message > > > > > On Fri, Mar 15, 2013 at 6:11 AM, Jérôme Gallard wrote: > >> Hi Anne, >> >> I'm a newbie in the "documentation area" but, I would like to give an >> help. >> >> I haven't found any documentations (or open bug) regarding the cinder >> multi-backend feature ( >> https://wiki.openstack.org/wiki/Cinder-multi-backend -- >> https://review.openstack.org/#/c/21815/ ). >> >> Do you know if this documentation is planed to be written? >> Can I open a bug for this? >> >> Thanks a lot, >> Jérôme >> >> On Tue, Mar 12, 2013 at 3:27 PM, Anne Gentle wrote: >> > Hi all, >> > You all did great with DocImpact, but now that we're less than a month >> from >> > release, the tiny doc team is facing a long list of doc bugs that won't >> be >> > done by April 4th, many generated by DocImpact flags. >> > >> > We typically do a "release" of the docs about a month after the actual >> > release date, to ensure packages are available and to try to get our >> doc bug >> > backlog to a manageable level. >> > >> > As you can see from our backlog for operator docs in openstack-manuals >> [1] >> > and API docs in api-site [2], there are over 50 confirmed doc bugs for >> > Grizzly operator and admin docs and less than 20 for API docs. With >> those >> > numbers we need all the help we can get. >> > >> > Please dive in, the patch process is just like code and fully >> documented. >> > [3] We're on IRC in #openstack-doc and can answer any questions you >> have as >> > you go. >> > >> > Thanks! >> > Anne, Tom, Diane, Laura, Emilien, Daisy, and all the other doc peeps >> > >> > 1. https://launchpad.net/openstack-manuals/+milestone/grizzly >> > 2. https://launchpad.net/openstack-api-site/+milestone/grizzly >> > 3. http://wiki.openstack.org/Documentation/HowTo >> > >> > ___ >> > 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 > > ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Announcing Elastic Hadoop on OpenStack project
This sounds awesome. Regards, Pranav On Thu, Mar 14, 2013 at 3:37 PM, Razique Mahroua wrote: > Amazing! > will follow that :) > > *Razique Mahroua** - **Nuage & Co* > razique.mahr...@gmail.com > Tel : +33 9 72 37 94 15 > > > Le 14 mars 2013 à 00:24, JuanFra Rodriguez Cardoso < > juanfra.rodriguez.card...@gmail.com> a écrit : > > Great fusion of strong IT buzzwords!! > > JuanFra > > > 2013/3/13 Sergey Lukjanov > >> Hello community, >> >> At Mirantis within our customer and partner base we see growing demand to >> deploy and run Hadoop clusters on OpenStack cloud and manage them via an >> OpenStack API. >> >> The main goal of this initiative, codenamed EHO (Elastic Hadoop on >> OpenStack), is to create native OpenStack component for fast provisioning >> and operating Hadoop clusters on demand. >> >> The key features are as follows: >> * Open source; >> * Native for OpenStack; >> * Support for different Hadoop distributions; >> * Fast clusters provisioning (e.g. for deploying Dev or QA environments); >> * Elastic MapReduce job execution similar to Amazon EMR >> >> We would appreciate all for your feedback and comments. >> >> Here are the key links: >> * Project blueprint: https://wiki.openstack.org/wiki/EHO | >> http://eho.mirantis.com/index.html >> * Roadmap: https://wiki.openstack.org/wiki/EHO/Roadmap | >> http://eho.mirantis.com/roadmap.html >> * API draft: http://eho.mirantis.com/restapi/v02.html >> * Sources: https://github.com/mirantis/eho >> * Launchpad project: https://launchpad.net/eho >> * Quickstart: http://eho.mirantis.com/quickstart.html >> * Horizon pages screenshots: http://eho.mirantis.com/horizon/index.html >> >> If you would like to ask some questions or make proposals, feel free to >> reply to this message in OpenStack mailing list or reach us on #eho irc >> channel at freenode. Typically somebody from our team will be online at irc >> from 6:00 to 20:00 UTC. You can also contact EHO community directly by >> email mailto:e...@lists.launchpad.net (please, note that your email >> address should be registered in launchpad, otherwise your mail will be >> ignored by mailing system). >> >> We're going to hold public weekly meetings on Thursday at 18:00 UTC on >> our irc channel. >> >> Also we would greatly appreciate if you consider contributing to EHO >> project. For both docs and code, simply send us pull requests via github. >> >> -- >> Sergey Lukjanov >> Mirantis Inc. >> >> ___ >> 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 > > > > ___ > 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
Re: [Openstack] Google Summer of Code
I did a mistake in the link follow this instead - https://github.com/cloud-rack Regards, Pranav On Thu, Mar 14, 2013 at 9:34 AM, Pranav wrote: > Hi, > I don't know weather I'm qualified for being a mentor (ill be graduating > this summer). But I have my project which Ill be officially done with this > summer (Before Google summer code starts) and would love to know if its a > good idea and if I could take it further and make it more professional. > This can be a good start-up idea for Google Summer Code. > > Here is the existing repository. I plan to implement a unique system for > backup, storage using GIT(PaaS and IaaS) and OpenStack(IaaS). > https://github.com/organizations/cloud-rack > Note: This project is work in progress and may have some mistakes. > Regards, > Pranav > > > On Thu, Mar 14, 2013 at 9:20 AM, Anne Gentle wrote: > >> Hi Pranav, >> >> What are you specifically interested in? >> >> On the mentoring and project side, we need an ideas page better than what >> we put together last year: https://wiki.openstack.org/wiki/GSoC2012/Ideas. >> It didn't have enough details for Google to accept our application. >> >> Thanks, >> Anne >> >> >> On Wed, Mar 13, 2013 at 4:02 PM, Pranav wrote: >> >>> Hi, >>> I'm interested. >>> Regards, >>> Pranav >>> >>> >>> On Wed, Mar 13, 2013 at 11:48 PM, Anne Gentle wrote: >>> >>>> Hi all - >>>> >>>> The deadline for projects to apply for Google Summer of Code is March >>>> 28th. Who is interested in making our Ideas page and mentoring? I'm happy >>>> to help in an administrative role but need mentors and project ideas. >>>> >>>> Thanks, >>>> Anne >>>> >>>> ___ >>>> 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
Re: [Openstack] Google Summer of Code
Hi, I don't know weather I'm qualified for being a mentor (ill be graduating this summer). But I have my project which Ill be officially done with this summer (Before Google summer code starts) and would love to know if its a good idea and if I could take it further and make it more professional. This can be a good start-up idea for Google Summer Code. Here is the existing repository. I plan to implement a unique system for backup, storage using GIT(PaaS and IaaS) and OpenStack(IaaS). https://github.com/organizations/cloud-rack Note: This project is work in progress and may have some mistakes. Regards, Pranav On Thu, Mar 14, 2013 at 9:20 AM, Anne Gentle wrote: > Hi Pranav, > > What are you specifically interested in? > > On the mentoring and project side, we need an ideas page better than what > we put together last year: https://wiki.openstack.org/wiki/GSoC2012/Ideas. > It didn't have enough details for Google to accept our application. > > Thanks, > Anne > > > On Wed, Mar 13, 2013 at 4:02 PM, Pranav wrote: > >> Hi, >> I'm interested. >> Regards, >> Pranav >> >> >> On Wed, Mar 13, 2013 at 11:48 PM, Anne Gentle wrote: >> >>> Hi all - >>> >>> The deadline for projects to apply for Google Summer of Code is March >>> 28th. Who is interested in making our Ideas page and mentoring? I'm happy >>> to help in an administrative role but need mentors and project ideas. >>> >>> Thanks, >>> Anne >>> >>> ___ >>> 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
Re: [Openstack] Google Summer of Code
Hi, I'm interested. Regards, Pranav On Wed, Mar 13, 2013 at 11:48 PM, Anne Gentle wrote: > Hi all - > > The deadline for projects to apply for Google Summer of Code is March > 28th. Who is interested in making our Ideas page and mentoring? I'm happy > to help in an administrative role but need mentors and project ideas. > > Thanks, > Anne > > ___ > 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
Re: [Openstack] Problem starting a VM
I believe that you have broken your configuration files. Please do make sure that your nova confi files are proper. I had similar issue where in i had to change the libvirt option to QEMU because some KVM issue and the images started spawning. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
