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 10 Next »

Once flexVDI 3.0 is installed, you need to apply a basic configuration to your first host, and create a flexVDI Manager instance to get all your physical resources under control. This operation is done with flexvdi-config, a text based tool which allows you to easily accomplish these tasks.

Initial checks

Every time you run flexVDI Config, it checks the compatibility of your host configuration with flexVDI. If any of these checks fails, it will try to fix them, or notify you otherwise. In particular, flexVDI Config checks the following:

  • The SSH service must be enabled an running.
  • The libvirt daemon service must be enabled and running.
  • The NUMA daemon service must be enabled and running.
  • libvirt must be configured to shut down guests on host shutdown.
  • The hugetlbfs filesystem must be mounted on /dev/hugepages
  • The ksm service must be stopped and disabled.
  • The ntpdate service must be enabled and running.
  • The o2cb service must be configured to use the o2cb stack with a cluster named "ocfs2".

Usually, flexVDI config will fix any problem by itself.

Open network ports

The flexVDI Config tool cannot reliably check that the required network ports are open, so you have to check it by yourself. The network ports used by different components of the flexVDI Software Suits are the following:

  • TCP 22: SSH is used to migrate virtual machines.
  • TCP 443: the flexVDI Gateway installed in each host uses this port to accept connections from clients. This port is configurable in /etc/flexvdi/flexvdi-gateway.conf.
  • TCP 7777: the OCFS2 tools and daemons use this port to communicate.
  • TCP 9443: the flexVDI Agent uses this port to receive requests from the flexVDI Manager.
  • TCP 5800: the flexVDI Manager VM uses this port to accept Spice connections.
  • TCP 5900 and up: Ports used for Spice connections to other VMs.

Of this list, only port TCP 443 must be reachable by flexVDI Clients. The rest can be made reachable only by other hosts of the platform and the Manager.

Main menu

flexVDI Config main menu shows the following options:

  1. Network: TCP/IP configuration, creation of virtual bridges, vLANs and bonding.
  2. Manager: Installation and configuration of flexVDI Manager.
  3. OCFS2: Configuration of storage clusters.
  4. CIFS: Installation of a CIFS server on this flexVDI host to be used as ISO storage for the Guests Media Storage.
  5. Subscription: register the flexVDI Host in flexVDI portal to enable downloading software updates and flexVDI Manager.

Network configuration

flexVDI organizes guests in subnets with the help of virtual bridges. A virtual bridge communicates virtual machines among them and with other computers. All the machines that have a network interface connected to the same virtual bridge will be connected to each other, as if they were in the same network segment. Also, to access machines outside the host, one of its physical interfaces has to be attached to that virtual bridge. With the flexvdi-config tool, you can manage virtual bridges, setup bonds and local VLAN interfaces, and configure the TCP/IP information of them all. In this first basic configuration we are going to create a single virtual bridge (vibr0) with one physical interface attached to it (enp2s0), and configure an IP address. Follow these steps:

  1. Select Network in the main menu.
  2. Select Bridges.
  3. Select Create.

You will be informed that a new network bridge named virbr0 has been created. Upon returning to the screen of network bridges, you will see you have a new bridge with that name, without any assigned slave. An isolated network bridge like that can be useful to define a subnet of virtual machines without direct access to the outside.

In order to attach a physical interface to the virtual bridge, just follow these steps:

  1. Select virbr0.
  2. Select Attach. A list of free network interfaces in that Host will be displayed. Select the one you want to use in order to provide network access to virtual machines (see how network interfaces are named).

Local VLAN management

In a complex network configuration, it may be interesting to separate network traffic in different VLANs. The LocalVLAN option lets you define interfaces that let the host access a VLAN on a virtual bridge. This step only provides VLAN access to the host, and does not provide VLAN access to the flexVDI Manager or other virtual machines, which will have to be configured separately. To create a local VLAN interface on virbr0, follow these steps:

  1. Select Network in the main menu.
  2. Select LocalVLAN.
  3. Select Create.
  4. Select virbr0.
  5. Enter the ID of the VLAN.

A new network interface is created with the name, where id is the VLAN identifier. Thus, through this interface the host is now able to access the VLAN in that virtual bridge.

TCP/IP Configuration

The TCP/IP submenu lets you define the IP network parameters associated with each interface. We will configure the network bridge virbr0 so that the host can access the Internet through it. This will allow us to update the host and download the flexVDI Manager image later. If you created a local VLAN interface in the previous step, configure that interface instead.

  1. Select Network in the main menu.
  2. Select TCP/IP.
  3. You will see a list of all available network interfaces on the host:
  4. Select virbr0 and assign the appropriate network parameters for access to their corporate network. For example:

DNS Configuration 

Finally, the DNS option of the Network menu allows you to configure DNS servers for host name resolution. Simply enter the DNS option, and configure the address of the name servers you want to use.

Applying network configuration changes

Once you have finished the previous steps, the network settings of your first flexVDI Host have been defined. To apply this configuration, you must leave the Network menu. Then flexVDI-config will notify you that the network settings have changed and it is required to restart the network service for the changes to take effect. Confirm that you want to perform the operation.

  • No labels