Getting the port ID from the heat server addresses attribute is not discoverable
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
Medium
|
Sergey Kraynev | ||
openstack-manuals |
Fix Released
|
Undecided
|
Sergey Kraynev |
Bug Description
The following is possible but basically nobody knows about it as it is not well documented:
server:
type: OS::Nova::Server
properties:
image: {get_param: image}
flavor: {get_param: flavor}
key_name: {get_param: key_name}
security_
- {get_resource: the_sg}
networks:
- network: {get_param: private_network}
server_
type: OS::Neutron:
properties:
floatingi
port_id: {get_attr: [server, addresses, {get_param: private_network}, 0, port]}
floating_ip:
type: OS::Neutron:
properties:
floating_
Specifically, it is possible to create a floating IP association without creating an explicit port resource (avoiding all the problems that causes with stack updates)
This situation could be improved by:
- demonstrating the above example the hot-guide as the recommended way to associate a server port with a floating IP
- improving the server addresses attribute reference to make it obvious that you can do the following:
{get_attr: [server, addresses, {get_param: private_network}, 0, port]}
Changed in heat: | |
status: | New → Triaged |
Changed in openstack-manuals: | |
assignee: | nobody → Sergey Kraynev (skraynev) |
Changed in heat: | |
assignee: | nobody → Sergey Kraynev (skraynev) |
Changed in heat: | |
milestone: | none → kilo-2 |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | kilo-2 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/147849
Review: https:/