...
- public_net_id: PUT YOUR NETWORK ID/NAME HERE
- ubuntu_1404_image: PUT THE UBUNTU 14.04 IMAGE NAME HERE
- ubuntu_1604_image: PUT THE UBUNTU 16.04 IMAGE NAME HERE
- flavor_small: PUT THE SMALL FLAVOR NAME HERE
- flavor_medium: PUT THE MEDIUM FLAVOR NAME HERE
- flavor_large: PUT THE LARGE FLAVOR NAME HERE
- flavor_xlarge: PUT THE XLARGE FLAVOR NAME HERE
- pub_key: PUT YOUR PUBLIC KEY HERE
- openstack_tenant_id: PUT YOUR OPENSTACK PROJECT ID HERE
- openstack_username: PUT YOUR OPENSTACK USERNAME HERE
- openstack_api_key: PUT YOUR OPENSTACK PASSWORD HERE
- horizon_url: PUT THE HORIZON URL HERE
- keystone_url: PUT THE KEYSTONE URL HERE
- externaldns_dnslist: PUT THE ADDRESS OF THE EXTERNAL DNS HERE (e.g. a comma-separated list of IP addresses in your /etc/resolv.conf in UNIX-based Operating Systems)
- external_dns: PUT THE FIRST ADDRESS OF THE EXTERNAL DNS LIST HERE
- aai_float_ip: PUT A&AI FLOATING IP HERE
- appc_float_ip: PUT APP-C FLOATING IP HERE
- dcae_float_ip: PUT DCAE FLOATING IP HERE
- dcae_coll_float_ip: PUT DCAE COLLECTOR FLOATING IP HERE
- dcae_db_float_ip: PUT DCAE DATABASE FLOATING IP HERE
- dcae_hdp1_float_ip: PUT DCAE HADOOP VM1 FLOATING IP HERE
- dcae_hdp2_float_ip: PUT DCAE HADOOP VM2 FLOATING IP HERE
- dcae_hdp3_float_ip: PUT DCAE HADOOP VM3 FLOATING IP HERE
- dns_float_ip: PUT DNS FLOATING IP HERE
- mso_float_ip: PUT MSO FLOATING IP HERE
- mr_float_ip: PUT MESSAGE ROUTER FLOATING IP HERE
- policy_float_ip: PUT POLICY FLOATING IP HERE
- portal_float_ip: PUT PORTAL FLOATING IP HERE
- robot_float_ip: PUT ROBOT FLOATING IP HERE
- sdc_float_ip: PUT SDC FLOATING IP HERE
- sdnc_float_ip: PUT SDN-C FLOATING IP HERE
- vid_float_ip: PUT VID FLOATING IP HERE
...
Be careful not to use private address space 172.18.0.0/16 for the setup of vanilla opernstack and/or the provider network and the floating addresses therein.
Some containers create a route in the hosting VM form 172.18.0.0./16 to a br-<some-hex-string> bridge which means these containers cannot connect to any other VM and/or container in the 172.18.0.0/16 space. DCAE might be the most prominent victim for that. See also 3246457 in https://wiki.onap.org/questions
Note:
Neutron may require that the dns_nameservers property of a OS::Neutron::Subnet resource be explicitly set, in order to allow VMs in the subnet to access the external network. dns_nameservers is a list of DNS IP addresses. However, some OpenStack installations do not support lists is the "user_data" section of a Heat template, which is used to build configuration files that are used during ONAP installation. As such, we define two different parameters: 1) dns_list is a list of DNS IP addresses that is provided to Neutron; 2) external_dns is a string that contains one of the DNS IP addresses in the list and can be used in the "user_data" section. In many cases, when only one DNS address is provided, these two parameters will be set to the same value.
...
All the other parameters in the environment file are set and can be left untouched.
...
- dcae_base_environment: LEFT FOR FUTURE DCAE RELEASES
- dcae_zone, dcae_state: The location in which DCAE is deployed
- openstack_region: The OpenStack Region in which DCAE is deployed (also used by MSO)
openstack_region must reflect the OpenStack OS_REGION_NAME environment variable (please refer to Tutorial: Configuring and Starting Up the Base ONAP Stack for cloud environment variables), while dcae_zone and dcae_state can contain any meaningful location information that helps the user distinguish between different DCAE deployments. For example, if an instance of DCAE is deployed in a data center in New York City, the two parameters can assume the following values:
...