You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Vijay Srinivasaraghavan (JIRA)" <ji...@apache.org> on 2015/01/06 23:30:34 UTC

[jira] [Commented] (AMBARI-5181) HCFS Component for Ambari JIRAs

    [ https://issues.apache.org/jira/browse/AMBARI-5181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14266888#comment-14266888 ] 

Vijay Srinivasaraghavan commented on AMBARI-5181:
-------------------------------------------------

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.

> HCFS Component for Ambari JIRAs
> -------------------------------
>
>                 Key: AMBARI-5181
>                 URL: https://issues.apache.org/jira/browse/AMBARI-5181
>             Project: Ambari
>          Issue Type: Task
>            Reporter: jay vyas
>   Original Estimate: 0h
>  Remaining Estimate: 0h
>
> Lets create an "HCFS" component for ambari JIRAs... ! ((( Ping [~erinaboyd] 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. 



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