Skip to content

Add support for additional disks to incus-migrate #1905

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
1 task done
stgraber opened this issue Apr 7, 2025 · 0 comments
Open
1 task done

Add support for additional disks to incus-migrate #1905

stgraber opened this issue Apr 7, 2025 · 0 comments
Assignees
Labels
Blocked Waiting on an external task Easy Good for new contributors
Milestone

Comments

@stgraber
Copy link
Member

stgraber commented Apr 7, 2025

Is there an existing issue for this?

  • There is no existing issue for this feature

What are you currently unable to do

As a follow-up to #1877, we should then allow adding additional disks to a container or VM as part of their migration. When doing so, those extra disks would first be transferred as custom volumes before the instance itself is transferred and the disks connected.

For containers, we'll only allow extra file system custom volumes (path).
For VMs, we'll support either file system or block (including qcow2 and vmdk as supported for the root volume).

What do you think would need to be added

No response

@stgraber stgraber added Easy Good for new contributors Blocked Waiting on an external task labels Apr 7, 2025
@stgraber stgraber added this to the later milestone Apr 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Blocked Waiting on an external task Easy Good for new contributors
Development

No branches or pull requests

2 participants