wip README

seapath · Mar 21, 2024 · c48e5c9 · c48e5c9
1 parent 7a51b25
commit c48e5c9
Show file tree

Hide file tree

Showing 3 changed files with 11 additions and 6 deletions.
diff --git a/inventories/README.md b/inventories/README.md
@@ -9,3 +9,14 @@ We recommend to have 3 kinds of inventories:
 - The cluster description inventory, where you will populate the details of your nodes (ip, interface, network details, disks, etc.): a template is provided (seapath_cluster_definition_example.yml)
 - The OpenVSwitch topology inventory, where you will describe the different bridges and ports configuration for OVS: a template is provided (seapath_ovstopology_definition_example.yml)
 - The VM inventory, where you will describe all variables related to the virtual machine (number of cores, features, ip, network interface, etc.): a template is provided (seapath_vm_definition_example.yml)
+
+== Optionnal variables ==
+
+The 
+
+
+variables
+-         apply_network_config: false # do we restart the ovs_config script to apply the changes to the ovs topology (default: false)
+        skip_reboot_setup_network: true # if we do not apply the changes (apply_network_config=false), then the network playbook will reboot the servers at the end. You can choose to skip this reboot here (default: false). It is recommended to let it to false except if you fully understand the network configuration process.
+        skip_recreate_team0_config: false # if defined and true, the network playbook won't try to destroy and recreate the team0 (cluster) bridge configuration (default is false)
+        remove_all_networkd_config: true  # if defined and true, the network playbook will start by wiping the /etc/systemd/network/ directory content, this can help cleaning old conflicting files. THIS MUST NOT BE USED WITH skip_recreate_team0_config at the same time or the cluster network config won't be recreated
diff --git a/inventories/seapath_cluster_definition_example.yml b/inventories/seapath_cluster_definition_example.yml
@@ -227,11 +227,6 @@ all:
         # Main network configuration
         gateway_addr: 10.0.0.1
         dns_servers: "8.8.8.8 8.8.4.4"
-        apply_network_config: false # do we restart the ovs_config script to apply the changes to the ovs topology (default: false)
-        #skip_reboot_setup_network: true # if we do not apply the changes (apply_network_config=false), then the network playbook will reboot the servers at the end. You can choose to skip this reboot here (default: false). It is recommended to let it to false except if you fully understand the network configuration process.
-        skip_recreate_team0_config: false # if defined and true, the network playbook won't try to destroy and recreate the team0 (cluster) bridge configuration (default is false)
-        remove_all_networkd_config: true  # if defined and true, the network playbook will start by wiping the /etc/systemd/network/ directory content, this can help cleaning old conflicting files. THIS MUST NOT BE USED WITH skip_recreate_team0_config at the same time or the cluster network config won't be recreated
-
         ntp_servers:
             - "185.254.101.25"
             - "51.145.123.29"

diff --git a/inventories/seapath_standalone_definition_example.yml b/inventories/seapath_standalone_definition_example.yml
@@ -39,7 +39,6 @@ all:
                             logstash_server_ip: 10.10.10.10
 
                             # Other Network configuration
-                            apply_network_config: true # true to apply the network configuration without rebooting
                             ptp_interface: "enp1s0f1" #OPTIONAL PTP Interface
                             ptp_vlanid: 100 #OPTIONAL VlanID for PTP
                             ptp_delay_mechanism: P2P # OPTIONAL E2E or P2P defaut is P2P