Open Stack

"Daniel P. Berrange" <berrange at redhat.com> wrote on 11/22/2013 11:32:59 
AM:

> > A good example is the current discussion around a new scheduling
> > service.  There have been lots of big ideas around this.  Robert 
Collins
> > just started a thread about a proposal to start this project but with 
a
> > very strict scope of being able to replace nova-scheduler, and 
*nothing*
> > more until that's completely done.  I like that approach quite a bit.
> 
> I'd suggest something even stronger. If we want to split out code into
> a new project, we should always follow the approach used for cinder.
> ie the existing fully functional code should be pulled out as is, and
> work then progress from there. That ensures we'd always have feature
> parity from the very start. Yes, you might have to then do a large
> amount of refactoring to get to where you want to be, but IMHO that's
> preferrable to starting something from scratch and forgetting to cover
> existing use cases.

I think that is what Robert is saying.

Regards,
Mike
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131122/01659b6a/attachment.html>