I'm trying to nest arrays within puppet to use in an ERB template... is
this something thats supported in puppet.
Im defining my variable as:
$var = [ [ foox, fooy ], [ barx, bary ] ]
Within my erb template, I'm doing:
var.each { |x,y|
%>
X: <%= x %>
Y: <%= y %>
<%
}
%>
This
Just checking if these came out of order. Is this working or not for you?
-- bk
Karl Bowden wrote:
> On Tue, Apr 7, 2009 at 11:46 AM, Karl Bowden wrote:
>> On Mon, Apr 6, 2009 at 11:59 PM, Bryan Kearney wrote:
>>> agentk wrote:
I'm not sure if I'm kicking tyres again, but first off: I lik
>
>
> Why Puppet cant have a push directive as well? obviously we already
> have the infrastructure to connect from the server to the clients
> (e.g. puppetrun, or my xinetd version), we already have all of the
> puppet types, so it should be easy to execute on a client (possible
> today w
Sorry, my statements could have been clearer.
The example you listed works great in augtool. It was just the syntax
I hoped for.
It seems that puppet is balking on the /dir[.='/path'] syntax though.
Only on the second augeas run when the changes get applied to the
filesystem as the log files cor
Luke Kanies wrote:
> On Apr 6, 2009, at 4:37 PM, David Lutterkort wrote:
>
>>> What do you think?
>> I am also much in favor of #2. I can see that relicensing as LGPL
>> might
>> make some sense.
>
> That seems to be the majority view so far, but there are still plenty
> of concerns about th
Kyle Cordes wrote:
> Luke Kanies wrote:
>> As is probably obvious, I've scaled back my free online support and my
>> attempts at fixing every bug ever, but a certain amount is still
>
> There is dangerous territory nearby: Paying customers have a higher
> expectation of a smooth out-of-box-e
On Tue, 7 Apr 2009, Bryan Kearney wrote:
> Kyle Cordes wrote:
>>
>> There is dangerous territory nearby: Paying customers have a higher
>> expectation of a smooth out-of-box-experience, than open source users;
>> to make this happen it is necessary to debug vigorously. However, open
>> source use
Thanks for the feedback, Larry,
> - The hardening module I would break out each of these services into
> separate modules, so it's more generic. The hardening class itself I
> would consider a 'role' that would then include all of these modules
> (I have roles exist in the manifest folder and ca
Jason Slagle wrote:
> On Tue, 7 Apr 2009, Bryan Kearney wrote:
>
>> Kyle Cordes wrote:
>>> There is dangerous territory nearby: Paying customers have a higher
>>> expectation of a smooth out-of-box-experience, than open source users;
>>> to make this happen it is necessary to debug vigorously. Ho
Luke Kanies wrote:
> Considering how many people have told me they don't buy support
> because they find Puppet so easy that they just don't need help, I'm
> not too concerned about this yet.
I think you're getting a false signal from this. I am confident that
tools in/around Puppet to make
Andrew Shafer wrote:
> The way I saw it before your email (and this isn't just in regard to
> Puppet) was a classification of support customers handful of overlapping
> categories. For example
> 'bought support as a company policy',
> 'recognized the value of the project and bought support t
Hallo Stephen,
> Well the two things I missed were: A documentation outlining all the
> steps being done, and that this is more of a hardening document. It
> can't bring a system to EAL3/4/x because the hardware and other parts
> need to be evaluated in toto by some 'authority'.
Yes, a more deta
Thanks for the feedback, Larry,
> - The hardening module I would break out each of these services into
> separate modules, so it's more generic. The hardening class itself I
> would consider a 'role' that would then include all of these modules
> (I have roles exist in the manifest folder and ca
Thanks for the feedback, Larry,
> - The hardening module I would break out each of these services into
> separate modules, so it's more generic. The hardening class itself I
> would consider a 'role' that would then include all of these modules
> (I have roles exist in the manifest folder and ca
Thanks for the feedback, Larry,
> - The hardening module I would break out each of these services into
> separate modules, so it's more generic. The hardening class itself I
> would consider a 'role' that would then include all of these modules
> (I have roles exist in the manifest folder and ca
I can set schedules, and those work fine. What I am trying to prevent is (my)
stupidity of accidently scheduling something that runs during the day. I will
then over-ride the default with anything that should be checked during the day.
I found where the default schedule is defined, and could m
On Tue, Apr 7, 2009 at 1:27 AM, Andrew Shafer wrote:
> The way I saw it before your email (and this isn't just in regard to Puppet)
> was a classification of support customers handful of overlapping
> categories. For example 'bought support as a company policy', 'recognized
> the value of the pr
Ok, the error's are still the same with puppet-0.24.8. But I had to
change the way I quoted args in changes lines for it to work.
If I use an [.='somevalue'] def in an augeas changes var in puppet I'm
still getting: change from need_to_run to 0 failed: Save failed with
return code false
I have c
> That's not how the model tends to work though. Usually the
> paid community gets the product first with the community
> version lagging behind by a release.
Huh? Not in Red Hat's model:
Fedora -> RHEL
JOPR -> JON
Spacewalk -> Satellite.
The community version leads, not lags.
-Peter
--~
On Tue, 7 Apr 2009, Burkholder, Peter wrote:
>> That's not how the model tends to work though. Usually the
>> paid community gets the product first with the community
>> version lagging behind by a release.
>
> Huh? Not in Red Hat's model:
>
> Fedora -> RHEL
> JOPR -> JON
> Spacewalk -> Satel
On Apr 7, 2009, at 6:14 AM, Kyle Cordes wrote:
> Luke Kanies wrote:
>> Considering how many people have told me they don't buy support
>> because they find Puppet so easy that they just don't need help, I'm
>> not too concerned about this yet.
>
> I think you're getting a false signal from this. I
On Apr 7, 2009, at 11:05 AM, Jason Slagle wrote:
>
>
>
> On Tue, 7 Apr 2009, Burkholder, Peter wrote:
>
>>> That's not how the model tends to work though. Usually the
>>> paid community gets the product first with the community
>>> version lagging behind by a release.
>>
>> Huh? Not in Red Hat'
On Tue, Apr 7, 2009 at 8:45 AM, Michael Semcheski wrote:
> I don't want to
> hear that I have to file a bug report - I'd rather open a trouble
> ticket, upload my log files, and let a level 1 technician write the
> bug report and give me the solution. What it comes down to is my
> employer can
I'm new to puppet, and I'm hoping to use it to configure our
production apps, each of which is configured from a single Java
properties file.
So we have a lot of redundant properties in these files, and I'd like
to consolidate them using puppet. For example, I'd like to "roll up"
these properties
On Tue, Apr 7, 2009 at 2:48 PM, Andrew Shafer wrote:
> I've been on both sides of this equation many times and my experience has
> always been that every intermediary in the communication loses/distorts
> information, so if I really want something to be fixed the best strategy
> always seemed to
I got puppet working with the LDAP search. It had to do with
authentication to my LDAP server.
Thanks for your help.
NOW, I have a bigger question for the Puppet Community. Here is a
small explanation as to what I am trying to accomplish with puppet and
package distribution:
We are a K-12 schoo
Hey all,
I have recorded my steps towards getting puppet functional
through one of the four different methods that I can think of, which
are:
1.Source(copying and insatlling to the recommended unix FSH
directory, /usr/local/src)
2.pkg hosted at explanatorygap
3.MacPorts
4.RubyGems
I haven't c
Hi Allister,
I am in no way a puppet expert, but I do have puppetmaster running on
MacOS 10.5.6 server and puppet on MacOS 10.5.6 clients.
I am using Nigels packages from
https://sites.google.com/a/explanatorygap.net/puppet/. I am using the
facter-1.5.2 and puppet-0.24.7 packages.
I have a ver
Hello again Ohad
I've finally found some time to play with this.
I'll give you the back of the proof of concept version and i'll write
some doco for the site when i get a chance.
I've done two facts which are probably written in the worst way
possible, but i haven't done this before :)
[r...@t
On Tue, Apr 7, 2009 at 3:39 PM, Marcus Rowell wrote:
>
>
> I believe that puppet doesn't use specific a puppet user on the mac
> and just runs as root.
>
I think when I get around to making a puppetmasterd-oriented package for OS
X, that we will create a puppet user/group for the server, as that'
On Wed, Apr 1, 2009 at 10:10 AM, Ryan Steele wrote:
>
> You're not properly setting your name in the control/changelog file
> this way. I'd like to put a mixture of both of our processes on the
> wiki - if I can't do so already, I'll bug jamtur to give me access.
It does actually. The uupdate s
I haven't seen a way to do this, because puppet's configuration has limited
datatypes.
To do something similar, I encoded the same data in strings.
I used this snippet in my manifest:
sources => ["key1/host1:1234", "key2/host2:1234"]
And this snippet in my template:
<%# syntax is "/" %>
<% sou
Ok I've got it sorted now and I'll submit the recipe to the wiki after
somebody here reviews it as I'm only new to puppet.
After writing tests in ruby with the libaugeas-ruby bindings it turns
out the problem is that the bindings do not like set values to be
quoted.
Works:
set \"/dir[.='<%= name
Hi chakkerz,
First of all thanks for putting the effort in this.
secondly, I'm not sure, but what is the difference between what you just
implemented with normal schedule meta parameter?
schedule allows you to decide how often a certain resource would be
checked/applied, and if I understood your
On Tue, Apr 7, 2009 at 8:32 PM, Larry Ludwig wrote:
>
>
> What xinetd version?
I wrote a simple daemon which uses puppet certificates and namespaceauth to
allow puppetrun on cron based hosts.
cheers,
Ohad
--~--~-~--~~~---~--~~
You received this message because yo
Ohad Levy schrieb am 08. Apr 2009 um 05:14:14 CEST:
> I think I'll enhanced my mini puppet listener script and post it if anyone
> would be interested...
That would be great.
Helmut
--
-
Helmut LichtenbergTel.: 05034/8
36 matches
Mail list logo
