Re: [Engine-devel] rewrite the engine-notifier service wrapper
----- Original Message -----
From: "Yair Zaslavsky" <yzaslavs(a)redhat.com>
To: "Alon Bar-Lev" <alonbl(a)redhat.com>
Cc: "Juan Hernandez" <jhernand(a)redhat.com>, "Simon Grinberg"
<simon(a)redhat.com>, "engine-devel"
<engine-devel(a)ovirt.org>
Sent: Tuesday, April 23, 2013 10:07:39 AM
Subject: Re: [Engine-devel] rewrite the engine-notifier service wrapper
----- Original Message -----
> From: "Alon Bar-Lev" <alonbl(a)redhat.com>
> To: "engine-devel" <engine-devel(a)ovirt.org>
> Cc: "Juan Hernandez" <jhernand(a)redhat.com>, "Simon
Grinberg"
> <simon(a)redhat.com>
> Sent: Tuesday, April 23, 2013 1:15:01 AM
> Subject: [Engine-devel] rewrite the engine-notifier service wrapper
>
> Hello,
>
> After finish to cleanup the engine-service to use downstream
> services and be
> portable to other distributions (upstart, openrc), we can use the
> same
> infrastructure for the engine notifier script.
>
> It is very similar to the engine-service in operation (running
> java), except
> it is written in bash instead of python and has no systemd support,
> and have
> its own configuration.
>
> What I suggest is to rewrite the notifier service in python and
> reuse the
> engine-service code.
>
> Also, drop the /etc/ovirt-engine/notifier/notifier.conf in favor of
> variables
> within the /etc/ovirt-engine/engine.conf[.d/*], this will provide a
> single
> point of configuration for all services.
>
> And of course proper systemd support and development environment
> support.
>
> Any comments? thoughts?
>
> Alon
IMHO - +1 , the sooner the better - start with that and move to all
the other bash scripts of the tools ;)
+1
> _______________________________________________
> Engine-devel mailing list
> Engine-devel(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
_______________________________________________
Engine-devel mailing list
Engine-devel(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel