Team, ONAP Beijing is currently crossing the 64G boundary as of a couple weeks ago. If you run the system on a 128G VM then heaps will expand past 64G within 24 hours. If you stay on 64G (which you can) - reduce the optional pods or you will be getting OOME's Use the ongoing POC JIRA as a guide - we need a full set of deploytime/runtime dependency trees to be able to know what to shutdown. https://jira.onap.org/browse/OOM-511
The recommended VM size (1 or a cluster) is now 80 to 128G - for Beijing (without the upcoming DCAE port) For Amsterdam the OOM side still fits in a 64G vm (you can shutdown vCPE/vVOLTE required pods like vfc) - heatbridge works there to DCAE which bring you up to 150G when the full heat side is up. https://wiki.onap.org/display/DW/ONAP+on+Kubernetes#ONAPonKubernetes-HardwareRequirements ONAP startup now reaches a peak of 60 cores so the more vCores you have the less CPU bound you will be. Thank you /michael This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
