I've updated https://issues.apache.org/jira/browse/VCL-579 issue:
- attached ESXi.pm module
- added comments on how to use it.

I'm not sure if this should be included in 2.3, probably not. The module will 
need more testing.
I've created it based on my idea how it could be used at GMU and we haven't 
deployed it yet. So there is no "real-world" testing/usage for this module. I 
have only tested it in sandbox environment. 

Thank you,

Dmitri Chebotarov
Virtual Computing Lab Systems Engineer, TSD - Ent Servers & Messaging
223 Aquia Building, Ffx, MSN: 1B5
Phone: (703) 993-6175
Fax: (703) 993-3404

On Wednesday, May 9, 2012 at 15:53 , Josh Thompson wrote:

> Hash: SHA1
> All,
> 2.3 appears to be nearing a release. There are 9 JIRA issues still open. I'd 
> like to aim for *Wednesday of next week* to cut a release candidate. Please 
> try to have any changes you want included in 2.3 submitted and tested by then.
> Please look through parts of the code that you maintain for any files that 
> have not been updated in 6 months or so to make sure necessary files have 
> been 
> updated and any old stuff has been cleaned out. Specifically, looking under 
> some of the backend code at the modules, the following items have not been 
> updated in 6 months. If you maintain any of these, please let me know if they 
> should be included in the release. If not, I'll drop them since they have not 
> been touched in a while. (Is someone going to commit Dmitri's updates for the 
> ESXi.pm OS module?).
> managementnode/lib/VCL/Module/OS/Linux/ESXi.pm
> managementnode/lib/VCL/Module/OS/Linux/ManagementNode.pm
> managementnode/lib/VCL/Module/OS/Linux/UnixLab.pm
> managementnode/lib/VCL/Module/OS/Windows/Version_5/2003.pm
> managementnode/lib/VCL/Module/OS/Windows/Version_5/XP.pm
> managementnode/lib/VCL/Module/OS/Windows/Version_6/2008.pm
> managementnode/lib/VCL/Module/OS/Windows/Version_6/7.pm
> managementnode/lib/VCL/Module/OS/Windows/Version_6/Vista.pm
> managementnode/lib/VCL/Module/Provisioning/esx.README
> managementnode/lib/VCL/Module/Provisioning/esx.pm
> managementnode/lib/VCL/Module/Provisioning/esxthin.README
> managementnode/lib/VCL/Module/Provisioning/esxthin.pm
> managementnode/lib/VCL/Module/Provisioning/helloworld.pm
> managementnode/lib/VCL/Module/Provisioning/vbox.pm
> managementnode/lib/VCL/Module/Provisioning/vmware.pm
> managementnode/lib/VCL/Module/Provisioning/xCAT21.pm
> managementnode/lib/VCL/Module/Provisioning/VMware/vmware_cmd.pm
> If anyone needs help setting up an area to test code, NCSU may be able to 
> provide you with some resources to do that - just let us know.
> As a reminder, the release process is to cut a release candidate (RC) and 
> post 
> that to my web space at ASF. Then, I'll start a vote thread on the lists that 
> will remain open for at least 72 hours. If we have a positive vote without 
> any major concerns, the vote passes our community. Then, I'll post a summary 
> of our vote to the Incubator PMC, where another vote will take place that 
> will 
> be open for at least 72 hours (after we graduate, this 2nd vote will no 
> longer 
> be needed). Once that passes, I'll create a release artifact from the RC, 
> publish it, and announce the release.
> Thanks,
> Josh
> ASF VCL release manager
> - -- 
> - -------------------------------
> Josh Thompson
> VCL Developer
> North Carolina State University
> my GPG/PGP key can be found at pgp.mit.edu
> All electronic mail messages in connection with State business which
> are sent to or received by this account are subject to the NC Public
> Records Law and may be disclosed to third parties.
> Version: GnuPG v2.0.17 (GNU/Linux)
> iEYEARECAAYFAk+qyzYACgkQV/LQcNdtPQMhlACeKyZxw27jM7tC3tdleQlRJNml
> o/AAnRYlBNV0iCjRodxJnqDyFyLW96vx
> =wdot

Reply via email to