[
https://issues.apache.org/jira/browse/BIGTOP-939?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sean Mackrory updated BIGTOP-939:
---------------------------------
Attachment: 0001-BIGTOP-939.-Make-usage-of-bigtop-tomcat-more-dynamic.patch
So I've tested that the Oozie and Sqoop servers can start and serve clients on
both Debian and Red Hat platforms. I've only made large changes to Oozie since
my last round of more extensive testing. I've moved all of the configuration
under /etc, and tested that you can toggle between the default and secure
configurations with "alternatives --config oozie-tomcat-conf".
All binaries and the entire webapps directory for other components are still
under /usr/lib. I'm happy with how the patch is and believe I've satisified all
other feedback so far, so I'm submitting it for proper review...
> 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,
> 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
