Image structure check

• • The image build properly and
  • That all dependencies related to the new base image are resolved correctly.

Container Sanity check

• The local build process completes successfully; with not container build errors.

•  The build changes result in a structurally sound container image.
• Libraries and dependencies are resolved correctly.

Note: for containers that can't run standalone without changes to the base image, there is no expectation that they will run after the migration to a new base image.

The strategy in this case is to move this test to the CSIT testing phase.

•  The container runs on their local development environment

When available:

• Execute test harnesses and unit tests provided by the project team.

Teams that have CSIT jobs will run these tests automatically in the build environment.

This testing is independent of the base image used to build the container.

Integration

testing

• Contributed changes will be subject to the integration tests designed and executed by the Integration team or the project team.

• In the Integration lab env, ONAP containers are deployed and ran inside VMs and those VMs use ubuntu-1604-cloud-amd64 image, however, the host OS is transparent to containers.

• The integration team uses OOM to deploy whatever ONAP container images are pulled from the registry.

The Integration team is not concerned with whether an image is based on Alpine, Ubuntu or something else.

This testing is independent of the base image used to build the container.

Contract (Pairwise) testing

Pairwise testing will proceed according to current best practices under the guidance of the project teams or the Integration team.           

This testing is independent of the base image used to build the container.

Note: CIA contributors would help resolve issues that are demonstrably caused by the new base image.