yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #17414
[Bug 1214683] Re: RPC compatibility required across minor RPC changes but not tested
We now test this with the partial-ncpu job.
** Changed in: nova
Status: Triaged => Fix Released
** Changed in: grenade
Status: New => Fix Released
** No longer affects: openstack-ci
** Changed in: devstack
Status: New => Fix Released
** Changed in: nova
Assignee: (unassigned) => Joe Gordon (jogo)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1214683
Title:
RPC compatibility required across minor RPC changes but not tested
Status in devstack - openstack dev environments:
Fix Released
Status in Grenade - OpenStack upgrade testing:
Fix Released
Status in OpenStack Compute (Nova):
Fix Released
Bug 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. 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.
To manage notifications about this bug go to:
https://bugs.launchpad.net/devstack/+bug/1214683/+subscriptions