blob: 00a8a2ac72d6e28fd073c55fda2ad11245a82352 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
# ONAP on Vagrant
[](https://api.travis-ci.org/electrocucaracha/vagrant-onap)
This vagrant project pretends to collect information about a way to deploy
and build [ONAP project](https://www.onap.org/) into a development environment.
### 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
---
| 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 |
---
## Execution:
#### deploying a single application
* 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>
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) |
| all_in_one | All ONAP services in a VM |
| testing | Unit Test VM |
#### generating documentation
The documentation of this project was written in reStructuredText
format which is located under the [docs folder](../blob/master/doc/source/index.rst).
It's possible to format this documents to HTML using Sphinix python
tool.
$ tox -e docs
This results in the creation of a new *doc/build/html* folder with
the documentation converted in HTML pages that can be viewed through
the prefered Web Browser.
## Contributing
Bug reports and patches are most welcome.
See the [contribution guidelines](CONTRIBUTING.md).
## License
Apache-2.0
|
