Versions Compared

Old Version 67

changes.mady.by.user Adolfo Perez-Duran

Saved on

compared with

New Version 68

changes.mady.by.user Adolfo Perez-Duran

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

NameDescriptionVersion
DockerDocker engine

Linux/Intel version that supports docker manifest

Linux/aarch64 version that supports docker manifest

DockerDocker registry

Version that supports fat manifest.

Current version of the ONAP registry has been reported to lack support for fat manifests.

AlpineAlpine LinuxLatest version

Testing

...

Strategies

Background


Depending on the artifacts available on the code base of each project, changes made to the container build artifacts could undergo four levels of testing.

...

Testing Phase

CIA Project Contributors

Project Team

Integration Team

Image structure check

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


Container Sanity check (Unit testing)

Verify that
  • 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.


Unit testsComponent testingVerify that
  •  The container runs on their local development environment

When available:

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

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


Integration teststesting



  • 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 tests) 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.


...