[Openstack] Error in spawning second VM

2013-04-23 Thread Nikhil Mittal
Hello, I installed openstack (package versions given below) on Ubuntu 12.04.2 LTS (x86 64 bit). I installed first VM image successfully. When I try to install (using "nova boot..") the same or a different VM image as a second image, I get following error right after a few seconds of image building:

Re: [Openstack] Grizzly fails on ubuntu server 13.04

2013-05-09 Thread Nikhil Mittal
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.open

Re: [Openstack] Grizzly installation successful but VM is not accessible over network or from the host machine

2013-05-10 Thread Nikhil Mittal
logs > > dhcp-agent.log > l3-agent.log > openvswitch-agent.log > ovs-cleanup.log > server.log > > > > > > Thank You, > > Regards > Kamarul > > Follow me at rehdat.blogspot.com > > > On Fri, May 10, 2013 at 1:29 PM, Nikhil Mittal wrote:

Re: [Openstack] Grizzly fails on ubuntu server 13.04

2013-05-10 Thread Nikhil Mittal
g 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 t

[Openstack] [OPENSTACK] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)

2013-05-14 Thread Nikhil Mittal
Hello, I recently installed Grizzly (single-node) on Ubuntu 13.04 on x86 64 bit having two physical NICs. I posted about the networking issues that I was facing after the installation in an earlier post. Well, while I was debugging the networking issue, I came across a more serious issue -- my host

Re: [Openstack] [OPENSTACK] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)

2013-05-14 Thread Nikhil Mittal
- > Wangpan > ---------- > *发件人:*Nikhil Mittal > *发送时间:*2013-05-14 15:59 > *主题:*[Openstack] [OPENSTACK] VMs don't start on host machine reboot > (Grizzly over Ubuntu 13.04) > *收件人:*"openstack" > *抄送:* > > Hello, > I recently install

Re: [Openstack] [OPENSTACK] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)

2013-05-14 Thread Nikhil Mittal
x27; > command say? > > Zhi Yan > > On Tue, May 14, 2013 at 5:43 PM, Nikhil Mittal > wrote: > > Wang, > > I guess you are referring to to the instance specific XML file under > > /etc/libvirt/qemu. It has the following section having '

Re: [Openstack] [OPENSTACK] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)

2013-05-15 Thread Nikhil Mittal
Any suggestions on debugging this issue ? As I mentioned below, the command qemu-img shows information where the file format is qcow2 whereas the image used in this instance is ISO. Is this a bug or am I missing something ? Thanks, -Nikhil On Tue, May 14, 2013 at 3:30 PM, Nikhil Mittal wrote

Re: [Openstack] [OPENSTACK] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)

2013-05-15 Thread Nikhil Mittal
/var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96 > is in normal? > > On Wed, May 15, 2013 at 3:16 PM, Nikhil Mittal > wrote: > > Any suggestions on debugging this issue ? As I mentioned below, the > command > > qemu-img shows information where the file format is qcow2 whereas the &g

Re: [Openstack] [OPENSTACK] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)

2013-05-15 Thread Nikhil Mittal
needs to be built keeping certain things in mind. FYI, the ISO image that I am using is an in-house custom built image which we have been using successfully across multiple platforms as well as on Openstack Essex release. On Wed, May 15, 2013 at 2:02 PM, Nikhil Mittal wrote: > Output of command &qu

Re: [Openstack] [OPENSTACK] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)

2013-05-16 Thread Nikhil Mittal
sr/bin/kvm == -Nikhil On Wed, May 15, 2013 at 3:34 PM, Nikhil Mittal wrote: > Some additional info: I tried the host machine reboot after installing a > qcow2 format ubuntu image as VM. And it works fine i.e. after power-cycling > the host node, the VM is able to boot again. I susp

[Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Nikhil Mittal
Hi, I am able to successfully spawn VMs on my single-node Grizzly setup on Ubuntu 13.04. I can ping from one VM to another VM. But i can't ping the internal router interface which resides on the same subnet as the VMs. I have not yet configured external network and gateway this router. NOTE: I can'

Re: [Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Nikhil Mittal
nfig for the agent and eventually > /var/log/quantum/l3-agent.log or what the log file is called again ? > > Endre > > > 2013/5/23 Nikhil Mittal > >> Hi, >> I am able to successfully spawn VMs on my single-node Grizzly setup on >> Ubuntu 13.04. I can ping

Re: [Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Nikhil Mittal
group is > now blocking the traffic. > If the interface does not show up this mean the l3 agent has either > crashed or is tracebacking. The logs, as suggested by Endre, might clarify > what is going on. > > Salvatore > > >> >> >> >> >

Re: [Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Nikhil Mittal
= -Nikhil On Thu, May 23, 2013 at 9:01 PM, Nikhil Mittal wrote: > Hi, > The command "ip netns exec qrouter-fd907599-60a2-4efa-9c7e-65fb8c8b0f77 ip > addr" shows: > 1: lo: mtu 65536 qdisc noop state DOWN > link/loopback 00:00:00:00:00:00 brd 00:00:00

Re: [Openstack] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-24 Thread Nikhil Mittal
Any suggestions folks ? I have tried even deleting the tenant, network, subnet, router and then recreating. Still the same status. On Fri, May 24, 2013 at 11:13 AM, Nikhil Mittal wrote: > I also noticed one more thing: everytime i run the command below, it shows > me only dhcp elated en

Re: [Openstack] Grizzly all-in-one error

2013-05-29 Thread Nikhil Mittal
This error would occur when the Keystone has not been properly configured with the authentication details for all the services. I faced this issue as well and it was fixed by correcting the DB and the configuration files. On Wed, May 29, 2013 at 4:32 PM, Rajesh Upadhayay wrote: > Hi, > > **

[Openstack] [OPENSTACK] Grizzly (three node setup) Error "Agent with agent_type=DHCP agent and host=network could not be found"

2013-06-07 Thread Nikhil Mittal
Hello I setup a three-node Grizzly setup using Ubuntu 12.04. In the /var/log/quantum/server.log (on controller node) i get the below error whenever i run command "quantum agent-list". Actually this command returns nothing (just a blank line) on either controller or network node that I run this com