Ansible Setup

Source: Onboarding RaaSv2.x — Configure Customer Ansible (TRIB 19707330758)

This page covers configuring the Ansible repository for a new RaaS customer. This is an AWS-specific process. For Azure, see Customer Onboarding — Azure Overview.

Prerequisite

Complete the Terraform Setup before Ansible configuration. The Ansible inventory variables reference resources created by Terraform.

Step 1: Clone the Ansible Repo

git clone git@github.com:rhapsody-health/ansible-raas-v2.x.git
cd ansible-raas-v2.x

Step 2: Update `.gitlab_ci` Variables

Edit the GitLab CI/CD configuration file (.gitlab-ci.yml or .gitlab_ci) to add the new customer:

Variable	Description	Example
`customer_code`	Short customer identifier	`uk-hscn`
`region`	AWS deployment regions	`eu-west-2`
`raas_instances`	List of RaaS instance hostnames	`rhapsody-1.uk-hscn.raas.rhapsody.global`
`account`	AWS account ID mapping	`943397710386`

Step 3: Configure `group_vars`

Create inventory vars for each combination of customer_code, devops_env, region, and instance:

inventory/group_vars/{{customer_code}}-{{devops_env}}_{{region}}_{{instance}}/
    vars.yml

Key variables to set:

rhapsody_version: "7.7.0.256"
rhapsody_license: "{{ vault_rhapsody_license }}"
customer_code: uk-hscn
region: eu-west-2
devops_env: prod

Step 4: Configure Secondary Block Devices (RAID)

Define secondary block devices required for the RaaS RAID configuration:

block_devices:
  - device: /dev/nvme1n1
    mount: /data/orionhealth
  - device: /dev/nvme2n1
    mount: /data/orionhealth

Ensure the instance type and Terraform config allocate the correct number of EBS volumes.

Step 5: Submit MR

Create a branch off {{customer_code}}-dev:

git checkout {{customer_code}}-dev
git checkout -b RAAS-{{ticket}}-{{brief-description}}

Commit the changes and push
Open a Merge Request targeting the {{customer_code}}-dev branch
Request review from a senior engineer (Lee / Cole / Emily)

Warning

Do not merge directly to master. Changes go: feature branch → {{customer_code}}-dev → master only after successful deployment verification.