Jonathan Hurley created AMBARI-24965:
----------------------------------------
Summary: Expose Upgrade Custom Server Actions via an Ambari Client
Library
Key: AMBARI-24965
URL: https://issues.apache.org/jira/browse/AMBARI-24965
Project: Ambari
Issue Type: Task
Components: ambari-server-spi
Affects Versions: 2.8.0
Reporter: Jonathan Hurley
Assignee: Jonathan Hurley
Fix For: 2.8.0
During a stack upgrade, it is possible for upgrade packs to specify custom Java
classes which will run in order to alter configurations or perform other tasks
on the cluster. The following is an example of this type of action:
{code}
<task xsi:type="server_action"
class="org.apache.ambari.server.serveraction.upgrades.RangerKmsProxyConfig">
<summary>Adding Ranger proxy user properties under kms-site</summary>
</task>
{code}
Historically, these tasks have typically been used to alter configurations of
the cluster using more complex logic than the XML markup in an upgrade pack
could provide.
With stacks and mpacks being moved out of Apache source control, Ambari needs a
way for 3rd party developers to provide these actions with the delivery of
their stack.
- The Ambari API/SPI created as part of AMBARI-24685 will need to include
classes which provide retrieval and modification of configurations in addition
to contracts for the server-side action
- Ambari will need to scan for matching classes and register them during the
upgrade
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)