Monday, 2016-10-17

*** shwetaap has quit IRC00:04
*** mickeys has quit IRC00:04
*** salv-orlando has joined #openstack-meeting-300:09
*** kzaitsev_mb has quit IRC00:09
*** mtanino has joined #openstack-meeting-300:10
*** salv-orlando has quit IRC00:14
*** stanzgy has joined #openstack-meeting-300:18
*** markvoelker_ has quit IRC00:18
*** claudiub has quit IRC00:24
*** emagana has joined #openstack-meeting-300:34
*** emagana has quit IRC00:38
*** hoangcx has joined #openstack-meeting-300:39
*** tovin07 has joined #openstack-meeting-300:52
*** mtanino has quit IRC00:53
*** zz_dimtruck is now known as dimtruck01:08
*** salv-orlando has joined #openstack-meeting-301:10
*** zhurong has joined #openstack-meeting-301:14
*** salv-orlando has quit IRC01:15
*** haleyb_ has joined #openstack-meeting-301:15
*** haleyb_ has quit IRC01:20
*** tuanluong has joined #openstack-meeting-301:51
*** dimtruck is now known as zz_dimtruck01:52
*** salv-orlando has joined #openstack-meeting-302:11
*** salv-orlando has quit IRC02:16
*** emagana has joined #openstack-meeting-302:22
*** baoli has quit IRC02:35
*** emagana has quit IRC02:38
*** vishwanathj has joined #openstack-meeting-302:53
*** vishwanathj has quit IRC02:53
*** haleyb_ has joined #openstack-meeting-303:17
*** shwetaap has joined #openstack-meeting-303:20
*** haleyb_ has quit IRC03:21
*** baoli has joined #openstack-meeting-303:28
*** baoli has quit IRC03:41
*** mickeys has joined #openstack-meeting-303:43
*** mickeys has quit IRC03:47
*** psachin has joined #openstack-meeting-303:49
*** flwang1 has quit IRC04:07
*** cshastri has joined #openstack-meeting-304:12
*** salv-orlando has joined #openstack-meeting-304:13
*** salv-orlando has quit IRC04:17
*** cshastri_ has joined #openstack-meeting-304:20
*** psachin has quit IRC04:20
*** haleyb_ has joined #openstack-meeting-304:22
*** yamamoto has quit IRC04:22
*** cshastri has quit IRC04:23
*** cshastri_ has quit IRC04:25
*** cshastri_ has joined #openstack-meeting-304:25
*** haleyb_ has quit IRC04:27
*** emagana has joined #openstack-meeting-304:31
*** kenji-i_ has joined #openstack-meeting-304:34
*** kenji-i has quit IRC04:35
*** psachin_ has joined #openstack-meeting-304:38
*** numans has joined #openstack-meeting-304:42
*** kenji-i_ has quit IRC04:52
*** shwetaap has quit IRC04:59
*** salv-orlando has joined #openstack-meeting-305:02
*** cshastri_ is now known as cshastri05:08
*** lpetrut has joined #openstack-meeting-305:13
*** yamamoto has joined #openstack-meeting-305:21
*** shwetaap has joined #openstack-meeting-305:23
*** mickeys has joined #openstack-meeting-305:28
*** cartik has joined #openstack-meeting-305:29
*** mickeys has quit IRC05:33
*** emagana has quit IRC05:38
*** kenji-i has joined #openstack-meeting-305:38
*** mfedosin has joined #openstack-meeting-305:40
*** lpetrut has quit IRC05:43
*** salv-orlando has quit IRC05:51
*** prateek has joined #openstack-meeting-305:54
*** psachin_ has quit IRC05:57
*** pgadiya has joined #openstack-meeting-305:58
*** paul-carlton2 has joined #openstack-meeting-306:01
*** acabot has quit IRC06:03
*** matjazp has joined #openstack-meeting-306:06
*** matjazp has quit IRC06:12
*** Poornima has joined #openstack-meeting-306:13
*** shwetaap has quit IRC06:13
*** Poornima has quit IRC06:13
*** matjazp has joined #openstack-meeting-306:15
*** coolsvap has joined #openstack-meeting-306:20
*** haleyb_ has joined #openstack-meeting-306:24
*** andreas_s has joined #openstack-meeting-306:26
*** haleyb_ has quit IRC06:29
*** jtomasek_ has joined #openstack-meeting-306:31
*** jtomasek_ has quit IRC06:47
*** salv-orlando has joined #openstack-meeting-306:52
*** salv-orlando has quit IRC06:56
*** matjazp has quit IRC07:03
*** matjazp has joined #openstack-meeting-307:07
*** matjazp has quit IRC07:13
*** matjazp has joined #openstack-meeting-307:15
*** mickeys has joined #openstack-meeting-307:15
*** salv-orlando has joined #openstack-meeting-307:15
*** nkrinner_afk is now known as nkrinner07:17
*** matrohon has joined #openstack-meeting-307:24
*** mickeys has quit IRC07:24
*** haleyb_ has joined #openstack-meeting-307:26
*** zhurong has quit IRC07:26
*** haleyb_ has quit IRC07:30
*** amotoki has joined #openstack-meeting-307:46
*** Poornima has joined #openstack-meeting-307:47
*** Poornima has quit IRC07:52
*** bogdando has joined #openstack-meeting-307:52
*** itxaka has joined #openstack-meeting-307:53
*** paul-carlton2 has quit IRC07:57
*** lpetrut has joined #openstack-meeting-308:11
*** mickeys has joined #openstack-meeting-308:25
*** mickeys has quit IRC08:30
*** ralonsoh has joined #openstack-meeting-308:32
*** acabot has joined #openstack-meeting-308:41
*** ccamacho has joined #openstack-meeting-308:51
*** claudiub has joined #openstack-meeting-308:55
*** neiljerram has joined #openstack-meeting-308:56
*** jschwarz is now known as jschwarz|ooo08:59
*** flwang1 has joined #openstack-meeting-308:59
*** matjazp has quit IRC09:05
*** pcaruana has joined #openstack-meeting-309:08
*** kzaitsev_mb has joined #openstack-meeting-309:25
*** salv-orlando has quit IRC09:26
*** tovin07 has quit IRC09:51
*** eliqiao has quit IRC10:02
*** hoangcx has quit IRC10:27
*** salv-orlando has joined #openstack-meeting-310:27
*** salv-orlando has quit IRC10:31
*** tuanluong has quit IRC10:53
*** salv-orlando has joined #openstack-meeting-310:57
*** salv-orlando has quit IRC11:02
*** derekjhyang has quit IRC11:10
*** rtheis has joined #openstack-meeting-311:19
*** salv-orlando has joined #openstack-meeting-311:21
*** matjazp has joined #openstack-meeting-311:23
*** salv-orl_ has joined #openstack-meeting-311:25
*** alexismonville has joined #openstack-meeting-311:26
*** salv-orlando has quit IRC11:28
*** donghao has joined #openstack-meeting-311:29
*** salv-orl_ has quit IRC11:29
*** stanzgy has quit IRC11:36
*** alexismonville has quit IRC11:37
*** salv-orlando has joined #openstack-meeting-311:39
*** salv-orlando has quit IRC11:44
*** paul-carlton2 has joined #openstack-meeting-311:45
*** jdwald has joined #openstack-meeting-312:01
*** alexismonville has joined #openstack-meeting-312:03
*** jdwald has quit IRC12:07
*** jdwald has joined #openstack-meeting-312:08
*** pgadiya has quit IRC12:10
*** tellesnobrega has quit IRC12:14
*** sdague has joined #openstack-meeting-312:14
*** stanzgy has joined #openstack-meeting-312:17
*** cshastri has quit IRC12:17
*** tellesnobrega has joined #openstack-meeting-312:17
*** coolsvap has quit IRC12:18
*** Poornima has joined #openstack-meeting-312:19
*** cartik has quit IRC12:20
*** Guest23990 is now known as zigo12:21
*** VW has joined #openstack-meeting-312:31
*** mickeys has joined #openstack-meeting-312:33
*** zhurong has joined #openstack-meeting-312:34
*** mickeys has quit IRC12:39
*** VW has quit IRC12:39
*** VW has joined #openstack-meeting-312:40
*** shwetaap has joined #openstack-meeting-312:44
*** baoli has joined #openstack-meeting-312:46
*** prateek has quit IRC12:46
*** VW has quit IRC12:46
*** bauwser is now known as bauzas12:48
*** psachin` has joined #openstack-meeting-312:51
*** zhurong has quit IRC12:55
*** zhurong has joined #openstack-meeting-312:55
*** egallen has joined #openstack-meeting-312:57
*** yamamoto has quit IRC12:58
*** tonytan4ever has joined #openstack-meeting-313:01
*** kzaitsev_mb has quit IRC13:08
*** kzaitsev_mb has joined #openstack-meeting-313:08
*** SotK_ is now known as SotK13:11
*** lblanchard has joined #openstack-meeting-313:13
*** pcaruana has quit IRC13:18
*** shwetaap has quit IRC13:19
*** ociuhandu has joined #openstack-meeting-313:25
*** Poornima has quit IRC13:26
*** jdwald has quit IRC13:26
*** VW has joined #openstack-meeting-313:27
*** Poornima has joined #openstack-meeting-313:27
*** andystack has joined #openstack-meeting-313:28
*** Poornima has quit IRC13:40
*** egallen has quit IRC13:41
*** egallen has joined #openstack-meeting-313:41
*** egallen has quit IRC13:42
*** egallen has joined #openstack-meeting-313:42
*** yamamoto has joined #openstack-meeting-313:42
*** egallen has quit IRC13:42
*** egallen has joined #openstack-meeting-313:43
*** egallen has quit IRC13:43
*** julim has quit IRC13:43
*** egallen has joined #openstack-meeting-313:44
*** shwetaap has joined #openstack-meeting-313:44
*** jdwald has joined #openstack-meeting-313:44
*** egallen has quit IRC13:44
*** egallen has joined #openstack-meeting-313:44
*** egallen has quit IRC13:45
*** matjazp has quit IRC13:52
*** vhoward has joined #openstack-meeting-313:52
*** shwetaap has quit IRC13:59
*** shwetaap has joined #openstack-meeting-314:00
*** egallen has joined #openstack-meeting-314:00
*** hogepodge has quit IRC14:04
*** krtaylor has quit IRC14:04
*** iyamahat has joined #openstack-meeting-314:06
*** chandanc_ has joined #openstack-meeting-314:07
*** sc68cal_ is now known as sc68cal14:10
*** mtanino has joined #openstack-meeting-314:12
*** chandanc_ is now known as chandanc14:14
*** VW has quit IRC14:14
*** paul-carlton2 has quit IRC14:17
*** paul-carlton2 has joined #openstack-meeting-314:18
*** marst has joined #openstack-meeting-314:20
*** abalutoiu has joined #openstack-meeting-314:21
*** donghao has quit IRC14:23
*** coolsvap has joined #openstack-meeting-314:25
*** julim has joined #openstack-meeting-314:28
*** hamzy has joined #openstack-meeting-314:35
*** tenobreg has joined #openstack-meeting-314:35
*** tellesnobrega has quit IRC14:39
*** tenobreg is now known as tellesnobrega14:51
*** MeganR has joined #openstack-meeting-314:56
*** gouthamr has joined #openstack-meeting-314:56
*** yamamoto has quit IRC14:59
*** yamamoto has joined #openstack-meeting-315:00
*** pcaruana has joined #openstack-meeting-315:03
*** luzC has quit IRC15:03
*** lcastell has quit IRC15:03
*** lcastell has joined #openstack-meeting-315:04
*** luzC has joined #openstack-meeting-315:13
*** matjazp has joined #openstack-meeting-315:14
*** alexismonville has quit IRC15:17
*** matjazp has quit IRC15:19
*** zhurong has quit IRC15:22
*** alexismonville has joined #openstack-meeting-315:23
*** egallen has quit IRC15:25
*** egallen has joined #openstack-meeting-315:29
*** alexismonville has quit IRC15:29
*** egallen has quit IRC15:30
*** alexismonville has joined #openstack-meeting-315:30
*** macsz_ has quit IRC15:31
*** macsz_ has joined #openstack-meeting-315:32
*** macsz_ is now known as macsz15:32
*** macsz has quit IRC15:33
*** macsz has joined #openstack-meeting-315:33
*** egallen has joined #openstack-meeting-315:36
*** krtaylor has joined #openstack-meeting-315:37
*** egallen has quit IRC15:41
*** david-lyle_ has joined #openstack-meeting-315:52
*** david-lyle has quit IRC15:53
*** hogepodge has joined #openstack-meeting-315:53
*** egallen has joined #openstack-meeting-315:57
*** egallen has quit IRC15:59
*** uxdanielle has joined #openstack-meeting-316:01
*** egallen has joined #openstack-meeting-316:06
*** egallen has quit IRC16:06
*** andreas_s has quit IRC16:06
*** armax has joined #openstack-meeting-316:07
*** iyamahat has quit IRC16:19
*** claudiub has quit IRC16:21
*** matrohon has quit IRC16:22
*** egallen has joined #openstack-meeting-316:22
*** lpetrut has quit IRC16:23
*** david-lyle_ is now known as david-lyle16:24
*** numans has quit IRC16:26
*** jtomasek has quit IRC16:28
*** njohnston_ is now known as njohnston16:33
*** bauzas has quit IRC16:39
*** shwetaap has quit IRC16:40
*** rhagarty has joined #openstack-meeting-316:41
*** itxaka has quit IRC16:44
*** lpetrut has joined #openstack-meeting-316:45
*** bauzas has joined #openstack-meeting-316:45
*** markvoelker has joined #openstack-meeting-316:46
*** Rockyg has joined #openstack-meeting-316:46
*** nicodemos has joined #openstack-meeting-316:47
*** lucasagomes has joined #openstack-meeting-316:47
*** rama_y has joined #openstack-meeting-316:47
*** markvoelker_ has joined #openstack-meeting-316:49
*** kzaitsev_mb has quit IRC16:51
*** kzaitsev_mb has joined #openstack-meeting-316:51
*** markvoelker has quit IRC16:51
*** mariojv has joined #openstack-meeting-316:52
*** rama_y has quit IRC16:53
*** rloo has joined #openstack-meeting-316:56
*** mat128 has joined #openstack-meeting-316:57
*** bfournie has joined #openstack-meeting-316:57
*** hshiina has joined #openstack-meeting-316:58
*** shwetaap has joined #openstack-meeting-316:58
*** yuriyz|2 has joined #openstack-meeting-316:58
*** dtantsur has joined #openstack-meeting-316:58
*** egallen_ has joined #openstack-meeting-316:59
*** egallen has quit IRC16:59
*** egallen_ is now known as egallen16:59
*** rpioso has joined #openstack-meeting-316:59
jroll#startmeeting ironic17:00
openstackMeeting started Mon Oct 17 17:00:00 2016 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
devanandao/17:00
*** openstack changes topic to " (Meeting topic: ironic)"17:00
openstackThe meeting name has been set to 'ironic'17:00
mat128o/17:00
vdroko/17:00
JayFo/17:00
rpiosoo/17:00
mjtureko/17:00
yuriyz|2o/17:00
bfournieo/17:00
krtayloro/17:00
lucasagomeso/17:00
mariojvo/17:00
jrollas always, agenda is here:17:00
hshiinao/17:00
jroll#link https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting17:00
jroll#topic announcements / reminders17:00
*** openstack changes topic to "announcements / reminders (Meeting topic: ironic)"17:00
jrollso the summit is next week17:00
rlooo/17:01
jrollaccordingly, let's not have this meeting next week17:01
jlvillalo/17:01
jrolldon't see any reason not to have it the following week, though17:01
TheJuliao/17:01
jrollalso, I mostly won't be here for the rest of this week17:02
lucasagomesjroll, it's halloween no ?17:02
*** milan has joined #openstack-meeting-317:02
milano/17:02
dtantsuro/17:02
rloolucasagomes: we can have a ghostly meeting?17:02
jrollI'll be here a bit today and tomorrow and then gone17:02
jrollhit me on hangouts if anything urgent :)17:02
lucasagomesrloo, ++ let's do it heh17:02
sambettso/17:02
jrolllucasagomes: tis, but that's not a 'day off' holiday anywhere that I know of17:02
jrollI'll wear a costume17:02
mat128videoconference? :)17:03
lucasagomesI think it is in ireland, but for another reason17:03
lucasagomesbank holiday17:03
lucasagomesanyway...17:03
jrollah17:03
jrollanyone have other announcements or reminders?17:03
rloojroll: reminder for folks attending summit read specs/prepare beforehand17:03
jroll++17:03
jrollall of my ++17:03
*** jtomasek has joined #openstack-meeting-317:04
rloojroll: maybe we should send an email out about that.17:04
*** nkrinner is now known as nkrinner_afk17:04
*** mickeys has joined #openstack-meeting-317:04
* rloo volunteers after i see what the state of the specs, etc are...17:04
jrollrloo: thanks :)17:04
milanrloo ++ mail w/ specs to read would be nice :)17:05
jrollI'd be surprised if people that don't know they should read background info will actually read the ML, but we shall see17:05
*** ralonsoh has quit IRC17:05
JayFrloo: ++ and also good for folks not attending to get input in the spec before others talk about it in the summit17:05
*** uxdanielle has quit IRC17:05
milanJayF, good point17:06
*** jtomasek has quit IRC17:06
jrollanything else?17:06
*** jtomasek has joined #openstack-meeting-317:06
rloojroll: oh, any meetup at summit?17:06
rloojroll: i mean, evening gathering17:06
jrollrloo: lucasagomes was going to look into a thing but as of yet nothing planned17:06
lucasagomesrloo, I want to book a restaurant17:07
lucasagomeswe need to decide the day17:07
rloolucasagomes: thx for volunteering!17:07
vdrokand are we going to have an arrival list as the last time?17:07
lucasagomeslet's do it at the end of the meeting ? Or should I send an email to the ML ?17:07
lucasagomesrloo, I will try, my spanish is not that great either17:07
jlvillalvdrok: https://etherpad.openstack.org/p/ironic-ocata-summit-people  ???17:07
jrollTIL17:07
vdrokoh, thanks jlvillal :)17:07
*** shwetaap has quit IRC17:07
krtaylormeetup++17:07
mat128jroll: might be worth a #link17:07
jroll#link https://etherpad.openstack.org/p/ironic-ocata-summit-people17:08
* krtaylor missed planning that for ocata17:08
rloocould we use that etherpad to indicate availability for dinner?17:08
*** xavierr has joined #openstack-meeting-317:08
dtantsurrloo, I'd prefer doodle, it's easier to analyze17:08
rloodtantsur: ok, that works too17:09
lucasagomesyeah I think doodle is easy to visualize17:09
* lucasagomes creates a doodle17:09
jrollalright, shall we move on?17:09
rlooalthough wasn't it doodle that the/some asians couldn't access?17:09
rloo+ movin' on17:09
jrollcan always add in the email "if you can't get to doodle, reply here"17:09
jroll#topic subteam status reports17:09
*** openstack changes topic to "subteam status reports (Meeting topic: ironic)"17:09
jrollas always, those are here17:10
jroll#link https://etherpad.openstack.org/p/IronicWhiteBoard17:10
jrollline 80 this time17:10
jrollwoo, serial console is finally done \o/17:10
jrollthanks to folks that were involved there17:10
rloojroll: ++. the reviews by the nova folks were ... interesting...17:10
jrollroot device hints also done, except docs \o/17:10
jlvillal+1!17:10
lucasagomeso/17:10
jrolland our first real notifications were approved today, woo17:12
mariojv\o/17:12
jrollyay we did stuff between release and summit17:12
rloolots of woo's today :)17:12
milan:)17:12
rloodtantsur: wrt the work around for neutron pool issue -- whoever is going to remove the workaround, I suggest do it early this week, or wait til after summit.17:12
jrollso if people need things to work on this week beyond prepping for summit, looks like BFV specs, driver comp specs, portgroups patches17:13
dtantsurwe can wait, I'll just leave this bug as critical as a reminder :)17:13
rloodtantsur: it isn't critical any more though but i guess it is fine to leave it as that. you're the only one that looks :D17:13
dtantsursigh...17:14
dtantsur:)17:14
jrollheh17:14
*** aarefiev22 has joined #openstack-meeting-317:15
jrollanything else on this topic?17:15
jrollk17:15
jroll#topic Where should Ironic keep it's canonical admin guide until the docs team supports writing the admin guide in-tree?17:15
*** openstack changes topic to "Where should Ironic keep it's canonical admin guide until the docs team supports writing the admin guide in-tree? (Meeting topic: ironic)"17:15
jroll#link http://lists.openstack.org/pipermail/openstack-dev/2016-October/105493.html17:15
jrollsomeone was bad and didn't put their name here, but I suspect this is a JayF topic?17:15
JayFWhoops!17:16
JayFYeah,17:16
JayFthe basic outline is this: The docs team does not want to do admin-guides in-tree this cycle (even if I was willing to do the work)17:16
JayFso we have to figure out what we want to do for admin-guide stuff moving forward:17:16
JayF1) Keep it in the docs repo, and contribute to it17:16
JayF2) Replace the minimal information in the existing admin-guide (which appears to have been copied from our dev docs) with a link back to our dev docs and put the admin guide in our dev docs17:17
dtantsurfor me, it sounds like something to try to discuss with docs folks on the summit...17:17
dtantsurotherwise, I'd prefer #217:17
mat128JayF: is there a 3?17:17
JayFI don't anticipate we'll do a lot of admin guide work this cycle, but it's getting hard to draw the line between "admin" stuff and "install" stuff17:17
jroll3) continue ignoring the concept of an admin-guide until we can do it in-tree :)17:17
JayFmat128: I don't really think so, I mean, there's an option to do nothing implied17:17
rloodtantsur: what sort of discussion at summit, are you thinking of? JayF already had a discussion with them in the ML17:18
*** claudiub has joined #openstack-meeting-317:18
JayFjroll: I don't think that's really a reasonable option; information on how to administrate ironic has to go /somewhere/ and I'm trying to avoid us overloading our install-guide in the short term.17:18
mat128JayF: move current admin-guide to our install-guide as the line is so thin anyway?17:18
dtantsurrloo, well, get to know their motivation better, maybe future plans. maybe show them a PoC.17:18
rlooso the thing with ignoring (status quo) is that there IS ironic stuff in the admin-guide, but it is a subset of what we have in our dev docs17:18
dtantsurrloo, iirc it's pretty miserable, but it's linked from the openstack main docs page.. so that's what people find first17:19
jrolldtantsur: they plan to do it in pike or later, fwiw17:19
rloodtantsur: JayF won't be at the summit. and based on the replies in the ML, i doubt that anything will happen before pike.17:19
JayFMy opinion is that we should do #2; put an admin-guide in-tree, with a specific mind to organizing it so it's easy to migrate to an in-tree admin-guide later17:19
dtantsurjroll, that's strange that they don't accept help for that..17:19
JayFdtantsur: that's exactly what I thought too17:19
jrolldtantsur: ¯\_(ツ)_/¯17:19
mariojv2) sounds ok. that way we can get something useful out quicker, and maybe move it to the docs repo later once we have something high quality17:19
*** pas-ha has joined #openstack-meeting-317:20
rlooI vote for 2)17:20
JayFdtantsur: I basicaly offered to do admin-guide intree for them, and they turned me down17:20
dtantsurhmmmm.. ok, #2 then.17:20
jrollJayF: yeah, indeed, I'd love for the later migration to be mv ironic/doc/source/admin-guide ironic/admin-guide17:20
dtantsurif they're so busy, they probably won't be pleased with a spam of our patches as well17:20
jrollso yeah, I'm good with #217:20
JayFI mean, they said they're willing to take our patches for the out-of-tree admin guide17:20
JayFI'm just not keen on that as we tend to like having our stuff in-tree17:21
*** tqtran has joined #openstack-meeting-317:21
JayFespecially since the relationship between dev docs / install guide / admin guide is ... not well established yet for ironic17:21
dtantsurwell, yeah, we can provide much more valuable review IMO17:21
rloodtantsur: so folks should read the entire thread. Basically, Lana said: "However, I want to collect data based on that experience before we begin, rather than barrelling on down that road. Additionally, I don't feel as though the Install Guide is absolutely complete until we've got the index page done. As I said earlier, there is also the consideration of the short release cycle for Ocata."17:21
JayFIt sounds like consensus is go with #2?17:21
mat128jroll, JayF: I like the idea of having the admin-guide in-tree but published inside of the developer docs and/or install-guide17:21
jrollJayF: sounds like it to me17:22
rlooif we eventually want to have the admin guide intree, i don't think it makes sense to move it outoftree and then back in again17:22
dtantsurrloo++17:22
jroll+117:22
JayFSo I'll take that action item, and will work to have patches to eliminate the partial information from the out-of-tree guide and link it to the in-tree dev docs by the time you all are back from summit17:22
rloothx JayF!17:23
mat128JayF: keep me in the loop, not going to the summit either :(17:23
jrollJayF: awesome, thanks17:23
*** psachin` has quit IRC17:24
jrollany other comments here?17:24
jroll#topic MoltenIron as a sub project17:24
*** openstack changes topic to "MoltenIron as a sub project (Meeting topic: ironic)"17:24
jroll#link https://review.openstack.org/#/c/387418/17:24
jrollmjturek: krtaylor: hamzy: this is you17:25
mjturekSo, we committed a blueprint today for MoltenIron with the intention of getting it under Ironic's governance.17:25
krtaylorsure, molten iron is a tool we wrote to manage pools of baremetal test targets, we've talked about it before and at last summit17:25
mjturekit's currently living in the third-party-ci-tools repo17:25
krtaylorwe were wanting to know what ironic wanted us to do with it, we'd love to get input from others, I know several vendors are interested17:26
devanandado any of the CI teams outside of IBM use this?17:26
krtayloryes, Dell I believe is one17:26
jrolljust to be clear - the question at hand is "should molteniron become part of the ironic umbrella (under ironic governance)?"17:27
krtaylorthere are a few others that were interested if it had featureXYZ17:27
*** piet_ has joined #openstack-meeting-317:27
rloohave you discussed with CI, about the 'shortcomings' of nodepool? I mean, what about changing nodepool to do what you want?17:27
*** vhoward has quit IRC17:27
devanandakrtaylor: that's encouraging.17:27
*** vhoward has joined #openstack-meeting-317:27
mat128krtaylor, mjturek: we have (had) this requirement but at a much larger scale - nodes, racks, servers, pdus, etc.17:27
devanandarloo: last time I spoke with the CI team, they said that nodepool v3 would include functionality to do this sort of thing, but that was ~6mo ago17:28
*** liangy has joined #openstack-meeting-317:28
rloodevananda: oh, maybe they have it done now :D (j/k)17:28
JayFCan I ask the flip-side question: Why wouldn't we want molteniron under the Ironic umbrella?17:28
krtayloryes, but there were reasons it wouldnt work, for us anyway17:28
JayFIt's used by ironic 3rd party UI, if it gets superceded later it gets superceded17:28
* krtaylor looks at mjturek17:28
devanandaJayF: my only reason to object would be "only one vendor is using it". but that's not the case, apparently :)17:29
JayFI'm not sure I understand any scenario we'd say "no" to the question at hand17:29
rlooi think it makes sense to talk to the CI team, if they are going to do something similar soon, why not just help them get that going, instead of duplicating.17:29
* dtantsur is still confused why we say yes17:29
*** shwetaap has joined #openstack-meeting-317:29
dtantsurJayF, it depends on what we imply under "taking under our governance", I guess17:29
jrollright, so the tradeoff is "core team is responsible for it", but it means molteniron is able to publish to docs.o.o17:29
mat128krtaylor, mjturek: is this only for CI or it's a full fledged cmdb?17:29
*** Swami has joined #openstack-meeting-317:29
devanandarloo: ++17:29
dtantsurJayF, e.g. what prevents us taking ironic-staging-drivers under our governance?17:29
jroll(it could have a separate/additional core team, of course, but the ironic team would be responsible for it)17:30
mjturekmatt128 currently just CI17:30
sambettsmat128: it is literally a tool for reserving a node to run tests against17:30
sambettsmat128: then giving it back for the next test run17:30
JayFdtantsur: I really wouldn't be opposed to that either, honestly17:30
krtayloryes, just a tool for managing reservations for baremetal targets17:30
rlooI feel like this falls under CI, not ironic17:31
devanandataking it under our governance means the PTL is taking responsibility for it, we need to give time in meetings to the project, and granting election voting rights to contributors to that project17:31
dtantsurJayF, me neither. we don't include it, because we don't want to assume the same level of support as for our production drivers.17:31
krtaylorrloo, it is very ironic specific17:31
jlvillalmaybe related. Today there was a thing with nodepool using ironic discussion: http://eavesdrop.openstack.org/meetings/third_party/2016/third_party.2016-10-17-15.00.log.html17:31
jrollbtw, this is the molteniron repo:17:31
jroll#link https://github.com/openstack/third-party-ci-tools/tree/master/nodepool/molteniron17:31
*** alexismonville has quit IRC17:32
*** bpokorny has joined #openstack-meeting-317:32
jrollroughly 1500-2000 LOC, seems pretty simple17:32
krtaylorthe third-party-ci-tools repo doesnt require tests,so we are looking to have automated tests,etc so a new project or a subproject is the question17:32
rlookrtaylor: you're going to be at the summit -- would you be willing to talk to CI folks about molteniron, see where/if nodepool works or if there is common ground?17:32
dtantsurI guess I'm just -0 to all inclusions, until we figure out what "being under our umbrella" fully requires and implies17:32
jrollI seem to remember quite a few talks between these folks an infra folks, but maybe I'm thinking of something else17:33
rloodtantsur: to future inclusions? since we already have a few things under the ironic umbrella :)17:33
krtayloryes, there have been several discussions, nodepool and also zuul were proposed17:33
JayFdtantsur: what devananda said above matches what I was thinking it meant; and tbh I don't like splitting a hair to say if you work on something like molteniron you get less rights than someone who works on inspector, bifrost, ipa, ironic, etc17:33
dtantsurrloo, well, we can always reconsider them too.. I don't remember anything feeling foreign, but maybe it's only me17:33
JayFdtantsur: I guess I'm just more +0 by default :D17:33
rloodtantsur: i agree with you wrt knowing more specifically, what it means for things under the ironic umbrella17:34
dtantsuryeah, I'm only asking because we have some problems with ironic-staging-drivers, which could be worked around by it being under an official project17:34
jrolldtantsur: what sort of problems?17:34
dtantsurand this is not something out of blue, that's our drivers, developed by ironic contributors and reviewed by ironic core reviewers (a subset of them)17:34
dtantsurjroll, no docs, no release support, no i18n (to name a few)17:35
*** alexismonville has joined #openstack-meeting-317:35
jrollnod17:35
lucasagomesa better guide on what should be under the Ironic umbrella and what not would be very welcome17:35
dtantsurI've gone through all this with ironic-discoverd  /me is nostalgic17:35
*** VW has joined #openstack-meeting-317:35
lucasagomesbut I also think that we probably should check nodepool first, if they are willing to extend it to support baremetal nodes we probably should help 'em out17:35
* mat128 doesnt understand why projects not under governance can't have docs, but here is not the place for this17:35
rlooseems like openstack should have a general guide, i don't know that ironic is special from other umbrellas17:35
dtantsurso, I'm not against "why not" approach, I just want it stated officially :)17:35
krtaylorre: nodepool, we could bring that up again, but generally there has not been much traction for third-party (non-infra) CI test changes17:36
lucasagomesmat128, it can, but not official under openstack (we use http://readthedocs.org)17:36
JayFmat128: being in the "big tent" gives you access to shared resources, such as docs17:36
jrollnodepool is also designed to only speak to nova, AIUI (intentionally such)17:36
TheJuliaMy understanding is that will be changing over the next six months or so17:36
devanandajroll: IIUC, that's changing in v3...17:36
mjturekright, the changes don't necessarily fit there. It's something we could propose, but we have a working solution sitting here17:36
jrollok, I had not heard that yet17:37
sambettsso the problem with nodepool is that it is designed to solve a different problem, e.g. its designed to provide nodes to Zuul as test slaves, but we want to provide BM resources for the next layer down, i.e the instances created during the tests17:37
jrollbut yes, in the meantime molteniron is useful for third party CI people17:37
krtayloryes, thats what we've found17:37
devanandaso we have two discussions going in parallel: a) should this CI tool be embraced, or deffered until nodepool gets better? b) should it be part of the ironic project team umbrella, and thereby get access to shared resources, give contributors voting rights, etc17:37
mat128sambetts: so molteniron is about delegating hardware resources to a test run so you don't have resource clash17:38
sambettsmat128: yes17:38
mat128sounds like our day to day problems from 7-8 years ago :)17:38
mat128with a physical lab17:38
krtaylorexactly, and as late as possible17:38
mat128got it then17:38
devanandaI think that, regardless of (a), if molteniron is used today by two of our driver maintainers (ibm and dell)17:38
JayFdevananda: and maybe c) What exactly does it mean to be a part of Bare Metal governance, and if we need clear guidlines about what is in/out17:38
devanandaand the designated driver maintainers are the ones working on molteniron already17:38
devanandait's already being developd by the ironic project team and I don't see a reason not to include the project17:39
mariojvi think i'd be +1 to this if the mission of MoltenIron were something more general, instead of solely testing/ci. this would definitely be easier to decide if we had clearer definitions of what is/is not under our umbrella17:39
devanandaJayF: what it means is quite clear, from a TC / Foundation perspective17:39
dtantsurdevananda, do you propose that as a general guidance?17:39
*** iyamahat has joined #openstack-meeting-317:40
devanandaJayF: voting rights in the PTL and TC election, access to cross-project resources, access to summit / PTG time (as determined by the PTL)17:40
mat128mariojv: "Delegate parts of a physical lab to an Ironic installation" sounds generic enough17:40
rlooit may be clear from a TC/Foundation perspective but it isn't clear to us :-(17:40
JayFdevananda: I agree with your logic about why it should be included. My question would then be: why wouldn't something like ironic-staging-drivers be included under the same logic?17:40
devanandarloo: ^ does that help?17:40
jrolldevananda: the TC/foundation doesn't mandate what is part of a project team's governance, though, that's completely up to the project team17:40
*** hshiina has quit IRC17:40
devanandaJayF: because, AIUI, the core team prevoiusly said "we do not want to accept responsibility for maintaining these drivers"17:40
devanandajroll: indeed17:41
rlookrtaylor: so you want to be under the ironic umbrella why again?17:41
jrollsome of the core team said that, yes17:41
lucasagomesyeah, all cores in the staging-drivers are also cores in ironic (/me don't want to diverge this conversation to it tho)17:41
rlookrtaylor: i mean, molteniron is being used as-is now. what will change (what do you want to have changed) if it is under our umbrella17:41
sambettsFor those interested, https://www.openstack.org/summit/barcelona-2016/summit-schedule/events/16921/cross-project-workshops-where-to-draw-the-line-for-proprietary-code-with-drivers17:41
sambettsdtantsur:  ^17:42
krtaylorrloo, hehheh, we are splitting out of third-party-ci-tools repo, so either a nongoverned project or the ironic umbrella made sense to us17:42
dtantsurdevananda, well, then "accept responsibility" is also an argument, right?17:42
rlookrtaylor: and i may have missed it. why are you splitting out? getting kicked out?17:42
dtantsurdo we want to accept responsibility for this new thing?17:42
krtaylorrloo, no, not kicked out, we want to add tests, docs, ect17:42
mjturekright, it's hard for us to manage enhancements  under it as well.17:43
krtaylorrloo, third-party-ci-tools repo is tests noop17:43
rlookrtaylor: ok. i think this is worth talking to infra folks about first.17:43
dtantsurfwiw you can add tests (even dsvm) for non-official projects17:43
jrollto be clear, you can use openstack... what dtantsur said17:43
devanandakrtaylor: splitting the project code into a separate repository seems orthogonal to whether that is under ironic project team governance17:43
dtantsurironic-staging-drivers has a dsvm job, for example17:43
mat128devananda: ++17:43
devanandakrtaylor: you can easily create your own project, add tests, publish docs to readthedocs, etc17:43
jrollso maybe we should do this:17:44
jrollmolteniron friends can work on making their own repo with tests running and such17:44
devanandaand then very easily be added to ironic governance at any later time17:44
jrollwhile we go to the summit and bikeshed about the governance topic17:44
krtaylordevananda, agreed17:44
devanandajroll: ++17:44
mjturekjroll: sounds reasonable to me!17:44
TheJuliajroll: ++17:44
JayFI mean, I disagree17:44
sambettssounds good17:44
jrolland send summary to the ML for those not at the summit17:44
dtantsurjroll++17:44
rloojroll: and talk to infra folks about molteniron17:44
JayFbecause I'd like people not at the summit to have input into the governance topic17:44
jrolland continue the conversation there17:44
* jroll will talk in full thoughts17:45
lucasagomesjroll, agree... maybe we should talk there and then ML the outcome17:45
dtantsurmaybe we can start with the ML, then continue in person, then again the ML?17:45
mat128JayF: we should have a virtual summit :)17:45
dtantsurto not exclude JayF and mat128 from the topic?17:45
jrollrewritten: molteniron friends can work on making their own repo with tests running and such, while we go to the summit and bikeshed about the governance topic, and send summary to the ML for those not at the summit, and continue the conversation there17:45
krtaylorthat seems reasonable, mjturek you agree?17:45
mjturek+117:45
lucasagomesjroll, +117:46
jrolldtantsur: we could, yeah17:46
*** spzala has joined #openstack-meeting-317:46
* rloo still wants to know what infra is thinking wrt v3, molteniron17:46
mat128jroll: I'm fine with that, but unsure if this is what JayF meant. Will let him answer though17:46
dtantsurstarting with the ML could help us get ideas from other teams17:46
dtantsure.g. neutron folks definitely have a different view ;)17:46
JayFI just wanna make sure folks not at the summit don't end up having zero input beyond just reading a consensus developed without them17:46
jrolldtantsur: heh17:46
JayFI know how well we take notes for these sort of ... "bikeshed about X" discussions at the summit17:47
jrollJayF: we won't stamp anything17:47
JayFand traditionally most of the decision is made there17:47
mjturekheh17:47
* rloo glad that JayF isn't going to the summit so he can stand up for those that don't attend17:47
jrollbut we need to document it post-summit17:47
krtayloragreed17:47
JayFI am -1 to a solution that ends in "talk about it at the summit".17:47
* dtantsur prefers to see summits as "make up our own minds" rather than "set something in stone forever"17:47
jrollJayF: which solution ended with that?17:47
mat128dtantsur: nothing is ever set in stone :)17:47
dtantsurmat128, yeah, but I think you get the idea :)17:48
JayFLiterally what you just said; the discussion happens at the summit with a summary to the ML. Myself and others not in Barcelona are going to be missing a whole truckload of context.17:48
JayFI mean, if that's what the majority says, it is what it is17:48
jrollJayF: "and continue the conversation there" (there == ML)17:48
jroll...17:48
JayFbut especially for governance things we need to ask how open it is to have the bulk of the conversation in aplace that requires $$$$ to attend17:48
dtantsurmy version: molteniron friends can work on making their own repo with tests running and such, while we go to the summit and bikeshed about the governance topic, and propose a summary for further discussion to ironic-specs17:48
mat128^ i like that wording17:49
rlooJayF: what's the use of going to the summit then, if not to have discussions etc?17:49
mat128less interepretation17:49
jrollrloo++17:49
jrollJayF: it sounds like you're saying we shouldn't discuss anything at the summit17:49
jrollor anything important, at least17:49
mariojvi'm +1 to dtantsur's suggestion, as someone not going to the summit. we can still have input there at least17:50
JayFI'm saying, especially for governance stuff, we should be careful to ensure the conversations happen in a place where everyone has an equal voice.17:50
JayFI clearly wouldn't feel so strongly this way if I was going to the summit17:50
mariojvif it's something really important that's being discussed like governance, maybe require a stricter threshold for passing it, like 4 +2s17:50
JayFbut I'm glad to have this experience to consider next time I *am* there hiow folks who are excluded might feel17:50
devanandaJayF: it's the nature / purpose of the summit that important discussions happen17:50
rloolook, nothing gets totally passed at the summit. or shouldn't. i hope whatever was discussed/decided upon, is reflected in some patch that people can comment on post-summit17:51
devanandarloo: ++17:51
lucasagomesrloo, yeah17:51
jroll+117:51
dtantsurthat's why I propose an ironic-specs patch (or docs or whatever) later on17:51
rlooand if that isn't the case, please point it out17:51
devanandaI don't think anyone has said we're going to decide once-and-for-all on anything at the summit17:51
jrollwe can't just restrict discussions because folks may miss context, IMO17:51
jrollnow, I'm totally +2 on starting the discussion now, in the ML17:52
jrollbut I don't want to be the one to start that thread and then go on vacation for the week17:52
devanandabut we can't NOT use that time to discuss important things -- it is the time with peak mass of people involved in the project17:52
devanandaeven this IRC meeting doesn't have every contributor, and for some years, we didn't even have every core here, because of timezone differences17:53
jroll(and still don't)17:53
devanandathis is why TC uses gerrit17:53
JayFThis IRC meeting is at least logged in its entirety. That's not true of summit sessions. At this point, it doesn't matter though, the path forward is decided. I just don't like it, and that's OK.17:54
devanandaand requires every motion be posted for a certain number of days, and discussed in at least one meeting, before being passed17:54
JayFdevananda: ++ tjat17:54
JayF*That's what I care more about; discussions at the summit are more opaque17:54
jrollJayF: like I said, we can start now in the ML, if somebody is willing to do that17:54
jrollother than that I see no alternatives17:54
mjturekjroll: I can start it up17:54
mjturekif that's preferred17:54
JayFthanks mjturek17:54
jrollmjturek: thanks17:55
jrollhowever17:55
TheJulia5 minute warning17:55
jrollI would like the ML conversation to be around "what should and should not be in ironic's governance"17:55
jrollnot "should molteniron be there"17:55
mjturekahhh sorry17:55
jrollmjturek: you're still welcome to start that discussion, of course17:55
jrolljust pointing out that's the real question here17:56
jrollgoing to move to open discussion in case there's anything else, thanks TheJulia17:56
mjturekjroll: sure, I'll post to the ML later17:56
jroll#topic open discussion17:56
*** openstack changes topic to "open discussion (Meeting topic: ironic)"17:56
jrollmjturek: thanks17:56
lucasagomesso the doodle about the meetup in barcelona is here: http://doodle.com/poll/56qkr5rsxu447acr17:56
lucasagomesshould I send it to the ML as well ?17:56
jrolllucasagomes: can't hurt17:56
lucasagomesjroll, ack, will do after the meeting17:56
krtaylorlucasagomes, nice17:57
lucasagomesso ppl willing to attend the meeting, please vote for the best date at17:57
lucasagomes#link http://doodle.com/poll/56qkr5rsxu447acr17:57
dtantsurlucasagomes, I'd wish it has "tentative" option17:57
* lucasagomes is not doodle expert17:57
*** paul-carlton2 has quit IRC17:57
lucasagomesdtantsur, I can edit it and try to add17:57
jlvillallucasagomes: Is that assuming in the evening?17:58
dtantsurlucasagomes, yeah, it's somewhere in "advanced" options17:58
lucasagomesjlvillal, yes17:58
* lucasagomes should add it to the description17:58
lucasagomesdtantsur, I will take a look17:58
lucasagomesthat said, it's not guaranteed that we get a venue. I got some indications of possible ones and I will try to make it happen17:59
lucasagomesif not we just gather together at the summit and go to a pub or something :-)17:59
dtantsur++17:59
jroll++17:59
*** ociuhandu has quit IRC17:59
jrollalright, that's time, thanks everyone17:59
jroll#endmeeting17:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"18:00
lucasagomesty18:00
openstackMeeting ended Mon Oct 17 17:59:59 2016 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-10-17-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-10-17-17.00.txt18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/ironic/2016/ironic.2016-10-17-17.00.log.html18:00
*** dtantsur has left #openstack-meeting-318:00
*** yuriyz|2 has quit IRC18:00
*** milan has left #openstack-meeting-318:00
*** mariojv has left #openstack-meeting-318:00
*** sambetts is now known as sambetts|afk18:01
*** lucasagomes has left #openstack-meeting-318:01
*** rama_y has joined #openstack-meeting-318:01
*** markvoelker_ has quit IRC18:03
*** s3wong has joined #openstack-meeting-318:04
*** mmedvede has joined #openstack-meeting-318:04
*** rpioso has left #openstack-meeting-318:04
*** aarefiev22 has quit IRC18:04
*** rloo has left #openstack-meeting-318:04
*** lpetrut has quit IRC18:04
*** kzaitsev_mb has quit IRC18:17
*** mjturek has quit IRC18:22
*** VW has quit IRC18:26
*** yamahata has joined #openstack-meeting-318:28
*** shwetaap has quit IRC18:29
*** shwetaap has joined #openstack-meeting-318:30
*** mjturek has joined #openstack-meeting-318:31
*** stanzgy_ has joined #openstack-meeting-318:40
*** stanzgy has quit IRC18:41
*** mjturek has left #openstack-meeting-318:50
*** xhku has left #openstack-meeting-318:51
*** bfournie has left #openstack-meeting-318:51
*** alexismonville has quit IRC18:54
*** chandanc has quit IRC18:54
*** shwetaap has quit IRC18:55
*** bauzas has quit IRC18:56
*** rajinir has joined #openstack-meeting-318:58
*** med_` is now known as medberry19:03
*** medberry has joined #openstack-meeting-319:03
*** alexismonville has joined #openstack-meeting-319:11
*** yamahata has quit IRC19:14
*** iyamahat has quit IRC19:15
*** rhagarty has quit IRC19:17
*** VW has joined #openstack-meeting-319:20
*** kzaitsev_mb has joined #openstack-meeting-319:23
*** vishwanathj has joined #openstack-meeting-319:24
*** lpetrut has joined #openstack-meeting-319:25
*** iyamahat has joined #openstack-meeting-319:29
*** ianychoi has quit IRC19:29
*** egallen has quit IRC19:30
*** egallen has joined #openstack-meeting-319:32
*** ccamacho has quit IRC19:34
*** tonytan4ever has quit IRC19:34
*** egallen has quit IRC19:37
*** kzaitsev_mb has quit IRC19:38
*** pas-ha has left #openstack-meeting-319:42
*** egallen has joined #openstack-meeting-319:44
*** piet_ has quit IRC19:47
*** ccamacho has joined #openstack-meeting-319:51
*** yamahata has joined #openstack-meeting-319:52
*** tonytan4ever has joined #openstack-meeting-319:58
*** spzala has quit IRC19:58
*** tonytan_brb has joined #openstack-meeting-319:59
*** spzala has joined #openstack-meeting-319:59
*** spzala has quit IRC19:59
*** spzala has joined #openstack-meeting-319:59
*** matjazp has joined #openstack-meeting-320:00
*** medberry has quit IRC20:00
*** yamahata has quit IRC20:00
*** med_ has joined #openstack-meeting-320:00
*** stanzgy_ has quit IRC20:00
*** med_ is now known as Guest6284620:01
*** VW has quit IRC20:01
*** tqtran has quit IRC20:02
*** bauzas has joined #openstack-meeting-320:02
*** tonytan4ever has quit IRC20:02
*** VW has joined #openstack-meeting-320:03
*** tonytan_brb has quit IRC20:04
*** MeganR has quit IRC20:04
*** tonytan4ever has joined #openstack-meeting-320:05
*** mfedosin has quit IRC20:07
*** tonytan4ever has quit IRC20:15
*** matrohon has joined #openstack-meeting-320:18
*** julim has quit IRC20:20
*** shwetaap has joined #openstack-meeting-320:21
*** julim has joined #openstack-meeting-320:21
*** flwang1 has quit IRC20:21
*** rhagarty has joined #openstack-meeting-320:23
*** abalutoiu has quit IRC20:24
*** hichihara has joined #openstack-meeting-320:24
*** pcaruana has quit IRC20:25
*** julim has quit IRC20:25
*** yamahata has joined #openstack-meeting-320:30
*** tonytan4ever has joined #openstack-meeting-320:32
*** tqtran has joined #openstack-meeting-320:33
*** markvoelker has joined #openstack-meeting-320:34
*** baoli has quit IRC20:35
*** piet_ has joined #openstack-meeting-320:36
*** markvoelker_ has joined #openstack-meeting-320:37
*** tonytan4ever has quit IRC20:38
*** abalutoiu has joined #openstack-meeting-320:40
*** markvoelker has quit IRC20:41
*** tonytan4ever has joined #openstack-meeting-320:41
*** andystack has quit IRC20:42
*** vhoward has quit IRC20:44
*** matrohon has quit IRC20:50
*** yamahata has quit IRC20:55
*** yamahata has joined #openstack-meeting-320:55
*** tonytan4ever has quit IRC20:56
*** tonytan4ever has joined #openstack-meeting-320:57
*** tonytan4ever has quit IRC20:57
*** MeganR has joined #openstack-meeting-320:59
*** krtaylor has quit IRC21:01
*** lblanchard has quit IRC21:06
*** shamail has joined #openstack-meeting-321:10
*** Rockyg has quit IRC21:12
*** Rockyg has joined #openstack-meeting-321:12
*** matjazp has quit IRC21:13
*** Rocky_g has joined #openstack-meeting-321:14
*** Rocky_g has quit IRC21:14
*** spzala has quit IRC21:18
*** spzala has joined #openstack-meeting-321:19
*** rhagarty has quit IRC21:22
*** jdwald has quit IRC21:22
*** mickeys has quit IRC21:23
*** mickeys has joined #openstack-meeting-321:23
*** VW has quit IRC21:32
*** ianychoi has joined #openstack-meeting-321:33
*** VW has joined #openstack-meeting-321:33
*** vishwanathj has quit IRC21:38
*** shamail has left #openstack-meeting-321:40
*** rtheis has quit IRC21:41
*** flwang1 has joined #openstack-meeting-321:46
*** Swami_ has joined #openstack-meeting-321:53
*** Swami has quit IRC21:56
*** Swami_ has quit IRC21:59
*** MeganR has quit IRC22:02
*** hichihara has quit IRC22:03
*** shwetaap has quit IRC22:03
*** marst has quit IRC22:05
*** VW_ has joined #openstack-meeting-322:17
*** spzala has quit IRC22:17
*** VW_ has joined #openstack-meeting-322:17
*** VW_ has quit IRC22:17
*** kzaitsev_mb has joined #openstack-meeting-322:19
*** VW has quit IRC22:20
*** lpetrut has quit IRC22:22
*** gouthamr has quit IRC22:23
*** marst has joined #openstack-meeting-322:24
*** abalutoiu has quit IRC22:26
*** mickeys has quit IRC22:29
*** Swami has joined #openstack-meeting-322:31
*** Swami_ has joined #openstack-meeting-322:36
*** marst has quit IRC22:38
*** Swami has quit IRC22:39
*** marst has joined #openstack-meeting-322:46
*** mickeys has joined #openstack-meeting-322:49
*** Swami__ has joined #openstack-meeting-322:52
*** marst has quit IRC22:53
*** Swami_ has quit IRC22:55
*** gouthamr has joined #openstack-meeting-322:59
*** markvoelker_ has quit IRC23:01
*** s3wong_ has joined #openstack-meeting-323:02
*** dloi has quit IRC23:03
*** s3wong has quit IRC23:04
*** zz_dimtruck is now known as dimtruck23:04
*** s3wong_ is now known as s3wong23:08
*** dloi has joined #openstack-meeting-323:09
*** egallen has quit IRC23:10
*** baoli has joined #openstack-meeting-323:10
*** sdague has quit IRC23:10
*** haleyb_ has joined #openstack-meeting-323:10
*** baoli has quit IRC23:15
*** amotoki has quit IRC23:31
*** rama_y has quit IRC23:33
*** rajinir has quit IRC23:36
*** amotoki has joined #openstack-meeting-323:44

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