Administration & Configuration

Manage system settings, Ansible configuration, category mappings, vendor archives, file transfer, and pre-rendering instructions.

System Status

Last updated: 2026-02-18T20:47:38

MOCK

Ansible Mode

Found

Inventory

9

Playbooks

12

6

Regions

4

Vendor Versions

Playbook Library (9) MOP Auto-Classifier Browse MOP Source Drive (4 files)

Ansible Configuration

How Ansible Works Here: Ansible runs locally on this server. When a MOP is executed, this application calls the ansible-playbook command-line tool as a subprocess. There is no separate Ansible server - the playbooks run directly from this machine, connecting to target hosts via SSH.

Execution Mode Mock mode simulates playbook runs. Live mode executes real Ansible commands.

Inventory File Path Path to Ansible inventory (YAML or INI format)

SSH User

SSH Key Path

Vault Password File Path to Ansible Vault password file for encrypted variables

Timeout (seconds)

Verbosity Level

Forks (Parallel Hosts)

Log Output Path

Enable Privilege Escalation (become/sudo)

SSH Host Key Checking

Category-to-Playbook Mappings

Each MOP category maps to one or more Ansible playbooks that execute in sequence.

Category	Playbooks (in order)	Description	Risk	Est. Duration	Actions
patch-linux	`patch_linux.yml`	Linux server patching and security updates	medium	30 min	Remove?
agent-upgrade	`edit_yaml.yml` `commit_to_git.yml` `run_manual_pipeline.yml`	Monitoring agent version upgrade via GitOps pipeline	medium	45 min	Remove?
pipeline-only	`run_manual_pipeline.yml`	Trigger Azure DevOps pipeline directly (no code changes)	low	15 min	Remove?
git-ops	`edit_yaml.yml` `commit_to_git.yml`	Infrastructure-as-code configuration changes via Git	low	20 min	Remove?
infrastructure	`edit_yaml.yml` `commit_to_git.yml` `run_manual_pipeline.yml`	Full infrastructure change with pipeline deployment	high	60 min	Remove?
terraform	`run_terraform.yml`	Terraform plan/apply for cloud resource provisioning	high	45 min	Remove?
cert-rotation	`cert_rotation.yml`	TLS/SSL certificate rotation and renewal	medium	30 min	Remove?
service-restart	`service_restart.yml`	Rolling service restart with health checks and drain	medium	20 min	Remove?
db-maintenance	`db_maintenance.yml`	Database maintenance (vacuum, reindex, backup)	high	60 min	Remove?
security-scan	`security_scan.yml`	Security compliance scanning and auditing	low	15 min	Remove?
multi-region-patch	`patch_linux.yml`	Linux patching across all regions sequentially	high	120 min	Remove?
multi-region-deploy	`edit_yaml.yml` `commit_to_git.yml` `run_manual_pipeline.yml`	Full deployment across multiple regions sequentially	critical	180 min	Remove?

Add New Category Mapping

Category Name

Playbooks (comma-separated)

Description

Risk

Duration

Regional Execution Settings

Execution Order (comma-separated region codes) Regions are executed sequentially in this order

eus2 wus2 wus3 scus eus2lea wus2lea

Require Manual Approval Between Regions

Auto-Proceed to Next Region

Auto-Rollback on Failure

Pause Between Regions (seconds)

Max Concurrent Regions

MOP Source Drive Configuration

MOP Source Drive: Configure the path to the mounted drive (or network share) where vendor MOP archive files are stored. Users can also upload archives from their Windows PC to this mount point through the file upload feature.

Mount Point / Source Path Linux path to the mounted drive or network share where MOP archive files are located (e.g., /mnt/mopsets, /nfs/vendor-mops)

Max Upload Size (MB)

Enable PC File Upload

Allow users to upload files from their Windows/Mac PC to the mount point

Auto-Process on Upload

Automatically run the archive processing pipeline when a file is uploaded

Mount Status

Mount Accessible 4 archive file(s) found at mnt_mopsets

Browse Mount Point

Recent Import Activity

Time	Source	Method	Details
2026-02-18T20:47:38	mnt_mopsets/mvm-markdown-lea-11.5.42.tgz	mount_import	v11542 (51 templates)
2026-02-18T20:04:22	mnt_mopsets/mvm-markdown-lea-11.5.42.tgz	mount_import	v11542-LEA (22 templates)
2026-02-18T19:26:04	mnt_mopsets/mvm-markdown-main-11.5.42.tgz	mount_import	v11542 (29 templates)
2026-02-18T18:28:59	PC upload: mvm-markdown-lea-11.5.4+2.tgz	pc_upload	1.78 MB
2026-02-18T18:28:30	PC upload: mvm-markdown-main-11.5.4+2.tgz	pc_upload	1.8 MB
2026-02-11T08:13:45	mnt_mopsets/mvm-markdown-main-11.5.37.tgz	mount_import	v11537 (44 templates)
2026-02-11T08:13:26	mnt_mopsets/mvm-markdown-lea-11.5.37.tgz	mount_import	v11537 (44 templates)
2026-02-11T06:06:03	mnt_mopsets/mvm-markdown-lea-11.5.37.tgz	mount_import	v11537 (44 templates)
2026-02-11T05:57:35	mnt_mopsets/mvm-markdown-lea-11.5.37.tgz	mount_import	v11537 (44 templates)
2026-02-11T04:40:32	mnt_mopsets/mvm-markdown-lea-11.5.37.tgz	mount_import	v11537 (44 templates)

Vendor Archive Management

Vendor Archives: Compressed archives (.tgz, .tar.gz, .gz) containing MOP sets of J2 (Jinja2) templates. Upload an archive to extract, validate, and prepare the vendor MOPs for rendering and execution.
Supported formats: .tgz, .tar.gz, .gz

Import from MOP Source Drive

Select an archive from the configured mount point: mnt_mopsets

Archive File on Mount

Version Override (optional)

Auto pre-render after extraction

Upload from PC

Upload a vendor archive directly from your computer.

Extracted Vendor Versions

Version	Location	Actions
11542	`mops/11542/`	View
json	`mops/json/`	View
11537	`mops/11537/`	View
11542-LEA	`mops/11542-LEA/`	View

File Transfer

General File Upload: Transfer any file to the platform - JSON configs (prerender map), YAML variable files, or other supporting files. Use this when you need to deliver files from production to development, or upload configuration files directly.

Upload File

File Accepted: .json, .yml, .yaml, .j2, .md, .txt, .cfg, .ini, .csv, .tgz, .tar.gz, .gz

Destination

Overwrite if file exists

Auto-Detect Rules

`.json`		`configs/`
`.yml / .yaml`		`vars/`
`.j2`		`templates/`
`.tgz / .gz`		`uploads/gz/`
`.md / .txt`		`docs/`
`.cfg / .ini`		`configs/`
`.csv`		`data/`

Recent Transfers

Time	File	Destination	Size
2026-02-11T06:14:20	`lookup.json`	`configs/lookup.json`	2.7 KB

Run Pre-Render (Pass 1)

Apply the prerender text map to a vendor MOP set. This scans each J2 template and inserts text blocks where patterns match.

Vendor MOP Set Source: mops/{version}/

Prerender JSON Map 12 active entries loaded

Output (In-Place) J2 templates modified in-place

Prerender Text Map

12 entries

How it works: During pre-rendering (Pass 1), the system scans each J2 template in the vendor MOP set. For each entry below, it checks:

MOP Name Pattern: Does the MOP filename match the glob pattern? (e.g., *failover* matches db-failover-steps.j2)
Search Text: Does the MOP content contain this exact text?
Insert Text: If both match, the insert text block is placed right after the search text in the J2 template

The insert text can include multiple lines with URLs, instructions, before/after markers, and any content that will be Jinja-rendered to markdown in Pass 2.

ID	MOP Name Pattern	Search Text	Insert Text	Actions
`rule_1_1`	`*upgradeadopipelineresources.j2`	`# 9.2.3 Update the pipeline configuration file`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?
`rule_1_2`	`*upgradeadopipelineresources.j2`	`Edit the variables identified in the release documentation`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?
`rule_2_1`	`*upgradeselfhostedagentvm.j2`	`# 9.2.3 Update the VM related parameters`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?
`rule_2_2`	`*upgradeselfhostedagentvm.j2`	`Set selfhost_golden_image`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?
`rule_3_1`	`*upgradetoolingvm.j2`	`# 9.2.3 Update the VM related parameters`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?
`rule_3_2`	`*upgradetoolingvm.j2`	`Set tooling_golden_image`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?
`rule_4_1`	`r11537to*2upgradeoverviewmop.j2`	`Upgrade the Tooling VMs and CLI tools`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?
`rule_4_2`	`r11537to*2upgradeoverviewmop.j2`	`Delete down level resources`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?
`rule_5`	`*upgradesimon.j2`	`9.2.12 Verify that the Thanos compactor is enabled`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?
`rule_6`	`*upgradeesc.j2`	`9.3.3 Proceed with the upgrade`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?
`rule_7`	`*upgradesas.j2`	`9.3.2.2 Canary a larger percentage of traffic`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?
`rule_8`	`*deletesas.j2`	`9.2 Implementation`	`https://dev.azure.com/mvmprodeus2/MVM/_git/documentation?path=/Labs-ANTS-DevOps/...`	Delete?

Add New Entry

Entry ID Unique identifier (lowercase, use hyphens)

MOP Name Pattern Glob pattern to match MOP filenames

Search Text Exact text to search for in the MOP content

Insert Text Multi-line text block inserted into the J2 template after the search text. Include line feeds, before/after characters, URLs, and any additional info. This content will be Jinja-rendered to markdown in Pass 2.

Enabled

Rendering Pipeline Configuration

Enable Two-Pass Rendering

When enabled, vendor templates go through pre-render (URL map pattern matching) then final render (regional variables)

Variables Directory

Output Directory

Rendering Pipeline Flow

Vendor Archive

J2 Templates

Pass 1: Pre-Render

URL Map Insertion

Pass 2: Render

Regional Variables

Execute

Ansible

Log

Results