Activity log for bug #1670946

Date Who What changed Old value New value Message
2017-03-08 06:20:44 Nam bug added bug
2017-03-08 06:21:09 Nam 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) (tbd) + Test that it works (ocata to pike/master) (tbd) + Develop a option like "online_data_migration" (Ex: Neutron and Cinder [2-3]) + Automatic testing with Grenade + Then, request a tag (assert:supports-upgrade) Here is a etherpad about this tag [4] - Second, after finish adding the tag, we will move to a tag "supports-rolling-upgrade": + Support version in RPC like other project [5] + Oslo version object + 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://review.openstack.org/#/c/432494/2 [3] https://review.openstack.org/#/c/330391 [4] https://etherpad.openstack.org/p/barbican-tracker-pike [5] https://review.openstack.org/#/c/407491 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) (tbd)        + Test that it works (ocata to pike/master) (tbd)        + Develop a option like "online_data_migration" (Ex: Neutron and Cinder [2-3])        + Automatic testing with Grenade        + Then, request a tag (assert:supports-upgrade)        Here is a etherpad about this tag [4] - Second, after finish adding the tag, we will move to a tag "supports-rolling-upgrade":        + Support version in RPC like other project [5]        + Oslo version object        + API multi versioning 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://review.openstack.org/#/c/432494/2 [3] https://review.openstack.org/#/c/330391 [4] https://etherpad.openstack.org/p/barbican-tracker-pike [5] https://review.openstack.org/#/c/407491
2017-03-08 06:56:58 Nam barbican: assignee Nam (namnh)
2017-03-08 07:26:28 Nam 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) (tbd)        + Test that it works (ocata to pike/master) (tbd)        + Develop a option like "online_data_migration" (Ex: Neutron and Cinder [2-3])        + Automatic testing with Grenade        + Then, request a tag (assert:supports-upgrade)        Here is a etherpad about this tag [4] - Second, after finish adding the tag, we will move to a tag "supports-rolling-upgrade":        + Support version in RPC like other project [5]        + Oslo version object        + API multi versioning 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://review.openstack.org/#/c/432494/2 [3] https://review.openstack.org/#/c/330391 [4] https://etherpad.openstack.org/p/barbican-tracker-pike [5] https://review.openstack.org/#/c/407491 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) (tbd)        + Test that it works (ocata to pike/master) (tbd)        + 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 [5]        + Oslo version object + + Develop a option like "online_data_migration" (Ex: Neutron and Cinder [3-4])        + 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/432494/2 [4] https://review.openstack.org/#/c/330391 [5] https://review.openstack.org/#/c/407491
2017-03-08 07:27:33 Nam 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) (tbd)        + Test that it works (ocata to pike/master) (tbd)        + 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 [5]        + Oslo version object + + Develop a option like "online_data_migration" (Ex: Neutron and Cinder [3-4])        + 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/432494/2 [4] https://review.openstack.org/#/c/330391 [5] https://review.openstack.org/#/c/407491 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 [5]        + Oslo version object        + + Develop a option like "online_data_migration" (Ex: Neutron and Cinder [3-4])        + 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/432494/2 [4] https://review.openstack.org/#/c/330391 [5] https://review.openstack.org/#/c/407491
2017-03-08 07:28:52 Nam 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 [5]        + Oslo version object        + + Develop a option like "online_data_migration" (Ex: Neutron and Cinder [3-4])        + 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/432494/2 [4] https://review.openstack.org/#/c/330391 [5] https://review.openstack.org/#/c/407491 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
2017-03-08 14:38:28 Dave McCowan barbican: status New In Progress
2017-03-08 14:38:32 Dave McCowan barbican: importance Undecided High
2017-03-08 14:38:39 Dave McCowan barbican: milestone pike-1
2017-03-14 00:55:13 Cao Xuan Hoang bug added subscriber Cao Xuan Hoang
2017-03-20 04:14:05 Nam bug added subscriber Hieu LE
2018-02-09 04:12:53 Hieu LE removed subscriber Hieu LE
2023-04-25 11:04:28 Grzegorz Grasza barbican: status In Progress Won't Fix