Open Stack

Well, I and I believe a few others feel a slightly higher sense of urgency about splitting out the scheduler but I don't want to hijack this thread for that debate.  Fair warning, I intend to start a new thread where we can talk specifically about the scheduler split, I'm afraid we're in the situation where we're all in agreement but everyone has a different view of what that agreement is.

--
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
Ph: 303/443-3786

-----Original Message-----
From: Jay Pipes [mailto:jaypipes at gmail.com] 
Sent: Friday, September 5, 2014 8:07 AM
To: openstack-dev at lists.openstack.org
Subject: Re: [openstack-dev] [nova] Averting the Nova crisis by splitting out virt drivers

On 09/05/2014 06:29 AM, John Garbutt wrote:
> Scheduler: I think we need to split out the scheduler with a similar 
> level of urgency. We keep blocking features on the split, because we 
> know we don't have the review bandwidth to deal with them. Right now I 
> am talking about a compute related scheduler in the compute program, 
> that might evolve to worry about other services at a later date.

-1

Without first cleaning up the interfaces around resource tracking, claim creation and processing, and the communication interfaces between the nova-conductor, nova-scheduler, and nova-compute.

I see no urgency at all in splitting out the scheduler. The cleanup of the interfaces around the resource tracker and scheduler has great priority, though, IMO.

Best,
-jay

_______________________________________________
OpenStack-dev mailing list
OpenStack-dev at lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev