[
https://issues.apache.org/jira/browse/AMBARI-12608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-12608:
-----------------------------------
Fix Version/s: (was: 2.1.2)
2.2.0
> Spectrum Scale service should be able to save core-site changes
> ---------------------------------------------------------------
>
> Key: AMBARI-12608
> URL: https://issues.apache.org/jira/browse/AMBARI-12608
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-web
> Affects Versions: 2.1.0
> Reporter: Nathan Falk
> Priority: Minor
> Fix For: 2.2.0
>
>
> With the upcoming release of IBM Open Platform 4.1, which is based on Ambari
> 2.1, it will be possible to add a stack to use Spectrum Scale in place of
> HDFS as the underlying filesystem for hadoop.
> A new service named 'GPFS' is introduced in this stack, and in the absence of
> HDFS, the core-site.xml, hadoop-env.xml and hdfs-site.xml files will be
> provided in services/GPFS/configuration.
> There is code in ambari-web which restricts the services which are permitted
> to save core-site changes. In the file
> ambari-web/app/mixins/common/configs/configs_saver.js, there is a function
> allowSaveSite (line numbers may differ in the current version of the file -
> this is from 2 or 3 weeks ago):
> {code}
> 483 /**
> 484 * for some file names we have a restriction
> 485 * and can't save them, in this this method will return false
> 486 * @param fName
> 487 * @returns {boolean}
> 488 */
> 489 allowSaveSite: function(fName) {
> 490 switch (fName) {
> 491 case 'mapred-queue-acls.xml':
> 492 return false;
> 493 case 'core-site.xml':
> 494 return ['HDFS', 'GLUSTERFS',
> 'RANGER_KMS'].contains(this.get('content.serviceName'));
> 495 default :
> 496 return true;
> 497 }
> 498 },
> {code}
> In order for the 'GPFS' service to save changes to core-site.xml, 'GPFS'
> needs to be added to the list on line 494, or some other mechanism would have
> to be provided to allow 3rd-party stacks to redefine which service owns
> core-site.xml.
> We are currently working around this problem by modifying
> /usr/lib/ambari-server/web/javascripts/app.js.gz directly, but this type of
> approach is inherently error-prone.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
