Select an authz module using setuptools' entry points mechainsm. Instead of having each authz package install an invirt.authz module, have them install modules under their own namespace. In their setup.py, they should indicate that their authz module provides a unique name within the invirt.authz entry point group. The new invirt.authz module (part of invirt-base) then gets a name from the configuration and uses that to find the module. svn path=/trunk/packages/xvm-authz-locker/; revision=2989
Have authz providers use an invirt.authz module. xvm-authz-locker now includes an invirt.authz module instead of xvm.authz.locker. All authz providers conflict with each other, and provide invirt-authz. svn path=/trunk/packages/xvm-authz-locker/; revision=2766
Move XVM's locker authorization code into a separate xvm-authz-locker package (and corresponding xvm.authz.locker Python package). This makes it possible to install invirt-base without needing the authz code installed as well, and also separates some very XVM-specific logic from the Invirt packages. svn path=/trunk/packages/xvm-authz-locker/; revision=2602