[
https://issues.apache.org/jira/browse/AMBARI-14854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jayush Luniya updated AMBARI-14854:
-----------------------------------
Attachment: (was: ApacheAmbariManagementPacks.pdf)
> Ambari Management Packs
> -----------------------
>
> Key: AMBARI-14854
> URL: https://issues.apache.org/jira/browse/AMBARI-14854
> Project: Ambari
> Issue Type: Epic
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Siddharth Wagle
> Assignee: Jayush Luniya
> Priority: Critical
> Fix For: 2.4.0
>
> Attachments: ApacheAmbariManagementPacks.pdf
>
>
> _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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
