Hi Martin,
On Sat, Jan 30, 2016 at 5:03 AM, Martin Alfke wrote:
> Hi Matt,
>
> an ENC can set an environment for a node.
Yep. I'm using an ENC to set the environment to 'apt'.
> In case that a node does not specify an environment it will make use of
> environment production.
> You can specify
Thanks All,
Finally it worked for me. I gave wrong path for modulepath.
Thanks,
Maruti.
On Thu, Jan 28, 2016 at 1:48 AM, Maruti Gangumolu <
maruti.gangum...@gmail.com> wrote:
> The behaviour was same!
> --
> From: Frederik Bjerggaard Nielsen
> Sent: 27-01-2016 16
On 30 Jan 2016, at 13:48, Tim Coote wrote:
> What's the best way to test upgrades of puppetmaster? I'm trying to migrate
> from 3.x to 4.x on a small network. An obvious step for me was to create the
> new manifests on a new VM and then to confirm that the existing puppet agents
> wouldn't h
What's the best way to test upgrades of puppetmaster? I'm trying to
migrate from 3.x to 4.x on a small network. An obvious step for me was to
create the new manifests on a new VM and then to confirm that the existing
puppet agents wouldn't have any changes if they try to use that server for
update
Hi Matt,
an ENC can set an environment for a node.
In case that a node does not specify an environment it will make use of
environment production.
You can specify node environment on the node in puppet.conf in agent section:
[agent]
environment = apt
Best,
Martin
On 28 Jan 2016, at 18:13, Matt
On 29 Jan 2016, at 21:44, Sans wrote:
>
> Hi there,
> Need to iterate over an arry, so was trying the Future Parser. Using a very
> simple example:
>
>
>
> $alpha = ['a','b','c']
> each($alpha) |String $value| { notice( "Hi there, ${value}" ) }
>
> but getting this error:
> Error: Could no
Hi Kyle,
On 30 Jan 2016, at 01:27, Kyle Flavin wrote:
> On Friday, January 29, 2016 at 3:44:24 PM UTC-8, Garrett Honeycutt wrote:
> Hi Kyle,
>
> I think you have a scoping issue, try using the double colons for the
> puppet class, such as 'class foreman-proxy::puppet inherits ::puppet'.
>
>
