DaaS - Chathura Ariyadasa (He/Him/His)

How to patch Horizon DaaS appliances from a Windows computer

Horizon DaaS hotfix management is a very straightforward process. Those Hotfixes and updates are being applied using the HVM (Horizon Version Manager). This process consists of several steps. 

  1. Upload hotfixes/updates to the HVM
  2. Refresh hotfix list
  3. Detect hotfixes on DaaS appliances
  4. Apply hotfix on DaaS appliances
  5. Verifying the hotfixes on DaaS appliances

In our example, we will look at DaaS 9.1.x version (21.1.0). Will look at the entire process in 5 sub-steps.

Upload hotfixes/updates to the HVM

First, download WinSCP and the DaaS hotfixes/updates from VMWare downloads, and then make an SCP connection to the HVM. You need to upload those hotfixes to the /opt/vmware/hvm/hotfixes directory. 

Refresh hotfix list

Once you are done with the hotfix upload, you need to refresh the list of hotfixes that are on the HVM. Projects > Horizon-DaaS-HotFix-Management 

and then Jobs > Refresh Hotfix List and then Run Job Now

Detect hotfixes on DaaS appliances

This is not mandatory. But it is always advisable to check whether the DaaS appliances are patched or not. So, you can simply access the Sub menu and select Step 4, which is Detect Hotfixes on DaaS Appliances. If the appliances are not patched, you may proceed to the next steps. If the appliances are already patched with the latest build, you may hold the patch process. 

Under the Org-IDs tab, you need to enter the relevant tenant ID (keep in mind that tenant ID 1000 is reserved for the SP [Service Provider] appliances).

Continue reading “How to patch Horizon DaaS appliances from a Windows computer”

Apply hotfix on DaaS appliances

When you are ready to apply the hotfixes to the appliances, always make sure to start with the SP appliances. Otherwise, there can be incompatibilities with the tenant appliance operations. On the menu, you will see an option called “Pre-Migrated“. 

As you can see in the above image, option 2 (Pre-Migrated) is for newly upgraded appliances that are yet to be migrated. If you have already migrated the appliances and are in production, you need to select option 3. 

In our example, we have used DaaS 9.1.x. which is version (21.1.0). Once you select the version, you will be presented with the relevant hotfixes which are being uploaded to the HVM hotfixes directory. Over there, you can see 2 different hotfixes. 

  • [SP-RM] – This is for Service Provider appliances and Resource Managers
  • [TA-DM] – This is for Tenant Appliances and Desktop Managers

Based on your need, you may pick the correct hotfix and run the job. If you are going to patch the Service Provider appliances, it would be the [SP-RM] filename

Jobs > Apply Hotfix to DaaS Appliances

Verifying the hotfixes on DaaS appliances

Once you are done with the patching, you could verify the patches by executing the Detect Hotfixes on DaaS Appliances job.

As you can see, we have successfully applied the hotfixes to the tenant appliances. 

Horizon DaaS Service Center resource allocation – the correct way

Once you are done with the VMware Horizon DaaS installation at the Service Provider side, you will be presented with the DaaS Service Center.

The service center enables you to assign compute resources and managers such as vCenter servers. Single vCenter configuration is not supported starting with DaaS 9.1.x, so always make sure to provision 2 more vCenter servers. You may simply add vCenters through Add Host Manager wizard. 

You can manage compute resources by expanding the Compute Resources tab on the Resources page. 

The Compute resource role can be Active, Reserved, or Standby. These options are described in the following table. This is one of the most important parameters on this page.  

Compute resource role Purpose / Usage
Active Compute resource that is actively hosting virtual desktops. All the tenant VDIs are being provisioned.
Reserved Not used for provisioning desktops. This is used to host UAG, TA, SP TA, and other utility servers. 
Standby No longer used.

As you can see in the below image, the following cluster is not being used to host any of the VDI systems. 

Continue reading “Horizon DaaS Service Center resource allocation – the correct way”

Then, will look at the Edit Compute Resource wizard. This is the second most important parameter in the Resource assignment section. 

Parameter Purpose / Usage
Failover Hosts If multiple hosts are detected, the default value is 1. If a single host is detected, the default value is 0.
Host Headroom Percent For the remaining hosts (those not designated as Failover Hosts), enter the percentage of capacity to reserve for disaster recovery. The default value is 20.
Memory Over allocation Ratio This ratio determines the amount of virtual machine memory that the compute resource can allocate. For example, if the ratio is 4.0 and the memory capacity of the compute resource is 64 GB, then it supports up to 256 GB of virtual machine memory. The default value is 1.5.
Virtual to Physical CPU Ratio This ratio determines the number of virtual machine CPUs that the compute resource can allocate. For example, if the ratio is 8.0 and the number of physical CPU cores on the compute resource is 8, then it supports up to 64 virtual machine CPU cores. The default value is 10.

 

 

Usage

Select one or more of the three options (Service, Tenant, Network).
Select Service to install Service Provider and Resource Manager appliances on the cluster.
Select Tenant to install Tenant and additional Desktop Manager appliances on the cluster.
Select Network to install Network appliances like Unified Access Gateway and NSX Edge Gateway on the cluster.

As you can see, all the cluster resources  (Compute/Memory/Network) are being locked by the Service provider service center resource managers. 

If you have correctly configured all the parameters, you should see the Status as GREEN

[source: docs.vmware.com]