March 2024 Migration

[amedenblik]

Use the migration document here.

Before migration:

• Ensure all expected updates are listed in the Migrations section in StreamStats OneNote. Contact the listed contact person if there are any questions.
• Clean up any test data in the databases so when we update it goes as smoothly as possible.
• Run:
  • SS Integration Tests
  • BatchTester
• (if needed) Create new release for code (checklist, instructions).

Migration checklist:

• 1) Turn Off TestWeb
• 2) Snapshot existing TestWeb
• 3) Create 2 ProdWeb(a&b)-new EC2 instances from TestWebSnapshot
• 4) Update config files on prod services
• 5) Test the ArcGIS desktop licenses on ProdWebA and ProdWebB
• 6) Turn off shared E: drive
• 7) Edit Task Scheduler scripts
• 8) Test the services
• 9) Point prod load balancer to new prod web machines
• 10) Reassign Elastic IP addresses from old to new prod web machines
• 11) Turn on TestWeb
• 12) (if needed) Update StateServices map service
• 13) Deploy new production code
  • Prod Batch Processor v1.2.0
• 14) Update Databases
  • Gagestats
• 15) Run:
  • SS Integration Tests
  • BatchTester
• 16) Post in StreamStats Team about the migration status & provide notes for news item if applicable
• 17) Once you’ve confirmed the migration has gone well (3 business days later):
  • Terminate old ProdWebA, ProdWebB machines
  • Delete their attached data volumes (the 1800GB data drives)

Additional items:

[harper-wavra]

Moved SC data from prod to test. Once Kitty confirms the correct data is on test:

• delete sc_newData from test (xml and data)
• delete streamstats-raw-data/SC_24MarchMigration/ bucket

[amedenblik]

The only updates on the migration notes are related to gagestats database. Updated issue accordingly.

We will do the StreamStats client code release (to include gageplots branch) at a later date.