Manage a Google Cloud Platform catalog

Manage machine catalogsdescribes the wizards that manage a machine catalog. The following information covers details specific to Google cloud environments.

Note:

Before managing a Google Cloud Platform catalog, you need to finish creating a Google Cloud Platform catalog. SeeCreate a Google Cloud Platform catalog.

Add machines to a catalog

To add machines to a catalog, follow these steps:

1. FromManage > Full Configuration, selectMachine Catalogsin the left pane.

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

3. SelectAdd Machinesin the action bar.

4. On theVirtual Machinespage, specify the number of machines you want to add and then selectNext.

5. On theMachine Identitiespage, select an Active Directory account and then selectNext.

6. On theDomain Credentialspage, selectEnter credentials, type the user name and password, selectSave, and then selectNext.

7. On theSummarypage, confirm the information and then selectFinish.

Update machines

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. FromManage > Full Configuration, selectMachine Catalogsin the left pane.

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

3. SelectChange Master Imagein the action bar.

4. On theMaster Imagepage, select a VM and the minimum functional level for the catalog and then selectNext.

5. On theRollout Strategypage, specify when you want to update the machines and then selectNext.

6. On theSummarypage, confirm the information and then selectFinish.

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. FromManage > Full Configuration, selectMachine Catalogsin the left pane.

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

3. SelectRoll Back Master Imagein the action bar.

4. On theOverviewpage, confirm the information and then selectNext.

5. On theRollout Strategypage, configure the rollout strategy and then selectNext.

6. On theSummarypage, confirm the information and then selectFinish.

Power management

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

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

你也可以管理谷歌云机器的力量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, seeAutoscale.

Update provisioned machines using PowerShell

TheSet-ProvSchemecommand changes the provisioning scheme. However, it does not affect existing machines. Using the PowerShell commandSet-ProvVMUpdateTimeWindow, you can now apply the current provisioning scheme to an existing persistent or non-persistent machine or set of machines. Currently, in GCP, the property update supported by this feature is machine profile.

You can update:

• A single VM
• A list of specific VMs or all existing VMs associated with a provisioning scheme ID
• A list of specific VMs or all existing VMs associated with a provisioning scheme name

To update the existing VMs:

1. Check the configuration of the existing machines. For example,

   Get-ProvScheme | select ProvisioningSchemeName, ProvisioningSchemeVersion 

2. Update the provisioning scheme. For example,

   `Set-ProvScheme –ProvisioningSchemeName "my-catalog" –MachineProfile "XDHyp:\HostingUnits\\machineprofileinstance.vm" 

3. Check if the current property of the VM matches the current provisioning scheme, and if there is any pending update action on the VM. For example,

   Get-ProvVM | select VMName, ProvisioningSchemeUpdateRequested, ProvisioningSchemeVersion 

   You can also find machines with a particular version. For example,

   Get-ProvVM -Filter "ProvisioningSchemeVersion -eq 1" | select VMName, ProvisioningSchemeVersion 

4. Update existing machines.

   • To update all the existing machines:

     Set-ProvVMUpdateTimeWindow -ProvisioningSchemeName my-catalog -StartsNow -DurationInMinutes -1 

   • To update a list of specific machines:

     Set-ProvVMUpdateTimeWindow -ProvisioningSchemeName my-catalog -VMName  -StartsNow -DurationInMinutes -1 

   • To update machines based on the output ofGet-ProvVM:

     Get-ProvVM -ProvisioningSchemeName "my-catalog" | Set-ProvVMUpdateTimeWindow -ProvisioningSchemeName my-catalog -StartsNow -DurationInMinutes -1 

   Note:

   • StartsNowindicates that the scheduled start time is the current time.
   • DurationInMinuteswith a negative number (for example, –1) indicates no upper bound on the schedule’s time window.

5. Find machines with an update scheduled. For example,

   Get-ProvVM -Filter "ProvisioningSchemeUpdateAfter" | select VMName, ProvisioningSchemeUpdateAfter 

6. Restart the machines. At the next power-up, property changes are applied to the existing machines. You can check the updated status using the following command:

   Get-ProvVM | select VMName, ProvisioningSchemeUpdateRequested, ProvisioningSchemeVersion 

Change disk related custom properties of an existing catalog

You can change the following disk related custom properties of an existing catalog and existing VMs of the catalog:

• PersistOSDisk
• PersistWBC
• StorageType
• IdentityDiskStorageType
• WbcDiskStorageType

Note:

• StorageTypeproperty is for OS disk
• PersistOsDiskproperty can be set only for non-persistent catalog with write-back cache enabled

This implementation helps you to select different storage types for different disks even after you create a catalog and thus, balances pricing associated with different storage types.

To do this, use PowerShell commandsSet-ProvSchemeandSet-ProvVMUpdateTimeWindow:

1. Open aPowerShellwindow.
2. Runasnp citrix*.
3. RunGet-ProvVM -VMName to get the custom properties.
4. Change the custom properties string:
   1. Copy the custom properties to a Notepad and change the custom properties.

   2. In thePowerShellwindow, paste the modified custom properties from Notepad and assign a variable to the modified custom properties. For example:

      $cp = '      ' 

5. Update the existing catalog. For example:

   Set-ProvScheme -ProvisioningSchemeName  -CustomProperties $cp 

6. Update the existing VMs. For example:

   Set-ProvVMUpdateTimeWindow -ProvisioningSchemeName my-catalog -VMName  -StartsNow -DurationInMinutes -1 

7. Restart the VMs. At the next power up, custom property changes are applied to the existing VMs.

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 thedeletionProtectionflag to TRUE.

默认情况下,虚拟机配置通过MCS或谷歌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 theGoogle Documentation site. New machines added to persistent catalogs are created withdeletionProtectionenabled.

If you attempt to delete a VM instance for which you have set thedeletionProtectionflag, the request fails. However, if you are granted the permissioncompute.instances.setDeletionProtectionor assigned the IAMCompute Adminrole, you can reset the flag to allow the resource to be deleted.

Identify resources created by MCS

Following are the tags that MCS adds to the resources on GCP platform. The tags in the table are represented as “key”:”value”.

Resource name	Tag
ID disk	“CitrixResource”: “internal”
	“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”
Image	“CitrixResource”: “internal”
	“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”
OS disk	“CitrixResource”: “internal”
	“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”
PrepVM	“CitrixResource”: “internal”
	“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”
Published snapshot	“CitrixResource”: “internal”
Storage bucket	“CitrixResource”: “internal”
Template	“CitrixResource”: “internal”
	“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”
VM in catalog	“CitrixResource”: “internal”
	“CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”. The plug-in also adds this label for MCS provisioned VMs: “citrix-provisioning-scheme-id”: “provSchemeId”. You can use this label to filter by catalog in the GCP console.
WBC disk	“CitrixResource”: “internal”
	CitrixProvisioningSchemeId”: “xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx”

Note:

A VM is not visible in the Citrix inventory if aCitrixResourcetag is added to identify it as a resource created by MCS. You can remove or rename the tag to make it visible.

更多的信息

• Connections and resources
• Connection to Google cloud environments
• Create machine catalogs
• Create a Google Cloud Platform catalog
• Manage machine catalogs