package import woes

2009-10-02 Thread Brian Bouterse
I have a problem with the esxthin.pm and VCL says it can't load VCL::Module::Provisioning::esxthin I've copied the esx.pm to esxthin.pm, and updated all the names and checks for esx to esxthin so that it is a valid VCL module. It is also installed correctly. The module performs the same

esxthin.pm username/password/filer ip variables

2009-10-02 Thread Brian Bouterse
Currently in the netapp based, esxthin.pm the username/password/and filer ip are hardcoded. I want to get those variables to not be hardcoded, but passed into the module. Should we put it in the db, a special config file, or in the vcld.conf? I will post the preliminary code to the SVN as

Re: a few more backend TODO items for 2.1 release

2009-10-02 Thread Aaron Peeler
Thanks. Andy and I will start working on this. Since the back end can be configured to support one or more of xCAT, vmware, standalone lab, etc. In the README file we'll separately list the required dependencies to get vcld started and the conditional dependencies to get other parts working. -

Re: additional perl library location (esxthin.pm provisioning related)

2009-10-02 Thread Aaron Peeler
I think that is fine. Unless of course it can be installed into one of the default perl lib paths under /usr/lib/perl5/ -A --On October 1, 2009 5:23:53 PM -0400 Brian Bouterse wrote: Speaking of which, any thoughts on using the following path as the installation path of those libraries wh