[ 
https://issues.apache.org/jira/browse/AMBARI-7201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14135920#comment-14135920
 ] 

Newton Alex commented on AMBARI-7201:
-------------------------------------

[~rlevas]  Here is what I had in mind while proposing the second set of 
versions.

Imagine a scenario, where we release the service definitions for HDFS/2.4.1 and 
may be HDP and PHD inherit from it.
At a later point of time we identify a bug in the HDFS service definition and 
we amend it.  HDP might decide to skip the newer version but PHD might want to 
adopt the fix.
If we don't have the version numbers for the service definitions itself, how 
would we identify the two different service definitions for HDFS/2.4.1 
available now? I don't think retro-fixing any bugs on a already published 
version will be a good idea as it might break dependent stacks.

Let me know if this sounds reasonable. Thanks

> Common Services
> ---------------
>
>                 Key: AMBARI-7201
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7201
>             Project: Ambari
>          Issue Type: Epic
>          Components: stacks
>    Affects Versions: 2.0.0
>            Reporter: Robert Levas
>              Labels: common-services, service, stack
>             Fix For: 2.0.0
>
>         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
(v6.3.4#6332)

Reply via email to