What kind of Identity is used to grant permissions to a virtual machine enable it to perform operations in GCP?

Citrix DaaS (formerly Citrix Virtual Apps and Desktops service) lets you provision and manage machines on Google Cloud. This article walks you through using Machine Creation Services (MCS) to provision virtual machines in your Citrix Virtual Apps or Citrix Virtual Desktops service deployment.

Requirements

• Citrix Cloud account. The feature described in this article is available only in Citrix Cloud.
• Citrix DaaS subscription. For details, see Get started.
• A Google Cloud project. The project stores all compute resources associated with the machine catalog. It can be an existing project or a new one.
• Enable four APIs in your Google Cloud project. For details, see Enable Google Cloud APIs.
• Google Cloud service account. The service account authenticates to Google Cloud to enable access to the project. For details, see Configure the Google Cloud service account.
• Enable Google private access. For details, see Enable-private-google-access.

Enable Google Cloud APIs

To use the Google Cloud functionality through the Citrix Virtual Apps and Desktops Full Configuration interface, enable these APIs in your Google Cloud project:

• Compute Engine API
• Cloud Resource Manager API
• Identity and Access Management (IAM) API
• Cloud Build API

From the Google Cloud console, complete these steps:

1. In the upper left menu, select APIs and Services > Dashboard.

   

2. On the Dashboard screen, ensure that Compute Engine API is enabled. If not, follow these steps:

   1. Navigate to APIs and Services > Library.

      

   2. In the search box, type Compute Engine.

   3. From the search results, select Compute Engine API.

   4. On the Compute Engine API page, select Enable.

3. Enable Cloud Resource Manager API.

   1. Navigate to APIs and Services > Library.

   2. In the search box, type Cloud Resource Manager.

   3. From the search results, select Cloud Resource Manager API.

   4. On the Cloud Resource Manager API page, select Enable. The status of the API appears.

4. Similarly, enable Identity and Access Management (IAM) API and Cloud Build API.

Configure the Google Cloud service account

A Google Cloud service account lets you create and manage resources inside Google Cloud projects. A Google Cloud service account is required to provision and manage machines, as described in this article. The Google Cloud account authenticates to Citrix Cloud using a key generated by Google Cloud. Each account (personal or service) has various roles defining the management of the project.

We recommend that you create a service account. To do so, follow these steps:

1. In the Google Cloud console, navigate to IAM & Admin > Service accounts.

2. On the Service accounts page, select CREATE SERVICE ACCOUNT.

3. On the Create service account page, type the required information and then select CREATE.

When creating the service account, consider the following:

• You can select CANCEL to save and exit the Service account details page without completing the Grant this service account access to project and the Grant users access to this service account pages. You can do these optional steps later.

• If you choose to skip these optional configuration steps, the newly created service account does not display in the IAM & Admin > IAM page.

• To display roles associated with a service account, add the roles without skipping the optional steps. This process ensures that roles appear for the configured service account.

When creating a service account, there is an option to create a key for the account. You need this key when creating a connection in Citrix DaaS. The key is contained in a credential file (.json). The file is automatically downloaded and saved to the Downloads folder after you create the key. When you create the key, be sure to set the key type to JSON. Otherwise, the Citrix Full Configuration interface cannot parse it.

Tip:

Create keys using the Service accounts page in the Google Cloud console. We recommend that you change keys regularly for security purposes. You can provide new keys to the Citrix Virtual Apps and Desktops application by editing an existing Google Cloud connection.

Also, you need to grant your service account the necessary permissions to access your Google Cloud project:

1. In the Google Cloud console, navigate to IAM & Admin > IAM. On the IAM page, locate the service account you created and then select the pencil icon to edit the service account.

2. On the Edit permissions page, select ADD ANOTHER ROLE to add the following roles to your service account one by one and then select SAVE.

   • Compute Admin
   • Storage Admin
   • Cloud Build Editor
   • Service Account User

3. Update the roles assigned to your Cloud Build service account project:

   1. In the Google Cloud console, navigate to IAM & Admin > IAM.
   2. On the IAM page, locate the Cloud Build service account and then select the pencil icon to edit the service account. You can identify the Cloud Build service account by its user name, which is in this format: <your_gcp_project_ID_number>@cloudbuild.gserviceaccount.com.
   3. On the Edit permissions page, select ADD ANOTHER ROLE to add the following roles to your Cloud Build service account one by one and then select SAVE.
      • Cloud Build Service Account
      • Compute Instance Admin
      • Service Account User

Storage permissions and bucket management

Citrix DaaS improves the process of reporting cloud build failures for the Google Cloud service. This service runs builds on the Google Cloud. Citrix DaaS creates a storage bucket named citrix-mcs-cloud-build-logs-{region}-{5 random characters} where the Google Cloud services captures build log information. An option is set on this bucket that deletes the contents after a period of 30 days. This process requires that the service account used for the connection has Google Cloud permissions set to storage.buckets.update. If the service account does not have this permission, Citrix DaaS ignores errors and proceeds with the catalog creation process. Without this permission, the size of the build logs increases and requires manual cleanup.

Enable private Google access

When a VM lacks an external IP address assigned to its network interface, packets are only sent to other internal IP addresses destinations. When you enable private access, the VM connects to the set of external IP addresses used by the Google API and associated services.

Note:

Whether private Google access is enabled, all VMs that are with and without public IP addresses, must be able to access Google Public APIs, especially if third-party networking appliances have been installed in the environment.

To ensure that a VM in your subnet can access the Google APIs without a public IP address for MCS provisioning:

1. In Google Cloud, access the VPC network configuration.
2. In the Subnet details screen, turn on Private Google access.

For more information, see Configuring Private Google Access.

Important:

If your network is configured to prevent VM access to the Internet, ensure that your organization assumes the risks associated with enabling Private Google access for the subnet to which the VM is connected.

Add a connection

In the Full Configuration interface, follow the guidance in Create a connection and resources. The following description guides you through setting up a hosting connection:

1. From Manage > Full Configuration, select Hosting in the left pane.

2. Select Add Connection and Resources in the action bar.

3. On the Connection page, select Create a new Connection and Citrix provisioning tools, and then select Next.

   • Zone name. Select a zone (equivalent to a resource location) where you want your host resources to reside. Zones are created automatically when you create a resource location and add a Cloud Connector to it. For more information, see Zones.
   • Connection type. Select Google Cloud from the menu.
   • Service account key. Import the key contained in your Google credential file (.json). To do so, locate your credential file, open the file with Notepad (or any text editor), and then copy the content. After that, return to the Connection page, select Import key, paste the content, and then select Save.
   • Service account ID. The field automatically populates with the information from the imported key.
   • Connection name. Type a name for the connection.

4. On the Region page, select a project name from the menu, select a region containing the resources you want to use, and then select Next.

5. On the Network page, type a name for the resources, select a virtual network from the menu, select a subset, and then select Next. The resource name helps identify the region and network combination. Virtual networks with the (Shared) suffix appended to their name represent shared VPCs. If you configure a subnet-level IAM role for a shared VPC, only specific subnets of the shared VPC appear on the subnet list.

   Note:

   • The resource name can contain 1–64 characters, and cannot contain only blank spaces or the characters \ / ; : # . * ? = < > | [ ] { } " ' ( ) ' ).

6. On the Summary page, confirm the information and then select Finish to exit the Add Connection and Resources window.

After creating the connection and resources, the connection and resources you created are listed. To configure the connection, select the connection and then select the applicable option in the action bar.

Similarly, you can delete, rename, or test the resources created under the connection. To do so, select the resource under the connection and then select the applicable option in the action bar.

Prepare a master VM instance and a persistent disk

Tip:

Persistent disk is the Google Cloud term for virtual disk.

To prepare your master VM instance, create and configure a VM instance with properties that match the configuration you want for the cloned VDA instances in your planned machine catalog. The configuration does not apply only to the instance size and type. It also includes instance attributes such as metadata, tags, GPU assignments, network tags, and service account properties.

As part of the mastering process, MCS uses your master VM instance to create the Google Cloud instance template. The instance template is then used to create the cloned VDA instances that comprise the machine catalog. Cloned instances inherit the properties (except the VPC, subnet, and persistent disk properties) of the master VM instance from which the instance template was created.

After configuring the properties of the master VM instance to your specifics, start the instance and then prepare the persistent disk for the instance.

We recommend that you manually create a snapshot of the disk. Doing so lets you use a meaningful naming convention to track versions, gives you more options to manage earlier versions of your master image, and saves time for machine catalog creation. If you do not create your own snapshot, MCS creates a temporary snapshot for you (which is deleted at the end of the provisioning process).

Create a machine catalog

Note:

Create your resources before you create a machine catalog. Use the naming conventions established by Google Cloud when configuring machine catalogs. See Bucket and object naming guidelines for more information.

Follow the guidance in Create machine catalogs. The following description is unique to Google Cloud catalogs.

1. From Manage > Full Configuration, select Machine Catalogs in the left pane.

2. Select Create Machine Catalog in the action bar.

3. On the Machine Type page, select Multi-session OS and then select Next.

   • Citrix DaaS also supports single-session OS.

4. On the Machine Management page, select the Machines that are power managed and the Citrix Machine Creation Services options and then select Next. If there are multiple resources, select one from the menu.

5. On the Master Image page, select a VM and the minimum functional level for the catalog and then select Next. If you want to use the sole tenancy functionality, be sure to select an image whose node group property is correctly configured. See Enable zone selection.

6. On the Storage page, select the type of storage used to contain the operating system for this machine catalog. Each of the following storage options has unique price and performance characteristics. (An identity disk is always created using the zonal standard persistent disk.)

   • Standard persistent disk
   • Balanced persistent disk
   • SSD persistent disk

   For details about Google Cloud storage options, see https://cloud.google.com/compute/docs/disks/.

7. On the Virtual Machines page, specify how many VMs you want to create, view the detailed specification of the VMs, and then select Next. If you use sole tenant node groups for machine catalogs, be sure to select only the zones where reserved sole tenant nodes are available. See Enable zone selection.

8. On the Disk Settings page, you can configure the following settings:

   • Choose whether to enable write-back cache. After enabling write-back cache, you can do the following:

     • Configure the size of the disk and RAM used for caching temporary data. For more information, see Configure cache for temporary data.
     • Select the storage type for the write-back cache disk. The following storage options are available to use for the write-back cache disk:
       • Standard persistent disk
       • Balanced persistent disk
       • SSD persistent disk

       For details about GCP storage options, see https://cloud.google.com/compute/docs/disks/.

     • Select the type for the write-back cache disk.
       • Use non-persistent write-back cache disk. If selected, the write-back cache disk does not persist for the provisioned VMs. The disk is deleted during power cycles and any data redirected to the disk will be lost.
       • Use persistent write-back cache disk. If selected, the write-back cache disk persists for the provisioned VMs. Enabling this option increases your storage costs.

   • When MCS storage optimization (MCS I/O) is enabled, you can choose whether to retain system disks for VDAs during power cycles. For more information, see Enabling MCS storage optimization updates.

   • Choose whether to use your own key to protect disk contents. To use the feature, you must first create your own Customer Managed Encryption Keys (CMEKs). For more information, see Using Customer Managed Encryption Keys (CMEK).

     Note:

     This feature is available as a preview. It is available only in the Manage > Full Configuration interface.

     After creating the keys, you can select one of those keys from the list. You cannot change the key after you create the catalog. Google Cloud does not support rotating keys on existing persistent disks or images. Therefore, after you provision a catalog, the catalog is tied to a specific version of the key. If that key is disabled or destroyed, the instances and disks encrypted with it become unusable until the key is reenabled or restored.

9. On the Machine Identities page, select an Active Directory account and then select Next.

   • If you select Create new Active Directory accounts, select a domain and then enter the sequence of characters representing the naming scheme for the provisioned VM computer accounts created in the Active Directory. The account naming scheme can contain 1–64 characters, and cannot contain blank spaces, or non-ASCII or special characters.
   • If you select Use existing Active Directory accounts, select Browse to navigate to the existing Active Directory computer accounts for the selected machines.

10. On the Domain Credentials page, select Enter credentials, type the user name and password, select Save, and then select Next.

    • The credential you type must have permissions to perform Active Directory account operations.

11. On the Scopes page, select scopes for the machine catalog and then select Next.

    • You can select optional scopes or select custom scope to customize scopes as needed.

12. On the Summary page, confirm the information, specify a name for the catalog, and then select Finish.

    Note:

    The catalog name can contain 1–39 characters, and cannot contain only blank spaces or the characters \ / ; : # . * ? = < > | [ ] { } " ' ( ) ' ).

Machine catalog creation might take a long time to complete. When it completes, the catalog is listed. You can verify that the machines are created on the target node groups in the Google Cloud console.

Add machines to a catalog

To add machines to a catalog, follow these steps:

1. From Manage > Full Configuration, select Machine Catalogs in the left pane.

2. Select the machine catalog to which you want to add machines.

3. Select Add Machines in the action bar.

4. On the Virtual Machines page, specify the number of machines you want to add and then select Next.

5. On the Machine Identities page, select an Active Directory account and then select Next.

6. On the Domain Credentials page, select Enter credentials, type the user name and password, select Save, and then select Next.

7. On the Summary page, confirm the information and then select Finish.

This feature can be useful in cases where you want to update your master image or the minimum functional level.

To update machines, follow these steps:

1. From Manage > Full Configuration, select Machine Catalogs in the left pane.

2. Select the machine catalog that contains machines you want to update.

3. Select Update Machines in the action bar.

4. On the Master Image page, select a VM and the minimum functional level for the catalog and then select Next.

5. On the Rollout Strategy page, specify when you want to update the machines and then select Next.

6. On the Summary page, confirm the information and then select Finish.

To roll back a machine update, follow these steps:

Important:

Do not rename, delete, or move master images. Otherwise you cannot roll back the update.

1. From Manage > Full Configuration, select Machine Catalogs in the left pane.

2. Select the machine catalog where you want to roll back the machine update.

3. Select Rollback Machine Update in the action bar.

4. On the Overview page, confirm the information and then select Next.

5. On the Rollout Strategy page, configure the rollout strategy and then select Next.

6. On the Summary page, confirm the information and then select Finish.

Power management

Citrix DaaS lets your power management of Google Cloud machines. Use the Search node in the navigation pane to locate the machine you want to power manage. The following power actions are available:

• Delete
• Start
• Restart
• Force Restart
• Shut Down
• Force Shutdown
• Add to Delivery Group
• Manage Tags
• Turn On Maintenance Mode

You can also power manage Google Cloud machines by using Autoscale. To do so, add the Google Cloud machines to a Delivery Group and then enable Autoscale for that Delivery Group. For more information about Autoscale, see Autoscale.

Protect accidental machine deletion

Citrix DaaS lets you protect MCS resources on the Google Cloud to prevent accidental deletion. Configure the provisioned VM by setting the deletionProtection flag to TRUE.

By default, VMs provisioned through MCS or Google Cloud plug-in are created with InstanceProtection enabled. The implementation is applicable to both persistent and non-persistent catalogs. The non-persistent catalogs are updated when the instances get re-created from the template. For existing persistent machines, you can set the flag in the Google Cloud console. For more information about setting the flag, see the Google Documentation site. New machines added to persistent catalogs are created with deletionProtection enabled.

If you attempt to delete a VM instance for which you have set the deletionProtection flag, the request fails. However, if you are granted the permission compute.instances.setDeletionProtection or assigned the IAM Compute Admin role, you can reset the flag to allow the resource to be deleted.

Import manually created Google Cloud machines

You can create a connection to Google Cloud and then create a catalog containing Google Cloud machines. Then, you can manually power cycle Google Cloud machines through Citrix DaaS. With this feature, you can:

• Import manually created Google Cloud multi-session OS machines into a Citrix Virtual Apps and Desktops machine catalog.
• Remove manually created Google Cloud multi-session OS machines from a Citrix Virtual Apps and Desktops catalog.
• Use existing Citrix Virtual Apps and Desktops power management capabilities to power manage Google Cloud Windows multi-session OS machines. For example, set a restart schedule for those machines.

This functionality does not require changes to an existing Citrix Virtual Apps and Desktops provisioning workflow, nor the removal of any existing feature. We recommend that you use MCS to provision machines in Citrix DaaS’s Full Configuration interface instead of importing manually created Google Cloud machines.

Shared Virtual Private Clouds (VPCs) comprise a host project, from which the shared subnets are made available, and one or more service projects that use the resource. Shared VPCs are desirable options for larger installations because they provide centralized control, usage, and administration of shared corporate Google cloud resources. For more information, see the Google Documentation site.

With this feature, Machine Creation Services (MCS) supports provisioning and managing machine catalogs deployed to Shared VPCs. This support, which is functionally equivalent to the support currently provided in local VPCs, differs in two areas:

1. You must grant extra permissions to the Service Account used to create the Host Connection. This process allows MCS to access and use Shared VPC Resources.
2. You must create two firewall rules, one each for ingress and egress. These firewall rules are used during the image mastering process.

New permissions required

A Google Cloud service account with specific permissions is required when creating the host connection. These additional permissions must be granted to any service accounts used to create Shared VPC based host connections.

Tip:

These additional permissions are not new to Citrix DaaS. They are used to facilitate the implementation of local VPCs. With Shared VPCs, these additional permissions allow access to other shared VPC resources.

A maximum of four extra permissions must be granted to the service account associated with the host connection to support Shared VPC:

1. compute.firewalls.list - This permission is mandatory. It allows MCS to retrieve the list of firewall rules present on the Shared VPC.
2. compute.networks.list - This permission is mandatory. It allows MCS to identify the Shared VPC networks available to the service account.
3. compute.subnetworks.list – This permission is optional depending on how you use VPCs. It allows MCS to identify the subnets within the visible Shared VPCs. This permission is already required when using local VPCs but must also be assigned in the Shared VPC host project.
4. compute.subnetworks.use - This permission is optional depending on how you use VPCs. It is necessary to use subnet resources in the provisioned machine catalogs. This permission is already required for using local VPCs but must also be assigned in the Shared VPC host project.

When using these permissions, consider that there are different approaches based on the type of permission used to create the machine catalog:

• Project-level permission:
  • Allows access to all Shared VPCs within the host project.
  • Requires the permissions #3 and #4 must be assigned to the service account.
• Subnet-level permission:
  • Allows access to specific subnets within the Shared VPC.
  • Permissions #3 and #4 are intrinsic to the subnet level assignment and therefore do not need to be assigned directly to the service account.

Select the approach that matches your organizational needs and security standards.

Tip:

For more information about the differences between project-level and subnet-level permissions, see the Google Cloud documentation.

Firewall Rules

During the preparation of a machine catalog, a machine image is prepared to serve as the master image system disk for the catalog. When this process occurs, the disk is temporarily attached to a virtual machine. This VM must run in an isolated environment that prevents all inbound and outbound network traffic. This is accomplished through a pair of deny-all firewall rules; one for ingress and one for egress traffic. When using Google Cloud local VCPs, MCS creates this firewall in the local network and applies it to the machine for mastering. After mastering completes, the firewall rule is removed from the image.

We recommend keeping the number of new permissions required to use Shared VPCs to a minimum. Shared VPCs are higher-level corporate resources and typically have more rigid security protocols in place. For this reason, create a pair of firewall rules in the host project on the shared VPC resources, one for ingress and one for egress. Assign the highest priority to them. Apply a new target tag to each of these rules, using the following value:

citrix-provisioning-quarantine-firewall

When MCS creates or updates a machine catalog, it searches for firewall rules containing this target tag. It then examines the rules for correctness and applies them to the machine used to prepare the master image for the catalog. If the firewall rules are not found, or the rules are found but the rules or their priorities are incorrect, a message similar to the following appears:

"Unable to find valid INGRESS and EGRESS quarantine firewall rules for VPC <name> in project <project>. " Please ensure you have created 'deny all' firewall rules with the network tag ‘citrix-provisioning-quarantine-firewall' and proper priority." "Refer to Citrix Documentation for details."

Before adding the Shared VPC as a host connection in Citrix DaaS’s Full Configuration interface, complete the following steps to add service accounts from the project you intend to provision into:

1. Create an IAM role.
2. Add the service account used to create a CVAD host connection to the Shared VPC host project IAM role.
3. Add the Cloud Build service account from the project you intend to provision into to the Shared VPC host project IAM role.
4. Create firewall rules.

Create an IAM role

Determine the access level of the role — project level access or a more restricted model using subnet level access.

Project level access for IAM role. For the project level IAM role, include the following permissions:

• compute.firewalls.list
• compute.networks.list
• compute.subnetworks.list
• compute.subnetworks.use

To create a project level IAM role:

1. In the Google Cloud console, navigate to IAM & Admin > Roles.
2. On the Roles page, select CREATE ROLE.
3. On the Create Role page, specify the role name. Select ADD PERMISSIONS.
   1. On the Add permissions page, add permissions to the role, individually. To add a permission, type the name of the permission in the Filter table field. Select the permission and then select ADD.
   2. Select CREATE.

Subnet-level IAM role. This role omits the addition of the permissions compute.subnetworks.list and compute.subnetworks.use after selecting CREATE ROLE. For this IAM access level, the permissions compute.firewalls.list and compute.networks.list must be applied to the new role.

To create a subnet level IAM role:

1. In the Google Cloud console, navigate to VPC network > Shared VPC. The Shared VPC page appears, displaying the subnets of the Shared VPC networks that the host project contains.
2. On the Shared VPC page, select the subnet that you want to access.
3. In the top-right corner, select ADD MEMBER to add a service account.
4. On the Add members page, complete these steps:
   1. In the New members field, type the name of your service account and then select your service account in the menu.
   2. Select the Select a role field and then Compute Network User.
   3. Select SAVE.
5. In the Google Cloud console, navigate to IAM & Admin > Roles.
6. On the Roles page, select CREATE ROLE.
7. On the Create Role page, specify the role name. Select ADD PERMISSIONS.
   1. On the Add permissions page, add permissions to the role, individually. To add a permission, type the name of the permission in the Filter table field. Select the permission, and then select ADD.
   2. Select CREATE.

Add a service account to the host project IAM role

After creating an IAM role, do the following steps to add a service account for the host project:

1. In the Google Cloud console, navigate to the host project and then to IAM & Admin > IAM.
2. On the IAM page, select ADD to add a service account.
3. On the Add members page:
   1. In the New members field, type the name of your service account and then select your service account in the menu.
   2. Select a role field, type the IAM role you created, and then select the role in the menu.
   3. Select SAVE.

The service account is now configured for the host project.

Every Google Cloud subscription has a service account that is named after the project ID number, followed by cloudbuild.gserviceaccount. For example: .

You can determine what the project ID number is for your project by selecting Home and Dashboard in the Google Cloud console:

Find the Project Number below the Project Info area of the screen.

Perform the following steps to add the Cloud Build service account to the Shared VPC:

1. In the Google Cloud console, navigate to the host project and then to IAM & Admin > IAM.
2. On the Permissions page, select ADD to add an account.
3. On the Add members page, complete these steps:
   1. In the New members field, type the name of the Cloud Build service account and then select your service account in the menu.
   2. Select the Select a role field, type Computer Network User, and then select the role in the menu.
   3. Select SAVE.

Create firewall rules

As part of the mastering process, MCS copies the selected machine image and uses it to prepare the master image system disk for the catalog. During mastering, MCS attaches the disk to a temporary virtual machine, which then runs preparation scripts. This VM must run in an isolated environment that prohibits all inbound and outbound network traffic. To create an isolated environment, MCS requires two deny all firewall rules (an ingress rule and an egress rule). Therefore, create two firewall rules in the Host Project as follows:

1. In the Google Cloud console, navigate to the host project and then to VPC network > Firewall.
2. On the Firewall page, select CREATE FIREWALL RULE.
3. On the Create a firewall rule page, complete the following:
   • Name. Type a name for the rule.
   • Network. Select the Shared VPC network to which the ingress firewall rule applies.
   • Priority. The smaller the value is, the higher the priority of the rule is. We recommend a small value (for example, 10).
   • Direction of traffic. Select Ingress.
   • Action on match. Select Deny.
   • Targets. Use the default, Specified target tags.
   • Target tags. Type citrix-provisioning-quarantine-firewall.
   • Source filter. Use the default, IP ranges.
   • Source IP ranges. Type a range that matches all traffic. Type 0.0.0.0/0.
   • Protocols and ports. Select Deny all.
4. Select CREATE to create the rule.
5. Repeat steps 1–4 to create another rule. For Direction of traffic, select Egress.

Add a connection

After adding the network interfaces to the Cloud Connector instance, add a connection.

Enable zone selection

Citrix DaaS supports zone selection. With zone selection, you specify the zones where you want to create VMs. With zone selection, administrators can place sole tenant nodes across zones of their choice. To configure sole tenancy, you must complete the following on Google Cloud:

• Reserve a Google Cloud sole-tenant node
• Create the VDA master image

Reserving a Google Cloud sole-tenant node

To reserve a sole-tenant node, refer to the Google Cloud documentation.

Important:

A node template is used to indicate performance characteristics of the system that is reserved in the node group. Those characteristics include the number of vGPUs, the amount of memory allocated to the node, and the machine type used for machines created on the node. For more information see the Google Cloud documentation.

Creating the VDA master image

To deploy machines on the sole-tenant node successfully, you need to take extra steps when creating a master VM image. Machine instances on Google Cloud have a property called node affinity labels. Instances used as master images for catalogs deployed to the sole-tenant node require a node affinity label that matches the name of the target node group. To achieve this, keep the following in mind:

Note:

If you intend to use sole tenancy with a shared VPC, see Shared Virtual Private Cloud.

Set a node affinity label when creating an instance

To set the node affinity label:

1. In the Google Cloud console, navigate to Compute Engine > VM instances.

2. On the VM instances page, select Create instance.

3. On the Instance creation page, type or configure the required information and then select management, security, disks, networking, sole tenancy to open the settings panel.

4. On the Sole tenancy tab, select Browse to view the available node groups in the current project. The Sole-tenant node page appears, displaying a list of available node groups.

5. On the Sole-tenant node page, select the applicable node group from the list and then select Select to return to the Sole tenancy tab. The node affinity labels field populates with the information you selected. This setting ensures that machine catalogs created from the instance will be deployed to the selected node group.

6. Select Create to create the instance.

Set a node affinity label for an existing instance

To set the node affinity label:

1. In the Google Cloud Shell terminal window, use the gcloud compute instances command to set a node affinity label. Include the following information in the gcloud command:

   • Name of the VM. For example, use an existing VM named s*2019-vda-base.*
   • Name of the node group. Use the node group name you previously created. For example, mh-sole-tenant-node-group-1.
   • The zone where the instance resides. For example, the VM resides in the *us-east-1b* zone.

   For example, type the following command in the terminal window:

   • gcloud compute instances set-scheduling "s2019-vda-base" --node-group="mh-sole-tenant-node-group-1" --zone="us-east1-b"

   For more information about the gcloud compute instances command, see the Google Developer Tools documentation at https://cloud.google.com/sdk/gcloud/reference/beta/compute/instances/set-scheduling.

2. Navigate to the VM instance details page of the instance and verify that the Node Affinities field populates with the label.

Create a machine catalog

After setting the node affinity label, configure the machine catalog.

Preview: Using Customer Managed Encryption Keys (CMEK)

You can use Customer Managed Encryption Keys (CMEK) for MCS catalogs. When using this functionality, you assign the Google Cloud Key Management Service CryptoKey Encrypter/Decrypter role to the Compute Engine Service Agent. Citrix DaaS account must have the correct permissions in the project where the key is stored. Refer to Helping to protect resources by using Cloud KMS keys for more information.

Your Compute Engine Service Agent is in the following form: service-<Project _Number>@compute-system.iam.gserviceaccount.com. This form is different than the default Compute Engine Service Account.

Note:

This Compute Engine Service Account might not appear in the Google Console IAM Permissions display. In such cases, use the gcloud command as described in Helping to protect resources by using Cloud KMS keys.

Assign permissions to Citrix DaaS account

Google Cloud KMS permissions can be configured in various ways. You can either provide project level KMS permissions or resource level KMS permissions. See Permissions and roles for more information.

Project level permissions

One option is to provide Citrix DaaS account with project-level permissions to browse Cloud KMS resources. To do this, create a custom role, and add the following permissions:

• cloudkms.keyRings.list
• cloudkms.keyRings.get
• cloudkms.cryptokeys.list
• cloudkms.cryptokeys.get

Assign this custom role to your Citrix DaaS account. This allows you to browse regional keys in the relevant project in the inventory.

Resource Level Permissions

For the other option, resource level permissions, in the Google Cloud console, browse to the cryptoKey you use for MCS provisioning. Add Citrix DaaS account to a key ring or a key that you use for catalog provisioning.

Tip:

With this option, you cannot browse regional keys for your project in the inventory because Citrix DaaS account does not have project-level list permissions on the Cloud KMS resources. However, you can still provision a catalog using CMEK by specifying the correct cryptoKeyId in the ProvScheme custom properties, described below.

Provisioning with CMEK using custom properties

When creating your Provisioning Scheme via PowerShell, specify a CryptoKeyId property in ProvScheme CustomProperties. For example:

'<CustomProperties xmlns="http://schemas.citrix.com/2014/xd/machinecreation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Property xsi:type="StringProperty" Name="CryptoKeyId" Value="<yourCryptoKeyId>" /> </CustomProperties>' <!--NeedCopy-->

The cryptoKeyId must be specified in the following format:

projectId:location:keyRingName:cryptoKeyName

For example, if you’d like to use the key my-example-key in key ring my-example-key-ring in the region us-east1 and project with ID my-example-project-1, your ProvScheme custom settings would resemble:

'<CustomProperties xmlns="http://schemas.citrix.com/2014/xd/machinecreation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Property xsi:type="StringProperty" Name="CryptoKeyId" Value="my-example-project-1:us-east1:my-example-key-ring:my-example-key" /> </CustomProperties>' <!--NeedCopy-->

All MCS provisioned disks and images related to this provisioning scheme use this customer managed encryption key.

Tip:

If you use global keys, the customer properties location must say global and not the region name, which in the example above is us-east1. For example: <Property xsi:type="StringProperty" Name="CryptoKeyId" Value="my-example-project-1:global:my-example-key-ring:my-example-key" />.

Rotating customer managed keys

Google Cloud does not support rotating keys on existing persistent disks or images. Once a machine is provisioned it is tied to the key version in use at the time it was created. However, a new version of the key can be created and that new key is used for newly provisioned machines or resources created when a catalog is updated with a new master image.

Key rings cannot be renamed or deleted. Also, you might incur unforeseen charges when configuring them. When deleting or removing a key ring, Google Cloud displays an error message:

Sorry, you can't delete or rename keys or key rings. We were concerned about the security implications of allowing multiple keys or key versions over time to have the same resource name, so we decided to make names immutable. (And you can't delete them, because we wouldn't be able to do a true deletion--there would still have to be a tombstone tracking that this name had been used and couldn't be reused). We're aware that this can make things untidy, but we have no immediate plans to change this. If you want to avoid getting billed for a key or otherwise make it unavailable, you can do so by deleting all the key versions; neither keys nor key rings are billed for, just the active key versions within the keys. <!--NeedCopy-->

Tip:

For more information, see Editing or deleting a key ring from the console.

Uniform bucket-level access compatibility

Citrix DaaS is compatible with uniform bucket-level access control policy on Google Cloud. This functionality augments the use of IAM policy that grants permissions to a service account to allow for the manipulation of resources, including storage buckets. With uniform bucket level access control, Citrix DaaS allows you to use an access control list (ACL) to control access to storage buckets or objects stored in them. See Uniform bucket-level access for overview information about Google Cloud uniform bucket-level access. For configuration information, see Require uniform bucket-level access.

• Connections and resources
• Create machine catalogs