Re: VCL w/ Netapp thin provisioning

2011-08-10 Thread Aaron Peeler
: Aaron Peeler [mailto:aaron_pee...@ncsu.edu] Sent: Monday, August 08, 2011 2:16 PM To: vcl-dev@incubator.apache.org Subject: Re: VCL w/ Netapp thin provisioning Hi Gerhard, Correct, this provisioning module did not get included in the latest release because it wasn't maintained

RE: VCL w/ Netapp thin provisioning

2011-08-09 Thread Hartl, Gerhard L.
I'm interested - Gerhard -Original Message- From: Aaron Peeler [mailto:aaron_pee...@ncsu.edu] Sent: Monday, August 08, 2011 2:16 PM To: vcl-dev@incubator.apache.org Subject: Re: VCL w/ Netapp thin provisioning Hi Gerhard, Correct, this provisioning module did not get included

Re: VCL w/ Netapp thin provisioning

2011-08-09 Thread Aaron Peeler
[mailto:aaron_pee...@ncsu.edu] Sent: Monday, August 08, 2011 2:16 PM To: vcl-dev@incubator.apache.org Subject: Re: VCL w/ Netapp thin provisioning Hi Gerhard, Correct, this provisioning module did not get included in the latest release because it wasn't maintained by the original creator. Since

Re: Fwd: VCL w/ Netapp thin provisioning

2011-08-09 Thread Josh Thompson
-- From: Aaron Peeler aaron_pee...@ncsu.edu Date: Mon, Aug 8, 2011 at 2:15 PM Subject: Re: VCL w/ Netapp thin provisioning To: vcl-dev@incubator.apache.org Hi Gerhard, Correct, this provisioning module did not get included in the latest release because it wasn't maintained

VCL w/ Netapp thin provisioning

2011-08-08 Thread Hartl, Gerhard L.
I've noticed that the Netapp (esxthin.pm) portion of the available provisioning engines was not included in the latest 2.1.1 version of VCL as it was in previous versions and was just curious if there are any updated versions of it. I have been able to get it working properly after a bit of

Re: VCL w/ Netapp thin provisioning

2011-08-08 Thread Aaron Peeler
Hi Gerhard, Correct, this provisioning module did not get included in the latest release because it wasn't maintained by the original creator. Since the current active committers don't have a way to test and validate it, we had to drop it from the 2.1.1 version. If I recall correctly, this