You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2015/12/15 16:05:46 UTC
[jira] [Commented] (AMBARI-14366) Script to generate bleprint
configuration json from configuration files provided
[ https://issues.apache.org/jira/browse/AMBARI-14366?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058177#comment-15058177 ]
Hudson commented on AMBARI-14366:
---------------------------------
FAILURE: Integrated in Ambari-trunk-Commit #4041 (See [https://builds.apache.org/job/Ambari-trunk-Commit/4041/])
AMBARI-14366. Create a script to allow config merge during Ambari (aonishuk: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=54d2326cac4f11808b246bbf626ac2354b180a36])
* ambari-server/src/main/resources/scripts/takeover_config_merge.py
> Script to generate bleprint configuration json from configuration files provided
> --------------------------------------------------------------------------------
>
> Key: AMBARI-14366
> URL: https://issues.apache.org/jira/browse/AMBARI-14366
> Project: Ambari
> Issue Type: Bug
> Reporter: Andrew Onischuk
> Assignee: Andrew Onischuk
> Fix For: 2.2.1
>
> Attachments: AMBARI-14366.patch
>
>
> _Background_:
> * The scope of this task is to provide a script that reads a dir structure for all configs. **For now only site.xml** since env files cannot be parsed, we might need to handle yaml files in later version.
> * It produces a output of all the problems / conflicts found along with a configuration.json which can be directly incorporated in a cluster **blueprint**
> _Tasks_:
> * Please find the attached patch with a partial script that you can start from (Really basic foundation patch).
> * Assume that user has copied all the configs in a directory, example:
> /tmp/my-master-configs/etc/hadoop/conf,
> /tmp/my-master-configs/etc/hbase/conf,
> /etc/my-slave-configs/hadoop/conf and so on. (There could be 5 core-site from
> different master / slave / client)
> * Parse these files and merge them into a map of configs that can be exported to json based on following rules:
> * If propertyA is found in core-site1 and core-site2 with same value, add it to the map
> * If propertyA is found in core-site1 only, add it to the map
> * If propertyA is found in core-site1 and core-site2 with different value, add it to an output file with same name as the config-type, as a conflict.
> Sample file (Choose appropriate formatting of choice) ::
>
> core-site-conflicts.txt ::
> || Conflicts ||
> | propertyA | <path-to-config-file> | value |
> | propertyA | <path-to-config-file> | value |
>
> * **Note**: Single run should generate all the conflicts, if no conflicts found generate the json file
> * Provide ability to force output and also a verbose mode to log every step
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)