HOW IT WORKSThe maturity model utilizes the CMMI structure, in order to convey a progressive series of maturity phases across these key areas. All phases of the maturity model are intended to be transitional except Optimizing. It is intended that all maturity areas should work to achieve a common maturity level before proceeding with transitions to higher maturity levels. This will maximize collaboration, a shared understanding and optimized processes.

Each maturity area identifies activities, behaviors and skillsets that the team responsible for each functional area should be

OVERVIEWThe RoundTower Container Maturity Model is intended to guide organizations as they adopt containers for production-ready use. Containers provide a reliable and highly scalable runtime for applications but successfully adopting them requires a deliberate approach across a number of maturity areas.

CONTAINER MATURITY MODEL

EXCEPTIONS

Some maturity items exist in multiple maturity areas. This is intentional and represents a shared maturity item between the functional disciplines identified. For example, the implementation of Overlay Networks is identified as a maturity item for both the Security & Network functional teams as part of the Defined maturity level.

For more information, please contact your local RoundTower sales representative to speak with a container adoption specialist.

© 2019 RoundTower Technologies, LLC. All rights reserved. RoundTower Technologies is a registered trademark of RoundTower Technologies, Inc. | HQ : 5905 E. Galbraith Rd, 3rd Floor, Cincinnati, Ohio 45236 | 1.888.679.0752

proficient with in order to satisfy the requirements of each maturity level. When references to specific processes are made, such as Continuous Delivery, it is assumed that the process is fully implemented for all applications that are in scope for container usage.

When references to specific tooling categories are made, it is assumed that an appropriate tool has been selected, fully implemented and the operators of that system have been trained in its use for both legacy systems, if applicable, and containers.

CONTAINER MATURITY MODEL | CLOUD

For more information, call 888-679-0752 or email sales@roundtower.com

www.roundtower.com

CONTAINER MATURITY MODEL | CLOUD

Development Monitoring Security Storage Network

Inital

• Continuous Integration• Automated Unit Tests• Deployment Documents• Test-Driven Development

Transition• Code Review

• Infrastructure Monotoring • Alert Based on Server,

Network or Storage Metrics

• Issue Triage Based on Direct System Access

• OS Patching• Reactive Security Posture• Manual Firewall Rule

Creation & Audit• Little/No Visibility into

Development Process

• Local Storage• Manual Configuration • Storage Tightly Coupled

to Compute Node• Manual Configuration of

Storage Resources• IaaS Storage

• Legacy Underlay Neyworks

• Hardware Firewall & ACL Controls

• Manual Configuration & Audit

Managed

• Automated Integration Tests

• Static Analysis• Deployment Automation• Automated Dev & QA• Deployments

• Log Aggregation• Infrastructure Logging

Correlation• Role-Specific Dashboards• Issue Triage Based on

Aggregated Data

• Applocation Patching• Access Control

Configuration as Code• Automated Firewall

Rule Creation, Audit and Access Modeling

• Library/Module Whitelist

• Automated Volumne Creation

• Holistic Inventory of Storage Use

• Forecasting

• Network Configuration as Code

• Automated Load Balancer Configuration

• Holistic Network Configuration Catalog & Modeling

Defined

• Continuous Delivery• Automated Regression

Tests• Automated Production

Deployments

• Application Performance Monitoring

• Alerts Based on Application Metrics

• Application Logging Correlation

• Transition to Overlay Network

• Local Curated Library/Module Repo

• Fully Integrated into CD Pipeline

• Transition to Software Define Storage

• Deprecation of Direct VM/Storage Binding

• Primitive Container Storage

• Transition to Overlay Netwokring

• Automated Firewall Configuration

QuantitativelyManaged

• Automated User Acceptance Tests

• Automated Rollbacks/Remediation

• Deployment Success/Failure Metrics

• Correlation of Business Metrics to Appliations

• Predictive Analytics • Transition from Low-

Level Metrics to Business Metrics for Alerts

• Auto-Expiring Firewall Rules

• Active Artifact Scanning• Provide Requirements and

Tools for Automated Tests

• Sotrage Forecasting• Cloud Replication

• Auto-Expiring Network Configurations

• Network Configuration as Code

Optimizing

• ‘Quick’ Regression Test on Commit

• 100% Test Coverage

• Monitoring Data Informs Development Priorities

• Alerts Based on Business Metrics

• Programmatic Access, Not Manual

• Self-Documenting Systems

• Dynamic Class-Based Storage Scheduling

• Multi-Platform Storage Based on Policy

• Full Overlay Networking• Dynamic Network

Entitlements