Hi everyone, At my organisation we tried to build a tiny cluster (1 head, 2 compute nodes) with CloudStack 4.6 and XenServer 6.6.90 for experimental reasons. As we use local storage for deploying VMs, we discovered that Cloudstack is not able to recognise the local storage pool of the slave compute node.
We tried reversing the master node (make the slave compute node -> poolmaster and the poolmaster -> slave) but the result was the same. We tried Cloudstack 4.5.2 and again problem didn’t solve. We checked the database of the poolmaster and it was totally updated and able to detect the local storage of the slave node. On Cloudstack-management interface, the XenServer 6.6 hosts appear as XenServer 6.5 hosts. In the meanwhile, we are totally able to deploy VMs in poolmaster and make use of the local storage. Did any of you face this issue and if yes, did you manage to solve it? I suspect that there are some changes in the API of Xenserver 6.6 which CS does not support currently. Best Regards Stavros ---------------------------- Stavros Konstantaras Science faculty Research IT support (FEIOG) University of Amsterdam, Science Park 904, 1098 XH Fingerprint: E5E5 9B19 D1CD 88CD 4763 3465 A8DC 7C92 330F D59A