Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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).

Changing the IP address of the flexVDI Manager instance

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.

  1. Stop the flexvdi-agent service in every host:

    No Format
    $ 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.

  2. Log into your flexVDI Manager instance (with ssh) and edit the file /etc/sysconfig/network-scripts/ifcfg-eth0. Modify it to your needs, changing the IPADDR field, and possibly the NETMASK and GATEWAY fields too.
  3. Restart the network service:

    No Format
    $ 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.

  4. Fix the flexVDI Manager IP address in the files /etc/flexvdi/flexvdi-agent-watchdog and /etc/flexvdi/flexvdi-gateway.conf in every host. Also, in every other flexVDI Gateway instance you have.
  5. Finally, restart the flexvdi-agent service in every host:

    No Format
    $ systemctl start flexvdi-agent # In every host


Changing the IP address of the flexVDI hosts

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.

...