[
https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Thorpe updated AMBARI-12885:
--------------------------------
Description:
The purpose of this proposal is to facilitate adding custom services to an
existing stack. Ideally this would support adding and upgrading custom
services separately from the core services defined in the stack. In particular
we are looking at custom services that need to support several different stacks
(different distributions of Ambari). The release cycle of the custom services
may be different from that of the core stack; that is, a custom service may be
upgraded at a different rate than the core distribution itself and may be
upgraded multiple times within the lifespan of a single release of the core
distribution.
One possible approach to handling this would be dynamically extending a stack
(after install time). It would be best to extend the stack in packages where a
stack extension package can have one or more custom services.
was:
It would be useful to support having multiple stacks. This would allow the
base stack to support all the standard components like HDFS, YARN, HBASE,
etc... but allow third parties to introduce their own components on top of the
base stack.
This would allow third parties to introduce their own components without
needing to modify the base stack of the ambari release they are using.
Summary: Dynamic stack extensions - install and upgrade support for
custom services (was: Support for multiple stacks)
> Dynamic stack extensions - install and upgrade support for custom services
> --------------------------------------------------------------------------
>
> Key: AMBARI-12885
> URL: https://issues.apache.org/jira/browse/AMBARI-12885
> Project: Ambari
> Issue Type: New Feature
> Components: ambari-agent, ambari-server, ambari-web
> Reporter: Tim Thorpe
>
> The purpose of this proposal is to facilitate adding custom services to an
> existing stack. Ideally this would support adding and upgrading custom
> services separately from the core services defined in the stack. In
> particular we are looking at custom services that need to support several
> different stacks (different distributions of Ambari). The release cycle of
> the custom services may be different from that of the core stack; that is, a
> custom service may be upgraded at a different rate than the core distribution
> itself and may be upgraded multiple times within the lifespan of a single
> release of the core distribution.
> One possible approach to handling this would be dynamically extending a stack
> (after install time). It would be best to extend the stack in packages where
> a stack extension package can have one or more custom services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
