from:"Nikhil Mittal"

[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:

---
root@ncs:/var/log/nova# dpkg -s nova-network
Package: nova-network
Status: install ok installed
Priority: extra
Section: net
Installed-Size: 114
Maintainer: Ubuntu Developers 
Architecture: all
Source: nova
Version: 2012.1.3+stable-20120827-4d2a4afe-0ubuntu1.4


root@ncs:/var/log/nova# dpkg -s nova-compute
Package: nova-compute
Status: install ok installed
Priority: extra
Section: net
Installed-Size: 115
Maintainer: Ubuntu Developers 
Architecture: all
Source: nova
Version: 2012.1.3+stable-20120827-4d2a4afe-0ubuntu1.4

root@ncs:/var/log/nova# dpkg -s nova-api
Package: nova-api
Status: install ok installed
Priority: extra
Section: net
Installed-Size: 73
Maintainer: Ubuntu Developers 
Architecture: all
Source: nova
Version: 2012.1.3+stable-20120827-4d2a4afe-0ubuntu1.4
---


ERROR (nova-compute.log):
==
2013-04-22 19:19:41 ERROR nova.compute.manager
[req-ae333ba1-5f41-4ae5-9266-340f7514a034 9f4b006a83b24e0fb6a5cfd2c08d4247
03ed9019dcb34cd8b2ed90905a2ed3be] [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6] Instance failed to spawn
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6] Traceback (most recent call last):
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6]   File
"/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 617, in
_spawn
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6]
self._legacy_nw_info(network_info), block_device_info)
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6]   File
"/usr/lib/python2.7/dist-packages/nova/exception.py", line 114, in wrapped
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6] return f(*args, **kw)
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6]   File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line
952, in spawn
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6] self._create_new_domain(xml)
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6]   File
"/usr/lib/python2.7/dist-packages/nova/virt/libvirt/connection.py", line
1618, in _create_new_domain
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6]
domain.createWithFlags(launch_flags)
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6]   File
"/usr/lib/python2.7/dist-packages/libvirt.py", line 581, in createWithFlags
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6] if ret == -1: raise libvirtError
('virDomainCreateWithFlags() failed', dom=self)
2013-04-22 19:19:41 TRACE nova.compute.manager [instance:
e3e106d5-ca65-4678-8717-17a1810cc3a6] libvirtError: Network filter not
found: Could not find filter 'nova-instance-instance-0006-fa163e60cecb'
=

Thanks,
Nikhil
___
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

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.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
> 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 installation successful but VM is not accessible over network or from the host machine

2013-05-10 Thread Nikhil Mittal

Kamarul,
The status shown on the dashboard is confusing. Under Router Detail
section, it shows Status as Active. But under Interfaces it shows as DOWN
but Admin status as UP (refer the cut-paste below).
Also i see following error message in /var/log/quantum/dhcp-agent.log:

+++
Stderr: "sudo: no tty present and no askpass program specified\nSorry, user
quantum is not allowed to execute
..
 ERROR [quantum.agent.dhcp_agent] Unable to sync network state.
+++

==
Router Overview: router_osk_1
Namerouter_osk_1IDa04a3393-f292-4943-9e13-4a5733921bb6StatusACTIVE
--
  Interfaces
Add 
Interface<http://10.78.104.111/horizon/project/routers/a04a3393-f292-4943-9e13-4a5733921bb6/addinterface>
  Name Fixed IPs Status Type Admin State Actions
(449eac7f)<http://10.78.104.111/horizon/project/networks/ports/449eac7f-e582-4816-b099-93f5dd49c15f/detail>

   - 10.78.99.81

DOWNInternal InterfaceUP
   Displaying 1 item
=
Thanks,
Nikhil



On Fri, May 10, 2013 at 11:59 AM, Kamarul  wrote:

> Nikhil,
>
> Configuring networking (quantum) is a common problem as such a vm cannot
> ping to other host outside of openstack setup.
> For a start, you may look into logs (/var/log/quantum), that will give you
> clue.
>
> What is your router's interfaces status, up or down?
>
> Go through below 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:
>
>> Hello,
>> I followed the guide on installing Grizzly on single-node setup. I was
>> able to install my own customized VM successfully (though after resolving a
>> few glitches) but the VM is not accessible on the same host or from another
>> machine. The IP address assigned to the VM does not respond to pings, etc.
>> though the instance is very much alive (can access via Dashboard console).
>> Network topology shows Router and the VM being assigned an IP.
>>
>> The commands 'ifconfig' does not show any of the bridges, nor 'route'
>> shows any additional routes created.
>> I have attached the screenshot of the network topology (from Dashboard).
>>
>> NOTE:
>> 1. I am using Ubuntu 13.04 on x86 64 bit Intel platform with two NICs.
>> Both NICs have addresses which are accessible within the enterprise network.
>> 2. I have added required security group to enable TCP and ICMP traffic.
>>
>> Thanks,
>> Nikhil
>> ___
>> 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

2013-05-10 Thread Nikhil Mittal

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

[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 machine got rebooted (power-cycle) and on reboot I
see that my two VMs are shown in "shut-off" Status and "shut-down" Power
state in the Dashboard GUI. The options available to me are only "soft
reboot", "hard reboot", "terminate instance", "Disassociate Floating IP"
and "Edit Instance". I did first "soft reboot" and the console shows "No
bootable device". Then i tried "Hard reboot" and again the same message "No
bootable device".
I checked that all services are running fine and there are no error
messages in the logs for nova, quantum, etc.

I followed installation instructions based on the following link:
https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_SingleNode/OpenStack_Grizzly_Install_Guide.rst

Thanks,
Nikhil
___
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] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)

2013-05-14 Thread Nikhil Mittal

Wang,
I guess you are referring to to the instance specific XML file under
/etc/libvirt/qemu. It has the following section having 'vda':

===

/usr/bin/kvm

  
  
  
  


===
Can you specify what exactly I need to change ?
Thanks,
Nikhil


On Tue, May 14, 2013 at 1:45 PM, Wangpan  wrote:

> **
> seems like the roog disk is not a bootable device, you may need to check
> the vda/xvda device in libvirt XML config file is bootable or not.
>
> 2013-05-14
>  --
>  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 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 machine got rebooted (power-cycle) and on reboot I
> see that my two VMs are shown in "shut-off" Status and "shut-down" Power
> state in the Dashboard GUI. The options available to me are only "soft
> reboot", "hard reboot", "terminate instance", "Disassociate Floating IP"
> and "Edit Instance". I did first "soft reboot" and the console shows "No
> bootable device". Then i tried "Hard reboot" and again the same message "No
> bootable device".
> I checked that all services are running fine and there are no error
> messages in the logs for nova, quantum, etc.
>
> I followed installation instructions based on the following link:
>
> https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_SingleNode/OpenStack_Grizzly_Install_Guide.rst
>
> Thanks,
> Nikhil
>
>
___
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] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)

2013-05-14 Thread Nikhil Mittal

Here it is:
===
image: /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk
file format: qcow2
virtual size: 160G (171798691840 bytes)
disk size: 200K
cluster_size: 65536
backing file:
/var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96
===
BTW, I launched the instance with ISO image format NOT qcow2. Don't know
why it is showing the format as qcow2.

On Tue, May 14, 2013 at 3:23 PM, lzy@gmail.com wrote:

> Nikhil
>
> What  the 'qemu-img info
> /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'
> 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 'vda':
> >
> > ===
> > 
> > /usr/bin/kvm
> > 
> >   
> >>
> file='/var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'/>
> >   
> >> function='0x0'/>
> > 
> > 
> > ===
> > Can you specify what exactly I need to change ?
> > Thanks,
> > Nikhil
> >
> >
> >
> > On Tue, May 14, 2013 at 1:45 PM, Wangpan 
> wrote:
> >>
> >> seems like the roog disk is not a bootable device, you may need to check
> >> the vda/xvda device in libvirt XML config file is bootable or not.
> >>
> >> 2013-05-14
> >> 
> >> 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 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 machine got rebooted (power-cycle) and on
> reboot I
> >> see that my two VMs are shown in "shut-off" Status and "shut-down" Power
> >> state in the Dashboard GUI. The options available to me are only "soft
> >> reboot", "hard reboot", "terminate instance", "Disassociate Floating
> IP" and
> >> "Edit Instance". I did first "soft reboot" and the console shows "No
> >> bootable device". Then i tried "Hard reboot" and again the same message
> "No
> >> bootable device".
> >> I checked that all services are running fine and there are no error
> >> messages in the logs for nova, quantum, etc.
> >>
> >> I followed installation instructions based on the following link:
> >>
> >>
> https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_SingleNode/OpenStack_Grizzly_Install_Guide.rst
> >>
> >> Thanks,
> >> Nikhil
> >>
> >
> >
> > ___
> > 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] 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:

> Here it is:
> ===
> image: /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk
> file format: qcow2
> virtual size: 160G (171798691840 bytes)
> disk size: 200K
> cluster_size: 65536
> backing file:
> /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96
> ===
> BTW, I launched the instance with ISO image format NOT qcow2. Don't know
> why it is showing the format as qcow2.
>
>
> On Tue, May 14, 2013 at 3:23 PM, lzy@gmail.com wrote:
>
>> Nikhil
>>
>> What  the 'qemu-img info
>> /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'
>> 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 'vda':
>> >
>> > ===
>> > 
>> > /usr/bin/kvm
>> > 
>> >   
>> >   > >
>> file='/var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'/>
>> >   
>> >   > > function='0x0'/>
>> > 
>> > 
>> > ===
>> > Can you specify what exactly I need to change ?
>> > Thanks,
>> > Nikhil
>> >
>> >
>> >
>> > On Tue, May 14, 2013 at 1:45 PM, Wangpan 
>> wrote:
>> >>
>> >> seems like the roog disk is not a bootable device, you may need to
>> check
>> >> the vda/xvda device in libvirt XML config file is bootable or not.
>> >>
>> >> 2013-05-14
>> >> 
>> >> 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 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 machine got rebooted (power-cycle) and on
>> reboot I
>> >> see that my two VMs are shown in "shut-off" Status and "shut-down"
>> Power
>> >> state in the Dashboard GUI. The options available to me are only "soft
>> >> reboot", "hard reboot", "terminate instance", "Disassociate Floating
>> IP" and
>> >> "Edit Instance". I did first "soft reboot" and the console shows "No
>> >> bootable device". Then i tried "Hard reboot" and again the same
>> message "No
>> >> bootable device".
>> >> I checked that all services are running fine and there are no error
>> >> messages in the logs for nova, quantum, etc.
>> >>
>> >> I followed installation instructions based on the following link:
>> >>
>> >>
>> https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_SingleNode/OpenStack_Grizzly_Install_Guide.rst
>> >>
>> >> Thanks,
>> >> Nikhil
>> >>
>> >
>> >
>> > ___
>> > 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] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)

2013-05-15 Thread Nikhil Mittal

Output of command "ls -l
/var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96"

-rw-r--r-- 1 nova kvm 6285240320 May 15 06:21
/var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96

Seems normal to me...

I added the image in glance using command:
glance add name="CCM_9001" is_public=true container_format=bare
disk_format=iso < *image_file*

The same commands have been working fine in Essex release.

On Wed, May 15, 2013 at 12:51 PM, lzy@gmail.com wrote:

> Can you check the backing file:
> /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
> 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:
> >>
> >> Here it is:
> >> ===
> >> image: /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk
> >> file format: qcow2
> >> virtual size: 160G (171798691840 bytes)
> >> disk size: 200K
> >> cluster_size: 65536
> >> backing file:
> >> /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96
> >> ===
> >> BTW, I launched the instance with ISO image format NOT qcow2. Don't know
> >> why it is showing the format as qcow2.
> >>
> >>
> >> On Tue, May 14, 2013 at 3:23 PM, lzy@gmail.com 
> >> wrote:
> >>>
> >>> Nikhil
> >>>
> >>> What  the 'qemu-img info
> >>> /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'
> >>> 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 'vda':
> >>> >
> >>> > ===
> >>> > 
> >>> > /usr/bin/kvm
> >>> > 
> >>> >   
> >>> >>>> >
> >>> >
> file='/var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'/>
> >>> >   
> >>> >>>> > function='0x0'/>
> >>> > 
> >>> > 
> >>> > ===
> >>> > Can you specify what exactly I need to change ?
> >>> > Thanks,
> >>> > Nikhil
> >>> >
> >>> >
> >>> >
> >>> > On Tue, May 14, 2013 at 1:45 PM, Wangpan  >
> >>> > wrote:
> >>> >>
> >>> >> seems like the roog disk is not a bootable device, you may need to
> >>> >> check
> >>> >> the vda/xvda device in libvirt XML config file is bootable or not.
> >>> >>
> >>> >> 2013-05-14
> >>> >> 
> >>> >> 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 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 machine got rebooted (power-cycle) and on
> >>> >> reboot I
> >>> >> see that my two VMs are shown in "shut-off" Status and "shut-down"
> >>> >> Power
> >>> >> state in the Dashboard GUI. The options available to me are only
> "soft
> >>> >> reboot", "hard reboot", "terminate instance", "Disassociate Floating
> >>> >> IP" and
> >>> >> "Edit Instance". I did first "soft reboot" and the console shows "No
> >>> >> bootable device". Then i tried "Hard reboot" and again the same
> >>> >> message "No
> >>> >> bootable device".
> >>> >> I checked that all services are running fine and there are no error
> >>> >> messages in the logs for nova, quantum, etc.
> >>> >>
> >>> >> I followed installation instructions based on the following link:
> >>> >>
> >>> >>
> >>> >>
> https://github.com/mseknibilel/OpenStack-Grizzly-Install-Guide/blob/OVS_SingleNode/OpenStack_Grizzly_Install_Guide.rst
> >>> >>
> >>> >> Thanks,
> >>> >> Nikhil
> >>> >>
> >>> >
> >>> >
> >>> > ___
> >>> > 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] VMs don't start on host machine reboot (Grizzly over Ubuntu 13.04)

2013-05-15 Thread Nikhil Mittal

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 suspect either there is bug
with Grizzly release in handling certain type of ISO files or the ISO 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 "ls -l
> /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96"
>
> -rw-r--r-- 1 nova kvm 6285240320 May 15 06:21
> /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96
>
> Seems normal to me...
>
> I added the image in glance using command:
> glance add name="CCM_9001" is_public=true container_format=bare
> disk_format=iso < *image_file*
>
> The same commands have been working fine in Essex release.
>
>
> On Wed, May 15, 2013 at 12:51 PM, lzy@gmail.com wrote:
>
>> Can you check the backing file:
>> /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
>> 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:
>> >>
>> >> Here it is:
>> >> ===
>> >> image:
>> /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk
>> >> file format: qcow2
>> >> virtual size: 160G (171798691840 bytes)
>> >> disk size: 200K
>> >> cluster_size: 65536
>> >> backing file:
>> >> /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96
>> >> ===
>> >> BTW, I launched the instance with ISO image format NOT qcow2. Don't
>> know
>> >> why it is showing the format as qcow2.
>> >>
>> >>
>> >> On Tue, May 14, 2013 at 3:23 PM, lzy@gmail.com 
>> >> wrote:
>> >>>
>> >>> Nikhil
>> >>>
>> >>> What  the 'qemu-img info
>> >>> /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'
>> >>> command say?
>> >>>
>> >>> Zhi Yan
>> >>>
>> >>> On Tue, May 14, 2013 at 5:43 PM, Nikhil Mittal <
>> mittalnik...@gmail.com>
>> >>> wrote:
>> >>> > Wang,
>> >>> > I guess you are referring to to the instance specific XML file under
>> >>> > /etc/libvirt/qemu. It has the following section having 'vda':
>> >>> >
>> >>> > ===
>> >>> > 
>> >>> > /usr/bin/kvm
>> >>> > 
>> >>> >   
>> >>> >   > >>> >
>> >>> >
>> file='/var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'/>
>> >>> >   
>> >>> >   > >>> > function='0x0'/>
>> >>> > 
>> >>> > 
>> >>> > ===
>> >>> > Can you specify what exactly I need to change ?
>> >>> > Thanks,
>> >>> > Nikhil
>> >>> >
>> >>> >
>> >>> >
>> >>> > On Tue, May 14, 2013 at 1:45 PM, Wangpan <
>> hzwang...@corp.netease.com>
>> >>> > wrote:
>> >>> >>
>> >>> >> seems like the roog disk is not a bootable device, you may need to
>> >>> >> check
>> >>> >> the vda/xvda device in libvirt XML config file is bootable or not.
>> >>> >>
>> >>> >> 2013-05-14
>> >>> >> 
>> >>> >> Wangpan
>> >>> >> 
>> >>> >> 发件人：Nikhil Mittal
>> >>> >> 发送时间：2013-05-14 15:59
>> >>> >> 主题：[Openstack] [OP

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

2013-05-16 Thread Nikhil Mittal

An update:
I used the glance image-create command to add the image to the glance DB.
If I use this image for creating VM, then the problem of VM not booting on
host machine node is gone away. I am still puzzled as to what is the
difference there it is vs. the original instance xml file. are there any
other files that I should be comparing with ?

Output of command "qemu-img info
/var/lib/nova/instances/6d6b2f12-0f59-4b94-adc2-b527d8bf4d94/disk" ::
+++
image: /var/lib/nova/instances/6d6b2f12-0f59-4b94-adc2-b527d8bf4d94/disk
file format: qcow2
virtual size: 160G (171798691840 bytes)
disk size: 200K
cluster_size: 65536
backing file:
/var/lib/nova/instances/_base/f0e93d9c7faf165914420bff74264d92be2bd84a
root@osk-team:/etc/libvirt/qemu# qemu-img info
/var/lib/nova/instances/6d6b2f12-0f59-4b94-adc2-b527d8bf4d94/disk.local
image:
/var/lib/nova/instances/6d6b2f12-0f59-4b94-adc2-b527d8bf4d94/disk.local
file format: qcow2
virtual size: 160G (171798691840 bytes)
disk size: 32G
cluster_size: 65536
backing file: /var/lib/nova/instances/_base/ephemeral_160_default
+++


The instance specific section in file
/etc/libvirt/qemu/instance-001c.xml is :


  
/usr/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 suspect either there is bug
> with Grizzly release in handling certain type of ISO files or the ISO 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 "ls -l
>> /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96"
>>
>> -rw-r--r-- 1 nova kvm 6285240320 May 15 06:21
>> /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96
>>
>> Seems normal to me...
>>
>> I added the image in glance using command:
>> glance add name="CCM_9001" is_public=true container_format=bare
>> disk_format=iso < *image_file*
>>
>> The same commands have been working fine in Essex release.
>>
>>
>> On Wed, May 15, 2013 at 12:51 PM, lzy@gmail.com wrote:
>>
>>> Can you check the backing file:
>>> /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
>>> 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:
>>> >>
>>> >> Here it is:
>>> >> ===
>>> >> image:
>>> /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk
>>> >> file format: qcow2
>>> >> virtual size: 160G (171798691840 bytes)
>>> >> disk size: 200K
>>> >> cluster_size: 65536
>>> >> backing file:
>>> >> /var/lib/nova/instances/_base/6a2ba9ce1da1fbdc28a3da86332cb65193a2bf96
>>> >> ===
>>> >> BTW, I launched the instance with ISO image format NOT qcow2. Don't
>>> know
>>> >> why it is showing the format as qcow2.
>>> >>
>>> >>
>>> >> On Tue, May 14, 2013 at 3:23 PM, lzy@gmail.com >> >
>>> >> wrote:
>>> >>>
>>> >>> Nikhil
>>> >>>
>>> >>> What  the 'qemu-img info
>>> >>> /var/lib/nova/instances/a562a6c9-9253-4f22-8076-344e855f713d/disk'
>>> >>> command say?
>>> >>>
>>> >>> Zhi Yan
>>> >>>
>>> >>> On Tue, May 14, 2013 at 5:43 PM, Nikhil Mittal <
>>> mittalnik...@gmail.com>
>

[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't ping to VMs from the host machine which I believe is because of
router not configured with external interface.
Any suggestions ?
Thanks,
Nikhil

Below is the output of useful commands:

===
root@osk-team:~# quantum port-list
+--+--+---++
| id   | name | mac_address   |
fixed_ips
|
+--+--+---++
| 53d63be8-967c-439c-8ffa-53ef1f7f3d37 |  | fa:16:3e:09:99:b9 |
{"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
"10.78.99.84"} |
| 565eb936-fb89-42a9-9482-0f089907c35a |  | fa:16:3e:96:78:92 |
{"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
"10.78.99.87"} |
| 6f01314f-6f47-4884-b812-1d66fae9ca3e |  | fa:16:3e:b6:c6:fe |
{"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
"10.78.99.83"} |
| 7894091c-274a-48dd-8348-b3fd449b6705 |  | fa:16:3e:bb:69:9e |
{"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
"10.78.99.85"} |
| 9c99fe76-4d74-44de-a2f5-3f3dc555c3d8 |  | fa:16:3e:db:f6:6f |
{"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
"10.78.99.86"} |
| badec4e8-fa4f-47e3-a7a2-123d84d03337 |  | fa:16:3e:79:01:50 |
{"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
"10.78.99.82"} |
| cfb7d5ba-3603-4448-9140-8c1d10ca2b2f |  | fa:16:3e:a2:db:c4 |
{"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
"10.78.99.81"} |
+--+--+---++

root@osk-team:~# quantum port-show cfb7d5ba-3603-4448-9140-8c1d10ca2b2f
+--++
| Field|
Value
|
+--++
| admin_state_up   |
True
|
| binding:capabilities | {"port_filter":
false} |
| binding:vif_type |
ovs
|
| device_id|
fd907599-60a2-4efa-9c7e-65fb8c8b0f77
|
| device_owner |
network:router_interface
|
| fixed_ips| {"subnet_id":
"5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address": "10.78.99.81"} |
| id   |
cfb7d5ba-3603-4448-9140-8c1d10ca2b2f
|
| mac_address  |
fa:16:3e:a2:db:c4
|
| name
|
|
| network_id   |
52df3dd6-76f6-4036-855d-7f81d2b440b9
|
| status   |
DOWN
|
| tenant_id|
e6a025539f2f4823b9ae25d17096efc2
|
==
___
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] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Nikhil Mittal

The /etc/quantum/l3-agent.ini file seems all correct. I didn't make any
changes to it except the following line:
interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver

Rest is default.
-Nikhil
On Thu, May 23, 2013 at 5:09 PM, Endre Karlson wrote:

> Have you checked your config 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 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't ping to VMs from the host machine which I believe is because of
>> router not configured with external interface.
>> Any suggestions ?
>> Thanks,
>> Nikhil
>>
>> Below is the output of useful commands:
>>
>> ===
>> root@osk-team:~# quantum port-list
>>
>> +--+--+---++
>> | id   | name | mac_address   |
>> fixed_ips
>> |
>>
>> +--+--+---++
>> | 53d63be8-967c-439c-8ffa-53ef1f7f3d37 |  | fa:16:3e:09:99:b9 |
>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>> "10.78.99.84"} |
>> | 565eb936-fb89-42a9-9482-0f089907c35a |  | fa:16:3e:96:78:92 |
>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>> "10.78.99.87"} |
>> | 6f01314f-6f47-4884-b812-1d66fae9ca3e |  | fa:16:3e:b6:c6:fe |
>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>> "10.78.99.83"} |
>> | 7894091c-274a-48dd-8348-b3fd449b6705 |  | fa:16:3e:bb:69:9e |
>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>> "10.78.99.85"} |
>> | 9c99fe76-4d74-44de-a2f5-3f3dc555c3d8 |  | fa:16:3e:db:f6:6f |
>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>> "10.78.99.86"} |
>> | badec4e8-fa4f-47e3-a7a2-123d84d03337 |  | fa:16:3e:79:01:50 |
>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>> "10.78.99.82"} |
>> | cfb7d5ba-3603-4448-9140-8c1d10ca2b2f |  | fa:16:3e:a2:db:c4 |
>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>> "10.78.99.81"} |
>>
>> +--+--+---++
>>
>> root@osk-team:~# quantum port-show cfb7d5ba-3603-4448-9140-8c1d10ca2b2f
>>
>> +--++
>> | Field|
>> Value
>> |
>>
>> +--++
>> | admin_state_up   |
>> True
>> |
>> | binding:capabilities | {"port_filter":
>> false} |
>> | binding:vif_type |
>> ovs
>> |
>> | device_id|
>> fd907599-60a2-4efa-9c7e-65fb8c8b0f77
>> |
>> | device_owner |
>> network:router_interface
>> |
>> | fixed_ips| {"subnet_id":
>> "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address": "10.78.99.81"} |
>> | id   |
>> cfb7d5ba-3603-4448-9140-8c1d10ca2b2f
>> |
>> | mac_address  |
>> fa:16:3e:a2:db:c4
>> |
>> | name
>> |
>> |
>> | network_id   |
>> 52df3dd6-76f6-4036-855d-7f81d2b440b9
>> |
>> | status   |
>> DOWN
>> |
>> | tenant_id|
>> e6a025539f2f4823b9ae25d17096efc2
>> |
>> ==
>>
>>
>>
>>
>> ___
>> 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] Router internal interface is DOWN (Grizzly with Quantum)

2013-05-23 Thread Nikhil Mittal

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:00:00:00

So only one interface is shown which is also DOWN.
BTW, I had changed the default security setting to port 22 for TCP and -1
for ICMP based on the guide given somewhere in Openstack documentation.
-Nikhil

On Thu, May 23, 2013 at 7:52 PM, Salvatore Orlando wrote:

>
>
> On 23 May 2013 13:15, Ashok Kumaran  wrote:
>
>> Since you have a single node installation , for connecting to the VM's
>> from the base host you won't need router/l3 stuffs.if its not happening
>> then you might need to check the secgroup  rules.
>>
>
> This is true only if you're running without overlapping IPs. Otherwise the
> IP addresses for your instances will be stored in a network namespace
> called qdhcp- and not reachable from the host machine, unless
> one eithers executes commands from within the namespace or goes through a
> Quantum router (and I believe you'd want to use floating IPs for that)
>
>
>>
>> Coming back to your question. Does the ifconfig shows internal router
>> interface ip ? have you added the routerid in the l3agent.ini . If not can
>> you add and restart the agent and check
>>
>
> Again if you're using namespaces, you'll need to run ifconfig or ip addr
> show from within that namespace with 'ip netns  exec '.
> The default security group already allow traffic between ports belonging
> to the same tenant, and this is apparently your case. If you've altered the
> default settings however, it might as well be that the security 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
>
>
>>
>>
>>
>>
>>
>> Ashok
>>
>> Sent from my iPhone
>>
>> On 23-May-2013, at 5:27 PM, Nikhil Mittal  wrote:
>>
>> The /etc/quantum/l3-agent.ini file seems all correct. I didn't make any
>> changes to it except the following line:
>> interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver
>>
>> Rest is default.
>> -Nikhil
>> On Thu, May 23, 2013 at 5:09 PM, Endre Karlson 
>> wrote:
>>
>>> Have you checked your config 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 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't ping to VMs from the host machine which I believe is because of
>>>> router not configured with external interface.
>>>> Any suggestions ?
>>>> Thanks,
>>>> Nikhil
>>>>
>>>> Below is the output of useful commands:
>>>>
>>>> ===
>>>> root@osk-team:~# quantum port-list
>>>>
>>>> +--+--+---++
>>>> | id   | name | mac_address   |
>>>> fixed_ips
>>>> |
>>>>
>>>> +--+--+---++
>>>> | 53d63be8-967c-439c-8ffa-53ef1f7f3d37 |  | fa:16:3e:09:99:b9 |
>>>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>>>> "10.78.99.84"} |
>>>> | 565eb936-fb89-42a9-9482-0f089907c35a |  | fa:16:3e:96:78:92 |
>>>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>>>> "10.78.99.87"} |
>>>> | 6f01314f-6f47-4884-b812-1d66fae9ca3e |  | fa:16:3e:b6:c6:fe |
>>>> {"subnet_id": "5b53398a-70ce-44c6-8f6b-7a21a4ea48d7", "ip_address":
>>>> "10.78.99.83"} |
>>>> | 7894091c-27

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

2013-05-23 Thread Nikhil Mittal

I also noticed one more thing: everytime i run the command below, it shows
me only dhcp elated entry. I manually enter the router entry each time.
Could this point to the issue I am facing ?
=
root@osk-team:~# ip netns list
qdhcp-52df3dd6-76f6-4036-855d-7f81d2b440b9
=
-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:00:00:00
>
> So only one interface is shown which is also DOWN.
> BTW, I had changed the default security setting to port 22 for TCP and -1
> for ICMP based on the guide given somewhere in Openstack documentation.
> -Nikhil
>
>
> On Thu, May 23, 2013 at 7:52 PM, Salvatore Orlando wrote:
>
>>
>>
>> On 23 May 2013 13:15, Ashok Kumaran  wrote:
>>
>>> Since you have a single node installation , for connecting to the VM's
>>> from the base host you won't need router/l3 stuffs.if its not happening
>>> then you might need to check the secgroup  rules.
>>>
>>
>> This is true only if you're running without overlapping IPs. Otherwise
>> the IP addresses for your instances will be stored in a network namespace
>> called qdhcp- and not reachable from the host machine, unless
>> one eithers executes commands from within the namespace or goes through a
>> Quantum router (and I believe you'd want to use floating IPs for that)
>>
>>
>>>
>>> Coming back to your question. Does the ifconfig shows internal router
>>> interface ip ? have you added the routerid in the l3agent.ini . If not can
>>> you add and restart the agent and check
>>>
>>
>> Again if you're using namespaces, you'll need to run ifconfig or ip addr
>> show from within that namespace with 'ip netns  exec '.
>> The default security group already allow traffic between ports belonging
>> to the same tenant, and this is apparently your case. If you've altered the
>> default settings however, it might as well be that the security 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
>>
>>
>>>
>>>
>>>
>>>
>>>
>>> Ashok
>>>
>>> Sent from my iPhone
>>>
>>> On 23-May-2013, at 5:27 PM, Nikhil Mittal 
>>> wrote:
>>>
>>> The /etc/quantum/l3-agent.ini file seems all correct. I didn't make any
>>> changes to it except the following line:
>>> interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver
>>>
>>> Rest is default.
>>> -Nikhil
>>> On Thu, May 23, 2013 at 5:09 PM, Endre Karlson 
>>> wrote:
>>>
>>>> Have you checked your config 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 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't ping to VMs from the host machine which I believe is because of
>>>>> router not configured with external interface.
>>>>> Any suggestions ?
>>>>> Thanks,
>>>>> Nikhil
>>>>>
>>>>> Below is the output of useful commands:
>>>>>
>>>>> ===
>>>>> root@osk-team:~# quantum port-list
>>>>>
>>>>> +--+--+---++
>>>>> | id   | name | mac_address   |
>>>>> fixed_ips
>>>>> |
>>>>>
>>>>> +--+--+---++
>>>>> |

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 entry. I manually enter the router entry each time.
> Could this point to the issue I am facing ?
> =
> root@osk-team:~# ip netns list
> qdhcp-52df3dd6-76f6-4036-855d-7f81d2b440b9
> =
> -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:00:00:00
>>
>> So only one interface is shown which is also DOWN.
>> BTW, I had changed the default security setting to port 22 for TCP and -1
>> for ICMP based on the guide given somewhere in Openstack documentation.
>> -Nikhil
>>
>>
>> On Thu, May 23, 2013 at 7:52 PM, Salvatore Orlando 
>> wrote:
>>
>>>
>>>
>>> On 23 May 2013 13:15, Ashok Kumaran  wrote:
>>>
>>>> Since you have a single node installation , for connecting to the VM's
>>>> from the base host you won't need router/l3 stuffs.if its not happening
>>>> then you might need to check the secgroup  rules.
>>>>
>>>
>>> This is true only if you're running without overlapping IPs. Otherwise
>>> the IP addresses for your instances will be stored in a network namespace
>>> called qdhcp- and not reachable from the host machine, unless
>>> one eithers executes commands from within the namespace or goes through a
>>> Quantum router (and I believe you'd want to use floating IPs for that)
>>>
>>>
>>>>
>>>> Coming back to your question. Does the ifconfig shows internal router
>>>> interface ip ? have you added the routerid in the l3agent.ini . If not can
>>>> you add and restart the agent and check
>>>>
>>>
>>> Again if you're using namespaces, you'll need to run ifconfig or ip addr
>>> show from within that namespace with 'ip netns  exec '.
>>> The default security group already allow traffic between ports belonging
>>> to the same tenant, and this is apparently your case. If you've altered the
>>> default settings however, it might as well be that the security 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
>>>
>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Ashok
>>>>
>>>> Sent from my iPhone
>>>>
>>>> On 23-May-2013, at 5:27 PM, Nikhil Mittal 
>>>> wrote:
>>>>
>>>> The /etc/quantum/l3-agent.ini file seems all correct. I didn't make any
>>>> changes to it except the following line:
>>>> interface_driver = quantum.agent.linux.interface.OVSInterfaceDriver
>>>>
>>>> Rest is default.
>>>> -Nikhil
>>>> On Thu, May 23, 2013 at 5:09 PM, Endre Karlson >>> > wrote:
>>>>
>>>>> Have you checked your config 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 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't ping to VMs from the host machine which I believe is because of
>>>>>> router not configured with external interface.
>>>>>> Any suggestions ?
>>>>>> Thanks,
>>>>>> Nikhil
>>>>>>
>>>>>> Below is the output of useful commands:
>>>>>>
>>>>>> ==

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,
>
> ** **
>
> Any idea about below errors as I have setup Grizzly all-in-one and getting
> below error on dashboard.
>
> ** **
>
> ** **
>
> ***1.  Error: *Unauthorized: Network list can not be retrieved.***
> *
>
> ***2.  Error: *Unauthorized: Unable to retrieve quota information.
> 
>
> ***3.  ***Unauthorized: Unable to retrieve router list.*×*
>
> ***4.  Error: *Unauthorized: Unable to retrieve a list of
> external networks "401 Unauthorized This server could not verify that you
> are authorized to access the document you requested. Either you supplied
> the wrong credentials (e.g., bad password), or your browser does not
> understand how to supply the credentials required. Authentication required
> ".
>
> # quantum router-list
>
> 401 Unauthorized
>
> ** **
>
> This server could not verify that you are authorized to access the
> document you requested. Either you supplied the wrong credentials (e.g.,
> bad password), or your browser does not understand how to supply the
> credentials required.
>
> ** **
>
> Authentication required
>
> ** **
>
> ** **
>
> Thanks & Regards,
>
> *Rajesh Upadhayay***
>
> ___
> 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

[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 command on.

NOTE: the network node's host name is "network".




2013-06-08 00:56:19DEBUG [quantum.openstack.common.rpc.amqp] received
{u'_context_roles': [u'admin'], u'_msg_id':
u'9987f73b2db44097ae472bd281210f2a', u'_context_read_deleted': u'no',
u'_context_tenant_id': None, u'args': {u'host': u'network'}, u'_unique_id':
u'a89b6f2b2dd04c97a2fb0ce694cac1b3', u'_context_is_admin': True,
u'version': u'1.0', u'_context_project_id': None, u'_context_timestamp':
u'2013-06-07 06:24:13.416063', u'_context_user_id': None, u'method':
u'get_active_networks'}

2013-06-08 00:56:19DEBUG [quantum.openstack.common.rpc.amqp] unpacked
context: {'user_id': None, 'roles': [u'admin'], 'tenant_id': None,
'is_admin': True, 'timestamp': u'2013-06-07 06:24:13.416063', 'project_id':
None, 'read_deleted': u'no'}

2013-06-08 00:56:19DEBUG [quantum.db.dhcp_rpc_base] Network list
requested from network

2013-06-08 00:56:19  WARNING [quantum.scheduler.dhcp_agent_scheduler] No
enabled DHCP agent on host network

2013-06-08 00:56:19ERROR [quantum.openstack.common.rpc.amqp] Exception
during message handling

Traceback (most recent call last):

  File
"/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py",
line 430, in _process_data

rval = self.proxy.dispatch(ctxt, version, method, **args)

  File "/usr/lib/python2.7/dist-packages/quantum/common/rpc.py", line 43,
in dispatch

quantum_ctxt, version, method, **kwargs)

  File
"/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/dispatcher.py",
line 133, in dispatch

return getattr(proxyobj, method)(ctxt, **kwargs)

  File "/usr/lib/python2.7/dist-packages/quantum/db/dhcp_rpc_base.py", line
42, in get_active_networks

context, host)

  File "/usr/lib/python2.7/dist-packages/quantum/db/agentschedulers_db.py",
line 137, in list_active_networks_on_active_dhcp_agent

context, constants.AGENT_TYPE_DHCP, host)

  File "/usr/lib/python2.7/dist-packages/quantum/db/agents_db.py", line
125, in _get_agent_by_type_and_host

host=host)

AgentNotFoundByTypeHost: Agent with agent_type=DHCP agent and host=network
could not be found

2013-06-08 00:56:19ERROR [quantum.openstack.common.rpc.common]
Returning exception Agent with agent_type=DHCP agent and host=network could
not be found to caller

2013-06-08 00:56:19ERROR [quantum.openstack.common.rpc.common]
['Traceback (most recent call last):\n', '  File
"/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/amqp.py",
line 430, in _process_data\nrval = self.proxy.dispatch(ctxt, version,
method, **args)\n', '  File
"/usr/lib/python2.7/dist-packages/quantum/common/rpc.py", line 43, in
dispatch\nquantum_ctxt, version, method, **kwargs)\n', '  File
"/usr/lib/python2.7/dist-packages/quantum/openstack/common/rpc/dispatcher.py",
line 133, in dispatch\nreturn getattr(proxyobj, method)(ctxt,
**kwargs)\n', '  File
"/usr/lib/python2.7/dist-packages/quantum/db/dhcp_rpc_base.py", line 42, in
get_active_networks\ncontext, host)\n', '  File
"/usr/lib/python2.7/dist-packages/quantum/db/agentschedulers_db.py", line
137, in list_active_networks_on_active_dhcp_agent\ncontext,
constants.AGENT_TYPE_DHCP, host)\n', '  File
"/usr/lib/python2.7/dist-packages/quantum/db/agents_db.py", line 125, in
_get_agent_by_type_and_host\nhost=host)\n', 'AgentNotFoundByTypeHost:
Agent with agent_type=DHCP agent and host=network could not be found\n']



Thanks,

-Nikhil
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp

[Openstack] Error in spawning second VM

Re: [Openstack] Grizzly fails on ubuntu server 13.04

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

Re: [Openstack] Grizzly fails on ubuntu server 13.04

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

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

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

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

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

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

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

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

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

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

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

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

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

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

18 matches

Site Navigation

Mail list logo

Footer information