20:00:05 #startmeeting openstack_upstream_institute 20:00:06 Meeting started Mon Apr 24 20:00:05 2017 UTC and is due to finish in 60 minutes. The chair is ildikov. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:00:07 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 20:00:09 The meeting name has been set to 'openstack_upstream_institute' 20:00:13 o/ 20:01:45 o/ 20:01:49 o/ 20:02:13 o/ 20:02:14 o/ 20:02:19 \o/ 20:02:20 o/ 20:02:32 hi y'all :) 20:02:42 diablo_rojo: around? 20:02:46 Happy Monday! 20:03:04 is it? 20:03:06 jungleboyj: this was evil of you! :) 20:03:16 That's optimistic 20:03:30 ildikov: Why? It has been a good Monday for me so far. 20:03:34 jaypipes: :) 20:03:42 so agenda for today: https://etherpad.openstack.org/p/openstack-upstream-institute-meetings 20:03:48 jaypipes: I am trying to be optimistic. 20:03:53 jungleboyj: :) 20:04:04 jungleboyj: I'm only aware of not bad Mondays... :) 20:04:31 ildikov: Atta Way! 20:04:32 so let's start! :) 20:04:40 #topic Announcements 20:05:03 the training is at the end of next week!!!!! 20:05:17 I'm freaked out, you shouldn't! :) 20:05:30 It is going to be great. 20:05:35 We got this 20:05:49 * jungleboyj high fives spotz 20:05:51 Hello :) 20:05:52 we still have work to do and figure out the hands on parts more, it's coming later in the agenda 20:06:09 update the content and do reviews! 20:06:24 yeah, I need to get on that. sorry I haven't been able to do that yet :( 20:06:40 jaypipes: Let me know if you need help buddy. 20:06:49 I will ping everyone who's signed up for Boston on the wiki this week to ensure we're all on the same page: https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute 20:06:55 There are 9 open reviews that need comments 20:06:58 jungleboyj: nah, just need to get on the reviews... 20:07:11 jaypipes: Ok. 20:07:16 diablo_rojo: ++ 20:07:21 jaypipes: no worries, whenever you can 20:07:45 if there's anyone around, who's able to attend the training and has not signed up on the wiki please go and update! 20:07:55 we have 65 registered students as of now 20:07:58 ildikov, +1 20:08:16 Nice. 20:08:29 I will send out a welcome, info and please confirm you're attending the training this week 20:08:35 ildikov: is that more or less than in Barcelona? 20:08:38 and hope for the best re response and show up rate 20:08:42 ildikov: I have tdasilva set up as a swift representative if we need someone for Swift. 20:08:45 mlavalle, a little less 20:08:55 We ended up qith about 90 people between the two days 20:09:02 wow 20:09:03 lots of people showed up that didnt register though 20:09:06 mlavalle: we had roughly 75 RSVP's for Barcelona and roughly almost 90 people showing up... :) 20:09:23 do we know their project interest already? 20:09:27 it was pretty unusual 20:09:36 mlavalle: we get there later today 20:09:36 mlavalle, yes we have that. 20:09:38 mlavalle: Yeah, was going to ask that. 20:09:45 Ok. 20:09:48 mlavalle, jungleboyj later on in the agenda :0 20:09:50 :) 20:09:56 stay tuned, we're just announcing right now :) 20:10:04 * mlavalle will not jump the gun again :-( 20:10:23 mlavalle: all good, we like excitement :) 20:10:23 diablo_rojo: Yeah, been jumping the gun today. 20:10:38 so we have a sign up etherpad for presenting topics: https://etherpad.openstack.org/p/boston-upstream-institute-presenters 20:10:43 #link https://etherpad.openstack.org/p/boston-upstream-institute-presenters 20:10:49 jungleboyj, meanwhile ildikov and I are scrambling today to get caught up frm last week 20:11:34 diablo_rojo: :-) 20:11:47 so jungleboyj was eager to take the how it's made parts, but I'm sure he's open to make a good deal if someone would like to jump in to that big block 20:11:55 I can take more sections to present or I can relinquish some if there are people who would rather talk. 20:11:55 jungleboyj: may I take a few items of How OpenStack is made? 20:12:10 vkmc_: Sure! 20:12:14 Happy to share. 20:12:33 jungleboyj: +1 20:12:40 Any preference? 20:12:57 vkmc_: with lots of sausage and spaghetti? ;) 20:13:00 vkmc_: jungleboyj: I think it's good if we have multiple people presenting, might help with keeping up people's attention as well to have some movement 20:13:13 jaypipes: lol 20:13:13 jaypipes, with beer? 20:13:17 Haha 20:13:20 diablo_rojo: ah, yes indeed :) 20:13:22 +1 to all that 20:13:28 Beer. 20:13:32 ildikov, +1 20:13:38 Ok, will add my name to the etherpad 20:13:40 somehow we should share this joy with the students as well 20:13:48 And we can later adjust it 20:13:54 Yaay 20:13:54 Need to change things up so people don't zone out. 20:13:55 these jokes always make me say out loud how much I like this community! 20:14:26 but back to track 20:14:41 vkmc_: You want to take governance and communication. 20:14:41 please add names to the etherpad and agree on who takes what on the final schedule 20:14:51 We can kind-of alternate? 20:14:59 I'm holding on to my 2!!!! 20:15:22 I would like to keep the official projects and release-cycle since I worked on the slides quite a bit. 20:15:31 Sounds good! 20:15:34 ok, you get 20 more seconds to discuss this and take the rest of the chats to the channel after the meeting plz :) 20:15:47 ildikov: Ok, we are done. :-) 20:16:08 jungleboyj: tnx :) 20:16:15 #topic Open reviews 20:16:19 Me and my excitement. 20:16:25 I want to take some of them, but I will be disappearing periodically for keynote practice so it might be hard. I can sign up for some and have someone be my understudy? 20:16:29 so I'm lazy, here you can find all: https://review.openstack.org/#/q/project:openstack/training-guides 20:16:33 #link https://review.openstack.org/#/q/project:openstack/training-guides 20:17:05 diablo_rojo: that should work, I think we have multiple people for each section, who can cover 20:17:31 I promise I'll check those out soon as well 20:17:46 Have been jumping around different things lately 20:17:48 I am going to respond to the current comments ASAP. 20:17:54 so please do reviews, I will ping our not too many cores to do their duties too 20:18:04 vkmc_: I hear ya! 20:18:22 ildikov: Thanks for looking through and merging some and commenting on others. 20:18:23 I think we're mostly good with the comments 20:18:32 I have some comments to respond to, but please make more! 20:18:33 is there anything to put up for discussion here? 20:18:37 nope 20:18:46 Hope all the updates I made last week are ok. 20:19:18 jungleboyj: I think I added comments to all by now, so we should be close either way 20:19:28 Great. Thanks. 20:19:34 I think I've been through them all if not poke with a specific one 20:19:51 spotz: Yeah, appreciated all the collaboration. 20:20:18 awesome, so I think we're looking good here 20:20:24 let's move forward with the agenda 20:20:33 #topic Topics 20:21:02 let's start with the areas to cover first as that's shorter than chatting about the slides 20:21:18 oh hi 20:21:25 so the list is on the etherpad as part of the agenda: https://etherpad.openstack.org/p/openstack-upstream-institute-meetings 20:21:33 ianychoi: hi, you're up early! 20:22:08 so we have quite a few areas to cover, I only added numbers to those, where we have only a few people interested in that specific area 20:22:33 ildikov, I am now transferring in SFO airport :) I need to go to Oslo - Norway before Summit and I would be unable to attend to upstream institute on Saturday :( 20:22:50 ianychoi: :( 20:22:52 the ones without numbers are more than 5 people 20:22:56 ianychoi: :( 20:23:05 ianychoi: are you still up for Sunday? 20:23:36 vkmc_: That is right, you are Manila and I have a swift candidate so I think we have all the storage covered. :-) 20:23:37 ianychoi: going to Boston through SFO from Norway sounds pretty cruel 20:23:42 So we NEED networking people, auth& security people, and containers people the most 20:23:43 ildikov, I will be back around afternoon Saturday so I will be on Sunday :) 20:24:11 knikolla: are you still available for Boston? 20:24:17 ildikov, and I will poke at liaisons for those projects, but if you know of anyone that is going early or in the area that works on them- rope those people in! 20:24:21 ildikov, yep but Korea <-> Norway and Korea <-> Boston are worse and Korea <-> Norway <-> Boston is so expensive.. T.T 20:24:27 ildikov: yes I am. 20:24:33 ildikov: I can see when a friend on Barbican is coming, it's been a year since I did anything with it 20:24:38 knikolla: to cover Keystone and maybe other parts as well 20:24:48 spotz, bring Igor! 20:24:58 I can ping some people later 20:25:01 spotz: would be great! 20:25:03 For the missing projects 20:25:09 ildikov: yes. it is the weekend before the summit right? 20:25:18 knikolla: yes 20:25:20 diablo_rojo: He replaced me as Heat engineer so he's not using it any more either:) 20:25:59 Checking with redrobot:) 20:26:41 I added the areas to the sections etherpad: https://etherpad.openstack.org/p/boston-upstream-institute-presenters 20:26:51 I am not sure if Brant Knudson is going to be in Boston. He could cover auth. 20:26:54 please check, I will try to clean it up a bit later 20:26:55 Oh you know who is going to be there. 20:27:02 Lance. 20:27:13 I will ping Lance for Auth. 20:27:18 when does he get in? 20:27:24 jungleboyj: we have knikolla as Keystone liaison 20:27:25 diablo_rojo: Checking. 20:27:33 SO long as they are there for Sunday that will be fine. 20:27:36 ildikov: Ok, never mind. 20:27:43 Since saturday will be less project specific 20:28:10 I know Lance likes this initiative, so if he can be around that's great of course 20:28:19 * redrobot pokes head in 20:28:29 jungleboyj: Yeah make Lance come! 20:28:38 I can poke him too ildikov:) 20:28:43 spotz: Ok. I will poke him. 20:28:46 so we have Storage, Auth and Compute covered 20:29:15 I've also hit up the barbican channel:) 20:29:22 spotz: jungleboyj: just don't be too pushy, we're a nice and friendly community not forcing people into things ;) 20:29:31 I would ask Flavio about containers, but I imagine he will be in the board meeting. 20:29:32 ildikov: They're my friends:) 20:29:42 spotz, thank you :) 20:29:47 spotz: jungleboyj vkmc_ : if you find more people plz add them to the wiki and the etherpad as well! 20:29:59 Sure thing 20:30:17 Do we have access to the list of people that RSVP? 20:30:19 redrobot won't get in until 2:( 20:30:26 ildikov: Will do. Wish we had Networking contacts. 20:30:27 And their main interests 20:30:27 spotz: jungleboyj: vkmc_: we need to have a rough idea how many people will be around from organizational perspectives, like catering, etc. 20:30:38 Yeah 20:30:43 vkmc_: yes, the list on the etherpad is built from their response 20:30:50 Awesome 20:31:04 ildikov: On the plus side if we don't have projects represented we can send folks to the onboarding rooms 20:31:10 I will add more numbers, just had some issues with the tools, so added indication to those topics, where we have only a very few people 20:31:28 Lance doesn't get in until 2 on Sunday. :-( 20:31:31 the rest is the we must have people in the room for those :) 20:31:41 we need to figure out Networking 20:32:06 diablo_rojo: Lenovo has Kolla contacts. I can have our guy reach out if Flavio can't help. 20:32:28 ildikov: I'm going to be there Sunday afternoon 20:32:32 I think Flavio was interested in coming too, he might be able to cover some containers stuff 20:32:58 mlavalle: I know 20:33:02 I could check with inc0 from kolla 20:33:12 jungleboyj, the more the merrier :) 20:33:26 :-) 20:33:34 mlavalle: do you know whether anyone else from the team might be around if people would be eager to ask a bit more specific questions during the first half of the training? 20:33:46 spotz: sounds good, tnx, I will ping Flavio 20:33:59 ildikov: no, I'll ask tomorrow morning during the weekly irc meeting 20:34:10 mlavalle: cool, thanks 20:34:32 mlavalle: there's a good chance we don't get to the deep dives until Sunday afternoon 20:34:47 mlavalle: unfortunately we don't have a reliable timing for the agenda yet 20:34:57 ildikov: what am I supposed to do during the deep dive? 20:35:03 which would be good in general, so that's on the "roadmap" for the team 20:35:05 We are going to rock the timing. 20:35:36 mlavalle: we will get to that in a second 20:35:58 * mlavalle jumping the gun again. bad mlavalle, bad! 20:36:23 mlavalle: tsk, tsk, tsk 20:36:40 mlavalle: sorry :) 20:36:54 just kidding :-) 20:37:06 ianychoi: if you'll be around and not too tired on Sunday I guess you can talk to people interested in docs, right? 20:37:38 mlavalle, lol 20:37:48 inc0 is texted 20:37:48 mlavalle: I know :) 20:38:17 ildikov, yep sure. I can talk docs part :) 20:38:18 I think we are roughly good with this part 20:38:25 ianychoi: cool, tnx 20:38:26 :-0 20:38:29 :-) 20:38:31 ildikov, yep 20:38:51 ianychoi: we had Christian having a docs deep dive with people in Barcelona, but he cannot come this time :( 20:39:08 ok, so let's move on to the content 20:39:16 ildikov, he now more focuses on Kolla :) I see 20:39:35 ianychoi: I know, he covered docs well too last time though 20:39:52 so we mentioned deep dives today, let's talk about that a bit 20:40:23 the idea/expectation for the last part of the training is to have small group sessions with the students 20:40:31 which are these deppe dives 20:40:39 s/deppe/deep/ 20:40:47 * ildikov cannot type anymore... 20:41:23 so what we tried to do last time was, showing people how we deal with the code or docs 20:41:24 too much BBQ.... 20:41:36 spotz: He he he. 20:41:40 spotz: right on the point :) 20:42:02 the aim is to show them how to run tests, how to and what to do with Devstack 20:42:14 ildikov: ++ 20:42:21 That was what my group was looking for. 20:42:37 how to test their modifications both unit/functional tests and how to test it in Devstack 20:42:52 great :) 20:43:11 we have ideas like download the code for a project, mess up something and let the team run the tests, find the failing ones and figure out what went wrong 20:43:30 they can get a cookie if they find it by themselves or smth :) 20:43:35 ildikov: Oh, we did talk about that. 20:43:47 That doesn't sound all bad. 20:44:09 ildikov: We could already have something broken that they clone so we can know how to debug it?:) 20:44:18 another thing is to figure out an exercise that would require adding new log messages and then restart the services and find them in the logs 20:45:25 spotz: I didn't mean to randomly break something there 20:45:53 spotz: Yeah, I think that was the idea. 20:45:57 spotz: or well, it would be ideal to have the mentors prepared with what to break, which tests will fail and how to debug the thing 20:46:00 I was just thinking of it from the troubleshooting side, if we knew ahead of time what is broken it's easier to guide them to fix it 20:46:11 so basically same thing:) 20:46:16 spotz: that's exactly the idea :) 20:46:45 spotz: it's another thing to get there with a team of cats to make these tings happen and be less on the fly style :) 20:46:46 Yep. Could even have them cherry-pick a patch that we have created that breaks things. Would demonstrate another skill. 20:47:00 ildikov: so each mentor can will come up with his / her own specific thing to do 20:47:05 right? 20:47:09 mlavalle: yes 20:47:12 Though, the smart ones can just look at the diff, but *shrug* 20:47:25 cool 20:47:26 mlavalle: we collect areas of interest so people can play with that code base they are actually interested in 20:47:35 mlavalle: I think we should all take an similar approach though. 20:47:35 mlavalle: also those services in Devstack, etc 20:48:07 jaypipes: vkmc_: knikolla: are you on board with the above ideas? 20:48:33 jungleboyj: yeah, I'll create a patch that breaks something and have them debug it 20:48:47 mlavalle: Sounds good. 20:48:49 ildikov: will have to read above as i wasn't here 20:48:52 mlavalle: sounds awesome, thanks! 20:48:56 Sounds good to me! 20:49:09 It will probably be more organized that way 20:49:22 knikolla: sure, you can ask on the channel too after the meeting if you need more info for this 20:49:37 vkmc_: you mean having a patch that breaks something? 20:50:15 ildikov: sure, fine by me. 20:50:28 jaypipes: cool, tnx 20:50:39 if jaypipes agrees, we are on the right track 20:50:45 Great! 20:51:03 mlavalle: :) 20:51:15 heh 20:52:07 All hail Lord Pipes! ;-) 20:52:28 I think it would be great to have some rough outlines for the deep dives 20:52:41 ildikov: ++ 20:52:50 if not before the training then summarizing it after as what work and what did not work 20:52:55 jungleboyj: lol 20:53:48 also I would like to ask every mentor to try to get all the students involved and let them and also encourage them to play with the environment and the code by themselves on their machine 20:54:01 ildikov, +1 20:54:12 Sounds good. 20:54:22 they will still miss the we don't fix a real bug experience 20:55:01 ildikov: We tried having some for git and gerrit it's just too hard to find enough of them they can do especially not knowing skill sets 20:55:11 I think we could theme this a bit, like having a Launchpad bug that describes the issue 20:55:53 they can get the patch that breaks the code on the training and they can upload their fix to the Sandbox project on Gerrit or smth like 20:56:13 or the description how they found the issue, or smth like 20:56:21 oooh nice 20:56:21 so they practice what they learned 20:56:29 +1 20:56:51 spotz: I don't like the fix real bug on the training idea to be honest 20:57:03 ildikov: That sounds good. 20:57:05 spotz: I think we need to be more "strategic" and educational than that 20:57:11 yeah it's not real doable 20:57:35 we do fake doc bugs and patches and reviews 20:57:39 agreed, so my thinking is do things like how we all do it in real life and give the students success 20:58:00 I have had a request from my team to cover more on git and rebasing changes but I just don't see a way to get that into the education. :-( 20:58:11 and also let them practice everything they learned on the way 20:58:35 jungleboyj: that's the lunch and learn maybe :) 20:58:53 and also telling people that sometimes they will need to cherry-pick anyhow... 20:58:53 ildikov: I think having a bug and pulling down a broken patch and then going through the process of fixing it and proposing a change for each project is great. 20:59:08 jungleboyj: awesome, tnx 20:59:43 Is there a way to do that in the Sandbox environment? 21:00:11 so homework for mentors to come up with a small patch that breaks something in their project, have a bug report for it the Sandbox project on Launchpad and then let the students rock! 21:00:17 jungleboyj: not on code level 21:00:46 Ok, so they can do part of it in the sandbox. 21:00:53 jungleboyj: I mean they can upload a diff a description of how they fixed the issue, but obviously we will not have the code base and test jobs there 21:00:55 I will figure it out. 21:01:05 ildikov: Right. 21:01:11 ok, time's up 21:01:12 That is all we need. 21:01:23 let's jump on the channel for further discussions 21:01:31 thanks everyone, great meeting! 21:01:33 Great meeting. thanks! 21:01:37 Thanks a lot all! 21:01:43 see most of you next week!!! :) 21:01:50 ciao :) 21:02:08 We still have one more meeting before the training 21:02:22 #endmeeting