You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Bruno Mahé (JIRA)" <ji...@apache.org> on 2013/07/07 01:43:48 UTC

[jira] [Commented] (BIGTOP-939) Make usage of bigtop-tomcat more dynamic

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

Bruno Mahé commented on BIGTOP-939:
-----------------------------------

I am still confused regarding what problem this ticket is trying to solve.
So some questions:
* What configuration challenges did you hit?
* Why can't these configurations be generated at build time?
* Configurations don't change most of the time. So why regenerating them for every start?
* As a user, how do I change tweak configurations without messing up packages (ie. editing files in /usr)?
* Why do we have specific use cases such as https coded in the init script in bash?

I don't mind generating files from templates, but I would rather have this step at build time of packages.

                
> Make usage of bigtop-tomcat more dynamic
> ----------------------------------------
>
>                 Key: BIGTOP-939
>                 URL: https://issues.apache.org/jira/browse/BIGTOP-939
>             Project: Bigtop
>          Issue Type: Task
>            Reporter: Sean Mackrory
>            Assignee: Sean Mackrory
>            Priority: Blocker
>             Fix For: 0.7.0
>
>         Attachments: 0001-BIGTOP-939.-Make-usage-of-bigtop-tomcat-more-dynamic.patch, 0001-BIGTOP-939.-Make-usage-of-bigtop-tomcat-more-dynamic.patch
>
>
> Projects like Oozie and Sqoop present some configuration challenges compared to other components because they use Tomcat. Sometimes small tweaks to the configuration or classpath have to be done in a very component-specific way as opposed to tweaking files in /etc/<comp>/conf or /etc/default. In one case, we even have redundant Tomcat deployments for common configurations (Oozie's SSL vs.  non-SSL).
> If the environment for Tomcat was generated more dynamically, we could avoid this redundancy and could allow common features to be configured in more "standard" ways.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira