[openstack-dev] [Nova][Evacuate] nova evacuate command failed

[zhang xiaobin]

hi, i run command nova evacuate failed, anyone can help point out direction?
steps:
1.run two compute host A and B
2.run instance vm01 on host A, shutdown host A
3.run command nova evacuate --on-shared-storage vm01 B


My analysis is:
When VM starting to be created in Host B, I can see the 'network-vif-plugged' 
message showed up in neutron server log.
but after VM is created, no more neutron 'network-vif-plugged' rpc message 
generated, thus we got 'timeout' error.
actually no any error messages in neutron server log during evacuation.

i see from source code that it has some notifier with port api 
create/delete/update and port db insert/update/set.
i guess that it is due to the port data not changed during evacuation, so no 
any message to be sent out as notification

could any confirm this?

-
Host B compute log:
nova-nova.virt.libvirt.driver WARNING: Timeout waiting for vif plugging 
callback for instance 091cde07-297b-437c-b21f-32bc53c24701
nova-nova.compute.manager INFO: Lifecycle event 1 on VM 
091cde07-297b-437c-b21f-32bc53c24701
nova-nova.compute.manager INFO: During sync_power_state the instance has a 
pending task. Skip.
nova-nova.virt.libvirt.driver INFO: Deleting instance files 
/instance_path/091cde07-297b-437c-b21f-32bc53c24701
nova-nova.virt.libvirt.driver INFO: Deletion of 
/instance_path/091cde07-297b-437c-b21f-32bc53c24701 complete
nova-nova.compute.manager ERROR: Setting instance vm_state to ERROR
Traceback (most recent call last):
  File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 5529, 
in _error_out_instance_on_exception
yield
  File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 2524, 
in rebuild_instance
self._rebuild_default_impl(**kwargs)
  File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 2377, 
in _rebuild_default_impl
block_device_info=new_block_device_info)
  File /usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py, line 
2265, in spawn
block_device_info)
  File /usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py, line 
3675, in _create_domain_and_network
raise exception.VirtualInterfaceCreateException()
VirtualInterfaceCreateException: Virtual Interface creation failed
nova-oslo.messaging.rpc.dispatcher ERROR: Exception during message handling: 
Virtual Interface creation failed
Traceback (most recent call last):
  File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py, 
line 133, in _dispatch_and_reply
incoming.message))
  File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py, 
line 176, in _dispatch
return self._do_dispatch(endpoint, method, ctxt, args)
  File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/dispatcher.py, 
line 122, in _do_dispatch
result = getattr(endpoint, method)(ctxt, **new_args)
  File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 393, in 
decorated_function
return function(self, context, *args, **kwargs)
  File /usr/lib/python2.6/site-packages/oslo/messaging/rpc/server.py, line 
139, in inner
return func(*args, **kwargs)
  File /usr/lib/python2.6/site-packages/nova/exception.py, line 88, in wrapped
payload)
  File /usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py, 
line 68, in __exit__
six.reraise(self.type_, self.value, self.tb)
  File /usr/lib/python2.6/site-packages/nova/exception.py, line 71, in wrapped
return f(self, context, *args, **kw)
  File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 274, in 
decorated_function
pass
  File /usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py, 
line 68, in __exit__
six.reraise(self.type_, self.value, self.tb)
  File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 260, in 
decorated_function
return function(self, context, *args, **kwargs)
  File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 327, in 
decorated_function
function(self, context, *args, **kwargs)
  File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 303, in 
decorated_function
e, sys.exc_info())
  File /usr/lib/python2.6/site-packages/nova/openstack/common/excutils.py, 
line 68, in __exit__
six.reraise(self.type_, self.value, self.tb)
  File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 290, in 
decorated_function
return function(self, context, *args, **kwargs)
  File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 2524, 
in rebuild_instance
self._rebuild_default_impl(**kwargs)
  File /usr/lib/python2.6/site-packages/nova/compute/manager.py, line 2377, 
in _rebuild_default_impl
block_device_info=new_block_device_info)
  File /usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py, line 
2265, in spawn
block_device_info)
  File 

[openstack-dev] [Nova][Schedule] how to schedule vms(like database VM, vs web server VM) to different resource pool(either LVM or GlusterFs)?

[zhang xiaobin]

Greeting,

I have some hosts in one availability zone, some hosts are solely based on LVM, 
which means their root images will be sitting on LVM;
while other hosts are setup with GlusterFS, which means their root image will 
be allocated on Gluster.

My question is: what's the best way to let VM be scheduled to the right 
resource pool(either LVM-based, or GlusterFs-based?)
how to configure and which kind of schedule filter to be used? can we use image 
metadata function to achieve this?

Many thanks!
本邮件（包括其附件）可能含有保密、专有或保留著作权的信息。如果您并非本邮件指定接受人，请即刻通知发送人并将本邮件从您的系统中删除，您不得散布、保留、复制、披露或以其他方式使用本邮件任何相关信息，并且通过邮件告知我们此次错误投递。发送人在本邮件下表达的观点并不一定代表苏宁云商集团股份有限公司的观点。苏宁云商集团股份有限公司并不保证本邮件是安全或不受任何计算机病毒影响的，并且对由于邮件传输而导致的邮件内容错误或缺失不承担任何责任。除非明确说明，本邮件并不构成具有约束力的契约。

This e-mail may contain confidential, copyright and/or privileged information. 
If you are not the addressee or authorized to receive this, please inform us of 
the erroneous delivery by return e-mail, and you should delete it from your 
system and may not use, copy, disclose or take any action based on this e-mail 
or any information herein. Any opinions expressed by sender hereof do not 
necessarily represent those of SUNING COMMERCE GROUP CO., LTD.,SUNING COMMERCE 
GROUP CO., LTD.,does not guarantee that this email is secure or free from 
viruses. No liability is accepted for any errors or omissions in the contents 
of this email, which arise as a result of email transmission. Unless expressly 
stated,this email is not intended to form a binding contract.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Neutron][DVR] Openstack Juno: how to configure dvr in Network-Node and Compute-Node?

[zhang xiaobin]

Could anyone help on this?

In Openstack juno, Neutron new feature called Distributed Virtual Routing (DVR),
But how to configure it in network-node and compute-node. Openstack.org just 
said router_distributed = True, which is far than enough.
could any help point to some detailed instruction on how to configure it?
When we were adding port, some errors from router reported errors like: 
AttributeError: 'Ml2Plugin' object has no attribute 'update_dvr_port_binding'
What's more, is this DVR per project, or per compute nodes?
Thanks in advance!




zhang xiaobin
本邮件（包括其附件）可能含有保密、专有或保留著作权的信息。如果您并非本邮件指定接受人，请即刻通知发送人并将本邮件从您的系统中删除，您不得散布、保留、复制、披露或以其他方式使用本邮件任何相关信息，并且通过邮件告知我们此次错误投递。发送人在本邮件下表达的观点并不一定代表苏宁云商集团股份有限公司的观点。苏宁云商集团股份有限公司并不保证本邮件是安全或不受任何计算机病毒影响的，并且对由于邮件传输而导致的邮件内容错误或缺失不承担任何责任。除非明确说明，本邮件并不构成具有约束力的契约。

This e-mail may contain confidential, copyright and/or privileged information. 
If you are not the addressee or authorized to receive this, please inform us of 
the erroneous delivery by return e-mail, and you should delete it from your 
system and may not use, copy, disclose or take any action based on this e-mail 
or any information herein. Any opinions expressed by sender hereof do not 
necessarily represent those of SUNING COMMERCE GROUP CO., LTD.,SUNING COMMERCE 
GROUP CO., LTD.,does not guarantee that this email is secure or free from 
viruses. No liability is accepted for any errors or omissions in the contents 
of this email, which arise as a result of email transmission. Unless expressly 
stated,this email is not intended to form a binding contract.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev