...
- DuraCloud deployed in VPC, with 7.0, in Beanstalk (new env)
- Swap over DNS to enable
- DuraCloud MC deployed in VPC, with 7.0, in Beanstalk (new env)
- Swap over DNS to enable
- Update deployment documentation (as needed)
DB update
...
to latest version
...
and move to VPC
- the mill (set instance auto-scaling to 0) Turn off
- Turn off the MC (set instance auto-scaling to 0)
- DB snapshot Take
- Restore snapshot into VPC
- Create a
- new security group for the DB (as part of restore). Open port 3306 to DuraCloud and MC security groups
- Update new DB to 5.6 latest
- Move Update new DB to 5.7 latest
- Restart duracloud and mc (if needed)
- Turn mill back on
DB move to VPC
- Turn off the mill
- Take DB snapshot
- Launch DB in VPC from snapshot
- Update MC to point Mill Update config file in S3 to point to new VPC DB (add new version of duracloud config in S3)
- Start MC (set number of instances back to 2)
- Update Mill DB path in the MC to point to new VPC DB
- Launch MillRestart DuraCloud
- Mill config file in S3 to point to new VPC DB Update
- Restart MC
- Restart DuraCloud
- Shutdown non-VPC (add new version of mill config in S3)
- Update mill to use new 4.0 version
- Launch Mill
- Verify 0 connections to non-VPC DB, then stop (not terminate) DB
Chronopolis Bridge
- Work with Chronopolis to get Bridge updated