ShadowJonathan commented on issue #12224: URL: https://github.com/apache/cloudstack/issues/12224#issuecomment-3638950407
@shwstppr indeed, one of the biggest worries on our end is that in whatever state the proxmox VM exists/existed, and with whatever manual additions or changes it has from a "norm" that cloudstack establishes, that it is hard to import them in their current state, or that it is hard to capture all the "quirks", or formalise all disks/networks position, state, offering, and more. i'm not sure how or if this can be solved, but it's one thing to look out for from my perspective in that regard, either; 1. instances need to be "pre-steamed" (manually) before they become eligible for import 2. instances get "steamed" *during* an import, with exact steps and changes (/ diff) of how the VM will be altered, so that system administrators can clear that -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
