system/systemd
system/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd synced 2024-07-21 18:24:38 +00:00
Code Issues Actions 5 Packages Projects Releases Wiki Activity

docs/WRITING VM_AND_CONTAINER_MANAGERS: update manpage link

Browse source 
and container interface link
This commit is contained in:
Mariano Giménez 2024-02-05 11:36:25 +01:00 committed by hulkoba
parent 288816c503
commit cc7ec2cab4
No known key found for this signature in database
GPG key ID: ACB6C4A3A4F2BE2F
1 changed files with 5 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

26
docs/WRITING_VM_AND_CONTAINER_MANAGERS.md
View file

@ -27,28 +27,12 @@ their own.
## Host OS Integration
All virtual machines and containers should be registered with the
[systemd-machined(8)](https://www.freedesktop.org/software/systemd/man/latest/systemd-machined.service.html)
mini service that is part of systemd. This provides integration into the core
OS at various points. For example, tools like ps, cgls, gnome-system-manager
use this registration information to show machine information for running
processes, as each of the VM's/container's processes can reliably attributed to
a registered machine. The various systemd tools (like systemctl, journalctl,
loginctl, systemd-run, ...) all support a -M switch that operates on machines
registered with machined. "machinectl" may be used to execute operations on any
such machine. When a machine is registered via machined its processes will
automatically be placed in a systemd scope unit (that is located in the
machines.slice slice) and thus appear in "systemctl" and similar commands. The
scope unit name is based on the machine meta information passed to machined at
registration.
All virtual machines and containers should be registered with the [machined](https://www.freedesktop.org/software/systemd/man/latest/org.freedesktop.machine1) mini service that is part of systemd. This provides integration into the core OS at various points. For example, tools like ps, cgls, gnome-system-manager use this registration information to show machine information for running processes, as each of the VM's/container's processes can reliably attributed to a registered machine. The various systemd tools (like systemctl, journalctl, loginctl, systemd-run, ...) all support a -M switch that operates on machines registered with machined. "machinectl" may be used to execute operations on any such machine. When a machine is registered via machined its processes will automatically be placed in a systemd scope unit (that is located in the machines.slice slice) and thus appear in "systemctl" and similar commands. The scope unit name is based on the machine meta information passed to machined at registration.
For more details on the APIs provided by machine consult [the bus API interface
documentation](https://www.freedesktop.org/software/systemd/man/latest/org.freedesktop.machine1.html).
For more details on the APIs provided by machine consult [the bus API interface documentation](https://www.freedesktop.org/software/systemd/man/latest/org.freedesktop.machine1).
## Guest OS Integration
A number of interfaces are defined that permit a machine or container manager
to set provide integration points with the payload/guest system. These
interfaces are documented in [Container Interface of
systemd](https://systemd.io/CONTAINER_INTERFACE) and [VM Interface of
systemd](https://systemd.io/VM_INTERFACE).
As container virtualization is much less comprehensive, and the guest is less isolated from the host, there are a number of interfaces defined how the container manager can set up the environment for systemd running inside a container. These Interfaces are documented in [Container Interface of systemd](CONTAINER_INTERFACE).
VM virtualization is more comprehensive and fewer integration APIs are available. In fact there's only one: a VM manager may initialize the SMBIOS DMI field "Product UUUID" to a UUID uniquely identifying this virtual machine instance. This is read in the guest via /sys/class/dmi/id/product_uuid, and used as configuration source for /etc/machine-id if in the guest, if that file is not initialized yet. Note that this is currently only supported for kvm hosts, but may be extended to other managers as well.