Nice, thanks for including the community - I was planning on forwarding - your message was in my queue. We currently deploy on kubernetes via OOM, details are below. If you are looking for HEAT (VM) deployment - this method is deprecated and only used for testing.
See details and scripts on the official OOM RTD's pages https://onap.readthedocs.io/en/latest/submodules/oom.git/docs/oom_quickstart_guide.html There are several (4) scripts to get your kubernetes system up either via fully automated scripts below or via embedded scripts in RTD above. https://wiki.onap.org/display/DW/Cloud+Native+Deployment https://git.onap.org/logging-analytics/tree/deploy https://git.onap.org/integration/tree/deployment/Azure_ARM_Template https://git.onap.org/integration/tree/deployment/heat/onap-oom For resource requirements - there are several pages like a cost structure one for AWS - it needs updating https://wiki.onap.org/display/DW/ONAP+Deployment+Specification+for+Finance+and+Operations#ONAPDeploymentSpecificationforFinanceandOperations-HardwareProfile - essentially you will need 96-128G of ram distributed among 3-9 VMs to handle the 172+ containers - ideally with a minimum total of 16 vCores (you will peak at 55 on startup), a 1+ Gbps pipe to get all the docker images, an NFS share that handles >5Gb and 80-100G HD (peaks at 4Gbps) per VM in your cluster. I would keep the master VM separate from the cluster VMs where your pods will run - helm is installed only on the master. Helm was just upgraded https://lists.onap.org/g/onap-discuss/topic/oom_integration_helm/24628483?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,20,24628483 For VNFs - I only have experience with the vFW which runs less than an extra 16g - specific to openstack (these are still VM/Heat orchestrated and are not containerized yet like the ONAP system itself) Community will add to this discussion. Thank you /michael From: Shubhra Garg <[email protected]> Sent: Tuesday, August 21, 2018 8:31 AM To: Michael O'Brien <[email protected]>; [email protected] Subject: Re: Complete details required - OANP to VNF via openstack + ONAP discuss. ________________________________ From: Shubhra Garg Sent: Tuesday, August 21, 2018 4:40 PM To: [email protected]<mailto:[email protected]> Subject: Re: Complete details required - OANP to VNF via openstack Gentle reminder! Could you please share the right links for the onap integration with VNF , using kubernetes? Note : i might not get the recommendations as I have opted out of ONAP mails. Best Regards, Shubhra ________________________________ From: Shubhra Garg Sent: Thursday, August 16, 2018 6:38 PM To: [email protected]<mailto:[email protected]> Subject: Complete details required - OANP to VNF via openstack Hi Michael, [ Need details from Scratch]: It's my humble request to please guide for the complete thing. This mail is regarding ONAP integration with openstack and VNF. I am looking for the right set of links for the integration. On one of the machine - ONAP sits. On other machine - openstack sits. Openstack we have installed via kubernetes. On the same/other machine - VNF sits. Now, I need those clear links/videos, which will lead to the integration of ONAP with openstack and NVF. Note : The reason why I have mentioned the above setup is : When I was watching onap videos, I noticed that in openstack, ONAP modules are created as VM's. This creates confusion for us. We are following the above mentioned approach. Also, how much total memory is required for the complete integration and lifecycle mgmt. of ONAP with VNF ? Request you to please guide for the same! Best Regards, Shubhra 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> -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11987): https://lists.onap.org/g/onap-discuss/message/11987 Mute This Topic: https://lists.onap.org/mt/24913671/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
