Details

    • Type: Task Task
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Lets create an "HCFS" component for ambari JIRAs... ! ((( Ping Erin A Boyd is this what your thought is ? This was originally your idea, thanks for mentioning it ! )))

      Now that Ambari is HCFS Compliant (i.e. see https://forge.gluster.org/hadoop/pages/ConfiguringAmbari2), it would be great if we were able to document and file bugs specific to HCFS related support .. for example:

      • if there was a bug associated with installing a file system plugin
      • if an HCFS ambari module breaks or causes ambari deployment to fail
      • if an HCFS is somehow not compliant with HDFS specific semantics in how ambari sets up the file system... see BIGTOP-1200 / BIGTOP-952 as an how management tools "should" (or at least "could") be doing HCFS provisioning

      So, lets create an HCFS component where we can track any file system plugin and setup related issues.

        Activity

        Hide
        Vijay Srinivasaraghavan added a comment -

        Martin Bukatovic Tracking issues using "hcfs" label certainly helps but my broader concern is that the current Ambari framework is not designed to support any HCFS (in-place of HDFS) as an alternate file system. The framework assumes HDFS as core component that should exist in the first place. I believe there was an effort attempted earlier to support generic HCFS but later reverted back to support only GlusterFS. I am trying to understand the painpoints on why the generic design was aborted.

        Show
        Vijay Srinivasaraghavan added a comment - Martin Bukatovic Tracking issues using "hcfs" label certainly helps but my broader concern is that the current Ambari framework is not designed to support any HCFS (in-place of HDFS) as an alternate file system. The framework assumes HDFS as core component that should exist in the first place. I believe there was an effort attempted earlier to support generic HCFS but later reverted back to support only GlusterFS. I am trying to understand the painpoints on why the generic design was aborted.
        Hide
        Martin Bukatovic added a comment -

        Vijay Srinivasaraghavan You are right, hcfs JIRAs may be related to various components, eg. AMBARI-8658 is clearly a stack related, while there are issues related to multiple components as well: eg. AMBARI-8468. On the other hand, there are issues without component (eg. AMBARI-8505) as it's not immediatelly clear which is the right one (from the reporter perspective).

        And since I needed some easy way to track hcfs related issues, I created hcfs label some time ago. What do you think about this approach? The downside is that me and Daniel Horak are the only ones currently using it so far.

        Show
        Martin Bukatovic added a comment - Vijay Srinivasaraghavan You are right, hcfs JIRAs may be related to various components, eg. AMBARI-8658 is clearly a stack related, while there are issues related to multiple components as well: eg. AMBARI-8468 . On the other hand, there are issues without component (eg. AMBARI-8505 ) as it's not immediatelly clear which is the right one (from the reporter perspective). And since I needed some easy way to track hcfs related issues, I created hcfs label some time ago. What do you think about this approach? The downside is that me and Daniel Horak are the only ones currently using it so far.
        Hide
        Vijay Srinivasaraghavan added a comment -

        It appears at some point in time there was a generic HCFS integration that got ported back to GlusterFS specific one (AMBARI-3167, AMBARI-2721). Do we know why this got moved (sorry JIRA comments are not really helpful)

        It looks like the GlusterFS integration is not just handled only at the stack level (inheritence model) but also touches many core components (ambari-server, ambari-web, ambari-client modules etc.,). It appears there is no clean way of extending the framework to add new services (HCFS).

        If we need to introduce new HCFS support to Ambari, should we need to follow same approach as adopted for GlusterFS (extending stack and also modifying core Ambari components - read hardcoded) or is there a generic way of introducing new HCFS stack support.

        I am planning to post my findings and propose new JIRA task but wanted to find if there is something on the radar already.

        Show
        Vijay Srinivasaraghavan added a comment - It appears at some point in time there was a generic HCFS integration that got ported back to GlusterFS specific one ( AMBARI-3167 , AMBARI-2721 ). Do we know why this got moved (sorry JIRA comments are not really helpful) It looks like the GlusterFS integration is not just handled only at the stack level (inheritence model) but also touches many core components (ambari-server, ambari-web, ambari-client modules etc.,). It appears there is no clean way of extending the framework to add new services (HCFS). If we need to introduce new HCFS support to Ambari, should we need to follow same approach as adopted for GlusterFS (extending stack and also modifying core Ambari components - read hardcoded) or is there a generic way of introducing new HCFS stack support. I am planning to post my findings and propose new JIRA task but wanted to find if there is something on the radar already.

          People

          • Assignee:
            Unassigned
            Reporter:
            jay vyas
          • Votes:
            1 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:

              Development