DCAE does not accept HEAT environment private IP addresses

It seems as if I can successfully spin up DCAE controller which in turn spins up 5 additional VMs. These five additional VMs do not get the private IP addresses as I defined in the HEAT template

dcae_ip_addr: 10.0.4.1
dcae_db_ip_addr: 10.0.4.101
dcae_coll_ip_addr: 10.0.4.102
dcae_hdp1_ip_addr: 10.0.4.103
dcae_hdp2_ip_addr: 10.0.4.104
dcae_hdp3_ip_addr: 10.0.4.105

down to /opt/config on dcae controller

/opt/config/dcae_ip_addr.txt:10.0.4.1
/opt/config/dcae_db_ip_addr.txt:10.0.4.101
/opt/config/dcae_coll_ip_addr.txt:10.0.4.102
/opt/config/dcae_hdp1_ip_addr.txt:10.0.4.103
/opt/config/dcae_hdp2_ip_addr.txt:10.0.4.104
/opt/config/dcae_hdp3_ip_addr.txt:10.0.4.105

or in /opt/app/dcae-controller/config.yaml

dcae_ip_addr: 10.0.4.1
dcae_pstg00_ip_addr: 10.0.4.101
dcae_coll00_ip_addr: 10.0.4.102
dcae_cdap00_ip_addr: 10.0.4.103
dcae_cdap01_ip_addr: 10.0.4.104
dcae_cdap02_ip_addr: 10.0.4.105

where I lost the track of the private IP addresses.

the public ones seem to be mentioned in configuration files like for example /opt/app/dcae-controller-platform-server/config/instances/vm-docker-host-1/ZONE.yaml

I can see IP addresses assigned from Openstack, randomly from a pool

Logging the network traffic to the Openstack controller, the behavior makes sense: Port is created and afterwards used in a server creation:

POST /v2.0/ports HTTP/1.1.
Content-type: application/json.
X-Auth-Token: gAAAAABZVhy1stqCrJ1ZRF9I1abCAqNKfHCNS97mRAYSefnux_5p_dLgj2lx79eaBkJIhXkDl2v4kT_zWOzBJMCR2Twt3G1Ff3GsT9K5RIreQO-TsS49Kv-W2OfdN6Sp-c9IfBB5n-R2O94F
X-Auth-Project-Id: a90952b7994341f4951fb5e97f829d0d.
Host: controller:9696.
Content-Length: 91.

{"port":{"name":"zldcZONESTATEcoll00","network_id":"f14a5061-9aa7-4b31-9ccb-6355a7f6ca51"}}

T 172.16.3.31:9696 -> 10.0.4.1:41941 [AP]
HTTP/1.1 201 Created.
Content-Type: application/json.
Content-Length: 859.
X-Openstack-Request-Id: req-8d617784-7323-4e58-9676-8cf12eee8410.
Date: Fri, 30 Jun 2017 09:42:33 GMT.

{"port": {"status": "DOWN", "binding:host_id": "", "description": "", "allowed_address_pairs": [], "tags": [], "extra_dhcp_opts": [], "updated_at": "2017-06-30T09:42:33Z", "device_owner": "", "revision_number": 5, "binding:profile": {}, "port_security_enabled": true, "fixed_ips": [{"subnet_id": "42878f4a-963e-447b-b185-4d489e807c2e", "ip_address": "10.0.0.5"}], "id": "250b1740-bdf2-44ad-aa2d-008c7ff37034", "security_groups": ["c8506922-c317-4b3b-96ea-232bf6f7a354"], "device_id": "", "name": "zldcZONESTATEcoll00", "admin_state_up": true, "network_id": "f14a5061-9aa7-4b31-9ccb-6355a7f6ca51", "tenant_id": "a90952b7994341f4951fb5e97f829d0d", "binding:vif_details": {}, "binding:vnic_type": "normal", "binding:vif_type": "unbound", "mac_address": "fa:16:3e:bd:bd:07", "project_id": "a90952b7994341f4951fb5e97f829d0d", "created_at": "2017-06-30T09:42:33Z"}}

T 10.0.4.1:41761 -> 172.16.3.31:8774 [AP]
POST /v2.1/servers HTTP/1.1.
Content-type: application/json.
X-Auth-Token: <token here> 
X-Auth-Project-Id: <etc...etc...etc>
Host: controller:8774.
Content-Length: 33842


{"server":{"name":"zldcZONESTATEcoll00","imageRef":"dd34f6e2-6783-4a42-9723-de7341311ec7","key_name":"onap_key_zxsH_dcae","flavorRef":"3f4a562f-5ae1-44ef-aa3d-15e47b7e539d","max_count":1,"min_count":1,"networks":[{"port":"250b1740-bdf2-44ad-aa2d-008c7ff37034"}],"config_drive":true,"user_data":"incredible-long-string"}}

You see the requests to create the port with ID

250b1740-bdf2-44ad-aa2d-008c7ff37034, but no IP address is assigned.

Any hints from you guys?

DCAE does not accept HEAT environment private IP addresses

1 answer