[dev.icinga.com #3869] make classic ui work standalone (drop icinga.cfg reading in favor of cmd pipe/status.dat/objects.cache/logs+archive) #1240
Comments
Updated by mfriedrich on 2013-03-19 12:24:08 +00:00
since icinga2 will write compat log files too, that location should be standalone as well. |
Updated by ricardo on 2013-03-26 20:03:56 +00:00
in current 'dev/cgis' I think this needs a special make option. What do you think? |
Updated by ricardo on 2013-03-26 20:04:19 +00:00
|
Updated by mfriedrich on 2013-03-26 20:05:30 +00:00 make option for what exactly? |
Updated by ricardo on 2013-03-26 20:25:19 +00:00 sorry. Was just wondering if then Classic-UI needs to be provided as single package or something. Or "make install-cgi-only" or something like that. |
Updated by mfriedrich on 2013-03-26 21:01:49 +00:00
works right now. maybe later, we may rip the classic off, and put it standalone somewhere. |
Updated by ricardo on 2013-03-26 23:21:31 +00:00
well then. please test if it works as expected. Thanks |
Updated by mfriedrich on 2013-04-13 11:51:05 +00:00
now copy the magic from a running icinga instance.
also tested the error case, when not having the standalone option enabled, if the icinga2 compat option trigger (they do not, but icinga.cfg will be used instead, nicely done!)
still, there's a small bug inside. if standalone is enable, but main_config_file is set, it will still try to read the values from icinga.cfg at first sight and ignores the rest. commenting main_config_file solves the problem for now.
possible todos
|
Updated by mfriedrich on 2013-04-13 12:56:03 +00:00 requires changes from #3962 and #3963 - first attempt.
|
Updated by mfriedrich on 2013-04-13 13:18:19 +00:00
I've corrected the logic on reading the main config file, if the standalone option is set. once set, it should fully ignore the main config file and use the cgi.cfg instead. otherwise, it would be strange to have the standalone option set, but still reading the main config file. if there's no cgi.cfg available then, it also throws the correct path :-) |
Updated by mfriedrich on 2013-04-13 13:25:51 +00:00 dnsmichi wrote:
--enable-classicui-standalone this is helped by #3962 which allows you to set your own apache config file location with --with-httpd-conf-file=
already modular there.
added hidden 'make install-cgiconf' which gets invoked during 'make install-classicui-standalone'
fixed the STATEDIR creation in install-basic, and used that as fix for the install routine for standalone too (creating the log+archives and extcmdfiledir as well).
see #3963 - this works now out of the box, so nothing more needed than:
|
Updated by mfriedrich on 2013-04-13 13:48:56 +00:00 i'll prepare the docs update, no extra issue required for now. |
Updated by mfriedrich on 2013-04-13 13:55:24 +00:00
everything done. @ricardo |
Updated by mfriedrich on 2013-04-15 10:13:39 +00:00
i've added a howto here: https://wiki.icinga.org/display/howtos/Setting+up+Icinga+Classic+UI+Standalone so for now, i consider this resolved, thanks. |
Updated by ricardo on 2013-04-17 15:01:45 +00:00 Testet and works as expected. Great Teamwork ;-) |
Updated by mfriedrich on 2014-12-08 09:15:20 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/3869
Created by mfriedrich on 2013-03-17 10:20:33 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2013-04-15 10:13:39 +00:00)
Target Version: 1.9
Last Update: 2014-12-08 09:15:20 +00:00 (in Redmine)
this is mainly a problem when putting icinga2 compat locations somewhere onto a dedicated classic ui interface, and setting everything via apache env variables just does not work. even further, tricking it with a dummy icinga.cfg with locations of
does work, but is still ugly. adding those 3 items directly to cgi.cfg (opt-in) will allow us to safely ignore icinga.cfg where no icinga is running.
Attachments
Changesets
2013-03-26 19:50:15 +00:00 by ricardo b1efafc
2013-04-13 12:37:52 +00:00 by (unknown) b805935
2013-04-13 13:14:11 +00:00 by (unknown) 530bca9
2013-04-13 13:34:01 +00:00 by (unknown) 9d3c943
Relations:
The text was updated successfully, but these errors were encountered: