[AMBARI-24965] Expose Upgrade Custom Server Actions via an Ambari Client Library

• Type: Task
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 2.8.0
• Fix Version/s: 2.8.0
• Component/s: ambari-server-spi
• Labels: pull-request-available
• Epic Link: Ambari 2.8 Stack Upgrades
• Assignee: Jonathan Hurley
• Reporter: Jonathan Hurley
• Created: 28/Nov/18 19:11
• Updated: 26/Feb/19 17:52
• Resolved: 29/Nov/18 14:55

Description

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:

<task xsi:type="server_action" class="org.apache.ambari.server.serveraction.upgrades.RangerKmsProxyConfig">
  <summary>Adding Ranger proxy user properties under kms-site</summary>
</task>

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

Issue Links

• links to: GitHub Pull Request #2663