You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whirr.apache.org by "Graham Gear (JIRA)" <ji...@apache.org> on 2012/08/20 12:38:37 UTC

[jira] [Created] (WHIRR-634) Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX

Graham Gear created WHIRR-634:
---------------------------------

             Summary: Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX
                 Key: WHIRR-634
                 URL: https://issues.apache.org/jira/browse/WHIRR-634
             Project: Whirr
          Issue Type: Improvement
          Components: core
    Affects Versions: 0.7.1
            Reporter: Graham Gear
            Priority: Minor



Currently, configure_hostnames.sh ensures that the public IP host file entry is written if required by the AUTO_HOSTNAME_SUFFIX variable. It does not however touch the internal IP host file entry, which is likely to retain an entry for the initial (and generally unresolvable) hostname. It is suggested that configure_hostname.sh also update the private IP host file entry, with a 'private.' prefix to ensure there is no ambiguity in reverse lookups, since the order of the host file entries cannot be relied on (eg the order varies host to host, IP to IP on Rackspace Cloud). This keeps the public/private host file entries in sync and allows them to be used interchangably depending on the visibility requirements of the node.

Eg, on Rackspace cloud, if provisioning a node with a whirr.cluster-name 'cdh-cluster' on Rackspace Cloud UK, the pre configure_hostnames.sh on a particular node looks as so:

-bash-4.1$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.177.7.48 cdh-cluster-74f
31.222.177.80 cdh-cluster-74f

after current trunk configure_hostnames.sh:

-bash-4.1$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.177.7.48 cdh-cluster-74f
31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

and after the suggested updates in this JIRA it would look like:

-bash-4.1$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.177.7.48 private.31-222-177-80.static.cloud-ips.co.uk
31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

--
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

        

[jira] [Commented] (WHIRR-634) Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX

Posted by "Andrew Bayer (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WHIRR-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438726#comment-13438726 ] 

Andrew Bayer commented on WHIRR-634:
------------------------------------

Deferring to this for 0.8.1 - I'm just not 100% sure of this one yet. =)
                
> Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX
> -----------------------------------------------------------------------
>
>                 Key: WHIRR-634
>                 URL: https://issues.apache.org/jira/browse/WHIRR-634
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.7.1
>            Reporter: Graham Gear
>            Assignee: Graham Gear
>            Priority: Minor
>             Fix For: 0.8.0
>
>         Attachments: WHIRR-634.patch
>
>
> Currently, configure_hostnames.sh ensures that the public IP host file entry is written if required by the AUTO_HOSTNAME_SUFFIX variable. It does not however touch the internal IP host file entry, which is likely to retain an entry for the initial (and generally unresolvable) hostname. It is suggested that configure_hostname.sh also update the private IP host file entry, with a 'private.' prefix to ensure there is no ambiguity in reverse lookups, since the order of the host file entries cannot be relied on (eg the order varies host to host, IP to IP on Rackspace Cloud). This keeps the public/private host file entries in sync and allows them to be used interchangably depending on the visibility requirements of the node.
> Eg, on Rackspace cloud, if provisioning a node with a whirr.cluster-name 'cdh-cluster' on Rackspace Cloud UK, the pre configure_hostnames.sh on a particular node looks as so:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 cdh-cluster-74f
> after current trunk configure_hostnames.sh:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk
> and after the suggested updates in this JIRA it would look like:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 private.31-222-177-80.static.cloud-ips.co.uk
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

--
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

        

[jira] [Commented] (WHIRR-634) Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX

Posted by "Andrei Savu (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WHIRR-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438697#comment-13438697 ] 

Andrei Savu commented on WHIRR-634:
-----------------------------------

+1 
                
> Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX
> -----------------------------------------------------------------------
>
>                 Key: WHIRR-634
>                 URL: https://issues.apache.org/jira/browse/WHIRR-634
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.7.1
>            Reporter: Graham Gear
>            Priority: Minor
>         Attachments: WHIRR-634.patch
>
>
> Currently, configure_hostnames.sh ensures that the public IP host file entry is written if required by the AUTO_HOSTNAME_SUFFIX variable. It does not however touch the internal IP host file entry, which is likely to retain an entry for the initial (and generally unresolvable) hostname. It is suggested that configure_hostname.sh also update the private IP host file entry, with a 'private.' prefix to ensure there is no ambiguity in reverse lookups, since the order of the host file entries cannot be relied on (eg the order varies host to host, IP to IP on Rackspace Cloud). This keeps the public/private host file entries in sync and allows them to be used interchangably depending on the visibility requirements of the node.
> Eg, on Rackspace cloud, if provisioning a node with a whirr.cluster-name 'cdh-cluster' on Rackspace Cloud UK, the pre configure_hostnames.sh on a particular node looks as so:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 cdh-cluster-74f
> after current trunk configure_hostnames.sh:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk
> and after the suggested updates in this JIRA it would look like:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 private.31-222-177-80.static.cloud-ips.co.uk
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

--
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

        

[jira] [Commented] (WHIRR-634) Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX

Posted by "Paul Baclace (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/WHIRR-634?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440955#comment-13440955 ] 

Paul Baclace commented on WHIRR-634:
------------------------------------

On HPCloud, it is possible to have only:

127.0.0.1 localhost

in /etc/hosts for ubuntu 12.04 "precise" (generic ipv6 entries are also present).  

That means z should append the entry if the ipaddr is not present at all.  

I tried this on HPCloud, but configure_hostnames.sh does not run.  How do I get it to be applied?


                
> Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX
> -----------------------------------------------------------------------
>
>                 Key: WHIRR-634
>                 URL: https://issues.apache.org/jira/browse/WHIRR-634
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.7.1
>            Reporter: Graham Gear
>            Assignee: Graham Gear
>            Priority: Minor
>             Fix For: 0.8.1, 0.9.0
>
>         Attachments: WHIRR-634.patch, WHIRR-634.patch
>
>
> Currently, configure_hostnames.sh ensures that the public IP host file entry is written if required by the AUTO_HOSTNAME_SUFFIX variable. It does not however touch the internal IP host file entry, which is likely to retain an entry for the initial (and generally unresolvable) hostname. It is suggested that configure_hostname.sh also update the private IP host file entry, with a 'private.' prefix to ensure there is no ambiguity in reverse lookups, since the order of the host file entries cannot be relied on (eg the order varies host to host, IP to IP on Rackspace Cloud). This keeps the public/private host file entries in sync and allows them to be used interchangably depending on the visibility requirements of the node.
> Eg, on Rackspace cloud, if provisioning a node with a whirr.cluster-name 'cdh-cluster' on Rackspace Cloud UK, the pre configure_hostnames.sh on a particular node looks as so:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 cdh-cluster-74f
> after current trunk configure_hostnames.sh:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk
> and after the suggested updates in this JIRA it would look like:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 private.31-222-177-80.static.cloud-ips.co.uk
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

--
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

        

[jira] [Updated] (WHIRR-634) Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX

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

Andrew Bayer updated WHIRR-634:
-------------------------------

    Attachment: WHIRR-634.patch

Slightly tweaked patch - it's possible to have only one IP on the instance, so we should make sure PRIVATE_IP isn't empty.
                
> Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX
> -----------------------------------------------------------------------
>
>                 Key: WHIRR-634
>                 URL: https://issues.apache.org/jira/browse/WHIRR-634
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.7.1
>            Reporter: Graham Gear
>            Assignee: Graham Gear
>            Priority: Minor
>             Fix For: 0.8.0
>
>         Attachments: WHIRR-634.patch, WHIRR-634.patch
>
>
> Currently, configure_hostnames.sh ensures that the public IP host file entry is written if required by the AUTO_HOSTNAME_SUFFIX variable. It does not however touch the internal IP host file entry, which is likely to retain an entry for the initial (and generally unresolvable) hostname. It is suggested that configure_hostname.sh also update the private IP host file entry, with a 'private.' prefix to ensure there is no ambiguity in reverse lookups, since the order of the host file entries cannot be relied on (eg the order varies host to host, IP to IP on Rackspace Cloud). This keeps the public/private host file entries in sync and allows them to be used interchangably depending on the visibility requirements of the node.
> Eg, on Rackspace cloud, if provisioning a node with a whirr.cluster-name 'cdh-cluster' on Rackspace Cloud UK, the pre configure_hostnames.sh on a particular node looks as so:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 cdh-cluster-74f
> after current trunk configure_hostnames.sh:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk
> and after the suggested updates in this JIRA it would look like:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 private.31-222-177-80.static.cloud-ips.co.uk
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

--
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

        

[jira] [Updated] (WHIRR-634) Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX

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

Andrew Bayer updated WHIRR-634:
-------------------------------

    Fix Version/s:     (was: 0.8.0)
                   0.9.0
                   0.8.1
    
> Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX
> -----------------------------------------------------------------------
>
>                 Key: WHIRR-634
>                 URL: https://issues.apache.org/jira/browse/WHIRR-634
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.7.1
>            Reporter: Graham Gear
>            Assignee: Graham Gear
>            Priority: Minor
>             Fix For: 0.8.1, 0.9.0
>
>         Attachments: WHIRR-634.patch, WHIRR-634.patch
>
>
> Currently, configure_hostnames.sh ensures that the public IP host file entry is written if required by the AUTO_HOSTNAME_SUFFIX variable. It does not however touch the internal IP host file entry, which is likely to retain an entry for the initial (and generally unresolvable) hostname. It is suggested that configure_hostname.sh also update the private IP host file entry, with a 'private.' prefix to ensure there is no ambiguity in reverse lookups, since the order of the host file entries cannot be relied on (eg the order varies host to host, IP to IP on Rackspace Cloud). This keeps the public/private host file entries in sync and allows them to be used interchangably depending on the visibility requirements of the node.
> Eg, on Rackspace cloud, if provisioning a node with a whirr.cluster-name 'cdh-cluster' on Rackspace Cloud UK, the pre configure_hostnames.sh on a particular node looks as so:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 cdh-cluster-74f
> after current trunk configure_hostnames.sh:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk
> and after the suggested updates in this JIRA it would look like:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 private.31-222-177-80.static.cloud-ips.co.uk
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

--
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

        

[jira] [Updated] (WHIRR-634) Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX

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

Andrei Savu updated WHIRR-634:
------------------------------

      Description: 
Currently, configure_hostnames.sh ensures that the public IP host file entry is written if required by the AUTO_HOSTNAME_SUFFIX variable. It does not however touch the internal IP host file entry, which is likely to retain an entry for the initial (and generally unresolvable) hostname. It is suggested that configure_hostname.sh also update the private IP host file entry, with a 'private.' prefix to ensure there is no ambiguity in reverse lookups, since the order of the host file entries cannot be relied on (eg the order varies host to host, IP to IP on Rackspace Cloud). This keeps the public/private host file entries in sync and allows them to be used interchangably depending on the visibility requirements of the node.

Eg, on Rackspace cloud, if provisioning a node with a whirr.cluster-name 'cdh-cluster' on Rackspace Cloud UK, the pre configure_hostnames.sh on a particular node looks as so:

-bash-4.1$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.177.7.48 cdh-cluster-74f
31.222.177.80 cdh-cluster-74f

after current trunk configure_hostnames.sh:

-bash-4.1$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.177.7.48 cdh-cluster-74f
31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

and after the suggested updates in this JIRA it would look like:

-bash-4.1$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.177.7.48 private.31-222-177-80.static.cloud-ips.co.uk
31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

  was:

Currently, configure_hostnames.sh ensures that the public IP host file entry is written if required by the AUTO_HOSTNAME_SUFFIX variable. It does not however touch the internal IP host file entry, which is likely to retain an entry for the initial (and generally unresolvable) hostname. It is suggested that configure_hostname.sh also update the private IP host file entry, with a 'private.' prefix to ensure there is no ambiguity in reverse lookups, since the order of the host file entries cannot be relied on (eg the order varies host to host, IP to IP on Rackspace Cloud). This keeps the public/private host file entries in sync and allows them to be used interchangably depending on the visibility requirements of the node.

Eg, on Rackspace cloud, if provisioning a node with a whirr.cluster-name 'cdh-cluster' on Rackspace Cloud UK, the pre configure_hostnames.sh on a particular node looks as so:

-bash-4.1$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.177.7.48 cdh-cluster-74f
31.222.177.80 cdh-cluster-74f

after current trunk configure_hostnames.sh:

-bash-4.1$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.177.7.48 cdh-cluster-74f
31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

and after the suggested updates in this JIRA it would look like:

-bash-4.1$ cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
10.177.7.48 private.31-222-177-80.static.cloud-ips.co.uk
31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

    Fix Version/s: 0.8.0
         Assignee: Graham Gear
    
> Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX
> -----------------------------------------------------------------------
>
>                 Key: WHIRR-634
>                 URL: https://issues.apache.org/jira/browse/WHIRR-634
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.7.1
>            Reporter: Graham Gear
>            Assignee: Graham Gear
>            Priority: Minor
>             Fix For: 0.8.0
>
>         Attachments: WHIRR-634.patch
>
>
> Currently, configure_hostnames.sh ensures that the public IP host file entry is written if required by the AUTO_HOSTNAME_SUFFIX variable. It does not however touch the internal IP host file entry, which is likely to retain an entry for the initial (and generally unresolvable) hostname. It is suggested that configure_hostname.sh also update the private IP host file entry, with a 'private.' prefix to ensure there is no ambiguity in reverse lookups, since the order of the host file entries cannot be relied on (eg the order varies host to host, IP to IP on Rackspace Cloud). This keeps the public/private host file entries in sync and allows them to be used interchangably depending on the visibility requirements of the node.
> Eg, on Rackspace cloud, if provisioning a node with a whirr.cluster-name 'cdh-cluster' on Rackspace Cloud UK, the pre configure_hostnames.sh on a particular node looks as so:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 cdh-cluster-74f
> after current trunk configure_hostnames.sh:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk
> and after the suggested updates in this JIRA it would look like:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 private.31-222-177-80.static.cloud-ips.co.uk
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

--
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

        

[jira] [Updated] (WHIRR-634) Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX

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

Graham Gear updated WHIRR-634:
------------------------------

    Attachment: WHIRR-634.patch

Suggested implementation.
                
> Update private IP host file entry when required by AUTO_HOSTNAME_SUFFIX
> -----------------------------------------------------------------------
>
>                 Key: WHIRR-634
>                 URL: https://issues.apache.org/jira/browse/WHIRR-634
>             Project: Whirr
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 0.7.1
>            Reporter: Graham Gear
>            Priority: Minor
>         Attachments: WHIRR-634.patch
>
>
> Currently, configure_hostnames.sh ensures that the public IP host file entry is written if required by the AUTO_HOSTNAME_SUFFIX variable. It does not however touch the internal IP host file entry, which is likely to retain an entry for the initial (and generally unresolvable) hostname. It is suggested that configure_hostname.sh also update the private IP host file entry, with a 'private.' prefix to ensure there is no ambiguity in reverse lookups, since the order of the host file entries cannot be relied on (eg the order varies host to host, IP to IP on Rackspace Cloud). This keeps the public/private host file entries in sync and allows them to be used interchangably depending on the visibility requirements of the node.
> Eg, on Rackspace cloud, if provisioning a node with a whirr.cluster-name 'cdh-cluster' on Rackspace Cloud UK, the pre configure_hostnames.sh on a particular node looks as so:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 cdh-cluster-74f
> after current trunk configure_hostnames.sh:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 cdh-cluster-74f
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk
> and after the suggested updates in this JIRA it would look like:
> -bash-4.1$ cat /etc/hosts
> 127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
> 10.177.7.48 private.31-222-177-80.static.cloud-ips.co.uk
> 31.222.177.80 31-222-177-80.static.cloud-ips.co.uk

--
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