Ok, so to clarify, OOM will not be building docker images. Instead, it will only consume/leverage the docker images that are built by the individual projects. Correct?
Regarding Python: In the absence of pip repos for Python, what we did in OPEN-O was to have the Python projects also provide a POM file that packages the necessary Python code into a zip file that then gets pushed to Nexus. Those zip files are then retrieved from Nexus by the docker build jobs like they do for Java artifacts. Thanks, Gary From: NG, JOHN [mailto:[email protected]] Sent: Tuesday, June 13, 2017 10:17 AM To: ROSE, DANIEL V <[email protected]>; Gary Wu <[email protected]>; Morales, Victor <[email protected]>; [email protected]; AGGARWAL, MANISHA <[email protected]>; FORSYTH, JAMES <[email protected]> Subject: RE: [onap-discuss] Standardizing docker-maven-plugin, com.spotify or io.fabric8 Re: OOM … OOM gets involved only after the application code is packaged as docker images in Nexus. Then OOM is triggered with a pre-defined deployment blueprint to execute the deployment. The deployment will contain reference to the docker image in Nexus and the target infrastructure on which the application is to be instantiated. ------------------------------------------------------- John Ng AT&T Labs – D2 Architecture 200 Laurel Ave, D5-3D16 Middletown, NJ 07748 +1 732 420 3742 +1 732 310 3253 (mobile) [email protected]<mailto:[email protected]> ------------------------------------------------------- From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of ROSE, DANIEL V Sent: Tuesday, June 13, 2017 11:34 AM To: Gary Wu <[email protected]<mailto:[email protected]>>; Morales, Victor <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; AGGARWAL, MANISHA <[email protected]<mailto:[email protected]>>; FORSYTH, JAMES <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] Standardizing docker-maven-plugin, com.spotify or io.fabric8 ***Security Advisory: This Message Originated Outside of AT&T *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information. I think that’s a good approach (with the caveat being that some things use python and I don’t know if we have a pip repo or anything) Thanks, Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: Gary Wu [mailto:[email protected]] Sent: Tuesday, June 13, 2017 11:28 AM To: ROSE, DANIEL V <[email protected]<mailto:[email protected]>>; Morales, Victor <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; AGGARWAL, MANISHA <[email protected]<mailto:[email protected]>>; FORSYTH, JAMES <[email protected]<mailto:[email protected]>> Subject: RE: [onap-discuss] Standardizing docker-maven-plugin, com.spotify or io.fabric8 I also would be in support of standardizing the docker builds. I think docker builds are now under the purview of the OOM project. Maybe someone from the OOM project can chime in? In OPEN-O, we had the Java merge jobs deploy Java artifacts to Nexus, and then the docker build jobs will pull the already-built Java artifacts from Nexus to build the docker images. The docker build jobs are then defined as downstream dependencies from the Java build jobs in Jenkins. We should be able to do something similar for ONAP to cleanly separate the Java builds from the docker builds. Thanks, Gary From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of ROSE, DANIEL V Sent: Tuesday, June 13, 2017 7:44 AM To: Morales, Victor <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]>; AGGARWAL, MANISHA <[email protected]<mailto:[email protected]>>; FORSYTH, JAMES <[email protected]<mailto:[email protected]>> Subject: Re: [onap-discuss] Standardizing docker-maven-plugin, com.spotify or io.fabric8 You could ask someone from aai like Harish, Jimmy or Manisha as they also use Spotify Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: Morales, Victor [mailto:[email protected]] Sent: Tuesday, June 13, 2017 10:33 AM To: ROSE, DANIEL V <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: Re: [onap-discuss] Standardizing docker-maven-plugin, com.spotify or io.fabric8 Thanks Daniel for answering this, one of the problems that I’ve faced with Spotify plugin is trying to build the image behind a corporate proxy, did you know if there a way to do it? From: "ROSE, DANIEL V" <[email protected]<mailto:[email protected]>> Date: Tuesday, June 13, 2017 at 9:26 AM To: Victor Morales <[email protected]<mailto:[email protected]>>, "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[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 ☺ Daniel Rose ECOMP / ONAP com.att.ecomp 732-420-7308 From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Morales, Victor Sent: Tuesday, June 13, 2017 10:23 AM To: [email protected]<mailto:[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://lists.onap.org/mailman/listinfo/onap-discuss
