WIP: integration upgrade test
a draft of how we could have an "slapos instance upgrade test case" and use it to test ERP5 upgrade.
The ERP5 upgrade reuse a quick script I had to connect to ERP5 using xmlrpc and run upgrader (this script does not work well, it does not properly wait for upgrader to finish)
Hi @jerome ,
I'm thinking of following approach (which is what ScalabilityTests is actually doing with the only difference that it changes configuration - i.e. number of nodes).
Request and instance (well a SR which is to be build also) using a dedicated SlapOs master account (working for ScalabilityTests)
Using XML-RPC run "live" tests against this instance and save output1
Request NEW SR. Wait to have it build and make sure former instance uses new SR (this should be doable from SlapOs point of view?)
Run "upgrader" scripts against the instance, wait no running activities are pending and run live tests against upgraded instance. Save to output2
Report to Nexedi ERP5 output1 and output2. If same => OK, if not same => FAIL
I guess that we can re-use at least 90% of ScalabilityRunner's code and only need to
create the notion of (inside cluster configuration field) of "initial_software_release", "target_software_release", "name_of_live_test(s)"
new type of "Upgrader Tests"
My proposition is quite draft but it covers imho what would a developer do for a real upgrade ...