My understanding is that due to project complexity (indeed it' huge), Vagrant 
has been introduced because it provides portable virtual software development 
I have seen similar situation earlier in another project I was involved into.

My understanding is that simplification of project focusing on Maven modules, 
dependencies and Docker images may lead to such situation that Vagrant is not 
Of course it's ideal situation and I was asking only if such option has been 
taken into consideration ??

Referring to pom files I was thinking of simplifying dependency management in 
SDC project.
For example scope <scope>compile</scope> is default in Maven and does not have 
to be added to dependency declaration - Maven resolves it with no problem.
It means that lines <scope>compile</scope> in pom files may be removed.


From: Morales, Victor <victor.mora...@intel.com>
Sent: Wednesday, March 7, 2018 3:13:40 PM
To: Migdal, Marcin (Nokia - PL/Wroclaw); Lando,Michael
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] SDC- local development - how to?

Can you elaborate more your approach to stop using vagrant? we used vagrant as 
supporting tool for ensuring that the scripts work in a base distro (or minimal 
dependencies) besides its capability to recreate everything automatically. 
Regarding the attempt to optimize Maven files, AFAIK that is done by OParent 
project [1]

Victor Morales

[1] https://git.onap.org/oparent/

From: "Migdal, Marcin (Nokia - PL/Wroclaw)" <marcin.mig...@nokia.com>
Date: Wednesday, March 7, 2018 at 5:39 AM
To: Victor Morales <victor.mora...@intel.com>, "Lando,Michael" 
Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>
Subject: Re: [onap-discuss] SDC- local development - how to?


Have you thought about stop using Vagrant and focus only on pure Docker images?
I think such approach could simplify few things - no setting env variables, 
coping configuration files.

Has there also been an attempt to optimize Maven files?
I can see that optimization of content can be easily achieved with no big 
Expected outcome would be:
- thin pom files

- better readability

- easier dependency management



From: Morales, Victor <victor.mora...@intel.com>
Sent: Tuesday, March 6, 2018 5:46:56 PM
To: Migdal, Marcin (Nokia - PL/Wroclaw); Lando,Michael
Cc: onap-discuss@lists.onap.org; Wejs, Maciej (Nokia - PL/Wroclaw)
Subject: Re: [onap-discuss] SDC- local development - how to?

Hi Marcin,

Just one additional think about the vagrant provider, even when VirtualBox is 
the default one you can use Libvirt.  There is a script that installs it





Mirror of https://gerrit.onap.org/r/#/admin/projects/integration

The other alternative is to use the scripts in your own environment without 
having to install a Virtual Machine, I tried to explain that here


I don’t recommend it because the dependencies will be installed in your host 
machine and eventually those can be omitted or assumed, resulting in 
heterogonous development environments.


Victor Morales

From: "Migdal, Marcin (Nokia - PL/Wroclaw)" <marcin.mig...@nokia.com>
Date: Tuesday, March 6, 2018 at 5:31 AM
To: "Lando,Michael" <ml6...@intl.att.com>
Cc: "onap-discuss@lists.onap.org" <onap-discuss@lists.onap.org>, Victor Morales 
<victor.mora...@intel.com>, "Wejs, Maciej (Nokia - PL/Wroclaw)" 
Subject: Re: [onap-discuss] SDC- local development - how to?


Thank you for suggestions.

Especially link: 

is very useful.
I can see that Vagrant is being used for local development with Virtual Box. 
Unfortunately, VirtaulBox is not a good option for running at machine hosting 
as OS Linux.

What I am still thinking of is something simpler.
I have JDK and Maven available at my machine (having Windows, Linux, Solaris, 
zOS, whatever) so that I am able to execute Maven's goals responsible for 
compilation, testing and packaging of SDC Maven modules.
Now I would like to run SDC locally in order to define PNF of VFN within SDC 

Lets assume I have Apache Tomcat/Jetty available.
I can see that modules:
a) sdc/catalog-be
b) sdc/catalog-fe
generate war modules that can be run on any Java web container, so I think they 
could be good starting points.

So would it be a good idea to focus on mentioned artifacts?
Also from Vagrant file I can see that elasticsearch & cassandra are also needed.



From: Lando,Michael <ml6...@intl.att.com>
Sent: Monday, March 5, 2018 8:59 AM
To: Migdal, Marcin (Nokia - PL/Wroclaw)
Cc: onap-discuss@lists.onap.org; Morales, Victor
Subject: RE: [onap-discuss] SDC- local development - how to?


You can find instructions here:


you can find all the info on SDC here:



Michael Lando

Opensource TL , SDC

AT&T Network Application Development · NetCom

Tel Aviv | Tampa | Atlanta | New Jersey |Chicago


Office: +972 (3) 5451487

Mobile: +972 (54) 7833603

e-mail: ml6...@intl.att.com<mailto:ml6...@intl.att.com>

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Morales, Victor
Sent: Friday, March 02, 2018 16:16
To: Migdal, Marcin (Nokia - PL/Wroclaw) <marcin.mig...@nokia.com>; 
Subject: Re: [onap-discuss] SDC- local development - how to?

Hey Marcin,

We tried to collect most of the instructions (clone and compile, install 
dependencies, build docker images, etc.) into the vagrant-onap script [1].  
This is its documentation [2], but it’s not covering the configuration and 
installation of the IDE, I suggest to install it manually and use the opt 
folder given that it’s sharing the source code between host and guest computers.


Victor Morales



 on behalf of "Migdal, Marcin (Nokia - PL/Wroclaw)" 
Date: Thursday, March 1, 2018 at 12:37 AM
To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" 
Subject: [onap-discuss] SDC- local development - how to?


Is there any instruction how to setup SDC for development in any IDE?

onap-discuss mailing list

Reply via email to