[RFE] Support rolling upgrade in Barbican

Bug #1670946 reported by Nam
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Won't Fix

Bug Description

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 (namnh)
description: updated
Nam (namnh)
Changed in barbican:
assignee: nobody → Nam (namnh)
Nam (namnh)
description: updated
description: updated
description: updated
Revision history for this message
Dave McCowan (dave-mccowan) wrote :

@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.openstack.org are two good places to publish your results.

Changed in barbican:
status: New → In Progress
importance: Undecided → High
milestone: none → pike-1
Revision history for this message
Dave McCowan (dave-mccowan) wrote :

@Nam, here are some instructions from @dane-fitcher. https://etherpad.openstack.org/p/tempest-plugin-testing

Revision history for this message
Nam (namnh) wrote :

@Dave, I saw your question on the path set. Thank you for your help

Revision history for this message
Nam (namnh) wrote :

I already tested upgrade from Newton to Ocata. And there are not problems with all commands and tempest test:

The work-flow to test upgrade like below:

Step 1: Install Barbican at Newton release by Devstack

Step 2: Run commands: http://paste.openstack.org/show/603356/

Step 3: Verify with barbican-tempest-plugin

Step 4: Upgrade Barbican to Ocata release

Step 5: Verify commands and barbican-tempest again

=> Result: There are not problems

Revision history for this message
Grzegorz Grasza (xek) wrote :

Closing out bugs created before migration to StoryBoard. Please re-open if you are of the opinion it is still current.

Changed in barbican:
status: In Progress → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.