Changing disk UUID after disk replacing in xcp-ng with Xen Orchestra
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 1.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 32
Description
##### ISSUE TYPE
* Improvement Request
##### CLOUDSTACK VERSION
~~~
Any
~~~
##### SUMMARY
Hello. I use CloudStack with XCP-NG and I am in search of the best backup solution.
All software, including Xen Orchestra, can restore a backup as new VM with a new disk UUID. After that I detach disk from original VM and attach the recovered disk. VM is working fine, but CloudStack cannot manage the disk due to the new disk UUID.
If I replace disk UUID in CloudStack databases, disk management will be performed normally
Example:
~~~
update volumes SET path="24c34f4d-35b3-400a-92e3-c27ba154aabf" where id=2283;
~~~
Maybe in new version of cloudstack you can add function of manually or automatically changing disk UUID from Cloudstack?
Or import VM from XCP-NG function.
Contributor guide
Research direction
The issue names no source files, tests, or entry points. Start by reviewing the 15-comment thread and the proposed volume database update, then clarify whether the intended scope is manual UUID changes, automatic replacement handling, or XCP-NG VM import. Done should be defined as a supported workflow that lets CloudStack manage the recovered disk safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- cloud, databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100