CLOUDSTACK-8612 [VMware] Make vCenter session timeout configurable for volume snapshot

[sureshanaparti]

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)

[VMware] Make vCenter session timeout configurable for volume snapshot

• Split the existing vCenter session timeout configuration into two configurations to ensure that a high timeout value set for snapshot backup operation and will not affect vCenter connections made for any other operations besides volume snapshot.

• To tune timeout value for CS's session vCenter during snapshot backup operation
  'vmware.snapshot.backup.session.timeout' (new; default: 20 minutes)
  For all other operations - 'vmware.vcenter.session.timeout' (existing; default: 20 minutes)

• There is a timeout for async-jobs that ensures that any job that has been in process for too long is cancelled. This timeout is configurable using a global configuration ‘job.cancel.threshold.minutes’ and it defaults to 1 hour. For large volumes, even though users configure other snapshot timeout values (‘vmware.snapshot.backup.session.timeout’ and ‘backup.snapshot.wait‘) to a very high value, the snapshot operation will still fail because the job will be cancelled in 1 hour.

• A new configuration parameter 'volume.snapshot.job.cancel.threshold' has been introduced that will allow admins to separate out the job cancellation timeout for ‘volume snapshot’ jobs from other vm work jobs.

This closes #562

[sureshanaparti]

@borisstoyanov Can you please run vmware tests on this PR.

[sureshanaparti]

@sateesh-chodapuneedi @rhtyd Please review the code changes

[sateesh-chodapuneedi]

@sureshanaparti Can you please resolve the conflicts and rebase?

[rohityadavcloud]

@sureshanaparti looks like good feature, can you rebase, fix conflicts, move schema change to 4.10->4.11 path?

[DaanHoogland]

ping @rhtyd do you know if this is still an issue?

[DaanHoogland]

ping all. I will close this one if no activity before 4.15

[rohityadavcloud]

Hi, the PR got auto-closed due to no known source repository or some other Github-specific issue during the recent renaming of the default branch to main. If you wish kindly submit a new PR.