I finally throwed in the towel. I did an installation of perfSONAR 4.0.1 on a dual-stack VM. Continue reading perfSONAR 4.0.1 on a dual-stack host
I should point out my intention of running perfSONAR with IPv6 only.
The first impressions aren’t that great. The web UI allows me to select Norway as my country of residence, but it doesn’t save the selected country. If I move to Northern Mariana Islands or to Oman, that’s fine. The main dashboard proudly proclaims: “Error loading test listing: Internal Server Error”. I have done nothing but follow the instructions to the letter. Maybe I should try the previous version and see how well that goes.
I won’t claim I know CentOS or any other Linux distros very well, I have stayed with FreeBSD for the past 18-19 years. I am amazed at the number of hoops we need to jump through to get networking ready in CentOS. In FreeBSD everything is usually placed in
/etc/rc.conf, that’s one file. OK, some other stuff goes in their respective files. In CentOS you have one or more files for each network interface, and several lines of variables in each file. What forced the Linux community to make such poor choices?
Running perfSONAR as a XenServer guest forced me to specify
inst.text as a bootoption. Consequently, I had to visit the package set submenu where I selected “Minimal install”. Selecting “Basic Web Server” made no difference. Selecting “Server with GUI” or “GNOME desktop” was a no-go.
In the name of science, I tried the previous version, perfSONAR 4.0. This one is worse than 4.0.1. The web UI isn’t UTF-8 aware and the
pscheduler service isn’t running at all. Selecting Norway didn’t work either. I also noticed the selected communities are not saved permanently.
firewalld is mostly to blame for preventing access to the Cassandra NoSQL database. Run these commands to stop and disable
systemctl stop firewalld systemctl disable firewalld shutdown -r now Preventive reboot after disabling firewalld.;sleep 1;logout
perfSONAR and its components are remarkably wedded to IPv4. Users running IPv4 only, or dual-stack, will not notice any difference until they turn off IPv4 in favour of IPv6.
One crude workaround is to add a dummy IPv4 address to the NIC, say
TEST-NET-1. Don’t bother adding a default gateway for IPv4.
Ensure the hostname resolves to the host’s IPv6 and IPv4 addresses, in that order, via
2001:db8::x yourhost.fqdn yourhost 192.0.2.x yourhost.fqdn yourhost
Better yet, run dual-stack until the matter is resolved.