Tuesday, 2020-08-25

*** armax has quit IRC00:24
*** armax has joined #openstack-meeting00:50
*** rcernin has quit IRC01:14
*** rcernin has joined #openstack-meeting01:16
*** baojg has joined #openstack-meeting01:36
*** armax has quit IRC01:37
*** gyee has quit IRC01:48
*** masahito has joined #openstack-meeting01:52
*** johnthetubaguy has quit IRC02:26
*** andrebeltrami has quit IRC02:47
*** masahito has quit IRC03:12
*** rfolco has quit IRC03:13
*** rh-jelabarre has quit IRC03:16
*** jmasud has quit IRC03:31
*** masahito has joined #openstack-meeting04:07
*** ijw has quit IRC04:07
*** ijw has joined #openstack-meeting04:08
*** ijw has quit IRC04:10
*** ijw has joined #openstack-meeting04:10
*** psahoo has joined #openstack-meeting04:16
*** manpreet has joined #openstack-meeting04:18
*** psahoo has quit IRC04:29
*** rcernin has quit IRC04:32
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-meeting04:35
*** makoto-h has joined #openstack-meeting04:38
*** hongbin has quit IRC04:39
*** psahoo has joined #openstack-meeting04:47
*** yasufum has joined #openstack-meeting04:53
*** Lucas_Gray has joined #openstack-meeting05:03
*** jmasud has joined #openstack-meeting05:03
*** rcernin has joined #openstack-meeting05:04
*** psahoo has quit IRC05:11
*** yoshito-ito has joined #openstack-meeting05:22
*** psahoo has joined #openstack-meeting05:24
*** psahoo has quit IRC05:33
*** rcernin has quit IRC05:41
*** Lucas_Gray has quit IRC05:44
*** psahoo has joined #openstack-meeting05:50
*** yasufum has quit IRC05:50
*** vishalmanchanda has joined #openstack-meeting05:50
*** ricolin_ has joined #openstack-meeting06:04
*** ricolin_ has quit IRC06:11
*** moguimar has joined #openstack-meeting06:23
*** ralonsoh has joined #openstack-meeting06:28
*** ijw has quit IRC06:31
*** slaweq has joined #openstack-meeting06:35
*** masahito has quit IRC06:37
*** ijw has joined #openstack-meeting06:44
*** ijw has quit IRC06:49
*** suzhengwei has joined #openstack-meeting06:56
*** apetrich has joined #openstack-meeting06:56
*** rcernin has joined #openstack-meeting06:57
*** suzhengwei has quit IRC07:01
*** suzhengwei has joined #openstack-meeting07:02
*** rcernin has quit IRC07:03
*** rcernin has joined #openstack-meeting07:06
*** suzhengwei has quit IRC07:13
*** rcernin has quit IRC07:14
*** ijw has joined #openstack-meeting07:15
*** ijw has quit IRC07:20
*** tosky has joined #openstack-meeting07:36
*** dklyle has quit IRC07:36
*** e0ne has joined #openstack-meeting07:45
*** ijw has joined #openstack-meeting07:47
*** ijw has quit IRC07:52
*** masazumi-ota has joined #openstack-meeting07:53
*** baojg has quit IRC07:58
*** baojg has joined #openstack-meeting07:59
*** takahashi-tsc has joined #openstack-meeting07:59
takahashi-tscHi tacker team.08:00
takahashi-tscOK, let's start the meeting08:00
takahashi-tsc#startmeeting tacker08:00
openstackMeeting started Tue Aug 25 08:00:43 2020 UTC and is due to finish in 60 minutes.  The chair is takahashi-tsc. Information about MeetBot at http://wiki.debian.org/MeetBot.08:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.08:00
*** openstack changes topic to " (Meeting topic: tacker)"08:00
openstackThe meeting name has been set to 'tacker'08:00
*** keiko-k has joined #openstack-meeting08:01
takahashi-tscI think we have 2 topics at least, TST from me and revise docs from yoshito-ito08:01
takahashi-tscAny other topics?08:01
yoshito-itoI have a topic about revising docs.08:02
*** ueha has joined #openstack-meeting08:02
yoshito-itooh, takahashi-tsc has already mentioned it, thank you.08:02
takahashi-tscOK. Can we start from my topic?08:03
yoshito-itoyes, please!08:04
takahashi-tscOK https://etherpad.opendev.org/p/tacker-meeting08:05
takahashi-tscI've participated TST meeting, and STF join the meeting. STF seems a team who make test code.08:06
takahashi-tscBasically, STF team agree with our proposal. Especially response code and response header.08:07
takahashi-tscBut discussion is still needed and the actual test improvement may be in W cycle period...08:08
*** sridharg has joined #openstack-meeting08:08
takahashi-tscToday, I'd like to discuss L38. i.e. What Tacker team can do for TST.08:08
takahashi-tscIn my opinion, Tacker should not do standardization work, but we can contribute our own test code to TST.08:09
takahashi-tscWhat do you think about it?08:10
yoshito-itoI agree. The standardization is not our (Tacker's) scope, but it's good to make feedback to TST.08:11
yoshito-itoI'm not sure how the contrubution of our test code will be.08:12
takahashi-tscI think I'll improve Robot code for Tacker team. And some of them can be shared with STF team.08:14
yoshito-itoOK, we can make bug reports to TST repository, which may be a simple error of Robot code or a wrong definition from SOL documents.08:15
takahashi-tscAgree. I think we proceed with it for "Tacker testing improvement", and share with STF/TST.08:17
masazumi-otaI agree too. It should be closed to feedback such as conditions to be met for the test code.Standardization should be left to the TST as a traditional role.08:17
*** ijw has joined #openstack-meeting08:18
takahashi-tscOK, thank you for your comment. I write these comment in etherpad. I'll plan to discuss it with TST team.08:19
takahashi-tscIf you have some other comment, please write in etherpad.08:20
yoshito-itoDid you discuss the "tag" strategy in ETSI repository? Now we can find "2.4.1" and "2.6.1" are provided, and also 2.7.1 and 3.3.1 seems in developement.08:20
takahashi-tscYes. you are correct. "2.4.1" and "2.6.1" are provided and later version is under development.08:21
*** NAO_H has joined #openstack-meeting08:21
takahashi-tscI suggest that TST should decide "maintenance policy". And STF team agree with it.08:22
yoshito-itoGreat. That is a important step.08:23
takahashi-tscI think they do not decide how to maintenance branch which is already released...08:23
*** ijw has quit IRC08:23
yoshito-itoI think we need to discuss when to start to try their Robot code. Can we wait for the policy from TST or STF?08:24
takahashi-tscIn my current development for using Robot, I'll just use version 2.6.1. But we should continue to discuss with the output of our development.08:25
takahashi-tscIn V cycle, I'll complete first development as above, and improve each (Tacker and TST/STF) code in W cycle.08:26
yoshito-itoGreat, thank you. I agree to use v2.6.1 first.08:26
takahashi-tscOK, can we move to next topic from yoshito-ito?08:28
yoshito-itoI'm trying to revise Tacker documents.08:29
yoshito-itoI found we need to update the doc structure itself because now we have unclear index.08:29
yoshito-itoMy proposal is shown in https://etherpad.opendev.org/p/tacker-meeting.08:30
yoshito-itoI welcome your feedback.08:30
yoshito-itoI've already created a new doc structure. Also, I mapped the existing docs to it and marked "TBD" for new required docs.08:31
masazumi-otaI have already checked out the proposal. I have no objection to it.08:32
takahashi-tscGreat thanks! As you wrote, we start to writing testing guide especially Robot (L429-432)08:33
takahashi-tscMain topic is Robot, but we try to organize UT, FT and Robot testing.08:34
yoshito-itoThanks! It helps me a lot.08:35
yoshito-itoI will create docs for ETSI NFV-SOL based implementation in Use Case Guide.08:36
takahashi-tscYes, we and Tacker users need it.08:36
yoshito-itoAfter the discussion in etherpad, I will upload a patch to re-design the structure of docs. Also I will propose required docs as much as possible in V release.08:37
yoshito-itoI'm not familiar with the legacy Tacker implementation, so I welcome your help.08:38
takahashi-tscThanks, basically seems good. And our team will also discuss and give feedback later.08:38
yoshito-itoGreat, thank you!08:38
takahashi-tscOK, I'll also talked about updating legacy Tacker docs.08:39
yoshito-itoThank you! That's all from me for today.08:42
takahashi-tscOK thanks. Any other topics everyone?08:42
masazumi-otaI have no topic.08:43
takahashi-tscOK, let's close the meeting. Thank you!08:45
yoshito-itoThank you! bye!08:45
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"08:45
openstackMeeting ended Tue Aug 25 08:45:38 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)08:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-08-25-08.00.html08:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-08-25-08.00.txt08:45
openstackLog:            http://eavesdrop.openstack.org/meetings/tacker/2020/tacker.2020-08-25-08.00.log.html08:45
*** yoshito-ito has quit IRC08:48
*** NAO_H has quit IRC08:48
*** ijw has joined #openstack-meeting08:49
*** ijw has quit IRC08:54
*** takahashi-tsc has quit IRC08:58
*** dosaboy has quit IRC08:59
*** dosaboy has joined #openstack-meeting08:59
*** keiko-k has quit IRC08:59
*** yamamoto has quit IRC09:16
*** yamamoto has joined #openstack-meeting09:18
*** ianychoi__ has joined #openstack-meeting09:21
*** ijw has joined #openstack-meeting09:21
*** ianychoi_ has quit IRC09:24
*** belmoreira has joined #openstack-meeting09:25
*** ijw has quit IRC09:26
*** masahito has joined #openstack-meeting09:26
*** verdurin has joined #openstack-meeting09:31
*** yamamoto has quit IRC09:32
*** e0ne has quit IRC09:39
*** yamamoto has joined #openstack-meeting09:45
*** yamamoto has quit IRC09:46
*** ijw has joined #openstack-meeting09:53
*** yamamoto has joined #openstack-meeting09:54
*** ijw has quit IRC09:57
*** ueha has quit IRC10:01
*** xyang has quit IRC10:13
*** jamespage has quit IRC10:14
*** johnsom has quit IRC10:16
*** jamespage has joined #openstack-meeting10:16
*** xyang has joined #openstack-meeting10:16
*** johnsom has joined #openstack-meeting10:17
*** ijw has joined #openstack-meeting10:24
*** masahito has quit IRC10:25
*** e0ne has joined #openstack-meeting10:28
*** ijw has quit IRC10:29
*** patrickeast has quit IRC10:49
*** knikolla has quit IRC10:49
*** csatari has quit IRC10:49
*** sri_ has quit IRC10:50
*** aprice has quit IRC10:50
*** yamamoto has quit IRC10:52
*** yamamoto has joined #openstack-meeting10:54
*** ijw has joined #openstack-meeting10:56
*** rcernin has joined #openstack-meeting10:58
*** patrickeast has joined #openstack-meeting11:00
*** ijw has quit IRC11:00
*** sri_ has joined #openstack-meeting11:01
*** csatari has joined #openstack-meeting11:01
*** knikolla has joined #openstack-meeting11:01
*** aprice has joined #openstack-meeting11:05
*** yamamoto has quit IRC11:24
*** yamamoto has joined #openstack-meeting11:25
*** ijw has joined #openstack-meeting11:27
*** trident has quit IRC11:31
*** ijw has quit IRC11:32
*** Lucas_Gray has joined #openstack-meeting11:41
*** rfolco has joined #openstack-meeting11:53
*** rh-jelabarre has joined #openstack-meeting11:58
*** yamamoto has quit IRC11:58
*** ijw has joined #openstack-meeting11:59
*** ijw has quit IRC12:03
*** raildo has joined #openstack-meeting12:13
*** ijw has joined #openstack-meeting12:30
*** ijw has quit IRC12:35
*** yamamoto has joined #openstack-meeting12:37
*** Guest34946 has joined #openstack-meeting12:47
*** yamamoto has quit IRC12:48
*** Guest34946 is now known as redrobot12:50
*** Luzi has joined #openstack-meeting12:55
*** lpetrut has joined #openstack-meeting12:57
*** bnemec has joined #openstack-meeting13:00
*** ijw has joined #openstack-meeting13:02
*** trident has joined #openstack-meeting13:02
*** masayukig has quit IRC13:05
*** ijw has quit IRC13:07
*** masayukig has joined #openstack-meeting13:16
*** masazumi-ota has quit IRC13:16
*** TrevorV has joined #openstack-meeting13:41
*** gyee has joined #openstack-meeting14:03
*** ijw has joined #openstack-meeting14:06
*** ijw has quit IRC14:07
*** ijw has joined #openstack-meeting14:07
*** Lucas_Gray has quit IRC14:13
*** dklyle has joined #openstack-meeting14:19
*** bauzas has quit IRC14:33
*** ijw_ has joined #openstack-meeting14:34
*** ijw has quit IRC14:38
*** moguimar has quit IRC14:43
*** rcernin has quit IRC14:45
*** bauzas has joined #openstack-meeting14:47
*** bauzas has quit IRC14:52
*** bauzas has joined #openstack-meeting14:54
*** lajoskatona has joined #openstack-meeting14:59
ralonsoh#startmeeting neutron_qos15:02
openstackMeeting started Tue Aug 25 15:02:02 2020 UTC and is due to finish in 60 minutes.  The chair is ralonsoh. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: neutron_qos)"15:02
openstackThe meeting name has been set to 'neutron_qos'15:02
lajoskatonaHi ralonsoh15:02
ralonsohtoday we have one topic15:02
ralonsohplease lajoskatona15:02
*** psahoo has quit IRC15:03
lajoskatonaLast time we discussed it you proposed to check the Port BEFORE_UPDATE, to avoid rollbacks and so on15:03
lajoskatonaI checked and basically works fine :-)15:03
ralonsohahhh yes15:03
ralonsohdo you have the link to the patch?15:04
lajoskatonatoday gibi went there and left really good comments both in tempest and in neutron patch15:04
ralonsohI'll review the n-lib and the neutron patch tomorrow morning15:05
ralonsohwe should have the n-lib patch ASAP15:05
lajoskatonaand I think the most relevant is (as I see now at least) to do rollback in placement allocation if port update fails in neutron db operation or anytime after before_update15:06
lajoskatonathe neutron patch is under construction, so I hope today afternoon or tomorrow I can push a new version15:06
ralonsohexactly, if the placement call fails, we need to rollback the operation15:06
*** mlavalle has joined #openstack-meeting15:06
lajoskatonathat is clear, but the comment is to rollback the placement allocation change if neutron fails sometime later in port update operation15:07
lajoskatonalike imagine db error or something like that15:07
ralonsohyou mean https://review.opendev.org/#/q/topic:bug/1882804+(status:open+OR+status:merged)15:08
ralonsohthis comment15:08
lajoskatonato tell the truth I can't see if that is possible for all possible failures, or is there some mechanism in neutron to notify in case of failure?15:08
lajoskatonayes that's it15:09
ralonsohyeah, we need to kind of mechanism to track the command failure15:10
ralonsohand in this case, revert the placement update15:10
ralonsohbecause executing this in the other way is not an option, right?15:10
ralonsohfor example15:10
ralonsoh1) request placement allocation15:11
ralonsoh2) db operation15:11
ralonsoh3) placement update15:11
ralonsoh(3) if (2) succeeds15:11
lajoskatonanot really as allocation can change any time, so better to keep the GET allocation and PUt close in time15:11
ralonsohlajoskatona, but when you update the placement, you have a feedback15:13
ralonsohthis is rest command15:13
ralonsohyou send an update command over the instant value15:13
ralonsohI know this value can change15:13
ralonsohbut you can have two operations in parallel15:14
ralonsohI don't know if I'm explaining myself well...15:14
ralonsohyou can read the allocation15:14
lajoskatonawhat do you mean in parallel?15:14
ralonsohfor example, two update commands in parallel15:14
lajoskatonaparallel placement update and db operation?15:14
ralonsohno no15:15
ralonsohtwo port update commands15:15
ralonsoheach one increasing the BW allocations15:15
ralonsohthis is a risk you can assume15:15
ralonsohlet me explain15:15
ralonsohyou can oversubscribe the BW allocation15:16
ralonsohif you have a max BW of 10015:16
ralonsohand you have a current allocation of 9015:16
ralonsohand you increase two ports at the same time, adding 10 to each one15:16
*** armax has joined #openstack-meeting15:16
ralonsohmaybe you'll finish those commands with an allocation of 11015:16
ralonsohif you do those 3 steps15:17
ralonsohread, db operation, placement update15:17
ralonsohbut this can be documented15:17
lajoskatonayeah that's possible, I am not sure if placement has some way to avoid such things15:17
*** psahoo has joined #openstack-meeting15:18
ralonsohby default, if you add a limit, placement won't let you overflow it15:18
lajoskatonayes, that's true as the max is added to the rp on the compute15:19
ralonsohIMO, it's easier in this case to rollback manually the DB operations15:20
ralonsohso if (3) fails, revert (2)15:20
lajoskatonabut if the placement update is after the db operation in case placement update fails the db must be rolled back15:20
ralonsohbut how many times that will happen?15:20
ralonsohif you read that you have 10mbps available15:21
ralonsohand you increase the port BW this amount15:21
ralonsohand then you update the placement, how many times you'll have an error there?15:21
lajoskatonagood question, but it can happen :-)15:22
ralonsohyes, in case you execute port qos update commands in parallel15:22
lajoskatonaand as it is a remote operation it can take time with retries (due to generation conflicts i.e.)15:23
lajoskatonanot just qos update15:23
lajoskatonaallocation is for instance and that can be changed several ways like memory/disk whatever change15:23
lajoskatonaor the vm is moved to new host15:23
lajoskatonaand those are at least retries with new get allocation and new put allocation15:24
lajoskatonathe terrible thing is that placement has this generation thing which is really good but for allocations theres more than enough :-)15:25
ralonsohit is not possible to send an "increase" command15:27
ralonsohyou need first to read the value and then send the new one15:27
lajoskatonaso it can time consuming and the result of update is not sure till placement operation is finished15:27
lajoskatonathat is in the neutron-lib patch basically15:27
ralonsohso placement should be a restfull API but it is not15:29
lajoskatonaupdate_qos_minbw_allocation awaits only the diff and adds that to the fetched values from placement15:29
*** belmoreira has quit IRC15:29
ralonsohIMO, but this is out of scope, we should have an "atomic" operation to increase/decrease allocations15:29
ralonsohthat's more efficient15:30
lajoskatonathose are always good discussions with them:-) Mostly they were the API sig at a time15:30
ralonsohok so15:30
ralonsohin your approach15:30
ralonsohyou need to handle the case of a DB failure15:31
*** lpetrut has quit IRC15:32
lajoskatonayes, and currently I don't see way for that15:33
ralonsohif, eventually you run out of ideas or time, try my idea if you want it15:34
lajoskatonayou mean fetch allocation - db change - change placement allocation ?15:34
lajoskatonawhat do you think about this summary: https://bugs.launchpad.net/neutron/+bug/1882804/comments/415:36
openstackLaunchpad bug 1882804 in neutron "RFE: allow replacing the QoS policy of bound port" [Wishlist,Confirmed] - Assigned to Lajos Katona (lajos-katona)15:36
lajoskatonait is not exactly that one, but as allocation update can be  time consuming nearly the same15:36
lajoskatonanow the neutron-lib patch do the GET allocation and PUT allocation in one method to keep GET and PUT close15:38
ralonsohso you are using a new field in the port to set the update transaction status15:38
lajoskatonathat was part of that thinking to show the user if update is still in progress15:40
lajoskatonado you think that is really necessary?15:40
lajoskatonaJKust thinking loudly15:40
ralonsohI always prefer to use the DB to lock a transaction15:41
ralonsohthis is adding an extra transaction parameter15:41
ralonsohdifferent to any other parameter (not standard in Neutron)15:41
*** baojg has quit IRC15:41
*** baojg has joined #openstack-meeting15:42
lajoskatonathat's true, but the placement REST operations must be out of db15:42
lajoskatonaI mean not in the lock to avoid stopping every other db operations15:43
ralonsohnot big fan of this idea15:44
ralonsohbut I don't see a better15:44
ralonsohbetter one*15:45
ralonsohyou should document in the dev docs what this flag means15:45
*** psahoo has quit IRC15:46
lajoskatonaupdate_status or similar15:46
ralonsohyeah, valid, if needed, for other DB objects15:46
lajoskatonayou mean other than port?15:47
ralonsohyes, in other feature15:47
ralonsohjust to implement something standard15:47
lajoskatonathat is an extension that "extends" not just ports but i.e. networks, subnets....15:50
lajoskatonaam I right?15:50
ralonsohif needed, yes15:51
ralonsohbut let's focus now in the port15:51
lajoskatonayeah, that can be a first step15:52
lajoskatonathanks ralonsoh, I go a check my previous attempt to have the allocation update after db update, and push that when I make it work again :-)15:53
ralonsohI'll review the patch then15:53
lajoskatonathanks for your time, I think we can close the meeting if there's no other thing15:55
ralonsohok, let's finish for today15:56
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:56
openstackMeeting ended Tue Aug 25 15:56:17 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-08-25-15.02.html15:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-08-25-15.02.txt15:56
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_qos/2020/neutron_qos.2020-08-25-15.02.log.html15:56
*** lajoskatona has left #openstack-meeting16:15
*** bnemec has quit IRC16:30
*** jgriffith has quit IRC16:31
*** bnemec has joined #openstack-meeting16:35
*** rh-jelabarre has quit IRC16:43
*** rh-jelabarre has joined #openstack-meeting16:43
*** rafaelweingartne has joined #openstack-meeting16:53
*** rafaelweingartne has quit IRC16:55
*** Luzi has quit IRC16:57
*** yasufum has joined #openstack-meeting17:27
*** ralonsoh has quit IRC17:27
*** yasufum has quit IRC17:36
*** bnemec has quit IRC17:50
*** bnemec has joined #openstack-meeting17:53
*** baojg has quit IRC17:59
*** sridharg has quit IRC18:22
*** hyunsikyang has joined #openstack-meeting18:31
*** hyunsikyang__ has quit IRC18:34
*** sri_ has quit IRC18:48
*** patrickeast has quit IRC18:49
*** sri_ has joined #openstack-meeting18:49
*** aprice has quit IRC18:49
*** patrickeast has joined #openstack-meeting18:50
*** aprice has joined #openstack-meeting18:54
*** Horrorcat has quit IRC19:23
*** ijw_ has quit IRC19:27
*** ijw has joined #openstack-meeting19:28
*** ijw has quit IRC19:32
*** ijw has joined #openstack-meeting19:34
*** ijw has quit IRC19:39
*** ijw has joined #openstack-meeting20:06
*** slaweq has quit IRC20:06
*** vishalmanchanda has quit IRC20:10
*** ijw has quit IRC20:11
*** slaweq has joined #openstack-meeting20:18
*** Lucas_Gray has joined #openstack-meeting20:21
*** zaneb has quit IRC20:21
*** ijw has joined #openstack-meeting20:37
*** ijw has quit IRC20:42
*** ijw has joined #openstack-meeting20:43
*** yamamoto has joined #openstack-meeting21:30
*** raildo has quit IRC21:31
*** TrevorV has quit IRC21:47
*** rfolco has quit IRC21:57
*** rfolco has joined #openstack-meeting21:57
*** yamamoto has quit IRC22:00
*** rcernin has joined #openstack-meeting22:02
*** rfolco has quit IRC22:02
*** rfolco has joined #openstack-meeting22:03
*** rfolco has quit IRC22:04
*** rfolco has joined #openstack-meeting22:06
*** rfolco has quit IRC22:08
*** rfolco has joined #openstack-meeting22:12
*** bnemec has quit IRC22:14
*** rfolco has quit IRC22:16
*** rh-jelabarre has quit IRC22:21
*** rh-jelabarre has joined #openstack-meeting22:21
*** zaneb has joined #openstack-meeting22:22
*** mlavalle has quit IRC22:57
*** tosky has quit IRC23:04
*** rfolco has joined #openstack-meeting23:19
*** yamamoto has joined #openstack-meeting23:59

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!