This series was originally going to be a more polished endeavour, but unfortunately time got in the way. A prod from James Kilby (@jameskilbynet) has convinced me to publish as is, as a series of lab notes. Maybe one day I’ll loop back and finish them…
I’ve deployed a CentOS7 VM from my standard template, and configured the prerequisites as per my prerequisites post. Updates, NTP, DNS and SELinux have all been configured. I have added a 200GB disk to the base VM, which has then been partitioned, formatted and mounted to /nfs/data - this will be the share used for vCloud Director.
Installing and configuring an NFS share is a pretty common admin task, so it doesn’t require a lot of explanation (I hope!)
Install the packages:
yum install nfs-utils rpcbind
Enable, and start the services:
systemctl enable nfs-server
systemctl enable rpcbind
systemctl enable nfs-lock
systemctl enable nfs-idmap
systemctl start rpcbind
systemctl start nfs-server
systemctl start nfs-lock
systemctl start nfs-idmaptouch
Once the services have been configured I add a configuration line to /etc/exports to export the mount (/nfs/data), allow access from the NFS subnet (10.12.0.97/27) with the required settings for vCloud Director.
echo “/nfs/data 10.12.0.97/27(rw,sync,no_root_squash,no_subtree_check)” » /etc/exports
The following command will load the /etc/exports configuration:
Finally, open the firewall ports to allow NFS clients to connect:
firewall-cmd -permanent -zone=public -add-service=nfs
firewall-cmd -permanent -zone=public -add-service=mountd
firewall-cmd -permanent -zone=public -add-service=rpc-bind
Now that the NFS share is in place, I can move on to the next supporting service for vCloud Director - RabbitMQ. The NFS share will be mounted to the vCloud Director cells when they are installed later.