On Thursday, August 16, 2012 3:37:23 AM UTC-5, Daniele Sluijters wrote:
>
> Hello,
>
> We've been using Hiera for a while and one of the things I'd like to do is
> use the data we have in the YAML backend and generate our BIND zonefiles
> and DHCPD.conf from it.
>
> Every node has a stanza defined with it's 'primary' IP-address and
> MAC-address like so:
> hostname.yaml:
> ---
> m_interface:
> - ip: 127.0.0.1
> - mac_address: aa:bb:cc:dd:ee:ff
>
> Based on that information and the YAML file it was found in (so the node
> in our case) I'd like to generate a dhcpd.conf like this:
>
> host hostname(.yaml) {
> fixed-address: m_interface[ip]
> hardware ethernet: m_interface[mac_address]
>
> Now, this can be done for a single node, however, I need a way to get that
> information for every node. As far as I understand both hiera_hash and
> hiera_array only walk the hierarchy upwards, not outwards (which is usually
> what you want anyway).
>
> I'm looking for something like a hiera_all that would return a hash with
> the node name as key and value the m_interface stanza for that node.
>
> At this point I'm not even sure this can be done so, anyone got any bright
> ideas?
>
>
At first glance this looks like a good use case for exported resources and
the Concat module. Each node would export a file fragment containing its
stanza of dhcpd.conf. The DHCP server would collect all the fragments and
use them to define the target file.
If you're not already using [thin] storeconfigs, however, then you will
need to set that up to use exported resources. That is not entirely
trivial to set up or to run. Also, this solution requires that nodes be
able sync with the master before their information is added to the DHCP
server, and given the nature of DHCP, that might not be possible.
On the other hand, if all the hiera data is for the DHCP server's benefit
in the first place, instead of for the nodes themselves, then it may be
easier simply to restructure the data. Instead of putting all your node
information into separate files, you could put it all into one hash in one
file:
interfaces.yaml:
---
interfaces: {
host1: {
ip: 127.0.0.1
mac_address: aa:bb:cc:dd:ee:ff
}
host2: {
ip: 127.0.0.2
mac_address: aa:bb:cc:dd:ee:fe
}
}
You would then load the hash via a single hiera() call, and use a template
to unpack and format the results.
That sort of arrangement of your data could even be made to work if the
individual nodes and the DHCP server need to share. The nodes would have
to extract the data differently (get the hash via hiera(), then select
their own entry, and within it the particular values they want), but it
should be doable.
John
--
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/-/1q9B2CURtBoJ.
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.
