> > To that end, I identified a series of small steps to get us there: > > 1) Unify the "fixed_key" oslo_config definitions in Cinder and Nova > so they are identical (right now their help texts are slightly > different). This step avoids triggering a DuplicateOptError exception > in the next step. > > 2) Add a ConfKeyManager implementation to Castellan. This essentially > involves copying in one of the existing implementations (either Cinder's > or Nova's). > > 3) Replace Cinder's and Nova's implementations with references to the > one in Castellan. This can be done in a way that retains compatibility > with the key_manager "backend" (was "api_class") config options > currently used by Cinder and Nova. The code in > cinder/keymgr/conf_key_manager.py and nova/keymgr/conf_key_manager.py > will collapse down to this: > > from castellan.key_manager import conf_key_manager > > class ConfKeyManager(conf_key_manager.ConfKeyManager): > pass > > Having a common ConfKeyManager implementation will make it much > easier to support migrating things to Barbican, and that's an important > step toward the goal of deprecating the ConfKeyManager entirely. > > Please let me know your thoughts, as I plan to begin proposing patches. > > Regards, > > Alan Bishop
Makes sense to me Alan. Thanks for looking into this. __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
