Hi,
there is an integration in place with Gluster, NFS-Ganesha and Pacemaker. This combination makes it possible to have an active-active high-available NFS-server backed by Gluster volumes.
We'd like to add automated testing for functional fail-over in the CI. This requires the use of virtual-IPs that get assigned to the different NFS-Ganesha servers, which will migrate to other servers upon failure.
On https://wiki.centos.org/QaWiki/PubHardware is a mentioning of "reserved IP addresses" where the Gluster project in the CI would like to get listed too. What is the process to request a few IPs, and what are the restrictions we need to be aware of (and how to put them in the Jenkins job)?
Thanks, Niels
On 19/05/16 12:17, Niels de Vos wrote:
Hi,
there is an integration in place with Gluster, NFS-Ganesha and Pacemaker. This combination makes it possible to have an active-active high-available NFS-server backed by Gluster volumes.
We'd like to add automated testing for functional fail-over in the CI. This requires the use of virtual-IPs that get assigned to the different NFS-Ganesha servers, which will migrate to other servers upon failure.
On https://wiki.centos.org/QaWiki/PubHardware is a mentioning of "reserved IP addresses" where the Gluster project in the CI would like to get listed too. What is the process to request a few IPs, and what are the restrictions we need to be aware of (and how to put them in the Jenkins job)?
Thanks, Niels
Hi Niels,
There are probably multiple ways to solve that. For example you have multiple interfaces (and eth0 -> eth3 are now in the same vlan, but only eth0 is configured ) So you can for example use another subnet not conflicting with the 172.19.0.0/22 (nor 172.19.4.0/22 also alocated for remote VMs), but I don't know how you'll test the virtual ip : I guess from another provisioned node (like a nfs client). I've reserved the following range for Gluster : 172.19.2.21 -> 172.19.1.30 (and documented it on the wiki page)
Does that work for you ?
-
Fabian Arrotin -
Niels de Vos