To: m.pta...@partner.samsung.com; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] OOM Beijing HW requirements
Michal,
Hi, there is a procedure to increase the 110 limit here
https://lists.onap.org/g/onap-discuss/topic/oom_110_kubernetes_pod/25213556?p=,,,20,0,0,0::recentpostdate
, May 7, 2018 11:38 AM
To: m.pta...@partner.samsung.com; onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] OOM Beijing HW requirements
Hi Michal,
The limit of 110 pods applies per node so if you add another node (or two) to
your cluster you’ll avoid this problem. We’ve had problems
org" <onap-discuss@lists.onap.org>
Subject: [onap-discuss] OOM Beijing HW requirements
Hi all,
I am trying to deploy latest ONAP (Beijing) using OOM (master branch) and I
found some challenges using suggested HW resources for all-in-one (rancher
server + k8s host on sing
Hi all,
I am trying to deploy latest ONAP (Beijing) using OOM (master branch) and I found some challenges using suggested HW resources for all-in-one (rancher server + k8s host on single node) deployment of ONAP:
HW resources:
24 VCPU
128G RAM
500G disc space
rhel7.4 os
Hi all,
I am trying to deploy latest ONAP (Beijing) using OOM (master branch) and I found some challenges using suggested HW resources for all-in-one (rancher server + k8s host on single node) deployment of ONAP:
HW resources:
24 VCPU
128G RAM
500G disc space
rhel7.4 os
Hi all,
I am trying to deploy latest ONAP (Beijing) using OOM (master branch) and I found some challenges using suggested HW resources for all-in-one (rancher server + k8s host on single node) deployment of ONAP:
HW resources:
24 VCPU
128G RAM
500G disc space
rhel7.4 os
