Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Fri, 27 Feb 2015 00:13:04 +0000 (UTC)
From: "Jeff Sposetti (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12763480.1419347571000.29241.1424995984528@Atlassian.JIRA>
In-Reply-To: <JIRA.12763480.1419347571000@Atlassian.JIRA>
References: <JIRA.12763480.1419347571000@Atlassian.JIRA>
 <JIRA.12763480.1419347571451@arcas>
Subject: [jira] [Updated] (AMBARI-8887) Rename host and properly delete
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jeff Sposetti updated AMBARI-8887:
----------------------------------
    Fix Version/s:     (was: 2.0.0)

> Rename host and properly delete
> -------------------------------
>
>                 Key: AMBARI-8887
>                 URL: https://issues.apache.org/jira/browse/AMBARI-8887
>             Project: Ambari
>          Issue Type: Epic
>          Components: ambari-server
>    Affects Versions: 1.6.1
>            Reporter: Alejandro Fernandez
>            Assignee: 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)


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