...
- 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
- Turn off the mill (set instance auto-scaling to 0)
- Take a DB snapshot
- Move to 5.6 latest
- Move to 5.7 latest
- Restart duracloud and mc (if needed)
- Update mill to use new 4.0 version
- Turn mill back on
DB move to VPC
- Turn off the millTurn off the MC (set number of instances instance auto-scaling to 0)
- Take DB snapshot
- Restore snapshot into VPC
- Create a new security group for the DB (as part of restore). Dev: open to world on 3306. Prod: open to VPC
- Update MC to point Mill to new VPC DB
- Update Mill config to point to new VPC DB (add new version of mill config in S3)
- Open port 3306 to DuraCloud and MC security groups
- Update new DB to 5.6 latest
- Update new DB to 5.7 latest
- 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
- Restart DuraCloud
- Shutdown non-VPC DB
- Launch Mill
- Update Mill config to point to new VPC DB (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