-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14/11/14 14:40, Dan Smith wrote: >> I don't think it's a problem. It puts a practical limit on the >> scope of an 'api call' which can be covered by a single database >> transaction though, because it would be difficult to arrange for >> 2 RPC calls to both use the same DB transaction on the remote >> end. I think we agree on this. > > Sure, but since RPC calls can be queued for *minutes* this is > probably not a realistic problem, right?
More violent agreement ;) I think scoping this to just conductor is appropriate and useful. Compare and swap at the object level would be a useful mechanism for safety across multiple rpc calls. Matt - -- Matthew Booth Red Hat Engineering, Virtualisation Team Phone: +442070094448 (UK) GPG ID: D33C3490 GPG FPR: 3733 612D 2D05 5458 8A8A 1600 3441 EA19 D33C 3490 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlRmJiQACgkQNEHqGdM8NJASFgCdFsz8Bm9LcIqTBf+uZSe0/hmE LG0An2D9L3vyI8QSAUxNDj3fpfSFt0tx =32fN -----END PGP SIGNATURE----- _______________________________________________ OpenStack-dev mailing list OpenStackemail@example.com http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev