Integrity Upgrade Playbook

From C3 Integrity
Jump to: navigation, search

Integrity Upgrade Playbook

Integrity upgrades are broken down into three different types, patch, minor, and major.

When scheduling time for an upgrade please be aware of the time windows when upgrades may be performed:

Monday 9am - 5pm
Tuesday 9am - 5pm
Wednesday 9am - 5pm
Thursday 9am - 5pm

Patch

Patch releases contain fixes to bugs detected in a previous release. Unless explicitly specified patch releases will only require code changes and will not require database or integration modification.

  • Upgrade Window: 1 hour
  • Upgrade Process:
  1. Begin downtime
  2. Ensure database backups are current (Client)
  3. Upgrade Integrity (C3)
  4. Confirm Integrity is now functioning correctly (Client)
  5. End downtime


Minor

Minor releases will contain new features and may deprecate existing features. These new features may require modifications to the database and require integrations to be modified.

  • Upgrade Window: 2 hours
  • Upgrade Process:
  1. Begin downtime
  2. Ensure database backups are current (Client)
  3. Upgrade Integrity (C3)
  4. Perform database upgrade (Client) (if required)
  5. Confirm Integrity is functioning correctly (Client)
  6. End downtime

Major

Major upgrades may contain backwards incompatible changes and any previously deprecated functionality may be removed entirely. There are two types of upgrades possible when a major upgrade occurs. If the system running Integrity requires an upgrade itself then a full system upgrade will be required. Otherwise a regular Integrity upgrade will be performed.

Integrity Upgrade

  • Upgrade Window: 4 hours
  • Upgrade Process:
  1. Begin downtime
  2. Ensure database backups are current (Client)
  3. Upgrade Integrity (C3)
  4. Perform database upgrade (Client) (if required)
  5. Confirm Integrity is functioning correctly (Client)
  6. End downtime

Full System Upgrade

  • Upgrade Window: 1 day
  • Upgrade Process:
  1. Provision instance as per base specifications and provide SSH account details to C3 (Client)
  2. Ensure database backups are current (Client)
  3. Install Integrity (C3)
  4. Start downtime
  5. Perform database upgrade (Client) (if required)
  6. Confirm new Integrity instance is functioning correctly (Client)
  7. Cutover to new Integrity instance (Client)
  8. End downtime

Base Specifications

  • Ubuntu 12.04.2 LTS 64-bit
  • 8GB RAM
  • 48GB Disk
  • 2 CPU Cores
  • Port 22/80/443 out
  • Port 22/443 in
  • Network visibility of any required database servers
  • Network visibility of a mail server

Note that these are considered the minimum requirements for a system running Integrity.