So most of the compute providers/APIs in core are now async-free on master - the only exceptions I can think of off the top of my head are the vcloud ones, the old rackspace ones, and the nova ones. The vcloud ones I'll get around to sometime in the next couple weeks - that's just a matter of gutting them out. But the rackspace/nova ones are a lot hairier.
When I tried de-asyncing the cloudservers API, I found I had to de-async the keystone v1 API as well - and that can't actually go live until cloudfiles is able to de-async too. I haven't verified, but I'm pretty sure it's the same situation for nova/keystone/swift. And cloudfiles/swift can't de-async until blobstore itself supports non-async. So this brings up an important question. We're about 6 weeks from the target date for 1.7.0 - can we actually get the blobstore stuff de-asynced by then? Or are we going to need to push the de-async completion back 'til 1.7.1/2/3/whatever? How high a priority should this be? A.
