Please enable JavaScript.
Coggle requires JavaScript to display documents.
Increase the real impact of OpenShift at the client site, Goal - Coggle…
Increase the real impact of OpenShift at the client site
Client delivery team
Increase the real impact of OpenShift at the clientsite with on development team deploying and going to production
The team can destroy and rebuild the Lab cluster within X amount of time
Increase understanding of setting up multiple OpenShift clusters with infrastructure-as-code for support
A sample client workload from the target application team is deployed on the Lab cluster. (Workload is deployed through the MVP pipeline, and the client demonstrates it using their own login and build-in OpenShift tools for X, Y, Z)
An MVP Non-Prod cluster is installed with the same process used in lab and runs a sample hello-world workload.
The team can destroy and rebuild the Non-Prod cluster within X amount of time and the app teams can redeploy via automation & IaC
Increase readiness to grow OpenShift as a self-service platform
MVP client requirements for storage, monitoring, logging, and security are understood, and if possible, delivered on the Lab cluster.
On Non-Prod, the client app team prepares their workload for MVP deployment on production (enhance pipeline with some of the following: unit test, integration tests, code quality, etc.)
Increase awareness of the value of a cross-functional (infra & app dev) team dedicated to OpenShift services
Increase knowledge of the specific work ahead of the client to better support them
Increase live workload operating on an MVP OpenShift platform to at least one meaningful workload
An MVP Lab cluster runs a sample hello-world workload
The client identifies and shares the rationale for the targeted workload for MVP go-live
MVP client requirements for storage, monitoring, logging, and security are operational on Non-Prod
An MVP Production cluster runs a sample hello-world workload
MVP client requirements for storage, monitoring, logging, and security are operational on Production
MVP client requirements for operational readiness and live traffic on production are understood and demonstrated by the production infrastructure.
The client application team deploys their workload on MVP production and takes live traffic.
Client leadership
increase the commitment to using continual and automated deployments
The client prepares their targeted workload for OpenShift and deploys it to Non-Prod via the second iteration of the pipeline; the client demonstrates the operational workload.
Increase organizational support to consistently measure and demonstrate the success of tech adoption and process changes
Establish a baseline by conducting MDT Baseline Workshop
Install Pelorus
Goal
Actor
Impact
Demonstrable Deliverables