Thursday, 2019-03-28

*** hongbin has joined #openstack-meeting-400:18
*** iyamahat has joined #openstack-meeting-400:45
*** cheng1 has joined #openstack-meeting-401:12
*** cheng1 has quit IRC01:27
*** celebdor has quit IRC01:37
*** cheng1 has joined #openstack-meeting-401:38
*** yamamoto has joined #openstack-meeting-402:15
*** diablo_rojo has joined #openstack-meeting-402:24
*** iyamahat has quit IRC02:26
*** yamahata has quit IRC02:26
*** k_mouza has quit IRC02:26
*** cheng1 has quit IRC02:37
*** cheng1 has joined #openstack-meeting-402:38
*** diablo_rojo has quit IRC02:47
*** k_mouza has joined #openstack-meeting-402:47
*** psachin has joined #openstack-meeting-402:52
*** k_mouza has quit IRC02:52
*** yamamoto has quit IRC03:18
*** cheng1 has quit IRC03:24
*** hongbin has quit IRC03:28
*** k_mouza has joined #openstack-meeting-403:29
*** k_mouza has quit IRC03:33
*** yamamoto has joined #openstack-meeting-403:42
*** k_mouza has joined #openstack-meeting-403:49
*** k_mouza has quit IRC03:54
*** cheng1 has joined #openstack-meeting-404:03
*** k_mouza has joined #openstack-meeting-404:10
*** k_mouza has quit IRC04:14
*** yamamoto has quit IRC04:25
*** yamamoto has joined #openstack-meeting-404:29
*** k_mouza has joined #openstack-meeting-404:30
*** k_mouza has quit IRC04:35
*** janki has joined #openstack-meeting-404:41
*** markvoelker has joined #openstack-meeting-405:04
*** premsankar has quit IRC05:11
*** k_mouza has joined #openstack-meeting-405:12
*** k_mouza has quit IRC05:16
*** igordc has quit IRC05:57
*** slaweq has quit IRC06:07
*** gcheresh has joined #openstack-meeting-406:08
*** cheng1 has quit IRC06:10
*** cheng1 has joined #openstack-meeting-406:20
*** gcheresh has quit IRC06:50
*** gcheresh has joined #openstack-meeting-406:56
*** slaweq has joined #openstack-meeting-407:14
*** serhatd_ has left #openstack-meeting-407:14
*** e0ne has joined #openstack-meeting-407:17
*** e0ne has quit IRC07:19
*** pcaruana has joined #openstack-meeting-407:20
*** yboaron_ has joined #openstack-meeting-407:22
*** celebdor has joined #openstack-meeting-408:04
*** k_mouza has joined #openstack-meeting-408:47
*** ralonsoh has joined #openstack-meeting-409:06
*** oanson has quit IRC09:10
*** snapiri has quit IRC09:10
*** snapiri has joined #openstack-meeting-409:18
*** shachar has joined #openstack-meeting-409:21
*** snapiri has quit IRC09:22
*** cheng1 has quit IRC09:30
*** ktibi has joined #openstack-meeting-409:39
*** oanson has joined #openstack-meeting-409:41
*** cheng1 has joined #openstack-meeting-409:45
*** e0ne has joined #openstack-meeting-409:47
*** lpetrut has joined #openstack-meeting-409:54
*** yamamoto has quit IRC10:03
*** yamamoto has joined #openstack-meeting-410:07
*** melwitt has quit IRC10:26
*** e0ne has quit IRC10:31
*** melwitt has joined #openstack-meeting-410:32
*** e0ne has joined #openstack-meeting-410:36
*** yamamoto has quit IRC10:37
*** yamamoto has joined #openstack-meeting-410:41
*** e0ne has quit IRC10:58
*** e0ne has joined #openstack-meeting-411:05
*** janki has quit IRC11:18
*** cheng1 has quit IRC11:21
*** k_mouza has quit IRC11:25
*** k_mouza has joined #openstack-meeting-411:25
*** k_mouza has quit IRC11:42
*** k_mouza has joined #openstack-meeting-411:42
*** janki has joined #openstack-meeting-411:43
*** cheng1 has joined #openstack-meeting-411:45
*** ktibi has quit IRC11:46
*** seajay has joined #openstack-meeting-411:59
*** markvoelker has quit IRC12:20
*** yamamoto has quit IRC12:21
*** yamamoto has joined #openstack-meeting-412:21
*** cheng1 has quit IRC12:25
*** rosmaita has joined #openstack-meeting-412:34
*** cheng1 has joined #openstack-meeting-412:37
*** ktibi has joined #openstack-meeting-412:40
*** celebdor has quit IRC12:41
*** e0ne has quit IRC12:41
*** e0ne has joined #openstack-meeting-412:43
*** celebdor has joined #openstack-meeting-412:50
*** Luzi has joined #openstack-meeting-413:03
*** ktibi has quit IRC13:10
*** e0ne has quit IRC13:20
*** howell has joined #openstack-meeting-413:21
*** lpetrut has quit IRC13:25
*** ktibi has joined #openstack-meeting-413:43
*** k_mouza has quit IRC13:44
*** ktibi has quit IRC13:51
*** yamamoto has quit IRC13:53
*** abhishekk has joined #openstack-meeting-413:59
*** ktibi has joined #openstack-meeting-414:00
*** yamamoto has joined #openstack-meeting-414:01
*** jokke_ has joined #openstack-meeting-414:01
jokke_#startmeeting glance14:01
openstackMeeting started Thu Mar 28 14:01:43 2019 UTC and is due to finish in 60 minutes.  The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
*** openstack changes topic to " (Meeting topic: glance)"14:01
openstackThe meeting name has been set to 'glance'14:01
jokke_#topic roll-call14:01
*** openstack changes topic to "roll-call (Meeting topic: glance)"14:01
jokke_o/14:01
rosmaitao/14:02
*** smcginnis has joined #openstack-meeting-414:02
smcginniso/14:02
jokke_#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:02
abhishekko/14:02
jokke_cool we have everyone here14:03
jokke_#topic updates14:03
*** openstack changes topic to "updates (Meeting topic: glance)"14:03
jokke_So looks like RC1 was success ... there's no critical bugs opened against it and it did not break the world \\o \o/ o// o/714:03
smcginnisAlways nice when the world doesn't break. :)14:04
jokke_yeah14:04
jokke_also the osc goal discussion is still going https://review.openstack.org/#/c/639376/4/goals/train/osc.rst14:05
jokke_Oh, and I fecked up ... totally missed the proposal window for forum sessions so we won't be having one14:05
*** yamamoto has quit IRC14:05
jokke_doing some finetuning on my mailing list filtering, hopefully will not miss such info in the future14:06
jokke_on that note14:07
jokke_#topic release updates14:07
*** openstack changes topic to "release updates (Meeting topic: glance)"14:07
jokke_abhishekk: welcome back14:07
abhishekk:D14:07
abhishekkas you just said we have successful glance rc1 release14:07
rosmaitayeah, the switch to openstack-discuss has been a PITA14:07
abhishekkno bug reported yet14:07
jokke_well there is a bug, but by quick glance it's brick not glance using the deprecated import14:08
abhishekkregarding periodic job we are still hitting with py35 interpreter not found error14:08
jokke_https://bugs.launchpad.net/glance/+bug/182130614:08
openstackLaunchpad bug 1821306 in os-brick "Using or importing the ABCs from 'collections' is deprecated" [Undecided,New]14:08
smcginnisOh, I hadn't seen that one yet.14:08
jokke_no actually we do it directly as well it seems14:09
smcginnisLooks like it should be an easy fix in os-brick.14:09
jokke_shouldn't be a big deal to fix and if that's the very only thing, I'm not sure fixing that warrants RC2 for us14:10
smcginnisGood to get rid of deprecation warnings, but I wouldn't consider it a critical issue.14:10
jokke_indeed14:10
abhishekkI will try to contact infra team regarding the py35 interpreter error14:10
rosmaitamaybe we need to change those tests to use py36 ?14:11
abhishekkmight be14:11
smcginnisOh, could be now that legacy jobs were switched to run on bionic nodes.14:12
jokke_So I thought there was some shifting around the py3 versions, not sure what we are actually supposed to be testing atm.14:12
rosmaitapy36 for stein14:13
rosmaitagmann has had some patches up for the tempest and grenade stuff, i think14:13
jokke_sounds kind of crazy that we're running tests on py 35, 36 and 37 but on the same time, the rate python is bringing backwards incompatibilities into 3.minor releases might be needed14:14
smcginnisYep, py36 is the default py3 for stein, py37 is good to test to make sure we are OK on the next bump.14:14
smcginnisI believe in train we can make sure all the py35 stuff is gone. Only really needed for grenade upgrades if I understood right.14:14
jokke_ok, lets swap the 35 tests to 36 and see if we get rid of those failures14:14
abhishekkack14:15
abhishekkthat's it from me14:17
abhishekk(I thought, I got disconnected)14:17
*** k_mouza has joined #openstack-meeting-414:18
jokke_ok14:18
jokke_moving on14:18
abhishekkevery thing on the agenda is rosmaita now :D14:18
rosmaita:)14:18
jokke_#topic queens backport14:19
*** openstack changes topic to "queens backport (Meeting topic: glance)"14:19
rosmaitaacutally, it's me talking about abhishekk's stuff!14:19
smcginnis:)14:19
jokke_didn't copy the hash to the topic :D14:19
abhishekk:d14:19
rosmaitaok, i think someone hit the 'file' store missing bug yesterday in #openstack-glance14:19
rosmaita#link http://eavesdrop.openstack.org/irclogs/%23openstack-glance/%23openstack-glance.2019-03-27.log.html#t2019-03-27T19:44:1714:20
abhishekkYes, I will backport it to queens (may be tomorrow)14:20
rosmaitanot sure exactly, but sounded liike it14:20
rosmaitaok, i was just wondering if it will be a clean backport (i think so)14:20
rosmaitaok, we can wait and see on that14:20
rosmaitai think it would be worth doing new stable releases with that bugfix?14:21
smcginnisLooks like it should be easy to backport. And good.14:21
rosmaitaok, cool, that's really all i had on that14:21
jokke_it should be as iirc it does not use the multi-store interface14:21
jokke_kk14:21
jokke_#topic inconsistencies in multistore API?14:21
*** openstack changes topic to "inconsistencies in multistore API? (Meeting topic: glance)"14:22
rosmaitaok, this may be controversial14:22
abhishekkonly case is that we didn't have tests in queens14:22
abhishekkso we only need to backport the actual code14:22
rosmaitai guess that's ok?14:22
abhishekkI guess so14:23
jokke_I would love to backport the tests as well, but if it's hell of a lot effort lets stick with the fix only14:23
jokke_#undo14:23
openstackRemoving item from minutes: #topic inconsistencies in multistore API?14:23
jokke_that all from it?14:24
abhishekkyes14:24
jokke_#topic inconsistencies in multistore API?14:24
*** openstack changes topic to "inconsistencies in multistore API? (Meeting topic: glance)"14:24
rosmaitai guess we can be confident that the rocky tests cover that part of queens?14:24
jokke_lets try this again :D14:24
abhishekk:D14:24
rosmaita(sorry, my typing is slow)14:24
abhishekkI am confident enough14:24
rosmaitajokke_: ? smcginnis: ?14:25
rosmaitai think i am ok with it14:25
jokke_#undo14:25
openstackRemoving item from minutes: #topic inconsistencies in multistore API?14:25
smcginnisYeah, should be good. I like the idea of backporting the tests if it's not too much work.14:26
rosmaitaok, we're not really in a rush on that14:26
rosmaitawe can let Abhishek do a backport and report back on the test situation14:26
abhishekkI will try best to backport tests as well14:26
jokke_well yeah ... it is deep stable ... like said in principle it would be great if we had the tests but if it's anyting else than finding the test patch and cherrypicking it in, lets forget it as we have already soon 2 stable branches in between14:26
abhishekkack14:28
jokke_it's just matter of principle and having tests for bugfixes. but like said it's very unlikely we manage to backport something that breaks it over 2 stable branches without noticing (or that the same tests would catch there something they did not catch on previous merges/backports)14:28
jokke_so definitely don't spend too much effort on the tests14:29
smcginnis++14:29
rosmaita++14:29
abhishekkok14:29
rosmaitathere is also the workaround of just having 'file' in the 'stores' config option14:30
rosmaitaam i right that as long as 'file' is in there, you don't hit the bug?14:30
abhishekkyes14:30
rosmaitaok, just wanted to verify14:30
jokke_there is that but also the proper fix is well self contained so there is really no reason why we should not backport it14:31
rosmaitai know i looked at it like a week ago, but it seems longer for some reason14:31
rosmaitajokke_: i agree14:31
abhishekk2 weeks almost14:31
abhishekklets move ahead14:32
jokke_rosmaita: anything else on this?14:32
rosmaitanot from me (for real this time)14:32
jokke_#topic inconsistencies in multistore API?14:32
*** openstack changes topic to "inconsistencies in multistore API? (Meeting topic: glance)"14:32
rosmaitaok, the background is a spec abhishekk has for cinder14:32
rosmaita#link https://review.openstack.org/#/c/641267/14:32
rosmaitai was looking at our docs and api calls14:33
rosmaitawe use 'store' when we are talking to end users14:33
rosmaitabut we tend to use 'backend' also14:33
rosmaitamy question is whether we should be more consistent about this14:33
rosmaitaso that it's easier to configure, etc14:33
abhishekkso you are suggesting to use store instead of backend?14:34
rosmaitayes14:34
rosmaitai think 'backend' shows up in the location metadata now?14:34
rosmaitais that right?14:34
abhishekkthe reason I have choose backend is we already have default_store option14:34
abhishekkfor single store deployment14:34
rosmaitayes, i kind of remember our discssion about this at the beginning of the cycle14:35
jokke_yeah14:35
rosmaitabut i think we should use 'store' to the greatest extent possible14:35
abhishekkand we can not use same option in case of multiple store deployment so I have renamed every option to backend i.e enabled_backends, default_backend etc14:35
rosmaitaok, i think that is ok for operator only facing stuff14:36
rosmaitabut something a user might see should be a 'store', i think14:36
jokke_it's one of these things where we can be user friendly by not accidentally breaking anything by overloading config options, etc. but then causing some confusion when we have "same" config options under multiple names for that14:36
abhishekkyes14:36
rosmaitai think the location metadata is the only place you'd see a 'backend' now as an end user?14:37
abhishekkso we should rename --backend to --store?14:37
rosmaitaalso in the glanceclient mabye? but we can fix that14:37
rosmaitathat is my thought14:37
rosmaitasince the api-ref is all talking about  stores14:37
jokke_and probably call it --store-id14:37
rosmaitaand the http header is something-Store14:37
jokke_just ot be super clear14:38
abhishekkok, I will identify al the cases including docs, input parameters etc and create one etherpad which will help us to identify the impact14:38
rosmaitayes, since we use 'id' in the /info response, i agree that store-id is cool14:38
*** e0ne has joined #openstack-meeting-414:38
rosmaitagreat, there is no rush on it, just before the API goes out of experimental14:38
rosmaitawe can assess at the ptg14:38
jokke_IIRC the feature is experimental through all three repos so it should not be big deal to change14:38
abhishekkcool14:39
rosmaitai don't want to make a lot of extra work, but it will be good to be consistent as much as possible14:39
abhishekkif it is simple change we can merge it before ptg as well14:39
rosmaitaabhishekk: ++14:39
jokke_just lets add that to the list of multi-store stuff we need to address in PTG14:39
*** hongbin has joined #openstack-meeting-414:39
abhishekkack14:39
rosmaitaok, cool14:39
rosmaitathat's all i have on this14:39
*** cheng1 has quit IRC14:40
jokke_I'd prefer not to act on the multistore stuff we consider changing before PTG so we have the whole picture how we are moving forward with that14:40
abhishekkrosmaita, between, does cinder proposal looks good to you?14:40
abhishekkjokke_, ack14:40
jokke_If we have many things on our list I just schedule whole day for it14:41
rosmaitaabhishekk: i think so, i had some more comments, don't know if you saw them yet14:41
rosmaitajokke_: ++ for multistore full day14:41
abhishekkrosmaita, I have fixed them and uploaded new spec as well14:41
rosmaitaabhishekk: cool14:41
abhishekkjokke_, ++14:41
rosmaitai put your spec as a proposal for the cinder ptg sessions14:42
abhishekkrosmaita, great14:42
rosmaitawould be good to discuss it quickly with the cinder team14:42
abhishekkI am working on PoC for both proposed as well as alternative solution, once done I will share with you14:43
abhishekkrosmaita, ++14:43
rosmaitaabhishekk: very nice14:43
rosmaitajokke_: also the encryption key management thing, it's on both our and cinder's ptg etherpad14:43
jokke_kk14:44
*** yboaron_ has quit IRC14:44
jokke_anything else on this?14:44
rosmaitanot from me14:45
abhishekknope14:45
jokke_#topic open discussion14:45
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:45
jokke_rosmaita had something flagged here as well I think14:45
rosmaitai just tossed some stuff on the etherpad in case we have time to sit down together and code at the PTG14:46
rosmaitathe first on is the config files14:46
rosmaitawe did a regen for abhishek's change to the cache management14:46
rosmaitathat config file is insane, it has all sorts of stuff that i don't think is needed14:46
rosmaitabut i am not 100% sure14:47
rosmaitait would really help operators if we could sort those out a bit14:47
jokke_I think it's pretty much the copy of -api.conf just different name for different config values if needed14:47
abhishekk++14:47
rosmaitaeither that, or jsut have one super-duper config file and get rid of all these individual ones14:47
abhishekkeven same for scrubber.conf as well14:47
rosmaitayes14:47
rosmaitaanyway, would be nice if we have time14:48
jokke_I would really like to clean the config files up. For example remove all the redundant crap from the help texts to limit the size a bit ;)14:48
jokke_I think -api.conf hit like 4 or 5k lines now14:48
rosmaitawell, there's some oslo.config stuff we're not taking advantage of14:48
rosmaitalike defining descriptions for individual enumeration items14:49
rosmaitawe did it by hand, but now there's some kind of oslo.config thing14:49
rosmaitabut the output includes both14:49
rosmaitaso you see our list of what the stuff means14:49
rosmaitaand then a list of each item with <no doc available>14:50
rosmaitabut, remember that that help text is really the configuration documentation14:50
rosmaitaso that's why it is verbose even though jokke_ doesn't like it14:50
jokke_We have lots of verbosity there and then we have tons of redundant crap that is purely boilerplate overhead that provides no value14:51
jokke_but increases the volume of those files by a lot14:52
rosmaitai disagree about the no value ... the related items or no related items is pretty helpful14:52
rosmaitayeah, well, an operator can run sed and strip out all the comments14:52
rosmaitait's either that or maintain separate documentation for all of it14:52
rosmaitaand that gets out of date so fast it's not worth it14:53
rosmaitaanyway, we can discuss over beverages at the PTG14:53
jokke_rosmaita: my point is not that the ones that has values should not be there, my point is that we have that crap there for every single option just to have it there even if it's just the key14:53
abhishekk++ for beverages14:54
rosmaitajokke_: it's because if you let one option in with just a one-liner, everyone wants to do it!14:54
jokke_it's like prepopulating all possible property keys to every imgage in glance just so that the user can see what would be possibly there ;)14:54
jokke_rosmaita: and there is nothing wrong with that if the oneliner is explanary enough for the option documentation being clear14:54
rosmaitai think i could use a beverage now14:55
jokke_:D14:55
abhishekk:D14:55
rosmaitajokke_: everyone always thinks their oneliner is completely explanatory ... and they are pretty much never correct14:55
abhishekklast 4 minutes14:56
jokke_rosmaita: and that why we have something called code review to catch those. but "lets add 10 lines of boilerplating to every option because some of them might benefit the info being there" is giving us exactly what you wanted to clean up :D14:56
jokke_fecking messy and insanely long config files14:56
rosmaitaanyway, if the config revamp is too controversial, my second suggestion is to actually remove some of the deprecated stuff14:56
abhishekkagree to remove deprecated stuff14:57
rosmaitawe never get around to it, so it might be good to just sit down and do it all together14:57
abhishekk+114:57
jokke_so we will be removing a lot in train taken that our deprecation of registry is finally up ... so we can clean all that out of there14:57
rosmaitawith beverages!14:57
jokke_which will clean lots of the configs as well14:58
rosmaitawe could have a registry removal hackfest14:58
rosmaitayeah, maybe let's do that first, and worry about configs later14:58
jokke_including glance-registry.conf and glance-registry-paste.ini as whole14:58
jokke_last minute, anything else?14:59
abhishekknothing from me14:59
rosmaitawe can have t-shirts "I removed the glance registry and all i got was this dumb T-shirt"14:59
abhishekkthank you all14:59
abhishekk+20014:59
smcginnisThanks!14:59
rosmaitabye!14:59
smcginnisrosmaita: ++ :)14:59
jokke_rosmaita: *"registry/v1 api"14:59
jokke_Thanks all!14:59
jokke_#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Thu Mar 28 15:00:10 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-03-28-14.01.html15:00
rosmaitajokke_: you got no thanks for removing the v1 api!15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-03-28-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-03-28-14.01.log.html15:00
*** abhishekk has quit IRC15:00
jokke_rosmaita: ikr :D15:00
rosmaita:)15:00
*** rosmaita has left #openstack-meeting-415:01
*** yboaron_ has joined #openstack-meeting-415:05
*** smcginnis has left #openstack-meeting-415:08
*** hamzy has quit IRC15:10
*** e0ne has quit IRC15:14
*** e0ne has joined #openstack-meeting-415:20
*** Luzi has quit IRC15:25
*** hamzy has joined #openstack-meeting-415:35
*** e0ne has quit IRC15:40
*** yboaron_ has quit IRC15:59
*** yboaron_ has joined #openstack-meeting-416:00
*** diablo_rojo has joined #openstack-meeting-416:02
*** premsankar has joined #openstack-meeting-416:03
*** janki has quit IRC16:07
*** iyamahat has joined #openstack-meeting-416:18
*** e0ne has joined #openstack-meeting-416:27
*** k_mouza has quit IRC17:02
*** ktibi has quit IRC17:03
*** k_mouza has joined #openstack-meeting-417:03
*** psachin has quit IRC17:05
*** e0ne has quit IRC17:07
*** e0ne has joined #openstack-meeting-417:08
*** igordc has joined #openstack-meeting-417:11
*** e0ne has quit IRC17:17
*** e0ne has joined #openstack-meeting-417:21
*** iyamahat has quit IRC17:25
*** k_mouza has quit IRC17:26
*** gcheresh has quit IRC17:36
*** iyamahat has joined #openstack-meeting-417:37
*** iyamahat_ has joined #openstack-meeting-417:43
*** JamesBenson has joined #openstack-meeting-417:44
*** gcheresh has joined #openstack-meeting-417:45
*** e0ne has quit IRC17:45
*** iyamahat has quit IRC17:46
*** yamahata has joined #openstack-meeting-417:54
*** k_mouza has joined #openstack-meeting-418:08
*** celebdor has quit IRC18:23
*** ralonsoh has quit IRC18:31
*** gcheresh has quit IRC18:31
*** yamamoto has joined #openstack-meeting-418:54
*** yamamoto has quit IRC18:58
*** ktibi has joined #openstack-meeting-418:59
*** k_mouza_ has joined #openstack-meeting-419:17
*** k_mouza has quit IRC19:20
*** k_mouza_ has quit IRC19:27
*** e0ne has joined #openstack-meeting-419:33
*** k_mouza has joined #openstack-meeting-419:34
*** k_mouza has quit IRC19:54
*** e0ne has quit IRC20:00
*** k_mouza has joined #openstack-meeting-420:02
*** pcaruana has quit IRC20:08
*** ktibi has quit IRC20:32
*** hamzy has quit IRC20:54
*** howell has quit IRC21:24
*** k_mouza has quit IRC21:35
*** k_mouza has joined #openstack-meeting-421:49
*** JamesBenson has quit IRC21:57
*** yamamoto has joined #openstack-meeting-422:08
*** igordc has quit IRC22:22
*** yamamoto has quit IRC22:28
*** yamamoto has joined #openstack-meeting-422:36
*** yamamoto has quit IRC22:39
*** yamamoto has joined #openstack-meeting-422:43
*** yamamoto has quit IRC22:52
*** yamamoto has joined #openstack-meeting-422:54
*** hongbin has quit IRC23:02
*** yamamoto has quit IRC23:03
*** yamamoto has joined #openstack-meeting-423:04
*** seajay has quit IRC23:05
*** yamamoto has quit IRC23:14
*** slaweq has quit IRC23:17
*** yamamoto has joined #openstack-meeting-423:53
*** yamamoto has quit IRC23:55

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