On May 4, 2010, at 9:25 PM, James Turnbull wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/05/10 1:53 PM, Geoff Crompton wrote:
This might be a crazy idea, but it just popped into my head, and I
wanted to know if it's possible. Perhaps not possible right now, but
possible in a theore
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/05/10 1:53 PM, Geoff Crompton wrote:
> This might be a crazy idea, but it just popped into my head, and I
> wanted to know if it's possible. Perhaps not possible right now, but
> possible in a theoretical sense.
>
> Is it possible that puppet cou
This might be a crazy idea, but it just popped into my head, and I
wanted to know if it's possible. Perhaps not possible right now, but
possible in a theoretical sense.
Is it possible that puppet could be modified to be used to manage
switches that have a command line based interface?
When I man
On 05/04/2010 03:00 PM, David Schmitt wrote:
Am 03.05.2010 21:33, schrieb Joe McDonagh:
Hello, I have run into a data corruption problem with naginator that is
fairly difficult for me to track down. Hand-written configurations do
not suffer from this fate. This was present in .24.8, and still pr
Am 03.05.2010 21:33, schrieb Joe McDonagh:
Hello, I have run into a data corruption problem with naginator that is
fairly difficult for me to track down. Hand-written configurations do
not suffer from this fate. This was present in .24.8, and still present
in .25.4. I'd love to complete this auto
On Tue, May 4, 2010 at 10:01 AM, James Turnbull wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Cameron Smith wrote:
> > Thanks for the info James!
> > I'll drop down and try again :)
>
> Cameron
>
> It'd be great if you could the specific issues you had as bug tickets so
> we can be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cameron Smith wrote:
> Thanks for the info James!
> I'll drop down and try again :)
Cameron
It'd be great if you could the specific issues you had as bug tickets so
we can be sure we fix them for Ruby 1.9.x
Thanks
James Turnbull
- --
Author of:
*
On 2010-05-03 19:06, merritt wrote:
I want to be able to add additional resources to my virtual users,
such as force a file or directory to exist if I realize that user, if
someone could point me in the right direction, I’m guessing i need to
use a definition I’m just not sure on the best way to
Thanks for the info James!
I'll drop down and try again :)
On Mon, May 3, 2010 at 3:15 PM, James Turnbull wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 4/05/10 1:32 AM, velvetpixel wrote:
> > First time Puppet user so please bear with me :)
> >
> > Is Puppet 2.5.4 compatible wit
Do you have version 0.25.x puppet clients connecting to version 0.24.x servers?
This looks a bit like that error.
On May 4, 2010, at 5:27 AM, Kent Rankin wrote:
> Can anyone shed any light to this error message? We're getting a
> number of them.
>
> Tue May 04 08:18:35 -0400 2010 ///File[
Can anyone shed any light to this error message? We're getting a
number of them.
Tue May 04 08:18:35 -0400 2010 ///File[/usr/local//]
(err): Failed to generate additional resources using 'eval_generate':
Could not intern_multiple from pson: source did not contain any PSON!
Thanks.
-
hello,
Probably best to send this kind of thing to mcollective's mailing list rather
than puppets :)
- "linuxdatacenter" wrote:
> I've been thinking a lot about running mcollective on my production
> servers recently, especially about its nice integration with puppet
> (using facts and so
I've been thinking a lot about running mcollective on my production
servers recently, especially about its nice integration with puppet
(using facts and so on). However I've got some concern about its
scalability - how publish/subscribe middleware scales in terms of
speed and flooding the network.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 4/05/10 5:59 PM, Patrick wrote:
> I think that Rwolf is puppet 0.2*6*.x.
>
That's correct.
Next maintenance release is 0.25.5 - currently in testing.
Next feature release is Rowlff which doesn't have a version number
assigned as yet and is the f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I?ve just written and released Scaffold
(http://github.com/jamtur01/puppet-scaffold) ? a very simple Puppet
scaffolding templating tool. It integrates with Puppet to create a
variety of Puppet configuration and objects.
You can install it via a gem cu
I want use node_terminus=ldap, not 'exec'.
On 30 апр, 17:25, Michael DeHaan wrote:
> /etc/puppet/manifests/site.pp (which probably loads your nodes.pp) and
> an external node source can be used together.
>
> So if you have an external nodes tool that queries LDAP, it would also
> work with site.p
I think that Rwolf is puppet 0.26.x.
On May 4, 2010, at 12:43 AM, Bernd Adamowicz wrote:
> Ok, found the answer myself. Just installed 25.5-rc2 on client and server and
> tried it. But same error message when parsing the template.
>
>>
Is there an elegant way to use complex facts in puppe
Ok, found the answer myself. Just installed 25.5-rc2 on client and server and
tried it. But same error message when parsing the template.
>
> > > Is there an elegant way to use complex facts in puppet's erb
> templates?
> >
> > Puppet will support hashes in the next major version (Rwolf),
> alth
JRendell writes:
[...]
> I specifically want to use the RPM provider, not the yum provider.
Ah, sorry. I missed that, somehow, and have never used the RPM provider.
I think other people have answered your questions there, though, which I hope
is helpful to you.
Thanks for not hating me for my
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I specifically want to use the RPM provider, not the yum provider.
> Otherwise (as I understand it) I will have to set up a yum repository
> for each machine (or at least environment), and updating/rolling back
> our app will be more complicated than
> > Is there an elegant way to use complex facts in puppet's erb templates?
>
> Puppet will support hashes in the next major version (Rwolf), although I am
> not sure if the interaction between Puppet and Facter will support it.
Dan,
does this mean it will be possible to have a template like this
21 matches
Mail list logo