Open Stack

On 08/07/2012 07:07 AM, Mark McLoughlin wrote:
>> Unfortunately it means the modules are going to be harder to reuse
>> outside of OpenStack because instead of providing a class-based API
>> that takes individual arguments that can come from another
>> application's config, or even a single config object as argument, the
>> global object needs to be initialized correctly.
>
> Yes, agree. But I don't see "enable reuse outside of OpenStack" as much
> of a priority here.
>
> Our focus should be on OpenStack's copy-and-paste technical debt rather
> than general re-usability. Allowing modules to add config parameters is
> a pragmatic approach to get us moving forward but, if we design the APIs
> well, we should be able to extend them later so that the config options
> can be overridden by API users.

+1

You can tie yourself in knots really fast trying to anticipate future 
needs for mythical users. :) Lets solve the actual needs first. It will 
be cleaner than what we have, which will make any future refactoring easier.

	-Sean

-- 
Sean Dague
IBM Linux Technology Center
email: sdague at linux.vnet.ibm.com
alt-email: sldague at us.ibm.com