Monday, 2017-03-27

*** amotoki has quit IRC00:01
*** baoli has joined #openstack-meeting-300:16
*** mtanino has joined #openstack-meeting-300:19
*** mtanino has quit IRC00:26
*** baoli has quit IRC00:29
*** wanghao has joined #openstack-meeting-300:29
*** kzaitsev_mb has quit IRC00:40
*** lucasxu has joined #openstack-meeting-300:56
*** lucasxu has quit IRC00:57
*** mickeys has joined #openstack-meeting-301:01
*** markvoelker has joined #openstack-meeting-301:01
*** amotoki has joined #openstack-meeting-301:04
*** mickeys has quit IRC01:06
*** reedip has quit IRC01:10
*** gcb has joined #openstack-meeting-301:15
*** tonytan4ever has joined #openstack-meeting-301:17
*** amotoki has quit IRC01:27
*** kzaitsev_mb has joined #openstack-meeting-301:37
*** sdoyle has joined #openstack-meeting-301:37
*** tuanluong has joined #openstack-meeting-301:37
*** huanxuan has joined #openstack-meeting-301:39
*** shuyingya has joined #openstack-meeting-301:52
*** dixiaoli has joined #openstack-meeting-301:53
*** bobh has quit IRC01:58
*** reedip has joined #openstack-meeting-302:00
*** gouthamr has quit IRC02:16
*** VW has quit IRC02:16
*** VW has joined #openstack-meeting-302:16
*** kzaitsev_mb has quit IRC02:21
*** dixiaoli has quit IRC02:21
*** yamamoto has joined #openstack-meeting-302:25
*** dixiaoli has joined #openstack-meeting-302:39
*** amotoki has joined #openstack-meeting-302:42
*** yamamoto has quit IRC02:43
*** yamamoto has joined #openstack-meeting-302:43
*** amotoki has quit IRC02:53
*** bobh has joined #openstack-meeting-302:58
*** reedip has quit IRC02:58
*** wanghao_ has joined #openstack-meeting-302:59
*** dixiaoli has quit IRC03:00
*** mickeys has joined #openstack-meeting-303:02
*** wanghao has quit IRC03:02
*** dixiaoli has joined #openstack-meeting-303:03
*** bobh has quit IRC03:03
*** amotoki has joined #openstack-meeting-303:06
*** wanghao has joined #openstack-meeting-303:06
*** mickeys has quit IRC03:06
*** dimtruck is now known as zz_dimtruck03:07
*** zz_dimtruck is now known as dimtruck03:07
*** wanghao_ has quit IRC03:09
*** shuyingya has quit IRC03:14
*** shuyingya has joined #openstack-meeting-303:14
*** yamamoto has quit IRC03:16
*** dimtruck is now known as zz_dimtruck03:16
*** kzaitsev_mb has joined #openstack-meeting-303:17
*** yamamoto has joined #openstack-meeting-303:18
*** reedip has joined #openstack-meeting-303:30
*** amotoki has quit IRC03:31
*** VW has quit IRC03:32
*** VW has joined #openstack-meeting-303:33
*** gcb has quit IRC03:33
*** lamt has joined #openstack-meeting-303:34
*** yamamoto has quit IRC03:35
*** joanna has quit IRC03:37
*** mpotdar has quit IRC03:38
*** mpotdar has joined #openstack-meeting-303:43
*** shuyingy_ has joined #openstack-meeting-303:51
*** kzaitsev_mb has quit IRC03:51
*** dixiaoli has quit IRC03:52
*** amotoki has joined #openstack-meeting-303:52
*** shuyingya has quit IRC03:54
*** gcb has joined #openstack-meeting-303:58
*** psachin has joined #openstack-meeting-304:04
*** zz_dimtruck is now known as dimtruck04:07
*** dimtruck is now known as zz_dimtruck04:17
*** yamamoto has joined #openstack-meeting-304:22
*** lamt has quit IRC04:28
*** dixiaoli has joined #openstack-meeting-304:48
*** dixiaoli has quit IRC04:49
*** dixiaoli has joined #openstack-meeting-304:50
*** mickeys has joined #openstack-meeting-304:51
*** dixiaoli has quit IRC04:52
*** bobh has joined #openstack-meeting-305:00
*** bobh has quit IRC05:05
*** zz_dimtruck is now known as dimtruck05:06
*** pgadiya has joined #openstack-meeting-305:10
*** anilvenkata has joined #openstack-meeting-305:12
*** VW has quit IRC05:15
*** dimtruck is now known as zz_dimtruck05:16
*** dixiaoli has joined #openstack-meeting-305:29
*** shuyingy_ has quit IRC05:30
*** shuyingya has joined #openstack-meeting-305:30
*** lamt has joined #openstack-meeting-305:34
*** shuyingy_ has joined #openstack-meeting-305:39
*** tonytan4ever has quit IRC05:41
*** pgadiya has quit IRC05:41
*** shuyingya has quit IRC05:42
*** ltomasbo|away is now known as ltomasbo05:56
*** bobh has joined #openstack-meeting-306:01
*** bobh has quit IRC06:06
*** zz_dimtruck is now known as dimtruck06:07
*** mickeys has quit IRC06:16
*** dimtruck is now known as zz_dimtruck06:17
*** lpetrut has joined #openstack-meeting-306:18
*** lamt has quit IRC06:20
*** reedip has quit IRC06:24
*** lamt has joined #openstack-meeting-306:26
*** nkrinner_afk is now known as nkrinner06:28
*** andreas_s has joined #openstack-meeting-306:29
*** psachin has quit IRC06:33
*** tuanluong has quit IRC06:50
*** lamt has quit IRC06:53
*** ralonsoh has joined #openstack-meeting-306:55
*** reedip has joined #openstack-meeting-306:56
*** ltomasbo is now known as ltomasbo|away06:57
*** wanghao_ has joined #openstack-meeting-306:59
*** wanghao has quit IRC06:59
*** zz_dimtruck is now known as dimtruck07:01
*** bobh has joined #openstack-meeting-307:02
*** mickeys has joined #openstack-meeting-307:02
*** bobh has quit IRC07:06
*** dimtruck is now known as zz_dimtruck07:11
*** acabot has quit IRC07:17
*** sankarshan has quit IRC07:19
*** sankarshan has joined #openstack-meeting-307:19
*** pcaruana has joined #openstack-meeting-307:20
*** tuanluong has joined #openstack-meeting-307:31
*** tonytan4ever has joined #openstack-meeting-307:41
*** aarefiev_afk is now known as aarefiev07:47
*** acabot has joined #openstack-meeting-307:52
*** dixiaoli has quit IRC07:59
*** rossella_s has joined #openstack-meeting-308:02
*** zz_dimtruck is now known as dimtruck08:02
*** makowals has quit IRC08:03
*** makowals has joined #openstack-meeting-308:04
*** matrohon has joined #openstack-meeting-308:04
*** dixiaoli has joined #openstack-meeting-308:05
*** dixiaoli has quit IRC08:07
*** dixiaoli has joined #openstack-meeting-308:08
*** dixiaoli has quit IRC08:08
*** dimtruck is now known as zz_dimtruck08:11
*** itamaro has joined #openstack-meeting-308:11
*** itamaro has quit IRC08:12
*** psachin has joined #openstack-meeting-308:12
*** dixiaoli has joined #openstack-meeting-308:16
*** mickeys has quit IRC08:16
*** irenab has left #openstack-meeting-308:17
*** irenab_ has joined #openstack-meeting-308:20
*** reedip has quit IRC08:23
*** irenab_ has quit IRC08:23
*** rakhmerov has quit IRC08:26
*** rakhmerov has joined #openstack-meeting-308:26
*** reedip has joined #openstack-meeting-308:27
*** stendulker has joined #openstack-meeting-308:29
*** tonytan4ever has quit IRC08:42
*** rossella_s has quit IRC08:42
*** rossella_s has joined #openstack-meeting-308:43
*** ccamacho has joined #openstack-meeting-308:44
*** lpetrut has quit IRC08:45
*** lpetrut has joined #openstack-meeting-308:45
*** lpetrut has quit IRC08:48
*** lpetrut has joined #openstack-meeting-308:51
*** qwebirc88315 has joined #openstack-meeting-309:00
*** zz_dimtruck is now known as dimtruck09:02
*** bobh has joined #openstack-meeting-309:03
*** apetrich has quit IRC09:06
*** bobh has quit IRC09:08
*** Guest73879 has joined #openstack-meeting-309:09
*** Guest73879 has quit IRC09:10
*** tobberydberg has joined #openstack-meeting-309:11
*** dimtruck is now known as zz_dimtruck09:12
*** qwebirc88315 has quit IRC09:13
*** mickeys has joined #openstack-meeting-309:17
*** dixiaoli has quit IRC09:18
*** dixiaoli has joined #openstack-meeting-309:19
*** shuyingy_ has quit IRC09:20
*** shuyingya has joined #openstack-meeting-309:21
*** mickeys has quit IRC09:21
*** egallen has joined #openstack-meeting-309:23
*** iyamahat has joined #openstack-meeting-309:23
*** shuyingy_ has joined #openstack-meeting-309:25
*** yamahata has quit IRC09:26
*** shuyingya has quit IRC09:28
*** iyamahat has quit IRC09:33
*** wanghao_ has quit IRC09:35
*** sambetts_ is now known as sambetts09:51
*** reedip has quit IRC09:54
*** ociuhandu has quit IRC09:56
*** lpetrut has quit IRC09:57
*** lpetrut has joined #openstack-meeting-309:57
*** zz_dimtruck is now known as dimtruck10:03
*** dixiaoli has quit IRC10:06
*** dixiaoli has joined #openstack-meeting-310:11
*** dimtruck is now known as zz_dimtruck10:13
*** bauwser is now known as bauzas10:17
*** mickeys has joined #openstack-meeting-310:18
*** mickeys has quit IRC10:22
*** neiljerram has joined #openstack-meeting-310:23
*** amotoki has quit IRC10:30
*** dixiaoli has quit IRC10:37
*** sdague has joined #openstack-meeting-310:38
*** sdague_ has joined #openstack-meeting-310:38
*** ociuhandu has joined #openstack-meeting-310:38
*** dixiaoli has joined #openstack-meeting-310:38
*** sdague has quit IRC10:39
*** sdague_ is now known as sdague10:40
*** tonytan4ever has joined #openstack-meeting-310:42
*** liangy has quit IRC10:43
*** reedip has joined #openstack-meeting-310:54
*** VW has joined #openstack-meeting-311:00
*** ccamacho is now known as ccamacho|lunch11:02
*** bobh has joined #openstack-meeting-311:05
*** dixiaoli has quit IRC11:06
*** bobh has quit IRC11:09
*** reedip has quit IRC11:15
*** dixiaoli_ has joined #openstack-meeting-311:25
*** gcb has quit IRC11:25
*** stendulker has quit IRC11:26
*** alexismonville has joined #openstack-meeting-311:31
*** zhurong has joined #openstack-meeting-311:31
*** alexismonville has quit IRC11:36
*** zz_dimtruck is now known as dimtruck11:40
*** tonytan4ever has quit IRC11:42
*** dixiaoli_ has quit IRC11:44
*** amotoki has joined #openstack-meeting-311:46
*** dixiaoli has joined #openstack-meeting-311:48
*** abalutoiu_ has joined #openstack-meeting-311:51
*** lpetrut has quit IRC11:54
*** lpetrut has joined #openstack-meeting-311:54
*** abalutoiu has quit IRC11:54
*** kkxue has joined #openstack-meeting-311:54
*** tuanluong has quit IRC11:56
*** lpetrut has quit IRC12:11
*** lpetrut has joined #openstack-meeting-312:11
*** kkxue has quit IRC12:12
*** zhurong has quit IRC12:12
*** ccamacho|lunch is now known as ccamacho12:16
*** dixiaoli has quit IRC12:18
*** gouthamr has joined #openstack-meeting-312:21
*** haleyb has quit IRC12:32
*** shuyingy_ has quit IRC12:36
*** bobh has joined #openstack-meeting-312:37
*** VW has quit IRC12:39
*** bobh has quit IRC12:42
*** bobh has joined #openstack-meeting-312:42
*** rossella_s has quit IRC12:42
*** liangy has joined #openstack-meeting-312:42
*** liangy is now known as lyan12:43
*** rossella_s has joined #openstack-meeting-312:43
*** tonytan4ever has joined #openstack-meeting-312:45
*** bobh has quit IRC12:46
*** markvoelker has quit IRC12:47
*** tonytan4ever has quit IRC12:48
*** reedip has joined #openstack-meeting-312:48
*** alexismonville has joined #openstack-meeting-313:02
*** baoli has joined #openstack-meeting-313:03
*** VW has joined #openstack-meeting-313:09
*** mickeys has joined #openstack-meeting-313:10
*** VW has quit IRC13:13
*** haleyb has joined #openstack-meeting-313:14
*** VW has joined #openstack-meeting-313:14
*** bobh has joined #openstack-meeting-313:15
*** mickeys has quit IRC13:16
*** gcb has joined #openstack-meeting-313:25
*** VW has quit IRC13:29
*** tonytan4ever has joined #openstack-meeting-313:31
*** VW has joined #openstack-meeting-313:32
*** gouthamr_ has joined #openstack-meeting-313:36
*** tobberyd_ has joined #openstack-meeting-313:36
*** lhx_ has joined #openstack-meeting-313:36
*** gouthamr has quit IRC13:36
*** dimtruck is now known as zz_dimtruck13:38
*** zz_dimtruck is now known as dimtruck13:38
*** tobberydberg has quit IRC13:39
*** tobberyd_ has quit IRC13:40
*** VW has quit IRC13:41
*** VW has joined #openstack-meeting-313:43
*** dimtruck is now known as zz_dimtruck13:47
*** huanxuan has quit IRC13:47
*** gcb has quit IRC13:54
*** crushil has joined #openstack-meeting-313:54
*** gcb has joined #openstack-meeting-313:54
*** anilvenkata has quit IRC13:55
*** egallen has quit IRC13:56
*** mtanino has joined #openstack-meeting-313:57
*** ansmith has joined #openstack-meeting-314:00
gcb#startmeeting  oslo14:00
*** markvoelker has joined #openstack-meeting-314:00
openstackMeeting started Mon Mar 27 14:00:13 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, rloo,rpodolyaka, sergmelikyan, sileht, spamaps, sreshetnyak, sreshetnyak, stevemar,therve, thinrichs, toabctl, viktors, zhiyan, zzzeek14:00
jungleboyjo/  Thanks for the ping!14:00
gcbhi jungleboyj14:01
jungleboyjHello.  :-)14:01
ansmitho/14:01
lhx_o/14:01
gcbgood morning/afternoon/evening everyone  lol14:02
crushilHey. I am the Ironic liason to oslo now. I updated the ping script to update14:02
*** alexismonville has quit IRC14:03
jungleboyjcrushil:  Welcome.14:03
gcbcrushil, welcome , I should update my ping list from the ping script14:03
lhx_crushil, welcome :)14:03
gcb#topic Red flags for/from liaisons14:04
*** openstack changes topic to "Red flags for/from liaisons (Meeting topic: oslo)"14:04
*** zz_dimtruck is now known as dimtruck14:04
dimso/14:04
gcbhi dims14:04
gcbI checked our periodic jobs, didn't find failure, but  zmq jobs for oslo.messaging failed recently14:05
gcbI posted #link https://review.openstack.org/450235 to make the job non-voting, then we'll try to fix the gate14:06
*** electrocucaracha has joined #openstack-meeting-314:06
gcbhope we can make it voting again ASAP14:07
dimsack gcb14:07
gcbseems, there is no red flags, let's move on14:07
gcb#topic Releases for Pike14:07
*** openstack changes topic to "Releases for Pike (Meeting topic: oslo)"14:07
*** shuyingya has joined #openstack-meeting-314:07
gcb#link  https://review.openstack.org/45016414:08
jungleboyjSorry, in two meetings.  No red flags here.14:08
gcback, jungleboyj14:08
gcbwe usually make weekly release for oslo libraries on Monday14:09
gcb#topic stuck reviews14:10
*** openstack changes topic to "stuck reviews (Meeting topic: oslo)"14:10
*** diablo_rojo has joined #openstack-meeting-314:10
gcbAny reviews need more people to look at here ?14:11
gcb#link https://review.openstack.org/384559 seems almost ready to merge14:11
*** zhurong has joined #openstack-meeting-314:12
gcb#topic Open discussion14:12
*** openstack changes topic to "Open discussion (Meeting topic: oslo)"14:12
gcbthe last part of weekly meeting, Anyone have any questions ?14:13
gcbIt's a short meeting today lol14:15
gcbokay, let's call it meeting, thanks everyone14:16
electrocucarachathanks gcb14:16
jungleboyjgcb:  Thanks!14:16
jungleboyjHave a great week.14:16
*** electrocucaracha has left #openstack-meeting-314:16
gcbelectrocucaracha, jungleboyj , have a nice day14:16
lhx_gcb, thanks :)14:16
gcb#endmeeting14:16
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"14:16
openstackMeeting ended Mon Mar 27 14:16:53 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:16
openstackMinutes:        http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-03-27-14.00.html14:16
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-03-27-14.00.txt14:16
openstackLog:            http://eavesdrop.openstack.org/meetings/oslo/2017/oslo.2017-03-27-14.00.log.html14:16
*** crushil has left #openstack-meeting-314:16
gcbthanks lhx_14:17
lhx_I'd like to look into the gate issue14:18
lhx_for oslo.messaging14:18
gcblhx_, let's talk at #openstack-oslo14:19
*** diga has joined #openstack-meeting-314:19
*** diga has left #openstack-meeting-314:19
*** sharatss has joined #openstack-meeting-314:20
*** ccamacho is now known as ccamacho|brb14:25
*** alexismonville has joined #openstack-meeting-314:28
*** marst has quit IRC14:30
*** VW has quit IRC14:32
*** VW has joined #openstack-meeting-314:32
*** alexismonville has quit IRC14:33
*** abalutoiu__ has joined #openstack-meeting-314:35
*** seanatcisco has joined #openstack-meeting-314:35
*** superdan is now known as dansmith14:38
*** abalutoiu_ has quit IRC14:38
*** zhurong has quit IRC14:41
*** lpetrut has quit IRC14:43
*** marst has joined #openstack-meeting-314:44
*** Michael-ZTE has joined #openstack-meeting-314:49
*** yamahata has joined #openstack-meeting-314:56
*** iyamahat has joined #openstack-meeting-314:56
*** thrash has joined #openstack-meeting-314:58
*** toure has joined #openstack-meeting-314:59
*** rbrady has joined #openstack-meeting-315:00
*** marst has quit IRC15:04
*** tonytan_brb has joined #openstack-meeting-315:06
*** tonytan4ever has quit IRC15:07
*** nkrinner is now known as nkrinner_afk15:08
*** annegentle has joined #openstack-meeting-315:08
toured0ugal meeting?15:10
d0ugaltoure: rakhmerov is running late15:10
*** joanna has joined #openstack-meeting-315:10
tourecool15:10
tourethanks15:10
d0ugaltoure: I wasn't sure if I should start it or just wait15:10
d0ugalI guess I can start it and we can have an open discussion until he arrives15:10
toureI am fine either way15:10
d0ugal#startmeeting mistral15:11
openstackMeeting started Mon Mar 27 15:11:27 2017 UTC and is due to finish in 60 minutes.  The chair is d0ugal. Information about MeetBot at http://wiki.debian.org/MeetBot.15:11
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:11
*** openstack changes topic to " (Meeting topic: mistral)"15:11
openstackThe meeting name has been set to 'mistral'15:11
d0ugalHey - who is here for the Mistral meeting?15:11
tourehello :)15:12
d0ugalWe are just waiting for rakhmerov to arrive before we start properly.15:12
*** VW has quit IRC15:12
d0ugalso before he does, we can just chat about anything people have15:12
*** VW has joined #openstack-meeting-315:12
sharatssme o/15:12
d0ugalHey sharatss15:13
rbrady\o15:13
thrasho/15:13
*** jozsef_kupai has joined #openstack-meeting-315:13
rbradyI'll be here for the next 10 min15:13
thrashsame ^^15:14
d0ugalcool, you can both entertain us until rakhmerov arrives :)15:14
* thrash dances15:14
tourehehe15:14
*** donghao has joined #openstack-meeting-315:15
d0ugaloh, cool, I see the Advanced Publishing spec landed.15:16
d0ugalhttp://specs.openstack.org/openstack/mistral-specs/specs/pike/approved/advanced_publishing.html15:16
d0ugalIt is worth a read if you've not seen it yet - should be a useful addition.15:16
d0ugalJump to the examples at the end of the "Proposed change" for the TLDR15:17
d0ugalrbrady: speaking of specs, do you if there is any ideas/info around for the securing sensitive information?15:18
d0ugalI assume it came up at the PTG15:18
rbradyyes...there was some initial ideas in the etherpad.  I'm not sure if anyone has started a spec for it yet.  if not, it's something I could start in the next couple of days15:19
d0ugalcool, would be interesting to see.15:24
rbrady#action rbrady start sensitive data spec15:26
*** alexismonville has joined #openstack-meeting-315:26
rbradyalright, my times up.  I will see you all in #openstack-mistral later15:26
d0ugalcya15:26
d0ugalI'm wondering if rakhmerov is going to make it :)15:26
d0ugalAnyone got any bugs to discuss or review requests?15:27
*** rbrady is now known as rbrady-afk15:27
d0ugalI'll wait a bit longer and then we can run through the normal agenda - probably not that much to cover this week15:27
*** lucasxu has joined #openstack-meeting-315:29
d0ugal#topic Review action items15:30
*** openstack changes topic to "Review action items (Meeting topic: mistral)"15:30
d0ugalOkay, so from last week we had two action items.15:31
d0ugal1. mgershen/team to talk with Renat about bug https://bugs.launchpad.net/mistral/+bug/167237915:31
openstackLaunchpad bug 1672379 in Mistral "default task on error not running when task fail to evaluate input" [Undecided,Invalid]15:31
d0ugalSince neither seem to be here, I'll just add that again so it isn't lost.15:32
d0ugal#action mgershen/team to talk with Renat about bug https://bugs.launchpad.net/mistral/+bug/167237915:32
d0ugal2. d0ugal to make a bug about using KeyStone sessions when we create OpenStack clients15:32
rakhmerovd0ugal: I'm here15:32
rakhmerovsorry15:32
d0ugalrakhmerov: hey, no problem15:32
*** VW has quit IRC15:32
d0ugalrakhmerov: I just started to go through the action items from last time - we have had a bit of open discussion initially just while we waited.15:32
*** VW has joined #openstack-meeting-315:33
rakhmerovooh, ok15:33
rakhmerovsure15:33
rakhmerovplease keep going15:33
rakhmerovI'll catch up15:33
d0ugalI've not done my action item ^ - so I'll just quickly open the bug now15:34
*** galstrom_zzz is now known as galstrom15:34
rakhmerovok15:35
d0ugal#link https://bugs.launchpad.net/mistral/+bug/167648515:36
openstackLaunchpad bug 1676485 in Mistral "Use Keystone sessions to create Mistral clients" [Medium,Confirmed]15:36
d0ugalOkay, that is that action item done now :)15:36
d0ugalrakhmerov: Unless you want to discuss https://bugs.launchpad.net/mistral/+bug/1672379 now (but maybe better when mgershen is here) we are finished with the action items15:36
openstackLaunchpad bug 1672379 in Mistral "default task on error not running when task fail to evaluate input" [Undecided,Invalid]15:36
rakhmerovMichal said she wouldn't be here today15:37
d0ugalokay, np15:37
rakhmerovyeah, well, we already had a quick chat about this bug15:37
rakhmerovwith her and my boss15:37
d0ugaloh, cool - I see you commented on it recently.15:37
rakhmerovit's not really a bug, I think I was able to explain her and she was going to create a BP15:38
rakhmerovyeah, if details are needed I can provide them15:38
d0ugalcool, thanks15:38
d0ugalrakhmerov: okay, you can take over with the current status section now if you want :)15:38
rakhmerovin a nutshell, this behavior was a result of long discussions and considerations and it's the way we designed it on purpose15:39
rakhmerovd0ugal: is there actually anyone else on the meeting besides me and you? :)15:39
d0ugal#chair rakhmerov15:39
openstackCurrent chairs: d0ugal rakhmerov15:39
rakhmerov#topic Current status15:40
*** openstack changes topic to "Current status (Meeting topic: mistral)"15:40
d0ugalrakhmerov: Good question. toure and sharatss might still be here.15:40
d0ugalbut rbrady-afk had to leave and I think thrash did too15:40
toureI am catching up, had to step away for a sec15:40
rakhmerovmy status: was on sick leave most of the last week, working on advanced publishing (publishing to different scopes + defining it in 'on-xxx')15:40
rakhmerovtoure: ok15:40
*** andreas_s has quit IRC15:41
rakhmerovthe task (advanced publishing) seems to be pretty hairy actually because it requires a serious refactoring first15:41
tourestatus: working on finalizing POC for workflow error analysis will post a review today15:41
rakhmerovto keep backwards compatibility15:41
d0ugalstatus: looking for another review on the mistral-extra spec. https://review.openstack.org/44699615:41
rakhmerovtoure: you're working on an endpoint now?15:42
rakhmerovtoure: can you just remind what's going to be a part of the POC?15:42
tourerakhmerov yeah, so I created a report endpoint15:42
sharatssstatus: working on keystoneauth migration and mistral-congress integration. will commit in a day or two15:42
rakhmerovd0ugal: I'll ask mgershen to review it tomorrow15:42
tourethis will include a controller backed by a service15:42
d0ugalrakhmerov: thanks15:43
tourerakhmerov ^^15:43
rakhmerovtoure: yep, ok15:43
tourerakhmerov I have also the clientside roughly worked out, need some more work also15:43
rakhmerovtoure: I saw that the spec has -1 for some reason, so I didn't look at the latest version yet15:43
d0ugalI think the -1 is mostly for small things15:44
tourerakhmerov there were a few formatting concerns which I addressed15:44
rakhmerovbut if you think I need to review it now I'll do (early feedback kinda)15:44
rakhmerovokay15:44
rakhmerovgot it15:44
rakhmerovtoure: ok, awesome15:44
rakhmerovlooking forward to seeing something working :)15:44
tourerakhmerov I think I will pick up that other blueprint in regards to error seperation15:44
tourerakhmerov thanks15:44
*** mickeys has joined #openstack-meeting-315:45
rakhmerovtoure: yes, feel free15:45
tourehttps://blueprints.launchpad.net/mistral/+spec/mistral-error-separation15:45
touresome of that wourk will be addressed in the other spec15:46
rakhmerovand also keep that error info structuring in mind15:46
rakhmerovstack trace stored in a different field etc.15:46
toureyup15:46
rakhmerovwhat we discussed at the PTG15:46
*** jozsef_kupai has left #openstack-meeting-315:46
rakhmerovok15:47
rakhmerovd0ugal: besides that spec (which seems to be good already), is there anything else you're now working on?15:48
rakhmerovmaybe you need help or something15:48
d0ugalrakhmerov: I am going to start implementing it soon, but last week I focused on a few TripleO tasks.15:48
rakhmerovok15:49
d0ugalrakhmerov: I did also spend a bit of time thinking how a "run-workflow" command would work - we talked about it before briefly15:49
rakhmerovd0ugal: on a different topic, has anyone from other teams already contacted you on docs?15:49
d0ugalbut the idea was to have a way to run a workflow so you can test it out without having to do create/update etc :)15:49
rakhmerovd0ugal: you're a doc liaison so I wonder if someone talks to you :)15:49
d0ugalrakhmerov: not really, I had one email related to it - but if I remember it wasn't relevant to Mistral15:50
d0ugalI'll check15:50
rakhmerovok15:50
rakhmerovnp, just reminding about it so that you might want to configure email etc. :)15:51
d0ugal#action d0ugal to check for doc liaison tasks15:51
rakhmerovd0ugal: yeah, that 'run-workflow' thing would be cool to have15:51
d0ugalrakhmerov: yup, thanks - I do forget about it sometimes and then remember and wonder if I have missed something - so I'll look again15:51
*** benj_ has quit IRC15:51
rakhmerov#action rakhmerov: ask Michal to review the spec about mistral-extra15:51
rakhmerovsure, ok15:52
*** bobh has quit IRC15:52
d0ugalrakhmerov: I wasn't sure how it would work with the API - I think the best place would be to let the user pass a workflow file to execution creation, but that seemed a bit wrong.15:52
*** bobh has joined #openstack-meeting-315:52
rakhmerovd0ugal: yeah, that's hairy15:53
rakhmerovd0ugal: if you want we can chat about it tomorrow in IRC15:53
d0ugalsure15:53
rakhmerovtasks like this always challenge design )15:54
d0ugalIndeed :)15:54
rakhmerovas far as storing workflows/workbooks and using them I believe our design might not be flexible enough15:54
rakhmerovok, we'll talk about it separately15:55
*** lpetrut has joined #openstack-meeting-315:55
d0ugalI did have one other big idea :)15:55
rakhmerovI don't have much else actually :)15:55
rakhmerovd0ugal: what was that?15:56
rakhmerov)15:56
d0ugalDo you know the Postgres query planner? I thought something like that for Mistral would be cool - so it would describe to you what a workflow would do15:56
rakhmerovd0ugal: yeah, pretty much every decent RDBMS has something similar15:56
d0ugalyeah15:56
rakhmerovhm.. interesting15:57
d0ugalI guess a first step would be to have something that shows you the workflow graph15:57
d0ugalbut that could get tricky to represent15:57
*** emagana has joined #openstack-meeting-315:57
d0ugalanyway, it is just an early idea for now :-D15:57
rakhmerovI'm trying to imagine what a plan of WF should look like15:57
toure+1 d0ugal's idea15:57
*** amotoki has quit IRC15:57
d0ugalCompring with a query planner is maybe not the best idea15:58
*** rpioso has joined #openstack-meeting-315:58
rakhmerovbtw, a very cool graphical tool is being developed inside Nokia now, it already does a lot15:58
d0ugalbasically I am thinking about tools to help you understand and analyze workflows15:58
*** donghao has quit IRC15:58
d0ugaloh, nice15:58
rakhmerovonce we can we'll show a demo I guess15:59
d0ugalrakhmerov: will that be open sourced? :)15:59
*** rama_y has joined #openstack-meeting-315:59
rakhmerovd0ugal: yeah, that's really good. That's the direction that I'm mentally taking now in terms of development15:59
rakhmerovbeing more usable15:59
d0ugalawesome16:00
d0ugaland that takes us to the end of our time16:00
rakhmerovd0ugal: yes, that's the plan, it's planned to be open sourced16:00
d0ugalgreat16:00
rakhmerovyep16:00
rakhmerovbye everyone16:00
d0ugalThanks all16:00
d0ugal#endmeeting16:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:00
openstackMeeting ended Mon Mar 27 16:00:46 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-03-27-15.11.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-03-27-15.11.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/mistral/2017/mistral.2017-03-27-15.11.log.html16:00
*** vsaienk0 has joined #openstack-meeting-316:01
tourecya16:01
*** toure has left #openstack-meeting-316:01
*** tonytan_brb has quit IRC16:03
*** tonytan4ever has joined #openstack-meeting-316:03
*** vgadiraj_ has joined #openstack-meeting-316:03
*** crushil has joined #openstack-meeting-316:04
*** haleyb has quit IRC16:05
*** aarefiev is now known as aarefiev_afk16:05
*** thrash has left #openstack-meeting-316:06
*** tobberydberg has joined #openstack-meeting-316:12
*** cinerama has joined #openstack-meeting-316:12
*** sharatss has quit IRC16:12
*** tobberydberg has quit IRC16:16
*** haleyb has joined #openstack-meeting-316:20
*** matrohon has quit IRC16:23
*** milan has joined #openstack-meeting-316:23
*** mgould has joined #openstack-meeting-316:26
*** mgould has left #openstack-meeting-316:26
*** lhx_ has quit IRC16:30
*** psachin has quit IRC16:32
*** Swami has joined #openstack-meeting-316:35
*** shuyingya has quit IRC16:35
*** annegentle has quit IRC16:35
*** alexismonville has quit IRC16:42
*** rossella_s has quit IRC16:42
*** rossella_s has joined #openstack-meeting-316:43
*** stendulker has joined #openstack-meeting-316:48
*** stendulker has quit IRC16:48
*** rloo has joined #openstack-meeting-316:48
*** stendulker has joined #openstack-meeting-316:49
*** cleong has joined #openstack-meeting-316:53
*** baha has joined #openstack-meeting-316:54
*** aNuposic has joined #openstack-meeting-316:56
*** lucasagomes has joined #openstack-meeting-316:56
*** mariojv has joined #openstack-meeting-316:57
*** vgadiraj_ has quit IRC16:58
*** amotoki has joined #openstack-meeting-316:58
*** donghao has joined #openstack-meeting-316:59
jroll#startmeeting ironic17:00
openstackMeeting started Mon Mar 27 17:00:00 2017 UTC and is due to finish in 60 minutes.  The chair is jroll. Information about MeetBot at http://wiki.debian.org/MeetBot.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
vdroko/17:00
lucasagomeso/17:00
bahao/17:00
xavierro/17:00
NobodyCamo/17:00
mariojvhi o/17:00
milano/17:00
rama_yo/17:00
jrollmmm, this chair is comfy, it's been a while17:00
jlvillalo/17:00
rlooo/17:00
stendulkero/17:00
TheJuliao/17:00
NobodyCam:p17:00
joannao/17:00
jrollhi everyone!17:00
*** annegentle has joined #openstack-meeting-317:00
* rloo hopes jroll doesn't fall asleep in comfy chair...17:00
TheJuliaheh17:00
*** vgadiraj_ has joined #openstack-meeting-317:00
jrollpft, I'm wide awake :D17:00
*** mjturek has joined #openstack-meeting-317:01
vgadiraj_o/17:01
jroll#topic announcements and reminders17:01
*** openstack changes topic to "announcements and reminders (Meeting topic: ironic)"17:01
jrollcouple things17:01
* NobodyCam not has monty python skit running through his head17:01
mjtureko/17:01
crushil\o17:01
jrolldmitry is out this week17:01
jrollI'm also planning to do a nice small release of ironic before we start slamming features home17:01
jrolland ironicclient17:01
Michael-ZTE\o17:01
jrolland ironic-lib17:01
jrollstill need to check the rest17:01
*** pc_m has joined #openstack-meeting-317:02
jrollwill do those this afternoon17:02
TheJuliajroll: I think bifrost as well, will double check in a little bit17:02
lucasagomesnice, I plan to release sushy this week as well17:02
jrollTheJulia: nice, thanks17:02
rloojroll: hmm, can we wait til we land the api for dynamic drivers?17:02
rloojroll: ah, maybe not. i'm not sure it'll be ready in time.17:02
jrollrloo: maybe, let's talk later17:02
TheJuliaOne other announcement.  I sent an email about a half hour ago to the cores that I would appreciate feedback on in the next day or two.  Thanks in advance!17:02
rpiosoo/17:02
*** armax has joined #openstack-meeting-317:02
*** amotoki has quit IRC17:03
jrollthanks TheJulia17:03
jrollany other announcements?17:03
jroll#topic review subteam status updates17:04
*** openstack changes topic to "review subteam status updates (Meeting topic: ironic)"17:04
jrollas always, those are here17:04
jroll#link https://etherpad.openstack.org/p/IronicWhiteBoard17:04
jrollline 7917:04
*** soliosg has joined #openstack-meeting-317:04
* jroll gives a friendly reminder to do these before the meeting, not during :)17:04
jrollvsaienk0: nice work on standalone stuff :)17:05
* rloo just updated Bugs stats17:05
lucasagomes++ vsaienk017:06
alezilo/17:06
* TheJulia glares at etherpad for eating her update17:06
jlvillal++ on stand-alone :)17:07
jlvillalAlso looking forward to vsaienk0's increased concurrency patch, if it works. Big time savings :)17:07
rloovdrok: are you taking over the node tags stuff?17:08
vsaienk0thanks folks!17:08
vdrokrloo: i can't say taking over, but I'll be updating them if zhenguo is not around17:08
rloogreat work vsaienk017:08
rloovdrok: thx!17:08
rloovsaienk0, sambetts: any idea what the status is wrt routed networks support? (L188)17:08
vsaienk0rloo: I'm still working on initial commits for networking-baremetal project17:10
rloovsaienk0: ok, i'll add that to the status, thx.17:10
jrollrouted networks support is mostly about scheduling, right? I can't remember the difference between that and "physical network awareness"17:10
TheJuliawe have to be aware of the networks to be able to schedule on them correctly17:11
jrolloh and more17:11
* jroll reads http://specs.openstack.org/openstack/ironic-specs/priorities/pike-priorities.html#routed-networks-support17:11
sambettsjroll: I think there is some other weird things there that require research but the physical awareness is a big part of it17:11
vdrokbtw routed networks spec has merged today17:11
jrollsambetts: right, they're two separate priorities/subteams, that's why I ask17:11
vsaienk0jroll: no not only about scheduling, we need to create a mechanism which will populate nova hypervisor (ironic node) to neutron segments mapping17:12
rloovdrok: is the link to that spec, in the etherpad (subteam report par)?17:12
jrollvsaienk0: right17:12
jrollrloo: it is17:12
*** pcaruana has quit IRC17:12
jroll\o/ for merging that17:12
vdrokyup17:12
rloojroll: it is? oh, do you mean the physical network spec?17:13
jrollrloo: yes, I know you weren't directing the question at me but I answered it17:13
mariojvyeah, physnet spec was landed - i didn't see the routed nets one though ?17:13
rloojroll: thx. and mariojv ++, that's what i thought we were talking about but guess not.17:13
jrollanything else on subteam updates? they seem legit to me17:14
jrollmariojv: yeah, I haven't seen a spec on that yet17:14
* jroll waits a sec17:14
mariojvcool - RFE is here, i'll put a link to that for tracking on the status page for now: https://bugs.launchpad.net/ironic/+bug/165896417:14
openstackLaunchpad bug 1658964 in Ironic "[RFE] Implement neutron routed networks support in Ironic" [Wishlist,Confirmed]17:14
*** ociuhandu has quit IRC17:14
rloothx mariojv17:15
jroll#topic Deciding on priorities for the coming week17:15
*** openstack changes topic to "Deciding on priorities for the coming week (Meeting topic: ironic)"17:15
jrolllooks like we were 1/5 last week17:15
vdrokI think we need to prioritize the rolling upgrades17:15
jrollso I suggest just leaving the same 4 there17:15
vdrokotherwise any patch bumping object version or rpc version breaks the grenade multinode job17:16
vdrokeg https://review.openstack.org/23335717:16
*** bfournie has joined #openstack-meeting-317:16
mariojvvdrok: i'm fine with adding rolling upgrades to that list, too - maybe at the bottom so folks review stuff that's lagging behind first?17:16
jrollthough... did folks find blockers with those? or is it just slow review/code cycle? are the existing things there close to ready?17:16
mariojvmaybe top is better to prevent that breakage, though17:16
NobodyCam++ for rolling upgrades17:16
jrollvdrok: yikes17:17
*** Patifa has joined #openstack-meeting-317:17
jrollthat seems... wrong17:17
rloowrt rolling upgrades. i rebased them last week, and fixed some stuff in one patch. there's *one* patch I'm not sure about. although others are welcome to review. i'd like to test this week.17:17
vdrokI think this includes the first patch in the chaing for rolling upgrades + adding some pins to our devstack plugin17:17
TheJuliaThat kind of does, but I'm +1 on rolling upgrades17:17
* jroll would love a doc on how the multinode grenade works17:18
rloovdrok: will talk to you later on irc about the rolling upgrades stuff17:18
rloo++ jroll. that is on my list this week to understand.17:18
vdrokrloo: ok sure17:18
vdrokbasically, we need to be able to pin things17:18
*** harlowja has quit IRC17:18
jrollyeah, it just seems like a compatible rpc bump should work anyway17:19
jrollwe can discuss that later17:19
jrollso rolling upgrades priority 1 or "last"?17:19
* TheJulia thinks priority 117:19
* NobodyCam would like to see 117:19
mariojv+117:19
jrollokay17:19
jrollif someone could throw the gerrit link there on the whiteboard, that would be awesome17:20
jrollany other priority change requests or are we good?17:20
rloojroll: done17:21
jrollthanks17:21
NobodyCamty rloo17:21
NobodyCam:)17:21
*** ricardoas has joined #openstack-meeting-317:21
jrollno stuck specs, discussion time17:21
jroll#topic CI failure rates17:21
*** openstack changes topic to "CI failure rates (Meeting topic: ironic)"17:21
jrollthis is TheJulia17:21
jroll#link http://paste.openstack.org/show/603960/17:21
TheJuliaSo dmitry put together a report at http://paste.openstack.org/show/603960/ that shows CI failure rates, and a major point of concern is the third party CI jobs.17:22
TheJuliaI guess the biggest question is if anyone has any insight as to why the failure rates are so much higher, and how we can make it better?17:23
rpiosoWe've been actively working on the issue -- http://lists.openstack.org/pipermail/openstack-infra/2017-March/005263.html17:23
*** markvoelker has quit IRC17:23
vdrokI think we can remove the parallel job now that we have the standalone tests?17:23
*** harlowja has joined #openstack-meeting-317:24
lucasagomes(just a note, the UEFI job is now voting in gate)17:24
mariojvTheJulia: are the top 4 jobs there (starting L151) expected to have 100% failure rates?17:24
vdrokgate-tempest-dsvm-ironic-parallel-ubuntu-xenial-nv17:24
vdrokor is it about the third party ci only? :)17:24
rlooTheJulia: I thought Dmitry said he'd get in touch with the 4rd party CI folks about their tests failing17:24
rloos/4/3/ :)17:24
jrollmariojv: they're experimental, so probably a WIP or abandoned WIP17:24
jlvillalA lot of those top jobs consist of our experimental jobs.17:25
jlvillalSome could probably be pruned17:25
TheJuliarloo: He indicated he was going to reach out, but I'm wondering if any of us in the larger community have any insight into the third party ci jobs failures, since the rates do see rather high across the board.  If it is something we're doing, we should likely fix it :)17:25
jlvillalBut they only get run if someone does "check experimental"17:25
mariojvok cool, just wanted to be sure there's not some super serious breakage there17:26
jrollI think we can probably kill parallel like vdrok said. the py3 jobs need to get working. the full, I would like to keep around, but I don't have much time lately to work on it17:26
jrollthe third party stuff, those parties will need to speak for :)17:26
vdrokalso, I don't see the ibm ci here in this list17:26
jlvillalI think JayF and hurricanerix are working or will be working on the Python3 jobs. Based on owners for Pike priorities.17:26
rlooI think we should/could either 1. wait for dmitry to get back to find out where/what he's done and/or 2. send email to the dev list.17:26
rajinirA bunch of devstack changes broke our CI. Not sure about others17:27
jrollI'd wait for dmitry on third party stuff17:27
TheJuliarloo: That is reasonable, I was just kind of hoping that people might have gained some insight by looking at failed third party CI logs when doing reviews17:27
xavierrrajinir: ++17:27
rlooTheJulia: honestly, they seem to fail so often that I don't look at them :-(17:27
jlvillalrloo: +1 on that.17:28
mariojvsame rloo17:28
milanvdrok, maybe it means it's passing all the time (passing as in def test(self): pass) ;)17:28
jrollrloo: right, that's one of dmitry's goals to fix this cycle, it seems17:28
mariojvi basically have 0 confidence voting on a lot of driver patches because of the CI flakiness there17:28
vdrokmilan: hopefully not :)17:28
rlooi think it was discussed before so i don't want to go over it now, but we need some definitive place to see the status of the 3rd party tests. that would at least give us an indication if we should look or not, to see if our patch is causing a failure.17:28
TheJuliaOkay, well it sounds like we have work to do.  Lets see what dmitry gets back from the 3rd party CI operators and go from there.17:28
TheJuliaThank you everyone17:29
jrollthanks for bringing it up, TheJulia :)17:29
rlooTheJulia: maybe add agenda item (again) for next week :)17:29
mariojv++17:29
rlooTheJulia: although dmitry might not be ready to give any update17:29
TheJuliarloo: excellent idea!17:29
rloothat'll teach him to go on PTO17:30
jrollrough17:30
TheJuliaheh17:30
lucasagomeslol17:30
rlooha ha17:30
NobodyCam:p17:30
jroll#topic open discussion17:30
*** openstack changes topic to "open discussion (Meeting topic: ironic)"17:30
jrollanything else?17:30
* TheJulia hears crickets17:30
rloojroll: oh, just remembered. do we have a bug triager?17:31
jrollrloo: not on the agenda, not my job!17:31
jroll:D17:31
NobodyCamjust a thank you to lucasagomes: for the red fish work17:31
rloojroll: ha ha. it got deleted from the agenda :)17:31
jrollwho wants to triage the bugs?17:31
lucasagomesNobodyCam, :-) cheers man17:31
TheJuliaI have brain cells, I can go through the new bugs17:31
jrollthanks again to mjturek for doing it again17:31
vdrokI can help with bug triage this week17:31
jrollTheJulia: vdrok: battle17:31
vdrok:D17:31
TheJulialol17:31
jrollI'll just mark both of you, thanks!17:31
vdrokyup17:32
* TheJulia suddenly thinks of "The Princess Bride"17:32
rloooh, wrt the brainstorming/forum thing. i'm guessing nothing happened there?17:32
jrollmuahaha17:32
rloofor the summit?17:32
*** gouthamr_ is now known as gouthamr17:32
TheJuliarloo: nope, I believe jroll submitted the tc inspired session17:32
rlooi forgot when the deadline was. apr 1? or already past?17:32
jrollyeah, the vm/baremetal session is proposed17:32
TheJuliaor someone did17:32
jrolland stig telfer proposed a "Baremetal BIOS/RAID reconfiguration according to instance" topic17:33
mariojv#link https://etherpad.openstack.org/p/BOS-ironic-brainstorming17:33
jrollhttp://forumtopics.openstack.org/ for the record17:33
mariojv^ there's the brainstorming etherpad, not a ton of stuff there17:33
*** lpetrut has quit IRC17:33
jrollrloo: april 217:33
mariojvlooks like a couple ideas about ops feedback17:33
xavierrwill you ironicers attend boston summit?17:33
* jroll makes a todo to add these things17:33
TheJuliaYeah, I had no braincells last week.17:33
rloothx jroll et al!17:34
jrollxavierr: I know at least two people are going, maybe 3, maybe more17:34
*** rossella_s has quit IRC17:34
* jroll counts down from 10 before closing the meeting, chirp up if you have something17:35
rloocrickets?17:35
jroll#endmeeting17:35
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:35
openstackMeeting ended Mon Mar 27 17:35:24 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:35
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-03-27-17.00.html17:35
jrollthanks y'all!17:35
Michael-ZTE8817:35
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-03-27-17.00.txt17:35
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2017/ironic.2017-03-27-17.00.log.html17:35
mariojvthanks all!17:35
lucasagomesty all17:35
*** mariojv has left #openstack-meeting-317:35
Michael-ZTEthanks all17:35
xavierrty17:35
TheJuliaThank you everyone17:35
*** rloo has left #openstack-meeting-317:35
*** lucasagomes has left #openstack-meeting-317:35
*** baha has left #openstack-meeting-317:35
*** ricardoas has left #openstack-meeting-317:35
*** rpioso has left #openstack-meeting-317:36
*** milan has quit IRC17:38
*** armax_ has joined #openstack-meeting-317:39
*** Michael-ZTE has quit IRC17:39
*** armax has quit IRC17:39
*** armax_ is now known as armax17:39
*** milan has joined #openstack-meeting-317:39
*** lucasxu has quit IRC17:40
*** pc_m has left #openstack-meeting-317:40
*** aNuposic has left #openstack-meeting-317:43
*** vgadiraj_ has quit IRC17:44
*** mtanino has quit IRC17:44
*** ccamacho|brb is now known as ccamacho17:46
*** baoli has quit IRC17:49
*** ociuhandu has joined #openstack-meeting-317:50
*** stendulker has quit IRC17:54
*** ociuhandu has quit IRC17:55
*** s3wong has joined #openstack-meeting-317:57
*** amotoki has joined #openstack-meeting-317:59
*** baoli has joined #openstack-meeting-317:59
*** MeganR has joined #openstack-meeting-318:01
*** amotoki has quit IRC18:03
*** anilvenkata has joined #openstack-meeting-318:05
*** bfournie has left #openstack-meeting-318:05
*** milan has quit IRC18:08
*** milan has joined #openstack-meeting-318:10
*** rbrady-afk is now known as rbrady18:10
*** ralonsoh has quit IRC18:11
*** lucasxu has joined #openstack-meeting-318:11
*** mtanino has joined #openstack-meeting-318:12
*** marst has joined #openstack-meeting-318:12
*** armax has quit IRC18:13
*** bobh has quit IRC18:15
*** pvaneck has joined #openstack-meeting-318:21
*** armax has joined #openstack-meeting-318:22
*** lamt has joined #openstack-meeting-318:23
*** baoli_ has joined #openstack-meeting-318:24
*** baoli has quit IRC18:25
*** d0ugal has quit IRC18:31
*** stanchan has joined #openstack-meeting-318:33
*** ociuhandu has joined #openstack-meeting-318:35
*** iyamahat has quit IRC18:35
*** yamahata has quit IRC18:36
*** milan has quit IRC18:39
*** ociuhandu has quit IRC18:40
*** milan has joined #openstack-meeting-318:40
*** armax has quit IRC18:41
*** milan has quit IRC18:46
*** bswartz has quit IRC18:47
*** d0ugal has joined #openstack-meeting-318:47
*** bswartz has joined #openstack-meeting-318:48
*** stanchan has quit IRC18:59
*** stanchan has joined #openstack-meeting-319:00
*** amotoki has joined #openstack-meeting-319:00
*** iyamahat has joined #openstack-meeting-319:00
*** yamahata has joined #openstack-meeting-319:01
*** amotoki has quit IRC19:05
*** mlavalle has joined #openstack-meeting-319:13
*** sambetts is now known as sambetts|afk19:13
*** soliosg has left #openstack-meeting-319:20
*** anilvenkata has quit IRC19:22
*** vkmc has joined #openstack-meeting-319:25
*** kzaitsev_mb has joined #openstack-meeting-319:26
*** baoli_ has quit IRC19:32
*** kzaitsev_mb has quit IRC19:35
*** baoli has joined #openstack-meeting-319:39
*** aimeeu__ has joined #openstack-meeting-319:41
*** aimeeu has quit IRC19:41
*** aimeeu__ is now known as aimeeu19:41
*** crushil has quit IRC19:44
*** annegentle has quit IRC19:44
*** ionutbalutoiu has quit IRC19:45
*** annegentle has joined #openstack-meeting-319:46
*** joanna has quit IRC19:49
*** ionutbalutoiu has joined #openstack-meeting-319:49
*** tonytan4ever has quit IRC19:51
*** tonytan4ever has joined #openstack-meeting-319:53
*** blancos has joined #openstack-meeting-319:56
*** lamt has quit IRC19:56
*** lamt has joined #openstack-meeting-319:58
*** jaypipes has joined #openstack-meeting-319:59
ildikov#startmeeting openstack-upstream-institute20:00
openstackMeeting started Mon Mar 27 20:00:29 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
jaypipeso./20:00
jungleboyjo/20:00
* diablo_rojo is back from Mexico :) 20:01
mlavalleo/20:01
ildikovbauzas: are you around too?20:01
bauzasyup20:01
ildikovdiablo_rojo: welcome back :)20:01
blancoso/20:01
diablo_rojoildikov, thanks :)20:01
* bauzas waves even if DST-impacted :)20:01
spotz\o/20:01
ildikovbauzas: I hear ya!20:01
*** baoli has quit IRC20:02
ildikovlet's wait one more minute and then start20:02
*** baoli has joined #openstack-meeting-320:02
*** annegentle has quit IRC20:02
spotzWe have a git section don't we?20:03
ildikovok, let's get into it20:04
mrhillsmano/20:04
ildikovspotz: you mean the follow up session we talked about?20:04
* mrhillsman being a fly on the wall20:04
spotzildikov: No during training, just contacted github to get cheat sheets for the lunch and learn, I'll ask for me if we need them for the weekend too:)20:05
spotzme=more20:05
diablo_rojospotz, yes we have a section on git20:05
spotzdiablo_rojo: Ok I'll bump my request by 50? when I hear back20:05
diablo_rojospotz, all the sections are here: https://docs.openstack.org/upstream-training/20:05
ildikovspotz: I think an advanced session would be better as that lunch slot or a follow up during the week20:06
diablo_rojoildikov, +120:06
ildikovif we do that as a lunch session during the training people's head will fall off :)20:06
spotzildikov: Ok we can just send folks to the Lunch and Learn on Wednesday20:06
ildikovspotz: +120:06
diablo_rojospotz, yeah it might be good to collect all of those sessions and promote them towards the end of the training as possible next steps20:06
ildikovspotz: we can add material about it though and if everyone turns out to be experienced we can switch to that20:07
jungleboyjildikov:  ++20:08
ildikovspotz: jungleboyj: I'm not holding my breath though :)20:08
spotzheheh20:08
jungleboyjProbably true.20:09
ildikovmrhillsman: glad you joined! :)20:09
jungleboyjNone the less, information we will need for the future.20:09
ildikovok, let's switch to the first topic20:09
ildikovjungleboyj: +120:09
*** markvoelker has joined #openstack-meeting-320:09
ildikov#topic Training exercises20:09
*** openstack changes topic to "Training exercises (Meeting topic: openstack-upstream-institute)"20:09
ildikovso we have an etherpad for that20:09
ildikov#link https://etherpad.openstack.org/p/upstream-training-exercises20:09
* smcginnis sneaks in late...20:10
ildikovit would be great to revitalize them as much as possible20:10
* jungleboyj gives smcginnis the evil eye20:10
ildikovsmcginnis: hi, thanks for joining :)20:10
ildikovthe plan is to try to teach the most things as part of an exercise20:11
diablo_rojoIf people can generate ideas for more exercises I am willing to make the changes in the slides.20:11
ildikovlet people find the info and figure out things for themselves20:11
jungleboyjildikov:  Like that idea.20:11
jungleboyjKeep them engaged and busy.20:11
ildikovalso the driving force for updating the slides should be the exercises20:11
ildikovjungleboyj: +120:12
diablo_rojoildikov, agreed :)20:12
ildikovin Barcelona we spent a lot of time with introductions, we should change this for Boston20:13
diablo_rojoI think we need to reduce the content in favor of exercises and then maybe add the things we want them to learn as notes on the exercises so that we know to highlight those things as we are having students do the exercises20:13
spotzdiablo_rojo: +120:13
ildikovdiablo_rojo: +120:14
jungleboyjildikov:  Yeah, that was pretty consistent feedback that we didn't need so much of that.20:14
spotzildikov: Was there any specific feedback from Barcelona that needs to be addresses?20:14
jungleboyjdiablo_rojo:  Makes sense.20:14
ildikovspending time on the slides can be boring and people start to disengage quickly20:14
jungleboyjYep.20:14
ildikovspotz: we had too many people in the room, the intro took ages20:14
spotzildikov: Students or 'instructors/helpers'?20:15
ildikovso my thinking is to have the trainers/coaches introduce themselves to the whole group20:15
diablo_rojoWorks for me20:15
jaypipesildikov: ++20:15
jungleboyjYeah, can't have everyone introduce themselves.20:16
spotzI usually do a slide with the main instructors, then one with the other folks in the room with their companies and they just kind of wave when they're name is read20:16
ildikovand as we ask students in advance about what's their area of interest we can split them into groups before the training20:16
ildikovwe will have round tables in the room20:16
jungleboyjThey will all get to know each other through the exercises and breaks.20:16
jungleboyjThat is a good idea.20:16
ildikovso we can give ten minutes to the groups to introduce themselves within those smaller groups20:16
ildikovmentors can check where everyone is and then move to the next thing when everyone's finished20:17
ildikovso people in the smaller groups have ideas on who they're sitting together with20:17
ildikovcan come up with a team name20:17
ildikovetc.20:17
jungleboyjildikov:  ++20:17
ildikovwhat do you think?20:17
*** baoli has quit IRC20:17
diablo_rojoSounds like a more efficient use of time to me20:17
spotzyeah20:17
jungleboyjMuch more effiecient.20:17
jungleboyjMore like other training sessions I have been in.20:18
jaypipesyup, ++ from me20:18
ildikovok, cool, then I will get the intro slides updated with that20:19
ildikov#action Ildiko to update the Intro slides with the introduction plans20:19
*** MeganR has quit IRC20:20
ildikovwe have a short exercise on joining IRC20:20
ildikovI think we will keep that as is and do it after the intros20:20
ildikovif there's no objection20:21
spotzSounds good20:21
diablo_rojoNo objections here20:21
ildikovthe point is to open up an extra communication channel for those who're shy to ask in front of the whole group, or speak English in written form better, etc20:21
ildikov#info Keep joining to IRC as a first exercise after the intros20:22
jungleboyjYeah, that is a good starting point.20:22
spotzildikov: Would it be a good idea in that case to make a channel for the training or also utilize 101?20:22
ildikovspotz: we used #openstack-10120:22
spotz+120:22
ildikovspotz: we will just keep that20:22
*** markvoelker has quit IRC20:22
ildikov#info use #openstack-101 as the IRC channel during the training20:23
*** raj_singh has quit IRC20:23
*** baoli has joined #openstack-meeting-320:23
ildikovwe had a very short intro section in Barcelona to introduce the training and OpenStack in just a few words20:23
*** raj_singh has joined #openstack-meeting-320:23
ildikovto get to a common ground20:23
jungleboyjildikov: I think we would still want that.20:24
*** matrohon has joined #openstack-meeting-320:24
*** rbrady has left #openstack-meeting-320:24
ildikovjungleboyj: +120:24
ildikovafter that we talked a little bit about Agile as we tried to find connection points between the daily work and the upstream/community work20:24
ildikovI think this one got various feedback20:24
jaypipesheh, I can imagine.20:25
jungleboyjYeah.20:25
ildikovin my view it's still worth having something like this, but we can figure out something else if you all hate it20:25
ildikovit was a good block to get people to discuss a topic within groups20:25
jungleboyjildikov:  Wonder if that could be more integrated into the small group work?20:27
jungleboyjDon't hit them with a hammer about it but just gently tap at the idea?20:27
ildikovas people will sit in groups, that would be a group discussion20:28
ildikovI mean small group discussion20:28
ildikovwe can open it up to the whole group if good ideas come out of in at the tables20:28
ildikovdon't want to waste too much time with it20:28
ildikovjaypipes: do you think it's a bad idea overall?20:29
jungleboyjildikov: I guess that would be a time for the small groups to get to know each other.  Who is agile, who is not?20:29
jungleboyjWhat the companies are thinking.20:29
*** gouthamr has quit IRC20:29
*** cleong has quit IRC20:30
jaypipesildikov: no, just that agile can bring in the tangential discussions that can take a conversation sideways very quickly ;)20:30
ildikovjaypipes: my thinking with it was to find out what parts of lean/agile we're using, what not, so people can get an idea how we operate without talking about it too much20:30
ildikovjaypipes: oh, I see :)20:31
diablo_rojoWe try to keep the discussions short so as to avoid that :)20:31
jungleboyj:-)20:31
ildikovjaypipes: last time we had a few people not that familiar with Agile, so were at the basics and had a few good chats20:31
ildikovbut I'm happy to re-think this part20:31
smcginnisI think a short section on that would be good.20:32
jaypipesildikov: or I can stay quiet during that part :P20:32
smcginnis;)20:32
jungleboyjKeep it short.  Get talking started in the groups.20:32
ildikovjaypipes: haha, you could share your views with this group at least if we keep this20:33
spotzpoor jaypipes:)20:33
ildikovjaypipes: so at least we know who stands where and why you're so quiet during that part :)20:33
jungleboyjDid I miss that it was pick on jaypipes  Day?20:33
bauzasman, had a network issue...20:34
ildikovshould we vote on whether or not to keep this part?20:35
jaypipes:)20:35
jaypipeskeep it, but keep it short I guess?20:36
jungleboyjjaypipes:  ++20:36
bauzaswe can honestly cut it20:36
bauzasat YVR, I saw my attendees looking at other things :p20:36
ildikovbauzas: it would be mostly a discussion20:37
ildikovbauzas: not a long presentation or anything20:37
ildikovjaypipes: ok, cool :)20:37
smcginnisI think in Paris we had a short overview at least.20:37
bauzasa very small one20:38
bauzasI was in Paris too20:38
bauzasbut meh20:38
smcginnisI think I actually took the training from you bauzas :)20:38
ildikov:)20:38
bauzasI mean, we can disucss on how to work upstream vs. your team, but maybe not saying "Agile"20:38
smcginnisBiggest point I think is to highlight whatever corporate waterfall method they may be using is not how things get done in OpenStack.20:38
bauzassmcginnis: orly ? :p20:39
jungleboyjsmcginnis: ++20:39
ildikovbauzas: we tried to use Agile as something many people know therefore they get a basic idea of a few things20:39
*** annegentle has joined #openstack-meeting-320:39
ildikovsmcginnis: +120:39
spotz+120:39
blancossmcginnis: ++ I think it's more important that they get an idea of how things work in the community20:40
bauzasokay, then just saying that Agile is an example :)20:40
ildikovwe asked them to think about what Agile methods are out and what makes sense to use in the community and what not and why20:40
ildikovwhat practices, not the whole methodology I mean20:41
bauzaslemme review the slides20:41
ildikovbauzas: that would be great, an update would surely be useful there20:42
ildikovso as a summary20:42
ildikov#info Keep the Agile part, use Agile as some sort of an example, let people discuss it. Should be a short section.20:42
*** baoli has quit IRC20:43
ildikovok, let's move to the next section20:43
diablo_rojo17 min left heads up20:43
ildikovdiablo_rojo: tnx20:43
ildikovwe have a section on official projects20:44
bauzas++20:44
ildikovwe might shorten it down as people does not necessarily need to know on day one how to create a new project, etc.20:44
smcginnisProbably better not to tell them how to start new projects.20:44
ildikovif someone could look up what material we have on the web we can have an exercise that people find out what projects we have in the Big Tent20:45
diablo_rojoildikov, agreed. People do regular talks on that type of thing every summit so there isnt much need to go into detail here.20:45
jungleboyjildikov:  Yeah, quick intro to the projects but not how to create one.20:45
ildikoveven what Big Tent is and what they can find out about it in 10 minutes and then we clarify the main idea and move on20:45
smcginnisildikov: +120:45
jungleboyjildikov:  +120:45
diablo_rojoWho wants that action?20:46
jungleboyjI don't fully understand big tent yet.  :-)20:46
bauzasmaybe just putting them to cookiecutter and the docs ? :p20:47
ildikovjungleboyj: then just write up the exercise in the slides and you can figure it out with your group ;)20:47
ildikovbauzas: lol :)20:47
*** rockyg has joined #openstack-meeting-320:47
jungleboyjildikov:  :-)  Sure, I can take it if you want.  I will learn.20:47
ildikovjungleboyj: cool :)20:48
bauzasI mean the project contributor guide20:48
jungleboyjHad a feeling by noting I needed to learn I would be volunteering myself.  :-)20:48
spotzhehe20:48
ildikovjungleboyj: cut out most of the content and start with the exercise20:49
*** ansmith has quit IRC20:49
jungleboyjildikov: Will do.20:49
ildikovbauzas: got it20:49
*** joanna has joined #openstack-meeting-320:49
bauzasFWIW for the context https://docs.openstack.org/contributor-guide/project-install-guide.html20:49
ildikov#action jungleboy looks into the Big Tent section and updates the exercise and content20:50
jungleboyjWill do.20:50
diablo_rojoOffical Projects section actually :)20:50
ildikovdiablo_rojo: Oooops :)20:51
jungleboyjdiablo_rojo:  I know what she meant20:51
diablo_rojoClose enough :)20:51
*** baoli has joined #openstack-meeting-320:51
ildikovbauzas: ah ok, I know this one20:51
ildikovok, we have 9 minutes left20:51
ildikovlet's try to deal with the Governance section too20:52
ildikovI have less ideas on how to keep that one interesting...20:52
ildikovanyone has anything in mind?20:52
jungleboyjDo we really want to cover that at the beginning?20:52
bauzasyup20:53
bauzasit's a very important topic IMHO20:53
diablo_rojoI think its important too. The structure of the community helps you understand how it functions.20:53
jungleboyjbauzas:  I suppose that is true.  Keep it short.20:53
spotzGo over high lights, code of conduct, etc20:53
bauzasjungleboyj: "short" can be 20 mins20:53
bauzasnot less20:54
bauzasdepending on what you wanna talk of course20:54
jungleboyjbauzas: It is important to understand the role of TC and UC.  How people are elected, etc.20:54
bauzasbut honestly, I'd prefer to see more time for that than Agile for example :p20:54
diablo_rojoLooking at the slides there isn't any info about the AUC's. Also..not sure that APC is a real thing- someone correct me if I am wrong.20:54
diablo_rojobauzas, +120:55
jungleboyjbauzas: Ok.  You volunteering?20:55
jungleboyj:-)20:55
bauzasAPC is a thing for PTL elections20:55
ildikovcould we somehow get the teams structured in a way to help understanding the community structure?20:55
ildikovI mean get a PTL for each group, etc.20:56
diablo_rojobauzas, huh, okay. Doesnt sound any different than ATC20:56
smcginnisildikov: That's not a bad idea. Do a little PTL election for each group?20:56
bauzasjungleboyj: we already have slides describing that20:56
jungleboyjildikov:  Would it be silly to select a PTL, a core and use that as an example to work through the process?20:56
spotzildikov: I'm sure there will be PTLs at summit, but they may not be coming early enough to be at the training20:56
jungleboyjildikov: With people at the table ?20:56
bauzaswe did that for the lego playroles20:56
blancosjungleboyj: I think that's a good idea. It makes the topic more interesting, I think20:56
diablo_rojoildikov, that would be fun20:57
smcginnisildikov: Are you going to bring a few cases of legos? :)20:57
bauzasone team was the upstream one, electing a PTL and cores20:57
ildikovI meant the election20:57
bauzasnot saying we should resurrect the lego playgame20:57
bauzasjust explaining that presenting it in a roleplay is a good idea20:57
ildikovwe can bring parts back of the lego game20:57
jungleboyjSounds like something to consider though?20:58
ildikovbut in a less concentrated way20:58
smcginnisbauzas: It was entertaining, but probably not worth the hassle.20:58
bauzassmcginnis: agreed20:58
ildikovso take some parts and build it up during the 1.5 days20:58
bauzastaking 2 important hours off your agenda20:58
ildikovbauzas: +120:58
ildikovok, we need to wrap up20:58
ildikovlet's think about the governance part a bit more and start with that next week20:58
jungleboyjI think I did the Release Cycle part in BCN.  I can look through that.20:59
ildikovjungleboyj: +120:59
ildikovthanks20:59
jungleboyjildikov: No problem.20:59
ildikovlet's try to finish the common parts next week and get to the tools and deep dives the week after the latest20:59
diablo_rojoI made some updates to the events section removing mentions of the old format and focusing on the new.21:00
diablo_rojoildikov, +121:00
ildikovplease do reviews and drop ideas to either the etherpad or Gerrit21:00
ildikovdiablo_rojo: +1, thanks21:00
ildikovthanks everyone for today!21:00
diablo_rojoTimes up21:00
ildikovgood progress21:00
*** VW_ has joined #openstack-meeting-321:00
jungleboyjGood meeting.  Thanks!21:00
ildikovsee you next week the latest! :)21:00
diablo_rojoildikov, Agreed :)21:00
ildikov#endmeeting21:00
smcginnisildikov: Thanks21:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:00
openstackMeeting ended Mon Mar 27 21:00:56 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-03-27-20.00.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack_upstream_institute/2017/openstack_upstream_institute.2017-03-27-20.00.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack_upstream_institute/2017/openstack_upstream_institute.2017-03-27-20.00.log.html21:01
*** MeganR has joined #openstack-meeting-321:01
*** blancos has quit IRC21:01
mlavalleildikov: deep dives meaning projects deep dives?21:01
*** gouthamr has joined #openstack-meeting-321:01
ildikovmlavalle: let's switch to #openstack-upstream-institute21:01
*** VW_ has quit IRC21:02
*** VW_ has joined #openstack-meeting-321:02
*** baoli has quit IRC21:02
*** Sukhdev has joined #openstack-meeting-321:03
*** dimtruck is now known as zz_dimtruck21:03
*** VW has quit IRC21:04
*** shuyingya has joined #openstack-meeting-321:10
*** ccamacho has quit IRC21:12
*** MeganR_ has joined #openstack-meeting-321:17
*** MeganR has quit IRC21:20
*** matrohon has quit IRC21:23
*** lucasxu has quit IRC21:34
*** alexismonville has joined #openstack-meeting-321:40
*** lucasxu has joined #openstack-meeting-321:41
*** haleyb has quit IRC21:47
*** rocky_g has joined #openstack-meeting-321:50
*** rockyg has quit IRC21:50
*** tonytan4ever has quit IRC21:51
*** Swami has quit IRC21:54
*** zz_dimtruck is now known as dimtruck21:56
*** MeganR_ has quit IRC21:57
*** amotoki has joined #openstack-meeting-322:02
*** david-lyle has quit IRC22:04
*** david-lyle has joined #openstack-meeting-322:05
*** amotoki has quit IRC22:12
*** bobh has joined #openstack-meeting-322:15
*** mlavalle has quit IRC22:17
*** sdague has quit IRC22:18
*** VW has joined #openstack-meeting-322:22
*** VW_ has quit IRC22:22
*** lyan has quit IRC22:23
*** emagana has quit IRC22:23
*** Adri2000 has quit IRC22:29
*** galstrom is now known as galstrom_zzz22:31
*** lamt has quit IRC22:36
*** bobh has quit IRC22:47
*** lucasxu has quit IRC22:51
*** markvoelker has joined #openstack-meeting-322:52
*** Patifa has quit IRC22:52
*** VW has quit IRC22:54
*** VW has joined #openstack-meeting-322:55
*** Adri2000 has joined #openstack-meeting-322:57
*** Adri2000 has quit IRC22:57
*** Adri2000 has joined #openstack-meeting-322:57
*** VW has quit IRC22:58
*** rocky_g has quit IRC23:01
*** marst has quit IRC23:04
*** bobh has joined #openstack-meeting-323:05
*** seanatcisco has quit IRC23:05
*** seanatcisco has joined #openstack-meeting-323:06
*** Sukhdev has quit IRC23:06
*** alexismonville has left #openstack-meeting-323:11
*** annegentle has quit IRC23:16
*** marst has joined #openstack-meeting-323:18
*** jaypipes has quit IRC23:24
*** benj_ has joined #openstack-meeting-323:25
*** diablo_rojo has quit IRC23:26
*** liangy has joined #openstack-meeting-323:34
*** crushil has joined #openstack-meeting-323:36
*** annegentle has joined #openstack-meeting-323:42
*** joanna has quit IRC23:48
*** annegentle has quit IRC23:49
*** dimtruck is now known as zz_dimtruck23:59
*** liangy has quit IRC23:59
*** shuyingya has quit IRC23:59

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