Uploaded image for project: 'Apache Whirr (retired)'
  1. Apache Whirr (retired)
  2. WHIRR-604

Non-resolvable hostnames should be reset to something resolvable

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 0.7.1
    • Fix Version/s: 0.8.0
    • Component/s: core
    • Labels:
      None

      Description

      So we currently have a hack in core/src/main/resources/functions/configure_hostnames.sh to reset the instance hostname on Rackspace to a-b-c-d.static.cloud-ips.com, since the hostname on the instance that Rackspace uses either isn't resolvable at all or isn't resolvable externally (not 100% sure which is the case there - I think they're just not resolvable). This logic should be generalized, since there are other providers where this is the case, and it's also an issue with, say, something like a private Cloudstack install.

      What seems to make sense is to add a property - something like whirr.ip-hostname-domain - and to add a check if we can actually resolve the instance's hostname from anywhere but that particular instance (since the very fact of it being in /etc/hostname means it'll be resolvable locally). If not, set the hostname to a-b-c-d.${whirr.ip-hostname-domain}, with logic in Java somewhere to have a mapping of known provider->ip hostname domains for cases like Rackspace, so that whirr.ip-hostname-domain doesn't need to be set explicitly in those cases.

        Attachments

        1. WHIRR-604.patch
          10 kB
          Andrew Bayer
        2. WHIRR-604.patch
          10 kB
          Andrew Bayer
        3. WHIRR-604.patch
          10 kB
          Andrew Bayer
        4. WHIRR-604.patch
          10 kB
          Andrew Bayer
        5. WHIRR-604.patch
          10 kB
          Andrew Bayer
        6. WHIRR-604.patch
          18 kB
          Andrew Bayer

          Activity

            People

            • Assignee:
              abayer Andrew Bayer
              Reporter:
              abayer Andrew Bayer
            • Votes:
              2 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: