Doni7722 commented on issue #3341: URL: https://github.com/apache/cloudstack/issues/3341#issuecomment-939564432
Hi @rhtyd & @DaanHoogland sorry for the (very) late response... I had a look at the deploy-as-is feature and I can tell you that it works! However I would still like to discuss the current "solution" of this new features as it does not cover all issues: 1. with the deploy-as-is feature CloudStack does not respect the kind of the disks but creates all disks inside the OVA as root disks (root-123-0, root-123-1, root-123-2, etc.) which is wrong as those are data disks and not root disks. I was still not able to finish all tests but this may could lead to other problems as well. 2. root disks are always mapped to the service offering in the matter of disk offering. So if you define your root disk to run on a good storage tier but would like to have you data disks on fast/better storage tier you will not be able as root-disks can not change storage tiers (at least not by users). 3. I was unable to create a disk backup (snapshot) from a single disk. So looks like this is broken if there are multiple root-disks. A normal VM snapshot was successful. 4. deploy-as-is did not map the OS correctly (however that's not a big thing as it can be manually corrected) As I already said the deploy-as-is method does work and all data disks were assigned correctly and were read- & writable. It does come with some cons however were I think that the biggest would be that we are unable to assign a different disk offering or storage tiers to those data-disks as this would be the need for so many use cases (DB data disks, Archive data-disks, etc.). This was not the case under https://github.com/apache/cloudstack/pull/2146 as here we could assign the correct storage tier but were just not flexible for the disk size. -- 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]
