Support more systemd unit types

[bcwaldon]

fleet currently hard-codes support for .service and .socket units. fleet can actually support pretty much all unit types without any extra code, so it's clear we should enable that.

We should probably punt on network units for now given the added complexity they will add to the code.

• service
• socket
• device
• mount
• automount
• timer
• path

[bcwaldon]

Here's the code that limits fleet to handling service and socket units:

fleet/job/payload.go

Line 20 in 5034b17

func (jp *JobPayload) Type() (string, error) {

[bcwaldon]

I'm struggling to see a usecase for device, mount and automount units being scheduled through fleet. Any help?

[polvi]

A cool use case would be a set of units that provision an EBS (.service), mount it (.mount), then run some container (.service). That way you could make sure that the system has the mount points needed no matter where the process was running.

Not sure about automount or device. /cc @marineam

[cnelson]

Agreed with the above. Would be nice to tie a service to a mount unit to ensure that services that need external mounts (say NFS) would work without having to ensure that mount is on every machine in the cluster