Re: [onap-discuss] ONAP on Kubernetes

itland , "onap-discuss@lists.onap.org" Subject: RE: [onap-discuss] ONAP on Kubernetes Hi, I started with another clean vm, and now OOM is running fine. However, I am interested to know why many pods return to "init" status after one or two days running. Thanks A. Seaudi __

Re: [onap-discuss] ONAP on Kubernetes

3:11 PM To: Michael O'Brien; Roger Maitland; onap-discuss@lists.onap.org Subject: RE: [onap-discuss] ONAP on Kubernetes Hi, I was able to clean my system and close down port 10250, and the cpu issue is now resolved. However, after a day or 2 runnnig OOM, i find many of the pods are now

Re: [onap-discuss] ONAP on Kubernetes

ng on limiting the profile for an individual container – out of the box each container thinks it has the whole VM. thank you /michael From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Roger Maitland Sent: Monday, March 26, 2018 09:55 To:

Re: [onap-discuss] ONAP on kubernetes

We would need more details on your environment. Running Rancher/kubadm Running amsterdam/Beijing Verify helm version Verify kubernetes version Verify kubectl version Verify docker version Verify Ubuntu version Verify the routable IP or hostname entered in /etc/hosts - for rancher registration Veri

Re: [onap-discuss] ONAP on Kubernetes

-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Roger Maitland Sent: Monday, March 26, 2018 09:55 To: abdelmuhaimen.sea...@orange.com; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] ONAP on Kubernetes I suspect you’ve come across two, possibly

Re: [onap-discuss] ONAP on Kubernetes

I suspect you’ve come across two, possibly three, different issues: * Memory leaks within the containers of (potentially) several projects: There already are several Jira bugs open against suspected memory leaks: SDC-1092, DCAEGEN2-198

Re: [onap-discuss] ONAP on Kubernetes OOM 1.1.0 - DCAE support

> > Cc: Roger Maitland <mailto:roger.maitl...@amdocs.com>>; onap-discuss@lists.onap.org > <mailto:onap-discuss@lists.onap.org> > Subject: Re: [onap-discuss] ONAP on Kubernetes OOM 1.1.0 - DCAE support > > Hi, it is still work in progress, but I’d say it’s almost don

Re: [onap-discuss] ONAP on Kubernetes OOM 1.1.0 - DCAE support

Maitland ; onap-discuss@lists.onap.org Subject: Re: [onap-discuss] ONAP on Kubernetes OOM 1.1.0 - DCAE support Hi, it is still work in progress, but I’d say it’s almost done. Intensive testing is currently being performed, so far with success. But I’d like to have 3 complete runs with no hick-up to

Re: [onap-discuss] ONAP on Kubernetes OOM 1.1.0 - DCAE support

14, 2017 10:00 PM > To: Alexis de Talhouët ; Vidhu Shekhar Pandey - ERS, > HCL Tech > Cc: onap-discuss@lists.onap.org > Subject: RE: [onap-discuss] ONAP on Kubernetes OOM 1.1.0 - DCAE support > > Vidhu, please keep in mind that OOM starts the DCAE controller which will > de

Re: [onap-discuss] ONAP on Kubernetes OOM 1.1.0 - DCAE support

- ERS, HCL Tech Cc: onap-discuss@lists.onap.org Subject: RE: [onap-discuss] ONAP on Kubernetes OOM 1.1.0 - DCAE support Vidhu, please keep in mind that OOM starts the DCAE controller which will deploy VMs in the OpenStack domain. As such you’ll need enough capacity in your OpenStack cloud to

Re: [onap-discuss] ONAP on Kubernetes OOM 1.1.0 - DCAE support

-boun...@lists.onap.org] On Behalf Of Alexis de Talhouët Sent: Thursday, December 14, 2017 10:16 AM To: Vidhu Shekhar Pandey - ERS, HCL Tech Cc: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] ONAP on Kubernetes OOM 1.1.0 - DCAE support Hi, DCAEGEN2 support is currently being added to OOM

Re: [onap-discuss] ONAP on Kubernetes OOM 1.1.0 - DCAE support

Hi, DCAEGEN2 support is currently being added to OOM. It’s tracked by JIRA https://jira.onap.org/browse/OOM-508 Implementation has been done, we’re currently testing the implementation to make sure it’s working as expected. You should be able to use it wi

Re: [onap-discuss] ONAP on Kubernetes with Rancher

Hi Roger, Thanks for the reply. Also, I found one more difference in a yaml file, oom/kubernetes/multicloud/templates/framework-deployment.yaml. The line with '_ name: MSB_PORT' is throwing error while deploying containers with parsing error. I guess it should read '- name: MSB_PORT' instead.

Re: [onap-discuss] ONAP on Kubernetes with Rancher

Hi Srini, AAI introduced some configuration changes yesterday (Wednesday) which resulted in the crash loop you are seeing. The problem has already been fixed locally and will be pushed to gerrit today. Thank you from pointing out the problem. The OOM team (the Integration team is in the same s