Table of Contents |
---|
Note | ||
---|---|---|
| ||
This wiki is under construction |
Setup
https://github.com/electrocucaracha/vagrant-onap
Going through Victor Morales' excellent port to Vagrant (which includes DCAE) - currently bringing up the 5th VM after 45 min (under full build/docker image load)
Progress
OSX - hanging on 4th (after dns, message_router, sdc) AAI vm trying to ssh into the box - tomcat is not up on 8181 - will verify that 1.1.0-SNAPSHOT is building properly on the box - or revert to 1.0.0 artifacts
Windows fails on init of message_router
Redhat 7.3 (VM under VMWare) - triple level - in progress
...
sudo vi /etc/yum.repos.d/virtualbox.repo
yum install VirtualBox-5.1
rpm -i ../vagrant_1.9.5_x86_64.rpm
Still failing on same AAI provisioning - looking into why the war is not up
==> aai: curl: (7) Failed to connect to 10.0.3.1 port 8181: Connection refused
==> aai: + RES=0
==> aai: + [[ 0 -lt 5 ]]
==> aai: ++ curl http://10.0.3.1:8181/sdc1/rest/healthCheck
==> aai: ++ grep -c OK
==> aai:
==> aai:
==> aai: %
==> aai:
==> aai: T
==> aai: otal % Received % Xferd Average Speed Time Time Time Current
==> aai: Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0
0 0 0 0 0 0 0 0 --:--:-- 0:00:20 --:--:-- 0
==> aai: curl: (7) Failed to connect to 10.0.3.1 port 8181: Connection refused
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
Component | Requirement |
---|---|
Vagrant | >= 1.8.6 |
Provider | VirtualBox, Libvirt or OpenStack |
Operating System | Linux, Mac OS or Windows |
Hard Disk | > 8 GB of free disk |
Memory | > 12 GB |
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:
app_name | description |
---|---|
aai | Active and Available Inventory |
appc | Application Controller |
dcae | Data Collection Analytics & Events |
mr | Message Router |
mso | Master Service Orchestrator |
msb | Microservices Bus Project |
policy | Policy |
portal | Portal |
robot | Robot |
sdc | Service Design & Creation |
sdnc | Software Defined Network Controller |
vid | Virtual Infrastructure Development |
vfc | Virtual Function Controller |
vnfsdk | VNF SDK |
vvp | VNF Validation Program |
multicloud | Multi Cloud |
ccsdk | Common Controller SDK |
all_in_one | All ONAP services in a VM |
testing | Unit Test VM |
HTML documentation
For more information, see http://onap.readthedocs.io/en/latest/submodules/integration.git/bootstrap/vagrant-onap/doc/source/
View file | ||||
---|---|---|---|---|
|
...