Docker build environment capable of producing a version of ONOS and needed apps that make the SD-Fabric control plane.
The name TOST comes from the early days of the SD-Fabric project. It stands for Trellis ONOS Stratum Tofino. We keep this name for backward compatibility.
Typically the ONOS restful api would be used to include apps after ONOS is started.
We provide multiple build targets for the Makefile. Versions of the components are defined in
stable version points to well known stable commits and
master branch points to ONOS master and to the tip of the TOST components. DOCKER_TAG is used to select which version to build, by default points to
onos-build is used to build a specialized Docker image of ONOS (
tost-onos) that will contain only the apps needed by TOST. It depends on
onos target, which is used to setup the
onos workspace for the build. It clones
onos if it does not exist in the workspace, it will try to checkout the ONOS_VERSION first and in case of failure will try to download the patchset from remote repository. ONOS_VERSION is defined in
Makefile.vars.DOCKER_TAG file, overriding the variable at run time it is possible to build a different version of ONOS.
# Build a tost-onos image from the current workspace. make onos-build
# Build a tost-onos image from the tip of the onos-2.2 branch. make ONOS_VERSION=onos-2.2 onos-build
# Build a tost-onos image from the review 12345. make ONOS_VERSION=ref/changes/72/12345/1 onos-build
Makefile will build also the apps. These are the apps currently integrated in the script: trellis-control, trellis-t3, up4 and fabric-tna. For each one, there is a build target.
appname-build builds with the version specified in the
Makefile.vars.DOCKER_TAG, using the following sources in order: (1) Maven central (for released versions or snapshots); (2) Local source code (for local branch not yet pushed); (3) Gerrit/Github (for pending review in the form of refs/changes/... or pending pull request). As a prerequisite, the script prepares
mvn_settings.xml file, creates the
local-apps folder and checks out the code if it is not present (relies on
appname target). APPNAME_VERSION, defined in
Makefile.vars.DOCKER_TAG file, can be overridden at runtime.
# Build trellis-control from the source code. make trellis-control-build
# Build up4 app from the source code. make up4-build
apps-build is an additional target that automates the build process of the apps building one by one all the apps.
# Build one by one all the apps. make apps-build
Finally, the last build target is
tost-build. It builds a
tost monolithic image using as base the
tost-onos image. It basically adds the external apps used by TOST. It does not activate all the required apps. This step is performed during the deployment and the required apps are specified in the chart.
# Build a tost image from the current workspace. make tost-build
appname targets to downloads commits, files, and refs from remotes.
# Update one by one all the apps. make apps
clean target to remove the local artificats generated by the tool.
# Cleans the workspace. make clean
We provide multiple push target for the Makefile. Typically, you need to first login by
docker login command to push the image on a repository.
onos-push will push the
tost-push will push the
tost image on the defined DOCKER_REGISTRY and DOCKER_REPOSITORY.
make DOCKER_REPOSITORY=onosproject/ tost-push
There are two special targets used by the CI/CD jobs:
docker-push. The first target automates the build process of the
tost image (
tost-build). While the second one, it is just a
tost-push called in a different way (temporary). Feel free to use them if you are ok with the prerequisites steps.