Quattor services should support systemd on EL7

[jouvin]

The current situation with Quattor services (cdispd, listend) managed as legacy services works and there is no hurry to improve it. But I think we need at some point to provide an EL7 of these RPMs (at least) that will provide the necessary scripts for integrating with systemd instead of init.d and use them in the RPM scripts. Part of the work to be done is in the services themselves, in particular to provide a pom file doing the right thing on each platform.
But this also has a consequence on our current release packaging. This cannot be done (in a clean way at least) with our current single YUM repository per release. My suggestion would be to move to one repository per major OS version (e.g. 15.2.0/el5, 15.2.0/el6, 15.2.0/el7) and do the right thing when configuring the repo on a given machine. This is pretty easy to do/to hide in the template-library that already provides repository/config/quattor as the recommended way to configure the repo. And to build the full release independently on each platform. This solution would have the advantage not to impact the release process. And if we could even define el5 as a symlink to el6 (or the opposite) as long as these two don't diverge... (if we solve the RPM format issue).
What do you think?

[stdweird]

rebuilding per OS might also solve some of the rpm packaging issues. the build_all_repos script actually already creates all rpms, and we already run this on EL5, 6 and 7.

wrt systemd, if a service file is available, it will always be pereferred to the sysvinit one, so no real issue to ship them both while we resolve building per OS (but people or scripts might use e.g. /etc/init.d/abc start instead of neutral service abc start)

[ned21]

Is the action here to open an RFE against the appropriate repositories (cdispd, cdp-listend) to include unit files as well as SysV initscripts?