The $servername variable isn't actually a fact -- it's set by the server
itself while compiling the catalog, so from the perspective of writing
manifests it smells a lot like a fact.
Wil
On Wed, Dec 3, 2014 at 2:13 PM, Ramin K wrote:
> I'm not a PE user, but the config for the OSS version has a
Congratulations Felix, I just saw it in my safari books online, checked few
topics, and found it brief and informative,
Thank you,
Walid
On 30 November 2014 at 17:24, Felix Frank
wrote:
> Hi all,
>
> it's with great pride that I follow Alessandro with yet another plug of
> relevant literature.
On 2014-03-12 15:35, Martijn Grendelman wrote:
Hi,
Please consider the following simplified code:
class apache::params {
$priority = 25
}
define apache::vhost (
$priority = $::apache::params::priority
) {
include apache::params
notify { "$name prio 1: $apache::params::priority": }
notify { "
On 2014-02-12 8:58, Nacho Barrientos wrote:
On 01/12/14 16:25, Spencer Krum wrote:
Maybe you could use the notice() or warn() functions?
Those would log server-side, wouldn't they? I want to see it on the
client console and on the Puppet report :)
Yes that is true. There is no current supp
On Dec 3, 2014 6:53 AM, "Martijn Grendelman"
wrote:
>
> Hi,
>
> Please consider the following simplified code:
>
> class apache::params {
> $priority = 25
> }
>
> define apache::vhost (
> $priority = $::apache::params::priority
> ) {
>
> include apache::params
>
> notify { "$name prio 1: $apache::
With the coming EOL of ruby 1.8 support we are upgrading our RSpec support
to latest. This means that we will also be adopting latest RSpec method
names.
The main changes will be in the removal of 'should' and 'stub' statements,
which will now be 'expect' and 'allow'.
For a rundown see:
http
I'm not a PE user, but the config for the OSS version has a blacklist to
remove facts like uptime, path, ps, etc from the facts.yaml. I'd expect
PE to follow the same process. Might be worth opening a support request.
Ramin
On 12/3/14 1:25 PM, Daren Arnold wrote:
Hi Ramin,
Is this feature/va
HI All,
Thanks for the responses - very helpful.
I've installed RVM and things are progressing much more smoothly now.
Cheers,
Josie
On Tuesday, December 2, 2014 11:56:42 AM UTC+11, josie.w...@gmail.com wrote:
>
> HI there,
>
> I'm looking for any tips/pointers on how to upgrade an existing
>
Hi Ramin,
Is this feature/variable turned on by default in PE 3.3? I am unable to
see a fact for 'servername'. I am probably trying to access it
incorrectly. To test, I issue an mco command:
mco inventory
I don't see servername available.
Thanks for any additional help you can provide.
D
Check audit as well. It is a meta parameter and made to address exactly
such use cases.
Thanks!
Anoop
On Wed, Dec 3, 2014 at 2:01 PM, Brian Morris
wrote:
> Hello all,
>
> Due to some persnickety Windows developers I have been tasked with showing
> that Puppet can be used to alert when a known c
Hi,
Noop mode is the answer
Regards,
El 3/12/2014 20:01, "Brian Morris" escribió:
> Hello all,
>
> Due to some persnickety Windows developers I have been tasked with showing
> that Puppet can be used to alert when a known configuration has changed
> rather than correcting the change, and then n
There is already a set of server facts available during a Puppet run.
https://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html#puppet-master-variables
Because you're running PE you should be able to query which servers are
using which server through mcollective.
Ra
If you already have SSH shared keys, a simpler method may be to just run a
remote ssh command through a loop. For instance, if you have the hostnames
in a text file named servers.txt, you could run something like
while read -u10 HOST ; do echo $HOST; ssh $HOST "grep server
/etc/puppet/puppet.co
Tony,
Thanks for your reply. I was hoping to avoid inspecting all of the agents
(either puppet.conf files or running puppet agent -t --debug) manually. I
am looking into an approach that involves creating an external fact to
query the value of 'server' in the puppet.conf. That may be what yo
Hello all,
Due to some persnickety Windows developers I have been tasked with showing
that Puppet can be used to alert when a known configuration has changed
rather than correcting the change, and then notifying of the correction. I
have tried wrapping my head around this, but it doesn't seem t
The agents should have the master defined in their puppet.conf file.
Failing that, you can manually run the agent on a system with "puppet agent
-t --debug" and look for entries that look like "Caching connection for
https://puppet.local:8140";
- Tony
On Wednesday, December 3, 2014 7:25:36 AM
And if I can learn how to use e-mail. Man, I'm getting tired.
Anyway, seem to have gotten environments to work. Still testing but I
think it will solve some of the issues we need to overcome. Yay!
On Wed, Dec 3, 2014 at 10:57 AM, leam hall wrote:
> On Wed, Dec 3, 2014 at 9:53 AM, leam hall wr
On Wed, Dec 3, 2014 at 9:53 AM, leam hall wrote:
> If I can get environments to work. Bleagh...
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "Puppet Users" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/puppet-u
Hello There,
We started our puppet adventures at 3.2.x with both windows and linux
boxes. Since then we have upgraded our Master to 3.3.2 and are looking to
upgrade to 3.7. The linux agent upgrades are very simple, but I am running
into issues with the windows agent upgrades :/ We have an Artif
Hello,
Newb question here. I have inherited a PE 3.3 setup that uses a Puppet
master hub, spoke and about 100 agents. The agents were installed at
various times - some were connected directly to the hub and others
connected to the spoke.
Is there a way to determine which agents are connect
Well, the manifest excerpt you pasted is valid in and of itself. I
suspect that you are using it in a wrong context, such as inside a
resource declaration block.
"if" constructs can appear
* in the global scope
* in the body of a class, node or define
HTH,
Felix
On 12/03/2014 03:08 PM, Spriya
Also, check to see if you have an exec somewhere that might be causing this
and you're seeing a flapping issue.
Trevor
On Wed, Dec 3, 2014 at 9:31 AM, jcbollinger
wrote:
>
>
> On Tuesday, December 2, 2014 10:03:53 PM UTC-6, chris smith wrote:
>>
>> Hi,
>>
>> This is a very strange one. On my CA
If I can get environments to work. Bleagh...
--
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+unsubscr...@googlegroups.com.
To view this discussion o
Hi,
Please consider the following simplified code:
class apache::params {
$priority = 25
}
define apache::vhost (
$priority = $::apache::params::priority
) {
include apache::params
notify { "$name prio 1: $apache::params::priority": }
notify { "$name prio 2: $priority": }
}
apache::vhost { 't
On Tuesday, December 2, 2014 10:03:53 PM UTC-6, chris smith wrote:
>
> Hi,
>
> This is a very strange one. On my CA server (which also runs puppet as
> an agent to control various things), sometimes a file gets turned into a
> directory. It's only this file and on this server (the other puppet
On Monday, December 1, 2014 4:11:31 PM UTC-6, Clay Stuckey wrote:
>
> I wrote two manifests for RHEL systems. One removed syslog. The other
> installed rsyslog. The syslog removal followed a tragic dependency tree
> removing RPMs such as coreutils, rpm, yum and pam. Once the servers
> rebooted
Hi,
I have two facts where the output is getting displayed for both. But now i
am trying fact1 with fact2. How can i do that?
I tried this one:
*if $java_foundversion_count != $java_authorized_count {*
* notify { "The server found java count has changed to
$java_foundversion_count": }*
*}*
27 matches
Mail list logo
