You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@jclouds.apache.org by "Ashley Taylor (JIRA)" <ji...@apache.org> on 2014/04/09 04:52:15 UTC

[jira] [Updated] (JCLOUDS-528) Ability to exclude public ips

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

Ashley Taylor updated JCLOUDS-528:
----------------------------------

    Issue Type: Improvement  (was: Bug)

> Ability to exclude public ips
> -----------------------------
>
>                 Key: JCLOUDS-528
>                 URL: https://issues.apache.org/jira/browse/JCLOUDS-528
>             Project: jclouds
>          Issue Type: Improvement
>          Components: jclouds-compute
>            Reporter: Ashley Taylor
>
> When working with the rackspace cloud after the vm has started the rackspace network configuring tools 'Rack Connect' reconfigures the machine to lock down the public ip and allow internal access on its private ip only.
> This happens in parallel with the jclouds ConcurrentOpenSocket which would select the public ip as the ip address to configure against before the rackconnect process runs.
> The patch makes the ConcurrentOpenSocket only try connect on the private ip address causing it to block until that interface is available.



--
This message was sent by Atlassian JIRA
(v6.2#6252)