Open Stack

In reference to the Oslo Wiki[1] , in the Incubation section, principle number 2:

"The API is already in use by a number of OpenStack projects"

And in the Incubation section:

"The process of developing a new Oslo API begins by taking code which is common to some OpenStack projects and moving it into the oslo-incubator repository."

Where should cross-project code be incubated in the phase *before* it is implemented by multiple projects? The Heat and Nova teams are working together on StructuredStateManagement[2] and want to start something new, but are struggling to determine where to put it. This is probably evolve into an Oslo library, but it's not obvious where it should live in the mean time. Should it be a splinter off of Heat? In Nova? Neither option seems quite right.

Have we considered having an OpenStack "Common" service that's designed to be a pluggable general purpose service on which multiple general-purpose utility services can be hung? I could imagine actually putting multiple services in here, such as Heat, Convection[3] (using StructuredStateManagement), EventScheduler[4], etc.

Ideally I'm looking for a project that's central like Oslo, but intended for hosting API controlled services, and that welcomes cooperative development from multiple teams to make a new modular code base that serves multiple projects in a way that it can be safely treated as a critical dependency.

In the absence of such a project, the only way I can think of addressing this is to have an existing project volunteer to incubate the common service(s). That would almost certainly mean changing the scope for the original project.

Thanks,

Adrian Otto

References:
[1] https://wiki.openstack.org/wiki/Oslo
[2] https://wiki.openstack.org/wiki/StructuredStateManagement
[3] https://wiki.openstack.org/wiki/Convection
[4] https://wiki.openstack.org/wiki/EventScheduler
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130506/431bcb2d/attachment.html>