| 2013-08-21 02:41:15 |
Joe Gordon |
bug |
|
|
added bug |
| 2013-08-21 02:42:41 |
Joe Gordon |
bug task added |
|
openstack-ci |
|
| 2013-08-21 02:43:33 |
Joe Gordon |
bug task added |
|
grenade |
|
| 2013-08-21 02:43:54 |
Joe Gordon |
bug task added |
|
devstack |
|
| 2013-08-21 02:44:45 |
Joe Gordon |
description |
We require minor changes to any RPCAPI to be backwards compatible (http://docs.openstack.org/developer/nova/api/nova.rpc.dispatcher.html) to help make rolling upgrades possible ( for example to allow a grizzly scheduler talk to a havana compute), but we have no testing mechanism in place to make sure this works. Since this kind of backwards compatibility is tricky and we have no testing for it there is a very very small probability that it works at all.
A test for this would require setting up a devstack environment with two copies of the nova source tree and running some services from the latest patch and some from the oldest nova version that supports the same major RPCAPI version.
but this won't be possible until we have db objects, as the DB schema are different. So until then the test can compare to the oldest nova commit that has the same schema. |
We require minor changes to any RPCAPI to be backwards compatible (http://docs.openstack.org/developer/nova/api/nova.rpc.dispatcher.html) to help make rolling upgrades possible ( for example to allow a grizzly scheduler talk to a havana compute), but we have no testing mechanism in place to make sure this works. Since this kind of backwards compatibility is tricky and we have no testing for it there is a very very small probability that it works at all.
A test for this would require setting up a devstack environment with two copies of the nova source tree and running some services from the latest patch and some from the oldest nova version that supports the same major RPCAPI version.
but this won't be possible until we have db objects, as the DB schema would be different. So until then, the test can compare to the oldest nova commit that has the same schema. |
|
| 2013-08-21 03:01:53 |
Joe Gordon |
description |
We require minor changes to any RPCAPI to be backwards compatible (http://docs.openstack.org/developer/nova/api/nova.rpc.dispatcher.html) to help make rolling upgrades possible ( for example to allow a grizzly scheduler talk to a havana compute), but we have no testing mechanism in place to make sure this works. Since this kind of backwards compatibility is tricky and we have no testing for it there is a very very small probability that it works at all.
A test for this would require setting up a devstack environment with two copies of the nova source tree and running some services from the latest patch and some from the oldest nova version that supports the same major RPCAPI version.
but this won't be possible until we have db objects, as the DB schema would be different. So until then, the test can compare to the oldest nova commit that has the same schema. |
We require minor changes to any RPCAPI to be backwards compatible (http://docs.openstack.org/developer/nova/api/nova.rpc.dispatcher.html) to help make rolling upgrades possible ( for example to allow a grizzly scheduler talk to a havana compute), but we have no testing mechanism in place to make sure this works. Since this kind of backwards compatibility is tricky and we have no testing for it there is a very very small probability that it works at all.
A test for this would require setting up a devstack environment with two copies of the nova source tree and running some services from the latest patch and some from the oldest nova version that supports the same major RPCAPI version.
But this won't be possible until we have db objects, as the DB schema would be different. So until then, the test can compare to the oldest nova commit that has the same schema (and RPCAPI major version).
Another option is to test against HEAD^ and test the continuous deploy case, where each patch is pushed out one by one. |
|
| 2013-08-26 21:14:12 |
Joe Gordon |
openstack-ci: assignee |
|
Joe Gordon (jogo) |
|
| 2013-08-26 21:14:16 |
Joe Gordon |
devstack: assignee |
|
Joe Gordon (jogo) |
|
| 2013-09-09 15:16:12 |
Russell Bryant |
tags |
|
testing |
|
| 2013-09-10 18:38:31 |
James E. Blair |
openstack-ci: milestone |
|
havana |
|
| 2013-09-10 18:38:36 |
James E. Blair |
openstack-ci: status |
New |
Triaged |
|
| 2013-09-10 18:38:46 |
James E. Blair |
openstack-ci: importance |
Undecided |
High |
|
| 2013-09-17 17:56:33 |
Dan Smith |
nova: status |
New |
Triaged |
|
| 2013-10-22 17:32:54 |
Clark Boylan |
openstack-ci: milestone |
havana |
icehouse |
|
| 2013-10-24 11:52:41 |
Joe Gordon |
description |
We require minor changes to any RPCAPI to be backwards compatible (http://docs.openstack.org/developer/nova/api/nova.rpc.dispatcher.html) to help make rolling upgrades possible ( for example to allow a grizzly scheduler talk to a havana compute), but we have no testing mechanism in place to make sure this works. Since this kind of backwards compatibility is tricky and we have no testing for it there is a very very small probability that it works at all.
A test for this would require setting up a devstack environment with two copies of the nova source tree and running some services from the latest patch and some from the oldest nova version that supports the same major RPCAPI version.
But this won't be possible until we have db objects, as the DB schema would be different. So until then, the test can compare to the oldest nova commit that has the same schema (and RPCAPI major version).
Another option is to test against HEAD^ and test the continuous deploy case, where each patch is pushed out one by one. |
We require minor changes to any RPCAPI to be backwards compatible (http://docs.openstack.org/developer/nova/api/nova.rpc.dispatcher.html) to help make rolling upgrades possible ( for example to allow a grizzly scheduler talk to a havana compute), but we have no testing mechanism in place to make sure this works. Since this kind of backwards compatibility is tricky and we have no testing for it there is a very very small probability that it works at all.
A test for this would require setting up a devstack environment with two copies of the nova source tree and running some services from the latest patch and some from the oldest nova version that supports the same major RPCAPI version. Although to start with perhaps we should just test the most recent release versus trunk.
Another option is to test against HEAD^ and test the continuous deploy case, where each patch is pushed out one by one. |
|
| 2013-10-24 11:53:48 |
Joe Gordon |
devstack: assignee |
Joe Gordon (jogo) |
|
|
| 2013-10-24 11:53:54 |
Joe Gordon |
openstack-ci: assignee |
Joe Gordon (jogo) |
|
|
| 2014-02-08 00:42:01 |
Joe Gordon |
grenade: assignee |
|
Joe Gordon (jogo) |
|
| 2014-02-08 00:42:07 |
Joe Gordon |
openstack-ci: assignee |
|
Joe Gordon (jogo) |
|
| 2014-02-08 00:42:11 |
Joe Gordon |
devstack: assignee |
|
Joe Gordon (jogo) |
|
| 2014-07-18 14:50:56 |
Joe Gordon |
nova: status |
Triaged |
Fix Released |
|
| 2014-07-18 14:51:04 |
Joe Gordon |
grenade: status |
New |
Fix Released |
|
| 2014-07-18 14:51:11 |
Joe Gordon |
bug task deleted |
openstack-ci |
|
|
| 2014-07-18 14:51:27 |
Joe Gordon |
devstack: status |
New |
Fix Released |
|
| 2014-07-18 14:51:44 |
Joe Gordon |
nova: assignee |
|
Joe Gordon (jogo) |
|
