Where can I find documentation for puppet devices? A search of the
puppetlabs docs yields almost nothing, and google searches keep returning
_MY_ questions about puppet devices. There's something seriously wrong with
that picture.
Doug
--
You received this message because you are subscribed to t
On May 21, 2011, at 4:10 PM, Gabriel Filion wrote:
> Hello,
>
> I found out that a puppetmaster I manage is currently not using the
> thin_storeconfigs option and suggested to the other admins that we use
> this in order to reduce puppet run times a little.
>
> Is it recommended to purge the [m
Hello,
I found out that a puppetmaster I manage is currently not using the
thin_storeconfigs option and suggested to the other admins that we use
this in order to reduce puppet run times a little.
Is it recommended to purge the [mysql] database once the option is
enabled on the puppetmaster?
p.
https
On Sat, May 21, 2011 at 12:48 PM, jacky wu wrote:
> which protocol does Puppet File Resource transfer based on? http? or
> rsync?
>
> --
> 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@g
which protocol does Puppet File Resource transfer based on? http? or
rsync?
--
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
On 5/21/11 10:42 AM, Brice Figureau wrote:
If you really want to simplify people's life, make those extra
attributes become metaparameters :
user { luke: ensure => present, virtual => [boolean] }
That would even allow us to parametrize virtuality/exportability with
the help of an expression (
On Fri, May 20, 2011 at 8:20 PM, Randall Hansen wrote:
> http://projects.puppetlabs.com/issues/7606
>
> The spaceship operator:
>
> User <| group == sysadmin or title == luke |>
>
> Is relatively easy to type but, if you don’t know it, very hard to
> read. We should consider a word-based syntax
On Sat, May 21, 2011 at 1:42 AM, Brice Figureau <
brice-pup...@daysofwonder.com> wrote:
> On 20/05/11 22:24, Randall Hansen wrote:
> > http://projects.puppetlabs.com/issues/7612
> >
> > The exported resources syntax:
> >
> > @@user { luke: ensure => present }
> >
> > Is concise and powerful, b
+1 from me also, from a newbie's perspective having a verbose syntax
available lowers the barrier to entry.
On May 21, 2011 4:10 AM, "Nathan Clemons" wrote:
> I am very much in favor of this. The current spaceship operator is just
> confusing, hands down. collect and search would be much nicer.
>
I am very much in favor of this. The current spaceship operator is just
confusing, hands down. collect and search would be much nicer.
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
On Fri, May 20, 2011 at 1:20 PM, Randall Hansen wrote:
> http:
Verbosity is preferred for readability. +1
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
On Fri, May 20, 2011 at 1:20 PM, Randall Hansen wrote:
> http://projects.puppetlabs.com/issues/7605
>
> The virtual resource operator:
>
>@user { luke
I'm pretty sure there is an open bug on this, I was looking around on this
the other day. It's related to using stored configs and Puppet/ruby not
closing the connections to the database servers.
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
On
I don't think the issue is necessarily that it's all on one page, the hard
part for me is that one section bleeds into the next section. It's hard to
tell where one leaves off and the next one starts. Some form of break
between sections would make it much more readable.
--
Nathan Clemons
http://ww
I would prefer the verbose form as it definitely is much easier to read.
--
Nathan Clemons
http://www.livemocha.com
The worlds largest online language learning community
On Fri, May 20, 2011 at 1:24 PM, Randall Hansen wrote:
> http://projects.puppetlabs.com/issues/7612
>
> The exported resourc
On 20/05/11 22:24, Randall Hansen wrote:
> http://projects.puppetlabs.com/issues/7612
>
> The exported resources syntax:
>
> @@user { luke: ensure => present }
>
> Is concise and powerful, but very difficult to read. We should
> consider word-based syntax, e.g.:
>
> export @user { luke:
On Sat, May 21, 2011 at 12:01 AM, R.I.Pienaar wrote:
>
>
> - Original Message -
> > On 2011-05-20 22:18, Randall Hansen wrote:
> > > http://projects.puppetlabs.com/issues/7601
> > >
> > > Our very long docs pages are difficult to use. E.g.,
> > > http://docs.puppetlabs.com/references/2.6.
On Fri, May 20, 2011 at 3:15 PM, jcbollinger wrote:
>
>
> On May 20, 3:17 pm, Randall Hansen wrote:
> > http://projects.puppetlabs.com/issues/7600
> >
> > I call this the "agent orange" option :)
> >
> > This works, purging all unmanaged hosts entries:
> >
> > resources { 'host':
> >
On Fri, May 20, 2011 at 3:15 PM, Jordan Sissel wrote:
>
>
> On Fri, May 20, 2011 at 1:20 PM, Randall Hansen wrote:
>
>> http://projects.puppetlabs.com/issues/7605
>>
>> The virtual resource operator:
>>
>>@user { luke: ensure => present }
>>
>> Is relatively easy to type but, if you don’t kno
- Original Message -
> On 2011-05-20 22:18, Randall Hansen wrote:
> > http://projects.puppetlabs.com/issues/7601
> >
> > Our very long docs pages are difficult to use. E.g.,
> > http://docs.puppetlabs.com/references/2.6.8/type.html
>
> I'd disagree on one point. It's not the length of t
19 matches
Mail list logo
