This is a non-trivial operation. There is a constant flow of communication between different components of the platform, and a change in the IP address of one, some or all of them must be correctly coordinated. Here we present two scenarios: changing the IP address of just the flexVDI Manager, or changing the address of both the Manager and the hosts (e.g. to move them to a different subnetwork).
This change does not require to stop the currently running guests, but we recommend you disable the access to the platform to new users until you finish this procedure.
Stop the flexvdi-agent service in every host:
$ systemctl stop flexvdi-agent # In every host
This is needed so they do not try to restart the flexVDI Manager instance once its address is changed and the communication is lost.
/etc/sysconfig/network-scripts/ifcfg-eth0. Modify it to your needs, changing the IPADDR field, and possibly the NETMASK and GATEWAY fields too.
Restart the network service:
$ service network restart
You will lose communication with the manager once the new IP address is made effective. You may ssh into it again to check that the change has been successfully done.
/etc/flexvdi/flexvdi-gateway.confin every host. Also, in every other flexVDI Gateway instance you have.
Finally, restart the flexvdi-agent service in every host:
$ systemctl start flexvdi-agent # In every host
Changing the IP address of the flexVDI hosts is a bit more delicate process. In particular, if you have configured the OCFS2 cluster and mounted one or more OCFS2 Volumes, you will have to unmount them and stop the cluster in order to change the hosts' IP addresses. This means that you must first stop all the Guests that are using any of these Volumes. In fact, we recommend that you stop all the Guests and disable the access to the platform before continuing.
In every host, stop the o2cb service:
$ systemctl stop o2cb
Your flexVDI Manager instance will be stopped if its images are being stored in an OCFS2 Volume.
/etc/ocfs2/cluster.confand replace all the IP addresses with their new values. You can edit this file once and then copy it to the other hosts.
If you have reconfigured the OCFS2 cluster, restart it again in every host:
$ systemctl start o2cb