As was pointed out by John Ng, currently ONAP requires a large openstack installation in order to run but in order for interest and development to really take off a local environment is the best path.

the exact specs can be adjusted but i think 16GB of ram, 4 cores and 150GB of free space is an acceptable goal for now (dev stack alone is 2 cores, 8GB and 60GB i believe and ecomp has to fit over that).

There will be several changes needed to accomplish this task and they will not all be listed here but some are:

• all components have to spin-able on one machine. This means it has to both be faster to spin up and also physically capable of running on one.
• Components have to rationalize some of their components duplication. Removal of duplicate datastores is a big one but also seperate vms for each components docker containers is also a sizing issue.
• Certain components have redundancy that is not needed on a local setup (or probably even a POC setup)