With VMware Tanzu Mission Control, we are providing customers with a powerful, API driven platform that allows operators to apply policy to individual clusters or groups of clusters, establishing guardrails and freeing developers to work within those boundaries.
The service provides the layer of automation and operational control enterprises need to utilize Cloud Native Buildpacks at scale. In particular, Build Service includes three key capabilities: automated image updates, image promotion, and build configurations.
On the top layer there is rapid change. On the bottom, change happens at a glacial pace. It’s this combination of everything, from seconds at the top, to millennia at the bottom, that give resilience to the system.
A key concept to this is that each layer has to respect the pace of another.
Can we take that governance and work with the platform team to codify, to automate that which they were doing on a per application basis – that’s, quiet frankly slowing down the delivery of the software – can we take that governance and can we have them work with the platform team to codfiy, to actually automate on a per application basis, have them expose that as a service on the platform
In other words: you should not only automate the audit three-ring binders of compliance, but enforce as much as possible in the platform.
The rest of the talk is good stuff on how think through re-arranging your organization to be all DevOps-y, with the help of Pivotal Cloud Platform to automate all the infrastructure and middleware stuff: