VMWare driver using VMWare file system tools
|Assignee:||Tino Vázquez||% Done:|
|Category:||Drivers - Auth||Estimated time:||20.00 hours|
|Target version:||Release 3.4 - Beta|
Using intensively Opennebula with VMWare driver in order to control an operational private cloud composed of servers running exclusively ESXi machine, I have found some limitations with the current implementation. Especially in file system management that requires to share all the storage between Opennebula host and the hypervisor. Since ESXi (using 4.1) supports only NFS, the solution is not very efficient and in my case almost impossible (need to exploit native 2TB partitions).
The idea is to keep a shared storage but only for registered image that would be visible as a datastore on ESXi. The transfer for copying, linking, creating and deleting virtual disks would use vmkfstools remotely by SSH on the ESXi host.
#7 Updated by Tino Vázquez over 7 years ago
- Status changed from New to Assigned
- Assignee changed from Emmanuel Mathot to Tino Vázquez
- % Done changed from 0 to 70
There is a new VMware TM driver uploaded to the "feature-1014" branch. It is using vmkfstools, but using a ssh approach, to avoid dependencies in the front-end. We would appreciate any feedback you may have.
#8 Updated by Emmanuel Mathot over 7 years ago
I reviewed your solution and it seems to be the good compromise for VMWare host with no shared storage for the VM disks.
On which VMWare system did you test it?
I will try to test it soon and give you more feedback.
In fact, reading again the ticket I wrote 4 months ago, using VMWare host remote ssh command was the first option especially because of the dependencies.
We use ONE in a production environment with security constraints like the 'lockdown mode' of the ESXi host which cuts the SSH access. Therefore on our branch with the driver vmware2, we exploit the VMWare tools at maximum, also for performance reason, but this complexify the deployment.
#9 Updated by Tino Vázquez over 7 years ago
We tested this on ESX 4.1 and ESX 5.0. The case you propose is interesting, in order to support the lockdown scenario on ESX we will create another set of TMs that will assume vmkfstools on the front-end so no ssh is required.
Thanks a lot for the great feedback!