Evaluation Maintenance Guide
This document provides a comprehensive guide to maintaining and managing the Raga Catalyst infrastructure, covering key operational tasks and configurations.
IP Address Update
Purpose: Update the VM IP address
Command:
bash $HOME/raga-evaluation-scripts/scripts/update_ip_address.sh
Proxy URL Update
Purpose: Update the proxy server URL
Command:
bash $HOME/raga-evaluation-scripts/scripts/update_proxy_url.sh <proxy_server_endpoint>
Note: Replace <proxy_server_endpoint>
with the actual proxy server endpoint
Enable Backups for AWS Instance
### Purpose Enable periodic backups for the Raga Catalyst AWS instance.
Step 1: Create an IAM Policy
Go to the IAM Console in AWS
Navigate to Policies > Create Policy
Choose the JSON tab and enter the following policy:
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "VisualEditor0",
"Effect": "Allow",
"Action": [
"ec2:DescribeVolumes",
"ec2:DescribeInstances",
"ec2:CreateSnapshot",
"ec2:DescribeSnapshots",
"ec2:CreateTags",
"ec2:DeleteSnapshot"
],
"Resource": "*"
}
]
}
Click Next and provide a name:
RagaCatalyst-EbsSnapshot-Policy
Review and create the policy
Step 2: Create an IAM Role
Go to the IAM Console and navigate to Roles
Click Create Role
Under Select trusted entity, choose AWS service
Choose EC2 as the use case
Click Next and attach the previously created policy
Give the role a name:
RagaCatalyst-EbsSnapshot-Role
Create the role
Step 3: Attach the Role to an EC2 Instance
Go to the EC2 Console
Select the instance you want to modify
Click Actions > Security > Modify IAM role
Select the role
RagaCatalyst-EbsSnapshot-Role
and save
Step 4: Schedule a Cron Job for Snapshots
SSH into the EC2 instance and execute:
(crontab -l; echo "0 1 * * * $HOME/raga-evaluation-scripts/scripts/aws-ebs-backup.sh") | crontab -
Note: This creates an AMI snapshot once a day at 1 AM UTC. Adjust the cron expression as needed.
Enable Backups for GCP Instance
Purpose
Enable periodic backups for the Raga Catalyst GCP instance.
Prerequisites
GCP Console access with Owner or Editor role
VM instance details (IP address)
IAM permissions to modify service accounts and VM configurations
Configuration Steps
1. Project Configuration
Navigate to GCP Console
Verify active project in top navigation
Document:
Project ID
Project Number (from Dashboard > Project Info)
2. VM Instance Setup
Access Compute Engine > VM Instances
Locate target VM using Internal/External IP
Document instance details:
Instance name
Zone
IP addresses
3. Service Account Configuration
Initial Setup
Stop the VM instance
Navigate to instance settings
Click "Edit"
Service Account Attachment
Select "Compute Engine default service account"
Format:
PROJECT_NUMBER-compute@developer.gserviceaccount.com
Configure Access Scopes:
Set "Access for each API"
Enable:
Compute Engine: "Read Write"
Storage: "Read Write"
Cloud Platform: "Full Access"
Save and restart VM
Note: Public IP may change after restart. Document new IP.
4. IAM Role Setup
Navigate to IAM & Admin > IAM
Locate compute service account
Add "Compute Storage Admin" role
Save changes
5. Snapshot Scheduling
SSH into Azure VM
Execute:
echo "0 1 * * * $HOME/raga-evaluation-scripts/scripts/GCP-disk-backup.sh" | crontab -
This creates daily snapshots at 1 AM UTC.
Verification
VM Configuration:
Confirm service account attachment
Verify configured scopes
IAM Settings:
Check storage admin role assignment
Verify permissions
Technical Requirements
Service Account
Format:
PROJECT_NUMBER-compute@developer.gserviceaccount.com
Required scopes:
compute-rw
storage-rw
cloud-platform
VM State
Must be stopped for service account modifications
Must be running for snapshot operations
Important Notes
Both service account scopes AND IAM roles are required
Allow full VM startup before testing
Verify all permissions before snapshot operations
Cron schedule can be modified based on requirements
Support
For additional assistance or issues, please contact your system administrator or GCP support team.
Enable Backups for Azure Instance
Purpose
Enable periodic backups for the Raga Catalyst Azure instance.
Enable System-Assigned Managed Identity
Follow these steps in the Azure Portal:
Open the Azure Portal
Navigate to the Virtual Machines service and select your VM
In the left-hand menu, find the Identity section under Settings
Under the System-assigned tab, toggle the Status to On
Click Save
Note down the Object ID of the managed identity once enabled
Grant Permissions to the Managed Identity
The managed identity needs appropriate permissions to execute operations like fetching VM metadata, retrieving disk information, and managing snapshots.
Identify Resource Group
Navigate to the Overview section of the VM in Azure Portal
Note down the Resource Group name
Assign Required Roles
Navigate to the Resource Group of the VM
Click on Access Control (IAM) in the left-hand menu
Click + Add > Add role assignment
Select the Disk Snapshot Contributor role
Under "Assign access to", select Managed identity
Search for your VM's managed identity and click Save
Schedule Snapshot Creation
To set up automatic snapshot creation:
SSH into the Azure VM using terminal
Execute the following command to schedule snapshots:
echo "0 1 * * * $HOME/raga-evaluation-scripts/scripts/Azure-disk-backup.sh" | crontab -
This configuration creates an AMI snapshot daily at 1 AM UTC. You can modify the cron expression based on your requirements.
Last updated