Compute Node Configuration

You will want to configure firewalld to not interfere with intra-cluster communication. Either disable it or configure it to use the trusted zone by default.

# PUBLIC_INTERFACE="" # populate this with the value for your COMPUTE NODE environment (e.g. enp1s0)

# firewall-cmd --set-default-zone=trusted

# firewall-cmd --permanent --zone=public --add-interface=${PUBLIC_INTERFACE}

# firewall-cmd --reload

Now you can install and configure NFS on the Compute node so that Fuzzball can share configuration and logging files with the Server node.

# dnf install -y nfs-utils

You can place the following contents in the file /etc/systemd/system/fuzzball-shared.mount to create a service for use with systemd. This will ensure that NFS starts properly again after a reboot.

# NFS_SERVER_IP="" # populate with the internal IP address of the Server node (e.g. 10.0.0.3)

# cat >/etc/systemd/system/fuzzball-shared.mount<<EOF
[Unit]
Description=Mount NFS Share
Requires=remote-fs.target network-online.target
After=remote-fs.target network-online.target

[Mount]
What=${NFS_SERVER_IP}:/srv/fuzzball/shared
Where=/fuzzball/shared
Type=nfs
Options=defaults

[Install]
WantedBy=multi-user.target
EOF

Now create the shared mount point on the Compute node and load/enable/start the newly created nfs service.

# mkdir -p /fuzzball/shared

# systemctl daemon-reload

# systemctl enable --now fuzzball-shared.mount

# ls /fuzzball/shared/
substrate

The final command demonstrates that a configuration directory has already been placed on NFS by Fuzzball Orchestrate.

If the NFS service fails to load or the /fuzzball/shared directory doesn’t allow you to share between the nodes, stop and troubleshoot your NFS configuration before continuing with the instructions. If the Compute node NFS configuration looks good, check the NFS configuration on the Server node.