On 21.01.2014 19:20, Andy Parker wrote:
I think that what we are hitting here is just a limitation of puppet's
ability to describe systems. What I think is missing is any idea of an
independent container. Within a given container everything needs to be
unique, but between containers you can have duplication. Each container
has certain properties that describe the container and would need to be
accessible from the managed resource while puppet executes. Containers
could be used to model the python virtual environments, different gem
install locations, etc. I think they would also be useful for modeling
different hosts where each host is a container and then you have a
catalog that includes the entire infrastructure.
This is just an idea that I'm throwing out there right now.
Well, it's basically core-support what one would already implement in a
manifest and workaround as already described with "structured" resource
names:
define virtualenv($package) {
package { "$name/$package": ensure => installed }
}
Once upon a time there were some patches/talk floating around to parse
complex titles into parameters and vice versa. That was deemed way too
complex at that time, but the world seems to have catched up ;-)
Regards, David
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/52DF81E5.30503%40dasz.at.
For more options, visit https://groups.google.com/groups/opt_out.
