Deployment Manager FAQ - Installation and upgrades

  1. Can cloud customers directly download new releases of Deployment Manager from Pega Marketplace?
    • Ans: We strongly recommend Pega cloud customers request for new versions of Deployment Manager through Pega Support. The newest versions of Deployment Manager are available simultaneously on both Pega cloud and Pega Marketplace. Having it provisioned through Pega support also ensures that the provided Deployment Manager orchestrator environment is configured correctly and makes support and future management of orchestrator instance easier.
  1. For cloud customers, will Deployment Manager seamlessly work once Pega support delivers the systems to us after deploying a new Deployment Manager release?

Future releases of Deployment Manager will provide a seamless experience after upgrade that minimizes any manual intervention.

  1. Can on premise customers use an existing environment, such as the development environment, to install Deployment Manager and do double duty as an orchestrator environment?
    • Ans: For on prem customer, our recommendation is to always have a separate environment to the Deployment Manager orchestrator. This is how it is deployed for our Pega cloud customers and it provides the following benefits
      • Security – Companies often have policies that prevent development environments, or lower environments in general, from being able to connect directly to higher environments especially production. The Deployment Manager orchestrator can be setup to be the only authorized entity that can connect between the different environments with all the appropriate security privileges enforced which can satisfy this policy.
      • Stability – if a dev environment needs to be restarted or is impacted in any significant way, then the DevOps pipelines running in the orchestrator are not affected.
      • Scale – A single Deployment Manager orchestrator instance can be used to manage multiple applications each of which will have their own environment stacks. Keeping the orchestrator separate will ensure that all the connectivity necessary between the different environments is handled only at the orchestrator and not between the dev environment
      • Ease of troubleshooting – it will be a lot of easier to trouble shoot issues with the pipelines if the devops environment is separate.
    • That noted, if you are early in the development cycle and are just looking to get started with a DevOps pipeline, with the goal to migrate to a separate environment in the future, you can proceed with installing Deployment Manager on an existing environment. Follow the installation steps as you would when setting up Deployment Manager for the first time. Please keep in mind the challenges you will face around the points listed above and proceed accordingly.
  1. What type of node does Deployment Manager need?
  1. My Dev and QA environments are in one VPC, and the production is in a different VPC. How can I leverage Deployment Manager in this case?
    • Ans: There are two key requirements in order to make Deployment Manager work across VPCs
      • The DevOps orchestrator environment needs to be able to connect through https to all the environments, Dev, QA and Production. This might require whitelisting the DevOps IP addresses, please work with Pega Support in order get this configured
      • All the environments, Dev, QA, Prod and the DevOps orchestrator environment need to have a shared artifact store such as S3. Deployment Manager seamlessly stores artifacts generated as you run your deployments in S3 folder assigned to you.
    • However, the S3 folders are specific to a VPC and are not accessible across to other VPCs. It will be necessary to procure and configure a repositorythat can be accessed across all the environments. This could include leveraging any corporate repositories that are already available such as JFrog Artifactory, Azure, S3 or even a network file share all of which are supported by Deployment Manager. You also have the option of creating a custom repository for any artifact repositoriesthat are not supported out of the box.
    • If you would like to continue using the Pega provided S3 solution, then please work with Pega support in order to provision an cross VPC compatible S3 bucket.
  1. Can 8.1 (Infinity) Deployment Manager on orchestrator system manage candidate systems (Dev, Staging and Production) on 7.4?
    • Ans: Deployment Manager 4.x series is the version that is compatible with the Pega 8.1 platform. This means that the orchestrator environment needs to be Platform version 8.1 or above in order to use. It is possible to have orchestrator in the Deployment Manager 4.x series manage applications running on Pega platform 7.4 (where the Dev, QA, Stage, and Prod candidate environments where the applications run are on Pega 7.4). This will require that the 7.4 compatible DevOps foundation layer is installed on the 7.4 candidate systems.
    • Environments older than Pega 7.4 is not supported.
    • However, a lower version of Deployment Manager, ex. version 3.4 on orchestrator system will not be able to support a higher platform versions, ex Platform version 8.1 and above on candidate systems. An article detailing how to set this up correctly will be published in the near future.


Keep up to date on this post and subscribe to comments