[ 
https://issues.apache.org/jira/browse/AMBARI-7166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122790#comment-14122790
 ] 

Hudson commented on AMBARI-7166:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #145 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/145/])
AMBARI-7166 Support changing the cluster name of an existing cluster (Frontend 
part). (atkach) (atkach: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=8477d45d818726ee8a9b80c55266a25d5168bc07)
* ambari-admin/src/main/resources/ui/admin-web/app/views/leftNavbar.html
* ambari-admin/src/main/resources/ui/admin-web/app/styles/main.css
* ambari-web/app/messages.js
* 
ambari-admin/src/main/resources/ui/admin-web/app/scripts/controllers/NavbarCtrl.js
* ambari-admin/src/main/resources/ui/admin-web/app/scripts/services/Cluster.js


> Support changing the cluster name of an existing cluster (Frontend part)
> ------------------------------------------------------------------------
>
>                 Key: AMBARI-7166
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7166
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-admin, ambari-web
>    Affects Versions: 1.7.0
>            Reporter: Andrii Tkach
>            Assignee: Andrii Tkach
>             Fix For: 1.7.0
>
>
> 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).



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

Reply via email to