One I might point out is Spotify's "Luigi" python framework. http://luigi.readthedocs.org/en/latest/index.html At first glance, it might look like it's really hadoop specific -- and it used to be, but the hadoop stuff's been scooped off to a contrib module. Don't let that fool you though, it's actually quite generic and useful for many things -- it's a lot more like GNU make where you describe the state things should be in to proceed.
If you're stuck doing complex dependency control; expressing it to luigi is far less of a headache. On Mon, Jul 6, 2015 at 11:18 AM, Lesley Kimmel <[email protected]> wrote: > You mention 'pacemaker'. Does anyone know of any other open-source > projects that might accomplish the type of remote service dependency > checking that I'm trying to accomplish? For example, if service A on > server A depends on service B on server B is there a project that makes > this type of checking possible/easy? > > > Date: Fri, 26 Jun 2015 19:14:36 +0300 > > From: [email protected] > > To: [email protected] > > CC: [email protected]; [email protected] > > Subject: Re: [systemd-devel] SysVInit service migration to systemd > > > > В Fri, 26 Jun 2015 10:02:41 -0500 > > Lesley Kimmel <[email protected]> пишет: > > > > > Thanks for the information. I've seen that blog before. Unfortunately, > it only describes a starting a service that already has a good level of > integration with some of the underlying infrastructure of systemd (e.g. > dbus). Let me be a little more specific about what I'm trying to accomplish > and see if anyone has any thoughts on how systemd could help (or impede me). > > > > > > I have a collection of servers hosting many processes such as Apache > HTTPD, a database, and Java application servers. Using init these servers > would: a) need to be started in a specific order and b) take a long time to > start. To improve both of these scenarios I created a Python service which > took an XML configuration file describing the dependencies of the various > components. The Python service is started by init and forks so as to not > stop the boot process. The forked process then does some basic dependency > checking (including remote tests, mostly telnet or pings) before starting > local services using init scripts that are not configured to be started by > init. > > > > That sounds exactly like what pacemaker does. > > > > > > > > I'm wondering, with systemd, if this Python "control" daemon would be > required at all. Does systemd have the ability to check the status of > remote servers? > > > > No. > > _______________________________________________ > systemd-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/systemd-devel > > -- Graham Cantin | (408) 890-7463
_______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
