On Oct 1, 2009, at 6:20 PM, Matt Hogstrom wrote:
Did you get your "key" where it needs to be ?
On Sep 22, 2009, at 12:17 PM, Josh Thompson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Based on Kevan's input, we'll go with options 2 and 3 - a tag to
make it easy
to see what the RC
Did you get your "key" where it needs to be ?
On Sep 22, 2009, at 12:17 PM, Josh Thompson wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Based on Kevan's input, we'll go with options 2 and 3 - a tag to
make it easy
to see what the RC was based off of, and an actual RC artifact that
p
Thanks for the comments. The NetApp perl client libraries do not have
Apache 2.0 licenses, so they will not be distributed as part of the
VCL code. Those wanting to use the esxthin.pm provisioning module
will need to download the library from the netapp website on their
own. I will docum
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've created a page to keep track with what has been done for the 2.1 release:
http://cwiki.apache.org/VCL/release-21-checklist.html
There are a few things I've finished for the frontend that now need to be done
for the backend.
The README file nee
I think this depends on how it's licensed. Does it have Apache 2.0
License? Others can comment on this.
Even if we can redistribute it. I'd prefer not to in case it changes, bug
fixes, new features, etc.
I'd suggest documenting on the Apache VCL wiki or in the module itself
where to get it and h
As referenced earlier, I'm creating an esxthin.pm which thin
provisions VM's for ESX servers. To interact with the NetApp API,
NetApp provides perl client libraries. These libraries need to exists
on any vcld machine which plans to use the esxthin.pm provisioning
engine. The entire clien
