You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@libcloud.apache.org by "Jay Doane (JIRA)" <ji...@apache.org> on 2012/05/23 00:21:40 UTC

[dev] [jira] [Created] (LIBCLOUD-200) Expose force_ipv4 parameter (default True) in _wait_until_running() method.

Jay Doane created LIBCLOUD-200:
----------------------------------

             Summary: Expose force_ipv4 parameter (default True) in _wait_until_running() method.
                 Key: LIBCLOUD-200
                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-200
             Project: Libcloud
          Issue Type: Bug
          Components: Compute
            Reporter: Jay Doane
            Priority: Minor
         Attachments: wait-until-running-force-ipv4.patch

Rackspace has a private beta OpenStack implementation that is returning both the ipv4 and ipv6 addresses in a node's public_ips list.  The current implementation just grabs the first address out of the list without testing that the current host can actually connect to it.

This patch exposes a force_ipv4 parameter set to True by default, which will preserve the existing behavior when a node also has ipv4 addresses by filtering ipv6 addresses from the list.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[dev] [jira] [Resolved] (LIBCLOUD-200) Expose force_ipv4 parameter (default True) in _wait_until_running() method.

Posted by "Tomaz Muraus (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LIBCLOUD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tomaz Muraus resolved LIBCLOUD-200.
-----------------------------------

    Resolution: Fixed

Merged into master using a less hacky way to determine if an IP is valid IPv4 address. Thanks.
                
> Expose force_ipv4 parameter (default True) in _wait_until_running() method.
> ---------------------------------------------------------------------------
>
>                 Key: LIBCLOUD-200
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-200
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>            Reporter: Jay Doane
>            Priority: Minor
>         Attachments: wait-until-running-force-ipv4.patch
>
>
> Rackspace has a private beta OpenStack implementation that is returning both the ipv4 and ipv6 addresses in a node's public_ips list.  The current implementation just grabs the first address out of the list without testing that the current host can actually connect to it.
> This patch exposes a force_ipv4 parameter set to True by default, which will preserve the existing behavior when a node also has ipv4 addresses by filtering ipv6 addresses from the list.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[dev] [jira] [Updated] (LIBCLOUD-200) Expose force_ipv4 parameter (default True) in _wait_until_running() method.

Posted by "Jay Doane (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LIBCLOUD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Doane updated LIBCLOUD-200:
-------------------------------

    Attachment: wait-until-running-force-ipv4.patch
    
> Expose force_ipv4 parameter (default True) in _wait_until_running() method.
> ---------------------------------------------------------------------------
>
>                 Key: LIBCLOUD-200
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-200
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>            Reporter: Jay Doane
>            Priority: Minor
>         Attachments: wait-until-running-force-ipv4.patch
>
>
> Rackspace has a private beta OpenStack implementation that is returning both the ipv4 and ipv6 addresses in a node's public_ips list.  The current implementation just grabs the first address out of the list without testing that the current host can actually connect to it.
> This patch exposes a force_ipv4 parameter set to True by default, which will preserve the existing behavior when a node also has ipv4 addresses by filtering ipv6 addresses from the list.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[dev] [jira] [Closed] (LIBCLOUD-200) Expose force_ipv4 parameter (default True) in _wait_until_running() method.

Posted by "Jay Doane (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/LIBCLOUD-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jay Doane closed LIBCLOUD-200.
------------------------------

    
> Expose force_ipv4 parameter (default True) in _wait_until_running() method.
> ---------------------------------------------------------------------------
>
>                 Key: LIBCLOUD-200
>                 URL: https://issues.apache.org/jira/browse/LIBCLOUD-200
>             Project: Libcloud
>          Issue Type: Bug
>          Components: Compute
>            Reporter: Jay Doane
>            Priority: Minor
>         Attachments: wait-until-running-force-ipv4.patch
>
>
> Rackspace has a private beta OpenStack implementation that is returning both the ipv4 and ipv6 addresses in a node's public_ips list.  The current implementation just grabs the first address out of the list without testing that the current host can actually connect to it.
> This patch exposes a force_ipv4 parameter set to True by default, which will preserve the existing behavior when a node also has ipv4 addresses by filtering ipv6 addresses from the list.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira