March 2022 Migration

[harper-wavra]

GitHub issue checklist:

Use the migration document here.

Before migration:

• [x] Ensure all expected updates are listed in the Migrations section in StreamStats OneNote. Contact the listed contact person if there are any questions.
• [x] Clean up any test data in the databases so when we update it goes as smoothly as possible.
• [x] Run:
  • [x] SS Integration Tests
  • [x] BatchTester
• [x] (if needed) Create new release for code (checklist, instructions).
  • [x] Client Code - IA QPPQ, IN coordinated reach, change of NSSServices to NSSServicesV2.
  • [x] NSSServices - QPPQ additions

Migration checklist:

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

Additional items:

• [x] NavigationServices and GagestatsServices were both updated on test, we should turn these back on prod.
• [x] Confirm that StreamStats is no longer using NSSServicesV2 (see #1197 for info) and that NSSServicesV2 are removed from prod and test
• [x] Update dist folders on Test for NSSServices; check web.config for "Production" and appsettings.json for DB credentials

[amedenblik]

Having issues with new NSSServices/database migration.

Plan for 3/25/22:

• [x] Change appConfig on StreamStats client on AWS:
  • [x] Remove "FDCTM" application from Iowa
  • [x] Confirm that it is using NSSServices (not NSSServicesV2)
• [x] Roll back NSSServices on both new prod machines to dist202107
• [x] Check appsettings.json and web.config in the NSSServices dist202107
• [x] Confirm that NSSServices is working on new prod machines
• [x] Do steps 8 through 11 above
• [x] Do step 15
• [x] Confirm that NSSservicesV2 is not being used
• [x] Update dist folders on Test for NSSServices; check web.config for "Production" and appsettings.json for DB credentials
• [x] Update the StreamStats Teams channel

Plan for 3/28/22 4/1/22:

• [x] Work on fixing NSSServices with prod database https://github.com/USGS-WiM/wim-infrastructure/issues/236
• [x] Update NSSServices dist folder path in IIS and check appsettings.json and web.config
• [x] Test new NSSServices
• [x] Update appConfig for StreamStats client on AWS: add back "FDCTM" to Iowa
• [x] Update the StreamStats Teams channel
• [x] Talk with Ryan about how to proceed with Location table in DB