For sure I'll be at both sessions and can report back to the Nova scheduler 
session.  The main reason for the Tues. session is to get cross-project ideas, 
I would expect that the Wed. Liberty scheduler session will be more Nova 
focused but there will clearly be overlap.

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

-----Original Message-----
From: John Garbutt [mailto:[email protected]] 
Sent: Thursday, May 14, 2015 3:35 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [nova-scheduler] Cross-project requirements for an 
independant (gantt) scheduler at Vancouver

On 13 May 2015 at 16:48, Dugger, Donald D <[email protected]> wrote:
> I’d like to get together to talk about what kind of APIs/requirements 
> different projects would need from a common scheduler.  To that end 
> room 221 is available on Tues. at 3:40PM.  If you’re at all interested 
> in a common scheduler come on by and join the conversation.
>
> Location:              Rm 221
> Time:                     3:40PM
> Date:                     Tues., 5/19

Its possible some of that will come up in this nova-scheduler session (see line 
44):
https://etherpad.openstack.org/p/YVR-nova-scheduler-in-liberty

But frankly, there is probably more than 40 mins of topics in that session 
right now.

In any case, it would be great if you can feedback the above discussions into 
the above session.

Thanks,
John

PS
Sorry, for the duplicate email, I replied to the wrong thread.

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: [email protected]?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to