vishvananda at gmail
May 9, 2012, 5:13 PM
Post #2 of 3
No this is mostly just legacy stuff that was never refactored.
Re: questions on the dynamic loading of virt drivers in nova
[In reply to]
On May 9, 2012 3:33 PM, "Sean Dague" <sdague [at] linux> wrote:
> I'm familiarizing myself with the nova code and trying to reconcile that
> while there is dynamic class based loading in ComputeManager using
> import_utils in __init__() there is also a defaulting to the
> nova.virt.connection.get_**connection function.
> That's actually got a big if / else statement of string literals of known
> virt drivers, and then loads specific virt drivers from there.
> Is there a reason for both approaches? Can we refactor to a point where we
> don't need need of a common file with driver specific imports and string
> literals? Is there a reason not to?
> Sean Dague
> IBM Linux Technology Center
> email: sdague [at] linux
> alt-email: sldague [at] us
> Mailing list: https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
> Post to : openstack [at] lists
> Unsubscribe : https://launchpad.net/~**openstack<https://launchpad.net/~openstack>
> More help : https://help.launchpad.net/**ListHelp<https://help.launchpad.net/ListHelp>