1
0
-1
1 answer
- 10-1
I can see your config.yaml is not correct. And thus your heat.env most not be correct. please show
config.yaml (remove passwords.)
Add your comment...
I can see your config.yaml is not correct. And thus your heat.env most not be correct. please show
config.yaml (remove passwords.)
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
down to /opt/config on dcae controller
or in /opt/app/dcae-controller/config.yaml
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:
You see the requests to create the port with ID
Any hints from you guys?
.. and while describing the issue above, think I got a workaround:
The ports are all created DCAE, but not deleted when I delete the 5 VMs. Previously, I deleted the ports too. I made another attempt and modified the port settings like
and restarted DCAE controller. Now I can see the correct private IP addresses in Opoenstack dashboard.
Nevertheless, it does not work out-of-the-box.