ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "vitthal (Suhas) Gogate (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7201) Common Services
Date Mon, 15 Sep 2014 16:54:33 GMT

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

vitthal (Suhas) Gogate commented on AMBARI-7201:
------------------------------------------------

[~mahadev] [~nalex]  I believe currently we can not inherit the stack from other vendor's
stack and in a sense this is fundamentally wrong model. So I would assume Bigtop stack considered
as sibling to HDP and PHD stack and then PHD inheriting from the Bigtop could be a problem.
 We may have to make some awkward changes to Ambari inheritance logic, if we want to follow
this model until we migrate to common services model. We may need a separate Jira to make
this work until we have common services model. 

[~nalex] lets chat if PHD can (or should) wait for common services model to be delivered in
Ambari or go with cross vendor stack inheritance model. (This discussion can be carried on
to a separate Jira as it may not be relevant here). 

> 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