ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Newton Alex (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7201) Common Services
Date Sat, 13 Sep 2014 00:52:33 GMT

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

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

Had a chat with [~mahadev], [~jspeidel] and a few others today  regarding the common-services
and Bigtop stack service definitions.
Here is what we agreed upon:

"For Ambari 1.7, we can have the Bigtop stack checked in (AMBARI-7292) as a sibling to HDP
stack. PHD stack will inherit the stack definitions from BT stack.
Once the common services infrastructure is available in Ambari-2.0, we can move the service
definitions from BT stack into the common-services (AMBARI-7293) and all other stacks HDP,
BT and PHD can inherit from the common-services.

Please let us know if you see any problem with this approach. 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)

Mime
View raw message