Re: [onap-discuss] [E] [OOM] Heads up: ONAP Kubernetes master has crossed the 64G VM barrier

2018-03-12 Thread Kumar Skand Priya, Viswanath V via onap-discuss
these > periodically and compare this. Ideally we run ram profiles as part of our > CI/CD pipeline in the future. > > > >Thank you > >/michael > > > > *From:* Kumar Skand Priya, Viswanath V [mailto:viswanath. > kumarskandpr...@verizon.com] > *Sent:* Sat

Re: [onap-discuss] [E] [OOM] Heads up: ONAP Kubernetes master has crossed the 64G VM barrier

2018-03-11 Thread Michael O'Brien
/michael From: Kumar Skand Priya, Viswanath V [mailto:viswanath.kumarskandpr...@verizon.com] Sent: Saturday, March 10, 2018 09:01 To: Michael O'Brien <frank.obr...@amdocs.com> Cc: onap-discuss@lists.onap.org Subject: Re: [E] [onap-discuss] [OOM] Heads up: ONAP Kubernetes master has crossed the

Re: [onap-discuss] [E] [OOM] Heads up: ONAP Kubernetes master has crossed the 64G VM barrier

2018-03-10 Thread Kumar Skand Priya, Viswanath V via onap-discuss
Hi Michael, Does this includes the memory occupied due to deployed VNF & NS as well? If so, what are the requirements for running just the ONAP ( for both R1) ? And more particularly, what's eating more space compared to R2 & R1 ( assuming both are plan ONAP installation i.e without DCAE & VNFs)