Hi Ohad,
> if you are interested in using foreman, see
> http://blog.theforeman.org/2012/01/getting-foreman-search-results-into.html
>
I currently do not use foreman, but this is good incentive to look into it.
Thank you very much.
Joe
--
Joe Topjian
Systems Administrator
C
st via a Puppet function. The built-in extlookup()
> function provides an approach of this sort. Hiera provides a more
> flexible approach of the same kind, and it will be a built-in starting
> with the next major version of Puppet (Telly).
>
Thank you for the options - it's app
useful. Thank you!
> Its worth noting that once the next generation of storeconfigs comes out
> (which is REALLY soon), it will have better APIs to support these kinds of
> functions and I intend to write puppet functions that support these kinds
> of use cases.
>
Good to know
he command has
just hung.
Similarly, running strace on the process results in an infinite output of
select.
ctrl-c does not kill the process - I have to kill the PID from another
terminal.
I cannot reproduce this issue at will -- it seems to happen randomly.
Thanks,
Joe
--
Joe Topjian
Systems A
st need to wait* for the 2.7.12 or
> later version of pupet to make it to the debian packages for Ubuntu then
> I should be able to test.
>
It's very disappointing / frustrating that Ubuntu LTS stocks 2.7.11 by
default. :/
Thanks,
Joe
--
Joe Topjian
Systems Administrator
Cybera Inc
nd then maintain that non-stock version from
there on out) or will have to put up with the bug mentioned in this thread
as well as miss out on built-in puppet module support.
All of which would not be necessary if 12.04 just shipped with 2.7.12+.
The comment was more whining on my part
apache/pull/37/files
Here, on all but one of the vhost entries, you mark ensure_dirs as false
and Puppet will not enforce the existence of the two directories. This
works, but it comes off as a workaround more than a proper solution.
Any ideas?
Thanks,
Joe
--
Joe Topjian
Systems Administrator
ughts?
>
The only thing I am curious about now is the difference between this and a
virtual resource? Maybe I was under the wrong impression about virtual
resources... I thought that they did this same thing.
Thank you for your help and work with this!
Joe
--
Joe Topjian
Systems Administrat
ensure_resource.rb:24
Thanks,
Joe
--
Joe Topjian
Systems Administrator
Cybera Inc.
www.cybera.ca
Cybera is a not-for-profit organization that works to spur and support
innovation, for the economic benefit of Alberta, through the use
of cyberinfrastructure.
--
You received this message because
>
> I made a few inline comments
>
Thank you.
> should be fixed in master.
>
Yup, looks good. I will open a pull request for this.
--
Joe Topjian
Systems Administrator
Cybera Inc.
www.cybera.ca
Cybera is a not-for-profit organization that works to spur and support
inno
c file and then use
the puppet module.
I am not 100% confident of this solution, though, since I'm not sure if
resolvconf will recreate the symlink at some point -- I haven't used this
solution enough to confirm that.
Thanks,
Joe
--
Joe Topjian
Systems Administrator
Cybera Inc.
www.cyber
>
> if /etc/resolv.conf is a puppet maintained file, even if resolvconf
> package is updated, it will be replaced by the puppet asserted file anyway.
>
Very true, but I would hate to have two services fighting with each other
in that way.
--
Joe Topjian
Systems Administrato
s discussion on the web visit
> https://groups.google.com/d/msg/puppet-users/-/lkxkivCib8YJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this
Hi Nan,
Like everyone else, I think this is great.
> Run pocco against a modules directory:
>
> pocco /etc/puppet/modules/
>
Just a quick comment: Isn't pocco the name of the Python *occo? (
http://fitzgen.github.com/pocco/) should the name be changed
to differentiate?
Joe
puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
>
>
--
Joe Topjian
Systems Administrator
Cybera Inc.
www.cybera.ca
C
unsubscribe from this group, send email to puppet-users+unsubscribe@**
> googlegroups.com .
> For more options, visit this group at http://groups.google.com/**
> group/puppet-users?hl=en<http://groups.google.com/group/puppet-users?hl=en>
> .
>
>
--
Joe Topjian
Systems Admini
ps
> "Puppet Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to puppet-users+unsubscr...@googlegroups.com.
> To post to this group, send email to puppet-users@googlegroups.com.
> Visit this group at http://groups.google.com/group
Hello,
I keep running into several parsing issues in 3.5 that don't exist in
Puppet 3.4.
I saw the thread about issues with the future parser and defined types:
https://groups.google.com/forum/#!topic/puppet-users/HOVnQ1EXwjY
I'm using the future parser, but I'm seeing issues in other manifest
Hi Henrik,
On Saturday, May 10, 2014 2:56:19 PM UTC-4, Henrik Lindberg wrote:
In 3.5 the new evaluator was added and it is on by default when using
> --parser future. If you want to turn it off you can use --evaluator
> current in addition to --parser future)
>
> If it works under --evaluator
Hi Henrik,
In 3.5 the new evaluator was added and it is on by default when using
> --parser future. If you want to turn it off you can use --evaluator
> current in addition to --parser future)
>
> If it works under --evaluator current but not under --evaluator future,
> we like to hear about i
20 matches
Mail list logo
