You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Andrew Bayer (JIRA)" <ji...@apache.org> on 2013/11/25 19:34:38 UTC

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

    [ https://issues.apache.org/jira/browse/JCLOUDS-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13831725#comment-13831725 ] 

Andrew Bayer commented on JCLOUDS-355:
--------------------------------------

Is this going to actually get done in the next two weeks, or should it move to post-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.4
>
>
> 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)