You must have root access on the target system in order to complete a migration, as you will need to copy and run a binary file on the target system.
UForge AppCenter migration does not support multi-kernels. When scanning a machine with more than one kernel, only the kernel running will be scanned and imported.
In order to migrate a system, it must meet the following conditions:
- The operating system must be in one of the supported formats (refer to Supported Operating Systems).
Your scan will take longer if not all minor versions of a distribution are install in your UForge AppCenter. For example, if you scan a CentOS 6.8 machine, but your AppCenter has only been populated with packages up to CentOS 6.7, then the AppCenter will use the machine’s yum repo to download the missing packages. As a result, the scan will take longer to complete.
- The image formats must be in supported formats (refer to Supported Machine Image Types)
- Any pre-install or post-install scripts on the system you are about to scan should only use ascii characters. Otherwise UForge AppCenter will return a scan error:
DB Error – invalid characters.
- Custom packages on the live system to be scanned should not contain references to package dependencies as relative path. They should be expressed as absolute paths.
- If custom packages are installed using
--nodepsflag, the scan process will not detect these packages. When running
Re-platform, UForge AppCenter will check for these dependencies. If they are custom packages that are not on the live system, the generation will fail. Therefore, it is recommended to provide a custom repository with all the necessary custom packages. Otherwise, they can be added after the scan to the appliance template in
- For Windows, the partition format must be NTFS
- For Windows, GPT is not supported. Scanned Windows machine has to have MBR.
Currently, UForge is not able to migrate the Yum repository GPG keys. This means that the user will have to accept the repository GPG key when the user installs or updates a package. The user will have to do this only once per repository.
Migrating CentOS 6 to AWS¶
If you plan to migrate a CentOS 6 instance onto AWS with SELinux enabled, you must setup the SELinux context of the public key on the migrated instance. For more detailed information, refer to CentOS 6 Release Note.
Migrating Windows to K5¶
If you plan to migrate a Windows instance onto K5 Fujitsu Public Cloud, you must also uninstall CloudBase-Init (if installed) before scanning.
For more detailed information, refer to official Fujitsu K5 IaaS Documentation.
Migrating Linux to VCenter¶
- If you plan to migrate a Linux instance from a platform using cloud-init (such as OpenStack) to VCenter you must following one of the next proposals:
cloud-init(if installed) before scanning
Re-platform. Once the appliance is imported, remove
cloud-initpackage before generating.
Migrating to Microsoft Azure¶
Currently, to publish to Microsoft Azure platform https://azure.microsoft.com/en-us/ you must do the following before scanning:
- Unless you are migrating from CentOS7+ or Red Hat Enterprise Linux 7+, uninstall NetworkManager (if installed).
- Uninstall the Microsoft Azure agent, i.e. WALinuxAgent and waagent packages (if installed).