[
https://issues.apache.org/jira/browse/AMBARI-22725?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Hurley updated AMBARI-22725:
-------------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Expose Conditional Elements For Tasks on Upgrade
> ------------------------------------------------
>
> Key: AMBARI-22725
> URL: https://issues.apache.org/jira/browse/AMBARI-22725
> Project: Ambari
> Issue Type: Task
> Affects Versions: 2.6.2
> Reporter: Jonathan Hurley
> Assignee: Jonathan Hurley
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.6.2
>
> Attachments: AMBARI-22725.patch
>
> Time Spent: 40m
> Remaining Estimate: 0h
>
> Some upgrade tasks, such as configuration tasks, need to leverage the
> conditional elements which change the flow of control if the cluster is
> Kerberized (or based on other configuration values). For example, today we
> have this:
> {code:java}
> <execute-stage service="RANGER_KMS" component="RANGER_KMS_SERVER"
> title="Calculating Proxy Properties under kms-site">
> <condition xsi:type="security" type="kerberos"/>
> <task xsi:type="server_action"
> class="org.apache.ambari.server.serveraction.upgrades.RangerKmsProxyConfig"/>
> </execute-stage>{code}
>
> Where {{condition}} elements can be added to an {{execute-stage}} or a
> {{group}}. However, since {{execute-stage}} may only contain one task, it
> makes doing this work on a per-task level impossible. This particularly
> impacts the {{processing}} element. We want something like this:
> {code:java}
> <task xsi:type="configure" id="hdp_2_6_hadoop_rpc_protection">
> <condition xsi:type="security" type="kerberos"/>
> </task>
> {code}
>
> So that {{task}} elements defined in the {{pre-upgrade}} section of
> {{processing}} can also be conditionally invoked.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
