Hi all,
Let take some times to talk about the packages for Shinken and how to launch the application for the users. ======== Package(s) ============= First of all how many packages? We've got differents part in the application : * the shinken python librairy that install in the python directory * the daemons (5 daemons) and some should not be install every where (like the arbiter, just need 2 even for a huge env) * all misc of them (/etc/defaults/shinken, libexec, var and etc). I think users will want 2 things : *easy install of the whole application in one host *easy install of just the scheduler or poller to scale the load. There is also a problem with broker modules : some need python-mysqldb. So we install it even if people use livestatus? And we should do as easy as we can for packagers and users :) ======= Howto launch =========== >From now there are init.d scripts to launch each daemon, and so the user can activate them with chkconfig or whatever else he want. Is a unique init.d script taht just look at *d.ini config files is a good idea? Is it easier for user? It's true that a gid parts of users will want to run all in their server, so combine with multiple packets, they will just install what they want and launch the uniq script without changing a line of conf. It's lazy mode, so it should be a good one :) What do you think about it? 6 packets (5 daemon, + one common for etc, defaults var and libexec) and one uniq init.d script. It ask more effort to packagers it's true, but users will be able to be lazy guys :) Jean On Thu, Aug 5, 2010 at 2:56 PM, nap <napar...@gmail.com> wrote: > Thanks a lot :) > > I add them to the git repository so every one can have a common version. > > For everyone : we talk here of ini, but from now in the code it's the > *d.cfg files that will be renamed into *d.ini to make a true > difference between them and the global configuration. > > For the global launch I don't know. It's easier to wrote the script, > but is is easier for the user? It's true he just need to launch one > init.d script to launch all, but at the begining it can be hard to > know that one daemon is not starting just because he missed to add the > good ini file. > > But it's also true that with the package, the ini files will already > be installed, so no problem for them after all (the only one are > people who want to install it at the hand). So it sounds like a good > idea for the majority of users. > > Now how to find which damon to launch. By the ini files name? (broker > in it -> broker daemon). > > > Jean > > On Thu, Aug 5, 2010 at 2:22 PM, Stéphane Urbanovski > <s.urbanov...@ac-nancy-metz.fr> wrote: >> Hi >> >> Here is a first draft of a shinken.spec. For now it require some tweaked >> configuration files (to fix paths). >> >> I'm suggesting here to have a single launcher script. This script check for >> the presence of a .ini file or a configuration parameter to know wich module >> should be launched. >> >> This can simplify the initscripts (SysV) logic. >> >> As a bonus, I joined the .spec file for pyro. >> >> All of this have been (not well) tested on a RHEL5 using EPEL version of >> python26. >> >> Regards >> >> -- >> Stéphane Urbanovski >> >> ------------------------------------------------------------------------------ >> The Palm PDK Hot Apps Program offers developers who use the >> Plug-In Development Kit to bring their C/C++ apps to Palm for a share >> of $1 Million in cash or HP Products. Visit us here for more details: >> http://p.sf.net/sfu/dev2dev-palm >> _______________________________________________ >> Shinken-devel mailing list >> Shinken-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/shinken-devel >> >> > ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Shinken-devel mailing list Shinken-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/shinken-devel
