You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "vitthal (Suhas) Gogate (JIRA)" <ji...@apache.org> on 2014/09/03 02:37:51 UTC

[jira] [Commented] (AMBARI-7124) Normalize stack directory structure to support multiple vendor stacks

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

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

Here are some of the high level similarities and differences between different vendor stacks. Objective is to have these stacks supported in Ambari, without duplicating any stack services package scripts across different vendor stacks. Also the existing capability of extending the newer versions of services from previous versions of services, if the service interface (in the context of Ambari) has not changed significantly across the versions.

1. Each vendor stack is made up of bunch of apache hadoop ecosystem services, plus may have some proprietary services of its own. 
2. Typically code base of open source service packaged in vendor's distribution is based on some released version of that service under open source project

So at a high level, 

-- If we pull out "services" as a high level directory same level as "stacks" and leave vendor specific information under "stacks" directory. 
-- The "services" directory should contain released versions of services in open source, corresponding Ambari "package" scripts etc. Services versions should be able to extend from previous versions of the same service (like stacks do today)
-- Individual vendor stack should be composed using appropriate versions of the services defined in the "services" directory. 
-- Vendor Stack should have ability to override as well as extend any services they use from "services" directory e.g. service configurations, package scripts etc.

Based on the preliminary analysis, looks like there may not be much change to existing stacks directory structure, but may be we have to have extra "services" directory structure along side of "stacks" 


> Normalize stack directory structure to support multiple vendor stacks
> ---------------------------------------------------------------------
>
>                 Key: AMBARI-7124
>                 URL: https://issues.apache.org/jira/browse/AMBARI-7124
>             Project: Ambari
>          Issue Type: Improvement
>          Components: stacks
>    Affects Versions: 1.6.1
>            Reporter: vitthal (Suhas) Gogate
>             Fix For: 1.8.0
>
>
> At present, on Ambari-server under "/var/lib/ambari-server/resources/stacks", we have HDP stack definition. Under HDP we have various versions of HDP stack and for each version, we have bunch of services, repos etc that are required for that version. 
> When multiple vendor's stack need be defined, we may have to modify this directory structure so that we can efficiently reuse the code available under various services/package and not to be duplicated for each vendor stack. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)