Thursday, 2019-03-14

*** slaweq has joined #openstack-meeting-400:11
*** slaweq has quit IRC00:15
*** Dantalion has quit IRC00:22
*** salmankhan has quit IRC00:23
*** igordc has quit IRC00:24
*** igordc has joined #openstack-meeting-400:25
*** dklyle has quit IRC00:31
*** dklyle has joined #openstack-meeting-400:31
*** igordc has quit IRC00:31
*** dklyle has quit IRC00:46
*** igordc has joined #openstack-meeting-400:58
*** liuyulong has joined #openstack-meeting-401:10
*** slaweq has joined #openstack-meeting-401:11
*** slaweq has quit IRC01:16
*** iyamahat has quit IRC01:26
*** cheng1 has joined #openstack-meeting-401:39
*** cheng1 has quit IRC01:52
*** cheng1 has joined #openstack-meeting-401:59
*** yamahata has joined #openstack-meeting-402:02
*** hongbin has joined #openstack-meeting-402:15
*** cheng1 has quit IRC02:46
*** cheng1 has joined #openstack-meeting-402:47
*** dave-mccowan has joined #openstack-meeting-402:50
*** dave-mccowan has quit IRC02:54
*** roman_g has quit IRC02:59
*** yamamoto has joined #openstack-meeting-403:00
*** psachin has joined #openstack-meeting-403:01
*** slaweq has joined #openstack-meeting-403:11
*** slaweq has quit IRC03:15
*** hongbin has quit IRC03:36
*** diablo_rojo has quit IRC03:47
*** yamamoto has quit IRC04:03
*** slaweq has joined #openstack-meeting-404:11
*** cheng1 has quit IRC04:12
*** slaweq has quit IRC04:15
*** janki has joined #openstack-meeting-404:35
*** yamamoto has joined #openstack-meeting-404:46
*** cheng1 has joined #openstack-meeting-404:50
*** lpetrut has joined #openstack-meeting-404:55
*** lpetrut has quit IRC05:19
*** iyamahat has joined #openstack-meeting-405:48
*** cheng1 has quit IRC05:50
*** slaweq has joined #openstack-meeting-406:11
*** gcheresh has joined #openstack-meeting-406:15
*** slaweq has quit IRC06:16
*** slaweq has joined #openstack-meeting-406:19
*** igordc has quit IRC06:26
*** witek has joined #openstack-meeting-406:43
*** Luzi has joined #openstack-meeting-406:46
*** witek has quit IRC06:47
*** gcheresh has quit IRC06:52
*** yamamoto has quit IRC06:55
*** yamamoto has joined #openstack-meeting-407:03
*** yamamoto has quit IRC07:04
*** lpetrut has joined #openstack-meeting-407:07
*** yamamoto has joined #openstack-meeting-407:14
*** gcheresh has joined #openstack-meeting-407:17
*** markvoelker has quit IRC07:19
*** witek has joined #openstack-meeting-407:30
*** lpetrut has quit IRC07:35
*** lpetrut has joined #openstack-meeting-407:42
*** e0ne has joined #openstack-meeting-407:45
*** gkadam_ has joined #openstack-meeting-407:50
*** Dantalion has joined #openstack-meeting-407:56
*** pcaruana has joined #openstack-meeting-408:07
*** pcaruana has quit IRC08:11
*** pcaruana has joined #openstack-meeting-408:23
*** witek has quit IRC08:33
*** slaweq has quit IRC08:53
*** slaweq has joined #openstack-meeting-408:55
*** k_mouza has joined #openstack-meeting-409:17
*** e0ne has quit IRC09:43
*** e0ne has joined #openstack-meeting-409:46
*** pcaruana has quit IRC09:48
*** cheng1 has joined #openstack-meeting-410:50
*** k_mouza has quit IRC10:52
*** k_mouza has joined #openstack-meeting-410:53
*** liuyulong has quit IRC10:54
*** pcaruana has joined #openstack-meeting-411:32
*** roman_g has joined #openstack-meeting-411:44
*** dave-mccowan has joined #openstack-meeting-411:46
*** cheng1 has quit IRC11:53
*** cheng1 has joined #openstack-meeting-411:54
*** seajay has joined #openstack-meeting-411:57
*** yamamoto has quit IRC12:13
*** yamamoto has joined #openstack-meeting-412:17
*** yamamoto has quit IRC12:17
*** yamamoto has joined #openstack-meeting-412:18
*** yamamoto has quit IRC12:22
*** cheng1 has quit IRC12:25
*** yamamoto has joined #openstack-meeting-412:29
*** yamamoto has quit IRC12:30
*** yamamoto has joined #openstack-meeting-412:30
*** e0ne has quit IRC12:31
*** ktibi has joined #openstack-meeting-412:58
*** jchhatbar has joined #openstack-meeting-413:00
*** janki has quit IRC13:00
*** dklyle has joined #openstack-meeting-413:01
*** ktibi has quit IRC13:07
*** ktibi has joined #openstack-meeting-413:07
*** jchhatbar has quit IRC13:10
*** janki has joined #openstack-meeting-413:10
*** howell has joined #openstack-meeting-413:11
*** yamamoto has quit IRC13:17
*** yamamoto has joined #openstack-meeting-413:20
*** yamamoto has quit IRC13:20
*** yamamoto has joined #openstack-meeting-413:21
*** yamamoto has quit IRC13:25
*** ktibi has quit IRC13:30
*** e0ne has joined #openstack-meeting-413:32
*** abhishekk has joined #openstack-meeting-413:36
*** mjturek has joined #openstack-meeting-413:37
*** mjturek has quit IRC13:38
*** yamamoto has joined #openstack-meeting-413:39
*** yamamoto has quit IRC13:39
*** yamamoto has joined #openstack-meeting-413:40
*** ktibi has joined #openstack-meeting-413:42
*** yamamoto has quit IRC13:44
*** mjturek has joined #openstack-meeting-413:46
*** rosmaita has joined #openstack-meeting-413:48
*** janki has quit IRC13:58
jokke_#startmeeting glance14:00
openstackMeeting started Thu Mar 14 14:00:25 2019 UTC and is due to finish in 60 minutes.  The chair is jokke_. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: glance)"14:00
openstackThe meeting name has been set to 'glance'14:00
jokke_#topic roll-call14:00
*** openstack changes topic to "roll-call (Meeting topic: glance)"14:00
jokke_o/14:00
jokke_#link https://etherpad.openstack.org/p/glance-team-meeting-agenda14:00
rosmaitao/14:01
abhishekko/14:01
lpetruto/14:02
jokke_hey all14:02
jokke_#topic updates14:03
*** openstack changes topic to "updates (Meeting topic: glance)"14:03
jokke_Soo we're on FF after the extended merge them features now we agreed last week.14:03
abhishekk#link https://etherpad.openstack.org/p/glance-stein-milestone-314:04
abhishekkcurrent status ^^14:04
jokke_I think lpetrut's work on the Windows compatibility is the last thing that is not purely bugfix we will consider14:04
abhishekkyes14:04
jokke_I don't think we have any FFE requests on anything else. We have some bugfixes pending but in general we're looking pretty good14:05
abhishekkalso do we need FF for visibility?14:05
rosmaitawas just going to ask14:05
rosmaitathat may need to be postponed to train14:05
jokke_We need to drop Tempest gating for that14:05
abhishekkagree14:05
lpetrutthanks a lot for your help on this. some updates on this matter: we're almost done with the CI14:05
abhishekkcool14:06
jokke_Which is yet again topic on my PTG list.14:06
rosmaitai will help with that, we need a strategy14:06
jokke_But lets move on and we can discuss the more pressing current matters under their slots14:07
jokke_#topic release updates14:07
*** openstack changes topic to "release updates (Meeting topic: glance)"14:07
abhishekkWe need to release glance milestone 3 today as agreed in last week14:07
jokke_Client got release last week on time and we did not release the milestone 314:07
abhishekkpython-glanceclient  --> Version 2.16.0 released last week14:08
rosmaita\o/14:08
abhishekkfor milestone 3, we need releasenotes patch, then need to regenerate sample config, and release patch14:09
jokke_I think the big question is do we have something we need the milestone 3 tag for?14:09
jokke_RC1 is next week14:09
jokke_tags are cheap, I'm not saying we definitely should not do that, but do we have any benefit for tagging it?14:10
abhishekkis it possible that we can release RC1 direct?14:10
rosmaitathat's a question for sean, but i believe we can14:10
jokke_abhishekk: yes, as of this cycle forward there is no need to tag milestones14:10
jokke_only reason we did need the milestone tagging was for the db migrations to work14:11
abhishekkcool, then I guess apart from cache-manage utility we don't have any major feature in this release14:11
jokke_As of release model, the Integrated release with milestones changed to kind of Integrated release with possible milestones14:11
abhishekkyeah, then we need to submit the patch to open the migration for Train release14:12
jokke_yes, that will be around Train-114:12
abhishekkack14:12
rosmaitaor when that test breaks the gate14:13
rosmaitawhich i forget what exactly it looks for14:13
jokke_or that ^^ ;D14:13
abhishekk:D14:13
jokke_I think we did merge the instructions into the release liaison document14:13
abhishekkjokke_, it was already there14:14
jokke_but it definitely should not blow up this week so lets move on unless there is something else about releases?14:14
jokke_Ohh, how are the periodical gates looking? Still just sporadical timeouts?14:14
abhishekkyes, 6 failures in last week14:15
abhishekkall are timeouts14:15
abhishekkI have added this topic in PTG discussion etherpad14:15
jokke_hmm-m that's like double what we had week before iirc14:15
jokke_sounds like the gate load plays a role in there as well14:15
abhishekkwe might opt help from infra guys?14:15
abhishekkthat's it from release updates topic14:16
abhishekkare we going to tag m3 today or RC1 directly14:16
jokke_I think it's at least worth of discussing. We definitely have the data to show now when we have had stable situation for a while14:16
abhishekkright14:17
jokke_Like said I don't mind either way. Does anyone have any compelling arguments for or against tagging m-3?14:17
jokke_I guess not. Lets skip it and focus to get good RC1 out next week then!14:18
abhishekksorry to say, suddenly there are 8-10 failures for periodic jobs14:18
abhishekkfunctional-py35 create: /home/zuul/src/git.openstack.org/openstack/glance/.tox/functional-py3514:18
abhishekkERROR: InterpreterNotFound: python3.514:18
abhishekk___________________________________ summary ____________________________________14:18
abhishekkERROR:  functional-py35: InterpreterNotFound: python3.514:18
jokke_^^ looks definitely like Infra issue14:19
rosmaitathey changed some images or something recently14:19
abhishekk#link http://zuul.openstack.org/builds?pipeline=periodic&project=openstack%2Fglance14:19
abhishekkyes14:19
jokke_thanks abhishekk14:19
rosmaitathierry said something about it on the ML, though not that exact issue14:19
rosmaitaforget that, it was a gpg key issue14:20
jokke_ok, moving on14:20
jokke_#topic feature Freeze14:20
*** openstack changes topic to "feature Freeze (Meeting topic: glance)"14:20
jokke_So we have those couple of patches lpetrut had to rebase there still hanging14:21
jokke_How is it looking ot get those reviewed?14:21
lpetrutthose have entered the gate14:21
abhishekkone patch needs to be reviewed where he has added time.sleep in tests14:22
abhishekk#link https://review.openstack.org/#/c/643336/114:22
lpetrutyep, I've marked that as WIP as there's still one case that I'll need to fix14:22
lpetrutso this got me wondering, did you have such problems before? I mean, due to the timestamps14:22
abhishekkAFAIK, never14:23
jokke_lpetrut: I can't recall at least. The good thing about that patch is that it's touching tests only14:23
rosmaitano, usually the functional tests are slow enough14:23
lpetrutinteresting, good to know14:23
rosmaitawhat i mean is, we haven't had to worry about instantaneous updates in the functional tests14:23
jokke_^^14:24
lpetrutyeah, I'm not sure if it's just very fast or the clock is inaccurate :)14:24
jokke_At this point we need to put full focus on nailing the bugs down. Stuff like the test hardenings are great for this time of the cycle14:25
lpetrutand sorry to ask, but do gate tests run on bare metal?14:25
jokke_Shall we have bug smash around the weekend, Monday maybe?14:25
rosmaitalpetrut: i don't think the tests run on bare metal14:25
jokke_lpetrut: no they mostly don't14:26
rosmaitathough, maybe occasionally14:26
rosmaitai think in general they are running on "donated" VMs14:26
abhishekkyes14:26
jokke_there is some baremetal testing but like rosmaita said mainly zuul respins VMs14:26
lpetrutgot it, thanks14:27
jokke_abhishekk: was your yes for lpetrut or bug smash? Sorry I mixed up the discussion here a bit14:27
abhishekkbug smash14:27
jokke_cool. And I hope you're feeling better14:28
rosmaitaquick question about lpetrut: how do we feel about the sleeps? just let them through?14:28
abhishekkyes, better and better14:28
rosmaitathey are very small sleeps14:28
lpetrutI thought that a few ms should be negligeable. mocking complicate the code and cause other issues14:28
lpetrutI can make them optional (e.g. have a separate method for that, something like .add_delay)14:29
rosmaitai agree, don't want to mock too much stuff in functional tests14:29
rosmaitamaybe let's just leave them in so we can get the rest merged and people can start testing it14:29
rosmaitado the optimizations as a followup patch14:29
jokke_As long as the delays are not in a places where we would expect catching real issues like race conditions I'm fine having them in tests14:29
rosmaitawell, they are db updates, so race condition city14:30
jokke_ok, lets review them carefully and see if we should perhaps make sure the test reflects real life scenario enough.14:31
abhishekkok14:31
jokke_if it's testing issue I'm fine with delaying them, if it's something we should fix to make sure it's atomic change, lets fix it :D14:32
abhishekkDo lpetrut need to send FFE mail as per standard?14:32
jokke_abhishekk: like said earlier these are testing hardening/bug fixing. Perfect for this time. I don't see new features introduced here14:32
abhishekkcool14:33
rosmaitayeah, but we need these test fixes for the other stuff to merge, right?14:33
jokke_rosmaita: I think they are not prerequisite for the stuff gating atm. but for the windows ci to run14:33
jokke_lpetrut: correct me if I'm wrong14:34
jokke_ok, moving on14:35
rosmaitain that case, it would be cool if lpetrut did the optimization of only sleeping if running on windows14:35
jokke_#topic py3 glance_store issue14:35
*** openstack changes topic to "py3 glance_store issue (Meeting topic: glance)"14:35
jokke_rosmaita: this was yours14:35
rosmaita#link https://review.openstack.org/#/c/620234/14:36
abhishekkrosmaita, I will try to have a look at test patch today (or may be tomorrow)14:36
rosmaitaabhishekk: don't i have another idea on that14:36
abhishekkgreat14:36
rosmaitai will be changing the patch a bit, had an idea while at the dentist this morning14:36
abhishekk:D14:37
rosmaitaanyway, i just want to push the above14:37
jokke_rosmaita: ok what you had in mind?14:37
rosmaitawell, mainly i need two +2s14:37
rosmaita:)14:37
rosmaitaor need to find out that this is unacceptable14:37
rosmaitai would like to close this out ASAP14:38
*** lpetrut has quit IRC14:38
jokke_Just bit of a background. We had discussion with rosmaita about this patch and what Tim said about monitoring the result returned from that read14:38
*** lpetrut has joined #openstack-meeting-414:39
rosmaitayeah, the basic idea is that i want to keep this patch as small as possible, that is, don't want it to mask any other problems14:39
jokke_So Tim's proposal was instead of faking the zero read to check every response we get from the reads and if it's anything but actual data coming in, replacing it14:39
lpetrutsuch a bad time to run out of battery :) without 634007, we cannot run the tests on Widndows (currently in the gate), while 643336 fixes unit tests. sorry for going off topic14:39
jokke_and that's exctly why we came to the conclusion that faking the zero read instead of replacing something that executed code returns to us would be the better way to go14:40
jokke_That way we will catch possible future issues while we try to find out what is the actual root cause14:41
rosmaitayes, so we just need sean or abhishek to agree with jokke_14:41
abhishekkyes makes sense to me14:41
rosmaitain the meantime, i am trying to get functional tests that catch this14:41
jokke_and we left the bug open, so the commit message is pointing to related-bug not closes-bug14:42
abhishekkand the note added by rosmaita helps better to understand it14:42
jokke_so we have reminder that we actually need to figure out what's crapping us in the first place. This change will just fix this specific issue so we can release and indeed work with py314:43
rosmaitai'll add some comments to the bug14:43
jokke_great, I think this is beaten, lets move on14:43
abhishekkgreat14:43
jokke_#topic data remains in staging14:44
*** openstack changes topic to "data remains in staging (Meeting topic: glance)"14:44
jokke_abhishekk: this is something you've been working on14:44
*** dangtrinhnt_x has joined #openstack-meeting-414:44
abhishekkjokke_, yes14:44
rosmaitai put it on the agenda for abhishekk14:44
rosmaitai want to make sure we are all ok with the way the problem is handled14:44
jokke_And I think rosmaita pointed out very well that the staging should not be relying deployment store enablements14:44
rosmaitai think it's fine14:44
abhishekkyesterday Me and rosmaita had a discussion about how to fix this14:44
rosmaitaand we will be refactoring this for Train14:44
jokke_ok14:45
abhishekk++14:45
rosmaitabut this fix i think needs to go back to rocky14:45
jokke_so we go as it is for now and keep it in the agenda of PTG discussions how we do this finally?14:45
abhishekkI have tested this for single store and multiple store and it is working14:45
rosmaitaso i do have a question for abhishek, though14:45
abhishekkplease shoot14:45
rosmaitayou found in testing that using _build_store() to create the store to delete from modified teh "real" store14:46
rosmaitabut why does it work in the api in the /stage call?14:46
abhishekkjust give me a minute14:47
rosmaitasure, or we can discuss later14:47
rosmaitajust wanted to determine whether we need to change the code in /stage also for now14:47
rosmaitai don't think so14:47
rosmaitabut it is kind of weird, i am missing something14:47
jokke_The staging code at least used to work in a way that it created new store object, owerwrote the config on that, so the config change stayed local on that object14:48
rosmaitaright14:48
abhishekkin staging code we are creating file store instance and calling add method of file store directly14:48
jokke_it is worst kind of black magic wizardry you can do in OOP14:49
jokke_abhishekk: and I think that was rosmaita's point on the comment, we should do the same on the cleanup. Just create the object with overwritten config and call it's delete directly14:50
abhishekkto call delete method of filestore we need to pass location object to delete method14:50
jokke_instead of relying the store library to figure out how to get to the path14:50
jokke_abhishekk: ohhh14:50
abhishekkand it is so weired to create a location object on the fly14:51
rosmaitathis is related, i think this will be a problem: https://github.com/openstack/glance/blob/master/glance/api/v2/image_data.py#L7614:51
jokke_so we would need to do even more hackstery to create that bloody object14:51
jokke_ok, then I agree. Lets keep this simple for now and do it properly in Train14:51
rosmaitai think get_location_from_uri requires the scheme to be "registered"14:51
abhishekkyes, so instead of that I have kept it simple14:51
rosmaitai think we need to do unlink that that _unstage function14:52
jokke_abhishekk: would you mind to write me an mail about this whole scenario and the reasons why it sucks? ;) I'd like to have this explained in known issues section of the release notes14:52
abhishekkrosmaita, right, and if I register it and if there is filestore in the 'stores' conf option then all images will be stored in staging area :D as it will override14:52
*** hrw has left #openstack-meeting-414:52
abhishekkjokke_, sure14:52
jokke_great14:53
*** dangtrinhnt_x has quit IRC14:53
jokke_ok, so lets stick with the current and explain in documentation.14:53
abhishekkI will draft a mail within a hour after the meeting14:53
jokke_this should get easier once we get to utilize those reserved stores on multistore for it14:54
abhishekkyes, way easy14:54
jokke_abhishekk: no rush, I need it like before the final release :D14:54
rosmaitaok, so i get it ... the problem is having to use the location for delete14:54
rosmaitahave i mentioned that i really hate image locations recently?14:55
abhishekk#MeToo14:55
abhishekk:D14:55
rosmaitameaning "recently mentioned" not "recently hated"14:55
jokke_rosmaita: and not only location, which we know, but the store delete expecting properly formed location object14:55
rosmaitai have hated them for a very long time14:55
jokke_yeah same14:55
rosmaitaok, so to summarize:14:55
rosmaitacreating the store in /stage is fine14:56
rosmaitaprobably a problem wiht the _unstage method in the image_data controller for the delete, though14:56
rosmaitain the task, abhishek's code is doing the right thing to just manually delete the stuff from teh staging area14:56
rosmaitathe end14:56
jokke_yeah 3 min for open discussion14:57
jokke_#topic open discussion14:57
*** openstack changes topic to "open discussion (Meeting topic: glance)"14:57
jokke_rosmaita: so just to clarify, the glance_store needs the store type to be enabled to be able to form the location object from the uri to pass to the delete ... in nutshell that's the current problem :D14:57
abhishekkcorrect14:58
rosmaitaright14:58
jokke_anything else?14:58
abhishekknope14:58
jokke_oh yeah14:58
abhishekkYou need to send mail for PTL candidacy14:59
jokke_#agreed Bug scrub day at Monday! Lets go through our open bugs and make sure we haven't missed anything critical14:59
rosmaitajokke_: what abhishekk said!!!14:59
abhishekkjust to update, I have submitted specs for nova and cinder to use multiple backned of glance14:59
jokke_abhishekk: I already submitted my candidacy to the elections repo ;)14:59
jokke_abhishekk: Amazing!14:59
abhishekkjokke_, great14:59
jokke_ok, time ... we can continue on #os-glance15:00
jokke_thanks all15:00
abhishekkthank you all15:00
jokke_#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Thu Mar 14 15:00:43 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-14-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-03-14-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2019/glance.2019-03-14-14.00.log.html15:00
*** roman_g has quit IRC15:04
*** rosmaita has left #openstack-meeting-415:05
*** roman_g has joined #openstack-meeting-415:06
*** roman_g_ has joined #openstack-meeting-415:07
*** roman_g has quit IRC15:11
*** lpetrut has quit IRC15:12
*** gcheresh has quit IRC15:28
*** hamzy has quit IRC15:43
*** yamamoto has joined #openstack-meeting-415:57
*** premsankar has joined #openstack-meeting-416:01
*** Luzi has quit IRC16:03
*** diablo_rojo has joined #openstack-meeting-416:05
*** gibi has quit IRC16:38
*** gibi has joined #openstack-meeting-416:38
*** e0ne has quit IRC16:38
*** gkadam_ has quit IRC16:50
*** ktibi has quit IRC16:53
*** abhishekk has quit IRC16:54
*** hongbin has joined #openstack-meeting-416:59
*** hamzy has joined #openstack-meeting-417:09
*** psachin has quit IRC17:21
*** k_mouza has quit IRC17:41
*** igordc has joined #openstack-meeting-417:45
*** e0ne has joined #openstack-meeting-417:46
*** iyamahat_ has joined #openstack-meeting-417:48
*** ktibi has joined #openstack-meeting-417:50
*** iyamahat has quit IRC17:50
*** ktibi has quit IRC17:55
*** k_mouza has joined #openstack-meeting-418:08
*** k_mouza has quit IRC18:13
*** iyamahat_ has quit IRC18:13
*** yamahata has quit IRC18:13
*** iyamahat has joined #openstack-meeting-418:29
*** e0ne has quit IRC18:33
*** notmyname has quit IRC18:38
*** roman_g_ has quit IRC18:39
*** notmyname has joined #openstack-meeting-418:39
*** e0ne has joined #openstack-meeting-418:40
*** gmann is now known as gmann_afk18:51
*** hamzy has quit IRC20:45
*** howell has quit IRC20:46
*** mjturek has quit IRC20:53
*** seajay has quit IRC22:12
*** pcaruana has quit IRC22:21
*** e0ne has quit IRC22:28
*** gmann_afk is now known as gmann22:40
*** pmesserli has quit IRC23:02
*** hongbin has quit IRC23:04
*** slaweq has quit IRC23:25
*** yamahata has joined #openstack-meeting-423:42
*** k_mouza has joined #openstack-meeting-423:46
*** k_mouza has quit IRC23:51

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