abh1sar opened a new pull request, #10140: URL: https://github.com/apache/cloudstack/pull/10140
Doc PR: https://github.com/apache/cloudstack-documentation/pull/474 ### Description This PR adds the ability to create a new Instance from a VM backup for Dummy, NAS and Veeam backup Providers. This will still work if the original Instance used to create the backup was expunged. New API - createVmFromBackup extends baseDeployVIrtualMachine - new arguments : backupId, preserveip - User can just specify the backupId and a new instance will be created by getting the VM and volumes' configuration stored in backup_details table. - User can also choose to configure the details themselves using the parameters present in deployVIrtualMachine cmd - If the original instance from which the backup was taken is deleted, user can choose to reuse the same IP addresses if they are available using the `preserveip` argument. UI - New action button in backups list view - 'Create Instance from Backup' - User can choose to directly create the VM or configure VM parameters before creating it. DB changes - New backup_details table - to store vm config data such as serviceOfferingUuid, networkUuids, ipAddresses - to store volumes config data such as diskOfferingUuids, size, miniops and maxiops for custom disk offerings. Other Changes - Added new parameter `Map datadisksdetails` to deployVirtualMachine api to create multiple data volumes at the time of instance creation. Plugins related changes - NAS and Veeam plugin changes to restore backup to a new VM and miscellaneous fixes around handling backups of expunged Instances. #### Other Miscellaneous changes 1. Add Name and description column to backup 2. Show Interval type in UI for backups 3. Support cephFS for NAS backup provider 4. Add Backup Storage Capacity Tracking and Alerts Infrastructure Backup Storage (used and available) is shown on the Capacity dashboard and tracks the alerts if supported by the plugin (Currently only NAS BnR plugin supports it) 5. Add Object Storage Capacity Tracking and Alerts Infrastructure Object Storage (allocated and available) is shown on the Capacity dashboard and tracked for alerts. <!--- Describe your changes in DETAIL - And how has behaviour functionally changed. --> <!-- For new features, provide link to FS, dev ML discussion etc. --> <!-- In case of bug fix, the expected and actual behaviours, steps to reproduce. --> <!-- When "Fixes: #<id>" is specified, the issue/PR will automatically be closed when this PR gets merged --> <!-- For addressing multiple issues/PRs, use multiple "Fixes: #<id>" --> <!-- Fixes: # --> <!--- ******************************************************************************* --> <!--- NOTE: AUTOMATION USES THE DESCRIPTIONS TO SET LABELS AND PRODUCE DOCUMENTATION. --> <!--- PLEASE PUT AN 'X' in only **ONE** box --> <!--- ******************************************************************************* --> ### Types of changes - [ ] Breaking change (fix or feature that would cause existing functionality to change) - [x] New feature (non-breaking change which adds functionality) - [ ] Bug fix (non-breaking change which fixes an issue) - [ ] Enhancement (improves an existing feature and functionality) - [ ] Cleanup (Code refactoring and cleanup, that may add test cases) - [ ] build/CI - [ ] test (unit or integration test code) ### Feature/Enhancement Scale or Bug Severity #### Feature/Enhancement Scale - [ ] Major - [ ] Minor #### Bug Severity - [ ] BLOCKER - [ ] Critical - [ ] Major - [ ] Minor - [ ] Trivial ### Screenshots (if appropriate): <img width="673" alt="Screenshot 2025-01-14 at 2 17 16 PM" src="https://github.com/user-attachments/assets/317c446c-4bdc-4e04-93a9-8da1dcc6c8c6" /> <img width="938" alt="Screenshot 2025-01-14 at 2 17 35 PM" src="https://github.com/user-attachments/assets/8fe2761d-e83b-4a78-ab4c-6d121a5978e2" /> ### How Has This Been Tested? <!-- Please describe in detail how you tested your changes. --> <!-- Include details of your testing environment, and the tests you ran to --> #### How did you try to break this feature and the system with this change? <!-- see how your change affects other areas of the code, etc. --> <!-- Please read the [CONTRIBUTING](https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md) document --> -- 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: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org