Skip to content

Latest commit

 

History

History
47 lines (27 loc) · 2.78 KB

upgrade_with_legacy_compilers.md

File metadata and controls

47 lines (27 loc) · 2.78 KB

Upgrade Puppet Enterprise with legacy compilers

What is a legacy compiler and a current compiler

As a legacy compiler we refer to a compiler that doesn't have PuppetDB. And a current Compiler is a compiler that has PuppetDB. By default, latest versions of Puppet enterprise comes with compilers that have PuppetDB.If your primary server and compilers are connected with high-latency links or congested network segments, you might experience better PuppetDB performance with legacy compilers.

Who is this documentation for

For those users that have installed Puppet Enterprise with puppetlabs-peadm prior version 3.21 and manually converted their existing complilers (all of the or at least 1) to legacy compilers.

Who is this documentation not for

For those users that have installed Puppet Enterprise with PEADM with 3.21 version or later, there is no need to follow this documentation. The install process will automatically have created the necessary configurations for you and you can use the peadm::convert_compiler_to_legacy plan if you need a legacy compiler. example:

bolt plan run peadm::convert_compiler_to_legacy legacy_hosts=compiler1.example.com,compiler2.example.com primary_host=primary.example.com

How to upgrade Puppet Enterprise with legacy compilers

1. Revert changes to the legacy compilers nodes

Usually users pin the nodes in the Pe Master Node Group and then manually removing PuppetDB from compilers nodes. To revert this changes go to your Puppet Enterprise console and unpin the compilers nodes from the Group.

2. Update certificate extensions for NON legacy compilers

If you have NON legacy compilers in your infrastructure, you have to add a certificate extension to them that recognizes them as NON legacy compilers. To do this, execute the following plan:

bolt plan run peadm::update_compiler_extensions primary_host=primary.example.com compiler_hosts=compiler1.example.com,compiler2.example.com

3. Use the convert legacy compiler plan

Now that we have unpinned the compilers nodes from the PE Master node group, execute the following plan to convert your needed compilers to legacy compilers:

bolt plan run peadm::convert_compiler_to_legacy legacy_hosts=compiler1.example.com,compiler2.example.com primary_host=primary.example.com

The above will create the needed Node group and Classifier rules to make the compilers legacy. Also will add certificate extensions to those nodes.

If you want to keep puppetDB service on the converted compilers, you can do so by passing the remove_pdb parameter as false.

4. Upgrade Puppet Enterprise

After you have completed the above steps, you can proceed with the upgrade of Puppet Enterprise as usual using the puppetlabs-peadm module. There is no need to do the above ever again.