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

Robert Levas commented on AMBARI-7201:
--------------------------------------

[~nalex],

Sorry for the delay on this... after discussing a bit with [~jspeidel], it 
seems like the 2 levels of version numbers may be overkill.  I was trying to 
come up with a use case for multiple versions of a service declaration for a 
particular service version and failed to do so.  Could you help with that.  For 
example, why would we have 

{quote}
common-services/HDFS/2.4.1/versions/1.0
common-services/HDFS/2.4.1/versions/1.1
common-services/HDFS/2.6/versions/1.0
{quote}

Maybe we only really need to worry about one version of each

{quote}
common-services/HDFS/2.4.1
common-services/HDFS/2.6
{quote}

My inclination is to be the most flexible, but maybe I was trying to be too 
flexible.  Thoughts?


> 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