ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Levas (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-7201) Common Services
Date Tue, 09 Sep 2014 14:16:30 GMT

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

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

[~nalex], Thanks!

bq. 1) What would be the common service definitions tested against? Are we looking at Bigtop
rpms?

I am not too sure.  I was hoping the community will join together and ensure that we have
a good place for that.

bq. 2) Minor fix:

I appreciate the fix for my documentation issue. I will correct it and upload a new PDF. 

bq. 3) I have some comments on the versioning of the service definitions. We are dealing with
two variables here:

I really like your ideas on versioning... thanks for pointing out the lack of details on this
in the specification.  You obviously put a lot of thought into this and I think that both
schemas are great.  My need to be explicit favors flavor II... even if it is a bit wordy.
 I will add one of these conventions to the document, but I want to see if anyone chimes in
against or for either of those scenarios.  




> 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
>         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