Before you deploy a PlateSpin Migrate Connector server, ensure that your environment meets the following requirements and guidelines.
PlateSpin Migrate Connector 2019.2 supports the following components of PlateSpin Migration Factory:
PlateSpin Transformation Manager 2019.2
PlateSpin Migrate Connector 2019.2 is included with this version of PTM.
PlateSpin Migrate 2019.2
PlateSpin Transformation Manager and PlateSpin Migrate Connector require PlateSpin Migrate servers to execute automated migrations and to track external migrations performed on them. 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 2019.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. The software is compatible with any version of SLES 12.
The PlateSpin Migrate Connector RPM file includes the dependent software packages listed in Table 13-1.
Table 13-1 Dependent Software for the PlateSpin Migrate Connector Host Server
|
Prerequisite Software Package |
Version |
|---|---|
|
certifi |
2018.11.29 |
|
connexion |
2.2.0 |
|
cryptography |
2.4.2 |
|
idna |
2.8 |
|
impacket |
0.9.18 |
|
ldap3 |
2.5.1 |
|
lxml |
4.3.0 |
|
mock |
2.0.0 |
|
paramiko |
2.4.2 |
|
pycrypto |
2.6.1 |
|
pypsexec |
0.1.0 |
|
python-dateutil |
2.7.5 |
|
python-ntlm |
1.1.0 |
|
pytz |
2018.9 |
|
pyvmomi |
6.7.1 |
|
requests |
2.21.0 |
|
requests-ntlm |
1.1.0 |
|
scp |
0.13.0 |
|
six |
1.12.0 |
|
smbprotocol |
0.1.1 |
|
stomp.py |
4.1.21 |
|
tzlocal |
1.5.1 |
|
urllib3 |
1.24.1 |
The PlateSpin Migrate Connector 2019.2 installation RPM contains files to upgrade Migrate Connector software as well as its dependent software on your existing Migrate Connector host servers. After the upgrade, you can verify that software versions have been updated or added as described in Table 13-2.
Table 13-2 Upgraded Dependent Software for the PlateSpin Migrate Connector
|
Prerequisite Software Package |
Version Required for PMC 2 |
Version Required for PMC 2019.2 |
|---|---|---|
|
certifi |
2018.1.18 |
2018.11.29 |
|
connexion |
1.3 |
2.2.0 |
|
cryptography |
2.2 |
2.4.2 |
|
idna |
Not used |
2.8 |
|
impacket |
0.9.15 |
0.9.18 |
|
ldap3 |
Not used |
2.5.1 |
|
lxml |
4.2.0 |
4.3.0 |
|
mock |
2.0.0 |
2.0.0 |
|
paramiko |
2.4.1 |
2.4.2 |
|
pycrypto |
2.6.1 |
2.6.1 |
|
pypsexec |
Not used |
0.1.0 |
|
pysmb |
1.1.22 |
Not used |
|
python-dateutil |
2.7.0 |
2.7.5 |
|
python-ntlm |
1.1.0 |
1.1.0 |
|
pytz |
2018.3 |
2018.9 |
|
pyvmomi |
6.5 |
6.7.1 |
|
requests |
2.18.4 |
2.21.0 |
|
requests-ntlm |
1.1.0 |
1.1.0 |
|
scp |
0.10.2 |
0.13.0 |
|
six |
1.11.0 |
1.12.0 |
|
smbprotocol |
Not used |
0.1.1 |
|
stomp.py |
4.1.20 |
4.1.21 |
|
tzlocal |
1.5.1 |
1.5.1 |
|
urllib |
3.1.22 |
Not used |
|
urllib3 |
Not used |
1.24.1 |
Consider the following guidelines as you deploy PlateSpin Migrate Connectors in your migration environment:
For source workload discovery, 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 target platform discovery in VMware environments on premises or in VMware Cloud (VMC) on Amazon Web Services, deploy a Migrate Connector instance in each target network to enable discovery of VMware vCenter Server platforms and their platform 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.
Each Migrate Connector instance can be available to all projects (the default), or it can be dedicated to a single project.
Associate each PlateSpin Migrate Connector instance with one or more PlateSpin Migrate servers.
Assign each Migration Server resource to only one Connector.
It is not supported to assign a PlateSpin Migrate server to multiple Migrate Connectors in the same project or in different projects.
Consider the following guidelines as you configure PlateSpin Migrate Connectors in your migration environment:
Each project requires access to at least one Migrate Connector server.
A Migrate Connector provides services for all projects by default.
(Optional) You can configure a Migrate Connector to provide services to a single project.
(Automation and tracking) Associate each PlateSpin Migrate server with one of the Connectors that is available in your project. Only the Connector associated with a Migration Server will process its migration events.
(Automation and tracking) Associate one or more PlateSpin Migrate servers with each Migrate Connector instance.
For automated migrations, each Connector balances workload migrations across its assigned Migrate servers.
For tracked migrations, each Connector collects migration information across its assigned Migrate servers.
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.