[Openstack] Floating IP association using Heat
Tim Schuh
tschuh at vazata.com
Mon Jun 12 12:41:51 UTC 2017
Start with basics since you didn't mention those specifically.
Is the connection actively refused or does it time out?
Does the instance reply to ICMP in both cases?
Service listening on the target instance?
-----Original Message-----
From: D. Davide Lamanna [mailto:davide.lamanna at binarioetico.it]
Sent: Monday, June 12, 2017 5:53 AM
To: openstack at lists.openstack.org
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 : openstack at lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
More information about the Openstack
mailing list