Hi Walter,
[ CCing the augeas-devel list, as that's the best place for Augeas lens
problems and help ]
On 22/01/12 20:48, Walter Heck wrote:
> Hi all,
>
> I'm trying to come up with a lens for the zabbix agent config files. I
> find the lens language untransparent at best, so I'm struggeling to
Thanks for the pointers Dominic, I'll check them out later this week
and report back with my findings!
On Mon, Jan 23, 2012 at 11:34, Dominic Cleal wrote:
> Hi Walter,
>
> [ CCing the augeas-devel list, as that's the best place for Augeas lens
> problems and help ]
>
> On 22/01/12 20:48, Walter H
Hello,
I am trying to setup a template with data being passed in as a long
string of data which is being returned via extlookup()
i.e. $resolvers = "10.10.10.10 11.11.11.11.12.12.12.12"
The template should split those up and put a nameserver entry per line
in /etc/resolv.conf
I have this in the
Hi,
On 01/20/2012 11:34 PM, Cody wrote:
> Defining all somewhat common packages in a central location becomes
> unrealistic when you no longer "control" the code that is in every
> module you use. If you obtain five modules from the forge and they
> all require a specific package and so all defin
Hi,
Is that variable declaration copied correctly?
> $resolvers = "10.10.10.10 11.11.11.11.12.12.12.12"
Should be
> $resolvers = "10.10.10.10 11.11.11.11 12.12.12.12"
what's that do for you?
Cheers
Den
On 23/01/2012, at 22:57, "ollies...@googlemail.com"
wrote:
> Hello,
>
> I am trying to s
On Jan 23, 1:17 pm, Denmat wrote:
> Hi,
>
> Is that variable declaration copied correctly?
>
> > $resolvers = "10.10.10.10 11.11.11.11.12.12.12.12"
>
> Should be> $resolvers = "10.10.10.10 11.11.11.11 12.12.12.12"
>
> what's that do for you?
>
That was a typo in my original mail. The syntax pro
Absolutely beats me.
Is this a verbatim paste from your template?
Are you certain that the template is the source of the error?
Does it say anything beyond "syntax error"?
Just pasting puppet output would be ideal.
Cheers,
Felix
On 01/23/2012 12:57 PM, ollies...@googlemail.com wrote:
> I have t
guys any other suggestions ?still i am not able to find the error.
On Jan 22, 12:02 am, bhagyesh wrote:
> [root@PROXY-03 puppet]# puppet apply networking/manifests/init.pp -d -
> e 'include networking::resolver'
> debug: importing '/etc/puppet/modules/networking/manifests/init.pp' in
> environmen
On Jan 23, 1:32 pm, Felix Frank
wrote:
> Absolutely beats me.
>
> Is this a verbatim paste from your template?
> Are you certain that the template is the source of the error?
> Does it say anything beyond "syntax error"?
>
> Just pasting puppet output would be ideal.
>
host: parse of /etc/resol
Thanks, I didn't realize it had to be a local file.
On Jan 20, 5:07 pm, Josh Cooper wrote:
> Hi,
>
>
>
>
>
>
>
>
>
> On Fri, Jan 20, 2012 at 2:47 PM, tborthwick wrote:
> > Hello,
>
> > I've set up a puppetmaster on red hat and a client on windows 7
> > (puppet version 2.7.9 on both), and I'm get
I added a bunch of yumrepo resources to my node definitions and thought I'd
finish it with a
resources { 'yumrepo': purge => true, }
But when I tried to run it, I get this:
err: Failed to apply catalog: Parameter purge failed: Purging is only supported
on types that accept 'ensure' at /etc/pu
The way my environment setup is that we have puppet dashboard handles ALL node
registration as well as class assignment. We simply declare different groups,
assign them with classes, and assign nodes into those groups for different
roles.
So we have zero usage for another node resources and we
I was working with yumrepo, defining new entried and seeing them appear in
/etc/yum.repos.d
After considerable tinkering, and with the sad discovery that resource {
'yumrepo': purge => true } does not work,
I moved my working /etc/yum.repos.d to /etc/yum.repos.d-old and re-ran my
catalog.
To
Hey there,
If you're going through all that, and are trying to get a purge-able
directory of resources, would you find it easier to declare the
/etc/yum.repos.d directory with purge => true, and then declare your repos
as file declarations? An exec of 'yum -makecache' set to refreshonly =>
true co
- Original Message -
> Hey there,
>
> If you're going through all that, and are trying to get a purge-able
> directory of resources, would you find it easier to declare the
> /etc/yum.repos.d directory with purge => true, and then declare your
> repos as file declarations? An exec of 'yu
On 01/23/2012 02:48 PM, ollies...@googlemail.com wrote:
> host: parse of /etc/resolv.conf failed
> ./resolver/templates/resolv.conf.erb:7:in `result': compile error
> (SyntaxError)
> ./resolver/templates/resolv.conf.erb:4: syntax error
> _erbout.concat(( scope.lookupvar('resolver::params::resolvers
On Mon, Jan 23, 2012 at 6:55 AM, tborthwick wrote:
> Thanks, I didn't realize it had to be a local file.
I've updated the package description on the Windows wiki page:
http://projects.puppetlabs.com/projects/puppet/wiki/Puppet_Windows?version=63
Josh
--
Josh Cooper
Developer, Puppet Labs
--
Using the instructions I found here:
http://docs.puppetlabs.com/guides/installing_dashboard.html
I've run into a snag at the point where you run:
rake RAILS_ENV=production db:migrate
It fails with the following error:
puppet-dashboard]# rake RAILS_ENV=production db:migrate (in
/root/puppet-dash
Yes, I could do it that way and I did before i realized that there was a
yumrepo resource.
Let me try a different approach: Is there something in the yumrepo resource
definition that will let me remove the info from the system ? I can live with
just disabling the repo, but I have some rabid s
- R.I.Pienaar wrote:
> - Original Message -
> > Hey there,
> >
> > If you're going through all that, and are trying to get a purge-able
> > directory of resources, would you find it easier to declare the
> > /etc/yum.repos.d directory with purge => true, and then declare your
> > repo
On Mon, Jan 23, 2012 at 03:09:49PM +, Dan White wrote:
> I added a bunch of yumrepo resources to my node definitions and thought I'd
> finish it with a
>
> resources { 'yumrepo': purge => true, }
>
> But when I tried to run it, I get this:
>
> err: Failed to apply catalog: Parameter purge
That the problem is known is a comfort.
I will trash my way around it one way or another, and if I come up with any
neato tricks for removal of a repo, I will contact the list and/or the Feature
Assignee :)
“Sometimes I think the surest sign that intelligent life exists elsewhere in
the unive
On Jan 23, 4:32 pm, Felix Frank
wrote:
> On 01/23/2012 02:48 PM, ollies...@googlemail.com wrote:
>
> > host: parse of /etc/resolv.conf failed
> > ./resolver/templates/resolv.conf.erb:7:in `result': compile error
> > (SyntaxError)
> > ./resolver/templates/resolv.conf.erb:4: syntax error
> > _erbo
Is your issue resolved? It looks like you don't have the correct erb
syntax in your loop
*<%=* scope.lookupvar('resolver::params::resolvers').split(/\s+/).each
I think should be
*<%* scope.lookupvar('resolver::params::resolvers').split(/\s+/).each
On Mon, Jan 23, 2012 at 4:00 PM, ollies...@go
While Puppet allows us to manage a large number of instances on EC2,
what are the best practices for caching packages on EC2??
Instead of manually configuring yum or apt proxies on each node, it
would save us lots of time if caching could be "somehow" handled by
Puppet. Are there any plans to add
What version of rubygems do you have? I suspect there is some type of
mismatch somewhere, but I could be wrong.
More information would be great:
OS
ruby version
rubygems version
gem list
Thanks
stahnma
On Mon, Jan 23, 2012 at 9:07 AM, Peter Berghold wrote:
> Using the instructions I found h
On Mon, Jan 23, 2012 at 1:21 PM, Rayson Ho wrote:
> While Puppet allows us to manage a large number of instances on EC2,
> what are the best practices for caching packages on EC2??
>
> Instead of manually configuring yum or apt proxies on each node, it
> would save us lots of time if caching could
On Mon, Jan 23, 2012 at 5:14 PM, Michael Stahnke wrote:
> How would Puppet handle it? It would still have to either cache the
> package locally (eating lots of disk space) or point to a proxy, which
> you can do with Puppet already. Your simplest solution might be to
> look for a mirror hosted i
On Mon, Jan 23, 2012 at 5:15 AM, Felix Frank <
felix.fr...@alumni.tu-berlin.de> wrote:
> Hi,
>
> On 01/20/2012 11:34 PM, Cody wrote:
> > Defining all somewhat common packages in a central location becomes
> > unrealistic when you no longer "control" the code that is in every
> > module you use. I
Nigel,
Just so we understand the requirements of this - what would it take to make
a function that
is usable in way that a few of us have mentioned - something that lets us
say "If a class
is included in this host, then X". It seems like this would be desirable
functionality and so
far everything
I've created a module to manage mounting LUKS encrypted devices at
https://github.com/jaredcurtis/puppet-encmount
It's a wrapper around the existing mount type and accepts the
additional input needed to unlock the LUKS device (key and mapper
name). It's untested outside of CentOS and does use some
This is sort of hackish but not too bad... set a list of file resources
that are the resultant names of the /etc/yum.repos.d/.repo files, and
purge everything else in that directory.
class yum::cleanup {
# shorthand for the repo directory
$rd = "/etc/yum.repos.d"
# clean the yum.rep
On Jan 23, 9:07 pm, Guy Matz wrote:
> Is your issue resolved? It looks like you don't have the correct erb
> syntax in your loop
>
> *<%=* scope.lookupvar('resolver::params::resolvers').split(/\s+/).each
>
> I think should be
>
> *<%* scope.lookupvar('resolver::params::resolvers').split(/\s+/).
On Jan 24, 7:14 am, "ollies...@googlemail.com"
wrote:
> On Jan 23, 9:07 pm, Guy Matz wrote:
>
> > Is your issue resolved? It looks like you don't have the correct erb
> > syntax in your loop
>
> > *<%=* scope.lookupvar('resolver::params::resolvers').split(/\s+/).each
>
> > I think should be
>
34 matches
Mail list logo
