[
https://issues.apache.org/jira/browse/VCL-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aaron Peeler closed VCL-389.
----------------------------
Resolution: Implemented
closing this call as this has been implemented in the current vmware support
> Duke ESX provisioning module
> ----------------------------
>
> Key: VCL-389
> URL: https://issues.apache.org/jira/browse/VCL-389
> Project: VCL
> Issue Type: Improvement
> Components: vcld (backend)
> Reporter: Andy Kurth
> Attachments: esxduke.pm
>
>
> I've written a provisioning module for VCL that we use here at Duke that I'd
> like to share for possible inclusion in VCL. The module is based off VCL 2.1.
> This module is designed to work against VirtualCenter/vCenter, but should be
> able to work directly with an ESX host as well. It works a little
> differently from the existing ESX modules in that it uses the VMware perl API
> directly instead of calling the helper apps. In addition, it also greatly
> reduces the amount of disk space and deployment time necessary.
> Instead of cloning the VM for deployment, this module uses ESX to create a
> snapshot of the golden image disk, and uses that for the deployed VM. This
> means the only disk space used for the deployed VM is the differences between
> it and the master. Likewise, no time is needed to copy all the bits, so
> creating the VM takes seconds instead of minutes.
> Internally we call the module 'esxduke' to distinguish it from the existing
> ESX module. Going forward is there a better name for this module? Also,
> what should be done from here to have this included in VCL?
> Thanks,
> Sean
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
