Ask Your Question
0

Launching instance failed in Multi node quantum

asked 2012-03-30 10:41:45 -0500

neelugaddam gravatar image

We are trying to test the multi node setup using quantum and openstack using devstack. In our setup, we have one controller node and the other is compute node with the following configuration.

Controller configuration:

localrc

HOST_IP=192.168.2.210 FLAT_INTERFACE=eth2 FIXED_RANGE=10.0.0.0/24 FIXED_NETWORK_SIZE=256 FLOATING_RANGE=10.0.1.128/28 MULTI_HOST=False ENABLED_SERVICES="$ENABLED_SERVICES,quantum,q-svc,q-agt"

Compute Configuration:

localrc

HOST_IP=192.168.2.211 FLAT_INTERFACE=eth1 FIXED_RANGE=10.0.0.0/24 FIXED_NETWORK_SIZE=256 FLOATING_RANGE=10.0.1.128/28 MULTI_HOST=False MASTER_SERVER=192.168.2.210 ENABLED_SERVICES="n-cpu,quantum,q-agt" MYSQL_HOST=$MASTER_SERVER RABBIT_HOST=$MASTER_SERVER KEYSTONE_AUTH_HOST=$MASTER_SERVER GLANCE_HOSTPORT=$MASTER_SERVER:9292 EC2_DMZ_HOST=$MASTER_SERVER

When we are trying to launch the instance on the compute node from the controller dashboard, it is giving error in the Spawning state. The nova compute log file is showing the following error:

Got semaphore "/opt/stack/nova/instances/_base/2acf438d92efd508d063f57861b674ab3d04da91" for method "copy_and_extend"... from (pid=3346) inner /opt/stack/nova/nova/utils.py:932 2012-03-30 14:24:02 DEBUG nova.utils [req-3e41e7f0-4f8e-4f31-bcff-929496d70028 b02b184c7f8340d58b043ad93684559b dd05174146e44739b560e56077612e9c] Running cmd (subprocess): qemu-img create -f qcow2 -o cluster_size=2M,backing_file=/opt/stack/nova/instances/_base/2acf438d92efd508d063f57861b674ab3d04da91 /opt/stack/nova/instances/instance-00000001/disk from (pid=3346) execute /opt/stack/nova/nova/utils.py:219 libvir: QEMU error : Failed to add tap interface to bridge '': No such device 2012-03-30 14:24:04 ERROR nova.compute.manager [req-3e41e7f0-4f8e-4f31-bcff-929496d70028 b02b184c7f8340d58b043ad93684559b dd05174146e44739b560e56077612e9c] [instance: e39578a5-d49a-45db-9921-a936821c42ed] Instance failed to spawn (nova.compute.manager): TRACE: Traceback (most recent call last): (nova.compute.manager): TRACE: File "/opt/stack/nova/nova/compute/manager.py", line 592, in _spawn (nova.compute.manager): TRACE: self._legacy_nw_info(network_info), block_device_info) (nova.compute.manager): TRACE: File "/opt/stack/nova/nova/exception.py", line 114, in wrapped (nova.compute.manager): TRACE: return f(args, *kw) (nova.compute.manager): TRACE: File "/opt/stack/nova/nova/virt/libvirt/connection.py", line 873, in spawn (nova.compute.manager): TRACE: self._create_new_domain(xml) (nova.compute.manager): TRACE: File "/opt/stack/nova/nova/virt/libvirt/connection.py", line 1670, in _create_new_domain (nova.compute.manager): TRACE: domain.createWithFlags(launch_flags) (nova.compute.manager): TRACE: File "/usr/lib/python2.7/dist-packages/libvirt.py", line 372, in createWithFlags (nova.compute.manager): TRACE: if ret == -1: raise libvirtError ('virDomainCreateWithFlags() failed', dom=self) (nova.compute.manager): TRACE: libvirtError: Failed to add tap interface to bridge '': No such device (nova.compute.manager): TRACE: 2012-03-30 14:24:04 DEBUG nova.compute.manager [req-3e41e7f0-4f8e-4f31-bcff-929496d70028 b02b184c7f8340d58b043ad93684559b dd05174146e44739b560e56077612e9c] [instance: e39578a5-d49a-45db-9921-a936821c42ed] Deallocating network for instance from (pid=3346) _deallocate_network /opt/stack/nova/nova/compute/manager.py:616 2012-03-30 14:24:04 DEBUG nova.rpc.amqp [req-3e41e7f0-4f8e-4f31-bcff-929496d70028 b02b184c7f8340d58b043ad93684559b dd05174146e44739b560e56077612e9c] Making asynchronous cast on network... from (pid=3346) cast /opt/stack/nova/nova/rpc/amqp.py:346 2012-03-30 14:24:05 ERROR nova.rpc.amqp [req-3e41e7f0-4f8e-4f31-bcff-929496d70028 b02b184c7f8340d58b043ad93684559b dd05174146e44739b560e56077612e9c] Exception during message handling (nova.rpc.amqp): TRACE: Traceback (most recent call last): (nova.rpc.amqp): TRACE: File "/opt/stack/nova/nova/rpc/amqp.py", line 252, in _process_data (nova.rpc.amqp): TRACE: rval = node_func(context=ctxt, *node_args) (nova.rpc ... (more)

edit retag flag offensive close merge delete

17 answers

Sort by ยป oldest newest most voted
0

answered 2012-06-18 17:19:24 -0500

gbaratto-3 gravatar image

Thanks!

For the configuration I described, do I need to run nova-network in the "cloud controller" as well? or just in the hypervisors? My understanding is that we dont need the network manager, if we are using quantum?

Cheers, g.

edit flag offensive delete link more
0

answered 2012-06-16 00:51:18 -0500

danwent gravatar image

On Fri, Jun 15, 2012 at 3:06 PM, tiadobatima < question192137@answers.launchpad.net > wrote:

Question #192137 on quantum changed: https://answers.launchpad.net/quantum/+question/192137 (https://answers.launchpad.net/quantum...)

tiadobatima posted a new comment: Hi Dan...

I guess I'm still confused about what "multi-node" setup is, and the quantum/openstack documentation mentioned earlier isn't very friendly:

http://docs.openstack.org/trunk/openstack-network/admin/content/Limits- (http://docs.openstack.org/trunk/opens...) dle455.html

Let's assume I have a setup with one "cloud controller" server with keystone, glance, nova-api, nova-scheduler, and quantum server (no hypervisor here). In this setup I'd also have 10 "compute nodes" (hypervisors), with everyone of them running nova-compute, nova-network and quantum-openvswitch-agent.

yes, that definitely works.

>

Is this how it's supposed to work? Do I need to run nova-network in the "cloud manager" server too? Why? What's the meaning of nova-network HA the doc is mentioning?

The confusion here is that Nova created a special HA option for nova-network which is enabled using the "multi_host" flag. This is what is not supported in Quantum for Essex: http://docs.openstack.org/diablo/openstack-compute/admin/content/existing-ha-networking-options.html (http://docs.openstack.org/diablo/open...)

>

Thanks for the help! g.


You received this question notification because you are an answer contact for quantum.


~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira, Inc: http://www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~

edit flag offensive delete link more
0

answered 2012-06-15 22:27:01 -0500

gbaratto-3 gravatar image

damn... getting confused with the names again: I meant "cloud controller", not "cloud manager"

edit flag offensive delete link more
0

answered 2012-06-15 22:01:23 -0500

gbaratto-3 gravatar image

Hi Dan...

I guess I'm still confused about what "multi-node" setup is, and the quantum/openstack documentation mentioned earlier isn't very friendly:

http://docs.openstack.org/trunk/openstack-network/admin/content/Limits-dle455.html (http://docs.openstack.org/trunk/opens...)

Let's assume I have a setup with one "cloud controller" server with keystone, glance, nova-api, nova-scheduler, and quantum server (no hypervisor here). In this setup I'd also have 10 "compute nodes" (hypervisors), with everyone of them running nova-compute, nova-network and quantum-openvswitch-agent.

Is this how it's supposed to work?
Do I need to run nova-network in the "cloud manager" server too? Why? What's the meaning of nova-network HA the doc is mentioning?

Thanks for the help! g.

edit flag offensive delete link more
0

answered 2012-04-01 17:16:14 -0500

danwent gravatar image

Multi-node just means you are running devstack on more than one "host" (e.g., you may be running a "controller" node with services like nova-scheduler, nova-api, quantum, etc) and one or more dedicated compute nodes (i.e., those running nova-network and the quantum agent).

"Multi-host" is the somewhat confusing term given to being able to run nova-network on each compute host, which is not what we're talking about in this bug.

On Sun, Apr 1, 2012 at 8:25 AM, yong sheng gong < question192137@answers.launchpad.net > wrote:

Question #192137 on quantum changed: https://answers.launchpad.net/quantum/+question/192137 (https://answers.launchpad.net/quantum...)

yong sheng gong posted a new comment: I don't know what you mean by saying Multi node quantum. document at

http://docs.openstack.org/incubation/openstack-network/admin/content/Limits-dle455.html (http://docs.openstack.org/incubation/...) says Multi-host nova-network HA is not supported.

I think we just are able to have 1. one quantum server running, 2. one nova-network with quantum manager running 3. and agent on each compute node running


You received this question notification because you are an answer contact for quantum.


~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks: http://www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~

edit flag offensive delete link more
0

answered 2012-04-01 15:25:22 -0500

gongysh gravatar image

I don't know what you mean by saying Multi node quantum. document at http://docs.openstack.org/incubation/openstack-network/admin/content/Limits-dle455.html (http://docs.openstack.org/incubation/...) says Multi-host nova-network HA is not supported.

I think we just are able to have 1. one quantum server running, 2. one nova-network with quantum manager running 3. and agent on each compute node running

edit flag offensive delete link more
0

answered 2012-04-01 07:52:09 -0500

danwent gravatar image

Instructions for setting up Quantum depend on the plugin. The Quantum Administrator Guide has pointers to each plugin's documentation.

For example, the Open vSwitch plugin docs are here: http://openvswitch.org/openstack/documentation/ (http://openvswitch.org/openstack/docu...)

dan

On Sat, Mar 31, 2012 at 11:10 PM, NAVEEN REDDY < question192137@answers.launchpad.net > wrote:

Question #192137 on quantum changed: https://answers.launchpad.net/quantum/+question/192137 (https://answers.launchpad.net/quantum...)

NAVEEN REDDY requested more information: Can you please point us for the detailed manual installation steps for two node set up using Quantum?


You received this question notification because you are an answer contact for quantum.


~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira Networks: http://www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~

edit flag offensive delete link more
0

answered 2012-04-01 06:09:05 -0500

Can you please point us for the detailed manual installation steps for two node set up using Quantum?

edit flag offensive delete link more
0

answered 2012-03-31 16:32:55 -0500

danwent gravatar image

Yes

edit flag offensive delete link more
0

answered 2012-03-31 05:02:51 -0500

neelugaddam gravatar image

Does the manual configuration of the multi-node setup with quantum work (without devstack) ?

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2012-03-30 10:41:45 -0500

Seen: 85 times

Last updated: Jun 18 '12