Dark Launch Deployment with CDA

A CDA user wants to deploy a new version of an Application into production with a dark launch deployment approach.

Why Should I Read this Scenario?

This scenario will help you learn how to safely test a new version of your Application by rolling out the changes on the back-end to only certain Deployment Targets and making them visible to a subset of users.

Canary VS Dark Launch

The Canary Strategy infrastructure is used as a basis. If you have already set up everything you need to perform a Canary deployment with CDA, simply follow the steps below to "dark launch" your Application's deployment:

1. Define Toggles in the Config files.
2. Add two extra Dynamic Properties to the Docker_Image Component
3. Add a new Action to the Docker_Image Component Workflow.
4. Define a Prompt Set and Precondition for the Action.

Note: The extra steps are highlighted in green.

What Will I Learn?

• How to create a new Application and its related entities with the wizard.
• How to build and arrange the corresponding Application Workflows, Component Workflows and Actions.
• How to define Dynamic and Custom Properties.
• How to define Prompt Sets and Preconditions in Workflows.
• How to create the appropriate Package Stateflow to move the Application to the next State.
• How to use Profiles and a set of Deployment Targets to perform the deployment.

Before you Start...

• Ensure the following action packs are installed. You should see them in the PACKAGES folder in the Explorer sidebar in the Process Assembly perspective.

  • PCK.AUTOMIC_DOCKER (Docker Action Pack) v1.3.1 or higher.

    This Pack allows you to use all Docker features in actions.

  • PCK.AUTOMIC_NGINX (Nginx Action Pack)

    The actions contained in this pack simplify the process of installing nginx, building the configuration and setting up your templates.

    Note: Nginx will be used as a load balancer.

  Note: If they are not listed in the Explorer sidebar, then you need to download them from our marketplace on https://marketplace.automic.com/ and install them. For instructions about installing an action pack, see Installing Packs in Working with Packs and Plug-ins.

• Instead of running a permanently installed Tomcat service, Docker Tomcat instances will be used.

Process Overview

The deployment process consists of the following steps:

Let us start!

0. Defining Toggles in Config Files
1. Creating a new Package Type and Defining Package States
2. Creating the Application and Related Components
3. Defining the "Green" Profile
4. Fine-Tuning the Environment
5. Fine-Tuning the Components
6. Creating and Fine-Tuning the Workflows
7. Assigning Workflows to Package States