ONAP on Vagrant

This vagrant project pretends to collect information about a way to deploy and build ONAP project into a development environment.

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

Component	Requirement
Vagrant	>= 1.8.6
Hypervisor	VirtualBox or Libvirt
Operating System	Linux, Mac OS or Windows(In Progress)
Hard Disk	> 8 GB of free disk
Memory	> 12 GB

Execution:

current options include:

app_name	description
aai	Active and Available Inventory
appc	Application Controller
dcae	Data Collection Analytics & Events
mr	Message Router
mso	Master Service Orchestrator
policy	Policy
portal	Portal
robot	Robot
sdc	Service Design & Creation
sdnc	Software Defined Network Controller
vid	Virtual Infrastructure Development
vfc	Virtual Function Controller (WIP)

add http_proxy and https_proxy to your environment variables

Linux or Mac

$ export http_proxy=<proxy>
$ export https_proxy=<proxy>
$ export no_proxy=<no_proxy_urls>

Windows

C:\> setx http_proxy <proxy>
C:\> setx https_proxy <proxy>
C:\> setx no_proxy <no_proxy_urls>

force VirtualBox provider

C:\> vagrant up --provider=virtualbox

setup the default provider on Windows

C:\> setx VAGRANT_DEFAULT_PROVIDER=virtualbox

Bug reports and patches are most welcome. See the contribution guidelines.

Apache-2.0