Ohad Levy wrote:
This really doesn't sound like a common design, if you have the need for such a complex setup, I would recommend to create an environment, and link the relevant modules into that env directory.

this has been proven to scale up with no issues.

my 2 cents,
Ohad

On Sat, Oct 17, 2009 at 8:02 PM, Billy Shaw <bi...@sceneunseen.com> wrote:



I am in the design and testing phase working on various configurations
and options.

I generate my configuration files programmatically once a day based on
queries to an asset management database to organize servers a specific way.
There was discussion of a design option that would have a few of hundred
entries in the modulepath day one and grow from there (creating new ones
if needed when the configuration files are generated)..
I don't want to start down a path that could limit me down the road and
require starting over and since I could not find a limit in the puppet
documentation so I thought I would ask.

James Turnbull wrote:
> Are you experiencing an error?  Have you tested?
>
> Regards
>
> James Turnbull
>
>






Thanks for the input to everyone on this thread. Sounds like the suggestion I posed of a large modulepath is not a good one (nor is it scalable which was my first instinct). I am going with a design which does have a unique module path for each department (around 40) and one which is shared by all. This will allow me leverage existing nomenclature within puppet (for customization) that is in alignment with existing server administration and change processes.


Thank you




--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to