Value Context:
- Develope Faster
- Less Boilerplate code, less errors
- CI/CD – Automated integrating and deployment to production
- Elasticity
- Improved DevOps
Lose Diego Cell
Page out To Garrent after BMC patrol 10 min
Determine VM is dead – 15-30
Create a new VM from a template – 10 Minutes
Add IP network - 10 minutes
ACLs, etc, chef
Install chef:
15 min – 30 min
Best Case 2-3 hours
PCF Auto rebalances lost apps/services to available cells
Between Round 2 and Rount 3, the project got pushed in May 2017due to priorities, and picked up again in Early 2018.
Lose Diego Cell
Page out To Garrent after BMC patrol 10 min
Determine VM is dead – 15-30
Create a new VM from a template – 10 Minutes
Add IP network - 10 minutes
ACLs, etc, chef
Install chef:
15 min – 30 min
Best Case 2-3 hours
PCF Auto rebalances lost apps/services to available cells
How quickly does the pipeline
Efficient and Effective
Keep everything in one tool
Bot fetches release notes for stemcell and tile.
Bot should be able to know which foundation and which tile using params set on the pipeline
Bot should know if the stemcell version is updated
Bot should know if the tile version is updated
Continuous integration environment would take the glob pattern for the product version and stemcell and upload and apply the changes to the ci environment when a version is published to pivnet that matches the glob pattern.
Pool Locks - ensures that only one change is flowing at a time
multiple pipelines can be running at a time but only one will be able to apply the changes
when the updates succeed to be applied a PR will be created to the next foundation in the chain