Tagged by CORD Jenkins version-tag job: 547, for Gerrit patchset: 34945
[VOL-5031] - baseline build for repo:voltha-onos

  o Update copyright notice ending date.
  o Patch will trigger a clean build to screen for pre-existing failures.

  o Remove duplciate apt-get call, only need to refresh the index once.

Change-Id: Iacf97a88266d300ec6985d233f388f1b25c5c90c
51 files changed
tree: 26ed638c582e81d44bd10403c97411cc56698182
  1. .gitignore
  2. .gitreview
  4. Dockerfile.voltha-onos
  5. Makefile
  6. README.md
  8. app-install.sh
  9. config.mk
  10. dependencies.xml
  11. etc/
  12. get-local-oars.sh
  13. makefiles/
  14. mvn_settings.sh
  15. mvn_settings.xml
  16. network-cfg-example.json
  17. network-cfg.json
  18. tests/

VOLTHA ONOS Development Build Environment

Docker build environment capable of producing a version of onos and needed apps that can run with voltha. Typically the onos restful api would be used to include apps after onos is started. This provides a build environment that includes current released and enabled oar files or optionally can import locally built oar files.


By default the current set of onos apps is imported from a maven repository as read from dependencies.xml.

make build

Including locally built oar files

If you wish to include your own onos apps then export the LOCAL_ONOSAPPS environment variable to have locally built oar files copied from local_imports/oar into the docker build environment rather than pulling from maven. Any oar files in this directory will be included and set to start on onos startup.

Note! its assumed that the standard apps (olt-app, sadis, aaa, and dhcpl2relay) build environment is one up directory from this build environment. Modify get-local-oars.sh if this is not the case:

export LOCAL_ONOSAPPS=true
make build

Including custom config

The voltha-onos build also includes a mechanism to build in a default onos network-config.json file. You can simply edit network-cfg.json before building the docker image. Or if using docker-compose or k8s volume mount over the built in file within the container /root/onos/config/network-cfg.json with your own.

For example, in a docker-compose file:

    - "8101:8101" # ssh
    - "6653:6653" # OF
    - "8181:8181" # UI
      ONOS_APPS: 'drivers,openflow-base'
    - "/var/run/docker.sock:/tmp/docker.sock"
    - "./network-cfg.json:/root/onos/config/network-cfg.json"
    - default
    restart: unless-stopped