AMBARI-6935

[Scott Creeley <sc...@redhat.com>]

Hi Andrew,

Regarding the JIRA in the subject line, when we install 2.1.GlusterFS stack (no HDP/HDFS) from latest 1.7.0 Trunk, the GUI now pops up an alert and requires HDFS be selected, even though we are not using it.

The only difference I could find was in the stack_service.js - older version has this which still allows GLUSTERFS to function

App.StackService.dependency = {
  'HDP-1': {
    'MAPREDUCE': ['PIG', 'OOZIE', 'HIVE'],
    'ZOOKEEPER': ['HBASE', 'HIVE', 'WEBHCAT']
  },
  'HDP-2': {
    'YARN': ['PIG', 'OOZIE', 'HIVE', 'TEZ'],
    'TEZ': ['YARN'],
    'OOZIE': ['FALCON'],
    'ZOOKEEPER': ['HDFS', 'HBASE', 'HIVE', 'WEBHCAT', 'STORM']
  }
};


and latest trunk has this which causes the installer to not get past step4 because of the dependency on HDFS:

App.StackService.dependency = {
  'HDP-1': {
    'HDFS': ['MAPREDUCE', 'HBASE', 'SQOOP'],
    'MAPREDUCE': ['PIG', 'OOZIE', 'HIVE'],
    'ZOOKEEPER': ['HBASE', 'HIVE', 'WEBHCAT']
  },
  'HDP-2': {
    'ZOOKEEPER': ['HDFS', 'HBASE', 'HIVE', 'WEBHCAT', 'STORM'],
    'HDFS': ['YARN', 'HBASE', 'FLUME', 'SQOOP'],
    'YARN': ['PIG', 'OOZIE', 'HIVE', 'TEZ'],
    'TEZ': ['YARN'],
    'OOZIE': ['FALCON']
  }
};

If I remove the 'HDFS':...  references then the issue goes away on my tests but don't want to back out what you already did.  Did you also test with 2.1.GlusterFS or is there a plan to also handle non HDFS file systems?  Do we need to further delineate the dependency categories (HDP-1, HDP-2, GLUSTER-2, etc...)?

thanks and let me know what I can do to help resolve this,

Scott