The Bulk Import spreadsheet contains the following information for one or more workloads in your transformation project:
Required workload data
Custom fields
Workload details
Location
NICs
Disks
Applications
You can download a sample spreadsheet from the Bulk Import dialog (Planning > Workloads > Bulk Import) in the Web Interface. Look for the word Required in a column heading to indicate which parameters are required for each type of data or in a data set. Mouse over the red triangle in a heading cell to display help about the purpose and format of the data in the column and whether it is required as part of the mapping process.
See the following tables for information about the expected values and format for each parameter in the Bulk Import spreadsheet:
Bulk Import requires only three columns in the spreadsheet to set up a workload: FQDN, Type, and Validation Status. See Table A-1. This flexibility requires that you provide a header row with proper column names. These three columns must be present in all re-imports for the workloads. If you also include the Workload ID column, PTM automatically populates the IDs in the Results spreadsheet.
NOTE:If you prepare a spreadsheet without column headings, all defined columns must be present in the expected order indicated in the sample spreadsheet.
Table A-1 Required Workload Parameters
|
Parameter |
Required/Optional |
Description |
|---|---|---|
|
FQDN |
Required for all imports. |
Specify the fully qualified domain name for the workload. Example: sqlserver5.paris.digitalair.com An FQDN is universally unique. Thus, a workload can have only one instance in a transformation project. |
|
Validation Status |
Required for all imports. Values are provided by PTM. |
Transformation Manager writes the status for each workload to the Results spreadsheet after validation or after successful import. Clear the field for import. |
|
Workload ID |
Optional; recommended for all imports. Values are provided by PTM. |
If this column is present, PTM writes the original workload’s unique workload ID to the Results spreadsheet after a workload is successfully imported to a project. Example: 1635326 |
|
Type |
Required for all imports. |
Specify the workload type. Acceptable values are CLOUD, PHYSICAL, or VIRTUAL. |
Bulk Import expects the headings of the Custom X columns to match the custom field names you have previously defined for the project. Each project can have up to 7 user-defined fields that apply project-wide. See Table A-2.
You can associate logical names and purpose with the custom fields for each project. For example, if you want to identify the workload with its day-to-day IT administrator, you might define a Field 1 name of Contact for the project. In the spreadsheet, you use Contact instead of Custom 1 as the column heading. Specify values for the field as appropriate for your project, such as a contact person’s name, username, or email address.
Table A-2 Custom Field Parameters
|
Parameters |
Required/Optional |
Description |
|---|---|---|
|
Custom 1 |
Optional |
Specify the project’s Field 1 name as the column heading. For each workload, specify the value based on the project's Field 1 definition. |
|
Custom 2 |
Optional |
Specify the project’s Field 2 name as the column heading. For each workload, specify the value based on the project's Field 2 definition. |
|
Custom 3 |
Optional |
Specify the project’s Field 3 name as the column heading. For each workload, specify the value based on the project's Field 3 definition. |
|
Custom 4 |
Optional |
Specify the project’s Field 4 name as the column heading. For each workload, specify the value based on the project's Field 4 definition. |
|
Custom 5 |
Optional |
Specify the project’s Field 5 name as the column heading. For each workload, specify the value based on the project's Field 5 definition. |
|
Custom 6 |
Optional |
Specify the project’s Field 6 name as the column heading. For each workload, specify the value based on the project's Field 6 definition. |
|
Custom 7 |
Optional |
Specify the project’s Field 7 name as the column heading. For each workload, specify the value based on the project's Field 7 definition. |
Workload details define the operating system and hardware for the source workload. These details are automatically populated for the target workload. You can later modify the details for the target workload by using the Workload dialog or the Bulk Edit action in the Web Interface. See Table A-3.
You can create source resources for Hosts, Networks, and Datastores by including those columns in the spreadsheet. Include the Environment column to create a resource that can apply to a source workload or target workload.
NOTE:A source resource name must be unique among source resources of the same type. The Environment resource name must be unique among environment resources for the project.
The resource name must begin with a letter or number. It can contain only letters, numbers, and the following special characters: space, hyphen, underscore, apostrophe, percent, ampersand, comma, and period.
Table A-3 Workload Details Parameters
|
Parameters |
Required/Optional |
Description |
|---|---|---|
|
Cloud Provider |
Optional; recommended for Cloud workloads |
Specify the cloud provider that will host a cloud workload. Acceptable values are:
|
|
Operating System |
Optional |
Specify an operating system from the Operating Systems list configured in PTM. If no matching value is found in the Operating Systems list, the spreadsheet will not validate. Names are case sensitive. Examples:
PTM includes most operating system types and release versions in the default Operating Systems list. Contact your System Administrator to add custom operating system values to the list. |
|
Memory (MB) |
Optional |
Specify the maximum memory available for the workload. Values default to MB if no unit is specified. Valid binary units are B, MB, GB, TB, PB, EB, ZB, and YB. Examples: 2 GB, 512, 8GB |
|
# of Processors |
Optional |
Specify the number of processors allocated to the workload. Example: 2 |
|
# of Cores |
Optional |
Specify the number of cores per processor. Example: 8 |
Location information can describe the logical, virtual, physical locations of the workload. See Table A-4.
Table A-4 Location Parameters
|
Parameter |
Required/Optional |
Description |
|---|---|---|
|
Environment |
Optional |
Specify the name of the Environment resource for this workload. Values are case sensitive. If no matching value is found, PTM creates a new Environment resource for the project. Examples: staging, preproduction, and production NOTE:The Environment resource name must be unique among environment resources for the project, but it can apply to multiple workloads. |
|
Host |
Optional |
For a virtual workload, specify the name of the source Host resource for the source workload. Values are case sensitive. If no matching value is found, PTM creates a new source Host resource for the project. Examples: mailhost, hyperv-cluster, esx2, citrix5.digitalair.com NOTE:The source Host resource name must be unique among source Host resources for the project, but it can apply to multiple workloads. |
|
Hypervisor |
Optional |
For a virtual workload, specify the hypervisor type running on its source Host resource. Names are case sensitive. Acceptable values are:
|
|
VM Name |
Optional |
For a virtual workload, specify the VM name known to its virtualization host server. Examples: vm-erm2, vm-msx-mailbox, vm-msx-web |
|
Site |
Optional |
Specify the geographical or logical location of the host machine. Examples: Paris, Metro General Hospital, South Campus |
|
Hardware Type |
Optional |
Specify the hardware for the workload’s host machine (that is, the physical machine or a VM’s virtualization host machine). Examples: Dell PowerEdge, Levono X, IBM BladeCenter |
|
Enclosure |
Optional |
Specify the enclosure for the host machine. Examples: AA-21, C205-R5, IL6-C5-R3 |
|
Enclosure Slot |
Optional |
Specify the slot number in the specified enclosure. Examples: U19, B07 |
|
Is Domain? |
Optional |
(OS: Windows family) Boolean value must be either TRUE or FALSE. Specify TRUE if the Windows workload is a member of a domain. Specify FALSE if the Windows workload is a member of a workgroup. |
|
Domain/Workgroup Name |
Optional |
Specify the name of the domain or workgroup for the Windows workload, as appropriate. Domain name examples: CORPDOM, PARIS, or paris.digitalair.com Workgroup name example: WORKGROUP |
You can identify one or more NICs for a workload. You can specify any one of the available NIC input parameters to set up a NIC. See Table A-5. If you also include the NIC1 UUID column, PTM automatically populates the UUIDs in the Results spreadsheet. You can set up multiple NICs by adding additional NIC# column instances.
Table A-5 NIC Parameters
|
Parameters |
Required/Optional |
Description |
|---|---|---|
|
NIC1 UUID |
Optional; recommended for NIC. Values are provided by PTM. |
The UUID is a set of hexadecimal numbers that uniquely identify the NIC in the project. If this column is present, PTM writes a unique ID for each NIC to the Results spreadsheet after a workload is successfully imported to a project, On a re-import, PTM keeps the same ID, and replaces the NIC’s configuration information for the original workload. Example: b916afef-ccfc-4501-aa4c-a4658cd9845d |
|
NIC1 Interface Name |
Optional |
Specify a unique interface name on the workload. Examples: eth0, eth1 |
|
NIC1 IP DHCP |
Optional |
Specify whether a DHCP server provides IP addresses for the NIC. Boolean value must be either TRUE or FALSE. |
|
NIC1 IP Address |
Optional |
Specify an address for the NIC in IPv4 format. Example: 10.10.10.40 |
|
NIC1 MAC |
Optional |
Specify the MAC address for the NIC in the MM:MM:MM:SS:SS:SS format. Example: 01:23:45:67:89:ab |
|
NIC1 Network Name |
Optional |
Specify the name of the source Network resource for the source workload. Values are case sensitive. If no match is found, PTM creates a new source Network resource for the project. Examples: OrgNet-DMZ, OrgNet-Isolated, Azure-VNet-01, VMnet-08 NOTE:The source Network resource name must be unique among source Network resources for the project, but it can apply to multiple NICs on the same or different workloads. |
|
NIC1 VLAN ID |
Optional |
Specify the assigned VLAN ID for this NIC. Providing the ID makes the validation and import functions run faster. Valid values are 1 to 4094. |
|
NIC1 Network Mask |
Optional |
Specify the network mask in IPv4 format. Example: 255.255.252.0 |
|
NIC1 Gateway |
Optional |
Specify the default gateway address in IPv4 format. Multiple entries are not supported. |
|
NIC1 DNS DHCP |
Optional |
Specify whether DNS DHCP is available for the NIC. Boolean value must be either TRUE or FALSE. |
|
NIC1 DNS Servers |
Optional |
Specify one or more addresses in IPv4 format. For multiple entries, place each value on a separate line. |
|
NIC1 Search Domains |
Optional |
Specify one or more search domains. For multiple entries, place each value on a separate line. |
|
Create additional NIC# sections as appropriate, then continue to the next component section. A workload can have multiple network cards, each of which has a unique network configuration. The first defined network card is designated as NIC1, the second as NIC2, and so on. |
||
You can identify one or more disks for a workload. See Table A-6. A disk requires only the Disk1 Vol Type and Disk1 Size columns. If you also include the Disk1 UUID column, PTM automatically populates the UUIDs in the Results spreadsheet. You can set up multiple disks by adding additional Disk# column instances with the minimum of Disk# Vol Type and Disk# Size columns.
Table A-6 Disk Parameters
|
Parameters |
Required/Optional |
Description |
|---|---|---|
|
Disk1 UUID |
Optional; recommended for Disks. Values are provided by PTM. |
The UUID is a set of hexadecimal numbers that uniquely identify the disk in the project. If this column is present, PTM writes a unique ID for each disk to the Results spreadsheet after a workload is successfully imported to a project. On a re-import, PTM keeps the same ID, and replaces the disk’s configuration information for the original workload. Example: 866b4209-4779-48f8-a81d-e8aa04c63d55 |
|
Disk1 Datastore Name |
Optional, applies to Virtual workloads |
Specify the name of the source Datastore resource that contains the disk. Values are case sensitive. If no matching value is found, PTM creates a new source Datastore resource for the project. Example: san-dc-east NOTE:The datastore name must be unique among source Datastore resources for the project. A datastore can apply to multiple disks on the same virtual workload or on different virtual workloads. |
|
Disk1 Vol Name |
Optional |
Specify the unique volume name on the workload. |
|
Disk1 Vol Type |
Optional; required for Disk |
Acceptable values are System, Local, NAS, or SAN. |
|
Disk1 Mount Point |
Optional |
Specify the path from the root of the volume. |
|
Disk1 Size |
Optional; required for Disk |
Specify the total size of the disk. Values default to MB if no unit is specified. Valid binary units are B, MB, GB, TB, PB, EB, ZB, and YB. Examples: 2TB, 500 GB, 102400 |
|
Disk1 Used |
Optional |
Specify the space used on the disk. Values default to MB if no unit is specified. Valid binary units are B, MB, GB, TB, PB, EB, ZB, and YB. Examples: 1.22TB, 162 GB, 51200 |
|
Disk1 Frag Percent |
Optional |
Specify the current percentage of fragmentation on the disk. Example: 3 |
|
Disk1 # Files |
Optional |
Specify the current number of files on the disk. Example: 13151359 |
|
Create additional Disk# sections as appropriate, then continue to the next component section. A workload can have multiple disks, each of which has its own configuration. The first defined disk is designated as Disk1, the second as Disk2, and so on. |
||
You can identify one or more applications for a workload. See Table A-7. Add an Application# column instance for each application you want to track for the workload.
Table A-7 Application Parameter
|
Parameter |
Required |
Description |
|---|---|---|
|
Application1 Name |
Optional |
Only the name of the application is needed. The application must be available to the workload. Values are case sensitive. If no matching value is found, PTM creates a new Application resource for the project. Example: Paris-Project2-Exchange NOTE:An Application name must be unique among Applications for the project, but it can apply to multiple workloads. |
|
Create additional Application# sections as appropriate. A workload can have multiple applications or services associated with it.The first defined application is designated with a column heading of Application1 Name, the second column heading as Application2 Name, and so on. |
||