Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I am converting some of our comment conversation into an answer.

You can see information about individual resources in your stack through the resource-list and resource-show commands. To see information about the floating ip created in your stack, you would run:

heat resource-show <stack_name> lb_floating

Which, per your information, shows that the floating ip address was created:

+------------------------+-----------------------------------------...+
| Property               | Value                                   ...|
+------------------------+-----------------------------------------...+
| description            |                                         ...|
| links                  | http://controller:8004/v1/ad948ee0c33749...|
|                        | http://controller:8004/v1/ad948ee0c33749...|
| logical_resource_id    | lb_floating                             ...|
| physical_resource_id   | a3fd80f3-ec10-48fa-9d70-1c9f72bd0dcd    ...|
[...]

Using the neutron floating-ip-list command, you can see with which fixed address this address is associated.

When you assign a floating ip address to a pool, all that does is map the floating ip to the fixed ip of the pool. It does not assign floating ips to instances that are members of the pool. Ideally, the pool members should not even require floating ip addresses -- all your access to the instances should be through the load balanacer. You can assign floating ips to the instances if you need to access them directly without going through the load balancer, or you could also run a "gateway" host -- this would only require a single additional floating ip, rather than one per instance. You would first log into the gateway host, and from there log in to your instances using their fixed address.