- Solaris 10 SPARC was end of life on 2021-01-01 - in accordance
with https://puppet.com/docs/puppet-enterprise/platform-support-lifecycle/
These platforms will no longer be included in future puppet-agent
releases from 5th October 2022.
Let us know if you have any questions.
Regards
*Lisa Ross
<
puppet-users@googlegroups.com> wrote:
> Am Donnerstag, dem 12.05.2022 um 11:56 +0100 schrieb Lisa Ross:
>
> Ubuntu 22.04 Agent support is planned for this quarter, we don't have a
> specific timeline just yet as we have other priorities that we are working
> on.
>
>
>
Hi Alex
Ubuntu 22.04 Agent support is planned for this quarter, we don't have a
specific timeline just yet as we have other priorities that we are working
on.
Thanks
Lisa
On Wed, May 11, 2022 at 6:16 PM Alex Rodriguez wrote:
> My apologies, the question was related to Ubuntu 22.04 but my previ
I've invited you to fill out the following form:
Puppet Data Project Beta
To fill it out, visit:
https://docs.google.com/forms/d/e/1FAIpQLSe2Wbxb9UphDqv0lok5hDWMbEI6rAVnKrS2b3zVwSWKToF26g/viewform?vc=0&c=0&w=1&flr=0&usp=mail_form_link
Hi all
We have been developing a beta product that allows fo
I've invited you to fill out the following form:
Puppet Data Project Beta
To fill it out, visit:
https://docs.google.com/forms/d/e/1FAIpQLSe2Wbxb9UphDqv0lok5hDWMbEI6rAVnKrS2b3zVwSWKToF26g/viewform?vc=0&c=0&w=1&flr=0&usp=mail_form_link
Hi All,
We have been developing a beta product that allows f
platforms will no longer be included in future puppet-agent releases.
Let us know if you have any questions.
Regards
*Lisa Ross*
Senior Technical Product Manager | Belfast
lisa.r...@puppet.com
--
You received this message because you are subscribed to the Google Groups
"Puppet Users&q
od_passenger.so"
> 18 }
> 19 file {
> 20 "/etc/apache2/conf.d/passenger.conf":
> 21 mode => 644,
> 22 owner => root,
> 23 group => root,
> 24 alias => "passenger_conf",
>
;s a more
logical spot for it to be:
https://github.com/westr/puppet/tree/feature%2Fmaster%2Fsvc-sysrc
Thanks,
Ross.
--
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
While working on a bunch of freebsd servers, one feature that I found
lacking was the ability to nicely modify rc.conf variables (eg:
item_flags="--something") for installed ports/applications and have a
service do dependency checking so it restarts if it changes.
So a wrote a new puppet type (rcc
I can solve 5 for you. The resource reference syntax is apparently a
magic String object of some sort on its own, and not something that
was being parsed by the original DSL.
So, you simply need to write:
:require => 'File[test123]'
In this case I used the path parameter; test123 is just
the _full
origin_ "database/mysql51-server".
If you've got custom compile options, then you can just make a dependency to
"/var/db/ports//options" so they get compiled correctly as well.
Cheers,
Ross.
--
You received this message because you are subscribed to the Google G
> On Thu, Jun 17, 2010 at 4:23 PM, PBWebGuy wrote:
>> I was just looking over your puppet-puppet recipe and I was curious on
>> how you are managing your different target environments. I see that
>> you have defined different trees for each environment:
>> ...
>> So I am assuming that you must ne
> We're going to set up Puppetmaster and Dashboard, and would like to
> automate the installation process. Have anyone made scripts or puppet
> manifests for installing these and would like to share?
I'm not aware of any specific examples, but do a search at
http://github.com/ if you haven't alrea
I just realized I should've posted here instead of on the puppet-dev
list to get people to test this out.
I've re-written the freebsd package provider for puppet so that it
supports updates and ensure => latest, so if anyone has a freebsd
machine they're willing to test on, that would be awesome.
do?
>
> If you're trying to extract stuff, I would recommend just hooking the
> puppet parser.
>
> Trevor
>
> On Wed, Oct 21, 2009 at 11:28, Cameron wrote:
> >
> > Is there a formal grammar specification defined for the Puppet
> > language (e.g. EBNF)
2009/9/10 David Lutterkort :
> Comments for most files[1] show up as nodes with label '#comment' and a
> value that contains the comment without the leading '#[ \t]*'.
> Therefore, to add a comment, you need to first create a '#comment' node
> and then set it to whatever you want the comment to be
Hi,
I've got a 'define' that I use to set kernel parameters in
/etc/sysctl.conf using the augeas type. It works well, but I'd like
to be able to add a comment line directly above my the parameter to
explain what it does and why it's been changed. We currently just add
a comment in site.pp, but
2009/7/28 Judd :
>
> In any case it's VERY misleading to have an explicit command
> completely ignored by an unstated policy.
>
Personally, I'm not too worried about the security aspects of this,
but I would certainly expect Puppet to do what its told. If I fluff
my permissions, more fool me. H
> Try using: ingroups => ['wheel', 'devel']
I was hoping to keep my users organised in neat classes as per the
Best Practices documentation, rather than have to define all the
groups a specific user is in all in a single place. However, as you
point out, it is a valid work around.
I presume 'in
Hi,
I've read puppet isn't great at handling lots of users, but I've got a
small user base and all my servers are geographically distributed and
hidden behind various firewalls/vpns, making them unsuitable for
centralised authentication that requires a constant connection (eg.
LDAP).
We've previ
per-node control over the removal.
I'm using puppet 0.24.8 on rhel5.3.
Can I get round this, or should I file a bug report?
-ross
Sophos Plc, The Pentagon, Abingdon Science Park, Abingdon, OX14 3YP, United
Kingdom.
Company Reg No 2096520. VAT Reg No GB 348 3873 20.
--~--~-~--~---
ere isn't an appropriate vmware kernel
module for the new version.
Alternatively, use puppet to ensure that all VM's have the necessary packages
required to compile kernel modules.
I guess my main point is, make sure you use the right tool for the job - it may
not be puppet but pup
nitely a good Unix
example of one tool, one job done well and should remain so. Puppet is a better
placed to handle the complexity - for that reason I'm not convinced facter
should ever try access the network for facts: is keeping your puppet node
information in ldap with extra variables not
et
does our "meta package management"...
-ross
--~--~-~--~~~---~--~~
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
I need a custom fact? Anyone write one
> yet? :)
Very unsophisticated but seems to do the job:
Facter.add("productclass") do
setcode do
Facter.value("productname").split(' ')[0]
end
end
-ross
--~--~-~--~~~-
ight knowing that puppet would rather give up at the merest hint of
something a bit "whiffy" than valiantly fire ahead anyway and make some
potentially serious mistakes...
I am running 0.24.5 on the client, 0.24.6 on the server & facter 1.5.0
throughout.
-ross
--~--~-~--~---
puppet-users@googlegroups.com wrote on 26/09/2008 22:20:01:
> puppetmasterd[32231]: RRD library is missing; cannot store metrics
> Any ideas? Thanks.
Take a look at
http://groups.google.com/group/puppet-users/browse_thread/thread/997c5ac71b29cde3/2cd751e3b3d595e5
hth.
-ross
--
nt. I suspect a pretty html page, containing basically
the same info with some additional comments would be sufficient, however.
-ross
--
Ross McKerchar
Systems Analyst, Sophos
Tel: 01235 559933
Web: http://www.sophos.com
Sophos - security and control
Sophos Plc, The Pentagon, Abingdon Science
puppet-users@googlegroups.com wrote on 18/09/2008 23:10:33:
> Try:
>
> http://projects.reductivelabs.com/projects/puppet/issues/new
Thanks James: Bug filed at
http://projects.reductivelabs.com/issues/show/1583
--
Ross McKerchar
Systems Analyst, Sophos
Tel: 01235 559933
to track the ticket down without much effort.
I'm now running 0.24.5 & still have the same problem. I also tried Nigel's
fix @
http://github.com/nigelkersten/puppet/tree/c1a6adb84ecdcc1c2a2657b4d603c96ae3282125/lib/puppet/provider/nameservice/directoryservice.rb
but it didn't h
Thanks for this, the snippet below worked great, with a couple of minor
changes, on my CentOS 5 system:
- full path to /usr/bin/test
- single equal in 'false' test
Thanks Francois!
Regards
Darryl
Francois Deppierraz wrote:
> Darryl Ross wrote:
>
>> What is the recom
Hi All,
What is the recommended way of managing something like the postfix
configuration file? I would prefer _not_ to overwrite the config file with one
stored centrally or using the templating system.
Ideally I'd like to use the 'postconf' and 'postconf -e' programs to get and
set options.
Ha
32 matches
Mail list logo
