Updates announcements and testing
-
New update candidate for XCP-ng 7.6. It adds support for NFS 4.1, that has been contributed by a member of the community and already merged upstream in the XAPI project!
Install it:
yum update sm sm-rawhba --enablerepo='xcp-ng-updates_testing'Revert:
yum downgrade sm sm-rawhbaThanks in advance for your feeback!
-
I feel alone in this thread
-
U are never ALONE
-
@stormi I am watching you.
-
We are the watchmens
-
I'm here. Alive n' kickin'
-
So did anyone install the update candidate for
sm, check that they see no obvious regression and ideally test NFS 4.1 support? -
@stormi
I have an netapp storage. it support nfs 4.1. how can I add a nfs sr with nfs 4.1? I want test it. -
@stormi I did not test it (yet) .. currently copying loads of vm data around at work... but if all goes well I have a free storage next week that will become our new nfs4.1 server for work ... stay tuned
-
@rizaemet-0 here is a XCP-ng Center with NFS 4.1 support: https://github.com/xcp-ng/xenadmin/releases/tag/v7.6.3.21
Just add your NFS SR via the normal assistant, the NFS 4.1 option is right there.
-
I create a nfs sr with nfs 4.1 with xcp-ng center v7.6.3.21. success.
live storage migrate a vm to this sr. success.
live vm migrate to another host. success.
backup vm with xo. success.
I tested copy-paste file in itself and nfs4, nfs4.1, fc between each other. nfs 4.1 speed is like nfs4 speed for my environment.
heavy i/o for 24 hours. no any performance or another issue. -
Do you have better perfs than 4.0 by the way?
-
@olivierlambert Similar performance for my environment. I did not any specific test. Just copy-paste files.
By the way, is multipath connection (or pnfs) possible xcp-ng between storage with nfs4.1? -
It should be possible if you SR is supporting pNFS (because IIRC, it's included in 4.1 protocol).
However, pNFS doesn't remove the usual SPOF (metadata NFS server)
-
pNFS may not be available in XCP-NG's kernel. I see option
CONFIG_NFSD_PNFSunset where as most of the distros haveCONFIG_NFSD_PNFS=y -
@r1 I think that config option is to enable pNFS server support, not the client. I'm pretty sure this being disabled just means that XCP-ng can't be used as a pNFS server (though a VM running on it certainly could).
-
@JeffBerntsen @r1 https://cateee.net/lkddb/web-lkddb/NFSD_PNFS.html
"This option enables support for the parallel NFS features of the minor version 1 of the NFSv4 protocol (RFC5661) in the kernel's NFS server." -
Update released for XCP-ng 7.6 :
openvswitch-2.5.3-2.2.3.3.xcpngIt fixes a problem in log rotation introduced by our previous update: rotated logs for
/var/log/ovsdb-server.logwould get rotated themselves, which could lead to the creation of thousands of rotated log files. My mistake.See https://github.com/xcp-ng/xcp/issues/100 and https://xcp-ng.org/forum/topic/1031/too-many-weird-ovsdb-server-log-file
If you had not installed the previous openvswitch update, then there's no hurry to install this specific update. It would just add log rotation of its logs to avoid having them grow too much.
You don't need to reboot your hosts after installing this update, even if Xen Orchestra says so (we haven't given XO knowledge about what update requires an update yet). Unless you are installing kernel or xen updates at the same time, of course.
The update will not clean the extraneous files, so you'll still need to delete them manually (/var/log/ovsdb-server.log.*).
closed OpenVSwitch Logs aren't rotated #100
-
@stormi
upon update, I got a
Transaction check error:
installing package openvswitch-2.5.3-2.2.3.3.xcpng.x86_64 needs 1 inodes on the /var/log filesystemWhich translated that the ovsdb-server logs were too many and had filled up my log storage.
I had to run:
find . -name "ovsdb*" -delete
because rm couldn't handle so many ovsdb log files to delete. -
@nuts23 Thanks for the feedback. Indeed, when the /var/log partition is out of inode, you may need to delete the files before installing the update.
