[jira] [Resolved] (JCLOUDS-1079) Floating IPs should be public in openstack-nova provider

["Ignasi Barrera (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/JCLOUDS-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ignasi Barrera resolved JCLOUDS-1079.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.0.0

> Floating IPs should be public in openstack-nova provider
> --------------------------------------------------------
>
>                 Key: JCLOUDS-1079
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-1079
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 2.0.0
>            Reporter: Josef Cacek
>              Labels: openstack-nova
>             Fix For: 2.0.0
>
>
> Floating IPs from private address blocks are not presented as public address of a NodeMetadata after refreshing it. (They are only configured as public addresses when creating a new Node).
> * The OpenStack can use private address block for floating IPs.
> * When creating new Node, it adds the floating address to NodeMetadata publicAddresses set (IMO correctly) - in {{AllocateAndAddFloatingIpToNode}} class.
> * when user refreshes the NodeMetadata by calling {{computeService.getNodeMetadata(id)}}, the floating address is added to private addresses (in {{ServerInRegionToNodeMetadata}} class). 
> Possible solution:
> The address returned from Openstack can also have a type:
> {code}
> {
> ...
> "addresses": {"qe-jenkins": [{"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:bf:82:43", "version": 4, "addr": "172.16.130.24", "OS-EXT-IPS:type": "fixed"}, {"OS-EXT-IPS-MAC:mac_addr": "fa:16:3e:bf:82:43", "version": 4, "addr": "10.8.54.75", "OS-EXT-IPS:type": "floating"}]}
> ...
> }
> {code}
> If the type present, then the {{ServerInRegionToNodeMetadata}} should use the type. Otherwise, fallback to the current behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)