3 Commits

Author	SHA1	Message	Date
Abhishek Kumar	35a7438033	test: fix failure in test_06_purge_expunged_vm_background_task (#10501) ... Failures seen in https://github.com/apache/cloudstack/pull/10006#issuecomment-2691067265 and others. With https://github.com/apache/cloudstack/pull/9773, the response of listManagementServers API has been changed. serviceip has been renamed to ipaddress. This was causing not all MS getting restarted and purge b/g task not being able to run. The code handling API response in the test has been updated. Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>	2025-03-06 09:25:22 +05:30
Abhishek Kumar	cd8442a42b	test: improve purge expunged resources b/g task testcase (#9426) ... * test: improve purge expunged resources b/g task testcase Failures were seen for during purging of expunged resources via bacground task during different test runs. This PR tries to make sure b/g task execution is not skipped after MS restrat in a multi-MS environment. It also updates expunged.resources.purge.interval to allow running task again in 60s. Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com> * new string formatting --------- Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>	2024-07-29 15:49:45 +05:30
Abhishek Kumar	3e6900ac1a	api,server: purge expunged resources (#8999) ... This PR introduces the functionality of purging removed DB entries for CloudStack entities (currently only for VirtualMachine). There would be three mechanisms for purging removed resources: Background task - CloudStack will run a background task which runs at a defined interval. Other parameters for this task can be controlled with new global settings. API - New admin-only API purgeExpungedResources. It will allow passing the following parameters - resourcetype, batchsize, startdate, enddate. Currently, API is not supported in the UI. Config for service offering. Service offerings can be created with purgeresources parameter which would allow purging resources immediately on expunge. Following new global settings have been added: expunged.resources.purge.enabled: Default: false. Whether to run a background task to purge the expunged resources expunged.resources.purge.resources: Default: (empty). A comma-separated list of resource types that will be considered by the background task to purge the expunged resources. Currently only VirtualMachine is supported. An empty "value will result in considering all resource types for purging expunged.resources.purge.interval: Default: 86400. Interval (in seconds) for the background task to purge the expunged resources expunged.resources.purge.delay: Default: 300. Initial delay (in seconds) to start the background task to purge the expunged resources task. expunged.resources.purge.batch.size: Default: 50. Batch size to be used during expunged resources purging. expunged.resources.purge.start.time: Default: (empty). Start time to be used by the background task to purge the expunged resources. Use format yyyy-MM-dd or yyyy-MM-dd HH:mm:ss. expunged.resources.purge.keep.past.days: Default: 30. The number of days in the past from the execution time of the background task to purge the expunged resources for which the expunged resources must not be purged. To enable purging expunged resource till the execution of the background task, set the value to zero. expunged.resource.purge.job.delay: Default: 180. Delay (in seconds) to execute the purging of an expunged resource initiated by the configuration in the offering. Minimum value should be 180 seconds and if a lower value is set then the minimum value will be used. Documentation PR: apache/cloudstack-documentation#397 Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com> Co-authored-by: Wei Zhou <weizhou@apache.org> Co-authored-by: Suresh Kumar Anaparti <sureshkumar.anaparti@gmail.com>	2024-06-20 11:34:44 +05:30