Hi
Sorry not trying to argue but just like to get my view point in
On 29 June 2016 at 08:30, jcbollinger wrote:
>
>
> On Monday, June 27, 2016 at 6:42:58 PM UTC-5, Alex Samad wrote:
>>
>> On 27 June 2016 at 23:33, jcbollinger wrote:
>> >
>> > Alex,
>> >
>> > I will be brief(ish) this time, sinc
On Monday, June 27, 2016 at 6:42:58 PM UTC-5, Alex Samad wrote:
>
> On 27 June 2016 at 23:33, jcbollinger >
> wrote:
> >
> > Alex,
> >
> > I will be brief(ish) this time, since wordiness seems not to be working.
> > I've been around Puppet for a fairly long time, and I think I know what
>
On 27 June 2016 at 23:33, jcbollinger wrote:
>
> Alex,
>
> I will be brief(ish) this time, since wordiness seems not to be working.
> I've been around Puppet for a fairly long time, and I think I know what I'm
> talking about, but by all means do evaluate my claims for yourself.
I have come to th
Alex,
I will be brief(ish) this time, since wordiness seems not to be working.
I've been around Puppet for a fairly long time, and I think I know what I'm
talking about, but by all means do evaluate my claims for yourself.
On Friday, June 24, 2016 at 9:20:58 PM UTC-5, Alex Samad wrote:
> T
On 25 June 2016 at 00:32, jcbollinger wrote:
>
>
> On Thursday, June 23, 2016 at 6:11:11 PM UTC-5, Alex Samad wrote:
>>
>> On 24 June 2016 at 00:16, jcbollinger wrote:
>
>
> [...]
>
>>
>> > In the first place, I recommend not using multiple Puppet environments
>> > unless you have a Puppet-relate
On Thursday, June 23, 2016 at 6:11:11 PM UTC-5, Alex Samad wrote:
>
> On 24 June 2016 at 00:16, jcbollinger >
> wrote:
>
[...]
> > In the first place, I recommend not using multiple Puppet environments
> > unless you have a Puppet-related reason for doing so. The prime reason
> in
> > t
On 24 June 2016 at 00:16, jcbollinger wrote:
>
>
> On Thursday, June 23, 2016 at 1:30:37 AM UTC-5, Alex Samad wrote:
>>
>> Hi
>>
>> So I am a bit of a newbie. My assumption was to setup using a master
>> puppet server. But I wanted to make sure that environment was handled
>> by the master puppet
On Thursday, June 23, 2016 at 1:30:37 AM UTC-5, Alex Samad wrote:
>
> Hi
>
> So I am a bit of a newbie. My assumption was to setup using a master
> puppet server. But I wanted to make sure that environment was handled
> by the master puppet - I have control over that and I might not be
> abl
Hi
sorry bit more.
puppet config print environment
So from what I understand you saying this show the environment from
the agent side no talking to the master puppet !
so a puppet agent --noop --test would be a way of looking. is there
no other way of querying what the master things of a node
Hi
So I am a bit of a newbie. My assumption was to setup using a master
puppet server. But I wanted to make sure that environment was handled
by the master puppet - I have control over that and I might not be
able to exclude control over the managed box from other users (dam
developers !).
I wan
On Wednesday, June 22, 2016 at 2:21:27 AM UTC-5, Alex Samad wrote:
>
> :)))
>
> seems like after writing this I found my answer
>
> I used
>
> puppet agent --test --verbose
>
> shows me that it is classified as environment alex. thats good.
>
> but
> puppet config print environment
> still sho
:)))
seems like after writing this I found my answer
I used
puppet agent --test --verbose
shows me that it is classified as environment alex. thats good.
but
puppet config print environment
still show production? so I am guessing the above just looks at the puppet
config files and as I hav
12 matches
Mail list logo
