Hello,
Steven VanDevender wrote,
> Douglas Garstang writes:
> > On Thu, Sep 1, 2011 at 1:35 PM, Steven VanDevender
> wrote:
> >
> > > Douglas Garstang writes:
> > > > Was that in reply to my original post, or a subsequent reply? You did
> > > see
> > > > where I said /etc/puppet was a wo
On Thu, Sep 01, 2011 at 09:07:37PM +0200, Reinoud van Leeuwen wrote:
> On Thu, Sep 01, 2011 at 11:58:04AM -0700, Russell Van Tassell wrote:
> > I'm currently in the same position, and the solution I've proposed (and am
> > currently working on) involves using a central repository (likely git). The
On Sep 1, 2011, at 2:01 PM, Douglas Garstang wrote:
>
> Editing files locally under /etc/puppet as an individual user is not mutually
> exclusive with editing files in a distributed working copy owned by the same
> user.
If it's not, then there's no point in asking for help: your environment
Douglas Garstang writes:
> On Thu, Sep 1, 2011 at 1:35 PM, Steven VanDevender wrote:
>
> > Douglas Garstang writes:
> > > Was that in reply to my original post, or a subsequent reply? You did
> > see
> > > where I said /etc/puppet was a working copy, right?
> >
> > It sounds like you nee
On Thu, Sep 1, 2011 at 1:35 PM, Steven VanDevender wrote:
> Douglas Garstang writes:
> > Was that in reply to my original post, or a subsequent reply? You did
> see
> > where I said /etc/puppet was a working copy, right?
>
> It sounds like you need to get to the point where no one does their
> e
On Thu, Sep 1, 2011 at 1:35 PM, Steven VanDevender wrote:
> Douglas Garstang writes:
> > Was that in reply to my original post, or a subsequent reply? You did
> see
> > where I said /etc/puppet was a working copy, right?
>
> It sounds like you need to get to the point where no one does their
> e
Douglas Garstang writes:
> Was that in reply to my original post, or a subsequent reply? You did see
> where I said /etc/puppet was a working copy, right?
It sounds like you need to get to the point where no one does their
edits under /etc/puppet on the puppetmaster, because you're obviously
run
You asked for best practices and that document describes them, essentially.
If your process is broken it should be fixed.
On Thu, Sep 1, 2011 at 1:28 PM, Douglas Garstang wrote:
> Was that in reply to my original post, or a subsequent reply? You did see
> where I said /etc/puppet was a working co
Aaron Grewell writes:
> Technically true, but administratively confusing IMHO.
We put our all our Puppet data (but not the puppetmaster config) in a
Subversion repository. Everyone does editing in their own working copy
checked out from that Subversion repository. Commits to the repository
trig
Was that in reply to my original post, or a subsequent reply? You did see
where I said /etc/puppet was a working copy, right?
Doug.
On Thu, Sep 1, 2011 at 1:09 PM, Scott Smith wrote:
> http://projects.puppetlabs.com/projects/1/wiki/Puppet_Version_Control
>
> On Thu, Sep 1, 2011 at 11:47 AM, Dou
I can't say I've ever met someone who had trouble with this.
On Thu, Sep 1, 2011 at 1:10 PM, Aaron Grewell wrote:
> Technically true, but administratively confusing IMHO.
>
> On Thu, Sep 1, 2011 at 1:08 PM, Scott Smith wrote:
>
>> A directory is a directory. That a directory has a parent directo
Also, setgid directories with umask 002 can help if you don't want to use a
VCS.
On Thu, Sep 1, 2011 at 11:47 AM, Douglas Garstang
wrote:
> I have a real-world, best practices, procedural question.
>
> How do you manage the he puppet master, under /etc/puppet, where multiple
> people may be editi
Technically true, but administratively confusing IMHO.
On Thu, Sep 1, 2011 at 1:08 PM, Scott Smith wrote:
> A directory is a directory. That a directory has a parent directory in
> which other files exist is pretty moot.
>
> On Thu, Sep 1, 2011 at 12:13 PM, Aaron Grewell wrote:
>
>> We don't put
http://projects.puppetlabs.com/projects/1/wiki/Puppet_Version_Control
On Thu, Sep 1, 2011 at 11:47 AM, Douglas Garstang
wrote:
> I have a real-world, best practices, procedural question.
>
> How do you manage the he puppet master, under /etc/puppet, where multiple
> people may be editing files? T
A directory is a directory. That a directory has a parent directory in which
other files exist is pretty moot.
On Thu, Sep 1, 2011 at 12:13 PM, Aaron Grewell wrote:
> We don't put our manifests under /etc/puppet at all. It's convenient for
> small installations but as we scaled up I found mixin
We don't put our manifests under /etc/puppet at all. It's convenient for
small installations but as we scaled up I found mixing configs (local,
managed by Puppet) and manifests (kept under version control) to be
problematic.
On Sep 1, 2011 11:58 AM, "Russell Van Tassell" wrote:
> I'm currently
On Thu, Sep 01, 2011 at 11:58:04AM -0700, Russell Van Tassell wrote:
> I'm currently in the same position, and the solution I've proposed (and am
> currently working on) involves using a central repository (likely git). The
> puppet client (running on the master) simply checks the current master
>
I'm currently in the same position, and the solution I've proposed (and am
currently working on) involves using a central repository (likely git). The
puppet client (running on the master) simply checks the current master
branch on the remote repository -- if the revisions are not the same, it
just
I have a real-world, best practices, procedural question.
How do you manage the he puppet master, under /etc/puppet, where multiple
people may be editing files? The /etc/puppet directory is a working copy,
and each user has read access to files created by other users. However, if
one person adds a
19 matches
Mail list logo
