| commit | 2c7a4db6ac0b1212b64c64873cf82427ace2c1cf | [log] [tgz] |
|---|---|---|
| author | pierventre <pier@opennetworking.org> | Fri Jun 26 21:24:00 2020 +0200 |
| committer | pierventre <pier@opennetworking.org> | Fri Jul 10 17:01:49 2020 +0200 |
| tree | a1129cda581fa6cac38f58462cd8e4b5f5d9d283 | |
| parent | b27fbfce76c8d98613dd5841fd3143b69573177e [diff] |
[AETHER-255] First version of the tost-onos image and build scripts Change-Id: I14a22158c2ad51779497bc5435af7b28b410beff
Docker build environment capable of producing a version of ONOS and needed apps that can run with TOST. Typically the ONOS restful api would be used to include apps after ONOS is started.
We provide multiple targets for the Makefile
onos is used to setup the workspace for the build. It is possible to build the image using a specific branch (export ONOS_BRANCH variable) or a specific review (export ONOS_REVIEW variable). It clones onos if does not exist in the workspace and uses current workspace unless above vars are defined.
onos-build is used to build a specialized Docker image of ONOS that will contain only the apps needed by TOST. It depends on onos-checkout target
# Build a Docker image from the current workspace. make onos-build
# Build a Docker image from the onos-2.2 branch. export ONOS_BRANCH=onos-2.2 && make onos-build
# Build a Docker image from the review 123456. export ONOS_REVIEW=12345 && make onos-build
Use target clean to remove the local artificats generated by the tool.
make clean
We provide multiple push-target for the Makefile. You need to first login by docker login command to push the image on a repository.
onos-push will push the produced ONOS_IMAGENAME on the defined DOCKER_REGISTRY and DOCKER_REPOSITORY.
export DOCKER_REPOSITORY=onosproject/ make onos-push