17:00:18 #startmeeting ironic 17:00:19 Meeting started Mon Aug 28 17:00:18 2017 UTC and is due to finish in 60 minutes. The chair is dtantsur. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:20 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:21 o/ 17:00:23 The meeting name has been set to 'ironic' 17:00:25 o/ 17:00:25 o/ 17:00:26 o/ 17:00:29 o/ 17:00:29 o/ 17:00:30 o/ 17:00:31 o/ 17:00:32 o/ 17:00:35 o/ 17:00:40 hi all! 17:00:50 our agenda as usual is at: 17:00:52 #link https://wiki.openstack.org/wiki/Meetings/Ironic 17:00:59 o/ 17:01:23 o/ 17:01:54 o/ 17:02:01 #topic Announcements / Reminder 17:02:06 o/ 17:02:11 #info Ironic 9.1.0 (Pike) release is finally out! 17:02:14 w000t! 17:02:21 o/ 17:02:22 \o/ 17:02:24 thanks all for your hard work, especially during the release week(s) 17:02:25 woo hoo :) 17:02:26 \o/ 17:02:26 yay! thanks everyone! 17:02:34 :) 17:02:50 I was surprised how much we got done, given the loss of bodies 17:02:55 o/ 17:02:57 yes, this is really impressive! 17:02:59 good job everyone 17:03:05 0/ 17:03:30 #info we have OSC baremetal documentation: https://docs.openstack.org/python-ironicclient/latest/cli/osc_plugin_cli.html#command-reference 17:03:49 I really love it btw, now we can just link people to commands 17:04:00 yes, that was a pleasant surprise! 17:04:21 Cool 17:04:29 #info Ironic-ui and BFV meetings will resume next week 17:04:32 cool stuff 17:04:34 o/ 17:05:25 #info New bug dashboard address: http://dashboard-ironic.7e14.starter-us-west-2.openshiftapps.com/ 17:05:30 well, I have a shorter version 17:05:41 #link http://tinyurl.com/ironic-dashboard 17:05:49 * rloo was almost afraid to click on it, worried it was spam :) 17:05:55 tl;dr OpenShift 2 is sunsetting, so I had to move to OpenShift 3 17:06:12 now we're on k8s like serious people :D 17:06:14 thx dtantsur! 17:06:44 per my PTL promise, I'll be improving this dashboard in the coming months 17:07:00 anything else to mention? 17:07:19 next monday, is there going to be a meeting? 17:07:26 is it only US/Canada that has a holiday? 17:07:34 it's not a holiday here, at least 17:07:44 neither in ukraine 17:07:51 dtantsur: ok, i'm happy if you meet and work :) 17:07:55 I'll be on regardless :) 17:08:09 well, we can try having a meeting anyway 17:08:16 well, I do need to go look for places for a gathering... 17:08:26 Today is bank holiday Monday in the UK, I think 17:08:28 it's the last one before the PTG, I'd like to leave the opportunity for random people to come and ask questions 17:08:40 makes sense 17:09:02 moving on? 17:09:18 ++ 17:09:20 #topic Review subteam status reports (capped at ten minutes) 17:09:32 not much to review, but please take a look: 17:09:48 #link https://etherpad.openstack.org/p/IronicWhiteBoard starting with line 124 17:10:11 I guess we will clean up the priorities list right after the PTG.. 17:10:30 can we delete 'nova resource class...' L144? 17:10:44 yeah, I think we can 17:10:52 also BFV? TheJulia? 17:11:17 Rolling upgrades has some updates 17:11:26 We'll resume planning BFV work next week, so there is no update at present 17:11:31 we have one more nova patch, but I guess it's not a priority (unless we decide it is on the PTG) 17:11:39 we must leave driver composition until those promised docs are available ;) 17:12:01 yes, shame on me :) 17:12:15 though, I'd appreciate if people maintaining drivers submitted their upgrade guide ;) 17:12:18 dtantsur: we should have made you promise that if you are ptl. or did you promise? :) 17:12:47 we should try to get the py3.5 compat stuff done now 17:12:55 * dtantsur denies everything 17:13:14 and jlvillal, the tempest plugin. is the next month a good time? 17:13:18 rloo: I thought ironic part is done? 17:13:29 vdrok: the job is not voting, and IPA is on python 2 17:13:39 vdrok: not sure. there is something there about. oh yeah, testing ironic-inspector 17:13:40 ah right ipa 17:13:49 rloo, I think so. They want us to submit a git repo to infra with all the changes. I will work with infra and dtantsur on it 17:13:58 thx jlvillal! 17:14:16 yeah, let's cook it on github first, I guess 17:14:22 Having a patch with 92 patches in the chain is a DoS on the build system :( 17:14:22 dtantsur: can we move the tempest stuff (L244) up. or do you want to wait til after ptg? 17:15:14 I think we also want refactoring of code to access other services, L267 17:15:22 rloo: I'd wait til the PTG, yes 17:15:29 dtantsur: Wht kind of information is expected in the driver upgrade guide? 17:15:30 just to avoid confusion 17:15:32 dtantsur: ok 17:15:44 stendulker: mapping between a classic driver and hardware type + interfaces 17:16:00 stendulker: essentially, populate the table at https://docs.openstack.org/ironic/latest/admin/upgrade-to-hardware-types.html with your drivers 17:16:34 dtantsur: Ok. Only those 2 things? 17:17:06 I think it's one thing :) but yes, only this table 17:17:22 stendulker: i think shiv may have done it: https://review.openstack.org/#/c/496480/ 17:17:23 stendulker, dtantsur: ty 17:17:38 rloo: You,too :) 17:17:48 rpioso: yw :) 17:18:21 dtantsur: In iLo driver have also added section related to that to show equivalence. Also another patch updating the above said doc is in progress 17:18:43 ah, https://review.openstack.org/#/c/496480/4/doc/source/admin/upgrade-to-hardware-types.rst right 17:18:50 this is what I was asking for 17:19:04 dtantsur: yes :) 17:19:38 dtantsur: i updated the whiteboard with the ilo hw patch 17:19:52 * dtantsur wonders if mgoddard is up for updating his VIF refactoring chain in the near future 17:19:54 thanks rloo 17:19:55 dtantsur: thank you 17:20:20 i'm ready to move on 17:20:48 * dtantsur too 17:20:53 everyone done? 17:21:03 yup 17:21:06 #topic Deciding on priorities for the coming week 17:21:22 so, the release is done 17:21:39 pas-ha's patch chain can still stay, I guess 17:21:50 and I'd still appreciate people reviewing specs 17:22:18 dtantsur: it would be useful to put links to specs that we plan on discussing at ptg, when/if we know which ones 17:22:32 along with pas-ha 's patches there is this one that should make our lives a bit easier https://review.openstack.org/359061 17:22:34 yep, I'll try to find them when preparing the final schedule 17:23:03 aha, true, we should get back to it 17:23:31 dunno if people think it's a priority though, but I've put it on my list 17:23:39 yeah, we're gonna bump the client anyway, so might as well include this 17:23:48 yes please :) 17:23:58 (I still have not done any removals, just so that people can state their opinions on that) 17:24:04 together with dropping OSC from requirements 17:24:26 pas-ha lives for the day... ^^ 17:24:29 hehe 17:24:41 dropping OSC from requirements is an easy win, I guess 17:25:01 mmm, 3 priorities, we may try to get more 17:25:10 rloo: anything from upgrades to take? 17:25:25 dtantsur: oh yes. 17:25:41 https://review.openstack.org/#/c/497666/ ? 17:25:47 dtantsur: https://review.openstack.org/#/c/497666/ 17:25:50 dtantsur: yeah, you beat me to it 17:25:54 hehe 17:26:34 we do need to get the 2nd patch in that series done, to disallow ocata -> queens, before we approve something that mucks it up. 17:26:39 change 666666 is close!! 17:26:42 * milan screenshots an all-green CI patch ;) 17:26:58 milan: wow, impossible. was it docs-only? :D 17:27:13 dtantsur: We could also be in the twilight zone 17:27:18 vdrok: what is 666666? 17:27:22 actually 497666 17:27:24 ;) 17:27:25 rloo: I'm guessing a joke 17:27:37 change number heh 17:28:02 vdrok: heh, cuz there is no 666666 and some folks don't like 6... 17:28:14 okay, how is the list looking? :) 17:28:40 dtantsur: +1 17:28:58 lgtm 17:29:11 okay, there is certainly stuff to discuss, so let's move on 17:29:17 #topic PTG planning 17:29:22 first items are more like FYI 17:29:30 #info Team photo on the PTG: https://docs.google.com/spreadsheets/d/18DmI9ydq6dKr4hAcoAN83vYXWn8TV1NEvy09Ll02_Y0/edit#gid=0 17:29:42 our slot is Wed 11:00 17:30:25 * jlvillal will remember to wear his best swag t-shirt :) 17:30:35 #info Team dinner/beers at the PTG? https://doodle.com/poll/nvavg9ab9ebq2e4v 17:30:47 this is the poll about the times 17:30:58 is there anybody here who did not participate so far? 17:31:15 dtantsur: darn, i would have liked the team dinner earlier rather than later. (to get synergy, etc). looks like it'll be thurs... 17:31:19 I think we should decide on the date already to avoid booking a venue too close to the place 17:31:29 well, actually, I can cancel my plans for Monday 17:31:36 dtantsur: + to cancel! 17:31:42 and I feel that I should to avoid excluding a team member (Arkady) 17:32:02 dtantsur: yes, do it 17:32:05 so, let me phrase it like this: any objections to having an ironic team dinner on Monday? 17:32:21 Not from me. 17:32:39 nope 17:33:05 okay 17:33:23 #agreed We will try planning the team dinner at the PTG on Monday, Sep 11th 17:33:36 now, we need volunteers to find a place and/or help TheJulia find a place 17:33:38 oh, 9/11... 17:33:55 well... 17:33:58 good things happen on that date too 17:34:07 dtantsur: I'm planning to get into Denver on Sunday morning, so I should be able to explore all that afternoon 17:34:14 awesome, thanks TheJulia! 17:34:21 if you have any tips, please let Julia know 17:34:29 and especially let her know if you have any special requests 17:34:35 ++++++ 17:34:41 thx TheJulia! 17:34:46 https://www.yelp.com/search?find_desc=Restaurants&find_loc=3801+Quebec+St,+Denver,+CO+80207 :) 17:35:06 okay, let's now talk about the schedule 17:35:20 #link https://etherpad.openstack.org/p/ironic-queens-ptg 17:35:31 I've started building a schedule from the proposed topics 17:35:39 most of mirantis folks leaves on Fri 17:35:48 to be honest, I think the previous PTG layout worked well for us, so I keep the idea the same 17:35:55 pas-ha: Fri morning/afternoon/evening? 17:35:59 dtantsur: we're in the same room, right? similar size as last ptg? 17:36:01 I leave in the evening, for example 17:36:14 rloo: dunno about similarity, but it's promised to be a large room 17:36:25 dtantsur: ok, that's good. 17:36:26 dtantsur: Fri morning/afternoon (11:00 or 14:00 flights) 17:36:34 I think I told the foundation we expect 20-30 people 17:36:58 pas-ha: ok, noted. I'll move the inspector discussion somewhere... 17:37:10 so for inspector stuff me and Anton might be available in the morning 17:37:16 folks, what is good to discuss on Friday morning, given that some people will have left? 17:37:17 yes 17:37:26 My flight is Friday at 7pm 17:37:29 Even then, the airport is 34-45 minutes from the venue if memory serves 17:37:56 TheJulia: non-US people better arrive a few hours in advance just in case 17:38:03 y'know, borders, formalities.. 17:38:07 ++ 17:38:27 dtantsur: you mean which ones would be ok to move to fri out of the proposed topics? 17:38:47 vdrok: yes, that's what I mean 17:38:51 dtantsur, One nice thing about the US, we don't really have an exit check. The airlines check your passport. But no formal passport control to leave the country. 17:39:23 the line can still be quite long afair 17:39:45 Oh yeah, the security (TSA) lines can take awhile. 17:39:58 mmm, maybe future of bare metal scheduling? 17:40:13 it may end up a relaxed flame war topic :) 17:40:14 that might... work 17:40:15 pas-ha: do we need to discuss taking ansible driver in-tree? seems like the spec will be approved before PTG? 17:40:40 rloo: we need to discuss whether we need the deploy steps work.. but we can do it at any time, including today 17:40:53 otherwise I'm +1 on Just Do It 17:41:04 dtantsur: i think we want it still? I need to update that spec. I don't know that we need to discuss. 17:41:20 I hope to share some nice graphs on PTG re ansible-deploy :) 17:41:30 dtantsur: I'm also willing to move client versioning to friday if necessary, we will still want to get the discussion out of the way regarding crossing versions with nova which this would relate. 17:41:38 openstack-wide goals? is there lots of things to discuss? 17:41:43 pas-ha: ah, so a presentation. no red in graphs please :D 17:41:45 Only 2... 17:42:01 TheJulia: which of the topics, version negotiation in the client or the nova virt problem? 17:42:08 rloo: :) 17:42:18 vdrok: just make sure we don't miss anything 17:42:31 dtantsur: they are intertwined, but the nova virtual problem should definitely be when more people are around 17:42:55 wed looks like 'stuff we need/want to do that we've already discussed', thurs is the fun part? 17:42:55 the exact mechanics of how will dictate the client versioning negation stuffs 17:42:58 TheJulia: in my view it depends on the negotiation.. but yeah, let's try it this way 17:43:27 dtantsur: we could always just combine them and try and time box it.... 17:43:54 ok, let's try it this way 17:45:02 mmm, wdyt about swapping "Processes and tools" and "Pressing issues"? 17:45:10 Thursday feels too packed the way it is now 17:45:58 Yeah, I think that is a good idea 17:46:10 dtantsur: i'm better in the morning so prefer contentious topics then, but otherwise, i'm fine 17:47:33 rloo: IMO reasoning about new proposals is even harder than about difficult, but familiar, topics 17:47:46 but this is probably not the same for all of us :) 17:47:54 It is going to vary based upon how each of us are wired differently in our brains 17:47:55 dtantsur: :) 17:48:41 okay, please check the new version. wdyt? 17:48:53 I've moved everything from Friday, but we will certainly find something to work on 17:49:04 we may end up organizing small working groups 17:49:54 lgtm 17:49:56 TheJulia: thanks for talking to Sean! I'll remove this comment, and will keep it in mind 17:50:06 dtantsur: ok 17:50:10 there was something about console at the bottom L 220. is that discussed or did we decide not to? 17:50:25 good catch, it was added after I built the list 17:50:47 I'm fine with talking about it 17:50:51 dtantsur: What about "Follow-up to the driver composition"? 17:51:09 rpioso: it is inside of "check status of Pike priorities" 17:51:10 dtantsur: maybe we should add a new section for new topics, otherwise it will be hard to know what was added after today. 17:51:19 I did not list everything there, we will just go over each item 17:51:34 rloo: well, I asked people to ping me when adding stuff, but.... 17:51:52 dtantusr: Okay. And "future of inspection (especially OOB) after switch to resource classes"? 17:51:54 I will just check it from time to time 17:52:00 dtantsur: L16 -- 17:52:19 yeah, maybe it's my fault. I'll clarify 17:52:19 dtantsur: maybe mention there to ping you, not sure. 17:52:35 What's the plan for Monday and Tuesday? My first PTG :) 17:52:43 rpioso: "Inspection and resource classes" 17:52:44 rpioso: L39 I think 17:52:57 jlvillal: x-project stuff 17:53:00 dtantsur: well, might be clearer to add new section, 'potential topics not reviewed yet' 17:53:06 dtantsur: or something like that 17:53:09 dtantsur, vdrok: ty 17:53:12 jlvillal: there will be rooms like "API SIG", "releases", "QA", etc 17:53:14 dtantsur, Well we document the Ironic x-project items? 17:53:21 rloo: I'm afraid people will miss them :) 17:53:23 s/Well/will/ 17:53:37 jlvillal: cross-project with nova are in nova's etherpad 17:53:43 jlvillal: there is something in the bottom. somebody will have to stop by nova (probably vdrok and me) 17:53:44 dtantsur, Ah, so not Nova/Ironic or Neutron/Ironic 17:53:45 not sure about this vm-bm sig 17:53:56 but I suppose the same 17:53:57 the vm-bm sig is something not entirely clear to me as well 17:53:57 Oh there is, okay 17:54:00 but I'll try figuring it out too 17:54:01 jlvillal: at the bottom, L295. 17:54:10 maybe we shoudl move the related sessions part higher. 17:54:21 I will 17:54:25 Thanks! 17:55:17 I looked at the vm-bm sig page last week and it went back, at least mentally, to the instance level credentials discussion of how as an instance do I obtain access to cloud resources without being pre-loaded with credentials, or how do I have a different set of credentials and permissions for my running process, not my administrative user. It might be different now 17:55:19 jlvillal: do you want to represent us in the QA room? 17:55:28 fwiw, list of etherpads: https://wiki.openstack.org/wiki/PTG/Queens/Etherpads 17:55:30 dtantsur: I can do that. Sign me up :) 17:55:41 TheJulia: it seems so. I'm not sure why it's specific to BMs or VM-BM world.. 17:56:02 vdrok: would you like to check the nova room? 17:56:04 Partially in that it needs to support config drive, or metadata service 17:56:09 I will be there too, when needed 17:56:14 dtantsur: but... *shrug* 17:56:29 anyone wants to check this BM-VM thingy? 17:56:30 dtantsur: yeah I'll be there on related discussions I think 17:56:37 I'm afraid I'll be with the API SIG most of the time 17:56:41 dtantsur: I can 17:56:42 (on Mon and Tue) 17:56:46 TheJulia: thanks! 17:57:04 oh yeah, i was thinking about being in the bm-vm thing too. 17:57:26 we also have infra room, cli, skip level upgrades, stable 17:57:27 if anyone goes to docs, please ask about red :) 17:57:34 and many more, but these can be of interest 17:57:43 dtantsur, GraphQL ? http://graphql.org/ :) 17:57:46 oh, and docs! 17:57:51 * dtantsur hides 17:57:58 rloo: note taken 17:58:08 thx TheJulia! 17:58:15 rloo: you like upgrades: https://etherpad.openstack.org/p/queens-PTG-skip-level-upgrades 17:58:17 :D 17:58:19 rloo: you mean the movie right? 17:58:20 * TheJulia ducks 17:58:38 dtantsur: i don't actually like it and have wondered several times why i offered. and yeah, i saw that and am afraid. 17:58:47 * dtantsur is pretty sure that skipping Pike won't work for Nova/Ironic pair 17:58:47 TheJulia: heh 17:59:10 dtantsur: so i guess i should also attend that upgrades one... 17:59:40 that may be of value 18:00:06 okay, out of time 18:00:08 thanks everyone! 18:00:12 thanks! 18:00:13 #endmeeting