ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sumit Mohanty (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-9363) role_command_order.json should not be at stack level
Date Fri, 06 Nov 2015 20:53:11 GMT

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

Sumit Mohanty updated AMBARI-9363:
----------------------------------
    Fix Version/s: 2.2.0

> role_command_order.json should not be at stack level
> ----------------------------------------------------
>
>                 Key: AMBARI-9363
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9363
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-server
>    Affects Versions: 1.7.0, trunk
>            Reporter: Mahesh Kumar Vasanthu Somashekar
>            Assignee: Tim Thorpe
>              Labels: feature_custom_service
>             Fix For: 2.2.0
>
>         Attachments: AMBARI-9363.patch
>
>
> In current stack definitions, role_command_order.json is at the stack level.
> For example: HDP/2.2/role_command_order.json
> Service definitions are all nicely separated into different directories, like HDP/2.2/services/{HDFS|YARN},
but not the role_command_order. It would be neater to separate role_command_order per service
and would be very useful while adding a new service to Ambari.
> Looking for something as below,
> - HDP/2.2/services/HDFS/role_command_order.json
> - HDP/2.2/services/YARN/role_command_order.json
> Ambari server while starting should merge all role_command_order.json and create dependencies
accordingly.
> This is extremely useful for custom services which are potentially added after the cluster
install.



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

Mime
View raw message