VMware introduced the supply of the migration device emigrate an on-prem VMware Cloud Director deployment to VMware Cloud Director service in November 2022.
This weblog will exhibit tips on how to carry out a migration of an on-prem VMware Cloud Director deployment to VMware Cloud Director service utilizing the migration device supplied by VMware, as defined within the documentation How Do I Migrate from On-premises VMware Cloud Director to VMware Cloud Director service by Utilizing the Migration Instrument.
An outline of the steps required is:
- Setup the necessities to run the migration device if this will likely be carried out from a Home windows machine
- Create a migration.properties file to learn into the migration device
- Run the migration device (obtain the most recent model from https://github.com/vmware-samples/cloud-director-service-migration and extract to the host you’ll carry out the migration from
Conditions:
Earlier than working the migration device, you’ll need to put in the required packages for Linux or on Home windows, use a shell reminiscent of cygwin to run the device. The under directions exhibit the migration device on Home windows utilizing cygwin. For a full checklist of the migration device necessities, see Migration Instrument Conditions.
For cygwin set up curl, jq, zip, ssh, scp, sshpass, and md5sum.
Create a Migration Properties File
You should not have to create the migration.properties file to do a migration, nevertheless it makes it simpler to see the information in a file, and if you need to rerun the script for any motive, you don’t should maintain retyping the identical info in.
For cygwin, within the default location when opening it, CD to /tmp and create the file known as migration.properties. File within the following keys and their corresponding values:
- SITE_NAME – that is the VMware Cloud Director web site identify that will likely be migrated, reminiscent of vcd-site1
- SITE_ADMIN_USERNAME – this might usually be the administrator account
- IS_APPLIANCE – tells the device whether or not the VMware Cloud Director is an equipment deployment
- CSP_ORG_ID – that is the lengthy org ID of your group within the VMware portal. For extra info on tips on how to discover this info, see
- CSP_ORG_REFRESH_TOKEN – that is the token generated within the VMware portal to make use of for working duties reminiscent of associations, migrations, and different capabilities. For extra info, see How Do I Generate an API Token.
- CELL_USERNAME – this might usually be root
- DBHOST_USERNAME – this might usually be root
Right here is an instance of a migration.properties file crammed out.
|
|
SITE_NAME=vcd–01a.corp.native SITE_ADMIN_USERNAME=administrator IS_APPLIANCE=true CSP_ORG_ID=abcdef–ghjk–1234–5678–abcdef CSP_ORG_REFRESH_TOKEN=12345678910 CELL_USERNAME=root DBHOST_USERNAME=root |
Observe that in case your VMware Cloud Director occasion just isn’t publicly accessible, reminiscent of a lab occasion for dev/take a look at/UAT, you’ll need so as to add one further line to the migration.properties file. The migration device connects to VCD to confirm the model earlier than trying a migration and does so by connecting to the general public DNS identify listed within the migration.properties file, so if it isn’t publicly accessible, add the road under with the attainable values within the hyperlink. You have to to interchange model with the main model quantity being migrated, reminiscent of 10.3, 10.4, and so on.
UPGRADE_CATEGORY=release-model:manufacturing
Under is an instance of my crammed out migration.properties file with UPGRADE_CATEGORY added because the VCD occasion just isn’t publicly accessible.
For those who run the migration script and it fails for any motive previous the purpose the place it begins studying within the migration.properties file, you’ll need to open the properties file and re-add the road for UPGRADE_CATEGORY as will probably be eliminated.
As soon as the migration.properties file has been accomplished, reserve it and open your cygwin bash or which ever bash you might be utilizing. Navigate to the folder that the migration device was extracted to and run the script by working ./migrate.sh.
The script will immediate you line by line to just accept the values that had been entered within the migration.properties file, or if the file doesn’t exist, you’ll need to manually enter the data when prompted.
- Migration properties file discovered, want to reuse. Enter y to learn within the entries from the properties file.
- On-prem VCD web site FQDN identify (discovered: name_from_file). Enter y to make use of the worth from the properties file.
- On-prem VCD admin person identify (discovered: admin_user). Enter y to make use of the worth from the properties file.
- Enter admin password for for on-prem VCD web site name_from_file. Enter the password for the admin account specified to hook up with VCD.
- Is VCD name_from_file equipment primarily based? Enter y to specify it’s an equipment primarily based VCD.
- Username for cell name_from_file discovered. Enter y to make use of the person specified within the file.
- Enter password for cell name_from_file. Enter the password the account specified to hook up with the VCD equipment.
- CSP ORG ID discovered csp_org_from_file. Enter y to make use of the org id specified within the file.
- CSP ORG refresh token discovered token_from_file. Enter y to make use of the CSP org token specified within the file.
- Enter CDI Identify emigrate: This would be the identify of the CDS occasion within the VMware portal. Enter the identify you want the CDS to be known as. Observe that this would be the web site identify inside VCD as nicely.
Within the display screen shot under, you possibly can see that you will want to reply every questions per line.
The migration device will gather the database info from the VCD database cell, add it to an S3 bucket, create the CDS occasion and import the database dump to the brand new occasion. You possibly can see within the display screen shot above on the final line within the backside crimson field that it’s dumping the database from vcd-01a.corp.native to arrange to add it to an S3 bucket.
As soon as the database dump has accomplished, the script will add the recordsdata to an S3 bucket to be imported to create the CDS occasion. Within the display screen shot under, the highest crimson field reveals that the recordsdata had been collected, then efficiently uploaded. The underside crimson field reveals that VMware Cloud Director on prem equipment that’s being migrated is put into upkeep mode to keep away from modifications within the configuration between the migration and the CDS occasion coming on-line.
It is best to now see the CDS occasion that was migrated with the identify supplied in the course of the migration.
