Mogo Infrastructure Documentation

Welcome to the Mogo Infrastructure Documentation.

This documentation provides the architecture, operational procedures and disaster recovery guidance for the MogoLabs production environment.


!!! danger "Production Incident?" If you are responding to a production incident, begin with the Emergency Guide.


Documentation Library

Emergency Guide

Used during active production incidents.

  • Incident Severity
  • Escalation Process
  • Recovery Priorities
  • Emergency Contacts
  • First 60 Minutes

Go to Emergency Guide


Infrastructure Manual

Describes how the environment is designed and configured.

Includes:

  • Architecture
  • Network
  • Active Directory
  • DNS
  • HAProxy
  • IIS
  • Application Servers
  • SQL Server
  • Azure
  • Blob Storage
  • Monitoring
  • Backups

Go to Infrastructure Manual


Operations Manual

Day-to-day operational procedures.

Includes:

  • Deployments
  • Blue / Green Releases
  • Maintenance
  • Certificate Management
  • Scheduled Tasks
  • SQL Jobs
  • Monitoring
  • Change Control

Go to Operations Manual


Disaster Recovery Manual

Scenario-based recovery procedures.

Examples include:

  • IIS Failure
  • HAProxy Failure
  • SQL Failure
  • Active Directory Failure
  • Azure Blob Failure
  • VM Failure
  • Database Corruption
  • Ransomware
  • Human Error

Go to Disaster Recovery Manual


Reference

Supporting documentation.

Includes:

  • Server Inventory
  • Authority Matrix
  • Ports
  • Certificates
  • Third Party Services
  • Glossary

Go to Reference


Documentation Principles

This documentation is the authoritative source for the MogoLabs production environment.

Source Control

Documentation is maintained in Git and follows the same change management process as production code.

All changes must:

  • Be committed to source control.
  • Be reviewed through a Pull Request.
  • Be approved before publication.

Credentials

Passwords, API keys, certificates and licence keys must not be stored within this documentation.

Credentials are maintained within 1Password.


Incident Philosophy

The objective of this documentation is to:

  1. Restore Service
  2. Restore Resilience
  3. Determine Root Cause
  4. Prevent Recurrence

Restoring customer service does not conclude an incident. An incident remains open until the platform has been returned to its intended resilient state.


Bus Factor

This documentation has been written to ensure the production environment can be understood, operated and recovered by an engineer with appropriate infrastructure knowledge, without requiring prior knowledge of the MogoLabs platform.


Revision Information

Property Value
Owner Trevor Watson
Classification Internal
Source Azure DevOps Git Repository
Published Automatically via Azure Pipeline