Overview

Migration Agents are divided into two types: custom and native. The latter type is developed by Parallels Operations Automation. The agent package consists of two parts: the Tarball with all agents’ files named “agent.tar” and the manifest file with meta-info about the agent named “agent.manifest”.

When the agent is being registered in the Migration Manager, the following actions are performed:

1. Migration Manager looks for agents’ files (the Tarball and manifest) in the user-specified directory.
2. Migration Manager parses the agent's manifest, validates it and stores info about the agent into DB.

In case of error on any registration step, the whole transaction is safely rolled back.

Unlike native agents the custom agents are not distributed in PPM packages. That’s why they cannot be deployed using POA package manager. To register the custom agent, find instructions in the Appendix F (Registering Custom Migration Agent in POA).