Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

New Features

flexVDI 3.1 comes with the following main features:

  1. New web-based Dashboard! Just point a modern web browser to your flexVDI Manager's IP address and enjoy this new interface. No more installation required.
  2. Many of the components it is based on have been upgraded:
    1. QEMU/KVM 2.12.0, based on RHEV 7 packaged version, with small additions.
    2. libvirt 4.5.0, as shipped by RHEL 7.6.
    3. SPICE server 0.14.0, based on RHEL 7.6 packaged version, with small additions.
  3. LDAP group search: Configure your Desktop Policies in a group entry for all the users in that group.
  4. Many small improvements:
    1. TODO

Upgrade process

Preparation

Upgrading from flexVDI 3.0 to 3.1 can be done with no downtime! However, just in case something goes really wrong, back up your flexVDI Manager Database, as explained in flexVDI Manager Backup.

Just in case I was not clear enough: Back up your flexVDI Manager Database. If you delete your old Manager instance without backing it up, you will have to rebuild your platform configuration by hand.

Upgrade!

Install flexVDI 3.1 in all your hosts. The flexVDI 3.1 installer will detect your current subscription and support contract certificates, so the installation is mostly automatic. If you wish to change your portal credentials or update your contract certificates, do so with flexvdi-config before running the installer.

This will update all the server packages to 3.1, while your Manager instance is still at 3.0. So, now just upgrade it as explained in the Administration Guide, and you are done! Enjoy your new flexVDI 3.1 platform!!

Reverting the upgrade process

If something goes terribly wrong and you need to revert the installation process to flexVDI 3.0, followe these steps. Read them carefully and do not perform any action that is not explicitly listed here:

  1. In your hosts, uninstall all flexVDI related packages. The OCFS2 kmod package may refuse to uninstall, this is acceptable.

    # rpm -qa | grep flexvdi | xargs yum remove -y
  2. Stop the flexVDI Manager instance, from the host that is currently running it.

    # virsh destroy flexVDI_Manager
  3. Remove the flexVDI 3.1 yum repository file and clean the yum metadata.

    # rm -f /etc/yum.repos.d/flexvdi-3.1.repo
    # yum clean metadata
  4. Run the flexVDI 3.0 installer on all your hosts. You may need to downgrade the kernel if you upgraded it to a version that is not supported by flexVDI 3.0.
  5. Run flexvdi-config and:
    1. Go to Manager → Install, and follow the steps to install the latest version of flexVDI Manager 3.0.
    2. Go to Manager → Password and change the Manager default password.
    3. DO NOT perform any other step yet: Register, Move, etc...
  6. Restore your Manager backup: Go to Manager → Restore and follow the instructions.
  7. In all your hosts, start the flexvdi-agent service.

    # systemctl start flexvdi-agent

At this point, your flexVDI 3.0 platform should be up and running again. Contact our support group to get additional help on your problems upgrading to flexVDI 3.1.

  • No labels