A local instance of PlateSpin Migrate Connector is automatically installed on the PlateSpin Transformation Manager Appliance. You can use this Connector instance for discovery actions in the same network. You must deploy remote instances of Migrate Connector to support discovery actions in other networks.
Before you deploy PlateSpin Migrate Connector, ensure that your environment meets the following requirements and guidelines.
Section 13.2.1, Supported PlateSpin Migration Factory Components
Section 13.2.2, Supported Connector Host OS and Dependent Software
Section 13.2.3, Deployment Guidelines for PlateSpin Migrate Connectors
Section 13.2.6, Dedicated User Account for Each Connector Instance
Section 13.2.7, Network Connectivity and Access Requirements
PlateSpin Migrate Connector 2019.5 supports the following components of PlateSpin Migration Factory:
PlateSpin Transformation Manager 2019.5
PlateSpin Migrate Connector 2019.5 is included with PlateSpin Transformation Manager 2019.5.
PlateSpin Migrate 2019.5
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.5 is not backwards compatible with previous release versions of PlateSpin Transformation Manager and PlateSpin Migrate.
PlateSpin Migrate Connector supports installation on SUSE Linux Enterprise Server (SLES) 15 servers.
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 |
|---|---|
|
asn1crypto |
0.24.0 |
|
bcrypt |
3.1.6 |
|
certifi |
2019.3.9 |
|
cffi |
1.12.3 |
|
chardet |
3.0.4 |
|
Click |
7.0 |
|
clickclick |
1.2.2 |
|
connexion |
2.2.0 |
|
cryptography |
2.6.1 |
|
dnspython |
1.16.0 |
|
docopt |
0.6.2 |
|
Flask |
1.0.2 |
|
future |
0.17.1 |
|
idna |
2.8 |
|
impacket |
0.9.20.dev0 |
|
inflection |
0.3.1 |
|
itsdangerous |
1.1.0 |
|
Jinja2 |
2.10.1 |
|
jsonschema |
2.6.0 |
|
ldap3 |
2.5.1 |
|
ldapdomaindump |
0.9.1 |
|
lxml |
4.3.3 |
|
MarkupSafe |
1.1.1 |
|
mock |
2.0.0 |
|
netifaces |
0.10.9 |
|
ntlm-auth |
1.3.0 |
|
openapi-spec-validator |
0.2.6 |
|
ordereddict |
1.1 |
|
paramiko |
2.4.2 |
|
pathlib |
1.0.1 |
|
pbr |
5.2.0 |
|
pyasn1 |
0.4.5 |
|
pycparser |
2.19 |
|
pycryptodomex |
3.8.1 |
|
PyNaCl |
1.3.0 |
|
pyOpenSSL |
19.0.0 |
|
pypsexec |
0.1.0 |
|
python-dateutil |
2.8.0 |
|
python-ntlm |
1.1.0 |
|
pytz |
2019.1 |
|
pyvmomi |
6.7.1.2019.12 |
|
PyYAML |
5.1 |
|
requests |
2.21.0 |
|
requests-ntlm |
1.1.0 |
|
scp |
0.13.2 |
|
six |
1.12.0 |
|
smbprotocol |
0.1.1 |
|
stomp.py |
4.1.22 |
|
tzlocal |
1.5.1 |
|
urllib3 |
1.24.3 |
|
Werkzeug |
0.15.2 |
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 instance 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.
For each Connector instance, you must specify the credentials of a PTM Server user account. The account is required for communications with the PTM Server and to perform actions on it. We recommend that you create a unique user identity for the Connector instance instead of using the credentials of a PTM user. Having a unique Connector user for each Migrate Connector helps you more easily distinguish actions performed by the Connector instance in logs and transformation histories.
The default instance of Migrate Connector on the PTM Appliance uses the credentials of the PTM System Administrator user to perform actions. You can replace these credentials with the email address of a PTM System user account on your PTM Server that has been assigned at least a Project Architect role at the Project level. Create a dedicated user account for each Connector instance with permissions appropriate for its assigned project.
Ensure that your network meets the requirements for discovery, migration, and event management defined in Section 2.2, Network Connectivity and Access Requirements.