From 7d1a627134365e1e79dd8e27bcdcb669cbb3d530 Mon Sep 17 00:00:00 2001 From: richm Date: Wed, 6 Sep 2023 20:48:52 +0000 Subject: [PATCH] Update README.html for latest --- docs/index.html | 38 ++++++++++++++++++++++++++++---------- latest/README.html | 38 ++++++++++++++++++++++++++++---------- 2 files changed, 56 insertions(+), 20 deletions(-) diff --git a/docs/index.html b/docs/index.html index 292638e..859d5e7 100644 --- a/docs/index.html +++ b/docs/index.html @@ -177,6 +177,8 @@ id="toc-type-macvlan">type: macvlan id="toc-type-infiniband">type: infiniband
  • type: wireless
    • +
  • type: dummy
  • autoconnect
    • @@ -232,24 +234,33 @@ the target machines. This role can be used to configure:

    Introduction

    The network role supports two providers: nm -and initscripts. nm is used by default in -RHEL7 and initscripts in RHEL6. These providers can be -configured per host via the initscripts. nm is used by default since +RHEL7 and initscripts in RHEL6. The +initscripts provider requires network-scripts +package which is deprecated in RHEL8 and dropped in RHEL9. These +providers can be configured per host via the network_provider variable. In absence of explicit configuration, it is autodetected based on the distribution. However, note that either nm or initscripts is not tied to a certain distribution. The network role works everywhere the required API is available. This means that nm requires at least NetworkManager's API version 1.2 -available. For initscripts, the legacy network service is -required as used in Fedora or RHEL.

    +available and certain settings supported by nm provider +also requires higher NetworkManager's API version since which the +settings are introduced.

    +

    The network role supports two modules: +network_connections and network_state.

    For each host a list of networking profiles can be configured via the network_connections variable.

    For each host the network state configuration can also be applied to the interface directly via the network_state variable, and @@ -462,6 +473,7 @@ or deactivates the connection without changing its configuration.

  • macvlan
  • infiniband
  • wireless
    • +
  • dummy

    • type: ethernet

    If the type is ethernet, then there can be an extra @@ -485,7 +497,8 @@ types work similar. Note that team is not supported in RHEL6 kernels, and has been deprecated in RHEL 9.

    For ports, the port_type and controller properties must be set. Note that ports should not have ip -settings.

    +settings, which means that the active ports will not have IP addresses +assigned.

    The controller refers to the name of a profile in the Ansible playbook. It is neither an interface-name nor a connection-id of NetworkManager.

    @@ -557,6 +570,9 @@ href="#ieee802_1x">ieee802_1x option.

  • password: password for the network (required if wpa-psk or sae is used)

    • +

    type: dummy

    +

    Dummy network interface, nm (NetworkManager) is the only +supported network_provider for this type.

    autoconnect

    By default, profiles are created with autoconnect enabled.

    Note: When route_append_only or rule_append_only is not specified, the network role deletes @@ -1449,6 +1464,9 @@ automatically.

    stored as ifcfg files as well, but it is not guaranteed that plain initscripts can handle these ifcfg files after disabling the NetworkManager service.

    +

    The network role also supports configuring in certain +Ansible distributions that the role treats like RHEL, such as AlmaLinux, +CentOS, OracleLinux, Rocky.

    Limitations

    As Ansible usually works via the network, for example via SSH, there are some limitations to be considered:

    diff --git a/latest/README.html b/latest/README.html index 292638e..859d5e7 100644 --- a/latest/README.html +++ b/latest/README.html @@ -177,6 +177,8 @@ id="toc-type-macvlan">type: macvlan id="toc-type-infiniband">type: infiniband
  • type: wireless
    • +
  • type: dummy
  • autoconnect
    • @@ -232,24 +234,33 @@ the target machines. This role can be used to configure:

    Introduction

    The network role supports two providers: nm -and initscripts. nm is used by default in -RHEL7 and initscripts in RHEL6. These providers can be -configured per host via the initscripts. nm is used by default since +RHEL7 and initscripts in RHEL6. The +initscripts provider requires network-scripts +package which is deprecated in RHEL8 and dropped in RHEL9. These +providers can be configured per host via the network_provider variable. In absence of explicit configuration, it is autodetected based on the distribution. However, note that either nm or initscripts is not tied to a certain distribution. The network role works everywhere the required API is available. This means that nm requires at least NetworkManager's API version 1.2 -available. For initscripts, the legacy network service is -required as used in Fedora or RHEL.

    +available and certain settings supported by nm provider +also requires higher NetworkManager's API version since which the +settings are introduced.

    +

    The network role supports two modules: +network_connections and network_state.

    For each host a list of networking profiles can be configured via the network_connections variable.

    For each host the network state configuration can also be applied to the interface directly via the network_state variable, and @@ -462,6 +473,7 @@ or deactivates the connection without changing its configuration.

  • macvlan
  • infiniband
  • wireless
    • +
  • dummy

    • type: ethernet

    If the type is ethernet, then there can be an extra @@ -485,7 +497,8 @@ types work similar. Note that team is not supported in RHEL6 kernels, and has been deprecated in RHEL 9.

    For ports, the port_type and controller properties must be set. Note that ports should not have ip -settings.

    +settings, which means that the active ports will not have IP addresses +assigned.

    The controller refers to the name of a profile in the Ansible playbook. It is neither an interface-name nor a connection-id of NetworkManager.

    @@ -557,6 +570,9 @@ href="#ieee802_1x">ieee802_1x option.

  • password: password for the network (required if wpa-psk or sae is used)

    • +

    type: dummy

    +

    Dummy network interface, nm (NetworkManager) is the only +supported network_provider for this type.

    autoconnect

    By default, profiles are created with autoconnect enabled.

    Note: When route_append_only or rule_append_only is not specified, the network role deletes @@ -1449,6 +1464,9 @@ automatically.

    stored as ifcfg files as well, but it is not guaranteed that plain initscripts can handle these ifcfg files after disabling the NetworkManager service.

    +

    The network role also supports configuring in certain +Ansible distributions that the role treats like RHEL, such as AlmaLinux, +CentOS, OracleLinux, Rocky.

    Limitations

    As Ansible usually works via the network, for example via SSH, there are some limitations to be considered: