hiera hierarchy by network

[Peter K]

This network lookup is simple and works well...but only on some clients because they have more than one network interface:

hiera.yaml:

---
:hierarchy:
  - "%{::trusted.certname}"
  - "%{::network}"
  - common

It fails on some machines because they have docker virtual interfaces and instead return a network name like 172.0.0.0 instead of the one I want: 10.1.1.0.

It seems the lookup just picks the first interface listed in the ::networking array.

Are there any other methods to do lookups based on the network? I want to match the same network that puppet is working on.

My experience is I can't easily parse the hiera lookup for ::networking (asked here) but maybe I can with hiera5 with globs.

Thx,

-peter

[Rob Nelson]

Try the structured facts. $facts['networking']['network'] is probably somewhat indeterministic, but if your interface names are predictable, then $facts['networking']['interfaces']['ens192']['network'] (or 'eth0' or whatever) could conceivably be the value you need.

Having tried to fight with this before, however, I went with an external fact. I don't need the network so much as I need the datacenter and I just create the file `/etc/facter/facts.d/datacenter` in my templates or during provisioning, so I never need to deal with some wacky new network that isn't correlated to a datacenter until I touch some code again. Something like that might be helpful even if you can get the structured fact right, as the provisioning process is often a better spot to insert such values.

Rob Nelson
rnel...@gmail.com

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/0593fc69-c51e-4176-a4c8-c28840ac59a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Peter K]

Thank you Rob. I've been close to experimenting with custom facts but haven't tried yet. I think I can stick with what I have for now and just watch out of breakage...at which point I'll create a custom fact.

-peter

[Nick Fagerlund]

I THINK the new mapped_paths feature in Puppet 4.10 can do this, when combined with the networking fact. Um, I think it'd look something like this:

hierarchy:
  - name: "Network interface (tries all interfaces)"
    mapped_paths: [facts.networking.interfaces, interface, "networks/%{interface.1.network}.yaml"]

Since facts.networking.interfaces is a hash, the local value of "interface" is an array with one key/val par, so something like ["en0", { hash of stuff, where we want the key 'network' }], hence interface.1.network.

[Nick Fagerlund]

Forgot to paste the docs link: https://docs.puppet.com/puppet/latest/hiera_config_yaml_5.html#specifying-file-paths