Some customers may
need to customize the configuration for their deployment. When customizing the
CPS configuration, it is important to make the customization in a way that does
not impact the normal behavior for VM deployment and redeployment, upgrades/migration, and rollbacks.
For this reason,
customizations should be placed in the
/etc/puppet/env_config directory. Files within
this directory are given special treatment for VM deployment, upgrade, migrations, and rollback operations.
configurations are manually changed in the VM itself after the VM has been
deployed, these configurations will be overridden if that VM is redeployed.
section describes the steps necessary to make changes to the puppet installer.
the CPS deployment are dependent on the requirements of the change. Examples of
To explain the
process, let us consider that we modify all VMs built from an installer, so we
use the Policy Server (QNS) node definition.
For the above
mentioned example, add custom routes via the examples42-network Puppet module.
(For more information on the module, refer to
In CPS 20.2.0, puppet is upgraded from 3.6.2-3 to 5.5.19 version. Puppet code has been modified to adapt to this change. Previous
release puppet code is not compatible with the current puppet version (5.5.19). Customer specific puppet code must be adapted
to current release puppet version (5.5.19) before applying it to CPS 20.2.0.
It is recommended
that version control is used to track changes to these Puppet customizations.
For example, to use
'git', perform the following steps:
directory as a repository:
# git init
empty Git repository in
# git add .
# git commit -m 'initial
commit of env_config'
If you are
making more changes and customizations, make sure you create new revisions for
# git add .
# git commit -m 'updated