Viswa, We have focused more in testing and improving the components individually. Last time that I tested the All in One configuration was having some issues in several dependencies, besides that port conflict that you mentioned.
Regards/Saludos Victor Morales From: Viswa KSP <[email protected]> Date: Friday, July 28, 2017 at 10:26 AM To: Victor Morales <[email protected]> Cc: "[email protected]" <[email protected]>, "[email protected]" <[email protected]> Subject: Re: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap projectavailable into Integration repo Victor, Would this tool be able to stand up all components of ONAP in single 12GB Ubuntu instance ( just going with the minimum reqs published in read.me<http://read.me> ). Last I heard there were port conflicts to bring-up all components within single machine. Was that resolved? BR, Viswa On Fri, Jul 28, 2017 at 8:21 PM, Morales, Victor <[email protected]<mailto:[email protected]>> wrote: Hey Huabing, That’s true, this tool clones/pulls source code, compile java artifacts, build docker images, etc. Regards/Saludos Victor Morales From: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Date: Thursday, July 27, 2017 at 8:02 PM To: Victor Morales <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: Re:[onap-discuss] [all] [integration] [bootstrap] vagrant-onap projectavailable into Integration repo Hi Victor, Thanks for bring this useful tool to ONAPer ! I'd like to understand the relationship between this project and OOM. It seems that this project just intend to provide a handy development environment for ONAP developer and will not be part of OOM, which aim to the production deployment. Do I understand correctly? Thanks, Huabing Original Mail Sender: <[email protected]<mailto:[email protected]>>; To: <[email protected]<mailto:[email protected]>>; Date: 2017/07/27 06:57 Subject: [onap-discuss] [all] [integration] [bootstrap] vagrant-onap projectavailable into Integration repo ONAPers, The vagrant-onap project started as an alternative to deploy ONAP services in Virtual Machines hosted locally without the need of an OpenStack deployment. After several changes and additions to this project, its goal has changed to provision a Development Environment. Its current implementation support different providers (like VirtualBox, Libvirt and OpenStack) and has been tested in some OS(like Ubuntu, Mac OS). This is an ongoing effort to collect instructions and standardize the methods to build and compile ONAP artifacts, as you can expect there are many things that are still missed so I encourage to everyone to take a look of the scripts placed into lib folder[1] and improve the documentation[2][3]. We have plans to add more Unit Tests to this project[4] to validate any change. Thanks Victor Morales irc: electrocucaracha [1] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib [2] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/README.md [3] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/doc/source [4] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/tests _______________________________________________ onap-discuss mailing list [email protected]<mailto:[email protected]> https://lists.onap.org/mailman/listinfo/onap-discuss
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
