Ganeti and systemd services

[Jens Larsson]

Hi,

I'm running Ganeti 3.1.0 on Rocky 9 using RPM:s from the
http://jfut.integ.jp/linux/ganeti/ repo.

One thing I haven't been able to find a clear instruction about is what
systemd services to enable. There is a Ganeti.target that I can enable
and start, but this is clearly not enough. Should I enable start the
individual Ganeti services too? Or ganeti-node.target and
ganeti-master.target? Any differences between the master node and the other?

I run configuration management from puppet so enable and disable
services is easy, but keeping track of which node is the master right
now is a bit more complicated.

/jens

[Martin McClure]

Hi Jens,

Well, on a healthy cluster running Ganeti 3.0.2 on Debian 12, I see only
one systemd service running on the master node: ganeti.service. From the
journal entries for the ganeti unit it looks like that one service
starts the various daemons. So I think that's all you need.

HTH,

-Martin

[Jens Larsson]

Hi!

Thanks. I will experiment a bit with this. It looks like a "systemct restart ganeti.target" restarts the already running services, so there is some connection there. I will investigate further.

/jens

[Daniel Howard]

I have noticed that the Debian packaging mechanism is sending nasty grams threatening to pull the ganeti package at the end of the month because it isn't doing systemd.

-Danny

--
Sent from my Western Electric Model 500

--
You received this message because you are subscribed to the Google Groups "ganeti" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ganeti+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/ganeti/027cf33e-fea9-4f25-8ea4-d51189c3fc46n%40googlegroups.com.

[bamblew...@gmail.com]

Jens,

Our org is running several Ganeti 3.0.2 clusters on Rocky 8. KVM is our hypervisor, and we use DRBD for disk replication. I have found the integ-ganeti packages very reliable, well-tested and well-documented. See https://github.com/jfut/ganeti-rpm/blob/main/doc/install-rhel.md for the full how-to on installation, including external dependencies like KVM, DRBD, LVM, SE Linux and the necessary DNF repositories.

Specifically, the necessary services are covered under "Installing Ganeti." In my experience with Ganeti 3.0, on non-master or "master candidate" nodes, the only essential service is ganeti-noded. On master nodes, the essential services are: ganeti-luxid, ganeti-noded, ganeti-rapi and ganeti-wconfd. Services ganeti-metad and ganeti-mond are optional. I have found that service ganeti-kvm is also optional.

Hope this helps.

_________________
John McNally

[Sascha Lucas]

Hi Danny,

On Mon, 27 Oct 2025, Daniel Howard wrote:

> I have noticed that the Debian packaging mechanism is sending nasty grams
> threatening to pull the ganeti package at the end of the month because it
> isn't doing systemd.

I see[1], thanks for pointing out. Looks like missing Ubuntu 26.04. again
...

Thanks, Sascha.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1039204

[Sascha Lucas]

Hi Jens,

On Mon, 27 Oct 2025, Jens Larsson wrote:

> Hi!
>
> Thanks. I will experiment a bit with this. It looks like a "systemct
> restart ganeti.target" restarts the already running services, so there is
> some connection there. I will investigate further.

Ganeti on Debian still uses SysV init script for which systemd will
generate a wrapping unit called ganeti.service.

OTOH Jun providing RPM packages, used provided systemd-examples[1] for a
long time now.

The systemd targets ganeti-node and ganeti-master bundle the required
services for the two node roles: normal node and master node. Also there
is a top level target "ganeti" referencing both of them. There is also a
corresponding ganeti.service which might be the single point of contact
you are looking for.

In SysV the init script determines automatically the needed services to
start WRT to the role of the node. ATM I have no glue how this is resolved
with systemd. If you find out, let me know :-)

Thanks, Sascha.

[1] https://github.com/ganeti/ganeti/tree/78174afe00428b855d4a255f509a347227522b14/doc/examples/systemd

[Daniel Howard]

Sasha,

Your link suggests an easy out:

> As already mentioned in the original bug report, if your package is

> not intended to work as a systemd service or under systemd at all,
> please feel free to downgrade or close+wontifx or anything else as you
> see fit. The severity raising is not intended to make anyone support
> scenarios they don't wish to support, but simply to ensure attention
> is given to the issue, even if just to close+wontfix.

... who is the maintainer, and can they just smack the "nope!" button?

Thanks,

-danny

--
You received this message because you are subscribed to the Google Groups "ganeti" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ganeti+un...@googlegroups.com.

To view this discussion visit https://groups.google.com/d/msgid/ganeti/945387a1-afbb-053b-6c2a-fe5a17eb4d95%40web.de.

--

http://dannyman.toldme.com

[Martin McClure]

I don't think that the "nope" button will work. If I'm reading the bug report correctly, Debian is removing the /etc/init.d compatibility that currently allows Ganeti to work as a system service. Once they do that, Ganeti will stop working, or at least won't automatically start its daemons at system startup any more.

Regards,

-Martin

To view this discussion visit https://groups.google.com/d/msgid/ganeti/CAKU%3DtE9iRcWLsfhk7bbn3KhLAYi1uAXbHrDdWEJPr%3D23UtU8PA%40mail.gmail.com.