/12.1.0.4.0/jdk/jre/bin/java
> java_foundversion5_path => /opt/itm/v6.2.2/JRE/lx8266/bin/java
> java_foundversion6_path => /u01/java/jdk1.7.0_72/jre/bin/java
> java_foundversion7_path => /u01/java/jdk1.7.0_72/bin/java
> java_foundversion8_path => /u01/java/jdk1.7.0_65/jre/bin/java
> java_fou
If you have a fact called factA and a fact called factB, and you need factC
to be a combination of both values, sure, that can be done.
I don't know what version of Facter you're using, but if you're using PE
3.7 + Facter 2.2.0, you can simply use Facter.value.
E.g:
Facter.add(:factC) do
set
Puppet support engineer here.
It would take some configuration tweaks to do the migration, but it should
be doable.
Once you're set up with a support plan, we can definitely assist you with
that :)
On Thursday, November 7, 2013 4:26:16 PM UTC-8, Forrie wrote:
>
> We have perhaps 40 to 50 syste
Possibly stupid question - how do I know when I have to use a variable
in a string like this - "${apache::params::moddir}/php.conf" - or when
it's safe to just do it like this -
"$apache::params::moddir/php.conf". It seems like sometimes I need to
do the former, and other times the latter.
I don't
My point was that I don't use and won't be using multiple puppet masters.
Also, at my current level of puppet knowledge, Nan's code is basically
meaningless to me :(
On Wed, Aug 15, 2012 at 9:51 AM, jcbollinger wrote:
> To use multiple Puppet masters for the same site and retain your sanity,
> i
That's a fair point, but not applicable to my use-case (multiple puppet
servers).
However, at some point in the near future, I'll be using hiera, and that
will be moot.
On Tue, Aug 14, 2012 at 1:44 PM, Chad Huneycutt wrote:
> On Tue, Aug 14, 2012 at 11:56 AM, Zachary Alex Stern
> wrote:
> >
> >
On Mon, Aug 13, 2012 at 12:42 PM, Nan Liu wrote:
> class puppet (
> $server = $puppet::params::server
> ) inherits puppet::params {
>
Still missing something here - why do I need "inherits", or ANY statement
at all, other than the $server = $puppet::params::server.
$puppet::params::server seem
> class puppet (
> $server = $puppet::params::server
> ) include puppet::params {
> ...
> }
>
If I'm already specifying scope, e.g. $server = $puppet::params::server,
why do I also need the include?
--
zachary alex stern I systems architect | ceo - enter: narnia
o: 212.731.2033 | f: 212.20
Ok, that's helpful, however:
On Sun, Aug 12, 2012 at 8:43 AM, Eric Shamow wrote:
> An example: suppose is this module you say $puppetmaster =
> "myserver.local" and in another module, you want to only run on a puppet
> master and so say $puppetmaster = true. When Puppet assembles the model of
>
I'm having a really hard time grasping how variables are scoped in
puppet (not really much of a programmer).
I've got a manifest that looks like this:
###
class puppet::config {
include puppet::params
file { '/etc/puppet/puppet.conf':
ensure => present,
content => template('puppet/pup
10 matches
Mail list logo
