ONAP on Vagrant

Definition

Started as an attempt to deploy ONAP services without relying on a OpenStack deployment, this project has been re-architectured to provide an automated tool for provisioning ONAP development environment. Covering some common development tasks such as the cloning source code repositories of specific component, compile java artifacts per component and building Docker images of specific component. This has been vehicle to standardize process and dependencies through an automated provisioning mechanism, as consequence its possible to setup a development environment using only a single instruction. Adding this tool into a CI/CD pipeline can prevent any compilation failure in the future and guarantee building image process works any time.

Problem Being Solved

• Reduce the barrier of entry to allow new ONAP developers to ramp up on to active development quickly

• Reduce the cost to the community in responding to simple environment setup questions faced by new developers

Minimal Requirements

Usage

• Windows

  ^{PS C:> cd integration\bootstrap\vagrant-onap}

  ^{PS C:\integration\bootstrap\vagrant-onap> Set-ExecutionPolicy Bypass -Scope CurrentUser}

  ^{PS C:\integration\bootstrap\vagrant-onap> .\tools\Run.ps1 <app_name>}

• Linux or Mac OS

  ^{$ cd integration/bootstrap/vagrant-onap $ ./tools/run.sh <app_name>}

supported options:

HTML documentation

For more information, see http://onap.readthedocs.io/en/latest/submodules/integration.git/bootstrap/vagrant-onap/doc/source/