Greetings,
I am having an issue with Hiera again. Bangin my head on it for a few hours
and not getting anywhere. Since this group was able to help last time, I
have my fingers crossed you can help me again. :-D
I am trying to use JSON with Hiera this time.
First, fully updated dev box.
$ cat
Greetings,
I am really stuggling here and would love another set of eyes. After a
failed attempt to migrate to Puppet 4 (my crappy modules need more work
then I have time for), I went back to Puppet 3. Only this time, I have the
chance to improve upon where things went wonky last time.
The
On Monday, August 10, 2015 at 3:23:46 PM UTC-5, Christopher Wood wrote:
I haven't set up puppetdb with the puppetlabs-puppetdb forge module in
over 18 months, but depending on your module version you may need to tweak
parameters. Quoth:
The PuppetDB module now supports PuppetDB 3.0.0 by
Now that I have a working example to figure out what puppetdb is doing, I
was able to figure out the other issues with ssl and connections.
Thanks again!!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop
Greetings,
I am building out a new puppet master system based on 4. Razor and
Dashboard are two projects that I never got around to implementing before,
but since I have some motivation (and time from those on high to spend
working on puppet) I thought it would be nice to have them in my new
Greetings,
I need help; I have been going in circles for too long now and I am sure it
is something silly that I over looked. I am attempting to use environments
with a new server build for Puppet 4 (never could get it working under the
Puppet 3 series; but I never put /that/ much effort into
On Thursday, July 23, 2015 at 6:05:27 PM UTC-5, Ellison Marks wrote:
No, the environment variable is set in the puppet.conf of every host. I'm
not even sure what the effect would be of trying to define environment in
hiera.
Please see:
On Wednesday, July 22, 2015 at 4:06:51 PM UTC-5, Kevin Corcoran wrote:
We added a new feature in Puppet Server 2.1.0 which allows it to be used
with Puppet 3 agents (as well as Puppet 4 agents, of course).
On Tuesday, July 21, 2015 at 9:14:04 AM UTC-5, jcbollinger wrote:
Questions!
1a)
I am debating as to whether I need to build multiple puppet masters or
not. Is the following documentation still valid for the 4.x series of
puppet?
On Tuesday, July 21, 2015 at 9:44:45 AM UTC-5, Martijn wrote:
Op dinsdag 21 juli 2015 01:28:09 UTC+2 schreef Stack Kororā:
If I am willing to take the time to migrate to puppet-forge modules
anyway (plus hopefully fix any bad code I can't replace), wouldn't this be
a good time to switch
On Tuesday, July 21, 2015 at 11:33:29 AM UTC-5, Felix.Frank wrote:
On 07/21/2015 04:14 PM, jcbollinger wrote:
2)
I read in the changelog that the older clients should work with the
backward compatibility, but is it worth even trying? Or should I just push
out the updated puppet
One last update on my progress.
I have 4 installed on Scientific Linux with the only client being itself at
the moment. The current plan is to either find replacement modules or move
over as many modules as I can. If I can get the bulk of the modules and a
few important ones, then I will be
Greetings,
First, a short intro. :-)
Last year I invested quite a bit of time building out a puppet
infrastructure. I have +150 Scientific Linux 6 and RHEL 6 servers running
puppet 3.7.1. It has been working really well concidering that I basically
haven't touched it since last October
On Friday, October 10, 2014 9:18:03 AM UTC-5, jcbollinger wrote:
Even if the agent runs as root, there can still be access controls (e.g.
SELinux policy) that prevent it from reading certain files that can be read
by commands you launch directly from a shell.
OMG. If that was the
Greetings,
So yeah. I spent several hours hacking away at adding hiera data to a bunch
of my modules. I haven't seen any weirdness going on. I wish there had been
/any/ kind of indication in puppet about trying to read this file but I
don't have permission/access rights. That would have saved
Wow! Thanks for the responses John!
On Thursday, October 9, 2014 8:52:00 AM UTC-5, jcbollinger wrote:
If the master had successfully looked up your datum then the result would
have been as you expected. The behavior you present is characteristic of
(and well documented for) the case where
On Thursday, October 9, 2014 12:49:40 PM UTC-5, Tony Thayer wrote:
Couple of things I noticed:
Your testhiera/manifests/init.pp file looks a little odd. I re-wrote it a
bit and it ran without a hitch.
class testhiera {
$test = hiera('testhiera::test')
notice(Test is ${test})
file {
Greetings,
I don't know why, but I am having a rough time trying to get hiera to
work. It seems to me that all the examples I see online are either absurdly
complex or so stupidly simple that they are absolutely useless. Either way
I have found the documentation for hiera completely
Greetings Corey,
Thank you for your advice.
If it was as simple as the clientcert being wrong, then it should have been
hitting the default hiera option, but it wasn't pulling back anything at
all. I honestly don't think it was even looking at hiera as I saw nothing
about it in the logs.
We
In case anyone else struggles with Hiera and needs a simple example:
https://github.com/cstackpole/SimpleHiera
That is my code so you don't have to try to cut'n'paste out of a forum
post. If I learn anything else useful, I will shove it into the repo too.
~Stack~
--
You received this message
OK, I am beginning to question either puppet+hiera's reliability or my
sanity...
I have code I am working on. It is existing code in which has a bunch of
variables prime for hiera use. I pull one variable out of the code into
hiera for testing and it works well. Tweak the code and now I am
Just so that the code is out there and my point made.
$ cat hieradata/hosts/puppet.test.vm.yaml
---
repos::reponetwork: one
repos::testvar: repotestvar
testhiera::test: blah
testhiera::testvar: testhieratestvar
$ cat modules/testhiera/manifests/init.pp
class testhiera ( $testvar =
Ack! So I put the '$testvar = $repos::testvar' line in the class header for
both the init.pp and the epel.pp (which is a subclass in repos). I removed
it out of epel.pp and the init.pp started to print!!! That makes zero sense
to me! So I removed it and the notify out of init.pp and put them in
if it will work, but have you tried adding provider = rpm in
the package resource?
Regards,
El 23/07/2014 02:37, Stack Kororā i.am@gmail.com javascript:
escribió:
Greetings,
In my multiple hundred servers, I have 10 that are Red Hat based. We
recently brought them under the same management
On Wednesday, July 23, 2014 3:38:26 AM UTC-5, mawi wrote:
Hi Stack,
Not sure if this is doable for you, but maybe you can create a schedule to
schedule your RedHat package removals.
http://docs.puppetlabs.com/references/latest/type.html#schedule
For example create a schedule to run this
Greetings!
Thank you so much John. I just learned something new about Puppet. Utilizing
inline_template is a heck of a lot easier then how I first attempted that
variable substitution. I might have to go back and fix some of my older code
later
Here are a few other notes in response
Greetings,
In my multiple hundred servers, I have 10 that are Red Hat based. We
recently brought them under the same management as the rest of the servers
utilizing Puppet. Then we ran into issues because we were hitting RHN too
frequently and we got our servers banned. :-(
I went digging for
Greetings,
Huh. I don't know why, but for some silly reason I thought I had to use
subclasses with arrows. I will re-work my script with them and see how it
goes.
Thanks! I appreciate the suggestion.
--
You received this message because you are subscribed to the Google Groups
Puppet Users
Greetings,
Thanks for the response.
The pkginventory is already doing this inside of util/pkg.rb:
rpm -qa --qf %{NAME}\t%{VERSION}-%{RELEASE}
I am fully aware of how multiple kernels work. As stated, the kernel was
just an example. I need/want every package installed returned to me and the
Greetings,
I am trying to puppetize a process that goes like this:
1) remove package a.i386
2) create repo file
3) install package a.x86_64 from repo
4) update config_file_1
5) update config_file_2
6) update config_file_3
7) start service
Shouldn't be too hard right? Except I have played with
Greetings,
I am using ody/pkginventory [http://forge.puppetlabs.com/ody/pkginventory] as a
way of getting information about what rpms are installed on a system. I am
using this module over `puppet resource package` for two reasons: 1) Having it
as a fact helps some of the other things we are
Thanks for the replies. I don't have it working quite yet, but I am working
on it.
Yeah, I am steering clear of augeas right now because it has terrible
support on SLES which unfortunately makes up a decent chunk of the
datacenter. So whatever I do I need to work across Scientific, RH, and
Greetings,
I am currently managing a configuration file for an application with
puppet+file_line and so far everything is going well. I have about 30 rules
that I need to ensure are in the configuration file. The tricky part is
that the rest of the file I don't care about but some admin
Just wanted to say Thanks! again. The example helped out quite a bit and
I was able to get it functioning the way I wanted it to (at least so far!
:).
Thanks!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and
On Thursday, June 27, 2013 6:33:37 AM UTC-5, Ken Barber wrote:
* The ports that all nodes share in common I am adding to the
modules/my_firewall/manifests/init.pp file, but the ports that are
specific
to a node I am adding to the node definition in manifests/site.pp. What
should I
Thank you very much Joe. I think this exactly the path that I need but I am
having trouble with it.
As I said, I have multiple systems that this repo class watches over. Thus,
for one of several instances, I have things like:
if $osfamily == 'RedHat' {
class {'repos::epel': }
}
The
Greetings,
I have a question about best practices for the puppet firewall module. I
have pasted my basic config files below and I am curious about a few things.
* The ports that all nodes share in common I am adding to the
modules/my_firewall/manifests/init.pp file, but the ports that are
Thanks for the quick reply! And the example! Let me review this and try it
out. I will post back if I run into any issues.
Thanks again!
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To unsubscribe from this group and stop receiving emails
Greetings!
tl;dr Why doesn't require=Class work?
I have a module I built that I creatively called repos. This does a
number of things for me:
* I have many systems on different networks. Depending on the network
depends on which repository the servers get their packages from.
* I have many
Greetings!
Thanks for all the pointers in the right direction. I was finally able to
figure it out today. I figured I would post my solution in case someone
else finds this thread later on and might be able to use it. I am running
this on a few servers successfully, but again, I just figured
Greetings!
I am having a problem with puppet mounting a device and am hoping someone
can help. Here is the short version, if you have questions or need more
detail, please feel free to ask.
I have a Panasas storage device on my network on which my home directory
resides. The Panasas device
On Tuesday, April 9, 2013 9:56:11 AM UTC-5, Jonathan Stanton wrote:
[snip]
If those are enabled, you may find that things you can do as a root user
don't work when run from cron or from a daemon process.
If this is RHEL/Centos then try putting SElinux in permissive mode (as
root user
42 matches
Mail list logo
