Monday, 2017-04-10

*** gouthamr has quit IRC00:00
*** kzaitsev_mb has joined #openstack-meeting-300:04
*** stanzgy has joined #openstack-meeting-300:04
*** neiljerram has quit IRC00:10
*** bobh has joined #openstack-meeting-300:23
*** seanatcisco has joined #openstack-meeting-300:25
*** wanghao has joined #openstack-meeting-300:28
*** bobh has quit IRC00:30
*** kzaitsev_mb has quit IRC00:31
*** zhurong has joined #openstack-meeting-300:33
*** mariannelm has quit IRC00:36
*** krtaylor has joined #openstack-meeting-300:38
*** seanatcisco has quit IRC00:42
*** seanatcisco has joined #openstack-meeting-300:43
*** mickeys has quit IRC00:50
*** kiseok7 has joined #openstack-meeting-300:53
*** seanatcisco has quit IRC01:24
*** kzaitsev_mb has joined #openstack-meeting-301:27
*** seanatcisco has joined #openstack-meeting-301:28
*** dixiaoli has joined #openstack-meeting-301:38
*** huanxuan has joined #openstack-meeting-301:45
*** mickeys has joined #openstack-meeting-301:50
*** kzaitsev_mb has quit IRC01:56
*** mickeys has quit IRC01:56
*** zhurong has quit IRC01:58
*** tuanluong has joined #openstack-meeting-301:59
*** tuanluong_ has joined #openstack-meeting-302:02
*** tuanluong has quit IRC02:05
*** gouthamr has joined #openstack-meeting-302:05
*** zhurong has joined #openstack-meeting-302:10
*** kzaitsev_mb has joined #openstack-meeting-302:23
*** VW_ has joined #openstack-meeting-302:25
*** VW has quit IRC02:25
*** VW_ has quit IRC02:26
*** VW has joined #openstack-meeting-302:27
*** bobh has joined #openstack-meeting-302:27
*** kzaitsev_mb has quit IRC02:28
*** bobh has quit IRC02:32
*** yamamoto has joined #openstack-meeting-302:45
*** tuanluong has joined #openstack-meeting-302:47
*** tuanluong_ has quit IRC02:49
*** mickeys has joined #openstack-meeting-302:53
*** mickeys has quit IRC02:57
*** yamamoto has quit IRC03:01
*** gouthamr has quit IRC03:16
*** tenobreg has joined #openstack-meeting-303:18
*** tellesnobrega has quit IRC03:20
*** yamahata has joined #openstack-meeting-303:21
*** tellesnobrega has joined #openstack-meeting-303:23
*** kzaitsev_mb has joined #openstack-meeting-303:24
*** tenobreg has quit IRC03:24
*** apetrich has quit IRC03:26
*** apetrich has joined #openstack-meeting-303:27
*** bobh has joined #openstack-meeting-303:28
*** bobh has quit IRC03:32
*** mickeys has joined #openstack-meeting-303:53
*** kzaitsev_mb has quit IRC03:57
*** mickeys has quit IRC03:58
*** yamamoto has joined #openstack-meeting-304:01
*** VW has quit IRC04:03
*** anilvenkata has joined #openstack-meeting-304:04
*** markvoelker has joined #openstack-meeting-304:05
*** psachin has joined #openstack-meeting-304:09
*** kzaitsev_mb has joined #openstack-meeting-304:22
*** kzaitsev_mb has quit IRC04:27
*** bobh has joined #openstack-meeting-304:29
*** seanatcisco has quit IRC04:32
*** bobh has quit IRC04:33
*** mickeys has joined #openstack-meeting-304:54
*** mickeys has quit IRC04:58
*** ociuhandu has quit IRC05:00
*** ociuhandu has joined #openstack-meeting-305:01
*** bknudson_ has quit IRC05:01
*** kzaitsev_mb has joined #openstack-meeting-305:24
*** yamamoto_ has joined #openstack-meeting-305:42
*** yamamoto has quit IRC05:45
*** mickeys has joined #openstack-meeting-305:50
*** ociuhandu has quit IRC05:55
*** kzaitsev_mb has quit IRC05:57
*** gcb has joined #openstack-meeting-305:57
*** cshastri has joined #openstack-meeting-305:58
*** tuanluong has quit IRC06:00
*** pcaruana has joined #openstack-meeting-306:01
*** ociuhandu has joined #openstack-meeting-306:05
*** tobberydberg has joined #openstack-meeting-306:09
*** pgadiya has joined #openstack-meeting-306:13
*** tuanluong has joined #openstack-meeting-306:14
*** kzaitsev_mb has joined #openstack-meeting-306:22
*** amotoki has joined #openstack-meeting-306:23
*** kzaitsev_mb has quit IRC06:27
*** bobh has joined #openstack-meeting-306:31
*** ociuhandu has quit IRC06:31
*** rossella_s has quit IRC06:33
*** rossella_s has joined #openstack-meeting-306:34
*** andreas_s has joined #openstack-meeting-306:35
*** bobh has quit IRC06:35
*** ociuhandu has joined #openstack-meeting-306:44
*** yantarou has quit IRC07:01
*** yantarou has joined #openstack-meeting-307:02
*** MarkBaker has quit IRC07:05
*** dmellado has joined #openstack-meeting-307:08
*** mickeys has quit IRC07:08
*** reedip_ has quit IRC07:09
*** markvoelker has quit IRC07:12
*** ccamacho has joined #openstack-meeting-307:13
*** markvoelker has joined #openstack-meeting-307:15
*** MarkBaker has joined #openstack-meeting-307:17
*** dimtruck is now known as zz_dimtruck07:18
*** ltomasbo has joined #openstack-meeting-307:22
*** kzaitsev_mb has joined #openstack-meeting-307:24
*** MarkBaker has quit IRC07:25
*** bobh has joined #openstack-meeting-307:31
*** bobh has quit IRC07:36
*** reedip has joined #openstack-meeting-307:36
*** neiljerram has joined #openstack-meeting-307:37
*** MarkBaker has joined #openstack-meeting-307:38
*** shuyingya has joined #openstack-meeting-307:38
*** stendulker has joined #openstack-meeting-307:41
*** MarkBaker has quit IRC07:41
*** gcb has quit IRC07:46
*** lpetrut has joined #openstack-meeting-307:48
*** rmart04 has joined #openstack-meeting-307:49
*** kzaitsev_mb has quit IRC07:56
*** anilvenkata is now known as anilvenkata_afk07:57
*** MarkBaker has joined #openstack-meeting-307:59
*** rossella_s has quit IRC08:02
*** rossella_s has joined #openstack-meeting-308:06
*** rossella_s has quit IRC08:08
*** mickeys has joined #openstack-meeting-308:09
*** gcb has joined #openstack-meeting-308:12
*** mickeys has quit IRC08:14
*** rossella_s has joined #openstack-meeting-308:17
*** ralonsoh has joined #openstack-meeting-308:21
*** kzaitsev_mb has joined #openstack-meeting-308:22
*** kzaitsev_mb has quit IRC08:27
*** bobh has joined #openstack-meeting-308:32
*** bobh has quit IRC08:37
*** ociuhandu has quit IRC08:51
*** shu-mutou is now known as shu-mutou-AWAY08:59
*** ociuhandu has joined #openstack-meeting-309:00
*** mickeys has joined #openstack-meeting-309:10
*** tuanluong has quit IRC09:10
*** ociuhandu has quit IRC09:14
*** mickeys has quit IRC09:14
*** ociuhandu has joined #openstack-meeting-309:18
*** dixiaoli has quit IRC09:24
*** dixiaoli has joined #openstack-meeting-309:26
*** kzaitsev_mb has joined #openstack-meeting-309:27
*** sambetts|afk is now known as sambetts09:29
*** wanghao_ has joined #openstack-meeting-309:32
*** wanghao_ has quit IRC09:33
*** bobh has joined #openstack-meeting-309:33
*** wanghao has quit IRC09:36
*** bobh has quit IRC09:37
*** egallen has joined #openstack-meeting-309:41
*** rpi has joined #openstack-meeting-309:43
*** rpi has quit IRC09:45
*** rpi has joined #openstack-meeting-309:45
*** rpi has quit IRC09:48
*** rpi has joined #openstack-meeting-309:49
*** aarefiev_afk is now known as aarefiev09:59
*** kzaitsev_mb has quit IRC09:59
*** sdague has joined #openstack-meeting-310:10
*** mickeys has joined #openstack-meeting-310:11
*** mickeys has quit IRC10:16
*** gcb has quit IRC10:16
*** bobmel_ has quit IRC10:18
*** reedip has quit IRC10:23
*** reedip has joined #openstack-meeting-310:23
*** kzaitsev_mb has joined #openstack-meeting-310:24
*** bobmel has joined #openstack-meeting-310:24
*** ociuhandu has quit IRC10:25
*** bobmel has quit IRC10:29
*** kzaitsev_mb has quit IRC10:29
*** bobmel has joined #openstack-meeting-310:29
*** rossella_s has quit IRC10:33
*** bobh has joined #openstack-meeting-310:33
*** rossella_s has joined #openstack-meeting-310:34
*** bobh has quit IRC10:38
*** dixiaoli has quit IRC10:48
*** ociuhandu has joined #openstack-meeting-310:55
*** stendulker has quit IRC10:58
*** wanghao has joined #openstack-meeting-311:01
*** jtomasek_ has joined #openstack-meeting-311:03
*** bobmel has quit IRC11:04
*** sdague_ has joined #openstack-meeting-311:04
*** xavierr has quit IRC11:18
*** wanghao has quit IRC11:28
*** kzaitsev_mb has joined #openstack-meeting-311:28
*** xavierr has joined #openstack-meeting-311:33
*** bobh has joined #openstack-meeting-311:34
*** belmoreira has joined #openstack-meeting-311:36
*** bobh has quit IRC11:39
*** huanxuan has quit IRC11:42
*** anilvenkata_afk is now known as anilvenkata11:43
*** mtanino has joined #openstack-meeting-311:51
*** kzaitsev_mb has quit IRC12:00
*** VW has joined #openstack-meeting-312:05
*** mickeys has joined #openstack-meeting-312:05
*** mickeys has quit IRC12:09
*** markvoelker has quit IRC12:10
*** ccamacho is now known as ccamacho|lunch12:19
*** ltomasbo is now known as ltomasbo|away12:19
*** alexismonville has quit IRC12:20
*** ltomasbo|away is now known as ltomasbo12:21
*** markvoelker has joined #openstack-meeting-312:25
*** zhurong has quit IRC12:26
*** pgadiya has quit IRC12:26
*** gouthamr has joined #openstack-meeting-312:28
*** haleyb has quit IRC12:32
*** shuyingya has quit IRC12:34
*** krtaylor has quit IRC12:34
*** krtaylor has joined #openstack-meeting-312:37
*** gcb has joined #openstack-meeting-312:50
*** rmart04_ has joined #openstack-meeting-312:55
*** rmart04 has quit IRC12:56
*** rmart04_ is now known as rmart0412:56
*** rmart04 has quit IRC13:05
*** lyan has joined #openstack-meeting-313:08
*** shuyingya has joined #openstack-meeting-313:08
*** rmart04 has joined #openstack-meeting-313:08
*** rmart04 has quit IRC13:10
*** julim has quit IRC13:11
*** lyan has quit IRC13:12
*** lyan has joined #openstack-meeting-313:12
*** shuyingya has quit IRC13:13
*** shuyingya has joined #openstack-meeting-313:13
*** tonytan4ever has joined #openstack-meeting-313:14
*** haleyb has joined #openstack-meeting-313:15
*** baoli has joined #openstack-meeting-313:20
*** zz_dimtruck is now known as dimtruck13:22
*** rmart04 has joined #openstack-meeting-313:23
*** stanzgy has quit IRC13:25
*** rmart04 has quit IRC13:25
*** kzaitsev_mb has joined #openstack-meeting-313:26
*** bauwser is now known as bauzas13:27
*** rmart04 has joined #openstack-meeting-313:28
*** mtanino has quit IRC13:28
*** cleong has joined #openstack-meeting-313:30
*** rmart04 has quit IRC13:32
*** rmart04 has joined #openstack-meeting-313:32
*** edleafe- is now known as edleafe13:36
*** rmart04_ has joined #openstack-meeting-313:37
*** rmart04 has quit IRC13:38
*** rmart04_ is now known as rmart0413:38
*** dimtruck is now known as zz_dimtruck13:39
*** alexismonville has joined #openstack-meeting-313:48
*** ccamacho|lunch is now known as ccamacho13:50
*** kgiusti has joined #openstack-meeting-313:51
*** sdague has quit IRC13:52
*** crushil has joined #openstack-meeting-313:52
*** baoli has quit IRC13:52
*** shuyingya has quit IRC13:52
*** shuyingya has joined #openstack-meeting-313:53
*** sdague has joined #openstack-meeting-313:56
*** sdague__ has joined #openstack-meeting-313:56
*** ansmith has joined #openstack-meeting-313:56
*** therve has joined #openstack-meeting-313:58
*** julim has joined #openstack-meeting-313:59
gcb#startmeeting oslo14:00
openstackMeeting started Mon Apr 10 14:00:04 2017 UTC and is due to finish in 60 minutes.  The chair is gcb. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: oslo)"14:00
openstackThe meeting name has been set to 'oslo'14:00
gcbcourtesy ping for amotoki, amrith, bknudson, bnemec, dansmith, dhellmann, dims,dougwig, e0ne, electrocucaracha, flaper87, garyk, gcb, GheRivero,haypo, jd__, jecarey, johnsom, jungleboyj, kgiusti, kragniz, lhx_, lifeless, lxsli, Nakato, ozamiatin, rbradfor, redrobot,crushil, rloo,rpodolyaka, sergmelikyan, sileht, spamaps, sreshetnyak, sreshetnyak, stevemar,therve, thinrichs, toabctl, viktors, zhiyan, zzzeek14:00
amrith./14:00
crushil\o14:00
therveHi14:00
kgiustio/14:00
jungleboyjo/14:00
ansmitho/14:00
gcb\o/14:00
*** electrocucaracha has joined #openstack-meeting-314:01
gcb#topic Red flags for/from liaisons14:01
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"14:01
*** kzaitsev_mb has quit IRC14:01
amrithnothing to report for trove14:01
*** lhx_ has joined #openstack-meeting-314:01
jungleboyjNo red flags from Cinder.14:02
*** srobert has joined #openstack-meeting-314:02
gcbjungleboyj,  I have a patch to fix periodic task for Cinder  https://review.openstack.org/455152 , we recently merged https://review.openstack.org/32869214:02
gcbthanks amrith14:03
gcbjungleboyj,  hope we can merge it before  we release new version of oslo.config14:03
*** rbak has joined #openstack-meeting-314:03
*** baoli has joined #openstack-meeting-314:03
jungleboyjgcb: Ok, Thank you for the update.  Let me take a look.14:04
gcbthanks jungleboyj14:04
jungleboyjgcb:  Was that a red flag I missed?  ;-)14:04
gcbjungleboyj,  check http://status.openstack.org/openstack-health/#/g/build_name/periodic-cinder-py27-with-oslo-master14:05
shuyingyao/14:06
* jungleboyj makes a note to start checking that page. :-)14:06
gcbhttps://review.openstack.org/328692 will break Cinder once we release new version of oslo.config. It doesn't break Cinder now14:06
gcbshuyingya, welcome14:06
gcbI didn't find other failure in our periodic jobs14:06
gcblet's move on14:07
gcb#topic Releases for Pike14:07
*** openstack changes topic to "Releases for Pike (Meeting topic: oslo)"14:07
gcb#link https://review.openstack.org/455318  actually I would like to hold on until tomorrow14:08
*** baoli has quit IRC14:08
gcbwe just merged some commits after today's periodic jobs, so let them pass tomorrow's periodic jobs and release14:09
*** shuyingya has quit IRC14:09
gcb#topic  Stuck Reviews14:09
*** openstack changes topic to "Stuck Reviews (Meeting topic: oslo)"14:09
*** shuyingya has joined #openstack-meeting-314:09
gcbI have one  to fix oslo.middleware gate failure in https://review.openstack.org/#/c/453712/14:10
gcbplease help review when you're free14:11
gcbDoes anyone have other stuck reivews ? :-)14:11
*** baoli has joined #openstack-meeting-314:12
gcb#topic Open discussion14:12
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"14:12
*** sdague has quit IRC14:12
gcbso please raise if you have anything to talk14:13
lhx_haha, I have just one14:13
lhx_https://review.openstack.org/#/c/454244/14:13
*** sdague__ is now known as sdague14:13
lhx_thanks in advance for reviewing14:13
gcbhttps://review.openstack.org/#/c/454244/ should be reviewed by release management team , not oslo team lol14:14
gcbthough Doug is in both of these two teams14:14
gcblhx_ ^^14:15
lhx_right, lol14:15
*** zz_dimtruck is now known as dimtruck14:15
lhx_someone in both sides can help14:15
kgiustifyi - the boston forum schedule was posted14:16
kgiustioslo dev/op feedback is on Weds 9am14:16
*** mtanino has joined #openstack-meeting-314:16
gcbkgiusti, thanks, I didn't check that before14:16
kgiustigcb: just hit my inbox :)14:17
gcbkgiusti, yeah, will check the details later, so please bring your new ideas, paint points there14:18
lhx_gcb, http://lists.openstack.org/pipermail/openstack-dev/2017-April/115174.html14:18
gcbI mean everyone, not just kgiusti lol14:18
kgiustithanks lhx_!14:19
gcblhx_, cool14:19
lhx_kgiusti, gcb, with little effort, lol14:20
gcbs/paint/pain14:20
gcbany other ?14:21
gcbIt seems a short meeting today14:22
gcbokay, thanks everyone14:23
gcb#endmeeting14:24
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:24
openstackMeeting ended Mon Apr 10 14:24:04 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:24
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-04-10-14.00.html14:24
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-04-10-14.00.txt14:24
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-04-10-14.00.log.html14:24
jungleboyjThank you.14:24
lhx_Thanks :)14:24
*** electrocucaracha has left #openstack-meeting-314:25
*** VW has quit IRC14:26
*** kgiusti has left #openstack-meeting-314:26
*** VW has joined #openstack-meeting-314:26
*** VW has quit IRC14:27
*** lucasxu has joined #openstack-meeting-314:27
*** VW has joined #openstack-meeting-314:27
*** shuyingya has quit IRC14:28
*** tobberydberg has quit IRC14:32
*** rossella_s has quit IRC14:33
*** rossella_s has joined #openstack-meeting-314:34
*** therve has left #openstack-meeting-314:36
*** alexismonville has quit IRC14:38
*** mariannelm has joined #openstack-meeting-314:43
*** galstrom_zzz is now known as galstrom14:43
*** belmoreira has quit IRC14:46
*** bobh has joined #openstack-meeting-314:51
*** baoli has quit IRC14:51
*** milan has joined #openstack-meeting-314:54
*** tobberydberg has joined #openstack-meeting-314:54
*** scottda has joined #openstack-meeting-314:57
*** rbrady has joined #openstack-meeting-314:58
*** tobberydberg has quit IRC14:58
*** rmart04 has quit IRC14:58
*** toure has joined #openstack-meeting-314:59
*** sharatss has joined #openstack-meeting-315:00
*** yamahata has quit IRC15:00
rakhmerov#startmeeting Mistral15:00
openstackMeeting started Mon Apr 10 15:00:18 2017 UTC and is due to finish in 60 minutes.  The chair is rakhmerov. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: Mistral)"15:00
openstackThe meeting name has been set to 'mistral'15:00
*** yamahata has joined #openstack-meeting-315:00
d0ugalhey!15:00
tourehello15:01
*** thrash|bbl has joined #openstack-meeting-315:01
rakhmerovhey15:01
rbradyhi15:01
sharatssHi15:01
rakhmerov1 sec..15:01
rakhmerovsharatss: hi15:01
rakhmerovsharatss: I looked at the new BP you created, I think we'll need to split it into several smaller BPs15:02
rakhmerovok, mgershen won't join today, she's on holidays15:02
rakhmerovlet's start15:02
rakhmerov#topic Review Action Items15:02
*** openstack changes topic to "Review Action Items (Meeting topic: Mistral)"15:03
sharatssrakhmerov, ok. I will change it tomorrow15:03
rakhmerovsharatss: leave it to me pls15:03
rakhmerovinstead, try to get your patches merged this week15:04
rakhmerov1. d0ugal to check for doc liaison tasks15:04
rakhmerov:)15:04
sharatssrakhmerov, sure :)15:04
rakhmerovd0ugal: is there any update on that?15:04
rakhmerovit's not that important but anyway..15:04
*** baoli has joined #openstack-meeting-315:04
*** thomasem has joined #openstack-meeting-315:04
d0ugalrakhmerov: yeah, so they want us to add Mistral to the installer docs15:05
d0ugalmost or all other projects are included in it - we are not yet :)15:05
rakhmerovooh, do you know details/guidelines on how to it?15:05
d0ugalNot yet, I just know it is something we should look into doing15:05
rakhmerov..how to do it..15:05
d0ugalI wasn't sure where to track this work.15:05
d0ugalhttps://docs.openstack.org/project-install-guide/ocata/15:06
rakhmerovok, then pls try to find out more15:06
d0ugalThat is where we want to be included I think15:06
rakhmerovok15:06
d0ugalShould I open a Mistral bug/blueprint for this?15:06
rakhmerovyes, please15:06
rakhmerov2. mgershen: create a BP about "on-error" semantics15:06
rakhmerovnot done yet AFAIK15:06
rakhmerov#action mgershen: create a BP about "on-error" semantics15:06
rakhmerov#topic Current Status (by team members)15:07
*** openstack changes topic to "Current Status (by team members) (Meeting topic: Mistral)"15:07
rakhmerovlet's quickly share our updates15:07
d0ugalhttps://blueprints.launchpad.net/mistral/+spec/mistral-os-install-docs15:08
rakhmerovmy status: last week I worked mostly on Java Mistral client for OpenStack4J (driven by internal tasks mostly) and advanced publishing (global, branch, atomic)15:08
rakhmerovthe latter is mostly done, will try to finish this week15:08
rakhmerovd0ugal: thanks15:08
d0ugalI made a few documentation improvements - they need a second +2: https://review.openstack.org/453542 https://review.openstack.org/454058 https://review.openstack.org/454057 https://review.openstack.org/45354315:09
rakhmerovd0ugal: I tentatively assigned it to P-2 but we'll decide when to do it exactly later during planning15:09
d0ugalOtherwise I have been working on making an rpm package for mistral-lib and I am working on mistral-extra, but I've not done much of that yet.15:10
rakhmerovd0ugal: yeah, Michal is on holidays this week so please try to ping other cores (kong, ddeja etc.)15:10
*** dosaboy has quit IRC15:10
*** baoli has quit IRC15:10
rakhmerovyou've created a good spec though, this is a good progress IMO15:10
rakhmerovrbrady, toure, sharatss: what about you guys?15:11
rbradyI've done some reviews since last time, but have been otherwise engaged with work for other projects.15:11
rakhmerovd0ugal: so you started moving OpenStack actions into mistral-extra?15:11
rakhmerovrbrady: ok15:11
sharatssrakhmerov, i have been trying to fix all the dashboard bugs which were pending from long time15:12
rakhmerovrbrady: any progress on your brewery idea? :)15:12
d0ugalrakhmerov: yeah, I am trying to - that is why I asked for the mistral-lib release, without those parts it is hard :)15:12
rakhmerovsharatss: yeah, I saw, we'll try to merge them this week15:12
thrash|bblhttps://review.openstack.org/#/c/450853/ Looks like all comments have been addressed.15:13
rakhmerovI'll ask people to review them15:13
rbradyrakhmerov: I started rebuilding the main controller this weekend15:13
thrash|bblStill working on using mod_wsgi in devstack.15:13
tourestatus: completed some reviews, working on the last bits of mistral engine changes for error analysis.15:13
*** crushil has quit IRC15:13
rakhmerovthrash|bbl: ok, I'll review it again tomorrow morning (your today's evening)15:13
rakhmerovthanks15:13
rakhmerovrbrady: cool :)15:14
tourerakhmerov I took your suggestion and created a method to make calls into workflow_exec and task_exec inside db_api15:14
*** chyka has joined #openstack-meeting-315:14
rakhmerovok15:14
touretesting changes :)15:14
rakhmerovtoure: is there anything from that's pending review now?15:14
rakhmerovok, awesome :)15:14
rakhmerov..from you..15:15
toureonce it doesn't blow up :)15:15
toureI have the client side up15:15
rakhmerovok15:15
* toure grabs review15:15
toure#link https://review.openstack.org/#/c/452901/15:15
rakhmerovI mean please let us know once you post something new and we need to review it15:16
rakhmerovok15:16
tourewill do15:16
rakhmerovI'll look into this tomorrow morning too15:16
rakhmerovok, thanks for updates15:16
tourenp15:16
rakhmerovany roadblocks that you guys hit and need help maybe?15:17
rakhmerovthrash|bbl: how's that apache wsgi thing going?15:17
rakhmerovand could you pls tell a little bit what exactly you're planning to achieve15:18
rakhmerov?15:18
rakhmerovok, maybe later15:18
rakhmerovlet's move to the next topic15:19
d0ugal:)15:19
rakhmerov#topic Pike-1 progress15:19
*** openstack changes topic to "Pike-1 progress (Meeting topic: Mistral)"15:19
d0ugalI think the goal is to have a new gate that tests Mistal in a wsgi setup15:19
rakhmerovyes, but what tests are we supposed to run there, what DB etc.15:19
rakhmerovI kind of see the idea but would like to have more details15:20
d0ugalah, I see15:20
d0ugalThere is a patch for it, rbrady had the link earlier.15:20
rakhmerovnp, we can discuss that later15:20
rakhmerovok15:20
rakhmerovso, the page for P-1: https://launchpad.net/mistral/+milestone/pike-115:20
rbradyhttps://review.openstack.org/#/c/454710/15:20
*** thrash|bbl is now known as thrash15:20
d0ugalrbrady: thanks.15:20
rakhmerovI've gone through the list of tickets today and updated some of them but I'd like you to look at it too and make sure your tasks are updated15:21
*** anilvenkata has quit IRC15:21
rakhmerovfor example, rbrady, d0ugal: do you think we can close https://blueprints.launchpad.net/mistral/+spec/mistral-actions-api-main-entities ?15:21
rakhmerovto me it seems like yes but I'd like to run with you15:22
thrashrakhmerov: The only coverage on apache wsgi is via the puppet jobs. I think it would be prudent to have both apache and non-apache devstack jobs. Once the initial part is done (which is the enabling of apache in the plugin) we can talk about how else to vary the jobs.15:22
d0ugalrakhmerov: I would like to see the mistral-lib release happen first, but I don't mind if we close it first.15:22
*** dosaboy has joined #openstack-meeting-315:23
rakhmerovthrash: makes sense, I agree. I thought may be you already have a comprehensive plan (naive me)15:23
rbradyrakhmerov: the work items in the BP suggest ensuring the mistral is using mistral-lib, but I don't have any objections to closing either15:23
*** lyan has quit IRC15:23
thrashrakhmerov: no comprehensive plan. Really just a means to an end ATM (running tempest on devstack with apache wsgi enabled)15:24
rakhmerovwait a sec, not sure that mistral-lib should be used15:24
rakhmerovit's just main entities in mistral-lib itself as far as I can tell15:24
rakhmerovthrash: ok15:24
*** chyka has quit IRC15:24
d0ugalrakhmerov: what do you mean by "not sure that mistral-lib should be used"?15:24
*** chyka has joined #openstack-meeting-315:25
rakhmerovI mean IMO refactoring other components to use mistral-lib is out of this ticket scope15:26
rakhmerovI wasn't clear enough15:26
d0ugalrakhmerov: okay, fine with me15:26
rakhmerovyeah, so it's the first step towards getting the task fully implemented15:26
rakhmerovlet's close it15:26
rakhmerovof course, we'll be making tons of changes moving forward anyway15:27
d0ugalyeah15:27
*** kzaitsev_mb has joined #openstack-meeting-315:27
*** aarefiev is now known as aarefiev_afk15:27
rakhmerovon other things, d0ugal and toure: I know it might not be fair but how about creating separate BPs for specs related to your tasks (mistral-extra and workflow analysis) and moving existing BPs to P-2?15:28
rakhmerovI'm just thinking how to track this work better15:29
rakhmerovwe've done work on these tasks but if we just move these BPs to the next milestone we'll not see a trace in LP15:29
rakhmerovd0ugal, toure: what do you think?15:29
rakhmerovI don't know, on the other hand it's kind of weird to create BPs for writing specs15:30
rakhmerov:)15:30
d0ugalrakhmerov: I have done very little work other than the spec itself - so I don't think there is anything worth tracking for P-1. Moving the blueprint to P-2 seems easiest.15:30
rakhmerovthen ok, let's do it15:30
d0ugalIndeed, I see a one to one relationship between blueprints and specs15:30
rakhmerovunless you make sure to finish it in P-115:30
rakhmerov:)15:30
tourerakhmerov sounds good to me15:31
d0ugal(there could be other dependant blueprints, but one main blueprint)15:31
rakhmerovok15:31
d0ugalhah, I wont be finished for P-1!15:31
rakhmerovyeah, d0ugal, I now remember that this was our plan15:31
rakhmerovjust to move it to the next milestone15:31
rakhmerov:)15:31
toureby sounds good, I mean moving it to p2 :)15:32
rakhmerovok15:32
rakhmerov:)15:32
rakhmerovgot it15:32
toures/mean/meant15:32
rakhmerovd0ugal: did you happen to send another patchset for https://blueprints.launchpad.net/mistral/+spec/mistral-engine-commands-docs today?15:33
rakhmerovas we talked15:33
rakhmerovthis one is a good candidate to be closed soon15:33
d0ugalrakhmerov: not yet, today has been a bit crazy for me. I'll do it soon.15:33
d0ugalMaybe right after this meeting :)15:33
rakhmerovok, np15:33
rakhmerovok, so, again: please try to finish hanging patches this week15:34
rakhmerovespecially d0ugal and sharatss, you have a bunch of them )15:34
rakhmerovI guess we just need to ask people for more reviews15:34
rakhmerovthanks15:35
d0ugalWe need more core reviewers :)15:35
rakhmerovd0ugal: yes, we do need them15:35
rakhmerovit's a different topic though15:35
rakhmerovok, thanks15:36
rakhmerovthere's one more thing I'd like to discuss with you quickly15:36
rakhmerovI mentioned it last week briefly15:36
rakhmerov#topic Mistral Goals 201715:36
*** openstack changes topic to "Mistral Goals 2017 (Meeting topic: Mistral)"15:36
*** crushil has joined #openstack-meeting-315:36
rakhmerovhttps://etherpad.openstack.org/p/mistral-goals-201715:37
*** egallen has quit IRC15:37
rakhmerovI created this etherpad based on our internal discussions on how we see project goals for Mistral that we want to achieve in 201715:37
*** cshastri has quit IRC15:38
rakhmerovso, I spent time thinking about 3-4 goals that would make a difference for the project in general if we focus on them with the resources we have now15:38
rakhmerovand here's what I came up with15:38
rakhmerovyou can omit "Definition of done" for now and just read quickly titles and descriptions15:39
* d0ugal reads15:39
rakhmerovbasically, I think these goals reflect my vision of what's really missing now in Mistral15:40
*** baoli has joined #openstack-meeting-315:40
rakhmerovso IMO if we achieve them we'll be able to 1) attract more users 2) attract more contributors 3) extend use cases where Mistral can be used15:40
rakhmerovand I'd add even one more: GUI15:41
rakhmerovbut I believe it'll go to the next year :)15:41
rakhmerovespecially, I'd say the two most important ones: Custom Actions API and Documentation15:41
rakhmerovthese two IMO should make Mistral more like a good product15:42
* toure reads15:42
rakhmerovon docs, we see lots of people coming to IRC and asking questions that they could read in docs but what they are looking for is not there pretty often15:42
*** makowals_ has joined #openstack-meeting-315:43
d0ugalrakhmerov: so you want to make workflows 50% faster?15:43
rakhmerovalso, even when it becomes comprehensive it's not structured well and there are not many examples and tutorials (almost none)15:43
d0ugalis that the goal for number 3?15:43
rakhmerovd0ugal: yes15:43
d0ugalk, just checking I read it correctly15:43
*** makowals has quit IRC15:43
d0ugalSounds good.15:43
rakhmerovd0ugal: believe it or not the current Mistral performance is not really OK still for our internal purposes15:43
rakhmerovand not only ours15:44
rakhmerovd0ugal: yes, 50% seems achievable15:44
d0ugalrakhmerov: oh, I believe it :) I've noticed it being quite slow at some things, but my main use-case it IO bound anyway, so speed isn't a huge issue for us.15:44
*** galyna has joined #openstack-meeting-315:44
rakhmerovand I know where to gain that extra performance15:44
rakhmerovyes, I know15:44
rakhmerovfor you maybe, but for us and some other folks it's an issue15:45
d0ugalThose goals sound good to me.15:45
rakhmerovalthough it got much much better last year15:45
rakhmerov~50-70 times15:45
d0ugalI would really like to improve the "on-boarding" expierence for new users - I think documentation improvements and the new custom actions API will make a huge difference here15:46
rakhmerovyeah, Custom Actions API, in my opinion, will give a clear way to extend Mistral actions15:46
rakhmerovwhich is missing now too15:46
d0ugalbut that is my personal goal, so I am particularly interested in #2 and #4 :)15:46
rakhmerovd0ugal: exactly, that's what I have in mind15:46
rakhmerovyou got it15:46
rakhmerovit's my personal goal too15:46
rakhmerovI think we as a project are suffering a lot from this15:47
rbradyis there a priority to these goals?15:47
*** lpetrut has quit IRC15:47
rakhmerovbtw, d0ugal, what you've been doing in your blog could be a part of this work I believe15:47
rakhmerovin fact, it already is15:47
toure+Docs :)15:47
rakhmerovrbrady: hm.. good question15:48
rakhmerovI think Documentation and Actions API15:48
rakhmerovtop 215:48
d0ugalThe funny thing is, I am really bad at writing, but I'll try and do more (and slowly improve) :)15:48
rakhmerovthat's ok15:48
*** psachin has quit IRC15:48
rakhmerovbtw, seems like Nokia is ready to give tech writers for this purpose15:49
d0ugalGreat15:49
rakhmerovbut I'm not sure yet15:49
rakhmerovanyway we'll need to help them with ideas/materials15:49
rakhmerovrough materials15:49
d0ugalI wonder if we have anyone that could help. I should ask.15:49
rbradyd0ugal: rain15:49
rbradyd0ugal: rleander I think15:49
rakhmerovd0ugal: what you said is actually even a simpler form of what I want to do: "Easy Mistral contributor and user onboarding"15:50
rakhmerovnot it's not easy, we need to admit15:50
d0ugalrbrady: true, there are quite a few people. Maybe I should have said ... s/could help/has time to help/ :)15:50
*** ccamacho is now known as ccamacho|brb15:51
rakhmerovas far as multi-node mode, there's a lot of things too but that's important for those who want high-availability and even greater performance15:51
rakhmerovlike us15:51
rakhmerovand at least slowly we need to be moving in this direction15:52
rakhmerovso, that's what I suggest we accept as project goals for this year kind of semi-officially15:52
rakhmerovfor our team15:52
rakhmerovand that could be our bacon in the darkness when we need to make decisions15:53
rakhmerovplease take more time to review this list and leave your comments/suggestions, after that we can move these goals to WIKI (or somewhere else) so we could reference them if needed15:54
rbradyrakhmerov: that needs to be an official mistral shirt: "bacon in the darkness"15:54
rakhmerovyeah, :))15:54
d0ugalLOL15:54
d0ugalyum15:54
rakhmerovI like poetry )15:54
toure:)15:54
rakhmerovIf I get sick of programming (really possible ;) ) I'll be writing poems15:55
d0ugalrakhmerov: I would put them somewhere more visible - Mistral readme or a special spec?15:55
rakhmerovI believe I even write code like poems sometimes.. :)15:55
d0ugalI would read more poetry if it was about bacon :)15:55
rakhmerovd0ugal: yeah, that's what I'm thinking too15:56
tourehehe15:56
rakhmerovbeacon!!!!!15:56
rakhmerovgosh15:56
rakhmerovjust realized why it was so funny for you :)15:56
rakhmerovhaha15:56
d0ugallol15:56
rakhmerovbut yeah, "bacon" would be phenomenal!15:56
rakhmerovlol15:57
tourelol15:57
rakhmerov:))))15:57
rakhmerovok, d0ugal: do you think README?15:57
*** seanatcisco has joined #openstack-meeting-315:57
d0ugalrakhmerov: yeah, I think that would be good15:57
rakhmerovd0ugal: let's think about it more15:57
*** iyamahat has joined #openstack-meeting-315:57
d0ugalI don't like the wiki :)15:57
rakhmerovd0ugal: yes, we almost don't use it now actually15:58
toureyeah wiki's tend to go stale15:58
rakhmerovwe used to but not anymore15:58
d0ugalI always forget it exists15:58
rakhmerovyep15:58
rakhmerovok, README probaly15:58
rakhmerovor mistral-specs somewhere maybe15:58
rakhmerovor/and15:58
rakhmerovok, let me take care of that15:58
*** marst has joined #openstack-meeting-315:59
rakhmerovso, time to finish15:59
rakhmerovthanks everyone for joining15:59
rakhmerovit was fun15:59
d0ugalthanks!15:59
tourethanks,have a great week...15:59
rakhmerovespecially "bacon in the darkness" :)15:59
thrashthanks o/15:59
toure:)15:59
rakhmerovbye!15:59
rakhmerov#endmeeting15:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"15:59
openstackMeeting ended Mon Apr 10 15:59:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-04-10-15.00.html15:59
rbradybye15:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-04-10-15.00.txt15:59
openstackLog:            http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-04-10-15.00.log.html15:59
rakhmerovhave a good week15:59
*** thrash has left #openstack-meeting-315:59
*** lucasxu has quit IRC16:00
*** toure has left #openstack-meeting-316:00
*** mickeys has joined #openstack-meeting-316:01
*** kzaitsev_mb has quit IRC16:02
*** mickeys has quit IRC16:05
*** sharatss has quit IRC16:06
*** galyna has left #openstack-meeting-316:06
*** galyna has joined #openstack-meeting-316:06
*** andreas_s has quit IRC16:07
*** mickeys has joined #openstack-meeting-316:09
*** lyan has joined #openstack-meeting-316:11
*** reedip_ has joined #openstack-meeting-316:15
*** ankur-gupta-f1 has quit IRC16:17
*** Patifa has joined #openstack-meeting-316:21
*** ltomasbo is now known as ltomasbo|away16:22
*** lamt has joined #openstack-meeting-316:30
*** tonytan4ever has quit IRC16:35
*** abalutoiu has joined #openstack-meeting-316:35
*** fellypefca has joined #openstack-meeting-316:38
*** guest303018 has joined #openstack-meeting-316:39
*** lamt has quit IRC16:42
*** stendulker has joined #openstack-meeting-316:43
*** ricardoas has joined #openstack-meeting-316:46
*** lhx_ has quit IRC16:50
*** diablo_rojo has joined #openstack-meeting-316:50
*** rloo has joined #openstack-meeting-316:53
*** Saulo_Aislan has joined #openstack-meeting-316:54
*** Saulo_Aislan has quit IRC16:54
*** sauloaislan has joined #openstack-meeting-316:55
*** mrtenio has joined #openstack-meeting-316:55
*** mariojv has joined #openstack-meeting-316:56
*** dtantsur has joined #openstack-meeting-316:56
*** lee4 has joined #openstack-meeting-316:57
*** wanyen has joined #openstack-meeting-316:58
*** rossella_s has quit IRC16:59
*** rpioso has joined #openstack-meeting-316:59
dtantsuranyone up for an ironic meeting? :)16:59
xavierro/16:59
ricardoaso/16:59
mariojvo/16:59
thomasemo/16:59
mrtenioo/17:00
dtantsur#startmeeting ironic17:00
mjtureko/17:00
openstackMeeting started Mon Apr 10 17:00:02 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
lee4 o/17:00
fellypefcao/17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: ironic)"17:00
openstackThe meeting name has been set to 'ironic'17:00
*** tonytan4ever has joined #openstack-meeting-317:00
sauloaislano/17:00
rama_yo/17:00
rpiosoo/17:00
crushil\o17:00
dtantsurHi everyone!17:00
rloohowdy17:00
milano/17:00
*** aNuposic has joined #openstack-meeting-317:00
*** soliosg has joined #openstack-meeting-317:00
dtantsurour agenda (quite light) is as usual at:17:01
dtantsur#link https://wiki.openstack.org/wiki/Meetings/Ironic17:01
*** bfournie has joined #openstack-meeting-317:01
stendulkero/17:01
dtantsur#topic Announcements / Reminders17:01
*** openstack changes topic to "Announcements / Reminders (Meeting topic: ironic)"17:01
*** nicodemos has joined #openstack-meeting-317:01
alezilI/17:01
dtantsur#info Boston Forum schedule was published17:02
jroll\o17:02
dtantsur(with some mistakes to be corrected, apparently)17:02
sambettso/ o/17:02
* dtantsur does not have a link at hand17:02
*** lee4 has quit IRC17:02
nicodemoso/17:02
soliosgo/17:02
*** lucasxu has joined #openstack-meeting-317:02
*** lee4 has joined #openstack-meeting-317:02
*** galyna1 has joined #openstack-meeting-317:02
dtantsurI don't have other announcements. Anyone?17:02
dtantsurah, hmm17:03
dtantsur#info dtantsur is on PTO starting from Fri, Apr 14. Back on Mon, Apr 2417:03
dtantsuryes, again :)17:03
jrollwoohoo17:03
milan:)17:03
rloodtantsur: wow, lucky you!17:03
dtantsurI think a few more folks are going to be out the same week, right? TheJulia at least17:03
jrollI'll be out tues-thurs this week, btw17:04
jrolljulia as well17:04
jroll(leadership training)17:04
JayFo/17:04
dtantsurthanks! let's keep it in mind when defining priorities for the coming weeks17:04
*** abalutoiu has quit IRC17:04
dtantsur#info a suggestion for a virtual meetup: https://etherpad.openstack.org/p/ironic-virtual-meetup17:04
rloojroll: would you chair next Mon's meeting?17:04
rloojroll: please :)17:05
jrollrloo: sure, why not17:05
dtantsurthanks jroll!17:05
*** baha has joined #openstack-meeting-317:05
* rloo going to see if there is any diff with jroll's leadership...17:05
*** abalutoiu has joined #openstack-meeting-317:05
jroll3 cycles of history not enough? :P17:05
dtantsurhah, rloo is already preparing for the next elections :)17:06
rloojroll: but the leadership course...!!17:06
jrolloh, that17:06
dtantsurah, yeah. fair :)17:06
jrollI've been once already, I'm helping connect dots17:06
rloo:)17:06
dtantsurplease have one in EU, and I'll attend. otherwise you'll have to live with my terrible leadership for some more time :-P17:06
dtantsuranyway, another request to take a look at the virtual meetup proposal: https://etherpad.openstack.org/p/ironic-virtual-meetup17:07
rloowrt virtual meetup. with dtantsur and TheJulia gone next week. Am wondering whether we should punt it another week.17:07
dtantsurrloo, it's proposed for week of Apr 2417:07
joannao/17:07
dtantsuras it was suggested on the previous meeting17:07
rloodtantsur: right, you and TheJulia will have just come back. will you be prepared to participate?17:07
TheJuliaI will be17:07
* TheJulia re-engages the cloaking device17:07
dtantsuralways prepared :) I'm not going anywhere, just hanging out here in Brno17:08
dtantsurtrying to reduce stress by examining the nearby bars17:08
TheJuliadtantsur: That sounds like an awesome plan17:08
milandtantsur, +200017:08
dtantsurwe can get back to the meetup topic in the open discussion. any other announcements?17:08
*** amotoki has quit IRC17:09
* milan announces lack of sleep :P17:09
dtantsur:)17:09
dtantsur#topic Review subteam status reports (capped at ten minutes)17:09
*** openstack changes topic to "Review subteam status reports (capped at ten minutes) (Meeting topic: ironic)"17:09
dtantsur#link https://etherpad.openstack.org/p/IronicWhiteBoard17:09
dtantsurstarting with line 7517:10
rloo(oh, was it last week that we did an ironic release?)17:10
dtantsuryeah, probably17:10
jrollyes, april 517:10
jroll8.0.0 specifically17:11
*** Nisha_Agarwal has joined #openstack-meeting-317:11
JayFOnly three more major releases and we'll be better than windows! /s17:11
rlooJayF: huh, aren't we better already?17:11
JayFrloo: Windows is 10, we're only 8!17:11
*** mgould has joined #openstack-meeting-317:11
dtantsurFirefox is 52..17:12
xavierrlol17:12
rlooJayF: but we're better, regardless ;)17:12
mrteniorloo, agreed17:12
JayFI was joking, obviously :)17:12
dtantsur"jroll promises to look at this week of march 27" I wonder if he did ;)17:12
dtantsur(line 154)17:12
jrolldamn, no I did not17:12
* jroll bumps on todo list, sorry17:13
dtantsurrolling upgrades: "make a change to the grenade job to only upgrade conductor" (from the priority list)17:14
dtantsurwas it done?17:14
rloojroll: related to last week and these priorities. you were going to review the nova stuff to see if there is anything we need to do b4 nova's feature proposal freeze17:14
jrollrloo: yes, I instead did paperwork all week. I've got it docketed for today17:15
* jroll hasn't had much time for upstream, sorry17:15
rloovdrok: ^^ do you know what the status is with multi-node grenade testing changes?17:15
rloojroll: ok, i'll try to remember to ask next week :)17:15
dtantsur2 more minutes to review the statuses17:17
dtantsurdone reviewing?17:19
rlooyuppers17:19
dtantsur#topic Deciding on priorities for the coming week17:19
*** openstack changes topic to "Deciding on priorities for the coming week (Meeting topic: ironic)"17:19
dtantsurI'm inclined to leave it as it is now (with moving BFV to next patches)17:20
dtantsurwhat are your thoughts?17:20
jrollfine with me17:20
rloo+117:20
joanna+17:20
JayF++17:20
mariojv++17:20
dtantsurgood17:21
*** srobert_ has joined #openstack-meeting-317:21
dtantsurbefore we move on. who was leading the bug triage previously and who wants to?17:21
* dtantsur thinks we should also start fixing bugs, not only triaging..17:21
* jroll looks back17:22
JayFI don't know who was doing it before, but I can take it this week if there are no volutneers17:22
dtantsurawesome! thanks JayF17:22
dtantsur#info JayF to help with bug triaging this week17:22
jrollI think we missed it last week17:22
jrollwas TheJulia and vdrok previously17:23
dtantsuryeah, my bad. was just out of PTO :)17:23
dtantsur#topic #Trello fate17:23
*** openstack changes topic to "#Trello fate (Meeting topic: ironic)"17:23
dtantsurwut?17:23
dtantsur#undo17:23
openstackRemoving item from minutes: #topic #Trello fate17:23
dtantsur#topic Trello fate17:23
*** openstack changes topic to "Trello fate (Meeting topic: ironic)"17:23
dtantsurlooks good now :) rloo, your turn17:23
rloowell, dtantsur brought it up at a previous meeting. we had been using trello. do we want to continue?17:24
* jroll pulls out a knife17:24
* jroll waits for the kill word17:24
rlootrello hasn't been updated so if no one will volunteer to use it, i think we should NOT17:24
dtantsurI'm very pleased with how we track things on the etherpad17:24
rlooi mean, volunteer to update it17:24
rlooso might be easiest to ask: does anyone want to continue using trello?17:24
*** srobert has quit IRC17:25
jrollwe've been asking about it for weeks, nobody has stood up and said they want it, afaik17:25
dtantsurI think somebody wanted it on the previous meeting.. but I'm not sure17:25
rloook, let's get rid of it. fwiw, the etherpad doesn't cover stuff that used to be i trello. trello had links to nova patches and ironic patches.17:25
rloodtantsur: i wanted it cuz i found it useful, but only if it is keep up to date.17:26
dtantsurrloo, 1-2 gerrit topics should cover it17:26
jrollany reason the etherpad doesn't? I feel like it should17:26
rloono reason tht the etherpad cannot. i'm just not sure it does have that info.17:26
dtantsurlet's just add all related topics to subteam items on the etherpad17:26
dtantsuranyone wants to? otherwise I can do it17:26
dtantsur#agreed abandon our Trello board in favor of the WhiteBoard17:27
rloodtantsur: while you're at it, i'm not sure cuz it has been a while, but trello had some projects that weren't completed that I don't think are in our priorities. if taht's the case, would you please make sure there are bugs open for those?17:28
dtantsurrloo, sure17:28
*** lamt has joined #openstack-meeting-317:28
rloothx dtantsur17:28
*** kzaitsev_mb has joined #openstack-meeting-317:28
dtantsur#action dtantsur to move all useful information from Trello to the WhiteBoard or Launchpad (for non-priorities)17:28
dtantsuranything else here?17:28
dtantsurok, before we jump into open discussions17:29
dtantsur#topic Virtual meetup17:29
*** openstack changes topic to "Virtual meetup (Meeting topic: ironic)"17:29
dtantsur#link https://etherpad.openstack.org/p/ironic-virtual-meetup17:29
dtantsurif it does happen on the week of Apr 24, I need to organize it *this* week. or I need somebody to organize it the next week.17:30
*** srobert_ has quit IRC17:30
jrollwhat all needs to be organized? time/place/?17:30
dtantsurI suggest to start with a doodle for specific dates17:30
dtantsurthen getting a conference number (or how was it called?)17:30
dtantsuractually, we can try using my bluejeans, they work with latest FF and Chrome without plugins17:31
dtantsurbut I can't promise :) so we'd better have SIP as a backup17:31
*** ralonsoh has quit IRC17:31
dtantsurand finally, to announce the details on the ML17:31
rlooi thought we used something that openstack provided. that stopped working during the meetup17:31
NobodyCam++ to SIP backup!17:31
* jroll wonders if there's anyone that will refuse to / cannot use bluejeans17:32
dtantsurrloo, this is what I just call SIP17:32
rloodtantsur: ah.17:32
dtantsurjroll, it probably involves non-free javascript, so there may be17:32
jrolldtantsur: right, also curious if it's reachable from china etc17:32
dtantsuroh yeah17:32
dtantsurI think I had meetings with folks from China, but the point is still valid17:32
jrollanyway, openstack SIP is always open, so that's an easy backup17:32
JayFI'll say that personally, I find it extremely difficult to understand what folks are saying without an accompanying video to lip read from17:32
JayFbut I understand if folks freedom-concerns prevent that17:33
dtantsurJayF++17:33
dtantsurfwiw I think you can call into bluejeans from a phone17:33
rloowell, i guess that's why we have PTG17:33
dtantsurwhich is of course completely free and open source ;)17:33
dtantsur(the phone, I mean)17:33
jrollhah17:33
rloodo we have an idea of how many days/hours?17:34
dtantsurjroll, should we reserve something in OpenStack SIP for specific days?17:34
jrolldtantsur: there's no reservation system, afaik17:34
dtantsurrloo, so, my idea was: two slots in one day to accommodate different timezones17:34
dtantsursimilar to the midcycle17:34
jrolldtantsur: this would be the closest thing to reservations https://wiki.openstack.org/wiki/VirtualSprints17:34
rloooh my, this was the previous midcycle: https://etherpad.openstack.org/p/ironic-newton-midcycle17:35
dtantsurso, back to planning, ideally if I can create the doodle this week, the next week somebody makes it official17:35
dtantsurbut I can rush everything in this week, if there are no volunteers17:35
* jroll doesn't want to promise anything right now, hopes someone steps up to coordinate17:36
dtantsur#link https://wiki.openstack.org/wiki/VirtualSprints17:36
rloodo we really want a midcycle? i'm half joking. just looking at the previous one and what we have gotten accomplished since then...17:36
mariojvgit clone https://git.openstack.org/openstack-dev/devstack.git devstack17:37
mariojvwhoops, sorry17:37
thomasemlol17:37
dtantsurmariojv, access denied ;)17:37
rlooam wondering whether we should 'just' have days/times, regardless of what week, to *do* something17:37
* jroll wonders if rloo is implying we haven't done much since, or have and so we don't need them17:37
dtantsurrloo, I was thinking into breaking the midcycle into such smaller sprints. and I want to have the first happening before I can suggest do it regularly17:37
rlooi mean, just pick feature X, prepare, and meet at <whenever> and do it.17:38
dtantsurplanning is hard though: timezones, other meeting, etc17:38
*** Patifa has quit IRC17:39
rlooif sprints work for folks then that is fine. i was just wondering if it might work better if we just say, eg. rescue is there, we want to just sit down and go over it. or spec Foo is there, lets just meet and go over it...17:39
*** ociuhandu has quit IRC17:39
rlooso eg, etags spec looks like it is almost there. let's just meet this week at .. and get it done.17:39
dtantsurthis is a bit different think, I suspect17:39
dtantsurin your etags example, we only need cores and the author17:40
joannarloo: something like regular spec review meeting with specific timeslot and list of specs?17:40
dtantsurthis can indeed just happen one day this week17:40
JayFI like rloo's example, honestly17:40
rloodtantsur: well, i was looking at your #2 in the meetup. what are we going to accomplish there?17:40
JayFand it mirrors some stuff we've done before with some features, i.e. a couple of weeks ago mario, annie, anup and I met and worked on rescue for a couple of hours17:40
dtantsurrloo, something close to what you suggest, I guess17:40
jrollI believe we had a similar conversation when dtantsur originally proposed this. and agreed we should do targeted meetups like rloo mentioned, *and* occassional syncups like dtantsur proposed. am I remembering this wrong/17:41
rloodtantsur: of those things listed in the meetup, i would be only interested in #3.17:41
jrolls/\//?/17:41
dtantsurjroll, I thought the same17:42
rloodtantsur: i think it'd be great if we could do 1, 2 in a diff way.17:42
rloodtantsur: i was hoping that our weekly meetings could address 117:42
dtantsurrloo, my point is, such meetup can collect bigger audience (e.g. our QE got interested when I talked about my proposal last week)17:42
dtantsurfor the benefit of people who don't attend every meeting we have17:43
dtantsur3rdparty CI conversation will attract specific audience who is not necessary here17:43
dtantsurbut dunno. I agree with jroll, we should have both17:43
dtantsurand I think targeted meetups do not have to be driven by the PTL ;)17:43
jroll++17:43
jrollif people aren't interested in the 'midcycle' topics, they don't need to join17:44
rloodtantsur: i'm fine if others want to have this meetup and will get something from it. and i agree the 3rd party ci will be a useful meeting to have.17:44
jrolllet's give it a shot17:44
dtantsurok, so I'll start with a doodle17:44
jroll(or those people can add more topics, of course) :)17:44
dtantsuras I don't see volunteers for organizing it, the deadline for the doodle will be Friday17:45
jrolldtantsur: thanks for doing that17:45
dtantsurwe'll use SIP, but we can also experiment with Bluejeans, if folks will feel like. co-ordination through our regular channel. any other thoughts?17:45
*** Aqsa has joined #openstack-meeting-317:46
dtantsurI'm ready to move on. And you? :)17:46
* jroll is17:47
dtantsur#topic Open discussion17:47
*** openstack changes topic to "Open discussion (Meeting topic: ironic)"17:47
ricardoashey, I've got an issue to share regarding oneview drivers :)17:47
dtantsursure17:48
xavierrhey ironic, we from oneview have a patch where we are discussing about non-persistent boot in our drivers we want your opinion if our idea for implement that is fair. suggestions are welcome! link: https://review.openstack.org/#/c/436469/17:48
ricardoaswe'd love to replace python-oneviewclient (and deprecated it) by hpOneView, it's been more actively maintained and supporting newer oneview api versions and we are already using it at oneview ml2 driver17:48
rloowant opinion on whether to show driver 'type' column in https://review.openstack.org/#/c/419274/17:48
dtantsurrloo, in driver-list or driver-show?17:48
*** apetrich has quit IRC17:48
ricardoasbut we need some advice on what to do with specific validations like the ones at https://github.com/openstack/ironic/blob/master/ironic/drivers/modules/oneview/common.py#L15017:49
mariojvrloo: oh, this is that microversion inconsistency topic?17:49
dtantsurricardoas, what's the problem with that?17:49
ricardoasour best guess is to move it upstream, wdyt?17:49
rloomariojv: yeah.17:49
*** apetrich has joined #openstack-meeting-317:49
dtantsurricardoas, "move it upstream" gets my support any day :)17:49
soliosgOne item here. Wonder if we could bring forward 'move ironic tempest plugin to the new repository' task17:50
ricardoasdtantsur, i've talked with some of you during the week and it was suggested to raise it here... so just checking if it is ok to move this validations upstream17:50
rloodtantsur: in driver_list17:50
ricardoasdtantsur: \o/17:50
*** abalutoiu_ has joined #openstack-meeting-317:50
mariojvrloo: i think it should be consistent with what driver show does17:50
soliosgI did some initial work, porting patches from ironic/ironic_tempest_plugin to the new repo17:50
*** mgould has left #openstack-meeting-317:50
rloodtantsur: in driver_show, it will show 'type' with no value, but it is in a row. in driver_list, 'type' will be a column with nothing in it.17:50
dtantsurrloo, hmm, in list. I suspect the answer is "no, because of microversions", right?17:50
dtantsurright17:50
dtantsurrloo, I suggest we don't show it. I hope the day will come when all drivers are new-style.17:51
mariojvrloo: but if it's a huge refactor to get it hidden or something, i might be ok with the small inconsistency17:51
soliosgThey're still waiting for review. I think cores could review & approve. The real review would be when making changes to project config and devstack-gate17:51
rlooso the right way, is not to show info that isn't avail in a microversion but we didn't do that for information. to date, that info is usually some field, so it shows up as a row in eg <resource>-show.17:51
dtantsursoliosg, thanks! this is one thing I constantly forget about. We have to freeze our tempest plugin and start merging the patches.17:51
rloothis list one is the first time (I think) the info is a column.17:52
*** s3wong has joined #openstack-meeting-317:52
mariojvalso here are some links illustrating the issue in case anyone has trouble visualizing this: http://paste.openstack.org/show/603982/ vs http://paste.openstack.org/show/603983/17:52
dtantsursoliosg, with project-config and devstack-gate, I think you can rely on help of #openstack-qa and mtreinish personally :) they are very keen on projects moving to branchless plugins.17:52
ricardoasregarding this patch that xavierr pasted... i think we should just store something at the node internal info to warn the boot change function that the next operation will be non persistent. Any better idea, folks? :D17:52
soliosgdtantsur: yes, also jlvillal_pto has provided great support!17:53
dtantsurrloo, why do we need to show this column at all?17:53
mtreinishdstanek: heh, actually both project-config and devstack-gate are the domain of -infra. I'll gladly look and review patches, but I don't have the big rubber stamp on either :)17:53
rloodtantsur: well, that is a good question. it isn't a need. do we want to or not?17:53
mariojvdtantsur: i suppose we don't, but then we'd be not exposing something potentially useful returned by the api17:53
dtantsurmtreinish, yeah, I specifically mean "look and review" part17:53
*** abalutoiu has quit IRC17:54
rloodtantsur: with the driver stuff, i think it is in the spec that driver-list shows the type.17:54
dtantsurrloo, mariojv, I hope one day all drivers are new-style, and this "Type" column will be always-true17:54
mariojvoh, i see your point17:54
dtantsureven worse, if we remove it in one microversion, then this column will have to go away too..17:54
dtantsurrloo, how many times have we amended this spec already? one more won't hurt :)17:55
rloodtantsur: I'm fine with amending the spec. we just need to decide. (and i wanted a decision before i reviewed more).17:55
*** galyna1 has quit IRC17:55
*** galyna2 has joined #openstack-meeting-317:55
rloodtantsur: keep in mind, the API is returning 'type' .17:55
dtantsuryeah, but we don't have to expose everything in a list CLI call17:55
dtantsurespecially when we have reasons to believe that it will become redundant one day17:56
*** lamt has quit IRC17:56
rloodtantsur: that is true. i'm fine with that. so no type in CLI except in show or if we add 'filter'ing on driver-list...17:56
ricardoasdtantsur: if there is some time left, i'd like to talk about this patch too: https://review.openstack.org/#/c/408298/17:56
mariojvi think that's reasonable for now17:57
rloodtantsur: or if driver-list --detail is specified. i think we have --detail...17:57
ricardoas(and everyone else...)17:57
dtantsurrloo, ++17:57
NobodyCam*Two (2) minutes to go*17:57
rloodtantsur: ok, no one is in disagreement, so i'll convey the news to the author of the patch :)17:58
dtantsurrloo, thanks! good point to raise indeed, the author of the driver composition spec clearly did not think about it ;)17:58
dtantsurI suggest we move the discussion of the specific patches to the channel, if you don't mind17:59
dtantsurricardoas, ^^^17:59
rloodtantsur: can't expect the author of the spec to think about everything. but we're close to the finish line now :)17:59
*** nicodemos has left #openstack-meeting-317:59
ricardoasok :)17:59
ricardoasno problem17:59
*** baoli has quit IRC17:59
dtantsur#agreed Do not expose "Type" column in the output of driver-list without --detail17:59
dtantsurthanks everyone!17:59
mariojvty18:00
joannathanks :)18:00
soliosgthanks all18:00
milano/18:00
*** mariojv has left #openstack-meeting-318:00
ricardoasthanks!18:00
*** wanyen has quit IRC18:00
dtantsur#endmeeting18:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Mon Apr 10 18:00:10 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-04-10-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-04-10-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-04-10-17.00.log.html18:00
*** crushil has left #openstack-meeting-318:00
*** ricardoas has left #openstack-meeting-318:00
aNuposicthanks :)18:00
fellypefcaty :)18:00
*** aNuposic has left #openstack-meeting-318:00
*** sambetts is now known as sambetts|afk18:00
*** dtantsur has left #openstack-meeting-318:00
*** fellypefca has left #openstack-meeting-318:00
*** soliosg has left #openstack-meeting-318:00
*** lyan has quit IRC18:01
*** mrtenio has left #openstack-meeting-318:01
*** milan has quit IRC18:01
*** bfournie has left #openstack-meeting-318:01
*** galyna2 has left #openstack-meeting-318:02
*** mrtenio has joined #openstack-meeting-318:02
*** mrtenio has left #openstack-meeting-318:02
*** baoli has joined #openstack-meeting-318:02
*** stendulker has quit IRC18:03
*** Patifa has joined #openstack-meeting-318:03
*** guest303018 has left #openstack-meeting-318:03
*** rloo has left #openstack-meeting-318:04
*** kzaitsev_mb has quit IRC18:04
*** lee4 has quit IRC18:04
*** ociuhandu has joined #openstack-meeting-318:04
*** sauloaislan has quit IRC18:07
*** baoli has quit IRC18:26
*** baoli has joined #openstack-meeting-318:32
*** seanatcisco has quit IRC18:35
*** srobert has joined #openstack-meeting-318:37
*** ralonsoh has joined #openstack-meeting-318:50
*** lyan has joined #openstack-meeting-318:54
*** seanatcisco has joined #openstack-meeting-318:54
*** sdague_ has quit IRC18:55
*** rbrady has left #openstack-meeting-318:57
*** alexismonville has joined #openstack-meeting-319:05
*** gugl_ has joined #openstack-meeting-319:06
*** gugl_ has quit IRC19:06
*** Nisha_Agarwal has left #openstack-meeting-319:10
*** reedip_ is now known as outofmemory19:10
*** kzaitsev_mb has joined #openstack-meeting-319:13
*** marst_ has joined #openstack-meeting-319:27
*** marst has quit IRC19:30
*** tonytan4ever has quit IRC19:36
*** tonytan4ever has joined #openstack-meeting-319:40
*** VW_ has joined #openstack-meeting-319:46
*** VW has quit IRC19:46
*** sgrasley has joined #openstack-meeting-319:46
*** VW_ has quit IRC19:46
*** VW has joined #openstack-meeting-319:46
*** sgrasley has left #openstack-meeting-319:52
*** gouthamr has quit IRC19:54
*** blancos has joined #openstack-meeting-319:55
*** mlavalle has joined #openstack-meeting-319:56
*** alexismonville has quit IRC19:58
*** abalutoiu__ has joined #openstack-meeting-319:59
*** skelso has joined #openstack-meeting-319:59
ildikov#startmeeting openstack_upstream_institute20:00
openstackMeeting started Mon Apr 10 20:00:10 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
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: openstack_upstream_institute)"20:00
openstackThe meeting name has been set to 'openstack_upstream_institute'20:00
mlavalleo/20:00
mrmartino/20:00
jungleboyjo/20:00
diablo_rojoHello :)20:00
ildikovping bauzas, jaypipes20:00
skelsoo/20:00
blancoso/20:01
kmARCo/20:01
ildikovhi all :)20:01
ildikovthanks to diablo_rojo we have a pretty good agenda for today20:02
ildikovso let's dive into it! :)20:02
diablo_rojoildikov, ha ha thanks :)20:02
ildikov#topic Announcements20:02
*** openstack changes topic to "Announcements (Meeting topic: openstack_upstream_institute)"20:02
diablo_rojoI do love organization..20:02
*** abalutoiu_ has quit IRC20:02
ildikovdiablo_rojo: :)20:02
ildikovso it's only 4 weeks until the next training!!!20:03
*** yamahata has quit IRC20:03
ildikovwhich means that we would like to further encourage all of you to look into the material and help us update and improve it20:03
ildikov#info We have 39 registered students so far20:04
jungleboyjCool.20:04
jungleboyjildikov:  So I spent time going through the slides today and had ideas.  Do you want me to just start pushing up reivews?20:04
ildikovwe will look into their areas of interest and will reach out to people in the project teams if we don't have the coverage yet20:04
diablo_rojojungleboyj, yes please :)20:05
jungleboyjdiablo_rojo:  Ok.  Will do.20:05
ildikovjungleboyj: yep, that would be great :)20:05
mlavalleildikov: do we know already what projects are they interested on? I'm trying to get a feel as to how many of them I can expect in the Neutron on-boarding room20:05
spotzHey all20:05
diablo_rojomlavalle, once we get access to the rsvp data we will know what projects to get reps from20:05
ildikovmlavalle: we have only the numbers for today and as diablo_rojo said we will pull the data too and let you know20:06
jungleboyjI did just push up changes to official-projects slides.  Let me know what you all think. https://review.openstack.org/#/c/455436/1/doc/upstream-training/source/slides/howitsmade-official-projects.rst20:06
ildikovmlavalle: we asked for their interest, so we should know shortly20:06
ildikovjungleboyj: cool, tnx20:06
mlavallediablo_rojo:, ildikov: ok, I've been working on the presentation / practices for the Neutron on-boarding room. I hope it is not wasted effort20:07
diablo_rojomlavalle, shouldn't be :)20:07
*** lamt has joined #openstack-meeting-320:07
ildikovmlavalle: the on boarding room is open for anyone to participate, so the training attendees just a subset20:07
mlavalleildikov: ahh, that's good20:08
ildikovmlavalle: and having that information collected and organized into a presentation is never a wasted effort! :)20:08
diablo_rojoWe should make sure to mention the onboarding rooms towards the end of the training as next steps for students20:08
ildikovdiablo_rojo: +120:08
spotz+120:08
ildikovdiablo_rojo: do we have anything else to announce today?20:09
*** dimtruck is now known as zz_dimtruck20:09
mlavalleildikov, diablo_rojo: also, even though I cannot not be there for the whole training, I will arrive at Boston at noon, Sunday. So I'll do my best to join you guys in the afternoon20:09
diablo_rojoildikov, nope, that's it I think20:09
jungleboyjdiablo_rojo: ++20:09
diablo_rojomlavalle, We will take whatever help we can get :)20:10
diablo_rojomlavalle, did you note that in the wiki?20:10
mlavallediablo_rojo: about to do it right now :-)20:10
mlavallediablo_rojo: you read my mind20:10
diablo_rojomlavalle, much appreciated20:10
ildikovmlavalle: thanks for letting us know and thanks for joining even for that short time20:10
ildikovok, let's move on20:11
ildikov#topic Open Reviews20:11
*** openstack changes topic to "Open Reviews (Meeting topic: openstack_upstream_institute)"20:11
ildikovbusiness as usual you can find the open reviews here:20:12
ildikov#link https://review.openstack.org/#/q/project:openstack/training-guides20:12
diablo_rojoWe have two right now. Mine and Jay's.20:12
jungleboyj:-)20:12
ildikovis there anything we should discuss about those two here?20:13
diablo_rojoPlease review? :)20:13
diablo_rojoThat's all.20:13
ildikovdiablo_rojo: +1 :)20:13
ildikov#topic Topics20:13
*** openstack changes topic to "Topics (Meeting topic: openstack_upstream_institute)"20:13
jungleboyjI hope my changes are ok.  Just shortened it up and have exercises to find some more info.20:13
ildikovjungleboyj: sounds good!20:13
ildikovok, let's continue to go through what we have in the current material20:14
ildikovnext one is Registration and Accounts20:14
jungleboyjI had a question here.  Is there a separate account that will be needed to storyboard?20:15
ildikov#link https://docs.openstack.org/upstream-training/workflow-reg-and-accounts.html#120:15
diablo_rojojungleboyj, looks good so far. Got some small nits, but it looks like a big improvement to me.20:15
jungleboyjOr is that not something we want to introduce yet?20:16
jungleboyjdiablo_rojo:  Thank you.  :-)20:16
diablo_rojojungleboyj, we will need to talk about storyboard- its on my todo list, but there arent any new accounts you need cause it uses openstackid20:16
jungleboyjdiablo_rojo:  Ok cool.  Yeah, I don't know that we need to make a long talk on storyboard yet but good to mention it is coming.20:17
ildikovso require Foundation registration now for signing up to the training20:17
jungleboyjdiablo_rojo: Did your presentation get accepted on that?20:17
diablo_rojojungleboyj, +120:17
diablo_rojoyes it did20:17
diablo_rojo:)20:17
jungleboyjGood.20:17
jungleboyjildikov: Ok, so that is going to shorted up this slide deck quite a bit.20:18
skelsoFoundation registration also drives the contributor agreement? I'd like to give folks a chance to review before arriving.20:18
jungleboyj*shorten20:18
ildikovin this sense we can remove the Foundation registration part maybe leave there a note that people need to be Foundation members and not community members there20:18
skelsoBecause sometimes they have to have a lawyer look at it before they can sign.20:19
ildikovskelso: that's different, you need to sign that one on Gerrit20:19
diablo_rojoildikov, +120:19
ildikovskelso: but good point to give people a heads up before they come to the training20:19
skelsoAh, okay, thanks.20:19
diablo_rojoI thought we were going to try to have people look at/sign the CLA before coming to the training?20:19
spotzskelso that's why we put up the pre-requisites for the Git and Gerrit session we ran into that in Tokyo where they couldn't sign20:19
skelsoCool.20:19
ildikovspotz: we ran into that in Barcelona too20:20
jungleboyjildikov: Do we have any way to track/enforce people doing that work beforehand?20:20
ildikovjungleboyj: I'm sure we could, but I'm not sure it's worth the effort, or at least we didn't have that many in Barcelona who couldn't sign20:21
ildikovjungleboyj: so I would think giving a heads up about it should be fine20:21
skelsoSeems right to me.20:21
spotzWe could ask people as they come in and help those who don't have logins as everyone settles in20:21
jungleboyjOk.  Cool.20:22
ildikovspotz: we have a short slot dedicated20:22
diablo_rojoWe can make sure the prereqs get stressed in the  email we will send out shortly before the training to also confirm attendance20:22
diablo_rojospotz, +120:22
jungleboyjI wasn't so much concerned with the signing as with people doing the pre-reqs in general so we don't have a few people holding up the group.20:23
jungleboyjdiablo_rojo:  +220:23
ildikovspotz: we only need an exercise to the end that ensures they really did the steps as it always turns out at the part when they try to upload a patch that some of them still failed with some steps...20:23
spotzildikov: True20:23
diablo_rojoildikov, right, we can check some of the things, like if they have signed the CLA, but knowing if they have the vm image ready...that we can't do.20:24
mlavallediablo_rojo, ildikov: since in the on-boarding room we may get people who didn't attend the training, could it be mentioned in the sesssion description to install the VM to be used in the training. I am assuming attendees will have the VM20:24
ildikovdiablo_rojo: we started with that in Barcelona and it went pretty well20:24
* mlavalle is not sure he was clear enough20:25
diablo_rojoWe can have the prereqes posted on the board while people are trickling in and people wandering around seeing if people have them done/need help.20:25
jungleboyjYeah, that is good.20:25
skelsodiablo_rojo +120:25
ildikovkmARC got them through that part pretty quickly as most of them was prepared already20:25
spotzdiablo_rojo: +120:25
diablo_rojoildikov, +1 We definitely need to do that again- I will make note of that.20:25
ildikovwe should have the short intro about the training and objectives and have them warmed up a little bit and then get the VM image running and jump on IRC20:26
kmARCmlavalle: any additional requirements what to install in the vm?20:26
mlavallekmARC: I just want the people who will attend the Neutron on-boarding room to have the VM isntalled. That's all20:27
diablo_rojoildikov, yep, the intro slides reflect that as of my patch- I can add the part about booting things up.20:27
ildikovdiablo_rojo: sounds good, tnx20:27
mlavallekmARC: so I would like that to be mentioned in the on-boarding room description20:27
kmARCsure that's easy :-)20:28
diablo_rojomlavalle, no problem20:28
diablo_rojoSo, a lot we can cut out of the registration/accounts slide deck- who wants it?20:29
spotzdiablo_rojo: May have questions for clarity but I can20:29
*** tobberydberg has joined #openstack-meeting-320:29
diablo_rojospotz, no problem :) Throw a patch up and we will all take a look.20:29
* mlavalle spent some time on Friday looking at kmARC github repo for the VM and thinks he kmARC has done a great job20:30
ildikovmlavalle: +120:30
* kmARC blushes20:30
*** zz_dimtruck is now known as dimtruck20:31
*** ralonsoh has quit IRC20:31
*** thomasem has left #openstack-meeting-320:31
ildikovis there anything else for the accounts section?20:31
diablo_rojoildikov, don't think so20:31
ildikovok, let's move on to Tracking then20:32
ildikov#link https://docs.openstack.org/upstream-training/workflow-launchpad.html#120:32
diablo_rojoLooking at the tracking, I think there is a lot to be condensed and we need to add SB stuff. I can take this one.,20:32
ildikovdiablo_rojo: cool20:33
diablo_rojoI will try to add an exercise for SB too.20:33
skelsoI wish we had a bug lifecycle picture, kind of like this one https://bugzilla.readthedocs.io/en/5.0/using/editing.html#life-cycle-of-a-bug20:33
ildikovI think we can throw a bunch of stuff out and get them start with an exercise of submitting a bug and analyze what they can set and what they think all those things mean, etc.20:33
diablo_rojoWhat repo did we have them make bugs against?20:33
diablo_rojoin BCN?20:33
ildikovdiablo_rojo: sandbox20:34
*** srobert_ has joined #openstack-meeting-320:34
diablo_rojoRight right, okay cool. I will add that info to the exercise that is there20:34
ildikovskelso: yeah, that one looks good20:34
diablo_rojoskelso, I like that too. I will see if I can find a good place to include it.20:34
ildikovdiablo_rojo: I would move the exercise to the beginning and use the slides to ensure we clarify the info they really need20:35
jungleboyjildikov: ++20:35
skelsodiablo_rojo: Cool20:35
diablo_rojoildikov, Yeah I was gonna shuffle stuff a bunch20:35
ildikovdiablo_rojo: coolio, tnx20:35
ildikovanything else for tracking?20:36
diablo_rojoIf anyone has other exercise ideas please speak up :)20:36
jungleboyjildikov:  Why do we have a number of the slides repeated in here?20:36
*** srobert has quit IRC20:36
ildikovjungleboyj: repeated?20:37
jungleboyjdiablo_rojo:  Like bug status twice .20:37
jungleboyjSame for importance.20:37
diablo_rojojungleboyj, might have been an issue with the sphinx rendering of the rst. I will clean all that up :)20:37
diablo_rojonoticed that too though.20:38
jungleboyjdiablo_rojo:  Ok.  Cool.  Thanks.20:38
diablo_rojoNo problemo :)20:38
*** srobert_ has quit IRC20:38
jungleboyjdiablo_rojo:  Is there a way to have people do an exercise where they submit a fix against their bug ... for the section on commits and show how the associated is made?20:38
jungleboyj*association20:38
*** egallen has joined #openstack-meeting-320:39
diablo_rojojungleboyj, yeah we should be able to do that20:39
ildikovjungleboyj: I'm not sure that works for sandbox, we need to check20:39
jungleboyjThat would be kind-of cool.20:39
jungleboyjOk, just a thought.  :-)20:39
spotzildikov: I'm pretty sure we do it, I'd have to double check20:39
diablo_rojoAgreed. I think the bug numbers/ links should work whether they are in the sandbox enviros or not20:40
spotzildikov: We may be doing it live with a dummy project thought20:40
diablo_rojosomething to test20:40
ildikovI remember there was something not working with this, but I might be wrong20:40
*** tonytan4ever has quit IRC20:41
ildikovanyway, if anyone can get there to test that would be great20:41
*** cleong has quit IRC20:41
diablo_rojo20 min warning20:41
*** tonytan4ever has joined #openstack-meeting-320:41
ildikovok, let's move on to Gerrit20:42
ildikov#link https://docs.openstack.org/upstream-training/workflow-gerrit.html#120:42
diablo_rojoDesperately needs exercises20:42
ildikovyep20:42
jungleboyjYeah, the content looks pretty good.20:43
*** lamt has quit IRC20:43
skelsoRight. In BCN, this deck was where we went from crawl to run.20:43
ildikovwe could prepare one or two patches that have history, etc. to show them20:43
jungleboyjI would like to add a note as to how you actually make comments as, believe it or not, people have trouble figuring that out.20:43
jungleboyjildikov: ++20:43
diablo_rojojungleboyj, good idea. The newer gerrit ui isnt the most intuitive20:44
ildikovjungleboyj: there's a whole reviewing section that covers that right now20:44
blancosCould we roll this into bug exercise perhaps? Like, find a commit in the sandbox and leave a comment20:44
diablo_rojoCould we combine the two sections?20:44
diablo_rojocombine gerrit and reviewing?20:44
spotz+120:45
ildikovI think we can do that20:45
diablo_rojoSince gerrit is small and goes with reviewing anyway20:45
jungleboyjildikov: diablo_rojo That would make sense.20:45
ildikovwe should avoid having long lecture parts in it still20:46
*** tonytan4ever has quit IRC20:46
ildikovso we could try to insert some exercises so people remain involved20:46
diablo_rojoildikov, agreed. Should come up with an exercise for the gerrit intro- adding an ssh key and reviewers to your patch or something20:46
diablo_rojoand then go into reviewing20:46
skelsoSlide 3 rocks (I guess I like diagrams) but its density means covering at same speed overwhelms learners. I was thinking to lecture a little more there.20:46
ildikovskelso: :)20:47
ildikovskelso: diagrams are good, I agree20:47
diablo_rojoskelso, if we break it up with more exercises it might make people process the info more so that people dont get overwhealmed by a lot of into being talked at them20:47
skelsoMaybe follow with exercises interleaved with lectures covering groups or 2-3 blocks.20:47
skelsodiablo_rojo: +120:47
jungleboyjYeah, that would be good.20:48
diablo_rojoSo, the plan is to combine gerrit and reviewing and add at least one more if not two more exercises into that deck20:48
diablo_rojo?20:48
ildikovdiablo_rojo: +120:48
ildikovanyone would like to take this one?20:48
spotzildikov: If no one else takes it I can, I've got all of this for the lunch and learn20:49
spotzWe do it a little different though, we have them make a bug, commit to it, review each other, etc20:50
jungleboyjspotz: That actually was kind of what I was getting at earlier.20:50
spotzjungleboyj: Wed during lunch:)20:50
*** abalutoiu__ has quit IRC20:50
ildikovspotz: sounds good20:50
diablo_rojospotz, we can do a lot of that. I will have them make a bug and a task in lp and sb so that when we get here we can do some of that.20:50
jungleboyjIt would be nice if we could combine all of this into introduction, exercise, follow on info, exercise.20:50
ildikovspotz: would be great if you can take this, especially as you deal with the topic already :)20:51
diablo_rojoHave them make a patch and reference the bug or sb task and push it and add reviewers and then review someone elses20:51
jungleboyjdiablo_rojo:  ++20:51
*** abalutoiu_ has joined #openstack-meeting-320:51
ildikovdiablo_rojo: +120:52
spotzdiablo_rojo: exactly20:52
diablo_rojoTotally do able.20:52
spotzOk I'll take this and accounts, no more volunteering untiL get these done though:)20:52
jungleboyjMuch more engaging.20:52
ildikovspotz: thanks much!20:52
diablo_rojoWe just need to get all these patches out ASAP. I can work on the tracking one and get it out tonight. I'll add you as a reviewer spotz ;)20:52
ildikovok, let's try to cover commit messages too today20:52
ildikov#link https://docs.openstack.org/upstream-training/workflow-commit-message.html#120:53
diablo_rojo7 min left20:53
spotzdiablo_rojo: sounds good:)20:53
diablo_rojoI have some ideas for exercises for this I can add20:53
diablo_rojothis as in the commit messages section20:53
ildikovsounds good20:53
diablo_rojonot sure if there is much we can cut out?20:53
diablo_rojoopinions there?20:53
*** Aqsa has quit IRC20:53
diablo_rojoI can try to make something a little more succint20:53
diablo_rojo*succinct20:53
ildikovdiablo_rojo: we can balance with how much we are talking about it20:53
jungleboyjI don't like carrot and stick stuff in here.20:53
diablo_rojojungleboyj,  like the bad and good examples?20:54
skelsoDoes carrot and stick translate WW?20:54
jungleboyjskelso: Probably not.20:54
spotzoh and formating:)20:54
jungleboyjThe first page needs to better explain the importance here.20:54
diablo_rojoThe formatting is a bit painful too.20:54
jungleboyjdiablo_rojo:  Will it conflict with you if I try to push up a patch that words that better?20:55
*** ansmith has quit IRC20:55
diablo_rojoYeah I think it would be better to do the importance and then go into the parts of a commit and have an exercise for writing each part.20:56
jungleboyjI also don't like the fact that the examples on page 5 are just summary lines.  Not really good examples.20:56
jungleboyjAh, yes, get the parts explained first.  Then an example(s) and exercise.20:56
diablo_rojojungleboyj, no you can do that if you want. Or I can get it started and you can push up a patchset in the same patch tweaking things after me if I havent done it well enough?20:56
jungleboyjdiablo_rojo:  :-p20:57
diablo_rojoI want to rework this whole section now that I think about it lol20:57
jungleboyjdiablo_rojo:  ++ I don't like it.20:57
skelsoWhat about slides 3-4? Are they really about how to structure or partition patches, or just about writing about them?20:58
ildikovdiablo_rojo: jungleboyj: you can sync up on the channel and might get others looking into this too20:58
diablo_rojojungleboyj, not poking at you I promise :)20:58
jungleboyjildikov: Ok.  Sounds good.20:58
diablo_rojoIf you want to go first I can make mine dependent on yours.20:58
jungleboyjUh huh.  ;-)20:58
jungleboyjNo go ahead and then I can make comments/changes.20:59
diablo_rojoWith only four weeks there's no time to poke :)20:59
ildikovwe're out of time, but I think we made great progress today20:59
spotzThanks all!20:59
diablo_rojoildikov, +1 Way more productive than last week!20:59
mlavalleo/20:59
jungleboyjAgreed.  Thanks!20:59
ildikovthanks for everyone volunteering and looking into the material!20:59
skelsoBye!20:59
kmARCgoodnight :-)20:59
ildikovkeep in touch on Gerrit and IRC21:00
mrmartingoodnight21:00
ildikovsee you next week here :)21:00
ildikovgood rest of the day everyone! :)21:00
ildikov#endmeeting21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Mon Apr 10 21:00:24 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack_upstream_institute/2017/openstack_upstream_institute.2017-04-10-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_upstream_institute/2017/openstack_upstream_institute.2017-04-10-20.00.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_upstream_institute/2017/openstack_upstream_institute.2017-04-10-20.00.log.html21:00
*** mlavalle has left #openstack-meeting-321:00
*** blancos has quit IRC21:00
*** tonytan4ever has joined #openstack-meeting-321:03
*** seanatcisco has quit IRC21:07
*** baha has quit IRC21:08
*** abalutoiu__ has joined #openstack-meeting-321:15
*** tobberydberg has quit IRC21:15
*** pcaruana has quit IRC21:15
*** abalutoiu_ has quit IRC21:18
*** abalutoiu__ is now known as abalutoiu21:19
*** haleyb has quit IRC21:35
*** ccamacho|brb has quit IRC21:37
*** galstrom is now known as galstrom_zzz21:38
*** lucasxu has quit IRC21:40
*** Sukhdev has joined #openstack-meeting-321:41
*** baoli has quit IRC21:43
*** kzaitsev_mb has quit IRC21:43
*** baoli has joined #openstack-meeting-321:44
*** baoli has quit IRC21:48
*** julim has quit IRC21:49
*** tellesnobrega has quit IRC22:01
*** tellesnobrega has joined #openstack-meeting-322:02
*** lamt has joined #openstack-meeting-322:02
*** mickeys has quit IRC22:04
*** liangy has joined #openstack-meeting-322:04
*** rbak_ has joined #openstack-meeting-322:06
*** lyan has quit IRC22:07
*** rbak has quit IRC22:09
*** skelso has quit IRC22:12
*** rbak__ has joined #openstack-meeting-322:14
*** mariannelm has quit IRC22:14
*** rbak_ has quit IRC22:16
*** tellesnobrega has quit IRC22:18
*** tellesnobrega has joined #openstack-meeting-322:18
*** dimtruck is now known as zz_dimtruck22:28
*** lamt has quit IRC22:31
*** gouthamr has joined #openstack-meeting-322:32
*** seanatcisco has joined #openstack-meeting-322:32
*** zz_dimtruck is now known as dimtruck22:33
*** bobh has quit IRC22:36
*** lee4 has joined #openstack-meeting-323:02
*** lee4 has quit IRC23:03
*** lee4 has joined #openstack-meeting-323:03
*** mickeys has joined #openstack-meeting-323:05
*** leetpy has joined #openstack-meeting-323:05
*** leetpy has quit IRC23:06
*** DFFlanders has joined #openstack-meeting-323:08
*** lee4 has quit IRC23:08
*** mickeys has quit IRC23:09
*** lamt has joined #openstack-meeting-323:09
*** sdague has quit IRC23:12
*** mickeys has joined #openstack-meeting-323:12
*** seanatcisco has quit IRC23:13
*** scottda has quit IRC23:15
*** tobberydberg has joined #openstack-meeting-323:16
*** tonytan4ever has quit IRC23:20
*** tobberydberg has quit IRC23:20
*** dimtruck is now known as zz_dimtruck23:20
*** liangy has quit IRC23:21
*** zz_dimtruck is now known as dimtruck23:24
*** chyka has quit IRC23:25
*** chyka has joined #openstack-meeting-323:25
*** ansmith has joined #openstack-meeting-323:26
*** rpioso has quit IRC23:27
*** lamt has quit IRC23:29
*** marst_ has quit IRC23:29
*** lamt has joined #openstack-meeting-323:33
*** dimtruck is now known as zz_dimtruck23:54
*** zz_dimtruck is now known as dimtruck23:54
*** lamt has quit IRC23:55
*** marst has joined #openstack-meeting-323:58

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!