(KBOSS) Add synchronous backup compression flag

[JoaoJandre]

Description

Currently, the backup compression process is always performed asynchronously; the existing backup is compressed into a new file, which then replaces the original. However, when using immutable storage, this behavior increases storage usage because the original backup file cannot be deleted.

To address this, the compress_async flag, defaulting to true, has been added to backup offerings. The default setting maintains the current behavior. When the flag is set to false, compression occurs during backup creation, resulting in only a single file copy. However, enabling synchronous backup compression slows down the backup creation process and makes it prone to timeouts unless the timeout settings are adjusted accordingly.

It is important to note that the flag only applies to backup offerings that have the compress flag set to true.

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• 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):

How Has This Been Tested?

Test description

1. I created a new backup offering with compressasync = false, and another without specifying compressasync.
2. I created the "sync" and "async" VMs and assigned the respective offerings to each VM.
3. I created backups using each of the VMs. I observed that the backups created with the "async" VM maintained the previous behavior, whereas the backups created with the "sync" VM were compressed during creation.

[codecov]

Codecov Report

❌ Patch coverage is 10.52632% with 68 lines in your changes missing coverage. Please review.
✅ Project coverage is 20.39%. Comparing base (d3f0700) to head (cb1bb88).

Files with missing lines	Patch %	Lines
...ache/cloudstack/backup/TakeKbossBackupCommand.java	4.00%	24 Missing ⚠️
...java/org/apache/cloudstack/utils/qemu/QemuImg.java	0.00%	17 Missing ⚠️
.../apache/cloudstack/backup/KbossBackupProvider.java	15.78%	14 Missing and 2 partials ⚠️
.../wrapper/LibvirtTakeKbossBackupCommandWrapper.java	33.33%	6 Missing ⚠️
...i/command/user/backup/CreateBackupOfferingCmd.java	0.00%	3 Missing ⚠️
...e/wrapper/LibvirtCompressBackupCommandWrapper.java	0.00%	2 Missing ⚠️

Additional details and impacted files

@@             Coverage Diff              @@
##               main   #13901      +/-   ##
============================================
- Coverage     20.39%   20.39%   -0.01%     
+ Complexity    21283    21280       -3     
============================================
  Files          6481     6481              
  Lines        588040   588091      +51     
  Branches      72021    72027       +6     
============================================
- Hits         119957   119950       -7     
- Misses       455052   455108      +56     
- Partials      13031    13033       +2     

Flag	Coverage Δ
uitests	3.70% <ø> (ø)
unittests	21.69% <10.52%> (-0.01%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.