Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Thu, 21 Aug 2014 16:21:11 +0000 (UTC)
From: "Yusaku Sako (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12735820.1408637951673.2287.1408638071600@arcas>
In-Reply-To: <JIRA.12735820.1408637951673@arcas>
References: <JIRA.12735820.1408637951673@arcas>
Subject: [jira] [Updated] (AMBARI-6977) Support changing the name of an
 existing cluster via API
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Yusaku Sako updated AMBARI-6977:
--------------------------------

    Summary: Support changing the name of an existing cluster via API  (was: Support changing the name of an existing cluster)

> Support changing the name of an existing cluster via API
> --------------------------------------------------------
>
>                 Key: AMBARI-6977
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6977
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 1.7.0
>            Reporter: Shivani Gupta
>             Fix For: 1.7.0
>
>
> 1) During cluster install (either via Blueprints or Wizard), user specifies the "cluster name".
> 2) This becomes the cluster name ID, used in the Ambari Web UI and in the API to uniquely identify the cluster.
> Provide ability to change the cluster name ID. By changing that cluster name ID, the API calls for that cluster will change too (for example, changing the name from ClusterX to Cluster Y means /api/v1/clusters/ClusterX will then become /api/v1/clusters/ClusterY).
> Expose this rename operation via Ambari API; this should not require direct SQL against the Ambari database


--
This message was sent by Atlassian JIRA
(v6.2#6252)