Comment 2 for bug 1362812

Oh - and I suspect this autodetection will fail entirely for TripleO even once thats fixed, because keystone will initially be empty, and then will get populated.

So we probably need to set the config option to match our deployment - but one-time autodetection like this seems like a bad idea IMNSHO.

Likewise, when dealing with federated clouds, won't a single global value for 'networking impl' be problematic?