On 12/06/2017 14:41, Tim Schuh wrote: > Start with basics since you didn't mention those specifically. Ok. Thank you.
heat_template_version: 2015-04-30 > > Is the connection actively refused or does it time out? It's a "Connection refused" > Does the instance reply to ICMP in both cases? ICMP is disabled in both cases. nmap in the not-working case: 554/tcp open rtsp 7070/tcp open realserver > Service listening on the target instance? 22/tcp open ssh 25/tcp closed smtp 80/tcp open http 443/tcp open https 554/tcp open rtsp 7070/tcp open realserver 8080/tcp closed http-proxy In the meantime I have an update. I deleted and launched the stack a bunch of times. Since the machine must have a fixed local IP plus a fixed floating IP (both of them must be fixed), I tried to dismiss the local IP address static definition (leaving it to DHCP) and the FIP association worked fine! So I thought of possible syncronization problems, i.e. what is done before or after? Then I tried to put the local fixed IP address back in the template and it worked, in a unpredictable way. So I'm afraid I can't say my issue is solved until I'm 100% sure the template always works. Can this be a task sequence issue? What is the rule for the order of tasks within Heat? (The "association" is the last task written in the YAML file, anyway). Sorry for basic questions. Cheers, Dave > > -----Original Message----- > From: D. Davide Lamanna [mailto:[email protected]] > Sent: Monday, June 12, 2017 5:53 AM > To: [email protected] > Subject: [Openstack] Floating IP association using Heat > > > Hi all, > > I'm using "association" resource in a heat template, like that: > > association: > type: OS::Nova::FloatingIPAssociation > properties: > floating_ip: { get_param: foo_floating_ip } > server_id: { get_resource: bar_instance } > > With: > > bar_instance: > type: OS::Nova::Server > properties: > key_name: { get_param: key_name } > image: { get_param: image_id } > flavor: { get_param: instance_type } > networks: > - port: { get_resource: bar_instance_port } > > foo_floating_ip: > type: string > label: Foo Floating IP > description: Floating IP to be associated to the Foo Instance > default: fd06c9c0-dcf7-4881-9bae-aafc1b8a8cf7 > > Where: > > fd06c9c0-dcf7-4881-9bae-aafc1b8a8cf7 > > is the ID of the Floating IP I want to associate to my instance. > > > > The stack gets created fine. The dashboard says that the association of the > floating IP is exactly what I planned, i.e. the instance gets the Floating IP > I wanted. But ssh connection gets refused! > > Then, if I deassociate by hand the floating IP associated by Heat and > reassociate by hand the same Floating IP, everything works fine. So it seems > like Heat associates the Floating IP, but it is not actually possible to > connect to it. Whereas it works if you do it by hand afterwards. > > > Any clue? > > > Cheers, > Dave > > > _______________________________________________ > Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack > Post to : [email protected] > Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack -- Ing. D. Davide Lamanna - CEO mobile: 340 4830930 voip: 06 916504256 fax: 06 233225276 Via Salaria, 292 - 00199 Roma www.binarioetico.it _______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : [email protected] Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
