Using an existing OVF file and staging it as a template and VGP
This topic contains the following sections:
This scenario assumes that an Open Virtualization Format (OVF) file is already present on the provisioning datastore. Information is taken from the OVF file and a template is created on a target Virtual Center server, then a corresponding Virtual Guest Package (VGP) is created.
To use an existing OVF file, use the importVM command, which takes the following arguments:
groupName— Parent group for this jobjobName— Name of the jobinputFile— Input file path
Sample input file
PathToOVF=a3fdda62-6a29-42ba-a18d-f39602194f2f/SuseTestVM.ovf
Target=/id/SystemObject/Server/21e41b60-760d-48f5-8c6b-c753e9f435a4/Assets/BMC_VMware_VirtualInfrastructureManager/82000000/domain-c23,/id/SystemObject/Server/21e41b60-760d-48f5-8c6b-c753e9f435a4/Assets/82000000/BMC_VMware_datastores/datastore1(1),cluster
ProvisionDataStore=Class://SystemObject/DataStore/Provisioning Datastore/localhost
VGPFolderPath=/VGP
VGPandTemplateName=myGentoo32Input file element | Description |
|---|---|
| (Required) This is the path to the .ovf file, relative to the provisioning datastore location. |
| (Required) List of comma-separated statements about the target Virtual Center server. For information on how to build the Target statement, see Build the Target. |
| (Required) Datastore instance for intermediate storage. |
| (Required) The depot folder where you want to store the VGP that this job creates. For example: |
| (Required) The name to use for both the VGP and the template(s). |
Running the importVm command
JOB_GROUP=/VMImportJobs
JOB_NAME=ImportVM
INPUT_FILE=file:///c:/importVM_Input.txt
JOB_KEY=`blcli VMCaptureJob importVM $JOB_GROUP $JOB_NAME $INPUT_FILE'
Comments
Log in or register to comment.