Before you import or update one or more virtual machines, you must edit the virtual machine CSV data file so that each machine value matches a value that exists in the target deployment. If you are migrating a virtual machine from one environment to another, editing is optional.
About this task
To import, update or migrate virtual machines contained in a CSV data file, each machine must be associated with a reservation, storage location, blueprint, and owner that already exists in the target vRealize Automation deployment. All of the values for each machine must be present in the target vRealize Automation deployment for the operation to succeed. You can change the values for reservation, storage location, blueprint, and owner for any operation on each machine by editing the CSV file.
If you are importing a virtual machine that uses a static IP address, you must append the appropriate command to the CSV file.
- Open the CSV file and edit the data categories so that they match existing categories in the target vRealize Automation deployment.
# Import--Yes or No
Can change to No to prevent a particular machine from being imported.
Virtual Machine Name
Do not change.
Virtual Machine ID
Do not change because it is ignored during the import process.
Host Reservation (Name or ID)
Must match the name of a reservation in the target vRealize Automation instance.
Host To Storage (Name or ID)
Must match the name of a storage location in the target vRealize Automation instance.
Blueprint (Name or ID)
Must match a blueprint in the target vRealize Automation instance.
Must match a domain user in the target vRealize Automation instance.
Custom properties are exported only for managed machines and appear in the CSV file following the data categories. This table presents the custom property format.
Custom property name, for example, __Legacy.Workflow.User.
Custom property value, for example, user%40org.sqa-horizon.local.
Custom property flags: (H|N) = Hidden|Not Hidden - (E|O) Encrypted|NotEncrypted - (R|P) Runtime|NotRuntime, for example, NOP = Not Hidden, Not Encrypted, Not Runtime.
Custom properties ensure that each managed machine is imported with all of the machine properties from the previous environment. The custom properties vary from machine to machine, and there is no standard set of custom properties that appear for each machine by default.
- If you are importing a virtual machine with a static IP address, append a command in the following form to the CSV file.
,VirtualMachine.Network#.Address, w.x.y.z, HOP
Configure the command with the appropriate information for your virtual machine.
#to the number of the network interface being configured with this static IP address. For example,
w.x.y.zto be the static IP address for the virtual machine.
HOPstring sets the visibility of the property. This default property is removed from the virtual machine after a successful import.
For a successful import, the IP address must be available in a properly configured address pool. If the address cannot be found or is already in use, the import will succeed without the static IP address definition, and an error will be logged.
- Save the CSV file and close it.