The container orchestrator landscape

Posted Aug 24, 2022 1:10 UTC (Wed) by jordan (subscriber, #110573)
In reply to: The container orchestrator landscape by bartoc
Parent article: The container orchestrator landscape

I find myself mourning fleet with some regularity.

The container orchestrator landscape

Posted Aug 26, 2022 14:37 UTC (Fri) by mdaverde (guest, #151459) [Link] (2 responses)

With systemd-nspawn, systemd-sysext & portable services, it really does feel like there's a space to be explored for a new systemd-based orchestrator.

I believe Facebook/Meta's infra is heavily systemd-based with their in-house Twine cluster manager but I don't know how much of the internals are available.

The container orchestrator landscape

Posted Aug 26, 2022 15:20 UTC (Fri) by mathstuf (subscriber, #69389) [Link]

How close to fleet[1] do you think this might turn out to be?

[1]https://github.com/coreos/fleet

The container orchestrator landscape

Posted Aug 26, 2022 15:46 UTC (Fri) by paulj (subscriber, #341) [Link]

Systemd would be used for setting up the containers / cgroups yes. But, it's a very small, localised implementation detail really.

Twine (the external name, but more often called 'Tupperware' - probably the better name to use in searches) would be hard-to-impossible to make available to non-FB use, and probably mostly pointless. It is very heavily integrated in with lots of other Facebook infrastructure, from the CI system, to the automated fleet roll-out system of services, to the service discovery and routing system, etc., etc.