kelvin/warewulf
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

updated the configuration to match 4.4.0 features

Browse Source 
Signed-off-by: Christian Goll <cgoll@suse.de>
This commit is contained in:
Christian Goll
2023-02-14 09:23:01 +01:00
parent 7e64e995cb
commit d614db5110
8 changed files with 505 additions and 243 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
userdocs/contents/profiles.rst
View File

@@ -75,7 +75,7 @@ Now that we've created a new profile, let's create a configuration attribute in
.. code-block:: bash
$ sudo wwctl profile set --cluster cluster01 test_profile
? Are you sure you want to modify 1 profile(s)? [y/N] y█
? Are you sure you want to modify 1 profile(s)? [y/N] y
$ sudo wwctl profile list -a test_profile | grep Cluster
test_profile Cluster cluster01
@@ -159,4 +159,4 @@ There are a lot of ways to use profiles to facilitate the management of large cl
But if you do wish to use profiles, the best way to use them is to manage "fixed" configurations of groups of cluster nodes. For example, if you have multiple sub-clusters in your cluster, it might be advantageous to have a ``cluster_name`` profile which includes things like network configurations, and/or a specific kernel, container, boot arguments, etc.
Node specific information, like HW/MAC addresses and IP addresses should always be put in a node configuration rather than a profile configuration.
Node specific information, like HW/MAC addresses and IP addresses should always be put in a node configuration rather than a profile configuration.