IVI Framework Viewer

Containers

C3

Manage the platforms that facilitate the organization and virtualization of software containers.

Improvement Planning

Practices-Outcomes-Metrics (POM)

Representative POMs are described for Containers at each level of maturity.

2Basic
  • Practices
    • Start to split the core systems into modules to give a better structure for development, build, and deployment.
    • Use an API-managed approach to describe internal dependencies.
    Outcomes
    • The core systems are modularized and use APIs to communicate between modules.
    • This provides the basis for the next level of abstraction and modularization.
    Metric
    # of core systems that are modularized and use APIs.
3Intermediate
  • Practice
    Use abstraction and other techniques to identify and break out modules into components that are self-contained and that can be separately deployed.
    Outcome
    Systems are further abstracted as the high-level system modules are divided into self-contained components that are separately deployed.
    Metric
    % of system modules that are divided into self-contained components.
4Advanced
  • Practice
    Split the entire system into self-contained components, and adopt a strict API-based approach to inter-communication so that each component can be deployed and released individually.
    Outcomes
    • Each system component can be deployed and released separately.
    • All components, interactions, and interfaces are fully understood and documented.
    Metric
    % of the system that is deployed as individual components/containers.
5Optimized
  • Practice
    Reduce the shared infrastructure by treating infrastructure as code and bind it to the application components.
    Outcomes
    • The system is totally reproducible from source control, from the O/S all the way up to the applications layer.
    • This enables the reduction of complexity and cost in other tools and techniques (for example, in disaster recovery) that serves to ensure that the production environment is reproducible.
    • Instead of having a separate process, disaster recovery is simply done by pushing out the last release from the pipeline like any other release.
    • This together with virtualization gives extreme flexibility in setting up test and production environments with minimum manual effort.
    Metrics
    • % cost savings due to containerization.
    • % of the data centre that is managed and provisioned using infrastructure as code/machine-readable definition files.