In order to support the rolling upgrade feature in Barbican, there are some items that we need to do:
- First, we have to have a tag "assert:supports-upgrade" [1]:
+ Test that it works (newton to ocata)
+ Test that it works (ocata to pike/master)
+ Automatic testing with Grenade
+ Then, request a tag (assert:supports-upgrade)
Here is a etherpad about this tag [2]
- Second, after finish adding the tag, we will move to a tag "supports-rolling-upgrade":
+ Support version in RPC like other project [3]
+ Oslo version object
+ + Develop a option like "online_data_migration" (Ex: Neutron and Cinder [4-5])
+ API multi versioning
+ Graceful service shutdown
I appreciate if receiving your comment to discuss about these items to support upgrade.
[1] https://governance.openstack.org/tc/reference/tags/assert_supports-upgrade.html#assert-supports-upgrade
[2] https://etherpad.openstack.org/p/barbican-tracker-pike
[3] https://review.openstack.org/#/c/407491
[4] https://review.openstack.org/#/c/432494/2
[5] https://review.openstack.org/#/c/330391
@Nam, thank you very much for taking on this important feature.
I don't think it's necessary to save test artifacts of upgrade testing. Documentation of the steps to do a successful upgrade and automation to run an upgrade test in the gate are the important deliverables. If you want to save some artifacts, paste.openstack.org or etherpad.