more tweaking
This commit is contained in:
parent
ef6600a91e
commit
7eb81a1b3a
1 changed files with 3 additions and 1 deletions
|
@ -5,7 +5,7 @@ ifupdown, BusyBox ifupdown and Cumulus Networks' ifupdown2.
|
|||
|
||||
## Dependency Resolution
|
||||
|
||||
![Dependency resolution example](doc/img/dependency-resolution.png)
|
||||
<img alt="Dependency resolution example" src="/ifupdown-ng/ifupdown-ng/raw/master/doc/img/dependency-resolution.png" style="float: left">
|
||||
|
||||
ifupdown-ng uses a dependency resolver to determine interface bring-up order
|
||||
in a deterministic way. To use this feature, you must declare relationships
|
||||
|
@ -16,6 +16,8 @@ as the `IF_REQUIRES` environment variable.
|
|||
For compatibility with some legacy ifupdown executors, we also provide the
|
||||
`requires` keyword under other environment variables in some cases.
|
||||
|
||||
<div style="clear: both"></div>
|
||||
|
||||
## Caveats
|
||||
|
||||
* ifupdown2 python plugins are not supported at this time. An executor could be
|
||||
|
|
Loading…
Reference in a new issue