Open mrickl opened 3 years ago
This is planned.
Bumping for visibility here, would be a good enhancement and bring the feature set alongside many other tools in the space.
Realistically this should be a simple process, no?
Would require that a user have a common user on the nodes. Could have the caveat that it can only move between nodes on the same platform (Linux > Linux, Windows > Windows) Hit migrate Specify where it goes For Linux, via SCP, Windows you might have to get creative It gets moved, relevant instance.jsons get updated, ads' restarted, bing bang boom.
Actually I'm planning on allowing cross-OS migrations in some situations. Linux -> Windows in Container for example.
The actual process of having AMP move instances between targets is non-trivial though in order to do it reliably. It needs to pack the data up, copy it over (via AMPs internal SFTP), verify the checksum, unpack it on the target, reconfigure it in place (the port mappings etc may be different), and verify its configuration before deleting the original.
If amp works as a controller or hybrid with multiple nodes the feature of an instance migrator would not be bad. This allows you to move the server to another node if you have a resource bottleneck on one node.