15:00:46 <n0ano> #startmeeting gantt
15:00:48 <openstack> Meeting started Tue Aug  5 15:00:46 2014 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.
15:00:49 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
15:00:51 <openstack> The meeting name has been set to 'gantt'
15:00:57 <bauzas> well, timezone difference maybe ^^
15:00:59 <n0ano> Anyone here to talk about the scheduler?
15:01:02 <bauzas> \o
15:01:33 <n0ano> bauzas, BTW, according to my timestamp, I started exactly at 1500 :-)
15:01:56 <bauzas> (17:00:46) n0ano: #startmeeting gantt
15:01:57 <mspreitz> moi
15:02:10 <bauzas> bonjour
15:02:14 <bauzas> :)
15:02:32 <n0ano> jeez, 46 seconds, and I thought I was compulsive :-)
15:02:56 <mspreitz> this is the scheduler group, man
15:03:06 <n0ano> mspreitz, good point
15:03:28 <n0ano> OK, in a vain attempt to get serious, let's start
15:03:29 <bauzas> yeah, you have 60 secs accepted
15:03:45 <n0ano> #topic mid-cycle meetup recap\
15:04:08 <n0ano> detailed log at the launchpad page\
15:04:15 <n0ano> #link https://etherpad.openstack.org/p/juno-nova-mid-cycle-meetup
15:04:26 <bauzas> summary ?
15:04:27 <bauzas> :)
15:04:40 <n0ano> Tues morning was the discussion  about gantt
15:04:48 <n0ano> my take was...
15:05:00 <n0ano> 1)  scheduler lib code being approved...
15:05:24 <n0ano> 2) DB isolation spec exception approved...
15:05:41 <bauzas> \o/
15:05:57 <Yathi> great job guys!
15:06:03 <n0ano> 3)  Jay wants to move resource claims out of compute and into scheduler, need a specific proposal from him before we know if we should gate the split on that...
15:06:32 <bauzas> well, my understand was a bit less enthusiastic :)
15:06:34 <jaypipes> n0ano: yeah, wiorking with yjiang on that
15:06:59 <bauzas> scheduler-lib and isolate-sched-db are on their way, that's it :)
15:06:59 <n0ano> 4) n0ano needs to ask on the mailing list if other projects are good about splitting out gantt (neutron said yes at the meetup, containers enthusiastic about it)...
15:07:31 <n0ano> I think those are the big points that I took away, bauzas & jaypipes you were there, anything to add?
15:07:41 <jaypipes> n0ano: nope, that's a good summary
15:07:57 <bauzas> I wish I would have been there, but Graham Bell helped me a lot
15:08:06 <jaypipes> heh
15:08:27 <bauzas> nah, I'm OK with the summary, as I said, work is on-going, more to investigate for the RT move
15:08:31 <Yathi> we need to talk to Cinder folks about their enthusiasm for gantt and unified scheduling etc
15:08:50 <n0ano> jaypipes, you're working with yjiang on the resource stuff, do you know when you'll have a BP posted?
15:09:15 <n0ano> bauzas, Yathi +1
15:10:01 <jaypipes> n0ano: chatting with him this afternoon about it.
15:10:17 <n0ano> jaypipes, so soon, hopefully, that's all we can ask for
15:10:35 <jaypipes> n0ano: yes
15:10:35 <bauzas> maybe an etherpad can help you ?
15:10:46 * bauzas loves the etherpads, eh
15:10:51 <jaypipes> bauzas: yeah, will create one and fill some stuff in from our conversation
15:11:13 <Yathi> jaypipes: I would love to be part of that discussion
15:11:19 <bauzas> sure, my point was just to overview the basic things before having a spec to review :)
15:11:43 <n0ano> bauzas, +1, I like small groups to do the work, we can review what you come up with
15:11:51 <jaypipes> Yathi: no. no discussion for you! one year.
15:12:05 <jaypipes> Yathi: j/k :) will ping you when I find yj later today
15:12:09 <Yathi> :)
15:12:25 <Yathi> jaypipes: sounds good
15:12:44 <n0ano> jaypipes, remarkably good impression of the Soup Nazi on IRC :-)
15:13:09 <n0ano> anything else to say about the meetup?
15:13:20 <jaypipes> n0ano: :)
15:13:35 <Yathi> n0ano: other thing to add - was another Soup Nazi treatment for solver scheduler stuff at the mid-cycle meetup :)
15:13:54 <Yathi> Solver Scheduler discussion and spec pushed for Kilo - until after Gantt
15:13:55 * mspreitz wonders what Soup Nazi is
15:14:21 <n0ano> mspreitz, Seinfield reference, American pop culture strikes again
15:14:51 <n0ano> Yathi, yeah, sorry about that, but it's a big change for late in the cycle, you'll have to push early in Juno I think
15:15:32 <bauzas> +1
15:15:44 <n0ano> anyway, moving on
15:15:46 <Yathi> n0ano: +1 yup.. will be more aggressive
15:16:07 <n0ano> Yathi, the term is `assertive`, not aggressive :-)
15:16:13 <bauzas> :)
15:16:19 <n0ano> #topic forklift effort
15:16:27 <bauzas> \o
15:16:28 <Yathi> :) OK!
15:16:33 <bauzas> sooooo
15:16:38 <n0ano> really, it's finalizing the two outstanding BPs
15:16:50 <bauzas> scheduler-lib is waiting reviews
15:16:59 <n0ano> scheduler lib is waiting for reviews, do we need to get assertive on that?
15:17:25 <bauzas> well, tbh, we're having a reviewers bandwidth issue
15:17:43 <bauzas> johnthetubaguy gave previously a +2 on it, but it needed rebase due to Extensible RT merge
15:18:05 <bauzas> unfortunately, ERT was reverted, so I reverted also my patch
15:18:21 <johnthetubaguy> bauzas: RT got reverted though right?
15:18:21 <n0ano> yeah, I'm not too concerned, I'll be at the nova meeting this week, if they talk about review patches I'll bring this one up
15:18:35 <bauzas> johnthetubaguy: yeahn, situation went back to normal
15:18:50 <johnthetubaguy> bauzas: cool, thanks
15:18:59 <bauzas> johnthetubaguy: ie. both ERT patch and sched-lib patch went back to their previous states
15:19:30 <bauzas> so, if ERT goes merged before sched-lib, the latter will require a rebase
15:19:48 <n0ano> bauzas, and vice versa
15:20:05 <bauzas> n0ano: yeah, life is sometimes hard
15:20:13 <bauzas> :)
15:20:24 <n0ano> we'll see who wins the race, hopefully you
15:20:35 <bauzas> atm, ERT is in a winning position
15:20:40 <bauzas> one +2 vs. zero
15:21:02 <n0ano> we'll see, the race is not over
15:21:16 <n0ano> anyway, I think scheuler lib is well in hand
15:21:21 <bauzas> correct
15:21:35 <n0ano> for DB isolation, we have one +2 on the spec, I think we need another one right?
15:21:39 <bauzas> isolate-sched-db is having one +2
15:21:52 <bauzas> yeah, need to ask ndipanov
15:21:59 <bauzas> as he's the 2nd sponsor
15:22:33 <bauzas> if you all look at https://review.openstack.org/89893, you'll see there are 3 workitems
15:22:45 <n0ano> I would feel comfortable starting the coding given that it's unlikely the spec will change dramatically between now and final approve, what do you think bauzas
15:23:11 <bauzas> #1 is the instance group thing, a patch is provided : https://review.openstack.org/#/c/110043/
15:23:20 <bauzas> #2 is aggregates thing
15:23:33 <bauzas> #3 is instances thing, I'm on my way for writing a patch on this
15:23:44 <bauzas> should be done by today or tomorrow
15:23:59 <bauzas> so, #2 could be done based on #3
15:24:12 <bauzas> n0ano: you expressed interest in coding #2 ?
15:24:31 <n0ano> I believe that tian is willing to do #2, I'll ping him to make sure he's up for that
15:24:36 <bauzas> n0ano: sure
15:24:47 <bauzas> n0ano: I can propose you and tian to wait for patch #3
15:25:01 <bauzas> n0ano: so we'll propose an identical way
15:25:12 <bauzas> n0ano: should not require a dependency in between #2 and #3 tho
15:25:28 <n0ano> he's in Shanghai so he won't be able to look at it until tomorrow so basing on #3 should be fine
15:25:30 <bauzas> as I'm basing my work on ERT
15:25:44 <bauzas> I'm creating another resource for instances
15:25:57 <bauzas> and another one for instance's flavors
15:26:55 <bauzas> that's it for me
15:27:12 <n0ano> sounds good, we'll see what you come up with for #3 and go from there
15:27:19 <bauzas> ok cool
15:27:53 <n0ano> I think we're good on the forklift status so moving on
15:27:56 <bauzas> +1
15:28:08 <n0ano> #topic opens
15:28:10 <Yathi> bauzas: if you want me to take a task item, let me know.. I might have some bandwidth
15:28:32 <bauzas> Yathi: well, atm, we should be good
15:28:32 <n0ano> Yathi, I think we're covered but we'll keep you in mind
15:28:48 <bauzas> Yathi: that's more likely a rewiewing bandwidth that we need
15:29:06 <n0ano> anything new anyone wants to raise today?
15:29:14 <bauzas> yep
15:29:19 <Yathi> bauzas: yup I am already reviewing all these gantt patches at the moment..
15:29:26 <bauzas> don't know if sahid is there ?
15:30:00 <bauzas> there is a Juno BP that has been accepted
15:30:04 <bauzas> lemme find it
15:32:00 <bauzas> gotcha
15:32:02 <bauzas> https://review.openstack.org/#/c/85399/
15:32:02 * n0ano that BP must be well hidden
15:32:13 <bauzas> yeah, Gerrit searches suck
15:32:36 <bauzas> this BP is validated for Juno and possibly impacting isolate-sched-db
15:32:51 <bauzas> so, that's more likely a FYI
15:33:02 <bauzas> I'm on my way to sort this out with sahid
15:33:11 <n0ano> I missed this, I'll have to review the spec
15:33:19 <bauzas> nah, the spec is merged
15:33:24 <bauzas> :D
15:33:28 <mspreitz> wow, that BP is news to me... title makes it look like toes in deep water
15:33:36 <n0ano> personal review, not formal voting :-)
15:33:46 * mspreitz needs to read and think ab out that spec
15:33:58 <bauzas> anyway, as I said, we just need to sync our work
15:33:59 <n0ano> mspreitz, what he said
15:34:25 <n0ano> bauzas, well, if you're in contact with sahid that's about all we can do right now
15:34:37 <bauzas> correct, as I said, it was a FYI
15:34:44 <bauzas> that's it for me
15:35:03 <n0ano> cool, anything else?
15:35:49 <n0ano> OK, hearing silence, I'll close and we can all go off and do some real work :-)
15:35:52 <n0ano> tnx everyone
15:36:06 <n0ano> #endmeeting