17:00:18 <jroll> #startmeeting ironic
17:00:19 <openstack> Meeting started Mon Aug  1 17:00:18 2016 UTC and is due to finish in 60 minutes.  The chair is jroll. Information about MeetBot at http://wiki.debian.org/MeetBot.
17:00:20 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
17:00:20 <jroll> hey folks
17:00:22 <JayF> o/
17:00:22 <openstack> The meeting name has been set to 'ironic'
17:00:28 <jlvillal> o/
17:00:32 <mariojv> o/
17:00:33 <vdrok> o/
17:00:34 <TheJulia> o/
17:00:35 <alineb> o/
17:01:03 <dtantsur> o/
17:01:10 <rama_y> o/
17:01:16 <jroll> #topic announcements and reminders
17:01:48 <jroll> just a note that library freeze is in 3 weeks, client in 4, keep that in mind when we're approving things
17:01:54 <devananda> o/
17:02:12 <jroll> also, ruby is out this week, I think
17:02:14 <jroll> anyone else have announcements?
17:02:20 <JayF> Presumedly the library freeze wouldn't apply to ironic-lib?
17:02:25 <JayF> Given it's not an external library?
17:02:34 <jroll> it would
17:02:36 <dtantsur> it might be subject to negotiations
17:02:44 <dtantsur> by default - it would
17:02:46 <jroll> the point is to lock down g-r updates
17:02:52 <JayF> got it, that makes sense
17:03:01 <jroll> exception process would probably be easier
17:03:12 <rpioso> o/
17:03:25 <jlvillal> Yes Ruby is out this week. Canada holiday today. And vacation rest of the week.
17:04:23 <jroll> cool
17:04:28 <jroll> #topic subteam status reports
17:04:43 <jroll> as always, those are here:
17:04:45 <jroll> #link https://etherpad.openstack.org/p/IronicWhiteBoard
17:04:53 <jroll> starts around line 79
17:04:57 * jroll gives people a few
17:05:05 <jroll> also, forgot to link the agenda at the start of the meeting
17:05:10 <jroll> #link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting
17:05:29 <dtantsur> should we drop node claims API from priorities for real? I don't think we have chances of finishing it by newton
17:05:31 <stendulker> o/
17:05:35 <krtaylor> o/
17:05:38 <mjturek1> o/
17:05:49 <jroll> dtantsur: yeah, I think it isn't useful anyway now
17:05:59 <jroll> I'll drop it from our lists this week, same for search api
17:06:09 <dtantsur> cool
17:06:21 <dtantsur> I still hope to have search API one day
17:06:32 <jroll> ditto, but it isn't a priority (to me) right now
17:08:08 <jroll> TheJulia: how close is the bfv spec? what's the chances on getting that + some of the plumbing in this cycle?
17:08:55 <TheJulia> jroll: basicall the spec is done and I've started active development of stuff that would lay on top of volume connection information.  We need to get volume connection information landed, even if we wait on the API/client changes until the next cycle
17:09:21 <jroll> TheJulia: okay, cool, so thinking at least DB changes this cycle?
17:09:22 <cinerama> one thing we need is to get the volume connector changes reviewed and landed. i am actively working on them now. link is in the whiteboard etherpad
17:09:37 <TheJulia> cinerama has been focused on rebasing the volume connection info work, and we might be able to get some of the bfv substrate in this cycle, just relies upon the volume connection info in the end.
17:09:45 <mgould> o/
17:10:25 <TheJulia> jroll: Yeah, I -2'ed the first API change change until we were ready to land it, but it also needs some work
17:10:37 <jroll> TheJulia: cool cool, thanks
17:10:48 * jroll trying to figure out what we can and cannot finish this cycle
17:11:36 <dtantsur> devananda, left some comments on https://etherpad.openstack.org/p/ironic-jjb-matrix
17:12:11 <devananda> dtantsur: thanks
17:14:21 <jroll> anything else on subteam reports?
17:14:46 <jroll> okay, nothing else on the agenda
17:14:49 <jroll> #topic open discussion
17:14:55 <jroll> anyone have a thing?
17:15:21 <TheJulia> Well, you already basically asked what cinerama was going to bring up :)
17:15:34 <cinerama> thanks for asking :)
17:16:04 <TheJulia> jroll: will you be making like an ordered priority review list for the next few weeks?
17:16:16 <jroll> as far as focus for this week, I'd like us to keep cranking on: resource class things (just docs left, need to put those up), networking things (the patch chain from the discussion this morning), BFV spec / connection info things, OSC plugins are probably an easy win too
17:16:23 <vdrok> do I understand correctly that portgroups stuff is moved to the next cycle now?
17:16:35 <jroll> oh and getting policy done is probably easy, too
17:16:43 <jroll> TheJulia: yeah I've been meaning to
17:16:50 <jroll> TheJulia: probably in the form of re-ordering the trello board
17:16:59 <TheJulia> jroll: Ok, thanks
17:17:00 <jlvillal> Any news on how long the Ocata cycle will be? /me has been out of the loop for a couple weeks.
17:17:01 <jroll> got caught up in actually writing code last week \o/
17:17:21 <jroll> vdrok: I'd like to land the APIs for it this cycle, but nova support will wait for sure
17:17:38 <vdrok> gotcha
17:17:46 <dtantsur> jroll, I'd kindly ask to land the agent API too. it's essentially done, some patches need rebase
17:18:09 <jroll> jlvillal: I believe 5 months?
17:18:12 * jroll is looking
17:18:17 <jroll> dtantsur: ++
17:18:59 <jlvillal> jroll: Thanks.
17:19:13 <jroll> jlvillal: http://www.openstack.org/blog/2016/05/faq-evolving-the-openstack-design-summit/ ctrl-f "When will the change happen"
17:19:19 <jroll> 5 months indeed
17:19:52 <jlvillal> Okay. Not as bad as a rumor I had heard once. Only one less month than normal.
17:19:56 <jroll> dtantsur: oh, we should get the serial console follow-ups done
17:20:06 <jroll> so yeah, plenty to do this week :)
17:20:12 <dtantsur> oh
17:21:10 <jroll> anybody have anything else for open discussion?
17:21:41 <dtantsur> unless we want to discuss defaults in the driver comp...
17:21:50 * dtantsur does not quite want it right now, but it has to happen
17:22:39 <jroll> hm, do we want to?
17:24:16 <dtantsur> maybe we should postpone it till the summit, dunno
17:24:16 <vdrok> seems like it's dtantsur's lucky day :)
17:24:25 <dtantsur> :)
17:24:40 <TheJulia> I was just going to suggest that higher bandwidth discusison may be required w/r/t driver composition
17:24:56 <dtantsur> the forth or the fifth attempt? :D
17:25:12 <vdrok> still, we're progressing
17:25:20 <jroll> I think it's four now :P
17:25:21 <TheJulia> I was thinking this awesome voip bridge and have it weekly if we need to
17:25:26 <JayF> I think having a specific chat about that over the OpenStack conference ^ that
17:25:26 <TheJulia> but I'm crazy :)
17:25:41 <JayF> like schedule something specifically on that topic
17:25:47 <JayF> you'll get less noise + higher bandwidth
17:25:49 <jroll> we can definitely do that
17:25:54 <TheJulia> ++
17:26:01 <jroll> who wants to set that up?
17:26:38 <JayF> *crickets*
17:26:42 <TheJulia> jroll: define that?
17:26:50 <jroll> TheJulia: a voip thing about this
17:27:11 <jroll> this being the driver comp defaults thing
17:27:19 <TheJulia> I guess we could post a doodle and try and figure out a good time in the next week or two?
17:27:37 <jroll> sure, I need someone to own kickstarting that, though
17:27:43 <TheJulia> I'll do it
17:27:47 <jroll> great, thanks!
17:27:51 <TheJulia> no problem
17:27:57 <jroll> as a note, we might want rloo there, so maybe early next week?
17:28:21 <dtantsur> voip sounds pretty cool
17:28:24 <TheJulia> Yeah, agreed... I'll only propose time days starting next tuesday
17:28:41 <TheJulia> s/time//
17:28:51 <jroll> cool, thanks again
17:28:53 <jroll> anything else?
17:29:01 <JayF> There is one small other thing
17:29:06 <JayF> be on the lookout for another doodle to the list
17:29:16 <JayF> I want to hold a gate troubleshooting session
17:29:29 <JayF> and neglected to, uh, actually attend the previously scheduled one due to moving and scrambling my schedule
17:29:36 <JayF> so if you're interested in that keep an ear on the list
17:29:52 <jroll> cool
17:30:07 <JayF> well, more like "How to troubleshoot the gate"
17:30:16 <jroll> with that let's take back half an hour so everyone can go review the priority things :)
17:30:43 <jroll> #endmeeting