...

Scope

What is this release trying to address?

During the Dublin Release, CIA will put in practice the best practices and principles identified and validated during Casablanca.

By applying such best practices the project aims at alleviating two ONAP pain points

1. High resource consumption due to large large container images

2. Long build and deploy times due to large container images

3. The inability to run ONAP on more than one hardware platform (cpu architecture) and cloud infrastructure

Use Cases

This release is targeting ONAP's Minimal Environment and, as a stretch goal, the vFW use case.

Minimum Viable Product

The MVP for this release will be delivered in an incremental and iterative approach.

The work will be approached in phases:

Phase 1: Minimize the footprint of container images used on ONAP Minimal Environment

Phase 2: Build platform-agnostic container images (i.e. multi-cpu architecture support) for ONAP minimal environment

Phase 3: Minimize the footprint of container images used on the vFW use case.

Phase 4: Build platform-agnostic container images (i.e. multi-cpu architecture support) for vFW use case.

Phase 5: Review Dockerfiles for the vFW use case, identify patterns and propose re-usable Dockerfile templates.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Stories

...

Container

image

...

Multi-Platform

Support

...

Image Footprint

Minimization

...

Used by

Minimal

Environment

...

Used by

vFw

Use Case

...

Scope

What is this release trying to address?

During the Dublin Release, CIA will put in practice the best practices and principles identified and validated during Casablanca.

By applying such best practices the project aims at alleviating two ONAP pain points

1. High resource consumption due to large large container images

2. Long build and deploy times due to large container images

3. The inability to run ONAP on more than one hardware platform (cpu architecture) and cloud infrastructure

Use Cases

This release is targeting ONAP's Minimal Environment and, as a stretch goal, the vFW use case.

Minimum Viable Product

The MVP for this release will be delivered in an incremental and iterative approach.

The work will be approached in phases:

Phase 1: Minimize the footprint of container images used on ONAP Minimal Environment

Phase 2: Build platform-agnostic container images (i.e. multi-cpu architecture support) for ONAP minimal environment

Phase 3: Minimize the footprint of container images used on the vFW use case.

Phase 4: Build platform-agnostic container images (i.e. multi-cpu architecture support) for vFW use case.

Phase 5: Review Dockerfiles for the vFW use case, identify patterns and propose re-usable Dockerfile templates.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

Stories

appc

MultiVIM/MultiCloud

(Working in coordination with Project Team)

Longer term roadmap

Working on the vFW use case will provide the foundation for the optimization of the entire onap container base.

...

Resources

Fill out the Resources Committed to the Release centralized page.

Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

...

• The team maintains documentation and guidelines on the their wiki page.

Other Information

• Vendor Neutral

...