ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Denissov (JIRA)" <>
Subject [jira] [Commented] (AMBARI-12885) Dynamic stack extensions - install and upgrade support for custom services
Date Tue, 23 Feb 2016 00:15:18 GMT


Alexander Denissov commented on AMBARI-12885:

[~mithmatt] and I reviewed this proposal for dynamic stack extensions. If and when implemented,
this will enable addition of custom services into an existing stack as an extension in a generic
and flexible way. However, until this is done, we have a need to let Ambari know about a new
repository for the service added to the default stack definition, hence the proposal in AMABRI-13216.

For the proposal here, I would suggest to evaluate whether the same approach will work for
all common services. IMO, common-services should be a dictionary of all services that can
be added to the cluster, independent of any stacks. If each service describes its dependencies
the way it is described here, then there might be no "standard services" vs. "extensions"
distinctions and "stack" becomes just a list of common services that a given vendor ships.
Perhaps, this will be a separate epic, but the ideas illustrated here fit that scenario well.

> Dynamic stack extensions - install and upgrade support for custom services
> --------------------------------------------------------------------------
>                 Key: AMBARI-12885
>                 URL:
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-agent, ambari-server, ambari-web
>            Reporter: Tim Thorpe
>            Assignee: Tim Thorpe
>         Attachments: Dynamic Stack Extensions - High Level Design v4.pdf
> 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

View raw message