[AMBARI-14854] Ambari Management Packs

• Type: Epic
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.4.0
• Component/s: ambari-server
• Epic Name: Ambari Management Packs
• Assignee: Jayush Luniya
• Reporter: Siddharth Wagle
• Created: 01/Feb/16 02:48
• Updated: 20/Oct/16 18:35
• Resolved: 08/Jun/16 16:57

Description

Motivation:
Completely Decouple Ambari's cluster management and monitoring functions from stack management and definition. This is true to some extent however the objective of this Jira is to identify and address all issues that do not allow Ambari core to live without a stack definition and thereby define the scope of work as : "Allow stack definition to be a deploy time artifact vs compile time".
In this regard following is short-term goals that can be achieved for the next minor release version.

Goals:

• Allow ambari to be shipped without a default stack definition
• On server setup:
  • Make sure ambari gets a stack definition from the FS or a URL
  • Support basic checksum validation on the downloaded stack
• Make sure Ambari start after setup-management-pack operation results in graceful failure for in-compatible stack definition downloaded. Example: Deployed stack version is not present in the downloaded management pack.
• Support updates to the pack (to be scoped out)

Assumptions:

• The stack definition is a copy/download and replace (with backup), we do not support fine-grained service merge / replace
• New definition is all inclusive stack def of all service versions supported with current deployed version of Ambari
• The stack can have newer versions of services.

Issue Links

• is related to: AMBARI-17465 Management packs should be able to install extensions
• is related to: AMBARI-17357 Add wiki on management packs
• relates to: AMBARI-12885 Dynamic stack extensions - install and upgrade support for custom services