Page Comparison

...

• Proposed name for the project: Docker/OCI Images - Best Practices and Tools

Project description:

Container technology is a popular packaging method for developers and system administrators to build, ship and run distributed applications.

...

This project takes a communal approach to capturing and developing best practices, guidance, recommendations and common tools for the design of images built using Dockerfiles.

Scope:

This project will develop a specification for the recommended structure of Dockerfiles based on industry best practices

...

•     Best practices for the design of space-efficient and scalable images built using Dockerfiles
•     Best practices for crafting Dockerfiles
•     Best practices for the development of platform-agnostic images
•     Dockerfile templates to
  •      Capture, automate and share experience across projects
  •      Reduce duplication
  •      Jumpstart image development
  •      Optimize resource consumption
  •      Develop vendor-agnostic images     
• New Docker builder patterns and tools
  • Explore and issue recommendation on the use of different front-ends
  • Evaluate and issue recommendations on the use of BuildKit

Out of scope:

  This project doesn't tackle the design or architecture of microservices-based applications.

Having said that, the project acknowledges the synergy and expects to collaborate with ONAP projects such as the Microservices project, OOM and Integration.

Architecture Alignment:

    The goals of this project are in perfect alignment with ONAP's architecture principles and architecture quality attributes.

    In particular, this projects suppoorts the themes adopted for Beijing and Casablanca: Platform Maturity Requirements (S3P) and Portability

 S3P:

Portability:

Software portability is the ability to use the same software artifacts (images/containers) in different environments.

...

Having best practices and Dockerfile templates that simplify the use of official multi-platform (OS, CPU) base images makes ONAP portable by enabing  ONAP deployment in diferent environments.   

Other Information:

• Vendor Neutral
• Meets Board policy (including IPR)

Use the above information to create a key project facts section on your project page

Project Proposal Deck

Project proposal deck is available here.

Key Project Facts:

Primary contact: Adolfo Perez-Duran

Release Components Name:

Note: refer to existing project for details on how to fill out this table

Resources committed to the Release:

Note 1: No more than 5 committers per project. Balance the committers list and avoid members representing only one company. Ensure there is at least 3 companies supporting your proposal.

Note 2: It is critical to complete all the information requested, that will help to fast forward the onboarding process.