Puppet users - Oct 2009 - Is there a limit to the number of entires you can have for modulepath in puppet.conf?

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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Are you experiencing an error?  Have you tested?

Regards

James Turnbull

-- 
Author of:
* Pro Linux Systems Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

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
>
>   

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

2009/10/17 Billy Shaw <billy@sceneunseen.com>:
> 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.
Okay.  I suspect there is a limit and that approach probably isn''t
scalable.

Everything under the path is included - so why not expand underneath
the path rather than extend the value of the option?

Regards

James Turnbull

-- 
Author of:
* Pro Linux Systems Administration (http://tinyurl.com/linuxadmin)
* Pulling Strings with Puppet (http://tinyurl.com/pupbook)
* Pro Nagios 2.0 (http://tinyurl.com/pronagios)
* Hardening Linux (http://tinyurl.com/hardeninglinux)

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

>
> 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.
>
>
I don''t see a limit to the module path number enforced in the code, but
I am
fairly confident that 100s of module path entries is probably not the best
solution and searching those module paths is likely to have negative
performance impacts.

What is the problem you are hoping to solve with module paths?

If you can explain a bit more about how and why, you got to that design,
hopefully we can be more helpful.

Cheers,
Andrew

--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

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 <billy@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
> >
> >
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=UTF-8"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Ohad Levy wrote:
<blockquote
 cite="mid:9ab1d3a90910181920g4483aef2v2b785678f0640d2a@mail.gmail.com"
 type="cite">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.<br>
  <br>
this has been proven to scale up with no issues.<br>
  <br>
my 2 cents,<br>
Ohad<br>
  <br>
  <div class="gmail_quote">On Sat, Oct 17, 2009 at 8:02 PM,
Billy Shaw <span
 dir="ltr">&lt;<a moz-do-not-send="true"
 href="mailto:billy@sceneunseen.com">billy@sceneunseen.com</a>&gt;</span>
wrote:<br>
  <blockquote class="gmail_quote"
 style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt
0.8ex; padding-left: 1ex;"><br>
    <br>
    <br>
I am in the design and testing phase working on various configurations<br>
and options.<br>
    <br>
I generate my configuration files programmatically once a day based on<br>
queries to an asset management database to organize servers a specific
way.<br>
There was discussion of a design option that would have a few of
hundred<br>
entries in the modulepath day one and grow from there (creating new
ones<br>
if needed when the configuration files are generated)..<br>
I don''t want to start down a path that could limit me down the road
and<br>
require starting over and since I could not find a limit in the puppet<br>
documentation so I thought I would ask.<br>
    <div class="im"><br>
James Turnbull wrote:<br>
&gt; Are you experiencing an error?  Have you tested?<br>
&gt;<br>
&gt; Regards<br>
&gt;<br>
&gt; James Turnbull<br>
&gt;<br>
&gt;<br>
    <br>
    <br>
    </div>
    <div>
    <div class="h5"><br>
    </div>
    </div>
  </blockquote>
  </div>
  <br>
  <br>
  <br>
</blockquote>
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.<br>
<br>
<br>
Thank you<br>
<br>
<br>
<br>
<br>
--~--~---------~--~----~------------~-------~--~----~<br>
You received this message because you are subscribed to the Google Groups
&quot;Puppet Users&quot; group. <br> To post to this group, send
email to puppet-users@googlegroups.com <br> To unsubscribe from this
group, send email to puppet-users+unsubscribe@googlegroups.com <br> For
more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en<br>
-~----------~----~----~----~------~----~------~--~---<br>
</body>
</html>
<br>