hi,
it's a stupid example but nevertheless it would be interesting to now
why the following throws a duplicate resource error under puppet 3.7.4
and puppet 4.2.1
test/manifests/init.pp:
# start puppet code
class test inherits test::subclass {
notify { 'hello?': }
}
include test
#end puppet cod
In the message dated: Tue, 27 Sep 2016 13:38:16 -0400,
The pithy ruminations from Christopher Wood on
were:
=> This is one of the first custom facts I wrote, you would likely want to
improve on it based on the guide. However it has worked for us for a few years
now. Enjoy?
=>
=> This lives in
On Tue, Sep 27, 2016 at 02:59:17PM -0400, markbergman...@gmail.com wrote:
> In the message dated: Tue, 27 Sep 2016 13:38:16 -0400,
> The pithy ruminations from Christopher Wood on
> condi
> tion statements.> were:
> => This is one of the first custom facts I wrote, you would likely want to
> imp
I found a thread from March on puppet-dev (Subject Line: End of Life estimate
for Puppet 3.X?)
On which Eric Sorenson said, referring to Open Source Puppet, "As a practical
matter we're going to have Puppet 3.8 on maintenance and security fixes as long as
there's a supported PE version that in
Dan,
That might be a better question for Red Hat as they often support
bundled/associated EOL
products (like ruby 1.8.7) by themselves once the vendor support ends.
On Wednesday, September 28, 2016, Dan White wrote:
> I found a thread from March on puppet-dev (Subject Line: End of Life
> estima
Good idea, but I thought I'd ask in both camps.
Thanks.
Dan White | d_e_wh...@icloud.com
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (Bill Waterson: Calvin
This shows the Satellite lifecycle:
https://access.redhat.com/support/policy/updates/satellite
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsub
Dan,
Disclaimer: I work for Red Hat, not on Satellite, and not in a customer
facing role: jpryor [AT] redhat.com
Red Hat is not customizing puppet 3.8 in Satellite 6 in any way. Puppet
3.8.x as part of of Satellite 6.2 is supported by Red Hat. It has been
publicly stated in presentations at Red Ha
It does, but it does not make any mention of the almost-obsolete Puppet inside
Satellite
Dan White | d_e_wh...@icloud.com
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to con
THAT is the definitive kind of answer I was hoping for.
Many thanks, James.
Dan White | d_e_wh...@icloud.com
“Sometimes I think the surest sign that intelligent life exists elsewhere in the
universe is that none of it has tried to contact us.” (
Hi,
I am working with this module https://github.com/voxpupuli/puppet-nginx to
get some nginx servers up. Here is my hiera config for a vhost:
nginx::nginx_vhosts:
'website1.domain.com':
proxy: 'http://website1.internal'
I would like to have my logs in one directory per vhost.
Here is w
On 9/28/16 3:54 PM, Ugo Bellavance wrote:
> Hi,
>
> I am working with this module https://github.com/voxpupuli/puppet-nginx
> to get some nginx servers up. Here is my hiera config for a vhost:
>
> nginx::nginx_vhosts:
> 'website1.domain.com':
> proxy: 'http://website1.internal'
>
> I woul
Howdy,
After working just fine for a long while, I'm suddenly running into this
error on my puppetmaster and any other host that touches the nagios types.
I'm not even sure where to start. I tried clearing the host from
puppetdb and clearing this host's cache in case something got stuck. No
Howdy,
After working just fine for a long while, I'm suddenly running into this
error on my puppetmaster and any other host that touches the nagios types.
Error: Failed to apply catalog: Could not parse configuration for
nagios_host: undefined method `For=' for
#
I'm not even sure where t
On Wednesday, September 28, 2016 at 4:35:50 PM UTC-4, Garrett Honeycutt
wrote:
>
> On 9/28/16 3:54 PM, Ugo Bellavance wrote:
> > Hi,
> >
> > I am working with this module https://github.com/voxpupuli/puppet-nginx
> > to get some nginx servers up. Here is my hiera config for a vhost:
> >
>
I would prefer not to have to treat these modules any differently than the rest
- the only thing about the problem modules is that they include data files that
need to be pushed intact. Putting them into the control repo would diverge them
from the way we want to handle all other modules, which
The 'site_configs' module is pretty equivalent to the 'data' module you
propose - odd config files, SSL certs, etc. I've been using that
successfully at home and work for over a year with r10k without any issues.
I'm not using 'data in modules' yet but that would let you combine hiera
data with the
On 28/09/16 14:30, Toni Schmidbauer wrote:
hi,
it's a stupid example but nevertheless it would be interesting to now
why the following throws a duplicate resource error under puppet 3.7.4
and puppet 4.2.1
test/manifests/init.pp:
# start puppet code
class test inherits test::subclass {
notify
On 23/09/16 14:16, Matt Raso-Barnett wrote:
require: "Network::If::Static['eth1']"
Should be
require: "Network::If::Static[eth1]"
Since the string form of resource references does not include quotes
around the title - thus it is searching for a resource named "'eth1'"
instead of one
Hi Robert!
Is separating the customer data an option? That would let you manage the
modules without having to increment them constantly, while pulling the customer
data from another location - perhaps from a GIT repository using Puppet's
vcsrepo module.
- Rilindo
-Original Message-
F
On Thursday, 29 September 2016, Rob Nelson wrote:
> The 'site_configs' module is pretty equivalent to the 'data' module you
> propose - odd config files, SSL certs, etc.
Rob
I can't find site_configs on the forge or google. Any pointers?
Thanks
John
--
John Warburton
Ph: 0417 299 600
Emai
Whoops, it's called lab_config in that project (site_config is my private
repo for the home lab) and can be found at
https://github.com/puppetinabox/lab_config. There's not as much to that
since it's a reference project, but for example DNS updates are pushed out
every 15 minutes from it (agents ch
22 matches
Mail list logo
