On Wed, Aug 15, 2012 at 8:00 AM, jcbollinger wrote:
>
>
> On Tuesday, August 14, 2012 4:14:47 PM UTC-5, Jeff McCune wrote:
>
>> On Mon, Aug 13, 2012 at 12:36 PM, llowder wrote:
>>
>>> If using the nodes/*.pp and having your site.pp be "import 'nodes/*'",
>>>
>>
>> You should avoid using the impor
On Tuesday, August 14, 2012 4:14:47 PM UTC-5, Jeff McCune wrote:
>
> On Mon, Aug 13, 2012 at 12:36 PM, llowder
> > wrote:
>
>> If using the nodes/*.pp and having your site.pp be "import 'nodes/*'",
>>
>
> You should avoid using the import statement (see
> http://projects.puppetlabs.com/issues/1
On 8/14/2012 2:14 PM, Jeff McCune wrote:
what is the best practice? Is it better to have one node def per
file, or group the node defs by class (ie, all app servers in one
file or all web servers in one file) or some other layout?
Best practice is to use an external node classifier
On Tuesday, August 14, 2012 4:14:47 PM UTC-5, Jeff McCune wrote:
>
> On Mon, Aug 13, 2012 at 12:36 PM, llowder
> > wrote:
>
>> If using the nodes/*.pp and having your site.pp be "import 'nodes/*'",
>>
>
> You should avoid using the import statement (see
> http://projects.puppetlabs.com/issues/1
On Mon, Aug 13, 2012 at 12:36 PM, llowder wrote:
> If using the nodes/*.pp and having your site.pp be "import 'nodes/*'",
>
You should avoid using the import statement (see
http://projects.puppetlabs.com/issues/12929). Instead, follow the [module
conventions](docs.puppetlabs.com/guides/modules.
If using the nodes/*.pp and having your site.pp be "import 'nodes/*'",
what is the best practice? Is it better to have one node def per file, or
group the node defs by class (ie, all app servers in one file or all web
servers in one file) or some other layout?
Also, is there a way to have the n
