You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/06/27 08:52:00 UTC
[jira] [Updated] (AMBARI-24162) Support for cluster-settings
(remove cluster-env)
[ https://issues.apache.org/jira/browse/AMBARI-24162?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated AMBARI-24162:
------------------------------------
Labels: pull-request-available (was: )
> Support for cluster-settings (remove cluster-env)
> -------------------------------------------------
>
> Key: AMBARI-24162
> URL: https://issues.apache.org/jira/browse/AMBARI-24162
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
> Affects Versions: 3.0.0
> Reporter: Balázs Bence Sári
> Assignee: Balázs Bence Sári
> Priority: Critical
> Labels: pull-request-available
> Fix For: 3.0.0
>
>
> Per the configuration refactoring occuring for Management Pack support, all configuration types will be scoped at the service level, rather than at the cluster level.
> The Blueprint processor will need to be updated, in order to treat all configuration at the service level. The Blueprint processor will need to take the configuration specified in a Blueprint, and convert this (where possible) to a service-level configuration in the internal representation of the configuration.
> The Blueprint processor will need to implement support for "cluster-settings", which replaces the "cluster-env" configuration type.
> We should accept older Blueprints with "cluster-env", and make the necessary conversions on the server side during deployment.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)