Dan, the tag release-1.1.0 is the default value in current HEAT template (as said in https://jira.onap.org/browse/SDNC-196). That means that as soon as the release is released it should point to the stable branch of SDN-C. If it’s 1.1.0, fine (even if I would louve to have the branch merged soon with code in order to be able to test the full heat deployment _before_ the release).
Remember that all the people who want to try ONAP will be pointed to the Heat template (and helm template later on), so if it doesn’t work it will be shameless at the very least... Le 15 nov. 2017 à 22:33, TIMONEY, DAN <dt5...@att.com<mailto:dt5...@att.com>> a écrit : Geora, The release-1.1.0 branch is pre-Amsterdam seed code. You want to be using the master branch, which should be working fine. The sdnc_install.sh script sets GERRIT_BRANCH (which is where it does the pull) to the contents of /opt/config/gerrit_branch.txt. I’m not sure how that’s set (Marco would know that better than me), but it sounds like that’s set to release-1.1.0 instead of master. Marco – can they just update that file and re-run sdnc-install.sh? Dan -- Dan Timoney SDN-CP / OpenECOMP SDN-C SSO Please go to D2 ECOMP Release Planning Wiki<https://wiki.web.att.com/display/DERP/D2+ECOMP+Release+Planning+Home> for D2 ECOMP Project In-take, 2016 Release Planning, Change Management, and find key Release Planning Contact Information. From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of "BARSKY, GEORA" <geo...@amdocs.com<mailto:geo...@amdocs.com>> Date: Wednesday, November 15, 2017 at 4:16 PM To: "PLATANIA, MARCO" <plata...@research.att.com<mailto:plata...@research.att.com>>, Arun Arora <arun_ar...@outlook.com<mailto:arun_ar...@outlook.com>>, "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>>, "sylvain.desbure...@orange.com<mailto:sylvain.desbure...@orange.com>" <sylvain.desbure...@orange.com<mailto:sylvain.desbure...@orange.com>>, "OBRIEN, FRANK MICHAEL" <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>> Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails Hi Marco, In addition to below , I also noticed that there is an issue with /opt/sdnc/installation/src/main/yaml/docker-compose.yml . It points to openecomp/images instead of onap sdnc: image: openecomp/sdnc-image:latest During the installation it seems like this code is pulled from release-1.1.0 branch : As a result we fail : Status: Image is up to date for nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest<http://nexus3.onap.org:10001/onap/sdnc-dmaap-listener-image:1.2-STAGING-latest> Pulling sdnc (openecomp/sdnc-image:latest)... ERROR: {"message":"repository openecomp/sdnc-image not found: does not exist or no pull access"} Thanks Geora Barsky Amdocs Technology 647-688-1039 <image001.png> Follow us on Facebook<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.facebook.com_amdocs_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo&s=Dw1-UGXnb-wT2UsV7miTa839sklh6NZYqmUybN7T-I8&e=>, Twitter<https://urldefense.proofpoint.com/v2/url?u=http-3A__twitter.com_amdocs&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo&s=Ra-vPiL3TdS6TfrtkPQ_O1F5PbHahT2Vc9jpjyu_qko&e=>, LinkedIn<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.linkedin.com_company_amdocs&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo&s=Zv9_KYcaWy--k2eplJHg4kAoqGucbhYjLZtDytwMcLs&e=>, YouTube<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.youtube.com_amdocsinc&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo&s=qwDjnw3jv6tlX0LOZw0iKpGndJAuj-oamu0gmPRcbQo&e=>, Google+<https://urldefense.proofpoint.com/v2/url?u=https-3A__plus.google.com_105657940751678445194&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo&s=vsM7wmSd0b4KGyO5Y-BGORyohptG77YsMAsUr6Sfwag&e=> and the Amdocs blog network<https://urldefense.proofpoint.com/v2/url?u=http-3A__blogs.amdocs.com_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo&s=QbJpaKW_Y-MRqu2gvVqMjPhxUbf6hLR7od8KAlcxTdU&e=>. From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of PLATANIA, MARCO (MARCO) Sent: Wednesday, November 15, 2017 1:27 PM To: Arun Arora <arun_ar...@outlook.com<mailto:arun_ar...@outlook.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; sylvain.desbure...@orange.com<mailto:sylvain.desbure...@orange.com>; Michael O'Brien <frank.obr...@amdocs.com<mailto:frank.obr...@amdocs.com>> Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails Arun, Sylvain, Michael, I ran docker pull for SDNC WindRiver and it worked. I noticed the same issue with MSB though, because the docker version in Heat is wrong. It is v1.0.0, while it should be 1.0.0 (without v). I’m going to submit a change soon, please update your local Heat env. Arun, If you are using an old heat template, please switch to the latest one: https://gerrit.onap.org/r/gitweb?p=demo.git;a=tree;f=heat/ONAP;h=f948399f5fcbe2300f0d7b8417792aea4682425d;hb=refs/heads/master<https://urldefense.proofpoint.com/v2/url?u=https-3A__gerrit.onap.org_r_gitweb-3Fp-3Ddemo.git-3Ba-3Dtree-3Bf-3Dheat_ONAP-3Bh-3Df948399f5fcbe2300f0d7b8417792aea4682425d-3Bhb-3Drefs_heads_master&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo&s=aV_dNDQ2_v-hokG2PIcvliJAVqGhhPK_K6NOrTtcxh8&e=> /opt/config/nexus_docker_repo.txt in the SDNC VM is used by the vm_init script to point to the Nexus repository. Make sure you have port 10001 instead of 10003 in that file. Marco From: <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Arun Arora <arun_ar...@outlook.com<mailto:arun_ar...@outlook.com>> Date: Wednesday, November 15, 2017 at 12:23 PM To: "onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>" <onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>> Subject: Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails Following JIRA Ticket: https://jira.onap.org/browse/SDNC-102<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SDNC-2D102&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jJs8089honCN-dSntDLJkfuXkr4ZTgk-PpoTTqBomVc&s=asydkDlpEShSZQIMXuHNQ7zrJgNmbroB84JkI_eCamY&e=> was created for this issue and marked as Resolved and Closed. However, the issue still seems to be present. In comments it was mentioned to change the port from 10003 to 10001 in docker-compose.yml. But I didn't find any such port in /opt/sdnc/installation/src/main/yaml/docker-compose.yml. Can someone provide me a working hack.. Thanks, Arun Arora [SDNC-102] SDNC Failed Robot Health Check - ONAP<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_SDNC-2D102&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jJs8089honCN-dSntDLJkfuXkr4ZTgk-PpoTTqBomVc&s=asydkDlpEShSZQIMXuHNQ7zrJgNmbroB84JkI_eCamY&e=> jira.onap.org<https://urldefense.proofpoint.com/v2/url?u=http-3A__jira.onap.org&d=DwQFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=KgFIQiUJzSC0gUhJaQxg8eC3w16GC3sKgWIcs4iIee0&m=jJs8089honCN-dSntDLJkfuXkr4ZTgk-PpoTTqBomVc&s=ZcMPuZKSmxB27OcQnSd9LjOVMVY_LGpM_PDUduDlfFc&e=> No reviews matched the request. Check your Options in the drop-down menu of this sections header. ________________________________ From: onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org> <onap-discuss-boun...@lists.onap.org<mailto:onap-discuss-boun...@lists.onap.org>> on behalf of Arun Arora <arun_ar...@outlook.com<mailto:arun_ar...@outlook.com>> Sent: Wednesday, November 15, 2017 10:37:33 PM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Subject: [onap-discuss] [SDNC] sdnc_vm_init.sh fails ERROR: {"message":"repository onap/sdnc-image not found: does not exist or no pull access"} Hi All, I am seeing this error since yesterday. I tried to re-pull SDNC dockers afresh. For that I deleted all dockers along with all the files/ directories downloaded in /opt when sdnc_install.sh runs. I tried this many times but the I receive the same error above in each trial. What may be the reason of this error? I doubt it is some local setup issue as I re-pulled other VMs as well along with SDNC but didn't see any such error. Is this seen by someone else? Any possible solutions? Thanks, Arun Arora 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://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=qLcfee4a2vOwYSub0bljcQ&m=eXJisYORbRfyG3_zkheRr5K_kPifNiBrsdBg35kOtbo&s=dvF7_lA0imaqmVJcCSeFVl9CIYvDL9_DlVSj1dhraKM&e=> _________________________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
