Re: [Puppet Users] Did PE 3.7 kills r10k?

2015-01-21 Thread Johan De Wit 

Hi,

I wrote a post addressing this issue : 
http://johan.koewacht.net/puppet/2015/01/12/R10k-and-PE-Console.html


Any comments are more then welcome.

Grts

Johan


On 27/12/14 20:32, chris mague wrote:

Vadym,

I ran into the same problem and was able to work around as follows 
with the caveat that it's unsupported:


sudo su - pe-postgres
psql
\connect pe-classifier
select * from groups;
# write everything down
update groups set environment_name='agent-specified' where 
environment_name='production';

# then set the last column to 't' if you have any other groups.

You may need to specify the override




On Saturday, December 27, 2014 7:59:55 AM UTC-8, Vadym Chepkov wrote:



On Saturday, December 27, 2014 9:44:44 AM UTC-5, Martin Alfke wrote:

Hi Vadym,

the PE node classifier is an ENC.
This ENC sets environments per nodes as an authority. Nodes
can no longer switch their environments if you use an ENC with
environment parameters set.

You still have the technical possibility to continue using
manifests based node classification and therefor you can
continue using r10k.
You will only loose the environment enforcement via ENC.

hth,

Martin



Hi Martin,

That's the problem,  PE 3.7 creates 'default' group, which can't
be edited and this group enforces 'production' environment for
each node.
You can create a new group and override environment there, but you
would have to do it for each single topic branch you create in git
and development team can't work on more than one topic branches
from the same node. This makes development process extremely
difficult.

Regards,
Vadym




--
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 on the web visit 
https://groups.google.com/d/msgid/puppet-users/30babbee-4d8e-467e-90ea-c3d0af8f446c%40googlegroups.com 
.

For more options, visit https://groups.google.com/d/optout.



--
Johan De Wit

Open Source Consultant

Red Hat Certified Engineer  (805008667232363)
Puppet Certified Professional 2013/2014 (PCP006)
blog : http://johan.koewacht.net/
_
 
Open-Future Phone +32 (0)2/255 70 70

Zavelstraat 72  Fax   +32 (0)2/255 70 71
3071 KORTENBERG Mobile+32 (0)474/42 40 73
BELGIUM http://www.open-future.be
_
 



Next Events:
Bacula Administrator 1 | 
http://www.open-future.be/bacula-administrator-i-training-13th-till-15th-january
Puppet Fundamentals | 
http://www.open-future.be/puppet-fundamentals-training-26th-till-28th-january
Puppet Architect | 
http://www.open-future.be/puppet-architect-training-29th-till-30th-january
Linux Training | http://www.open-future.be/linux-training-9th-till-13th-february
Puppet Practitioner | 
http://www.open-future.be/puppet-practitioner-training-17th-till-19th-february
Bacula Administrator 1 | 
http://www.open-future.be/bacula-administrator-i-training-24th-till-26th-february
Subscribe to our newsletter | http://eepurl.com/BUG8H

--
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 on the web visit 
https://groups.google.com/d/msgid/puppet-users/54BF7FF3.6090603%40open-future.be.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Did PE 3.7 kills r10k?

2014-12-27 Thread chris mague 
Vadym,

I ran into the same problem and was able to work around as follows with the 
caveat that it's unsupported:

sudo su - pe-postgres
psql
\connect pe-classifier
select * from groups;
# write everything down
update groups set environment_name='agent-specified' where 
environment_name='production';
# then set the last column to 't' if you have any other groups.

You may need to specify the override 




On Saturday, December 27, 2014 7:59:55 AM UTC-8, Vadym Chepkov wrote:
>
>
>
> On Saturday, December 27, 2014 9:44:44 AM UTC-5, Martin Alfke wrote:
>>
>> Hi Vadym, 
>>
>> the PE node classifier is an ENC. 
>> This ENC sets environments per nodes as an authority. Nodes can no longer 
>> switch their environments if you use an ENC with environment parameters 
>> set. 
>>
>> You still have the technical possibility to continue using manifests 
>> based node classification and therefor you can continue using r10k. 
>> You will only loose the environment enforcement via ENC. 
>>
>> hth, 
>>
>> Martin 
>>
>
>
> Hi Martin,
>
> That's the problem,  PE 3.7 creates 'default' group, which can't be edited 
> and this group enforces 'production' environment for each node.
> You can create a new group and override environment there, but you would 
> have to do it for each single topic branch you create in git and 
> development team can't work on more than one topic branches from the same 
> node. This makes development process extremely difficult.
>
> Regards,
> Vadym
>
>
>
>
>

-- 
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 on the web visit 
https://groups.google.com/d/msgid/puppet-users/30babbee-4d8e-467e-90ea-c3d0af8f446c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Did PE 3.7 kills r10k?

2014-12-27 Thread Vadym Chepkov 


On Saturday, December 27, 2014 9:44:44 AM UTC-5, Martin Alfke wrote:
>
> Hi Vadym, 
>
> the PE node classifier is an ENC. 
> This ENC sets environments per nodes as an authority. Nodes can no longer 
> switch their environments if you use an ENC with environment parameters 
> set. 
>
> You still have the technical possibility to continue using manifests based 
> node classification and therefor you can continue using r10k. 
> You will only loose the environment enforcement via ENC. 
>
> hth, 
>
> Martin 
>


Hi Martin,

That's the problem,  PE 3.7 creates 'default' group, which can't be edited 
and this group enforces 'production' environment for each node.
You can create a new group and override environment there, but you would 
have to do it for each single topic branch you create in git and 
development team can't work on more than one topic branches from the same 
node. This makes development process extremely difficult.

Regards,
Vadym




-- 
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 on the web visit 
https://groups.google.com/d/msgid/puppet-users/63a9c317-1fea-489d-8d7f-2e5d2246c6ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Puppet Users] Did PE 3.7 kills r10k?

2014-12-27 Thread Martin Alfke 
Hi Vadym,

the PE node classifier is an ENC.
This ENC sets environments per nodes as an authority. Nodes can no longer 
switch their environments if you use an ENC with environment parameters set.

You still have the technical possibility to continue using manifests based node 
classification and therefor you can continue using r10k.
You will only loose the environment enforcement via ENC.

hth,

Martin


On 27 Dec 2014, at 00:38, Vadym Chepkov  wrote:

> Hi,
> 
> I really hope I am mistaken, but it seems you can't use r10k with it's full 
> potential anymore in Puppet Enterprise 3.7.
> 
> In the past (PE3.3) I could create any branch, feature_something, in git 
> repository. r10k would create a branch/environment​ ​and I​ could​ ​apply it 
> from the command line on some development host, i.e.
> 
> puppet agent -t --environment=feature_something
> 
> Now, according to puppetlabs support, "console node classifier being the 
> definitive and authoritative environment-setter", so I can't do that anymore.
> This seems like a major setback and a deal breaker for me. Does anybody else 
> use environments this way?​ ​Why even have --environment switch altogether if 
> I can't select anything besides what is set in the console.
> 
> What are other choices except ditching PE altogether?
> 
> Thanks,
> Vadym
> 
> -- 
> 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 on the web visit 
> https://groups.google.com/d/msgid/puppet-users/CA%2BQfOKiQG%2BZd-kt_U1tcvOrK2yE9-JXR9P0jZYM%2Bdhp_6Q8NRA%40mail.gmail.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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 on the web visit 
https://groups.google.com/d/msgid/puppet-users/01F337DE-7CE8-4451-AA92-90A4AC3489CC%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Puppet Users] Did PE 3.7 kills r10k?

2014-12-26 Thread Vadym Chepkov 
Hi,

I really hope I am mistaken, but it seems you can't use r10k with it's full
potential anymore in Puppet Enterprise 3.7.

In the past (PE3.3) I could create any branch, feature_something, in git
repository. r10k would create a branch/environment
​ ​
and I
​
could
​ ​
apply it from the command line on some development host, i.e.

puppet agent -t --environment=feature_something

Now, according to puppetlabs support, "console node classifier being the
definitive and authoritative environment-setter", so I can't do that
anymore.
This seems like a major setback and a deal breaker for me. Does anybody
else use environments this way?
​ ​
Why even have --environment switch altogether if I can't select anything
besides what is set in the console.

What are other choices except ditching PE altogether?

Thanks,
Vadym

-- 
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 on the web visit 
https://groups.google.com/d/msgid/puppet-users/CA%2BQfOKiQG%2BZd-kt_U1tcvOrK2yE9-JXR9P0jZYM%2Bdhp_6Q8NRA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.