Nigel Kersten wrote:
> Just pointing out that 0.24.8 (non RC) is available in debian testing.
>
> http://packages.debian.org/source/testing/puppet
>
>
>
> On Fri, May 8, 2009 at 9:09 PM, Robin Sheat wrote:
>> My puppet setup has been working nicely for a while, but recently I get
>> errors
>
6:04 AM, Eric Gerlach
> > wrote:
>
> >> Kyle, Ryan,
>
> >> I'd love it if those instructions made it into the Wiki. The uupdate thing
> >> would be hugely helpful to some other Debian administrators, I'm sure.
>
> >> Cheers,
>
> >
Kyle Cordes wrote:
> Ryan Steele wrote:
>
>> a bit of a delay, and if you want more bleeding edge .debs, your options
>> are either a PPA, backporting, or creating your own.
>
> There is a better option, available for some projects: have either the
> project itself,
Nigel Kersten wrote:
> When can we expect the 0.24.8 debs to be out?
Depends on your distribution and the release you're running. If you
need it sooner than your distribution is going to work it in to your
current release, your options are either to backport it or create your
own. With Debia
On Mar 27, 9:33 am, Kyle Cordes wrote:
> Kyle Cordes wrote:
> >> Apply the .diff
> Ryan Steele wrote:
> > I didn't have to download any diffs. Here's what I did:
> > 2. Grab the debian directory for 0.24.7 from git (git clone
> > git://git.debian.o
Kyle Cordes wrote:
> Eric Gerlach wrote:
>
>> As a point of reference, it took about 2-3 weeks for 0.24.7 to get packaged.
>> You'll have to get it from the experimental repository, though.
>
> It's not hard to whip up your own package though, if you don't mind it
> being a bit ugly:
>
>
> Gr
On Mar 3, 12:11 pm, Luke Kanies wrote:
> Yes I'm amenable to it being added but it's pretty low on the priority
> list for the general community, so you get both. :)
Works for me :) Thanks for being open minded about it, and keep up
the good work.
--~--~-~--~~~
On Feb 27, 5:56 pm, Luke Kanies wrote:
> On Feb 27, 2009, at 1:40 PM, Ryan Steele wrote:
>
>
>
> > Does Puppet have any plans to make resource types for special files,
> > such as FIFO pipes and sockets? Seems like a cleaner alternative to
> > using an exec (e.g.,
Does Puppet have any plans to make resource types for special files,
such as FIFO pipes and sockets? Seems like a cleaner alternative to
using an exec (e.g., running 'file' on the resource), and acting
appropriately based on the returned result (e.g., running mknod).
--~--~-~--~~-
Hey folks,
I have a question regarding users with varying group memberships. If I
have two several nodes, and on each node I need user FOO present, but in
different groups, is the best approach to that an inheritance chain?
For example, a base class 'users', and two other classes 'node1users'
On Oct 29, 5:40 pm, Luke Kanies <[EMAIL PROTECTED]> wrote:
> On Oct 27, 2008, at 12:33 PM, Ryan Steele wrote:
> > That answers part of my question about whether the "non-
> > resource" (obviously more appropriately titled "language") bits of the
> &g
On Oct 27, 12:35 pm, Luke Kanies <[EMAIL PROTECTED]> wrote:
> The entire set of manifests is evaluated on the server, producing a
> catalog which is evaluated on the client.
Ok, so the puppetmaster creates a static catalog (devoid of variables
and control structures) for any resources applica
It's been my understanding that the order in which resources are
defined having no bearing on the order of execution. This would mean
that the only way to ensure one resource is declared after or before
another is with the use of certain metaparameters (e.g., before/
require and notify/subscribe)
Bah, copy and paste fail. I agree that uniformity is certainly
something to go for, and something that will be addressed no later
than the LDAP rollout. But, I think that piece-mealing my configs, as
Andrew and Brian suggested, is probably the most prudent approach at
the moment. Thanks to ever
On Oct 21, 2:15 pm, "Brian Mathis" <[EMAIL PROTECTED]> wrote:
>
> Do you have the jurisdiction to change the IDs on the servers to sync
> them up? That doesn't need LDAP, just judicious use of 'find' and
> some downtime.
>
> Syncing up the IDs is really what needs to happen.
--~--~-~--~
Jeff Leggett wrote:
> I see what you're doing, but I question WHY? The amount of time you
> have spent troubleshooting this could have been better spent bringing
> up a small LDAP Directory that would both resolve these issues, work
> well with Puppet, and allow you a lot more flexibility in the
On Oct 21, 9:47 am, Ryan Steele <[EMAIL PROTECTED]> wrote:
>
> ...snip..
>
> I then need a way to look up the custom facts, which take on the form
> "jsmith_uid", "jsmith_pgid", and "jsmith_gid". This yields the
> following function
After having put in no small amount of time in to trying to coerce
Puppet into managing some decentralized users, I'm starting to wonder
if it's even possible. I have a network in which some user attributes
vary from node to node, such as UID, GID, and groups. However, short
of a truckload of in
Hey folks,
Before responding to the ticket below, I think I should provide a little
bit more qualifying information. I had a discussion with Luke Kanies
regarding the design of the ssh_authorized_keys type, and the agreement
we came to was that the key itself would be a good identifier becaus
Hey folks,
Over the past day or so, I've been working a lot with the
ssh_authorized_keys module, but found what I believe to be several
design flaws. I'd be interested to see if anybody else feels bound by
the same limitations and lack of support for what I believe to be
common use cases. I've
20 matches
Mail list logo
