Did PE 3.7 kills r10k?

175 views
Skip to first unread message

Vadym Chepkov

unread,
Dec 26, 2014, 6:39:02 PM12/26/14
to puppet...@googlegroups.com
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

Martin Alfke

unread,
Dec 27, 2014, 9:44:44 AM12/27/14
to puppet...@googlegroups.com
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
> --
> 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...@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.

Vadym Chepkov

unread,
Dec 27, 2014, 10:59:55 AM12/27/14
to puppet...@googlegroups.com


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




chris mague

unread,
Dec 27, 2014, 2:32:28 PM12/27/14
to puppet...@googlegroups.com
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 

Justin Holguin

unread,
Dec 27, 2014, 4:54:57 PM12/27/14
to puppet...@googlegroups.com
Hi Vadym,

The new classifier does allow agents to specify their own environments, but it involves an extra couple of steps. What you'll want to do is create a new group for the nodes that you're concerned with (which could be all of them) and set the environment of the new group to "agent-specified" in the pulldown menu. If you never want to override that setting with another classifier group, then you should also set "Override all other environments" in the group's metadata.

Hope that helps!
Justin

Vadym Chepkov

unread,
Dec 27, 2014, 11:04:38 PM12/27/14
to puppet...@googlegroups.com
Hi Justin,

That definitely helps, worked like a charm, thank you.

Vadym

Johan De Wit

unread,
Jan 21, 2015, 5:31:32 AM1/21/15
to puppet...@googlegroups.com
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
--
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...@googlegroups.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 (PCP0000006)
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
_________________________________________________________
 

Upcoming Events:

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


Reply all
Reply to author
Forward
0 new messages