Thursday, 2019-12-19

*** wuchunyang has joined #openstack-meeting-400:04
*** wuchunyang has quit IRC00:08
*** wuchunyang has joined #openstack-meeting-400:34
*** wuchunyang has quit IRC00:39
*** wuchunyang has joined #openstack-meeting-400:45
*** yamamoto has quit IRC00:48
*** wuchunyang has quit IRC00:50
*** wuchunyang has joined #openstack-meeting-400:52
*** wuchunyang has quit IRC00:57
*** Liang__ has joined #openstack-meeting-401:01
*** dave-mccowan has quit IRC02:26
*** ktibi has joined #openstack-meeting-402:41
*** ktibi has quit IRC02:46
*** yamamoto has joined #openstack-meeting-402:51
*** irclogbot_0 has quit IRC02:56
*** lvbin01 has joined #openstack-meeting-403:07
*** irclogbot_0 has joined #openstack-meeting-403:09
*** irclogbot_0 has quit IRC03:09
*** irclogbot_1 has joined #openstack-meeting-403:15
*** dave-mccowan has joined #openstack-meeting-403:20
*** psachin has joined #openstack-meeting-403:41
*** wuchunyang has joined #openstack-meeting-403:43
*** yamamoto has quit IRC03:51
*** k_mouza has joined #openstack-meeting-403:54
*** wuchunyang has quit IRC03:58
*** k_mouza has quit IRC03:58
*** wuchunyang has joined #openstack-meeting-404:04
*** yamamoto has joined #openstack-meeting-404:06
*** wuchunyang has quit IRC04:09
*** wuchunyang has joined #openstack-meeting-404:16
*** wuchunyang has quit IRC04:20
*** dosaboy has quit IRC04:23
*** icey has quit IRC04:24
*** wuchunyang has joined #openstack-meeting-405:04
*** wuchunyang has quit IRC05:10
*** wuchunyang has joined #openstack-meeting-405:13
*** wuchunyang has quit IRC05:17
*** wuchunyang has joined #openstack-meeting-405:18
*** wuchunyang has quit IRC05:23
*** wuchunyang has joined #openstack-meeting-405:29
*** wuchunyang has quit IRC05:35
*** psachin has quit IRC05:36
*** dave-mccowan has quit IRC05:39
*** wuchunyang has joined #openstack-meeting-405:40
*** pcaruana has joined #openstack-meeting-405:43
*** wuchunyang has quit IRC05:45
*** psachin has joined #openstack-meeting-405:56
*** links has joined #openstack-meeting-406:00
*** jraju__ has joined #openstack-meeting-406:04
*** links has quit IRC06:05
*** links has joined #openstack-meeting-406:52
*** jraju__ has quit IRC06:53
*** lpetrut has joined #openstack-meeting-407:06
*** lvbin01 has quit IRC07:12
*** lvbin01 has joined #openstack-meeting-407:13
*** gcheresh_ has joined #openstack-meeting-407:13
*** psachin has quit IRC07:44
*** irclogbot_1 has quit IRC07:44
*** irclogbot_1 has joined #openstack-meeting-407:45
*** psachin has joined #openstack-meeting-407:45
*** wuchunyang has joined #openstack-meeting-408:02
*** wuchunyang has quit IRC08:07
*** k_mouza has joined #openstack-meeting-408:30
*** k_mouza has quit IRC08:34
*** yamamoto has quit IRC08:46
*** yamamoto has joined #openstack-meeting-408:46
*** yamamoto has quit IRC08:46
*** yamamoto has joined #openstack-meeting-408:48
*** ralonsoh has joined #openstack-meeting-408:51
*** yamamoto has quit IRC08:53
*** yamamoto has joined #openstack-meeting-408:54
*** Liang__ has quit IRC09:23
*** e0ne has joined #openstack-meeting-409:45
*** bobmel has quit IRC09:55
*** gcheresh_ has quit IRC09:55
*** gcheresh_ has joined #openstack-meeting-409:57
*** k_mouza has joined #openstack-meeting-410:08
*** wuchunyang has joined #openstack-meeting-410:35
*** wuchunyang has quit IRC10:40
*** icey has joined #openstack-meeting-411:35
*** wuchunyang has joined #openstack-meeting-412:00
*** wuchunyang has quit IRC12:05
*** wuchunyang has joined #openstack-meeting-412:18
*** salmankhan has joined #openstack-meeting-412:25
*** wuchunyang has quit IRC12:26
*** salmankhan has quit IRC12:33
*** gcheresh_ has quit IRC12:37
*** gcheresh_ has joined #openstack-meeting-412:38
*** Liang__ has joined #openstack-meeting-412:47
*** Liang__ has quit IRC12:52
*** bobmel has joined #openstack-meeting-413:01
*** yamamoto has quit IRC13:02
*** tosky has joined #openstack-meeting-413:07
*** yamamoto has joined #openstack-meeting-413:24
*** yamamoto has quit IRC13:25
*** gcheresh_ has quit IRC13:26
*** gcheresh_ has joined #openstack-meeting-413:30
*** rosmaita has joined #openstack-meeting-413:31
*** yamamoto has joined #openstack-meeting-413:38
*** abhishekk has joined #openstack-meeting-413:46
*** bh526r has joined #openstack-meeting-413:56
*** yebinama has joined #openstack-meeting-413:56
abhishekk#startmeeting glance14:00
openstackMeeting started Thu Dec 19 14:00:04 2019 UTC and is due to finish in 60 minutes.  The chair is abhishekk. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
abhishekk#topic roll call14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
*** openstack changes topic to "roll call (Meeting topic: glance)"14:00
jokke_o/14:00
abhishekk#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
abhishekko/14:00
yebinamao/14:00
*** wuchunyang has joined #openstack-meeting-414:00
* tosky lurking14:00
abhishekkjokke_, could you pleasee co chair this meeting with me?14:00
rosmaitao/14:00
*** yamamoto has quit IRC14:01
abhishekkI don't have electricity since morning and my laptop may dry any moment14:01
jokke_abhishekk: kk14:01
abhishekk#chair jokke_14:01
openstackCurrent chairs: abhishekk jokke_14:01
abhishekkjokke_, thank you14:01
jokke_np14:01
abhishekk#topic Updates14:02
*** openstack changes topic to "Updates (Meeting topic: glance)"14:02
abhishekkAs discussed in last week, we will not have meeting next week on 26 December14:02
abhishekkUssuri milestone patch is up and updated, kindly review14:02
abhishekk#link https://review.opendev.org/#/c/696017/14:03
abhishekk#topic release/periodic jobs update14:03
*** openstack changes topic to "release/periodic jobs update (Meeting topic: glance)"14:03
abhishekkperiodic job is all green14:03
abhishekkwe are going to release M-1 for glance tomorrow14:04
jokke_so based on the agenda I assume we did not release U1 milestone14:04
abhishekkhave couple of suggestions/questions around the same14:04
jokke_releasing Friday is now a thing? :o14:04
*** wuchunyang has quit IRC14:04
abhishekkshould we include policy in code patch in M1?14:05
abhishekkjokke_, no that is not the case14:05
abhishekk#link https://review.opendev.org/69312914:06
abhishekkI should have asked this earlier but I was busy and it slept out of my min14:06
abhishekks/min/mind14:06
abhishekkapart from this, is there need to include empty alembic scripts?14:07
*** yamamoto has joined #openstack-meeting-414:08
abhishekkany suggestions or I got disconnected from here :O14:08
abhishekkjokke_, rosmaita ?14:09
jokke_just thinking, I can't remember if they were needed for the version bump or not14:09
*** gcheresh_ has quit IRC14:10
rosmaitai don't remember, but some tests will fail if some constants aren't updated14:10
abhishekkjokke_, I don't think so14:10
rosmaitawe have some tests in tests/gate i think that will indicate what needs to be kept in sync14:10
abhishekkrosmaita, I guess we have some release where we didn't have any script for that entire cycle14:10
jokke_yeah, that's the part I can't remember if those constants needed the empty migrations or not14:11
jokke_or if it broke trying to get the migrations (even empty) in before tagging the first on the series14:11
jokke_I think it was the later, we need tag first before we can merge any migrations14:11
abhishekksafe side we should add empty migration scripts14:12
*** wuchunyang has joined #openstack-meeting-414:12
jokke_you can try, but I think it will fail the gate before tag14:12
abhishekkok, lets tag first then14:13
abhishekkshould we include policy in code patch as it is in good shape and resolved all the concerns?14:13
jokke_I think we need empty migrations only if we're merging partials14:13
rosmaitai think that is correct14:13
abhishekkok14:14
abhishekkSo I need to regenerate config files, and then tag the release14:15
jokke_yeah, so if we want to include the policy, we should merge all the policy changes and include the example file with the example configs14:16
abhishekkIMO we should get that in14:17
*** wuchunyang has quit IRC14:17
abhishekkthere will be now example policy file I guess14:17
jokke_there is generator config in the policy change14:18
jokke_then there is:14:18
jokke_#link https://review.opendev.org/#/c/698793/14:18
abhishekk(my laptop is dying quickly, will sustain next 10-12 minutes)14:18
jokke_and14:18
jokke_#link https://review.opendev.org/#/c/694387/14:19
rosmaitai just -1d https://review.opendev.org/#/c/69312914:19
jokke_abhishekk: ok, go ahead ... we can try to keep speed up to cover as much as possible while you're still online14:19
abhishekkOk, lets leave it for M2 then we will release with current status14:20
abhishekkWill submit config regenerator patch if possible today14:20
abhishekkand also tag the release as well14:20
abhishekkMoving ahead,14:20
abhishekk#topic Multiple store import plugins14:21
*** openstack changes topic to "Multiple store import plugins (Meeting topic: glance)"14:21
abhishekkmultiple import specs14:21
abhishekk#link https://review.opendev.org/66920114:21
abhishekkyebinama, sorry in last minute I have added one suggestion there14:21
abhishekkdo you have any questions around the same?14:22
yebinamaYep, I've seen it :)14:22
yebinamaNo, this one should be quite easy14:22
yebinamaI'm more "worried" by rosmaita's review14:22
abhishekkhe is here14:22
abhishekk:d14:23
*** tosky_ has joined #openstack-meeting-414:23
*** tosky is now known as Guest2789014:23
*** tosky_ is now known as tosky14:23
*** enriquetaso has joined #openstack-meeting-414:23
yebinamaHe proposed to change allow_failure14:23
*** yamamoto has quit IRC14:24
abhishekkyes I saw that14:24
yebinamato all_stores_must_succeed14:24
yebinamaAre everyone ok with that?14:24
yebinamaI think it'as a good idea14:24
abhishekkif you rename it then you need to reverse all your current logic14:24
rosmaita\o/14:25
abhishekkI am ok with it14:25
yebinamaYes that's why I prefer to be sure everyone agrees before doing it14:25
rosmaitait's good to check, becasue we will have to live with it for a long time14:25
abhishekk+114:25
abhishekkit is meaningful as well14:26
*** Guest27890 has quit IRC14:26
jokke_Is that clear enough, or will we need longer novel next when we figure out corner case for it?14:26
rosmaitayou'd think jokke_ was being charged by the character14:27
jokke_I think there is 2 things here: 1) How the API operates and 2) how it's documented14:27
rosmaitawell, the problem is that allow_failure isn't attached to the "stores" element in the json14:28
jokke_and then we can bikeshed how much we want about the color of the option, it win't change the fact that world will find dumb enough user for us who manages to misunderstand it :P14:28
rosmaitaso if you want to do "stores": {[s1, s2], "allow_failure": true} then i am ok14:28
*** links has quit IRC14:29
rosmaitai think this is where i bring up sean's example of we're not talking about the color of the bikeshed, just whether we build it next to the house or in the middle of the driveway14:30
abhishekkI think we should rename it instead of adding one more layer of dict in the body14:31
yebinamaOr maybe we can just ensure to have a clear documentation?14:31
abhishekkIt is a good suggestion and as the work is still in progress we should do it now14:32
rosmaitanobody reads the documentation :)14:32
abhishekk:D still we need to have clear documentation as well14:33
rosmaitaagreed14:33
abhishekk(last 5 minutes)14:33
jokke_yebinama: what rosmaita said as well. So It really doesn't matter. We could call it F=True and no-one would pay any attention to it anyways :P14:33
yebinamaSo why bother with it? :p14:34
rosmaitathe json is supposed to be self-documenting14:34
rosmaitaallow_failure is too vague14:34
yebinamaMaybe we can go with allow_upload_failures?14:34
yebinamaTo not change the logic14:34
rosmaitaexcept it's not upload, it's import14:34
jokke_lets take this offline and keep going as long as we have abhishekk with us14:34
jokke_rosmaita: well it's upload failure during import :P14:35
rosmaitai guess the thing i really want to know is how the extra properties will be handled14:35
yebinamayes It's the other thing I wanted to discuss14:35
abhishekkrosmaita, I guess you are ok with copy existing image specs14:35
rosmaitayes, just this same issue about the exrta properties14:36
abhishekkyou guys can continue discussion, I will go through logs later14:36
rosmaitahappy holidays, abhishekk!14:36
abhishekkjust one minute remaining14:36
abhishekkrosmaita, thanks14:36
jokke_rosmaita: so when I proposed those properties, it was never meant to be to use on any level of control (thus I said we should just use the normal properties to indicate the status)14:37
abhishekkjokke_, yebinama thank you14:37
yebinamathanks abhishekk, bye14:37
abhishekkI will propose config generator patch if electricity is restored14:37
*** abhishekk has quit IRC14:37
smcginnisGood luck!14:37
jokke_rosmaita: whole point was to have some messaging going to the user what's happening that the user can easily clear themselves14:37
yebinamaAren't notifications enough?14:38
rosmaitanotifications aren't necessarily exposed to end users14:38
jokke_yebinama: no-one has any mechanism to follow up notifications14:38
yebinamaI have one :p14:38
jokke_I don't think any deployers lets users to tap into even notification queues of their rabbit14:38
yebinamaGoing through the code, I found that there is a status for each location of the image14:39
yebinamaBut It is only set to "active"14:39
jokke_yebinama: so you guys let your normal users to consume notifications? nice14:39
rosmaitajokke_: that's fine, i just wanted to make sure that we aren't relying on the content of the properties, since  auser can monkey with it14:39
rosmaitaalso, whether we are going to leave them there or delete them or what14:40
yebinamajokke: we send it to another public rabbit where users can subscribe14:40
jokke_rosmaita: yeah, absolutely not, just something the user can monitor and either clear themselves or wil be reset when next task runs agains that image14:40
jokke_yebinama: oh, cool14:40
yebinamaCould we use the status of the locations?14:40
jokke_rosmaita: I think it was in the spec, that they are to be cleared if new task is ran14:40
yebinamajokke_: exact14:41
jokke_yebinama: again, users should not have access to the locations ... bad for security14:41
rosmaitayes, but cleared meaning "set to None" or deleted14:41
jokke_yebinama: we have big hairy OSSN about that :P14:42
jokke_rosmaita: so my take is, we clear&reuse if needed, we allow user to clear (or do what they want with them) and other than that we just leave them. As how would we determine when it's right time to clear them automatically14:43
jokke_rosmaita: so rather just leave and let user to clear if they wish14:43
rosmaitawell, the stores_to_be_processed is no longer needed when its empty14:44
jokke_rosmaita: and once all has succeeded, they will be cleared14:44
rosmaitasame deal with empty failures14:44
jokke_yes, exactly14:44
yebinamaproperties have to be string?14:45
rosmaitayes, these do14:45
jokke_so if the queue indicator and he failure indicator exists everything wen't great, if failure exists after queue does, we're done with some issues14:45
yebinamarosmaita: ok. So we have to create a string with comma delimiter14:45
jokke_if those two doesn't exist I was supposed to say14:45
rosmaitawell, like i said on the spec, i kind of like this idea ... the other option would be a "message" element on the image, we had talked about that a while back, but i think this may be better14:46
jokke_rosmaita: I got quite fond of this after thinking of it. self explanary, easy to manage and user clearable.14:47
rosmaitaright, and doesn't pollute the images table14:48
jokke_And indeed would give that little indication to the user we have been talking for about as long as those async ops have existed14:48
rosmaitaright, so the issue is how to handle these in teh image schema14:48
rosmaitaor not at all14:48
jokke_I think easiest not at all, like with any other custom property14:49
rosmaitaok14:50
jokke_let user to clear them and show them if needed ... I think we don't have schema option for RD anyways14:50
jokke_which would have been the optimal14:50
jokke_ok, then there's the extension for this spec which is abhishekk's copy job spec14:51
jokke_#link https://review.opendev.org/69472414:51
rosmaitaok, cool, you've answered my questions.  key thing was, are these normal custom properties? answer is yes, and are we using them for control? answer is no14:51
jokke_rosmaita: correct14:51
rosmaitagreat, i left a comment on the copy spec, would like him to mention using these properties again14:52
*** dosaboy has joined #openstack-meeting-414:52
rosmaitabecause at least with import, there's an image status transition that indicates something happened14:53
rosmaitawith the copy, there won't be14:53
jokke_sure technically and operationally he doesn't have choice so I didn't get tangled to that, but doesn't hurt there either14:53
jokke_rosmaita: yeah, that's where the queue property specially will be big thing to actually know the task started at least14:53
rosmaitaexactly14:54
rosmaitaanyway, i like using the custom properties -- i would have gone with a "message" which would have been more complicated and not any better14:55
rosmaitaso kudos to whoever thought of that14:55
jokke_rosmaita: and you're ok with it being import method rather than needing to mingle full dedicated entry point for it and all the filtering needed?14:55
rosmaitawell ...14:56
jokke_cheers, yeah that was my lil brain getting that blink of light for a change :D14:56
jokke_btw we have 4 min14:56
rosmaitai'm ok with it, don't love it, but then i'm not doing the implementation14:56
rosmaitaand i think the api WG is out of business14:57
jokke_rosmaita: I hear you and I did share your concern when we initially talked about this. It just makes life so much easier to treat it as import job than duplicate all the piping to have it's own thing14:57
rosmaitayeah, i think keep it simple for now14:58
jokke_and we can always mask it in the client if we wish14:58
rosmaitaall that stuff may need to be refactored to a separate service at some point, so we can deal with it in v314:58
jokke_yeah, I leave to who ever is designing v3 after I'm dead :P14:59
jokke_#topic Open Discussion14:59
*** openstack changes topic to "Open Discussion (Meeting topic: glance)"14:59
jokke_ok, last minute14:59
jokke_#link https://review.opendev.org/#/c/698018/14:59
jokke_selfish plug, the delete image from a store spec, the code is ready for glance and client15:00
jokke_and we're out of time.15:00
rosmaitaok, will put it on my list15:00
jokke_Thanks all!15:00
yebinamabye15:00
jokke_#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Thu Dec 19 15:00:39 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-12-19-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-12-19-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-12-19-14.00.log.html15:00
*** yebinama has quit IRC15:01
*** rosmaita has left #openstack-meeting-415:01
*** wuchunyang has joined #openstack-meeting-415:06
*** wuchunyang has quit IRC15:12
*** wuchunyang has joined #openstack-meeting-415:14
*** wuchunyang has quit IRC15:24
*** k_mouza has quit IRC15:29
*** k_mouza has joined #openstack-meeting-415:29
*** k_mouza_ has joined #openstack-meeting-415:31
*** k_mouza has quit IRC15:34
*** gcheresh_ has joined #openstack-meeting-415:34
*** salmankhan has joined #openstack-meeting-415:36
*** yamamoto has joined #openstack-meeting-415:42
*** yamamoto has quit IRC15:50
*** wuchunyang has joined #openstack-meeting-416:22
*** wuchunyang has quit IRC16:27
*** lpetrut has quit IRC16:28
*** wuchunyang has joined #openstack-meeting-416:30
*** wuchunyang has quit IRC16:40
*** icey has quit IRC16:47
*** dosaboy_ has joined #openstack-meeting-416:52
*** dave-mccowan has joined #openstack-meeting-416:58
*** dave-mccowan has quit IRC17:05
*** k_mouza_ has quit IRC17:15
*** k_mouza has joined #openstack-meeting-417:20
*** wuchunyang has joined #openstack-meeting-417:21
*** wuchunyang has quit IRC17:28
*** wuchunyang has joined #openstack-meeting-417:29
*** k_mouza has quit IRC17:31
*** wuchunyang has quit IRC17:33
*** wuchunyang has joined #openstack-meeting-417:36
*** wuchunyang has quit IRC17:41
*** wuchunyang has joined #openstack-meeting-417:47
*** icey has joined #openstack-meeting-417:48
*** lpetrut has joined #openstack-meeting-417:49
*** wuchunyang has quit IRC17:55
*** bobmel has quit IRC17:57
*** wuchunyang has joined #openstack-meeting-418:01
*** e0ne has quit IRC18:03
*** ralonsoh has quit IRC18:04
*** wuchunyang has quit IRC18:06
*** dosaboy_ has quit IRC18:13
*** dosaboy has quit IRC18:13
*** dosaboy has joined #openstack-meeting-418:14
*** bh526r has quit IRC18:15
*** lvbin02 has joined #openstack-meeting-418:22
*** lvbin01 has quit IRC18:25
*** lvbin02 is now known as lvbin0118:25
*** lpetrut has quit IRC18:26
*** wuchunyang has joined #openstack-meeting-418:28
*** wuchunyang has quit IRC18:33
*** lpetrut has joined #openstack-meeting-418:37
*** k_mouza has joined #openstack-meeting-418:43
*** k_mouza has quit IRC18:48
*** enriquetaso has quit IRC18:50
*** enriquetaso has joined #openstack-meeting-418:51
*** wuchunyang has joined #openstack-meeting-419:01
*** wuchunyang has quit IRC19:05
*** wuchunyang has joined #openstack-meeting-419:12
*** wuchunyang has quit IRC19:16
*** psachin has quit IRC19:28
*** itxaka has quit IRC19:44
*** spotz has quit IRC19:44
*** wuchunyang has joined #openstack-meeting-419:54
*** e0ne has joined #openstack-meeting-419:55
*** wuchunyang has quit IRC20:00
*** e0ne has quit IRC20:00
*** irclogbot_1 has quit IRC20:06
*** wuchunyang has joined #openstack-meeting-420:07
*** irclogbot_3 has joined #openstack-meeting-420:09
*** wuchunyang has quit IRC20:12
*** wuchunyang has joined #openstack-meeting-420:13
*** enriquetaso has quit IRC20:16
*** wuchunyang has quit IRC20:18
*** enriquetaso has joined #openstack-meeting-420:31
*** pmesserli has joined #openstack-meeting-420:34
*** wuchunyang has joined #openstack-meeting-420:52
*** wuchunyang has quit IRC20:57
*** wuchunyang has joined #openstack-meeting-421:00
*** gcheresh_ has quit IRC21:00
*** wuchunyang has quit IRC21:13
*** wuchunyang has joined #openstack-meeting-421:14
*** wuchunyang has quit IRC21:18
*** enriquetaso has quit IRC21:20
*** pcaruana has quit IRC21:23
*** wuchunyang has joined #openstack-meeting-421:24
*** wuchunyang has quit IRC21:29
*** wuchunyang has joined #openstack-meeting-421:34
*** gcheresh_ has joined #openstack-meeting-421:36
*** e0ne has joined #openstack-meeting-421:42
*** wuchunyang has quit IRC21:43
*** wuchunyang has joined #openstack-meeting-421:47
*** yamamoto has joined #openstack-meeting-421:49
*** wuchunyang has quit IRC21:51
*** wuchunyang has joined #openstack-meeting-421:53
*** gcheresh_ has quit IRC21:54
*** yamamoto has quit IRC21:54
*** wuchunyang has quit IRC22:00
*** wuchunyang has joined #openstack-meeting-422:03
*** e0ne has quit IRC22:07
*** wuchunyang has quit IRC22:08
*** salmankhan has quit IRC22:08
*** wuchunyang has joined #openstack-meeting-422:13
*** wuchunyang has quit IRC22:18
*** wuchunyang has joined #openstack-meeting-422:36
*** wuchunyang has quit IRC22:40
*** wuchunyang has joined #openstack-meeting-422:45
*** tosky has left #openstack-meeting-422:47
*** wuchunyang has quit IRC22:49
*** slaweq has quit IRC22:51
*** wuchunyang has joined #openstack-meeting-422:56
*** wuchunyang has quit IRC23:01
*** Liang__ has joined #openstack-meeting-423:08
*** bnemec has quit IRC23:24
*** bnemec has joined #openstack-meeting-423:24
*** wuchunyang has joined #openstack-meeting-423:25
*** wuchunyang has quit IRC23:29
*** wuchunyang has joined #openstack-meeting-423:32
*** wuchunyang has quit IRC23:37
*** wuchunyang has joined #openstack-meeting-423:46
*** wuchunyang has quit IRC23:53
*** wuchunyang has joined #openstack-meeting-423:55
*** yamamoto has joined #openstack-meeting-423:55
*** wuchunyang has quit IRC23:59

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