ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Newton Alex (JIRA)" <>
Subject [jira] [Commented] (AMBARI-7201) Common Services
Date Mon, 08 Sep 2014 23:03:29 GMT


Newton Alex commented on AMBARI-7201:

Sorry about the auto linking. 
Rewording to make it slightly better:

"Consider a scenario where we release the service definitions for HDFS-2.4 and call it common-services/hdfs/1.0.0.
After some time we release the service definition for HDFS-2.5 and call it common-services/hdfs/.
Now if for some reason we need to patch the service definition for the older HDFS-2.4, what
would the version number for such a fix look like? Do we call it common-services/hdfs/,
common-services/hdfs/1.0.1 or common-services/hdfs/1.1.1? "

> Common Services
> ---------------
>                 Key: AMBARI-7201
>                 URL:
>             Project: Ambari
>          Issue Type: Epic
>          Components: stacks
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>              Labels: common-services, service, stack
>         Attachments: CommonStackServicesTechnicalDocument.pdf
>   Original Estimate: 504h
>  Remaining Estimate: 504h
> *Problem*
> The current implementation of the Ambari stack does not allow for a common set of services
to be defined and reused in vendor-specific stack definitions. Therefore in order for the
same service to be made available to different stacks, it’s definition must be copied or
inherited from stack to stack.  
> *Solution*
> There needs to be a repository of services that exist outside the scope of any vendor-specific
stack, but are accessible to vendor-specific stacks via service inheritance. This set of services
should be known as common services and are to be maintained by the community to ensure that
changes do not break vendor-specific services that inherit from them. 
> See [^CommonStackServicesTechnicalDocument.pdf] for more information.

This message was sent by Atlassian JIRA

View raw message