FinanceServersMigrationPlan

From Newroco Tech Docs
Jump to navigationJump to search

Overview

Steps before down time

  • Create the VMs according to their needs
  • Install all packages required
  • Take full DB dumps from the old VMs
  • Restore dumps to new VMs
  • Edit /etc/hosts and add names and IPs to all VMs involved so they can be addressed by DNS rather than IPs:
10.0.10.49 finance.thehumanjourney.net
10.0.10.24 timesheets.thehumanjourney.net
10.0.10.43 hrdb.thehumanjourney.net
10.0.10.180 tenders.thehumanjourney.net
10.0.10.130 archives-db.thehumanjourney.net
192.168.98.24 mapdata.thehumanjourney.net
  • Open port 5432 on the firewall (IP restricted) for timesheets to access finance
  • Open port 5432 on the firewall (IP restricted) for HRDB to access timesheets
  • Test "pull time sheets" script on PMDB interface - this will test both ways finance - timesheets connection
  • Test making changes to staff on PMDB interface - this will test HRDB connection to timesheets, admin, finance and also RabbitMQ sending messages from Finance to tenders and archives
  • Test making changes to projects on PMDB interface - this will test finance RabbitMQ sending messages to archives
  • Test making changes to an episode on Tenders interface and see if the changes were transmitted to mapdata into tenders table on oasites DB

Steps during down time

Steps after down time

  • Test all interfaces work well
  • Test special functions that might no longer work
    • Make staff changes in HRDB and check if the change was propagated to TRS, Finance, Admin DB on Finance VM, Tenders, Archives
    • Make project changes on Finance and see if the change was propagated to Archives - this checks if RabbitMQ worked well
  • Monitor any support tickets related to any of these services and first find a cause in the migration done.

Finance

HRDB

Time Sheets

Tenders