vRealize Automation incluye propiedades personalizadas que sirven para proporcionar más controles relativos a los blueprints de clon vinculado.

Algunas propiedades personalizadas de vRealize Automation deben usarse de forma obligatoria con los blueprints de clon vinculado.

Tabla 1. Propiedades personalizadas de los blueprints de clon vinculado

Propiedad personalizada

Descripción

VirtualMachine.DiskN.Storage

Specifies the datastore on which to place the machine disk N, for example DATASTORE01. This property is also used to add a single datastore to a linked clone blueprint. N is the index (starting at 0) of the volume to assign. Enter the name of the datastore to assign to the volume. This is the datastore name as it appears in the Storage Path on the Edit Compute Resource page. Disk numbering must be sequential.

VirtualMachine.DiskN.StorageReservationPolicy

Specifies the storage reservation policy to use to find storage for disk N. Also assigns the named storage reservation policy to a volume. To use this property, substitute the volume number for N in the property name and specify a storage reservation policy name as the value. This property is equivalent to the storage reservation policy name specified on the blueprint. Disk numbering must be sequential. This property is valid for all Virtual and vCloud reservations. This property is not valid for Physical, Amazon, or OpenStack reservations.

VirtualMachine.DiskN.Size

Defines the size in GB of disk N. For example, to give a size of 150 GB to a disk G, define the custom property VirtualMachine.Disk0.Size and enter a value of 150. Disk numbering must be sequential. By default a machine has one disk referred to by VirtualMachine.Disk0.Size, where size is specified by the storage value on the blueprint from which the machine is provisioned. The storage value on the blueprint user interface overwrites the value in the VirtualMachine.Disk0.Size property. The VirtualMachine.Disk0.Size property is not available as a custom property because of its relationship with the storage option on the blueprint. More disks can be added by specifying VirtualMachine.Disk1.Size, VirtualMachine.Disk2.Size and so on. VirtualMachine.Admin.TotalDiskUsage always represents the total of the .DiskN.Size properties plus the VMware.Memory.Reservation size allocation.

VirtualMachine.DiskN.Label

Specifies the label for a machine’s disk N. The disk label maximum is 32 characters. Disk numbering must be sequential. When used with a guest agent, specifies the label of a machine's disk N inside the guest operating system.

VirtualMachine.DiskN.Letter

Specifies the drive letter or mount point of a machine’s disk N. The default is C. For example, to specify the letter D for Disk 1, define the custom property as VirtualMachine.Disk1.Letter and enter the value D. Disk numbering must be sequential. When used in conjunction with a guest agent, this value specifies the drive letter or mount point under which an additional disk N is mounted by the guest agent in the guest operating system.

MaximumProvisionedMachines

Especifica el número máximo de clones vinculados relativos a un snapshot de máquina. El valor predeterminado es ilimitado.

Linux.ExternalScript.Name

Especifica el nombre de un script de personalización opcional (por ejemplo config.sh), que el agente invitado de Linux ejecuta después de que el sistema operativo se haya instalado. Esta propiedad está disponible para las máquinas de Linux clonadas a partir de plantillas en las que el agente de Linux está instalado.

Si especifica un script externo, deberá definir también dónde se ubica utilizando las propiedades Linux.ExternalScript.LocationType y Linux.ExternalScript.Path.

Linux.ExternalScript.LocationType

Especifica el tipo de ubicación del script de personalización nombrado en la propiedad Linux.ExternalScript.Name. Puede ser local o NFS.

También hay que especificar la ubicación del script mediante la propiedad Linux.ExternalScript.Path. Si el tipo de ubicación es NFS, use también la propiedad Linux.ExternalScript.Server.

Linux.ExternalScript.Server

Especifica el nombre del servidor NFS (por ejemplo, lab-ad.lab.local) en el que se encuentra el script de personalización externo de Linux nombrado en Linux.ExternalScript.Name.

Linux.ExternalScript.Path

Especifica la ruta local al script de personalización de Linux o la ruta externa al script de personalización de Linux en el servidor NFS. El valor debe empezar por una barra diagonal y no incluir el nombre de archivo (por ejemplo, /scripts/linux/config.sh).

Si ha instalado el agente invitado para personalizar máquinas clonadas, utilizará algunas propiedades personalizadas más que otras.

Tabla 2. Propiedades personalizadas para personalizar máquinas clonadas con un agente invitado

Propiedad personalizada

Descripción

VirtualMachine.Admin.UseGuestAgent

If the guest agent is installed as a service on a template for cloning, set to True on the machine blueprint to enable the guest agent service on machines cloned from that template. When the machine is started, the guest agent service is started. Set to False to disable the guest agent. If set to False, the enhanced clone workfow will not use the guest agent for guest operating system tasks, reducing its functionality to VMwareCloneWorkflow. If not specified or set to anything other than False, the enhanced clone workflow sends work items to the guest agent.

VirtualMachine.Admin.CustomizeGuestOSDelay

Specifies the time to wait after customization is complete and before starting the guest operating system customization. The value must be in HH:MM:SS format. If the value is not set, the default value is one minute (00:01:00). If you choose not to include this custom property, provisioning can fail if the virtual machine reboots before guest agent work items are completed, causing provisioning to fail.

VirtualMachine.Customize.WaitComplete

Set to True to prevent the provisioning workflow from sending work items to the guest agent until all customizations are complete.

VirtualMachine.SoftwareN.ScriptPath

Specifies the full path to an application's install script. The path must be a valid absolute path as seen by the guest operating system and must include the name of the script filename.

You can pass custom property values as parameters to the script by inserting {CustomPropertyName} in the path string. For example, if you have a custom property named ActivationKey whose value is 1234, the script path is D:\InstallApp.bat –key {ActivationKey}. The guest agent runs the command D:\InstallApp.bat –key 1234. Your script file can then be programmed to accept and use this value.