Borislav. Hi, I think I need your help with pushing images to nexus3 (I can manually build but a manual push fails) - as we discussed - I also looked at the docker-maven-plugin examples you mentioned below - and dcae which builds images - getting a 500 on the apt-get install nodejs section of Ubuntu-sdnc-image:20 in this case running a maven deploy.
As we discussed in one of our last ONAP calls there are at least 3 (OOM, CLI (Kanagaraj), Policy) of us that could share info on getting new images up to nexus3 so we can consume them both in the heat and kubernetes deployments we are all working on. In my case I am having issues pushing a built pgaas image for the first time https://jira.onap.org/browse/OOM-62 We can compare notes and store docker procedures here for everyone - https://wiki.onap.org/display/DW/Docker+DevOps Details I login fine $docker login -u docker -p docker nexus3.onap.org<http://nexus3.onap.org/>:10001 Login Succeeded Docker build is OK - docker push is not obrienbiometrics:pgaas michaelobrien$ docker build -t nexus3.onap.org:10001/openecomp/dcae/pgaas -f Dockerfile . Sending build context to Docker daemon 23.55kB Step 1/29 : FROM ubuntu:16.04 ---> ccc7a11d65b1 Step 2/29 : RUN apt-get update && apt-get -y install maven openjdk-8-jdk unzip python-pip curl dnsutils vim gawk wget openssh-client-ssh1 ---> Using cache ---> e27620f35717 Step 3/29 : RUN pip install pyyaml ---> Using cache ---> 40d785873ab8 Step 4/29 : RUN apt-get update && apt-get install -y postgresql libpq5 repmgr python-psycopg2 python3-psycopg2 libgetopt-java ---> Using cache ---> b968a0c5df2e Step 5/29 : RUN rm -f /usr/sbin/policy-rc.d ---> Using cache ---> e851f3a8b924 Step 6/29 : RUN mkdir -p /opt/app ---> Using cache ---> 2c02cfb595de Step 7/29 : RUN (cd /opt/app ; curl -Lo apache-groovy-binary-2.4.6.zip https://dl.bintray.com/groovy/maven/apache-groovy-binary-2.4.6.zip ) ---> Using cache ---> c91ea06d0a94 Step 8/29 : RUN (cd /opt/app ; unzip apache-groovy-binary-2.4.6.zip ) ---> Using cache ---> da19722c0a77 Step 9/29 : RUN mkdir -p /opt/app/java/jdk ---> Using cache ---> ec843d4f7865 Step 10/29 : RUN ln -s /usr /opt/app/java/jdk/jdk170 ---> Using cache ---> d447e308b16b Step 11/29 : RUN mkdir -p /opt/app/groovy ---> Using cache ---> 25d7815b2867 Step 12/29 : RUN ln -s /opt/app/groovy-2.4.6 /opt/app/groovy/246 ---> Using cache ---> 88dd80141003 Step 13/29 : RUN if [ ! -e /home/dcae ]; then useradd -m -s /bin/bash dcae; fi ---> Using cache ---> e107c2cff531 Step 14/29 : RUN curl -s -k -f -o /tmp/org.openecomp.dcae.storage.pgaas-cdf_1.0.0.deb https://nexus.onap.org/content/sites/raw/org.openecomp.dcae.pgaas/deb-releases/org.openecomp.dcae.storage.pgaas-cdf_1.0.0.deb ---> Using cache ---> 82d0be1ce886 Step 15/29 : RUN curl -s -k -f -o /tmp/org.openecomp.dcae.storage.pgaas-postgresql-prep_1.0.0.deb https://nexus.onap.org/content/sites/raw/org.open ecomp.dcae.pgaas/deb-releases/org.openecomp.dcae.storage.pgaas-postgresql-prep_1.0.0.deb ---> Using cache ---> 746f5f53852d Step 16/29 : RUN curl -s -k -f -o /tmp/org.openecomp.dcae.storage.pgaas-postgresql-config_1.0.0.deb https://nexus.onap.org/content/sites/raw/org.openecomp.dcae.pgaas/deb-releases/org.openecomp.dcae.storage.pgaas-postgresql-config_1.0.0.deb ---> Using cache ---> 22ff58b2de79 Step 17/29 : RUN curl -s -k -f -o /tmp/org.openecomp.dcae.storage.pgaas-pgaas_1.0.0.deb https://nexus.onap.org/content/sites/raw/org.openecomp.dcae.pgaas/deb-releases/org.openecomp.dcae.storage.pgaas-pgaas_1.0.0.deb ---> Using cache ---> d9a52792b793 Step 18/29 : RUN curl -s -k -f -o /tmp/org.openecomp.dcae.storage.pgaas-pgaas-post_1.0.0.deb https://nexus.onap.org/content/sites/raw/org.openecomp.dcae.pgaas/deb-releases/org.openecomp.dcae.storage.pgaas-pgaas-post_1.0.0.deb ---> Using cache ---> efbbcf83b747 Step 19/29 : RUN apt-get update && apt-get install -y sudo && rm -rf /var/lib/apt/lists/* ---> Using cache ---> ad5a0b50f77a Step 20/29 : RUN mkdir -p /opt/tools ---> Using cache ---> a45ef3366f1e Step 21/29 : RUN mkdir -p /dbroot/pgdata ---> Using cache ---> bf5f882317bf Step 22/29 : RUN mkdir -p /dbroot/pglogs ---> Using cache ---> 666884979215 Step 23/29 : EXPOSE 5432 ---> Using cache ---> 7d2bee59e349 Step 24/29 : VOLUME /opt/tools ---> Using cache ---> 5789985b883b Step 25/29 : VOLUME /dbroot/pgdata ---> Using cache ---> 6691fcd153ce Step 26/29 : VOLUME /dbroot/pglogs ---> Using cache ---> c223d38f5301 Step 27/29 : COPY setup.sh /usr/local/bin/entrypoint.sh ---> Using cache ---> ffc35d82be53 Step 28/29 : RUN chmod a+x /usr/local/bin/entrypoint.sh ---> Using cache ---> ae4f2e93242f Step 29/29 : ENTRYPOINT usr/local/bin/entrypoint.sh ---> Using cache ---> d3cf07a80918 Successfully built d3cf07a80918 Successfully tagged nexus3.onap.org:10001/openecomp/dcae/pgaas:latest obrienbiometrics:pgaas michaelobrien$ docker images REPOSITORY TAG IMAGE ID CREATED SIZE nexus3.onap.org:10001/openecomp/dcae/pgaas latest d3cf07a80918 9 minutes ago 1.03GB obrienbiometrics:pgaas michaelobrien$ docker push nexus3.onap.org:10001/openecomp/dcae/pgaas The push refers to a repository [nexus3.onap.org:10001/openecomp/dcae/pgaas] b4f440dc89cd: Preparing b1a91ac0378f: Preparing a6ab361d9284: Preparing 01d34e08a9e0: Preparing 67166bc93a3a: Preparing f0cc66c45ab4: Waiting d09c777e7ae4: Waiting e30c66e473f0: Waiting 01b1f5510a52: Waiting 94f82c263b44: Waiting a1df65c04630: Waiting 3c8596501eba: Waiting 17ba7123d342: Waiting 1fcfa71c715c: Waiting 7ed908687894: Waiting 764d7670ed3c: Waiting 28868d65df7c: Waiting a55b0c3f0a89: Waiting 372ceae4f0a6: Waiting 63a268fe22b1: Waiting 28312f9d3023: Waiting ef1d2d917acc: Waiting a09947e71dc0: Waiting 9c42c2077cde: Waiting 625c7a2a783b: Waiting 25e0901a71b8: Waiting 8aa4fcad5eeb: Waiting error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "\n<!DOCTYPE html>\n<html>\n<head>\n <title>404 - Nexus Repository Manager</title>\n <meta http-equiv=\"Content-Type\" content=\"text/html; charset=UTF-8\"/>\n\n\n <!--[if lt IE 9]>\n <script>(new Image).src=\"https://nexus3.onap.org/favicon.ico?3.2.0-01\"</script>\n <![endif]-->\n <link rel=\"icon\" type=\"image/png\" href=\"https://nexus3.onap.org/favicon-32x32.png?3.2.0-01\" sizes=\"32x32\">\n <link rel=\"mask-icon\" href=\"https://nexus3.onap.org/safari-pinned-tab.svg?3.2.0-01\" color=\"#5bbad5\">\n <link rel=\"icon\" type=\"image/png\" href=\"https://nexus3.onap.org/favicon-16x16.png?3.2.0-01\" sizes=\"16x16\">\n <link rel=\"shortcut icon\" href=\"https://nexus3.onap.org/favicon.ico?3.2.0-01\">\n <meta name=\"msapplication-TileImage\" content=\"https://nexus3.onap.org/mstile-144x144.png?3.2.0-01\">\n <meta name=\"msapplication-TileColor\" content=\"#00a300\">\n\n <link rel=\"stylesheet\" type=\"text/css\" href=\"https://nexus3.onap.org/static/css/nexus-content.css?3.2.0-01\"/>\n</head>\n<body>\n<div class=\"nexus-header\">\n <a href=\"https://nexus3.onap.org\">\n <div class=\"product-logo\">\n <img src=\"https://nexus3.onap.org/static/images/nexus.png?3.2.0-01\"/>\n </div>\n <div class=\"product-id\">\n <div class=\"product-id__line-1\">\n <span class=\"product-name\">Nexus Repository Manager</span>\n </div>\n <div class=\"product-id__line-2\">\n <span class=\"product-spec\">3.2.0-01</span>\n </div>\n </div>\n </a>\n</div>\n\n<div class=\"nexus-body\">\n <div class=\"content-header\">\n <img src=\"https://nexus3.onap.org/static/rapture/resources/icons/x32/exclamation.png?3.2.0-01\"/>\n <span class=\"title\">Error 404</span>\n <span class=\"description\">Not Found</span>\n </div>\n <div class=\"content-body\">\n <div class=\"content-section\">\n Not Found\n </div>\n </div>\n</div>\n</body>\n</html>\n\n" From: [email protected] [mailto:[email protected]] On Behalf Of Borislav Glozman Sent: Sunday, August 6, 2017 10:48 To: Kanagaraj Manickam <[email protected]>; [email protected] Subject: Re: [onap-discuss] [oom][cli] CLI deployment from OOM Hi, 1. You need to create a directory with all your products and also write a Dockerfile descriptor. You can take a look at other projects and do similar in sdnc project (like sdnc/oam/installation/sdnc) a. Take a look at the docker file: sdnc\oam\installation\sdnc\src\main\docker\Dockerfile b. Take a look at the pom: sdnc\oam\installation\sdnc\pom.xml i. You will find here docker-maven-plugin among others. ii. Then you can run a maven (something like mvn deploy) command in Jenkins and the images will be created and uploaded. 2. Once you will have a docker image (produced from 1.), I can help you with the k8s deployment. a. You can look at an example of sdnc deployment descriptors at oom project: oom\kubernetes\sdnc\*.yaml files Thanks, Borislav Glozman O:+972.9.776.1988 M:+972.52.2835726 From: Kanagaraj Manickam [mailto:[email protected]] Sent: Friday, August 4, 2017 7:46 AM To: Borislav Glozman <[email protected]<mailto:[email protected]>>; [email protected]<mailto:[email protected]> Subject: RE: [oom][cli] CLI deployment from OOM Hi Borislav Glozman, We would like to deploy the CLI as part of OOM ONAP deployment and we are currently investigating on making the required changes for building CLI docker as part of CI. So could you please help us 1. How to create the docker image for CLI as part of Jenkins CLI 2. How to create the k8s deployment ? Thanks Kanagaraj M This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
