• Index > DevOps Lifecycle

---

Phase 6: Deployments

Objective

Describe the objectives of this phase of the lifecycle.

6A. Administrative Prerequisites

• Action: Identify the Portal Project PI
• Action: Identify or Establish a TAS Project/Allocation
• Action: Identify the TAS Project GID for the Portal Allocation
• Action: Ensure the Correct Users are Added to the TAS Project
• Action: Identify the WMA Developer(s) Administrating the Portal
• Action: Verify Developer Access to Required Resources
• Action: Identify the Public URL for the Portal

6B. Resource Planning & Allocation

Host VM Requests

• Action: Request the deployment target host VMs for PPRD, PROD, DEV, etc. via KB.

SSL Certificates

• Action: Request SSL Certificates for each requested host VM via KB.

WSO2 Tenant Request

• Action: Select the Tenant Type for the portal (shared or dedicated).
• Action: Request a dedicated WSO2 tenant for TAPIS access.
• Action: Install portal service applications on the dedicated tenant.

CPS Exceptions

• Action: Have a CPS exception made for the PROD public domain name URL.

6C. Secrets & Credentials Managements

Credentials Management

• Action: Establish new UT Stache entry to store Administrator credentials.
• Action: Establish new UT Stache entries to store Portal credentials.
• Action: Establish new UT Stache entries to store CMS credentials.

WSO2 Tenant

• Action: Create a TACC Tenant OAuth client for each host VM.
• Action: Configure TACC Tenant long lived token for each host VM.

PostgreSQL

• Action: Create Database Credentials & a Database in the WMA PostgreSQL Cluster for each host VM Portal.
• Action: Create Database Credentials & a Database in the WMA PostgreSQL Cluster for each host VM CMS.

ElasticSearch

• Action: Create ElasticSearch Credentials in the WMA ES Cluster for each host VM.
• Action: Create ElasticSearch Indeces in the WMA ES Cluster for each host VM Portal and host VM CMS.

Web Services

• Action: Generate a new Google Analytics property ID for the PROD public domain name.
• Action: Generate a new Google Site Verification token for the PROD public domain name.
• Action: Generate a new reCAPTCHA code for the PROD public domain name.

Document Secrets

• Action: Populate UT Stache with the secret values for each host VM CMS: PROJECTNAME DEPLOYMENT_TARGET CMS.
• Action: Populate UT Stache with the secret values for each host VM Portal: PROJECTNAME DEPLOYMENT_TARGET Portal.

Prepare Settings

• Action: Create a secrets.py file for the django CMS container on each host VM.
• Action: Create a settings_secret.py file for the django portal container on each host VM.
• Action: Create a rabbitmq.env file for each host VM.

6D. Resource Provisioning & Configuration

Host Provisioning

• Action: Generate the dhparam.pem file on the deployment target host.
• Action: On the deployment target host create the user portal.
• Action: Add the Jenkins Deployment SSH key to the target host’s authorized keys file.
• Action: Nginx SSL Certs Configuration for containers.
• Action: Install host dependencies.
• Action: Add the portal user to the (new) docker group.
• Action: Create deployment directories for the Camino workflow in each deployment host VM.
• Action: Clone Camino into each deployment host VM.
• Action: Request that NSO grant the user portal SSH access from the Jenkins Deployer VM IP Address into each deployment host VM.

Placing Secrets

• Action: SCP secrets.py into each deployment host VM.
• Action: SCP settings_secret.py into each deployment host VM.
• Action: SCP rabbitmq.env into each deployment host VM.

CI/CD Jobs

• Action: Configure the Portal Project Jenkins CI job.

Backend Systems

• Action: Create Default Storage Systems for the project.
• Action: Create Default Execution Systems for the project.
• Action: Setup a Community Data Project.
• Action: Setup a Public Data Project. (Optional)

6E. Branding & Image Publishing

• Action: Setup the custom branding and navigation bar in Core-CMS-Resources.
• Action: Generate & Publish the Custom Project CMS Image on Dockerhub.

6F. Deployment Configurations

• Action: Update the Core-Portal-Deployments repo with correct docker image tag values for the CMS and Portal containers.

6G. Deployments

6G1. First Deployment

• Action: Deploy the Portal via Jenkins CI job on the target host system.
• Action: SSH into the deployment target host and become the user portal.
• Action: Complete the container setup.
• Action: Create an index page in the CMS.

6G2. Regular Deployment

• Action: Deploy the Portal via Jenkins CI job to each target host system.

6H. Post Deployment

• Action: Run the ES Indexing management command against each deployed target host VM.
• Action: Schedule a QA Review for each deployed target host VM.

Back to Top

---

• Index > DevOps Lifecycle