Re: [onap-discuss] 答复: RE: [clamp] Questions about https://jira.onap.org/browse/CLAMP-80

Hi, The tosca parser is not yet available in R2 code. Br, Martial From: yuan@zte.com.cn [mailto:yuan@zte.com.cn] Sent: jeudi 11 janvier 2018 02:40 To: Ngueko, Gervais-Martial Cc: onap-discuss@lists.onap.org Subject: 答复: RE: [onap-discuss] 答复: RE: [clamp] Questions

Re: [onap-discuss] OOM Installation Problem | Unable to bring up Portal Pod

Hi Mandeep, Alexis, Michael, Viswa , Thanks a lot for your quick responses and suggestions. As Michael suggested that RAM should be more than 55 G, so I increased it to 128G. After increasing RAM size , I am able to install ONAP using OOM. Thanks! Regards, Karthik. On 11 Jan 2018 03:42,

[onap-discuss] for sdc vnfd model , could a user-defined property be added in the node property for vdu, cpd, storage

hi, for sdc vnfd model , could a user-defined property be added in the node property for vdu, cpd, storage .. for example: -type define- UserDefine: derived_from: tosca.datatypes.Root properties: name: type: string

Re: [onap-discuss] [sdc] Error in SDC on dependency validation in ONAP R1

Hello, We couldn’t reproduce the problem in our environments. Would it be possible for you to send us the HEAT files + CSAR after you’ve added the dependency? Also, just to make sure if you’re running with the latest build of R1. Regards, Vitaliy Emporopulo Software Architect @ Amdocs From:

[onap-discuss] [dcae] DCAE failing in Amsterdam MR

Hi DCAE team, Since last night the Amsterdam MR has been failing to spin up DCAE components. Can you take a look? You can use the SB-05 environment to debug the issue. Thanks, Gary ___ onap-discuss mailing list onap-discuss@lists.onap.org

[onap-discuss] [uui] UUI intermittently failing in Amsterdam MR

Hi UUI team, The UUI component seems to intermittently fail to pass health check in the Amsterdam maintenance release. Can you take a look? You can use the SB-04 environment to debug the issue. Thanks, Gary ___ onap-discuss mailing list

[onap-discuss] OOM Option to preserve VNC Jump server ?

I have been re-installing ONAP via OOM’s cd.sh script a couple times to test patches. Turns out the jump server (VNC ) on a re-install loses all the data as expected. Its a bit of a pain. Would it be feasible to preserve that container as an option on a re-install via cd.sh or put its file

[onap-discuss] Did You Know?

Did You Know? OOM makes services available on any Node in a K8S cluster using a NodePort. This allows a service to be reachable on any node in the cluster, using a statically assigned NodePort (default range: 3-32767). NodePorts are automatically mapped to the internal port of a

[onap-discuss] [integration] RE: Jenkins CSIT requiring attention

It looks like the latest versions of the selenium robot libraries were incompatible with ExtendedSelenium2Library. I’ve changed to script to use a known-good older version here: https://gerrit.onap.org/r/#/c/27973/ The latest run of

Re: [onap-discuss] OOM Robot Distribute

So why not submit a change to testsuite so they split it into two IP’s and modify the robot_vm_install.sh to ocpy the input into the two variable so that we can use the same asdc_interface.robot for either HEAT or OOM ? Testsuite will be adding to the asdc_interface.robot over time (as in this

Re: [onap-discuss] OOM Robot Distribute

That’s a good solution Brian, not that we haven’t thought about it. We’re looking into un-forking every config bit we forked to integrate the fork we’ve done correctly in each project. ONAP has 80+ containers, hence we forked config at first, but there is a long journey in front of us to

Re: [onap-discuss] OOM Robot Distribute

It’s the same IP address in the HEAT deployment. In OOM it’s not the same. sdc-fe.onap-sdc for frontend —> GLOBAL_INJECTED_SDC_FE_IP_ADDR sdc-be.onap-sdc for backend —> GLOBAL_INJECTED_SDC_BE_IP_ADDR Alexis > On Jan 11, 2018, at 4:07 PM, FREEMAN, BRIAN D wrote: > > The front

Re: [onap-discuss] OOM Option to preserve VNC Jump server ?

Hi Brian, I have opened https://jira.onap.org/browse/OOM-576 to track this and it is currently being investigated. Thanks for the suggested improvement, Mike. On Jan 11, 2018, at 11:59 AM, FREEMAN, BRIAN D > wrote: I have been re-installing ONAP via

[onap-discuss] Committer Promotion Request for [appc]

Dear TSC, Please consider request below for Committer Promotion for APPC project. https://wiki.onap.org/pages/viewpage.action?pageId=22251669 One of our existing committers has indicated that he will step down from Committer to Contributor role. Existing Committers have all voted +1 on Taka

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Hi Lusheng, 10.12.5.80 is a docker cache local within the Wind River lab that allows us to dramatically speed up ONAP spin-up. Unfortunately it only supports http. The workaround for this is to configure the VM to allow insecure registries

Re: [onap-discuss] [E] [oom] OOM Installation Problem | Unable to bring up Portal Pod

Viswa, Karthik, Hi, we are here to help you through this - I may have replied to an earlier mail. Just verifying you are OK now - it looks like you have increased your ram after talking to Mandeep and myself - yes portal is at the top of the hierarchy and will not start unless all the

Re: [onap-discuss] OOM Robot Distribute

The front end and back of SDC are the same IP address so its not clear to me why you had to change anything in the asdc_interface.robot ? Brian root@onapoom3:/dockerdata-nfs/onap/robot/robot/resources# diff asdc_interface.robot asdc_interface.robot.old 47,48c47,48 < ${ASDC_FE_ENDPOINT}

[onap-discuss] FW: HF2 Network Downtime Jan 12 2018

Appologies for the late notice, the lab where the ONAP developers POD is located will be off line tomorrow morning from 07:00 to 09:00 PST, see below message from Intel IT. I was added to the IT mailing list today, thus, in the future notices to the ONAP community will go out in advance. Br, -

Re: [onap-discuss] clarification question on ONPA R2 resilience requirement

Hi Lusheng, Thanks for the questions & attention to detail: For #1, go with what is on the detailed requirements page... just "reroute" is necessary. However, if you combine it with the scalability requirement, then there will be a need to add a new instance within the site... whether that

Re: [onap-discuss] OOM Robot Distribute

Brian, For some reason, we had to fork asdc_interface.robot script, that’s why it’s not up-to-date, please create a ticket for this and assign it to me. The reasons are hostname resolution are different from HEAT and OOM. Robot can point to HEAT’s VM IP, whereas robot point to the service

[onap-discuss] OOM Robot Distribute

Alexis, Michael, I was using robot ete-k8s.sh from amsterdam release and the version of asdc_interface.robot in dockerdata-nfs was out of date. I cant seem to find where it got loaded from since the asdc_interface.robot wasn't compatible with the robot testsuite (the return parameter list from

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Gary, The log of dcae bootstrap docker container shows that there was a transient problem last night. One of the artifacts hosted by LF Nexus server failed to download (getting “502 bad gateway” response). I dumped the docker log to file /opt/log-docker-15afe9c18611-20180110 on the dcae

Re: [onap-discuss] OOM Robot Distribute

> On Jan 11, 2018, at 4:00 PM, Alexis de Talhouët > wrote: > > Robot can point to HEAT’s VM IP, whereas robot point to the service directly.. Not clear. In the HEAT setup, robot points to the SDC VM IP for that resources, whereas for the OOM setup, we point directly

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

+1 Thanks & regards, Dhananjay Pavgi Tech Mahindra Ltd +91 98220 22264 -- Original message-- From: MAHER, RANDA Date: Fri, 12 Jan 2018 05:29 To: onap-...@lists.onap.org; Cc: onap-discuss@lists.onap.org; Subject:[onap-tsc] Committer Promotion Request for

[onap-discuss] MUSIC Proposal for Beijing

TSC Members, I met this afternoon with members of the OOM project and MUSIC team. I confirmed the following Although on the key common area among both projects is resiliency, OOM’s scope is life cycle management of the ONAP platform itself. Scope is the following

[onap-discuss] VNF SDK 01-12-2018 Meeting - Developer Wiki - Confluence

Dear all, Here is agenda for this Friday 6am VNFSDK meeting. Talk to you soon. https://wiki.onap.org/display/DW/VNF+SDK+01-12-2018+Meeting Thank you, Tina IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Gary, Unfortunately, that is not an easy fix. Is it possible to add https to this registry? If not, This is what I did to fix SB-05: getting into dcae-bootstrap vm and run this: sudo sed -ie 's/10.12.5.80:5000/nexus3.onap.org:10001/g' /opt/app/config/invinputs.yaml

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Ok, as long as we know what the issue was, I’ll think of a workaround. I’ll probably end up customizing the wind river heat template to exclude dcae-bootstrap VM from using the local docker cache, as you described. Thanks for your help! -Gary From: JI, LUSHENG (LUSHENG)

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

+1 Please add the candidate’s company plus existing committers. On Jan 11, 2018, at 6:57 PM, MAHER, RANDA > wrote: ***Security Advisory: This Message Originated Outside of AT *** Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Re: [onap-discuss] [E] RE: [sdc] Error in SDC on dependency validation in ONAP R1

Thanks Viswa. We're on it -- Sent from my Android Device From: Kumar Skand Priya, Viswanath V Sent: Thursday, January 11, 2018 3:37:25 PM To: Avi Gaffa Cc: Thiruveedula, Bharath Subject: Re: [E] RE: [onap-discuss] [sdc] Error in SDC on dependency validation in

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

Thank you, Mazin. I have updated the Committer Promotion form on wiki with details and also including information here: APPC has always had a very small number of committers: 4 before recent step down of one committer (3 from AT, 1 from Intel) The Committer that stepped down was from AT the

Re: [onap-discuss] [E] [oom] OOM Installation Problem | Unable to bring up Portal Pod

Hi Michael and Team, Good day ! @Michael - Thanks for your inputs. Yes, no problem with the Installation right now. Onap is up and running.I highly appreciate for pro actively helping others to solve the problems. Thanks a lot for your help. Best Regards, Karthik. On 12 Jan 2018 00:22,

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

Hello Randa +1 for your proposal Regards Jamil Le 12 janv. 2018 à 00:58, MAHER, RANDA > a écrit : Dear TSC, Please consider request below for Committer Promotion for APPC project. https://wiki.onap.org/pages/viewpage.action?pageId=22251669 One of our