[
https://issues.apache.org/jira/browse/BIGTOP-939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678209#comment-13678209
]
Sean Mackrory commented on BIGTOP-939:
--------------------------------------
{quote}
I propose that these modifications be done via catalina.properties exclusively
{quote}
Perhaps I'm misunderstanding what you mean but that, but (contrary to my
comment above :) I actually don't think this is possible. Not all the things we
need to do can be done from catalina.properties alone. Setting the classpath
for Sqoop and Oozie will be done in that file, yes, but then the option of
configuring SSL for Oozie requires other files to be replaced like web.xml,
etc. Other future options might be the same way.
Here's what I propose. All Tomcat projects ship with a "template" directory
like "/usr/lib/<component>/tomcat-deployment.template.", or perhaps
"/etc/<component>/conf/tomcat-deployment.template" (both have pros and cons).
Options for supported tweaks need to be added to the defaults file
"/etc/default/<component>" (for example "AUX_CLASSPATH=..." and
"USE_SSL=true"). When the init script starts the service, it copies the
deployment template to another location (/usr/lib/<component>/<current
location>), deleting what was there if it exists, sources the defaults file and
makes tweaks accordingly, and then launches Tomcat that way it does now.
Now, not being overly familiar with Tomcat or how users are customizing Sqoop
and Oozie now, I expect there may be problems with this simple approach, so
please do chime in with your thoughts. Of course, if this is agreeable to
everyone, I can start on this immediately. Any thoughts from [~jarcec] or
[~rkanter]?
> 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
>
>
> 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
