-
Bug
-
Resolution: Done
-
Medium
-
Beijing Release
-
None
-
None
Documented config needs to be updated to current reality
https://onap.readthedocs.io/en/latest/guides/onap-developer/settingup/fullonap.html#requirements
http://10.12.25.2/auth/login/?next=/project/instances/
see discussion on
https://jira.onap.org/browse/OPENLABS-161
For the DCAE side - I am trying to figure out if we need all the DCAE vms and the cloudify-manager (64G) vm that orchestrates the 7 cdap nodes (themselves 7 x 16g = 112g)
I checked Integration-SB-01 and compared to readthedocs (looks to need an update)
https://onap.readthedocs.io/en/latest/guides/onap-developer/settingup/fullonap.html#requirements
The cns (consul) nodes for example are two sizes larger now at 16G each instead of the documented 4G - I remember mails in the past about memory saturation that caused the bump to m1.xlarge from m1.medium (although consul is already in oom so we should not need these)
on top of what is above
DCAE GEN 2 Stack ( 14 VMs ): 42 vCPUs, 84 GB RAM, and 840 GB HDD
- mentioned in
-
Page Loading...