I'm with Andy on this one... I'm doing something very similar with my
NetApp volume provider (https://github.com/fatmcgav/fatmcgav-netapp/).
I've created a define with the following contents:
define util::netapp::volume (
$ensure = present,
$size,
$aggr = 'aggr1',
$snapresv = 0,
$autoincrement = true,
$snapschedule = {"minutes" => 0, "hours" => 0, "days" => 0, "weeks"
=> 0}
) {
netapp_notify {"volume_define_${name}":
message => "Processing Volume ${name}",
}
->
netapp_volume { "v_${name}":
ensure => $ensure,
initsize => $size,
aggregate => $aggr,
spaceres => "none",
snapreserve => $snapresv,
autoincrement => $autoincrement,
options => {'convert_ucode' => 'on', 'no_atime_update' =>
'on', 'try_first' => 'volume_grow'},
snapschedule => $snapschedule
}
->
netapp_qtree { "q_${name}":
ensure => $ensure,
volume => "v_${name}"
}
->
netapp_export { "/vol/v_${name}/q_${name}":
ensure => $ensure,
persistent => true
}
}
I've added a default hash to 'snapschedule' in the options list, but that
can be over-ridden from the Hiera data.
Then use the following to pull the data from hiera and call the define:
create_resources( util::netapp::volume, hiera('volumes') )
'Volumes' in hiera yaml looks like:
volumes:
vol1:
ensure: present
size: '500m'
vol2:
ensure: present
size: '20g'
snapschedule:
minutes: 0
hours: 36
days: 0
weeks: 0
You can also use the 'hiera' command to test your yaml structure:
$ hiera -c hiera.yaml volumes clientcert=act-star-nactl01
{"vol1"=>{"ensure"=>"present", "size"=>"500m"},
"vol2"=>{"ensure"=>"present", "size"=>"20g", "snapschedule"=>{"days"=>0,
"weeks"=>0, "hours"=>36, "minutes"=>0}}}
As you can see from the above output, *snapschedule* for *vol2* is a nested
hash. This assumes that your resource provider can support hashes on the
relevant param/property ;)
HTH
Gav
On Friday, 4 January 2013 15:37:25 UTC, llowder wrote:
>
>
>
> On Friday, January 4, 2013 9:11:28 AM UTC-6, Andy Taylor wrote:
>>
>> Hi,
>>
>> I'm trying to build a module for haproxy which fetches all the
>> configuration data from Hiera to populate the haproxy config file. I've run
>> into a number of issues though when I try to use hashes. Ideally, I want to
>> use something like this:
>>
>> haproxy_listeners :
>> "cluster1" :
>> ip : '192.168.0.2'
>> port : '80'
>> servers :
>> "server1" :
>> ip : '192.168.0.3'
>> port : '8080'
>>
>> So a hash of clusters with each cluster containing a nested hash of
>> servers. Is this possible with Hiera/ERB? It's easy enough to iterate over
>> the first hash, but I can't work out how to extract the contents of the
>> nested hash. Or I might just be approaching this in entirely the wrong
>> way... Any help would be much appreciated.
>>
>>
> I haven't used the function myself, but this looks like it would be a good
> case for a define + create_resources(), which I think is part of stdlib.
> You might need to restructure the hashes slightly, but I think that will be
> the best approach.
>
>
>
>> Thanks,
>>
>> Andy
>>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/UjWLd-yp7iIJ.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
