|
Hi All. After spending a few days, making integration with Nova / Keystone / Glance etc, just to get Multizone working, surfing the nova code, asking in launchpad / IRC / lists, we've come into a hard conclusion : "You will not get Multizone working on Diablo, if you are using KVM as your hypervisor" Why is that ? Mainly, if you manage to configure Nova to authenticate with keystone, add child zones, get visibility of the zones via python-novaclient, etc, yo will get to a point where a so called : service_stats dictionary, is empty where supposed to be a list of compute nodes with their capabilities, and the nova-scheduler crashes ( ok, at least this is fixed in Diablo 2011.3.1 ). So to have a little background about whats happening, heres the deal ... Via "nova.compute.manager.periodic_tasks" this function calls "update_service_capabilities" that, at the same time it calls "nova.virt.driver.get_hosts_stats" every compute node, reports their capabilities to the scheduler, so the scheduler, can collect them and via the BaseScheduler, decide where an instance should be running. The thing is, since the get_host_stats call is delegated to the virt layer, when you are using KVM as your hypervisor, this function is not implemented (line 489, of nova.virt.driver), only the XenServer driver has this method implemented. So, if anyone implemented it, for KVM, please share it ! In mean time, we checked that since Milestone 2 in Essex, the compute nodes supposed to report their capabilities for KVM, so ... we are testing ESSEX Milestone 3. Cheers. --
 Alejandro Comisario
Infrastructure IT - #melicloud Cloud Builder Arias 3751, Piso 7 (C1430CRG) Ciudad de Buenos Aires - Argentina Cel: +549(11) 15-3770-1857 Tel : +54(11) 4640-8443 |
_______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
