IV. RESULTADOS
4.5 Geofísica
4.5.1 Reinterpretación de Secciones Geofísicas
The following sections describe the specific settings and custom properties required to create blueprints for various purposes. These procedures apply to both local and global blueprints.
To create a blueprint, select Provisioning Group > Blueprints or Enterprise Administrator > Global Blueprints in the activity pane, move the pointer over the New Blueprint link at the right-hand end of the title bar, and choose Virtual, Physical, or Cloud. Enterprise Administrators and PGMs (or a user who is both) can create blueprints. Users who are both Enterprise Administrator and PGM can choose whether to create a global or a local blueprint.
If you are creating more than one blueprint for similar purposes, remember that you can always copy a Master blueprint to begin a new one. An Enterprise Administrator can copy a global blueprint to create another global blueprint; a group manager who is not an Enterprise Administrator can create only a local blueprint, even if the blueprint being copied is global.
Creating a Blueprint for Virtual Provisioning by Cloning
You can use vCAC to clone both Windows and Linux virtual machines. Cloning involves two objects:
•
A template to clone from, created from a reference machine. A reference machine can be used directly for this purpose as well.•
A customization object to customize the cloned machines by applying System Preparation Util- ity for Windows (SysPrep) information or Linux customization. When cloning in vCenter Server, you specify a customization specification as the customization object. When Cloning in SCVMM Console, Windows SysPrep is performed using Guest OS Profiles that are included in the tem- plate.When cloning Windows machines, you must use a customization object to customize the machines. To customize Linux clones, however, you can specify an external customization script when cloning from a template on which the Linux agent was installed. In vCenter Server, you can even use a customization object and a script together.
Note: When provisioning Windows machines by cloning, you must use the custom- ization specification to set the Active Directory OU of provisioned machines; the default provisioning group OU and the Infrastructure.Admin.MachineObjectOU property are ignored.
Release 5.2 69 VMware Documentation vCloud Automation Center Operating Guide
With vCenter Server, you can take advantage of NetApp FlexClone space-effi- cient storage technology when provisioning by cloning on FlexClone-enabled devices.
To provision by cloning within vCenter Server or SCVMM, create a virtual blueprint with the following set- tings on the Build Information tab:
•
Select Clone to specify that the machine will be cloned. The Provisioning workflow drop-down list is set to CloneWorkflow.•
Set the # CPUs and Memory specifications as desired. vCAC can create a clone with CPU and memory specifications that differ from those of the template in use.•
Set the Minimum counter for Reserved storage exactly as the total storage specification of the template in use.•
Enter the name of the template to clone from in the Clone from box. Type a template name or click the ellipsis (...) button to select it from the list of available templates.Note: The list of templates you can select from includes all templates on all available reservations. vCAC does not validate that the selected template exists on the reservation that is used when provisioning a machine from the blueprint. To avoid errors during provisioning, ensure that the template is available on all reservations that could be used to provision machines from this blueprint, either by adding the template to all possible reservations, or by using reservation poli- cies to restrict the blueprint to reservations where the template is available.
•
For vCenter Server clone blueprints, enter the name of the customization specification in theCustomization spec box. A customization specification is not required unless you are cloning with static IP addresses but you cannot perform any customization of Windows cloned machines without it, or of Linux cloned machines without either a customization specification or an external script or both.
•
Specify the following set of custom properties (or add some or all of them to the incorporated build profile).The four Linux.ExternalScript properties are used to specify your own customization script to be executed by the Linux agent during the CustomizeOS activity. You can execute customization scripts specified using the Linux.ExternalScript properties during provisioning by cloning only if the legacy Linux agent was installed on the reference machine from which the cloning template was created.
You can include other vCAC properties.
Table 5 Custom Properties Required for Cloning Blueprint
Property Definition
VirtualMachine.Admin.ThinProvision
Determines whether thin provisioning is used on ESX Server hosts using local or iSCSI storage. If True, thin provisioning is used; if False, standard provisioning is used; if not specified, virtualization platform default is used.
Note: When provisioning by cloning, the only way to join provisioned Windows machines to an Active Directory domain is by using the customization specifica- tion from vCenter Server or including a GuestOS Profile with your SCVMM tem- plate. Machines provisioned by cloning cannot be placed in an Active Directory container; this must be done manually after the machine is provisioned, if desired.
The VirtualMachine.Admin.AddOwnerToAdmins custom property, which is used to add the machine’s owner (VirtualMachine.Admin.Owner) to the local Administrators group on the machine, is not used for provisioning by cloning.