Release
- Software release, in this order:
- duracloud-db
- duracloud (update duracloud-db dependency)
- duracloud-mc (update duracloud and duracloud-db dependency)
- duracloud-mill (update duracloud and duracloud-db dependency)
- duracloud-snapshot (update duracloud and duracloud-db dependency)
- Make sure everything makes it to sonatype and github (release)
- Update documentation (as needed)
Deploy
Beanstalk
- DuraCloud deployed in VPC, with 7.0, in Beanstalk (new env)
- DuraCloud MC deployed in VPC, with 7.0, in Beanstalk (new env)
- Update deployment documentation (as needed)
DB update to latest version and move to VPC
- Turn off the mill (set instance auto-scaling to 0)
- Turn off the MC (set instance auto-scaling to 0)
- Take DB snapshot
- 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
- 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
- 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
{"serverDuration": 60, "requestCorrelationId": "c643da6998e11271"}