You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2015/08/17 18:46:45 UTC

[jira] [Updated] (AMBARI-9363) role_command_order.json should not be at stack level

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

Alejandro Fernandez updated AMBARI-9363:
----------------------------------------
    Labels: feature_custom_service  (was: )

> 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
>            Reporter: Mahesh Kumar Vasanthu Somashekar
>              Labels: feature_custom_service
>
> 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 message was sent by Atlassian JIRA
(v6.3.4#6332)