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-03-31 16:32:55 -0500

danwent gravatar image

Yes

edit flag offensive delete link more
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-18 22:15:07 -0500

gongysh gravatar image

hi, we need nova-network with quantum manager in essex. Quantum network manager will connect quantum to do actual work. when nova-network is running with each compute host ( which is running hypervisor), this is multi-host network settings.

edit flag offensive delete link more
0

answered 2012-03-30 11:04:42 -0500

neelugaddam gravatar image

Sorry, we are using ubuntu 11.10 on compute and controller nodes.

edit flag offensive delete link more
0

answered 2012-03-30 15:38:20 -0500

danwent gravatar image

Hi, it looks like the OVS bridge for libvirt to plug the VMs into does not exist.

stack.sh should default to using the OVS plugin, but you could see if explicitly setting Q_PLUGIN=openvswitch in your localrc helps.

Otherwise, can you post the output of stack.sh? I'm trying to figure out why the OVS bridge is not being created by stack.sh.

edit flag offensive delete link more
0

answered 2012-03-30 16:13:42 -0500

gongysh gravatar image

there are bugs for quantum-server to accept --config-file to specify all the configuration files. Also there is a bug for Devstack after it wants to use /etc/quantum/quantum.conf file to configuration quantum-server and its plugin

see bugs: #965202 quantum.conf should be able to specify where the plugins.ini is #965199 quantum config is broken after being moved to /etc #965883 add a general funtion to read item in plugins.ini

edit flag offensive delete link more
0

answered 2012-03-30 17:29:54 -0500

neelugaddam gravatar image

I solved this issue by adding the following tweaks in the stack.sh script of the compute node.

libvirt_ovs_bridge=br-int libvirt_type=kvm libvirt_vif_type=ethernet libvirt_vif_driver=nova.virt.libvirt.vif.LibvirtOpenVswitchDriver

Now the VM is launching on compute node, but the VMs are not getting the IP addresses. Is there anything wrong in the network configuration.

Which branch of devstack is stable for testing the qunatum with multiple hosts?

Please help me.

edit flag offensive delete link more
0

answered 2012-03-30 18:22:04 -0500

danwent gravatar image

ah, of course. I only scanned the original config and had missed the fact that you are running multiple nodes.

Dave lapsley has some changes that will make devstack + quantum work for multiple hosts. He's planning on posting them very soon, right dave?

edit flag offensive delete link more
0

answered 2012-03-30 18:43:38 -0500

Yes. Will that out in the next few days.

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: 99 times

Last updated: Jun 18 '12