>> Model wise, in an ideal world, the proxied/virtual address would be a >> 'node' of sorts, and have that entry, but if no box exists to compile >> that catalog, well then we're just talking crazy :-). >> > > > Well no, if the proxied / virtual address is not a property specific to any > individual node, then it is a property of the overall site configuration. > Puppet therefore does not need to determine this from the nodes; instead, it > needs to *apply* it to them. As such, it ought to be recorded in the Hiera > data repository from which Puppet is working. If it's in the data, then it > does not need to be communicated between nodes via exported resources. > Rather, Puppet should draw it from the same source for all nodes that need > it for any purpose.
I think you've missed my modelling point or perspective, I was simply expressing that if you could do it, you would record the intended exported resource to a virtual node that maps to the virtual address, but this isn't possible today. Hiera isn't part of the resulting model, its just input that creates the graph. This is academic though, its not possible anyway. Irrespective of this imaginary world, one could store the data in hiera to be consumed, if one chose to - or somewhere else, it matters little for the resulting graph. ken. -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/CAE4bNTk-D4w96-7729kOzZhx%2B4DnkR7VrR0Uat9x8HmnFribPA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
