You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Mahadev konar (JIRA)" <ji...@apache.org> on 2015/05/18 08:23:00 UTC

[jira] [Updated] (AMBARI-7562) Provide ability to change hostname with Ambari

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

Mahadev konar updated AMBARI-7562:
----------------------------------
    Assignee:     (was: Alejandro Fernandez)

> Provide ability to change hostname with Ambari
> ----------------------------------------------
>
>                 Key: AMBARI-7562
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7562
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-server
>    Affects Versions: 1.6.1
>            Reporter: Alejandro Fernandez
>
> There are several issues associated with hosts.
> - Uniquely identify a host. MAC address, IP are not sufficient. Perhaps store a file so that even if the hostname changes on the same physical machine, the rename can be auto-detected.
> - Ability to rename: requires using FK from an primary ID that is not the hostname, will require DB schema changes. When a host is readded, need to consider what happens if the OS or environment changes.
> - Properly delete a host (determine if we do hard-deletes that cascade across all of the log records, or soft-deletes so that the hosts persist but not in the cluster)
> Expose ability (capability, steps and/or utility) to change hostnames in Ambari, to avoid users having to:
> a) remove hosts and re-add, or
> b) having to dump the database and adjust directly
> Note: any utility cannot expect a SQL client. It needs to assume there is no database client available to the user.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)