Re: [onap-discuss] A service naming in OOM

Hi James and CT, “aai-aai” actually refers to the HA Proxy service. Microservices/components that need to contact the A APIs do so via the HA proxy service which is why you will see references to “aai-aai” in the Helm charts. Hope that helps, Susan On May 16, 2018, at 3:48 AM, C.T. Paterson

[onap-discuss] [ONAP Helpdesk #56152] [linuxfoundation.org #56152] RE: [so] mso:1.2.1 image missing

Hi Gary This is strange why things go missing, I triggered a new build and I can see the Docker back https://nexus3.onap.org/#browse/search=keyword%3Dmso:7f6379d32f8dd78fd8e42923c8ff348e:88bfafa960bab52124a30fecfc044940 [cid:image001.png@01D3EEBC.1BCABC50]

Re: [onap-discuss] [so] mso:1.2.1 image missing

Hi Gary This is strange why things go missing, I triggered a new build and I can see the Docker back https://nexus3.onap.org/#browse/search=keyword%3Dmso:7f6379d32f8dd78fd8e42923c8ff348e:88bfafa960bab52124a30fecfc044940 [cid:image001.png@01D3EEBC.1BCABC50]

Re: [onap-discuss] [onap-tsc] [Onap-usecasesub] The summary of Usecase subcommittee meeting 14/05/2017 - Casablanca use cases/functional requirements endorsement

Hi Dan, Thanks for the clarification. I checked the SDN-R documents on the wiki page … According to the SDN-R subproject proposal (drafted Nov. 2017) the following features are in scope for R2: · Enhancements to support the ONAP release 2 use cases, e.g., RAN deployment, Slicing, SON

Re: [onap-discuss] [so] mso:1.2.1 image missing

Hi Seshu, Thanks for taking care of this. I hope LF can figure out why these docker images keep disappearing. Thanks, Gary From: Seshu m Sent: Friday, May 18, 2018 12:23 AM To: Gary Wu ; helpd...@onap.org; onap-discuss@lists.onap.org Subject: RE: [so] mso:1.2.1 image

[onap-discuss] [ONAP Helpdesk #56152] [linuxfoundation.org #56152] RE: [so] mso:1.2.1 image missing

Hi Seshu, Thanks for taking care of this. I hope LF can figure out why these docker images keep disappearing. Thanks, Gary From: Seshu m Sent: Friday, May 18, 2018 12:23 AM To: Gary Wu ; helpd...@onap.org; onap-discuss@lists.onap.org Subject: RE: [so] mso:1.2.1 image

[onap-discuss] Canceled event: Arch Subcommittee (updated Feb 12, 2018) @ Tue May 22, 2018 7am - 9am (PDT) (onap-discuss@lists.onap.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:CANCEL BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02

Re: [onap-discuss] OOM Beijing CPU utilization

This is a major drawback of Containerization versus Virtualization. How a process could hog platform resources and affect everything else. Wondering if Kubernetes or Docker have a solution for this. Arash From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org]

Re: [onap-discuss] OOM Beijing CPU utilization

FYI Below are what we found out about CPU Management of Logstash. https://discuss.elastic.co/t/cpu-management-of-logstash/99487 Before deploy 'log'(CPU 6%) [centos@server-k8s-cluster-1node-kubernetes-master-host-afxat7 kubernetes]$ kubectl top node NAME

Re: [onap-discuss] OOM Beijing CPU utilization

Hong, Nice link to the parallel threads issue - very timely and useful as we just put in the replicaSet workaround to 3 yesterday to fix an issue running only on one core. Will look more into the logstash config as well - the issue is we baseline at 30 logs/sec on an idle system now -

[onap-discuss] Canceled event: [usecase] Subcommittee (updated Jan. 30, 2018) @ Mon May 21, 2018 7am - 8am (PDT) (onap-discuss@lists.onap.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:CANCEL BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02

Re: [onap-discuss] [app-c] Problem accessing LCM API

Hi Chandrashkhar, It sounds like payload is missing in the request: { "body": { "input": { "common-header": { "timestamp": "2018-05-17T10:03:46.827Z", "api-ver": "2.00", "originator-id": "95dac45d-ba9b-48c5-bb52-805b24ec4319", "request-id":

[onap-discuss] Invitation: [usecase] e2e use cases approvals for Casablanca @ Tue May 22, 2018 7am - 8am (PDT) (onap-discuss@lists.onap.org)

BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VEVENT DTSTART:20180522T14Z DTEND:20180522T15Z DTSTAMP:20180518T141057Z ORGANIZER;CN=ONAP Meetings and Events:mailto:linuxfoundation.org_1rmtb5tpr3

[onap-discuss] [ONAP Helpdesk #54849] Nexus3.onap.org currently serving at least 10x slower at 1MB/sec

Thank you Michael! Let's sync up on this after the weekend. Thanks! Jess On Fri May 18 14:58:32 2018, frank.obr...@amdocs.com wrote: > Jessica, > On my public systems I have not seen any issues - but I have not run > a bmon lately. > I'll do one over the weekend and was also planning on

Re: [onap-discuss] [ONAP Helpdesk #54849] Nexus3.onap.org currently serving at least 10x slower at 1MB/sec

Jessica, On my public systems I have not seen any issues - but I have not run a bmon lately. I'll do one over the weekend and was also planning on adding a Jenkins job Looks good so far. /michael -Original Message- From: Jessica Wagantall via RT

Re: [onap-discuss] [ONAP Helpdesk #54849] Nexus3.onap.org currently serving at least 10x slower at 1MB/sec

Jessica, On my public systems I have not seen any issues - but I have not run a bmon lately. I'll do one over the weekend and was also planning on adding a Jenkins job Looks good so far. /michael -Original Message- From: Jessica Wagantall via RT

Re: [onap-discuss] Fixing invalid YAML in read only git repos

Hi Michael, Aai-config repo is no longer used by AAI Team, and thus the repo has been locked. You can use this link to see status of the repo in Gerrit: https://gerrit.onap.org/r/#/admin/projects/?filter=aai [cid:image001.jpg@01D3EE97.AD1B0D60] Thanks, Gildas ONAP Release Manager 1 415 238

Re: [onap-discuss] [ONAP Helpdesk #55854] RE: [integration] Problem with integration CSIT tests not being able to execute docker-compose

Not lately, maybe you can gleen something from those failed jobs. Pam On 5/18/18, 2:21 PM, "Jessica Wagantall via RT" wrote: Are you guys still seeing docker-compose issues? Please let me know and I can look thanks! Jess

Re: [onap-discuss] [ONAP Helpdesk #55854] RE: [integration] Problem with integration CSIT tests not being able to execute docker-compose

Not lately, maybe you can gleen something from those failed jobs. Pam On 5/18/18, 2:21 PM, "Jessica Wagantall via RT" wrote: Are you guys still seeing docker-compose issues? Please let me know and I can look thanks! Jess

[onap-discuss] OOF integration testing

Hi Helen, Gildas, Following up on our earlier meeting regarding the integration testing, I wanted to reach out and provide an update on the progress here as you requested. We have completed all the pairwise testing with our downstream dependencies (AAI, MultiCloud, Policy), and expect to

[onap-discuss] [ONAP Helpdesk #55854] RE: [integration] Problem with integration CSIT tests not being able to execute docker-compose

Are you guys still seeing docker-compose issues? Please let me know and I can look thanks! Jess On Fri May 11 14:57:22 2018, pdrag...@research.att.com wrote: > Unfortunately, now the problem has reappeared again: > > 18:51:22 /w/workspace/policy-master-csit- >

[onap-discuss] [ONAP Helpdesk #54849] Nexus3.onap.org currently serving at least 10x slower at 1MB/sec

Hi Michael, I just wanted to check in. How are things going in Nexus3? are you seeing an improvement since the last time we met for this? thanks! Jess On Tue May 01 13:00:45 2018, jwagantall wrote: > Actually, I think this is the latest ticket on this issue, > > I will leave this opened

[onap-discuss] [ONAP Helpdesk #56089] [LF] Gerrit review fails to push on jetty 404 looking for /tools/hooks/commit-msg

Oh, good to know Michael! Just as a small note, git push does not have to push directly into master. You can use "git push origin HEAD:refs/for/master" where "for" will make sure it goes into Gerrit. I am glad you are unblocked though. thanks Jess On Wed May 16 20:00:12 2018,

Re: [onap-discuss] [ONAP Helpdesk #55868] RE: [onap-tsc] [LF] Request new JIRA project - CD - for all continuous delivery/deployment work

Hi, I would like to propose, we postpone the discussion and potential changes after Beijing Release is out of the door. Focusing on getting the ONAP working is the urgency for now. Thanks for your understanding, Gildas ONAP Release Manager 1 415 238 6287 -Original Message- From:

Re: [onap-discuss] [ONAP Helpdesk #55868] RE: [onap-tsc] [LF] Request new JIRA project - CD - for all continuous delivery/deployment work

Hi, I would like to propose, we postpone the discussion and potential changes after Beijing Release is out of the door. Focusing on getting the ONAP working is the urgency for now. Thanks for your understanding, Gildas ONAP Release Manager 1 415 238 6287 -Original Message- From:

Re: [onap-discuss] [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing

This job runs hourly, and checks the image tags in the docker manifest: https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv Thanks, Gary -Original Message- From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] Sent:

Re: [onap-discuss] [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing

This job runs hourly, and checks the image tags in the docker manifest: https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest.csv Thanks, Gary -Original Message- From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] Sent:

Re: [onap-discuss] [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing

Not that I'm aware of, because virtually none of the images in the manifest are release versions yet. Thanks, Gary -Original Message- From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] Sent: Friday, May 18, 2018 4:07 PM To: Gary Wu Cc:

Re: [onap-discuss] [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing

Not that I'm aware of, because virtually none of the images in the manifest are release versions yet. Thanks, Gary -Original Message- From: Jessica Wagantall via RT [mailto:onap-helpd...@rt.linuxfoundation.org] Sent: Friday, May 18, 2018 4:07 PM To: Gary Wu Cc:

[onap-discuss] [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing

I have been investigating all the examples we have. This has to be something coming from Jenkins. So far, I have not seen this issue in the docker.releases repo which is the only repo where we do not use automation to push, but rather on demand pushes. Another separate issue, why are we

[onap-discuss] [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing

Gary, How often is this job triggered? Does it checks all possible "missing" images? Thanks! Jess On Fri May 18 18:31:50 2018, jwagantall wrote: > I have been investigating all the examples we have. > > This has to be something coming from Jenkins. > > So far, I have not seen this issue in

[onap-discuss] [ONAP Helpdesk #56152] [so] mso:1.2.1 image missing

Thanks! Can you confirm something with me please? No occurrences have happened in docker.releases right? This will help me narrow down the cause which could be Jenkins jobs if my assumption is correct. If this also happens in docker.releases then I would suggest an upgrade to the newest