Before you deploy a PlateSpin Migrate Connector server, ensure that your environment meets the following requirements and guidelines.
PlateSpin Migrate Connector 2 supports the following components of PlateSpin Migration Factory:
PlateSpin Transformation Manager 2
PlateSpin Migrate Connector 2 is included with this version of PTM.
PlateSpin Migrate 2018.11
PlateSpin Transformation Manager and PlateSpin Migrate Connector require PlateSpin Migrate servers to execute automated migrations and to track manual migrations. Other discovery and planning features do not require PlateSpin Migrate servers.
IMPORTANT:If the Role service WebDAV Publishing is installed on the PlateSpin Migrate server, uninstall it from Server Manager > Roles > Web Server (IIS) > Role Service > Common HTTP features > WebDAV Publishing.
For information about how to buy this product, see PlateSpin Migrate.
For information about installing and using this product, see the PlateSpin Migrate Documentation website.
PlateSpin Migrate Connector 2 is not backwards compatible with previous release versions of PlateSpin Transformation Manager and PlateSpin Migrate.
PlateSpin Migrate Connector has been written and tested on SUSE Linux Enterprise Server (SLES) 12 Service Pack 3 (SLES 12 SP3) servers.
Installation of the PlateSpin Migrate Connector RPM on other distributions of Linux requires the dependent software packages in Table 14-1. For example, you can upgrade Migrate Connector from version 1.1.1 running on SLES 11 SP4 to version 2.0 if the dependent software packages are available on your SLES 11 SP4 server.
Table 14-1 Prerequisite Software for PlateSpin Migrate Connector on Linux Distributions
|
Prerequisite Software Package |
Version |
|---|---|
|
certifi |
2018.1.18 |
|
connexion |
1.3 |
|
cryptography |
2.2 |
|
impacket |
0.9.15 |
|
lxml |
4.2.0 |
|
mock |
2.0.0 |
|
paramiko |
2.4.1 |
|
pycrypto |
2.6.1 |
|
pysmb |
1.1.22 |
|
python-dateutil |
2.7.0 |
|
python-ntlm |
1.1.0 |
|
pytz |
2018.3 |
|
pyVmomi |
6.5 |
|
requests |
2.18.4 |
|
requests-ntlm |
1.1.0 |
|
scp |
0.10.2 |
|
six |
1.11.0 |
|
stomp.py |
4.1.20 |
|
tzlocal |
1.5.1 |
|
urllib |
3 1.22 |
Consider the following deployment guidelines for PlateSpin Migrate Connector:
Deploy at least one Migrate Connector server in each source network (the network where source workloads reside).
PlateSpin Transformation Manager Appliance includes a pre-installed instance of the PlateSpin Migrate Connector that is configured to work with the PTM server. You can use this Connector instance to migrate source workloads that reside in the same network as the deployed PTM Appliance.
You can deploy multiple Connector instances in the same source network to increase performance of event processing for source workloads in that network. Each Connector instance services the workloads it discovers.
For migration to VMware or to VMware Cloud on Amazon Web Services, deploy a Migrate Connector instance in each target network to enable discovery of its target VMware vCenter Servers and their resources.
Configure each Migrate Connector server to work with your PTM server.
There is no set limit to the number of Connectors you can register for a PTM server.
Each Migrate Connector instance can register with only one PTM server.
Consider the following deployment guidelines for PlateSpin Migrate Connector:
Each project requires access to at least one Migrate Connector server.
A Migrate Connector services all projects by default
You can optionally configure a Migrate Connector to service a single specified project.
For executing automated migrations and tracking manual migrations using PlateSpin Migrate servers, you must associate one or more Migrate servers with each Connector instance. Each Migrate server is associated with a single Connector. Only the Connector associated with a Migration Server will process its migration events.
You can optionally configure a Migrate Connector to work with a specified project. Create the project in PlateSpin Transformation Manager, then use its Project ID to configure the appropriate Connector instance with the dedicated project assignment. See Configuring a Connector Instance for PTM.
Ensure that your network meets the requirements for discovery, migration, and event management defined in Section 2.2, Network Connectivity and Access Requirements.