Open Stack

Hi Gary,

One more question, when using VCDriver, I can use it in the following two
ways:
1) start up many nova computes and those nova computes manage same vcenter
clusters.
2) start up many nova computes and those nova computes manage different
vcenter clusters.

Do we have some best practice for above two scenarios or else can you
please provide some best practise for VCDriver? I did not get much info
from admin guide.

Thanks,

Jay


2014-02-16 23:01 GMT+08:00 Jay Lau <jay.lau.513 at gmail.com>:

> Thanks Gary, clear now. ;-)
>
>
> 2014-02-16 21:40 GMT+08:00 Gary Kotton <gkotton at vmware.com>:
>
>> Hi,
>> There are two issues here.
>> The first is a bug fix that is in review:
>> - https://review.openstack.org/#/c/69209/ (this is where they have the
>> same configuration)
>> The second is WIP:
>> - https://review.openstack.org/#/c/69262/ (we need to restore)
>> Thanks
>> Gary
>>
>> From: Jay Lau <jay.lau.513 at gmail.com>
>> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>> <openstack-dev at lists.openstack.org>
>> Date: Sunday, February 16, 2014 6:39 AM
>> To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org
>> >
>> Subject: [openstack-dev] [Nova][VMWare] VMwareVCDriver related to
>> resize/cold migration
>>
>> Hey,
>>
>> I have one question related with OpenStack vmwareapi.VMwareVCDriver
>> resize/cold migration.
>>
>> The following is my configuration:
>>
>>  DC
>>     |
>>     |----Cluster1
>>     |          |
>>     |          |----9.111.249.56
>>     |
>>     |----Cluster2
>>                |
>>                |----9.111.249.49
>>
>> *Scenario 1:*
>> I started two nova computes manage the two clusters:
>> 1) nova-compute1.conf
>> cluster_name=Cluster1
>>
>> 2) nova-compute2.conf
>> cluster_name=Cluster2
>>
>> 3) Start up two nova computes on host1 and host2 separately
>> 4) Create one VM instance and the VM instance was booted on Cluster2
>> node  9.111.249.49
>> | OS-EXT-SRV-ATTR:host                 | host2 |
>> | OS-EXT-SRV-ATTR:hypervisor_hostname  |
>> domain-c16(Cluster2)                                     |
>> 5) Cold migrate the VM instance
>> 6) After migration finished, the VM goes to VERIFY_RESIZE status, and
>> "nova show" indicates that the VM now located on host1:Cluster1
>> | OS-EXT-SRV-ATTR:host                 | host1 |
>> | OS-EXT-SRV-ATTR:hypervisor_hostname  |
>> domain-c12(Cluster1)                                     |
>> 7) But from vSphere client, it indicates the the VM was still running on
>> Cluster2
>> 8) Try to confirm the resize, confirm will be failed. The root cause is
>> that nova compute on host2 has no knowledge of domain-c12(Cluster1)
>>
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp   File
>> "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 2810, in
>> do_confirm_resize
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp
>> migration=migration)
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp   File
>> "/usr/lib/python2.6/site-packages/nova/compute/manager.py", line 2836, in
>> _confirm_resize
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp
>> network_info)
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp   File
>> "/usr/lib/python2.6/site-packages/nova/virt/vmwareapi/driver.py", line 420,
>> in confirm_migration
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp
>> _vmops = self._get_vmops_for_compute_node(instance['node'])
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp   File
>> "/usr/lib/python2.6/site-packages/nova/virt/vmwareapi/driver.py", line 523,
>> in _get_vmops_for_compute_node
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp
>> resource = self._get_resource_for_node(nodename)
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp   File
>> "/usr/lib/python2.6/site-packages/nova/virt/vmwareapi/driver.py", line 515,
>> in _get_resource_for_node
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp
>> raise exception.NotFound(msg)
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp
>> NotFound: NV-3AB798A The resource domain-c12(Cluster1) does not exist
>> 2014-02-16 07:10:17.166 12720 TRACE nova.openstack.common.rpc.amqp
>>
>>
>> *Scenario 2:*
>>
>> 1) Started two nova computes manage the two clusters, but the two
>> computes have same nova conf.
>> 1) nova-compute1.conf
>> cluster_name=Cluster1
>> cluster_name=Cluster2
>>
>> 2) nova-compute2.conf
>> cluster_name=Cluster1
>> cluster_name=Cluster2
>>
>> 3) Then create and resize/cold migrate a VM, it can always succeed.
>>
>>
>> *Questions:*
>> For multi-cluster management, does vmware require all nova compute have
>> same cluster configuration to make sure resize/cold migration can succeed?
>>
>> --
>> Thanks,
>>
>> Jay
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
>
> --
> Thanks,
>
> Jay
>



-- 
Thanks,

Jay
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140216/e7da9e73/attachment.html>