This message was deleted.
# puppet-enterprise
s
This message was deleted.
m
it provides a graphical user interface, point-and-click code deployment strategies, continuous testing and integration, and the ability to predict the impact of code changes before deployment. As well as enterprise level support, and access to features such as orchestration and patch management only available in PE
w
awesome, thanks
ok, that, plus the docs at puppet.com/docs/pe are probably all I need
interestingly, I see Debian isn't on the list of supported platforms for PE. I wonder why that is?
m
its supported as an agent platform, just not as an infrastructure component
w
is it because no commercial version of it exists?
m
im not actually sure the specific reason, but the eligibility for infrastructure has many factors including market demand
t
From tech view the main improvement for PE is PCP/PXP Orchestration broker. This allows one to shut down ssh or winrm and still being able to do anything with your servers.
w
thanks, @tuxmea - that is a pretty cool action.
from os standpoint - I guess I can see you corporates interested in PE, would put it on a licensed OS.
I think we have rolled out open-source clones of many of the PE features, but maintaining it is becoming a bit of a ache. especially with any amount of staff turn-over
we put in r10k, then g10k, then reaktor. But it sounds like code manager is better?
we also spend an inapropriate time checking if our modules are up to date, and if newer modules are still compatible with our fleet
(240 modules in our puppetfile, 3500 nodes, around 70 unique roles)
we have puppet-catalog-diff working pretty well, but I hope there is something better in PE?
and we use puppet-dashboard, but it sounds like enterprise dashboard and console will blow it out of the water?
same with puppet plans and bolt plans?
t
stay with puppet-catalog-diff and hopefully you also use the catalog-diff-viewer web UI
PE console allows you to provide different access rights (RBAC) which is not available in puppetboard
RBAC also is done for running tasks/plans via API or web UI
k
there is no puppet catalog diff equivalent in PE afaik
h
puppet module maintenance for a controlrepo is still there under PE
i.e. you still have to do it
w
ok, so not much win there