...
- onap_openstack.yaml / onap_openstack.env: ONAP VMs created out of this template have one vNIC. The vNIC has a private IP towards the Private Management Network and a floating IP. The floating IPs addresses are assigned during ONAP installation by OpenStack, based on floating IP availability. This template can be used when users do not know the set of floating IPs assigned to them. Note that this template should be used in OpenStack Kilo and older releases, because those releases do not support fixed floating IP association via Heat template. CURRENTLY, THIS TEMPLATE DOES NOT SUPPORT DCAE DATA COLLECTION AND ANALYTICS PLATFORM INSTALLATION.
- onap_openstack_float.yaml / onap_openstack_float.env: ONAP VMs created out of this template have one vNIC. The vNIC has a private IP towards the Private Management Network and a floating IP. The floating IPs addresses are specified ahead of time in the environment file. This template can be used when users always want to assign the same floating IP to an ONAP VM in different ONAP installation. Note that fixed floating IP assignment via Heat template is not supported in OpenStack Kilo and older releases. THIS TEMPLATE SUPPORTS DCAE DATA COLLECTION AND ANALYTICS PLATFORM INSTALLATION. In order to correctly install the Data Collection and Analytics Platform, at this time, the DCAE controller requires manual allocation of five (5) Floating IP addresses to your OpenStack project. To allocate those addresses, from the OpenStack horizon dashboard, click on Compute -> Access & Security -> Floating IPs. Then click “Allocate IP To Project” five times. OpenStack will assign five IPs to you. Then, please assign these the allocated Floating IPs to the following VMs defined in the Heat environment file:
dcae_coll_float_ip
dcae_hdp1_float_ip
dcae_hdp2_float_ip
dcae_hdp3_float_ip
dcae_db_float_ip
...