[AMBARI-22196] Refactor non-stack cluster-env configs to cluster settings

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.5.2
• Fix Version/s: trunk, 3.0.0
• Component/s: ambari-server
• Epic Link: Config Management in Multi Everything Architecture
• Assignee: Swapan Shridhar
• Reporter: Swapan Shridhar
• Due: 11/Oct/17
• Created: 10/Oct/17 22:36
• Updated: 14/Dec/17 13:05
• Resolved: 22/Oct/17 10:52

Description

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.

    <property>
      <name>security_enabled</name>
      <value>false</value>
      <description>Hadoop Security</description>
      <on-ambari-upgrade add="true"/>
    </property>
  

• 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.

Issue Links

• blocks: AMBARI-22197 Remove cluster-env from ambari
• links to: Review request
• links to: Reviewboard