From ed7f81793260fd01f2203a5bac28152e769ce273 Mon Sep 17 00:00:00 2001 From: Jonathon Anderson Date: Tue, 21 Feb 2023 09:18:07 -0700 Subject: [PATCH] Capitalize Warewulf in userdocs where appropriate Signed-off-by: Jonathon Anderson --- userdocs/contents/containers.rst | 6 +++--- userdocs/contributing/development-environment-kvm.rst | 4 ++-- userdocs/contributing/development-environment-vbox.rst | 6 +++--- userdocs/debian/debian.md | 2 +- 4 files changed, 9 insertions(+), 9 deletions(-) diff --git a/userdocs/contents/containers.rst b/userdocs/contents/containers.rst index e1b63234..e6752222 100644 --- a/userdocs/contents/containers.rst +++ b/userdocs/contents/containers.rst @@ -68,8 +68,8 @@ The above is just an example. Consideration should be done before doing it this Syncuser -------- -At import time warewulf checks if the names of the users on the host match the users and UIDs/GIDs in the imported container. If there is mismatch, the import command will print out a warning. -By setting the ``--syncuser`` flag you advise warewulf to try to syncronize the users from the host to the container, which means that ``/etc/passwd`` and ``/etc/group`` of the imported container are updated and all the files belonning to these UIDs and GIDs will also be updated. +At import time Warewulf checks if the names of the users on the host match the users and UIDs/GIDs in the imported container. If there is mismatch, the import command will print out a warning. +By setting the ``--syncuser`` flag you advise Warewulf to try to syncronize the users from the host to the container, which means that ``/etc/passwd`` and ``/etc/group`` of the imported container are updated and all the files belonning to these UIDs and GIDs will also be updated. A check if the users of the host and container matches can be triggered with the ``syncuser`` command. @@ -177,7 +177,7 @@ You can use these as starting points and adding any additional steps you want in Building A Container Using Podman -------------------------------------- -You can also build a container using podman via a `Dockerfile`. For this step the container must be exported to a tar archive, which then can be imported to warewulf. The following steps will create an openSUSE Leap container and import it to Warewulf: +You can also build a container using podman via a `Dockerfile`. For this step the container must be exported to a tar archive, which then can be imported to Warewulf. The following steps will create an openSUSE Leap container and import it to Warewulf: .. code-block:: bash diff --git a/userdocs/contributing/development-environment-kvm.rst b/userdocs/contributing/development-environment-kvm.rst index 3c9111a5..023b3eb9 100644 --- a/userdocs/contributing/development-environment-kvm.rst +++ b/userdocs/contributing/development-environment-kvm.rst @@ -56,7 +56,7 @@ Turn off default network dhcp on server master1 sudo virsh net-start default -Build and install warewulf on wwdev +Build and install Warewulf on wwdev =================================== .. code-block:: bash @@ -125,4 +125,4 @@ Build and install warewulf on wwdev sudo wwctl server start sudo wwctl server status -Boot your node and watch the bash and the output of the Warewulfd process \ No newline at end of file +Boot your node and watch the bash and the output of the Warewulfd process diff --git a/userdocs/contributing/development-environment-vbox.rst b/userdocs/contributing/development-environment-vbox.rst index f75fb756..68d7e188 100644 --- a/userdocs/contributing/development-environment-vbox.rst +++ b/userdocs/contributing/development-environment-vbox.rst @@ -28,7 +28,7 @@ I have VirtualBox running on my desktop. # Next attach the second Network adapter #2 to the NAT Network and you should be able to choose # the 'wwnatnetwork' created above in step #1 from the drop down list. -3. Build and install warewulf on wwdev +3. Build and install Warewulf on wwdev .. code-block:: console @@ -135,7 +135,7 @@ I have VirtualBox running on my desktop. sudo wwctl server start sudo wwctl server status -4. Create a new guest VM instance inside the VirtualBox to be the warewulf client/compute node. Under the system configuration make sure to select the optical and network options only for the boot order. The default iPXE used by VirtualBox does not come with bzImage capability which is needed for warewulf. Download the ipxe.iso available at ipxe.org and mount the ipxe.iso to the optical drive. Enable one Network adapter for this VM and assign it to the NAT Network created in step #1 above. +4. Create a new guest VM instance inside the VirtualBox to be the Warewulf client/compute node. Under the system configuration make sure to select the optical and network options only for the boot order. The default iPXE used by VirtualBox does not come with bzImage capability which is needed for Warewulf. Download the ipxe.iso available at ipxe.org and mount the ipxe.iso to the optical drive. Enable one Network adapter for this VM and assign it to the NAT Network created in step #1 above. .. code-block:: console @@ -144,4 +144,4 @@ I have VirtualBox running on my desktop. # VM Settings -> Storage and mount the above download ipxe.so to the Optical Drive. # VM Settings -> Network Enable adapter #1, attach to 'Nat Network' and choose 'wwnatnetwork' from the drop down list. -Boot your node and watch the console and the output of the Warewulfd process \ No newline at end of file +Boot your node and watch the console and the output of the Warewulfd process diff --git a/userdocs/debian/debian.md b/userdocs/debian/debian.md index 6bf5622d..0afec37b 100644 --- a/userdocs/debian/debian.md +++ b/userdocs/debian/debian.md @@ -12,7 +12,7 @@ docker build -t docker.psi.ch:5000/debian:buster-slim . docker push docker.psi.ch:5000/debian:buster-slim ``` -### import docker container into warewulf +### import docker container into Warewulf ```bash wwctl container import docker://docker.psi.ch:5000/debian:buster-slim debian-10:slim