On 20.5.2014, 17:05, jcbollinger wrote:
>
>
> On Tuesday, May 20, 2014 7:36:31 AM UTC-5, Henrik Lindberg wrote:
>
> This suggests a design that is somewhat inside-out, the idea is that
> what is *in* the environment defines what you want, not that you inside
> the environment make de
Hi,
On Mon May 19 16:39:25 2014, jcbollinger wrote:
>
>
> On Monday, May 19, 2014 6:06:45 AM UTC-5, Boyan Tabakov wrote:
>
> Hi,
>
> The variable I want to access is not defined in a module/class.
> It's the
> globally defined $::environment.
>
> ::class_name::variable
>
> Regards,
>
> El 09/05/2014 13:15, "Boyan Tabakov" <mailto:bl...@alslayer.net>> escribió:
>
> Hi,
>
> The puppet master sets several global variables, including $environment,
> $serverip, etc
>
>
Hi,
The puppet master sets several global variables, including $environment,
$serverip, etc
(http://docs.puppetlabs.com/puppet/latest/reference/lang_facts_and_builtin_vars.html).
However, looks like client facts with the same names can mask out these
variables. How can one determine reliably the c
On 16.4.2013 16:30, jcbollinger wrote:
> [... which carries maintenance costs typical of such boilerplate
> repetition.]
>
> It sounds to me like requiring an explicit declaration for each project
> class is the way to go. As I said already, however, that's entirely
> unrelated to the question of
Hi John,
Thanks for your reply!
On 15.4.2013 18:02, jcbollinger wrote:
> Single point of entry does not serve well and is not a particularly
> useful goal when the desired results are very divergent. The single
> declaration then becomes magical, and therefore difficult to understand
> and maint
Hi all,
Let's consider the following situation:
I use the module structure, proposed by R.I.Pienaar:
http://www.devco.net/archives/2012/12/13/simple-puppet-module-structure-redux.php
I have a module, let's say apache, that follows that pattern for
installing and setting up basic apache server.
On 22.1.2013 23:04, jcbollinger wrote:
> You are correct that that only the identity of the client node is
> authenticated by Puppet, and even that only insomuch as the client can
> be relied upon to protect its SSL certificate. The $hostname fact
> cannot be relied upon to convey that information
sted
puppetmaster-side metadata for nodes? Is that the way to go?
Thanks in advance!
Best regards,
Boyan Tabakov
signature.asc
Description: OpenPGP digital signature
