/
2017-01-25 Migration Meeting notes

2017-01-25 Migration Meeting notes

Owned by Tim Whitlock (Deactivated)
Last updated: Feb 15, 2017

Date

Attendees

Goals

  • Discuss network changes and form opinion on how this may be done
  • Identify how testing could be done on the VMs before going live
  • Identify how the backup should be configured
  • Identify what testing of the backup will be required prior to going live
  • Identify testing required post migration for backup
  • Identify a prefered migration path/process

Discussion items

TimeItemWhoNotes
Network ChangesTim Whitlock (Deactivated)
  • Changes to the VLAN structure will require configuration changes to the VMs.
  • Extra network interface on internet side (N3 would be unchanged?)
  • Extra routing table entries
  • Exact details unclear at the moment.
 VM Testing configuration with network changes & testingTim Whitlock (Deactivated)
  • Fully testing the VMs will not be possible for them all due data feeds required.
  • Will need to confirm VMs function as expected and where possible check data flows.
  • Internet websites should be fairly straight forward. N3-internet proxy, Redhat license manager will be harder.
 Backup solutionTim Whitlock (Deactivated)
  • Should be possible to verify functionality
  • Truly testing the "slow" backups will only be possible when the systems are live due to the way the data changes occur.
  • We will start with managed backups so we can ensure any issues are ironed out before possibly taking over the backup management.
  • Need to ensure we have documented methods for asking for backup changes, restores etc.
 Backup testing before during and after migrationTim Whitlock (Deactivated)
  • Further backup testing will be required after we are live to verify all is working as expected.
  • In particularly will need to do full test restores of patientview and healthshare to verify that the backups work and are complete.
 Migration PlanTim Whitlock (Deactivated)
  • AIMES "are working on a migration plan"
  • We would anticipate doing some test runs of the process with all the VMs and verifying that they have transferred correctly and work.
  • If changes to the vlan are required we will need to have a documented change list for each affected VM that should be applied to get it working. This change will need to be tested as well.
    

Action items

  • George Swinnerton Create first draft of Internal Expectations/Technical Requirements document to use as guidance during discussions with AIMES Initial draft to be available for next AIMES call scheduled on