I'm thinking about reusing custom types from existing puppet infrastructure in standalone (ruby)
Example -> Custom Type for a "storage pool" consisting of volume groups,
logical volumes, drbd resources, filesystems, nfs export... you get the idea.
Suppose that we have already defined this type in the form of a puppet module / custom type.
Instead of reimplementing this stuff in an external library / script I'd
rather reuse the puppet module, and as an additional goody, use some of the
puppet datatypes / features (reporting differences in system state, noop, transaction, ...)
So far I stumbled upon some different concepts in puppet land which might make
puppet internal dsl
One requirement would be the "standalone" aspect. While interacting with this
hypthetical storage pool, I'd rather not do network roundtrips to the puppet
master, as I prefer robustness over freshness in this case.
I looked somewhat into the faces variant but coldn't find a way to construct a
catalog without talking to the master.
And by using just the Faces[:resource, ..] - stuff I'm missing some
other nice features of the catalog.
Any ideas / snippets / tips / tutorials to get me started?
Thanks alot in advance
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/-/CaaCOxX_UK4J.
To post to this group, send email to firstname.lastname@example.org.
To unsubscribe from this group, send email to email@example.com.
For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.