ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Sposetti (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-7562) Provide ability to change hostname with Ambari
Date Fri, 27 Feb 2015 00:17:04 GMT

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

Jeff Sposetti updated AMBARI-7562:
----------------------------------
    Description: 
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.


  was:
Provide steps to change hostnames via API, to avoid users having to:
a) remove hosts and re-add, or
b) having to dump the database and adjust directly


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

Mime
View raw message