How mature is your cloud..

Using a maturity model is a very traditional way of answering this question – most of which will be 4 to 6 columns which start on the left with “no solution” through to the far right hand side where everything is working not only as designed but fully optimised.
Summarising the Open Data Centre Alliance Maturity model
  – None i.e. legacy apps on legacy infrastructure
 – 1 – awareness of cloud apps – some cloud computing components
 – 2 – processes for cloud adoption defined
 – 3 – Tooling and integration for automated cloud usage
 – 4 – Manual federation i.e. cloud aware apps deployed with metrics
 – 5 – Federated, interoperable, open cloud “Proactively enables business strategy”..
We are never short of further maturity models:
 – Business Capabilities
 – Technology Capabilities
 – IaaS Maturity
  -PaaS Maturity
 – SaaS Maturity
 – Info-aaS Maturity
Typically an organisation (if there is such one), will be around Level 3 i.e. some cloud technologies will have been deployed, using a level of orchestration, the provisioning will be done through virtualisation techniques so not withstanding manual process interventions, the speed for deployment is relatively quick.However, business processes are likely to have not changed within the development area. The key shift to benefits realisation therefore is the move to a DevOps culture.  So if we assume all the technology has been deployed and can be ascertained to be working around a L4 point of maturity – is this a mature cloud.  Technically the organisation can claim to have a mature cloud, but if the same dev techniques are being used then the reality is a very expensive platform has been deployed with a significant under-realisation of benefits.  Therefore it is critical then in parallel with any infrastructure/platform program that a business change program focusing on development techniques, tools and processes is run.  This will mean that the Infrastructure program when delivering in increments (as opposed to a traditional large deployment program) is aligned wholly to the updated development processes.
Moving to Devops is not an Infrastructure project – it is a cultural shift that won’t be achieved simply by providing the tools – no matter how good the tools are…

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s