[jira] [Resolved] (AMBARI-22815) Change requiredServices in metainfo.xml

["Dmytro Sen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMBARI-22815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmytro Sen resolved AMBARI-22815.
---------------------------------
    Resolution: Fixed

Committed into branch-feature-AMBARI-14714

> Change requiredServices in metainfo.xml
> ---------------------------------------
>
>                 Key: AMBARI-22815
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22815
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 3.0.0
>            Reporter: Dmytro Sen
>            Assignee: Dmytro Sen
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.0.0
>
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> Today we define requiredServices as follows
> {code}
> <requiredServices>
>     <service>ZOOKEEPER</service>
> </requiredServices>
> {code}
> In the mpack model we need to categorize the scope of service dependency. We could have an INSTALL time dependency (i.e. we should also install the dependent service) or a RUNTIME dependency (i.e. there should be a running instance of the service in the cluster). 
> For example HIVE in EDW mpack, will have an install-time dependency on ZOOKEEPER-CLIENT but a RUNTIME dependency on ZOOKEEPER.
> {code}
> <requiredServices>
>   <service>
>       <name>ZOOKEEPER-CLIENT</name>
>       <scope>INSTALL</scope>
>    </service>
>   <service>
>       <name>ZOOKEEPER</name>
>       <scope>RUNTIME</scope>
>    </service>
> </requiredServices>
> {code}
> We should also check how we maintain compatibility with legacy stack definitions.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)