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

Scott Creeley commented on AMBARI-6867:
---------------------------------------

[~jaimin] [~u39kun] [[email protected]] [~erinaboyd]

I began working on this JIRA yesterday and have most of 2.1.GlusterFS stack 
converted from global to env, also working on the 2.0.6.GlusterFS stack as well 
in this process (75% done).  But I'm having a bit of confusion as alot has 
changed over the past month.  Can anyone give me a hint on what I'm missing 
regarding the 2 questions below:

1.  Step 7 of installer - when I click on the GLUSTERFS tab I get duplicate 
variables for every variable that is in my core-site.xml AND in the 
site_properties.js in the General section:
                GlusterFS fs impl      ...blah blah
                GlusterFS fs impl      ...blah blah
                etc... 

2.   I see service_configs.js has changed alot since 1.6.0 implementation and 
I'm wondering how I now add a "Custom core-site" section with the Add 
Property... for "Config" tab in step 7 and post installation.  I tried to 
follow other examples from other services, but not having much luck.  Now for 
GLUSTERFS service I only get:
                  General (based on my core-site.xml)
                  and
                  Advanced hadoop-env  (based on the hadoop-env.xml)

Any insight would be appreciated...





> GLUSTERFS stack->Installer wizard ->Service Configuration page is rendered 
> empty
> --------------------------------------------------------------------------------
>
>                 Key: AMBARI-6867
>                 URL: https://issues.apache.org/jira/browse/AMBARI-6867
>             Project: Ambari
>          Issue Type: Bug
>          Components: site
>    Affects Versions: 1.7.0
>            Reporter: Jaimin D Jetly
>            Assignee: Scott Creeley
>             Fix For: 1.7.0
>
>




--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to