On 15-10-2015 09:39, Paulo Ricardo Paz Vital wrote:
Aline, addressing both questions in one answer.
May be the name of the file kimchid.service.fedora is not a good name,
but there is no Kimchi service. We will work only with Wok service. The
kimchid.service.fedora file is a configuration extension for the
wokd.service, where after the installation of the kimchid.service.fedor
a will provide the information to wokd.service that libvirtd is
required.
Let'me try to explain how it works using a use case. The user will
install the RPM or DEB file of Wok, only. This will enable the wokd
service in systemd. Starting the service, libvirtd will not be
required.
Then, the user installs the RPM or DEB file of Kimchi. This will
install an additional file in /etc/systemd/system/wokd.service.d called
kimchi.conf that extends how wokd.service will works after the
installation of Kimchi. At this point, wokd.service will read this
configuration file and used it to start up the service, now requeiring
libvirtd as required service.
If user uninstall the RPM or DEB file of Kimchi, this configuration
file will be deleted and libvirtd will not be required anymore to
wokd.service.
With this approach I can extend wokd service to work with any kind of
plugin I want to use in my system, by configuring only those
requirements and particularities that each plugin needs.
Best regards,
Paulo
On Wed, 2015-10-14 at 18:48 -0300, Aline Manera wrote:
> Hi Paulo,
>
> I am not familiar with systemd config files so I have some questions:
>
> 1) The main service now will be wokd. How starting wokd do we make
> sure
> kimchid service will be trigged and then libvirtd service?
>
> 2) From my view, with your patch the kimchid service would be the
> main
> which is not true.
>
> Regards,
> Aline Manera
>
Really nice solution!
--
Lucio Correia
Software Engineer
IBM LTC Brazil