You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Swapan Shridhar (JIRA)" <ji...@apache.org> on 2017/10/22 10:53:00 UTC
[jira] [Resolved] (AMBARI-22196) Refactor non-stack cluster-env
configs to cluster settings
[ https://issues.apache.org/jira/browse/AMBARI-22196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Swapan Shridhar resolved AMBARI-22196.
--------------------------------------
Resolution: Fixed
> Refactor non-stack cluster-env configs to cluster settings
> ----------------------------------------------------------
>
> Key: AMBARI-22196
> URL: https://issues.apache.org/jira/browse/AMBARI-22196
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.2
> Reporter: Swapan Shridhar
> Assignee: Swapan Shridhar
> Priority: Critical
> Fix For: trunk, 3.0.0
>
>
> *Following to be done as part of this JIRA:*
> - Move all non-stack specific configs in *cluster-env.xml* to *cluster-settings.xml*
> - For example {{cluster-env/security_enabled}} is a cluster setting and shouldn't be associated with any stack/mpack.
> {code}
> <property>
> <name>security_enabled</name>
> <value>false</value>
> <description>Hadoop Security</description>
> <on-ambari-upgrade add="true"/>
> </property>
> {code}
> - Add new file as : {{/var/lib/ambari-server/resources/cluster-settings.xml}} which includes all the read only cluster specific settings.
> *New API Endpoint serving the cluster-settings* : api/v1/cluster_settings
> *Followup work :*
> - AMBARI-22197 takes care of removing cluster-env.xml and associated code and API once we have AMBARI-22198 completed.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)