Hi Shashank / Victor, Great initiative. Does this vagrant aid only in docker builds or does it support deployment as well - something like ONAP in a laptop also possible ? Could you also comment on resource requirements ?
BR, Viswa On Wed, Jun 14, 2017 at 12:06 AM, Shankar, Shashank Kumar < [email protected]> wrote: > Thank you very much for the details Manoop. > > Regards, > Shashank > > From: "TALASILA, MANOOP (MANOOP)" <[email protected]> > Date: Tuesday, June 13, 2017 at 11:28 AM > To: Shashank Kumar Shankar <[email protected]> > Cc: "ROSE, DANIEL V" <[email protected]>, "Morales, Victor" < > [email protected]>, "[email protected]" < > [email protected]> > > Subject: Re: [onap-discuss] Standardizing docker-maven-plugin, > com.spotify or io.fabric8 > > Hi Shashank, > > Portal’s Jenkin's jobs checkout the ecomp-sdk folder from “ecompsdkos > <https://gerrit.onap.org/r/#/admin/projects/ecompsdkos>" repo. The same > job executes the below shell script to build the portal container. I hope > this helps. > > Here is the reference to one of the Portal’s Jenkins job: > https://jenkins.onap.org/view/portal/job/portal-docker- > master-merge-docker-script/configure > > Regards, > Manoop Talasila > AT&T Labs Research > 1 AT&T Way, Bedminster, NJ 07921 > ···························································· > Office: +1 (908)901 2158 | e-mail: [email protected] > > > > "This e-mail and any files transmitted with it are AT&T property, > are confidential, and are intended solely for the use of the individual or > entity to whom this e-mail is addressed. If you are not one of the named > recipient(s) or otherwise have reason to believe that you have received > this message in error, please notify the sender and delete this message > immediately from your computer. Any other uses, retention, dissemination, > forwarding, printing, or copying of this e-mail is strictly prohibited." > > On Jun 13, 2017, at 2:21 PM, Shankar, Shashank Kumar < > [email protected]> wrote: > > Hi Daniel, > > Thanks for the info. We also had another question regarding the local > build of portal container. It looks like the os_build_febe.sh script in > portal expects to have a directory named ecomp-sdk as seen in [1] in the > root directory. But it seems like there is no directory named ecomp-sdk > there [2]. Any idea from where the SDK folder gets created or is it left > out? > > > [1] - https://git.onap.org/portal/tree/deliveries/os_build_febe.sh#n33 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_portal_tree_deliveries_os-5Fbuild-5Ffebe.sh-23n33&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w&m=9kcWxXd3Er0kISsFneyOtJtqLNooDSp4TfmuEf61S7A&s=qVyH0UDP83xEA-JyL8BGB-XYx1nqqW9EnQtpqVJpOow&e=> > [2] - https://git.onap.org/portal/tree/ > <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_portal_tree_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w&m=9kcWxXd3Er0kISsFneyOtJtqLNooDSp4TfmuEf61S7A&s=iLi3F8MdOB5Nz2G4ILfTJ1Hr6SXI9vV5xV-8hUJ9TNI&e=> > > Regards, > Shashank > > From: <[email protected]> on behalf of "ROSE, DANIEL V" > <[email protected]> > Date: Tuesday, June 13, 2017 at 7:26 AM > To: "Morales, Victor" <[email protected]>, " > [email protected]" <[email protected]> > Subject: Re: [onap-discuss] Standardizing docker-maven-plugin, > com.spotify or io.fabric8 > > We currently build docker images via scripts, via fabric8 plugin and via > Spotify plugin. Spotify and fabric8 should be easier to merge, the script > way may be harder. I leave it to others to decide if we should standardize > J > > Daniel Rose > ECOMP / ONAP > com.att.ecomp > 732-420-7308 > > *From:* [email protected] [mailto:onap- > [email protected] <[email protected]>] *On > Behalf Of *Morales, Victor > *Sent:* Tuesday, June 13, 2017 10:23 AM > *To:* [email protected] > *Subject:* [onap-discuss] Standardizing docker-maven-plugin, com.spotify > or io.fabric8 > > Howdy, > > Shashank and I started a vagrant project to collect the set of > instructions to build ONAP Docker Images[1]. What we have found is that not > all the projects are building their images in the same way. Even more, > some of them uses different maven plugins, for example data-router that > uses the Spotify plugin[2] and MSO uses Fabric8[3]. I’m not pretending to > start a discussion about which is better but shouldn’t be better to keep > one a standardize the method to build those images? > > Regards/Saludos > Victor Morales > irc: electrocucaracha > > [1] https://github.com/electrocucaracha/vagrant-onap/ > blob/master/lib/functions#L135-L154 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_electrocucaracha_vagrant-2Donap_blob_master_lib_functions-23L135-2DL154&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=RewA7K8yAmaw4CPli1rONNj1D50vCHLdbJloDLb2H6I&s=SpElGUuQgrGiChtxw93tMs9UlAu2PIllH6Ov9ouoh9k&e=> > [2] https://git.onap.org/aai/data-router/tree/pom.xml#n161 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_aai_data-2Drouter_tree_pom.xml-23n161&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=RewA7K8yAmaw4CPli1rONNj1D50vCHLdbJloDLb2H6I&s=iBMmiHFxvUguNUqfwqqFIt9QLnY9vRvRwe2fN0KTOVE&e=> > [3] https://git.onap.org/mso/tree/packages/docker/pom.xml#n101 > <https://urldefense.proofpoint.com/v2/url?u=https-3A__git.onap.org_mso_tree_packages_docker_pom.xml-23n101&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=2wwdGZ3YcpSivQ2Kio028A&m=RewA7K8yAmaw4CPli1rONNj1D50vCHLdbJloDLb2H6I&s=goOLaTLEbE3uwXebXnQqo1jBlnHoZu2jZmgdLdtHjWg&e=> > > > > _______________________________________________ > onap-discuss mailing list > [email protected] > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists. > onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c= > LFYZ-o9_HUMeMTSQicvjIg&r=WrNqy1qTY6qs8trIiLe-U2OvGp0SXnE4nO3a-LJ-q_w&m= > 9kcWxXd3Er0kISsFneyOtJtqLNooDSp4TfmuEf61S7A&s= > Bs8DM2osd1n6a8eNxViyupUMv8q9wv6ovYWq_cnhu_o&e= > > > > _______________________________________________ > onap-discuss mailing list > [email protected] > https://lists.onap.org/mailman/listinfo/onap-discuss > >
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
