Install Continuous Delivery
After installing Bolt, specify your initial configuration setting and deploy Continuous Delivery for the first time.
Unlike version 4.x, Continuous Delivery 5.x uses Bolt to run plans from the cd4peadm
module for installation,
configuration, and administration instead of PAM. To install Continuous Delivery, you need a Forge API token to download the cd4peadm
module.
cd4peadm
module version matches the version of the Continuous Delivery application.Before migrating, please make sure the Linux system you plan to install Bolt on has internet access as well as SSH access to the system on which you intend to install Continuous Delivery 5.x. In addition, because Bolt is installed on one or more systems and used to manage one centralized Continuous Delivery installation, it may be a good idea to maintain the Bolt project in its own VCS repo.
If noexec
is set on the /tmp
filesystem on the system on which you intend to install Continuous Delivery 5.x, you need to use Bolt’s tmpdir
setting in inventory.yaml to point at a directory on a filesystem that does not have noexec
set.
- Install Bolt version 3.27.4 or later on a Linux jumphost. This can be the intended Continuous Delivery 5.x host, or any other system.
- Create the Continuous Delivery Bolt project and switch to that directory.Copy
mkdir cd4pe-bolt-project
cd cd4pe-bolt-project
bolt project init cd4pe_bolt_project - Edit the bolt-project.yaml file’s
modules
andmodule-install
sections. Replace theversion_requirement
with the version you wish to install, for example you would use 5.9.0 for the latest version. Add your Forge API token inauthorization_token
.Copy# bolt-project.yaml
modules:
- name: puppetlabs/cd4peadm
version_requirement: <version to install>
module-install:
forge:
authorization_token: 'Bearer <your API token>'
baseurl: https://forgeapi.puppet.com - Optional: Enable log append mode for Bolt logging to simplify debugging efforts in the case of problems.
Add the following to bolt-project.yaml: Copy
# bolt-project.yaml
log:
bolt-debug.log:
append: true
level: debugEnabling logging causes bolt-debug.log to grow over time. You can safely delete this file to free space as needed. - Install the
cd4peadm
module using the command:bolt module install
. - Create an inventory.yaml
file with the connection information for the host on which
Continuous Delivery 5.x is to be installed. Do not install Continuous Delivery on the same host you've installed Puppet Enterprise on. For
example:Copy
---
groups:
- name: cd4pe-nodes
config:
transport: ssh
ssh:
host-key-check: false
native-ssh: true
ssh-command: <Path to SSH command>
user: root
targets:
- cd4pev5.<yourcompany.com>If you are installing on a localhost, use the following
inventory.yaml
instead:Copy---
groups:
- name: cd4pe-nodes
config:
transport: local
targets:
- uri: localhostIf you need to change your resolvable hostname for some reason, see Update your resolvable hostname. - Optional: If you have a license file, create a directory named
files
and copy the license file tofiles/license.lic
. A license file is required to access the premium features of Continuous Delivery. - Install Continuous Delivery on the target host using:
bolt plan run cd4peadm::install
.If you prefer to install Continuous Delivery noninteractively, instead of usingbolt plan run cd4peadm::install
do the following:- Generate a configuration file manually using:Copy
bolt plan run cd4peadm::generate_config \
admin_password=perforce! \
inventory_aio_target="cd4pe_host" \
resolvable_hostname="cd4pev5.mycompany.net"This generates a configuration file at data/common.yaml. If you would like to see all of the configuration options, use
bolt plan show cd4peadm::generate_config
. - Install Continuous Delivery on the target host using:
bolt plan run cd4peadm::install_from_config
.
- Generate a configuration file manually using:
You can now log into the application at the resolvable hostname with the admin username and password you provided during the installation.