On Jul 21, 2010, at 7:29 PM, Douglas Garstang wrote:
> The need for this is driven from the fact that various packages will
> often install a local user. In order to make sure that that id's of
> any of these local users do not clash with id's from LDAP users, the
> ldap client configuration needs
On Jul 21, 2010, at 5:16 PM, Douglas Garstang wrote:
> On Wed, Jul 21, 2010 at 4:44 PM, Patrick Mohr wrote:
>>
>> On Jul 21, 2010, at 4:29 PM, Douglas Garstang wrote:
>>
>>> Anyone,
>>>
>>> How can I guarantee that all components of the LDAP client module get
>>> installed before ANY componen
Ryan Y. Coleman wrote:
> I spent a few minutes playing with stages as well and they seem like
> a great solution to certain problems. Will there be more
> documentation made available about how to use stages after final
> release? All I'm familiar with is what's in the changelog.
>
We've had fina
On Wed, Jul 21, 2010 at 4:44 PM, Patrick Mohr wrote:
>
> On Jul 21, 2010, at 4:29 PM, Douglas Garstang wrote:
>
>> Anyone,
>>
>> How can I guarantee that all components of the LDAP client module get
>> installed before ANY components of any other module?
>
> Use 2.6.x and use run stages.
>
> -OR-
---
> From: "Douglas Garstang"
> To: puppet-users@googlegroups.com
> Sent: Wednesday, July 21, 2010 7:47:46 PM
> Subject: Re: [Puppet Users] Installing a module FIRST
> On Wed, Jul 21, 2010 at 4:32 PM, Avi Miller
> wrote:
> > Hey Douglas
> >
> > Dougla
On Wed, Jul 21, 2010 at 4:55 PM, Jeff McCune wrote:
> On Wed, Jul 21, 2010 at 4:47 PM, Douglas Garstang
>> "Note that we’re using the new parameterized classes here – this is
>> necessary because of the class-level limitations of Run Stages. These
>> limitations are present because of the complica
On Wed, Jul 21, 2010 at 4:47 PM, Douglas Garstang
> "Note that we’re using the new parameterized classes here – this is
> necessary because of the class-level limitations of Run Stages. These
> limitations are present because of the complication of trying to
> untangle resource dependencies across
On Wed, Jul 21, 2010 at 4:32 PM, Avi Miller wrote:
> Hey Douglas
>
> Douglas Garstang wrote:
>>
>> How can I guarantee that all components of the LDAP client module get
>> installed before ANY components of any other module?
>
> Take a look at the new Run Stages[1] functionality in Puppet 2.6. Run
On Jul 21, 2010, at 4:29 PM, Douglas Garstang wrote:
> Anyone,
>
> How can I guarantee that all components of the LDAP client module get
> installed before ANY components of any other module?
Use 2.6.x and use run stages.
-OR-
Use 0.25.x and make all User and Package resources depend on that
Hey Douglas
Douglas Garstang wrote:
How can I guarantee that all components of the LDAP client module get
installed before ANY components of any other module?
Take a look at the new Run Stages[1] functionality in Puppet 2.6. Run
stages would allow you to specify that the LDAP class has to run
Anyone,
How can I guarantee that all components of the LDAP client module get
installed before ANY components of any other module?
The need for this is driven from the fact that various packages will
often install a local user. In order to make sure that that id's of
any of these local users do n
11 matches
Mail list logo