ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mahesh Kumar Vasanthu Somashekar (JIRA)" <>
Subject [jira] [Created] (AMBARI-9363) role_command_order.json should not be at stack level
Date Tue, 27 Jan 2015 23:40:35 GMT
Mahesh Kumar Vasanthu Somashekar created AMBARI-9363:

             Summary: role_command_order.json should not be at stack level
                 Key: AMBARI-9363
             Project: Ambari
          Issue Type: New Feature
          Components: ambari-server
    Affects Versions: 1.7.0
            Reporter: Mahesh Kumar Vasanthu Somashekar

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

This message was sent by Atlassian JIRA

View raw message