From fb38e22cd13a97945520697860de8f0cd6ed8156 Mon Sep 17 00:00:00 2001
From: Ariadne Conill <ariadne@dereferenced.org>
Date: Tue, 18 Aug 2020 15:26:02 -0600
Subject: [PATCH] admin guide: expand on dependency relationships

---
 doc/ADMIN-GUIDE.md | 60 ++++++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 60 insertions(+)

diff --git a/doc/ADMIN-GUIDE.md b/doc/ADMIN-GUIDE.md
index 7ff5fd9..7a9c30f 100644
--- a/doc/ADMIN-GUIDE.md
+++ b/doc/ADMIN-GUIDE.md
@@ -135,6 +135,66 @@ iface eth0
     gateway 2001:db8:1000:2::1
 ```
 
+### Relationships
+
+As previously mentioned, ifupdown-ng features a dependency
+resolver that allows for determining the interface configuration
+order.
+
+![Dependency resolution example](img/dependency-resolution.png)
+
+In order to make use of this, dependencies can be managed in one
+of two ways:
+
+#### Explicit dependency management using `requires`
+
+The `requires` keyword can be used to manage explicit
+dependencies:
+
+```
+auto eth0
+iface eth0
+    use dhcp
+
+auto gre0
+iface gre0
+    requires eth0
+
+    use gre
+    gre-endpoint 203.0.113.2
+    gre-ttl 255
+    gre-flags ignore-df
+
+    address 203.0.113.194/30
+    gateway 203.0.113.193
+```
+
+#### Implicit dependency management using executors
+
+Executors can declare implicit dependencies which work the same
+way as explicit dependencies, but are learned at run-time, for
+example:
+
+```
+auto bond0
+iface bond0
+    use bond
+
+    bond-members eth0 eth1
+    [...]
+```
+
+Is equivalent to:
+
+```
+auto bond0
+iface bond0
+    use bond
+
+    requires eth0 eth1
+    [...]
+```
+
 ## Questions
 
 If you have further questions about how to use ifupdown-ng to