0a7f1c7914
Current cleanup mechanism is awful. It's hardcoded, without repeat on failures, contains a lot of mistakes, in some places it is too fast (in case of deletion of VMs) in other to slow (like deletion of users). As well there is mix of cleanup mechanism and resource cleanup mechanism. To resolve these all issues this patch introcude a cleanup engine that resolves all issues above. It's resource based, so to add new resouce you should just a make subclass of base.Resource and probably override some of methods like (list, delete, is_deleted) and that's all. All complexity of managing: 0) waiting until async deletion is finished 1) repeat on failure logic 2) greaceful failure handling 3) parallelization 4) plugin support Is hidden deep inside cleanup engine + bonus we are able to specify now single resource (without clenaping whole service) PART 3: ------- *) Refactor all contexts cleanups method to use new generic cleanup engine insted of cleanup.utils *) Remove obsolate cleanup.utils *) Fix all tests bp benchmark-context-cleanup-refactor Change-Id: I70557e6ebb56bbe565792d9ee854d3e78428a881 |
||
|---|---|---|
| .. | ||
| comparing_results_of_2_tasks.rst | ||
| distributed_load_generation.rst | ||
| historical_performance_data.rst | ||
| multi_scenarios_load_gen.rst | ||
| persistence_benchmark_env.rst | ||
| production_ready_cleanup.rst | ||
| README.rst | ||
Feature requests
To request a new feature you should create a document similar to other feature requests. And contribute it to this directory using next instruction.
If you don't have time to contribute via gerrit, please contact Boris Pavlovic (boris@pavlovic.me)