You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 30, 2020. It is now read-only.
Copy file name to clipboardExpand all lines: Documentation/unit-files-and-scheduling.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,6 +23,7 @@ Note that these requirements are derived directly from systemd, with the only ex
23
23
|`MachineMetadata`| Limit eligible machines to those with this specific metadata. |
24
24
|`Conflicts`| Prevent a unit from being collocated with other units using glob-matching on the other unit names. |
25
25
|`Global`| Schedule this unit on all agents in the cluster. A unit is considered invalid if options other than `MachineMetadata` are provided alongside `Global=true`. |
26
+
|`Replaces`| Schedule a specified unit on another machine. A unit is considered invalid if options `Global` or `Conflicts` are provided alongside `Replaces=`. A circular replacement between multiple units is not allowed. |
26
27
27
28
See [more information][unit-scheduling] on these parameters and how they impact scheduling decisions.
0 commit comments