Jakov
Thank you for the positive feedback.
The NetApp puppet stuff is on the back burner atm, hopefully should be able
to get back to buy in the new year :-)
Cheers
Gav
On Dec 19, 2012 2:34 AM, "Jakov Sosic" wrote:
> On 11/12/2012 12:59 PM, Gavin Williams wrote:
>
>> Monday update from me...
>
On 11/12/2012 12:59 PM, Gavin Williams wrote:
Monday update from me...
Implemented support for Export creation on Friday, after making some
further good progress...
Now I'm looking at fine-tuning stuff, such as volume settings, export
options, etc...
Great work! When I get some spare time I w
Monday update from me...
Implemented support for Export creation on Friday, after making some
further good progress...
Now I'm looking at fine-tuning stuff, such as volume settings, export
options, etc...
Cheers
Gavin
On Friday, 9 November 2012 09:54:22 UTC, Gavin Williams wrote:
>
> Quic
Quick update on the below error...
I dropped into the #puppet-dev IRC channel, and was able to resolve the
issue with some assistance from Dominic, so many thanks for that...
Latest code has been committed to Git, but basically I was missing a couple
of requires for Puppet libs...
Now happi
:( Seems to be one step forward and two steps back atm...
Following the successful creation and deletion of NetApp filer volumes
using puppet earlier in the day, I added the required provider and type to
support qtree creation and deletion...
However since then, I haven't been able to create
Quick update... It looks like all that was needed to resolve the below was
a puppetmaster restart.
Have successfully managed to create a new volume on the NetApp filer using
puppet :) :D
Now to plough on with adding support for the rest of the bits we need :)
Cheers
Gavin
On Tuesday, 6 Nov
Scratch my last, had a bit of a eureka moment...
Added ':transport: to the attr_accessor against device.rb, and it started
working again...
However now failing elsewhere...
Have got the following against a relevant node:
# Test NetApp volume provider
> netapp_volume { 'v_pupp
Ok, quick update...
I've not managed to get past the 'Undefined method' error despite my best
efforts today...
Any ideas on where I could be going wrong?
Cheers
Gavin
On Monday, 5 November 2012 17:46:07 UTC, Gavin Williams wrote:
>
> Looks like the below error was caused by some locally cac
Looks like the below error was caused by some locally cached code that
hadn't been updated by my Git pull :s
Resolved that, and now am getting the following:
$ sudo puppet device -v
> Info: starting applying configuration to actint-star-nactl01 at
> actint-star-nactl01
> Warning: Local environm
Ok, moving on then...
I've created a 'netapp_volume' type and provider, and am trying to test it
against one of the existing NetApp device nodes:
*manifests/site.pp* contains:
node 'actint-star-nactl01' {
>
> # Test NetApp volume provider
> netapp_volume { 'v_puppet_test':
>
Me again...
I pressed on using the /var/lib/puppet... configdir for the time-being, and
with a bit more jiggery pokery, I've managed to successfully register a
NetApp device, and extract some facts from it... And here's the
photographic proof :) :D http://ow.ly/i/15SLN
Now to start looking at
Ok, have fixed that error aswell...
Replaced *':configdir' *with *':confdir'*.
However it's now failing due to the netapp.yml file not being present...
What's confused me is the path it's come up with for *':confdir'*.
According to the debug output, it's trying to use
ESC[0;36mDebugESC[0m: P
Ok, after a bit more googling, have solved the NaElement load error...
Tweaked the NaServer.rb file as follows:
#require 'NaElement'
> require File.dirname(__FILE__) + "/NaElement"
>
I've now successfully loaded the require Netapp SDK files, and started
working through the connection process..
13 matches
Mail list logo
