Comment 2 for bug 1388047

Yeah, I think it has to be done per-stack at runtime, based on the content of the keystone catalog, which is not perfect as it doesn't prove the service is running, but it does at least prove it's configured and expected to be available in the environment heat is running - this to me seems the least expensive pre-create check we can do, but open to other ideas :)