...

The basic structure of the CD part of the flow is an hourly check for new ISO images. If a new ISO build is found at https://nexus.akraino.org/content/repositories/images-snapshots/TA/release-1/images/ then it is downloaded and a deployment to bare metal OpenEdge19 cluster is attempted. If the ISO installs successfully, then the RIC install is attempted as a post-install job and some tests are automatically run.

Currently the only ISO is the Telco Appliance ISO. The REC Continuous Deployment Jenkins (the private per contributor part of the diagram below) installs TA on bare metal and then installs the RIC using a REC workflow script. The future plan is to incorporate the RIC into a REC ISO, at which point the TA ISO and the REC ISO will be differentat build time rather than install time. When this happens, the Akraino Continuous Integration Jenkins (the shared/public part of the diagram below) with produce a REC ISO in addition to the TA ISO. The TA ISO will continue to exist and be available for use in the creation of new blueprints in the TA blueprint family, but REC won't need the TA ISO anymore because the REC ISO will be built directly from the TA Gerrit repositories and build products (e.g. RPMs) combined with RIC components from the O-RAN-SC Gerrit and image repository. Right now there is only the TA ISO because we haven't built the CI jobs to integrate RIC source code and TA source code into a combined REC ISO.

Continuous Integration → Continuous Deployment Flow

...