The existing example persistent volume test framework would benefit from two improvements:
- It relies on statically reserved resources. To more accurately represent real-world use cases, and to remove the dependency on slaves with statically reserved resources, the framework should be updated to dynamically reserve the disk resources that it uses for persistent volumes.
- The framework currently runs quickly and then exits. It would be useful to have a command-line flag that allows the framework lifetime to be specified, so that it could run continuously for a specified length of time, or indefinitely. This would facilitate testing, including the testing of realistic live-upgrade scenarios.