15:00:03 #startmeeting ironic 15:00:04 Meeting started Mon Jan 14 15:00:03 2019 UTC and is due to finish in 60 minutes. The chair is dtantsur. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:05 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:07 The meeting name has been set to 'ironic' 15:00:10 hi everyone! 15:00:16 o/ 15:00:19 o/ 15:00:20 o/ 15:00:20 o/ 15:00:20 o/ 15:00:22 o/ 15:00:27 hmm, it's been a while since I last chaired a meeting :) 15:00:38 o/ 15:00:42 our agenda, as always, can be found here: 15:00:45 #link https://wiki.openstack.org/wiki/Meetings/Ironic 15:00:49 o/ 15:01:05 o/ 15:01:15 o/ 15:01:34 #topic Announcements / Reminder 15:01:43 o/ 15:01:44 #info TheJulia is traveling for on-site meetings this week 15:02:08 #info vdrok has requested to be removed from ironic-core 15:02:17 thanks for everything vdrok_! 15:02:19 o/ 15:02:35 o/ 15:02:49 also TheJulia and I would like to remind you that we will be looking to grow the core team, and review activity is one of the most important aspects that we look for. 15:02:58 thanks so much vdrok_, we'll miss you (we already do) 15:03:06 so please review :) 15:03:46 this, of course, is also very important for the health of the project 15:04:08 #info Mid-cycle call - Please vote for times on the 21st and 22nd: https://doodle.com/poll/i2awf3zvztncixpg 15:04:19 Call times poll will be closed tomorrow morning 15:04:41 it seems likely that the meeting next week will be cancelled in favor of the midcycle, if they end up overlapping 15:04:49 #info Mid-cycle topic/planning etherpad has been posted. Please add topics! https://etherpad.openstack.org/p/ironic-stein-midcycle 15:05:00 Core Reviewers: please ensure that you have responded to the call times poll. 15:05:16 any questions on the midcycle planning? 15:05:53 How will it be hosted? Is it irc or video conference? 15:06:05 it is likely to be a bluejeans conference 15:06:14 at least it worked pretty well for us previously 15:06:26 I'll defer to TheJulia for the final decision 15:07:17 okay, the last but not the least: 15:07:23 #info Help wanted list for items that could use additional contributor assistance: https://etherpad.openstack.org/p/IronicHelpWanted 15:07:41 if you want to help with a big chunk of work, here's your chance 15:07:55 please do make sure to sync with other people who may be interested 15:08:17 any other announcements, reminders, comments? 15:09:04 dtantsur: i think it might be useful to put more info in that helpwanted etherpad. wrt, if i am interested, then what? 15:09:39 good point. I guess the answer is "reach out to the team". I'll update later if nobody beats me to it 15:10:00 dtantsur: thx 15:10:16 #topic Review action items from previous meeting 15:10:24 #link http://eavesdrop.openstack.org/meetings/ironic/2019/ironic.2019-01-07-15.00.html 15:10:33 TheJulia promised to create a help needed list, and she did 15:10:38 no other action items recorded 15:10:43 any comments here? 15:11:18 #topic Review subteam status reports (capped at ten minutes) 15:11:33 #link https://etherpad.openstack.org/p/IronicWhiteBoard starting around line 231 15:14:41 so, I think someone has taken the neutron event processing over? hjensas? 15:15:26 dtantsur: I want to look into atleast the networking-barametal pices. I need to read the spec again to get understanding of what is needed in ironic. 15:16:05 #info If you want to help with the Neutron even processing work, please sync with TheJulia and hjensas 15:16:15 this is re rloo's question on how to help ^^ 15:16:44 please update the help wanted etherpad with ^^ too :) 15:17:10 my understanding (it has been awhile) is that the event processing is fairly straightforward. 15:18:04 mmmm, not quite. it's a lot of working spanning different parts of code. 15:18:09 s/working/work/ 15:18:12 * hjensas seem to remeber something about how to have threads/process wait in the spec that was'nt clear. (But I need to re-read it.) 15:18:41 rpittau: are you still doing anything about the graphical console? 15:18:42 dtantsur, I would like to keep helping on the graphical console patch 15:18:47 heh 15:18:49 dtantsur, yes :) 15:19:08 cool, thanks rpittau. I think rpioso is (was?) interested in the Dell side of it. 15:20:14 any other comments on the status? 15:20:32 dtantsur, just need clarification on kaifeng comment about the api code, but we can discuss in a different moment 15:20:45 we can get back to it in the open discussion 15:20:53 ok :) 15:20:53 moving on? 15:21:00 rpittau: +1 15:21:19 oh hi rpioso. are you still willing to help with the graphical console? 15:21:25 rpioso :) 15:22:35 * dtantsur moves to the priorities meanwhile 15:22:42 #topic Deciding on priorities for the coming week 15:22:59 lemme clean up a bit. we haven't merged much though 15:23:15 dtantsur: Interested, yes. Time, not as certain. I need to discuss with my team. 15:23:28 rpioso: got it, cool. 15:26:03 okay, I only added gate stabilizing as a #1 goal for this week 15:26:07 anything else to add here? 15:26:22 also anyone to help TheJulia and me looking at the gate problems? 15:27:07 dtantsur, for gate or CI in general I raised the issue with the grenade job not working last friday 15:27:09 i can try 15:27:40 rpittau: you mean, the wsgi problem? 15:27:55 after investigation it doesn't look like depends from us and I don't know if it's worth to keep working on it (I'm talking about the one in stable/queens) 15:27:56 thanks iurygregory, see the whiteboard (after line 51) 15:27:59 yes dtantsur 15:28:03 ah, queens 15:28:12 I'm currently trying to stabilize master. queens will be next :( 15:28:20 rpittau: please put your findings to the whiteboard, gate status 15:28:28 dtantsur, ack 15:28:38 is everyone fine with the priorities for the week? 15:29:01 +1 15:30:07 +1 (I will take a look at the gate status as well.) 15:30:18 2 votes for, 0 against. approved! :D 15:30:23 #topic Open Discussion 15:30:31 anything? 15:31:20 I have some update on the XClarity CI 15:31:32 rpittau talked about he needs some clarification about the comment of graphical console? 15:31:49 kaifeng, yes, just about your more recent comment on the api exposure 15:31:57 jiapei: sure, what's new? 15:31:58 We've made some progress on the deployment using XClarity driver, and we plan to add deploy test to LXCA CI this week 15:32:12 wonderful! 15:33:19 rpittau: link handy? 15:33:31 https://review.openstack.org/#/c/547356/ 15:33:31 https://review.openstack.org/#/c/547356 15:33:32 patch 547356 - ironic - Implement basic interfaces for GraphicalConsole In... - 35 patch sets 15:33:32 dtantsur: Alghough there are still some manual work, such as we use "openstack ironic deploy ..." instead of tempest... 15:33:33 patch 547356 - ironic - Implement basic interfaces for GraphicalConsole In... - 35 patch sets 15:34:13 jiapei: well, that's a start. ideally we should come to running tempest, but running any deploy is the most crucial bit. 15:35:15 rpittau: -1 does not look right indeed 15:35:28 hey hey folks, happy monday, thanks for having me :) 15:35:59 thank YOU vdrok_ :) 15:36:29 Yes, adding deploy is really a difficult part, we plan to add/test it during the day time China (night in US), so it seems won't affect the normal testing :) 15:37:04 yes vdrok_, thank YOU! 15:37:52 dtantsur, kaifeng could we exclude the field instead of removing all the api related code ? 15:38:19 rpittau: well, it's going to be weird to introduce an API version, but do nothing with it.. or which parts do you want to keep? 15:38:51 rpittau well it's only a suggestion, ideally it would be going with the api patch 15:39:30 I'd prefer not to split the API part in several microversions, to be honest 15:40:16 hmm, actually the only API part is this new field. I think it's enough to remove it to avoid touching the API layer at all. 15:41:54 it api code is fairly lightweight, so it would be easy to be split out 15:42:07 yeah, actually it makes sense to have the api patch to include the change 15:42:49 are you looking at https://review.openstack.org/#/c/547356 Just looking at the files that were touched, that isn't done right. too many changes in that one pr. 15:42:50 patch 547356 - ironic - Implement basic interfaces for GraphicalConsole In... - 35 patch sets 15:43:19 unless the author really knows what they are doing, that feature needs to be broken into more patches than this one. 15:44:02 i think there are other patches, they just haven't shown up :) 15:45:13 i'm a big believer in not approving any patches related to a feature, until all/most of the PRs for the feature are available. And we usually always have a 'last' PR (that exposes the feature) with the API version bump 15:45:35 which may not answer your current question. 15:46:58 make sense 15:47:42 We're trying to configure fake_pxe, but we can't get any output of 'openstack baremetal introspection bulk start' 15:48:16 We're not sure what to look at/do. 15:48:26 zenpac: hi, we're in a meeting, please wait a couple of minutes 15:48:38 also, are we done? I guess we are in agreement re the API patch? 15:50:13 I guess it means yes :) thanks everyone! 15:50:14 dtantsur, good for me, thanks 15:50:18 #endmeeting