This section shows how to configure flexVDI Manager in High Availability. After this, if the flexVDI Host that is running the flexVDI Manager fails, another instance of the flexVDI Manager will be started on another host automatically. The requirements to clusterize are:
You must use disks shared between the flexVDI Hosts to store the disk image of the instance flexVDI Manager, so that it can be started indiscriminately in any of them. To do this, you must create an Image Storage, and within this a Volume. This task must be done with the flexVDI Dashboard application. Read the guide First steps using flexVDI Dashboard 2.2 , and in particular the section on configuring storage objects to learn more about creating storage objects.
Once the shared Volume has been created, you can access clusterize flexVDI Manager executing flexVDI Config on any host.
After the clusterization has finished, a window will be displayed informing about the outcome of the operation.
You can check the configuration from any flexVDI Host by accessing the /flexvdi/etc/flexvdi-agent-watchdog.conf file. Its contents should be similar to these:
{ "ipaddress" : "10.111.1.181" , "vmname" : "flexVDI_Manager" , "vmimage" : "/flexvdi/image_storages/myImageStorage/myVolume/flexvdi-manager-2.2.17" , "vmdata" : "/flexvdi/image_storages/myImageStorage/myVolume/flexvdi-manager-data" , "vmbridge" : "virbr0" , "vmvlan" : "" , "vmpassword" : "adsfas32" , "instance" : "00" , "ha_mode" : "clustered" , "host_list" : [ "flexhost1" , "flexhost2" ], "ocfs2_primarydisk_id" : "beaf11" , "ocfs2_secondarydisk_id" : "" , "ocfs2_volume_id" : "myVolume" , "ocfs2_imagestorage_id" : "myImageStorage" , "storage_mode" : "ocfs2" } |