Puppet Enterprise breaks up into several large components. You can either have the Web-based installer do the work for you or save anwser files to install from a terminal later on other servers.
The Puppet Enterprise installer will break the installation up into parts for you if you select 'Split site' as your installation type.
The installation instructions for this 'split site' on puppet.com.
The order recommended is:
- Install the first Puppet Master which will be the Certificate Authority (CA) or Master of Masters.
- Install the PuppetDB server.
- Install the Puppet Enterprise Console.
This is how Puppet is setup since the addition of PuppetDB and the Console in 2.x all the way up to PE 2016.
As mentioned the Web-based Puppet Enterprise installer can do all of this for you. It uses public-key based SSH logins from root on the server you run the installer to the various parts you are installing.
In any case you will need at least three servers, virtual machines or AWS instances or phyiscal machines, and correctly setup /etc/hosts files or DNS. For ease of installation run the installer on the server that will be setup first, the CA or Master of Master server.
There are other more complicated procedures available as well. You can install a PostgreSQL cluster before starting and connect PuppetDB to that in step 2. You can add more Compile Masters after step 3.
The mCollective orchestration facility will be deployed to that first Puppet Master as part of installation and any additional Compile-only Masters you add. At any time after setup you can create more AMPQ hubs and spoke servers that just support mCollective and Application Orchestration.