lagertonne/ifupdown-ng
1
0
Fork 0
Code Issues Pull requests Projects Releases 4 Wiki Activity

Merge pull request #122 from ifupdown-ng/feature/configure-auto-executor-selection

Browse source 
Feature/configure auto executor selection
This commit is contained in:
Ariadne Conill 2020-11-04 21:53:42 -07:00 • committed by GitHub
commit d250ab213c
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
7 changed files with 37 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

6
doc/ADMIN-GUIDE.md
View file

@ -60,6 +60,12 @@ Currently the following settings are supported in
in order to require inheritance from specified templates.
Valid values are `0` and `1`, the default is `1`.
* `auto_executor_selection`: Automatically select executors based
on the presence of their config options. An admin may choose to
disable this setting in order to require explicitly enabling
executors through `use` statements. Valid values are `0` and `1`,
the default is `1`.
* `compat_create_interfaces`:
Denotes where or not to create interfaces when compat\_* settings are
active and it would be necessary to create an interface to be fully

6
doc/ifupdown-ng.conf.scd
View file

@ -17,6 +17,12 @@ configuration options.
performance improvements in setups where only ifupdown-ng executors
are used. Valid values are _0_ and _1_, the default is _1_.
*auto_executor_selection* _bool_
Automatically determine which executors to use. At present, this
is done by inserting `use` statements for the namespace a config
option has. The namespace is separated from the config option with
a dash (`-`). Valid values are _0_ and _1_, the default is _1_.
*use_hostname_for_dhcp* _bool_
Automatically learn the hostname property, used for DHCP
configuration by querying the system hostname using uname(2).

20
doc/interfaces.scd
View file

@ -108,9 +108,9 @@ the system will only respond to certain keywords by default:
configuration data from _object_. Normally _object_
must be a *template*.
*use* _option_
Designates that an option should be used. See _OPTIONS_
section for more information on options.
*use* _executor_
Designates that an executor should be used. See _EXECUTORS_
section for more information on executors.
*pre-down* _command_
Runs _command_ before taking the interface down.
@ -133,11 +133,11 @@ the system will only respond to certain keywords by default:
Additional packages such as *bonding*, *bridge*, *tunnel*, *vrf* and
*vxlan* add additional keywords to this vocabulary.
# OPTIONS
# EXECUTORS
The *use* keyword designates that an _option_ should be used.
The *use* keyword designates that an _executor_ should be used.
This system is extendable by additional packages, but the
most common options are:
most common executors are:
*batman*
The interface is a B.A.T.M.A.N. adv. mesh interface.
@ -181,8 +181,12 @@ most common options are:
*wireguard*
The interface is a Wireguard VPN tunnel endpoint.
Check *interfaces-<option>(5)* for further informaton about a given
option and available configuration parameters.
Check *interfaces-<executor>(5)* for further informaton about a given
executor and available configuration parameters.
If the _auto\_executor\_selection_ ifupdown-ng.conf option is enabled,
*use* statements will automatically be added for executors when their
configuration statements are present in the interfaces file.
# EXAMPLES