The following tables list the tools used in ONAP development. This is intended for reference. For instructions on installing client tools and preparing to access the server-based tools, see Setting Up Your Development Environment.

See the Development Guides for specific additional tools required by different subsystems. Example tools include: nodejs, node-gyp (which in turn requires Python v.2.7.x and GCC), grunt-cli, and bower.

Server-Based Tools and Repositories

These tools and repositories are server-based. Some are accessed via a browser with no setup, other than obtaining a login and password. Others may require you to set environment variables, create private encryption keys, or make settings within client tools.

Gerrit code review server, hosting the Git repositories as well as controlling access, push, and review of new code. It also hosts the Jenkins job configuration in a Git repository that follows the same workflow.

ONAP Jenkins Master host, this host will only serve as a 'Display' as most of the jobs will be executed by 'minions' (slave hosts which are defined by using the Jenkins configuration repository in Gerrit).

ONAP Nexus 2 repository, this repo will hold Maven2 artifacts produced by builds (both Release and Snapshot, also Javadoc-mavensite), Access is automatically provided to builds by the maven settings on the Jenkins Master, see Jenkins job for more details. User should be able to access and browse artifacts through this URL.

ONAP Nexus 3 repository, this repo will hold Docker containers produced by ONAP builds. Access is automatically provided to builds by the maven settings on the Jenkins Master, see Jenkins job for more details. User should be able to access and browse artifacts through this URL.

There are three hosted repositories:

release repository: nexus3.onap.org:10002

snapshot repository: nexus3.onap.org:10003

staging repository: nexus3.onap.org:10004

The release repository contains the docker images at specific release cuts. The snapshot repository contains daily docker image builds. The staging repository contains docker images before a release cut. When approved, docker images in the staging repository are moved to the release repository.

There is an additional repository, nexus3.onap.org:10001, which is a proxy to the hosted repositories. By logging into the proxy repository, it is possible to access all the docker images contained in release, snapshot and staging repository. Also, from the proxy repository it is possible to access public docker images that are used in ONAP, such as MariaDB, HBASE, Cassandra, etc.

Access to hosted and proxy repositories is regulated by username and password:

username: docker

password: docker

These credentials provide read-only access to repositories. This is the only account that will work for community members to be able to access docker images.