You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@jclouds.apache.org by "Everett Toews (JIRA)" <ji...@apache.org> on 2013/10/24 05:11:41 UTC

[jira] [Updated] (JCLOUDS-355) ServerInZoneToNodeMetadata should use accessIPv4

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

Everett Toews updated JCLOUDS-355:
----------------------------------

    Fix Version/s: 1.6.3
                   1.7.0

> ServerInZoneToNodeMetadata should use accessIPv4
> ------------------------------------------------
>
>                 Key: JCLOUDS-355
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-355
>             Project: jclouds
>          Issue Type: Bug
>          Components: jclouds-compute
>    Affects Versions: 1.6.2
>            Reporter: Everett Toews
>            Assignee: Everett Toews
>              Labels: openstack, rackspace
>             Fix For: 1.7.0, 1.6.3
>
>
> In OpenStack you can use the accessIPv4 field of a Server as the public address of the Server. This doesn't get accounted for in ServerInZoneToNodeMetadata when the public addresses are being added. The accessIPv4 should be added to publicAddresses. 



--
This message was sent by Atlassian JIRA
(v6.1#6144)