Is there any documentation which describes RBAC and the “Project Deployers” role and how to create a “Project” and what IS a “Project” at all? I want to give users access to running tasks and plans. I assumed that “Project deployers” would be the right role. But that is not the case.

Someone mentioned before it was added as a planned feature, but not implemented yet

so it does nothing at the moment

Someone mentioned before it was added as a planned feature, but not implemented yet

@vchepkov good to know. many thanks.

This message was deleted.

This message was deleted.

PE-28206 is a comment in the puppet_enterprise module and mentions basically 'switch from G1 garbage collector to parallelGC'. that ticket is private. can someone give some background? is that quite an old change?

It came in with PE 2019.0 and Java 11. Basically, after performance testing, we found that: • ParallelGC can reduce the maximum heap size below

-Xmx

when appropriate, which frees RAM for use by other part of the system (GC may have gained this capability by Java 17). • G1 does not fit well with JRuby: https://github.com/jruby/jruby/issues/5789

thanks, will have a look. We were considering to switch to G1 because of our pxp-agent timeouts

This message was deleted.

Otherwise, you can use something like the following:

/opt/puppetlabs/server/apps/java/lib/jvm/java/bin/jcmd \
  $(systemctl show pe-puppetserver -p MainPID|cut -d= -f2) \
  JFR.configure stackdepth=128

/opt/puppetlabs/server/apps/java/lib/jvm/java/bin/jcmd \
  $(systemctl show pe-puppetserver -p MainPID|cut -d= -f2) \
  JFR.start name=pcp-broker settings=profile disk=true duration=2h filename=/var/log/puppetlabs/puppetserver/pcp-broker.jfr

This message was deleted.

hopefully the last thing for the week: we noticed regression in puppet lookup in PE 2021.08.10. could someone provide an estimate when we could get a fix for this? https://tickets.puppetlabs.com/browse/PUP-11595

Can anyone tell me what the license is for the puppet-dev-tools docker container?

This message was deleted.

That does make a good point about separate JVMs though: Catalog compilation needs a high throughput GC and PCP Broker needs a low pause GC --- and those are opposing goals that a given GC algorithm has to pick one of.

The broker is already publicly available: https://github.com/puppetlabs/pcp-broker So, having pre-built packages wouldn't be a huge change. But, the missing FOSS component would be an Orchestrator equivalent that transforms API requests like "run puppet", "run a task", "run a job" into the PXP messages that flow back and forth over the broker.

new LTS is out👋

This message was deleted.

This message was deleted.

dozens of rhel 5 mostly, 32 and 64bit.

This message was deleted.

What should be used instead of eyaml for encrypted hiera data? Should the workaround sentence say "... you can use a non-FIPS-enabled primary server with FIPS-enabled agents, which limits the issue to situations where only the primary uses the Ruby Library"?

The parameter is undocumented but if you set $permit_unsafe_versions to true then peadm will attempt install of 2021.7

This message was deleted.

This message was deleted.

hey people to get some visibility into the ENTERPRISE jira project and the workflow? For example I raised a feature request (https://tickets.puppetlabs.com/browse/ENTERPRISE-1460) in april. I don't know if that's accepted, if someone is working on this or if I could help with a pull request. are those tickets reviewed on a regular basis? Should we raise feature requests in a different way?

I have equally opinionated dev setup 🙂 https://github.com/vchepkov/bootstrap-pe-ha

ah, nice. thanks. I'll take a look. I have quite a rather opinionated setup myself. it works for us, and works well in general, but has tended to make upgrades more challenging than normal for PE and more challenging than it can be for the folks I'd like to hand off platform maintenance to - hence a big driver for having a plan where I can capture those manual things.