[ 
https://issues.apache.org/jira/browse/AMBARI-22647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivér Szabó updated AMBARI-22647:
----------------------------------
    Description: 
Goals:
- package logsearch / logfeeder classes into jars
- create default logsearch-env and logfeeder-env files (those where only 
generated by ambari stack code)
- rename run.sh start scripts to logsearch.sh and logfeeder.sh, and create a 
symlink for those in /usr/bin/
(therefore we can call commands like: 'logsearch start' or 'logfeeder test 
--test-log-entry ...')
- refactor logfeeder command line tool -> new java entry point -> use it 
through /usr/bin/logfeeder
- remove pid / process handling logic from ambari stack code (as the new 
logsaerch/logfeeder script will handle those)
- move all config files from classes target/package/conf during maven package 
phase
- move "/etc/ambari-logsearch-.../conf" folder to 
/usr/lib/ambari-logsearch.../conf, keep the old one as a symlink. (this 
solution is useful as we can include every requried files in a tar.gz as well 
and it can work without provided rpm/deb)
- as conf file was moved out, we need to handle some cases during yum/apt 
upgrade - move conf/keys/ or conf/checkpoints/ files to the new location (as 
those could be generated there before and we do not want to loose them)
- as conf files are moved, cleanup maven assembly configs

> Rafactor: Package Log Search and Log Feeder into jars + cleanup start scripts
> -----------------------------------------------------------------------------
>
>                 Key: AMBARI-22647
>                 URL: https://issues.apache.org/jira/browse/AMBARI-22647
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-logsearch
>    Affects Versions: 3.0.0
>            Reporter: Olivér Szabó
>            Assignee: Olivér Szabó
>             Fix For: 3.0.0
>
>
> Goals:
> - package logsearch / logfeeder classes into jars
> - create default logsearch-env and logfeeder-env files (those where only 
> generated by ambari stack code)
> - rename run.sh start scripts to logsearch.sh and logfeeder.sh, and create a 
> symlink for those in /usr/bin/
> (therefore we can call commands like: 'logsearch start' or 'logfeeder test 
> --test-log-entry ...')
> - refactor logfeeder command line tool -> new java entry point -> use it 
> through /usr/bin/logfeeder
> - remove pid / process handling logic from ambari stack code (as the new 
> logsaerch/logfeeder script will handle those)
> - move all config files from classes target/package/conf during maven package 
> phase
> - move "/etc/ambari-logsearch-.../conf" folder to 
> /usr/lib/ambari-logsearch.../conf, keep the old one as a symlink. (this 
> solution is useful as we can include every requried files in a tar.gz as well 
> and it can work without provided rpm/deb)
> - as conf file was moved out, we need to handle some cases during yum/apt 
> upgrade - move conf/keys/ or conf/checkpoints/ files to the new location (as 
> those could be generated there before and we do not want to loose them)
> - as conf files are moved, cleanup maven assembly configs



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to