Wednesday, 2020-07-08

*** tetsuro has joined #openstack-meeting-alt00:02
*** enriquetaso has quit IRC00:04
*** rfolco has quit IRC00:22
*** yamamoto has joined #openstack-meeting-alt00:39
*** rcernin has quit IRC00:42
*** rcernin has joined #openstack-meeting-alt00:46
*** tetsuro has quit IRC01:32
*** ricolin has joined #openstack-meeting-alt01:40
*** tetsuro has joined #openstack-meeting-alt01:41
*** tetsuro has quit IRC01:43
*** tetsuro has joined #openstack-meeting-alt01:44
*** rcernin has quit IRC02:13
*** apetrich has quit IRC02:14
*** rcernin has joined #openstack-meeting-alt02:15
*** rcernin has quit IRC02:33
*** dave-mccowan has quit IRC02:41
*** dave-mccowan has joined #openstack-meeting-alt02:50
*** rcernin has joined #openstack-meeting-alt02:55
*** tetsuro has quit IRC03:11
*** markvoelker has joined #openstack-meeting-alt04:03
*** markvoelker has quit IRC04:07
*** diurnalist has quit IRC04:19
*** dave-mccowan has quit IRC04:19
*** diurnalist has joined #openstack-meeting-alt05:32
*** links has joined #openstack-meeting-alt05:32
*** diurnalist has quit IRC06:04
*** ianw is now known as ianw_pto06:38
*** trident has quit IRC06:39
*** ccamacho has joined #openstack-meeting-alt06:42
*** trident has joined #openstack-meeting-alt06:42
*** markvoelker has joined #openstack-meeting-alt06:43
*** markvoelker has quit IRC06:48
*** rcernin has quit IRC06:59
*** rdopiera has joined #openstack-meeting-alt07:02
*** rcernin has joined #openstack-meeting-alt07:06
*** ttsiouts has joined #openstack-meeting-alt07:16
*** lbragstad_ has joined #openstack-meeting-alt07:19
*** lbragstad has quit IRC07:21
*** rcernin has quit IRC07:41
*** ralonsoh has joined #openstack-meeting-alt07:47
*** ttsiouts has quit IRC08:06
*** ttsiouts has joined #openstack-meeting-alt08:15
*** derekh has joined #openstack-meeting-alt08:19
*** diurnalist has joined #openstack-meeting-alt09:00
*** diurnalist has quit IRC09:04
*** rcernin has joined #openstack-meeting-alt09:27
*** yamamoto has quit IRC09:39
*** rcernin has quit IRC09:41
*** yamamoto has joined #openstack-meeting-alt09:42
*** derekh has quit IRC09:57
*** derekh has joined #openstack-meeting-alt09:58
*** yamamoto has quit IRC10:00
*** yamamoto has joined #openstack-meeting-alt10:02
*** e0ne has joined #openstack-meeting-alt10:12
*** yamamoto has quit IRC10:18
*** rfolco has joined #openstack-meeting-alt10:38
*** apetrich has joined #openstack-meeting-alt10:44
*** yamamoto has joined #openstack-meeting-alt10:51
*** yamamoto has quit IRC10:56
*** ttsiouts has quit IRC11:07
*** ttsiouts has joined #openstack-meeting-alt11:25
*** markvoelker has joined #openstack-meeting-alt11:34
*** raildo has joined #openstack-meeting-alt11:37
*** markvoelker has quit IRC11:39
*** ttsiouts has quit IRC11:58
*** rcernin has joined #openstack-meeting-alt12:09
*** ttsiouts has joined #openstack-meeting-alt12:11
*** rcernin has quit IRC12:16
*** ttsiouts has quit IRC12:16
*** ttsiouts has joined #openstack-meeting-alt12:25
*** yaawang has quit IRC12:54
*** yaawang has joined #openstack-meeting-alt12:58
*** tosky has joined #openstack-meeting-alt13:16
*** lpetrut_ has joined #openstack-meeting-alt13:21
*** ccamacho has quit IRC13:23
*** ttsiouts has quit IRC13:28
*** ttsiouts has joined #openstack-meeting-alt13:33
*** rosmaita has joined #openstack-meeting-alt13:44
*** liuyulong has joined #openstack-meeting-alt13:51
*** Liang__ has joined #openstack-meeting-alt13:54
*** geguileo has joined #openstack-meeting-alt13:54
*** knomura has joined #openstack-meeting-alt13:55
*** liuyulong has quit IRC13:57
*** dviroel has joined #openstack-meeting-alt13:58
*** Liang__ has quit IRC13:59
*** jungleboyj has joined #openstack-meeting-alt13:59
rosmaita#startmeeting cinder14:00
openstackMeeting started Wed Jul  8 14:00:35 2020 UTC and is due to finish in 60 minutes.  The chair is rosmaita. 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: cinder)"14:00
openstackThe meeting name has been set to 'cinder'14:00
jungleboyjo/14:00
rosmaita#topic roll call14:00
e0nehi14:00
*** openstack changes topic to "roll call (Meeting topic: cinder)"14:00
whoami-rajatHi14:00
geguileohi! o/14:01
*** eharney has joined #openstack-meeting-alt14:01
eharneyhi14:01
toskyhi14:01
rosmaitaok, looks like we have some people14:02
rosmaitahello everyone14:02
rosmaita#linkĀ https://etherpad.openstack.org/p/cinder-victoria-meetings14:02
rosmaitai'm at a coffee shop due to a power outage14:03
smcginniso/14:03
rosmaitaso not using my usual keyboard, as you will notice14:03
rosmaitaok, let's get started14:03
rosmaita#topic updates14:03
*** openstack changes topic to "updates (Meeting topic: cinder)"14:03
jungleboyjrosmaita,  You can go to coffee shops?14:03
jungleboyj:-)14:03
rosmaitai am sitting outside, 15 feet from anyone else14:04
jungleboyj++14:04
rosmaitainside is closed, you can only get coffee and leave14:04
rosmaitabut the wifi is working!14:04
toskywhat else is needed then14:04
rosmaitaa better keyboard!14:04
rosmaitai the function and control keys are mashed together and i am having cutting & pasting problems14:05
*** sfernand has joined #openstack-meeting-alt14:05
rosmaitabut enough about that14:05
rosmaitaok, the video meeting poll closes tomorrow14:05
rosmaita#link https://rosmaita.wufoo.com/forms/monthly-video-meeting-proposal/14:05
*** Liang__ has joined #openstack-meeting-alt14:05
rosmaitait even has an option for "don't care", so even if you don't care, you can still fill it out14:05
*** enriquetaso has joined #openstack-meeting-alt14:06
rosmaitathis week is R-minus-1414:06
rosmaitamilestone 2 is at R-1114:06
enriquetasoo/14:06
rosmaitahello sofia14:06
rosmaitathat is, really soon14:06
rosmaitait is also the new driver merge deadline14:06
rosmaitai think we have 2 new drivers proposed?14:06
rosmaitahitachi is mostly together14:06
rosmaitathanks to lseki and smcginnis for reviewing that closely14:07
rosmaitaand i think dell/emc is proposing a new driver?14:07
rosmaitai don't think i've seen any patches, just the launchpad blueprint so far14:07
rosmaitaand a special note for geguileo14:07
rosmaitaussuri cinderlib must be released by R-914:07
smcginnisrosmaita: I don't think we will get that Dell one for Victoria.14:08
*** Liang__ is now known as LiangFang14:08
LiangFango/14:08
rosmaitasmcginnis: ok14:08
geguileorosmaita: as soon as we review the patches that are in gerrit (with the exception of the one with the -W) we can release14:08
rosmaita"we" meaning "me", at least partially ... OK, will do14:08
*** TusharTgite has joined #openstack-meeting-alt14:08
rosmaitaok, that's all the announcements14:09
rosmaitai thought for a minute i deleted lseki's topic by mistake14:09
rosmaitabut i see that he has moved it lower due to connection problems14:09
rosmaita#topic Moving stable/ocata and stable/pike to quick EOL14:10
*** openstack changes topic to "Moving stable/ocata and stable/pike to quick EOL (Meeting topic: cinder)"14:10
sfernandLucio is having some issues to join the meeting, he is asking if we could post pone that14:10
sfernandahh ok14:10
TusharTgitehi14:10
rosmaitaok, so you may have seen on the ML that nova is proposing to put pike and ocata into 'unmaintained'14:10
rosmaitahang on while i paste links14:10
rosmaita#link http://lists.openstack.org/pipermail/openstack-discuss/2020-July/015747.html14:11
rosmaita#link http://lists.openstack.org/pipermail/openstack-discuss/2020-July/015798.html14:11
rosmaitayou may remember that there was a proposal to do this for ocata before the PTG14:11
rosmaitaand smcginnis pointed out in that thread that if one of the major projects EOLs a branch, we pretty much all have to do it14:12
rosmaitaanyway14:12
rosmaitai looked at our cinder ocata and pike branches14:12
rosmaitaand they haven't been committed to in over 6 months14:12
rosmaitai mention that because lyarwood was proposing to back-date the nova 'unmaintained' phase to the last commit, which would mean a 3 month head start14:13
rosmaitai am not being clear14:13
rosmaitathe issue is that a branch is supposed to be 'unmaintained' for 6 months, and then can go EOL14:13
rosmaitaso, if it's ok for nova to back-date the 'unmaintained' period, i think we can too14:13
rosmaitajust so happens that our back-dating can be 6 months14:14
rosmaitaso my proposal is to put out a notice on the ML14:14
rosmaitathat we are putting cinder pike and ocata into 'unmaintained' for 2 weeks, and if no one adopts them, we will EOL them14:14
smcginnis++14:14
rosmaitathat's what i was waiting for!14:15
rosmaitathanks smcginnis14:15
smcginnis;)14:15
rosmaitaok, so i will do that this afternoon ... 2 weeks from today is 22 July14:15
rosmaita(just to have that on the record)14:15
LiangFang++14:15
toskyremoving them will simplify a lot the job handling; most "modern" jobs starts from pike, if not rocky14:16
rosmaitayeah, ocata has been dead to me for a month now14:16
rosmaitaand pike is not much better14:16
rosmaitahooray for modernization14:16
rosmaitathat's all, if anyone has second thoughts, we may have some open discussion later, and there is always the ML14:17
rosmaita#topic rethink the visibility of __DEFAULT__ type14:17
*** openstack changes topic to "rethink the visibility of __DEFAULT__ type (Meeting topic: cinder)"14:17
rosmaitawhoami-rajat: that's you14:17
whoami-rajatrosmaita, thanks!14:17
*** lseki has joined #openstack-meeting-alt14:18
rosmaita#link https://bugs.launchpad.net/cinder/+bug/188663214:18
openstackLaunchpad bug 1886632 in Cinder "Cannot delete __DEFAULT__ volume type" [Undecided,New] - Assigned to Rajat Dhasmana (whoami-rajat)14:18
whoami-rajatSo we've had a recent bug in which the author states that their users are being confused by the __DEFAULT__ name14:18
* lseki sneaks in14:18
rosmaitai was skeptical at first, but the last comment on the bug is very revealing14:18
whoami-rajats/name/type14:18
whoami-rajatthey say they don't want their users to see the __DEFAULT__ type since they've already configured CONF.default_volume_type14:19
eharneythey don't want to see it when listing types, that is?14:19
rosmaitaeharney: yes, but maybe even stronger than that14:20
rosmaitai think the way to go here is to not display __DEFAULT__ in the GET /types response if there is a default-type configured in cinder.conf14:20
*** LiangFang has quit IRC14:20
jungleboyj*Sigh*14:20
whoami-rajateharney, yes, they say the users gets confused if they should use this one or the other their admin has configured as default14:20
rosmaitafor type-show, you need to know the UUID of the type, is that right?14:20
whoami-rajatrosmaita, id or name14:21
rosmaitawe take the name in the path?14:21
whoami-rajatnames are unique for volume types14:21
jungleboyjThe concern does make sense.14:21
*** Liang__ has joined #openstack-meeting-alt14:21
whoami-rajatI'm not really sure if this is a problem for a large mass of just this particular case14:21
rosmaitai think we will see it more and more14:22
rosmaitathe problem i see, is that __DEFAULT__ shows up in the api ref14:22
geguileorosmaita: hiding the __DEFAULT__ vol type if we have a default in .conf could lead to a deployment having some volumes with __DEFAULT__ type but not getting it listed14:22
rosmaitaand if you can do GET /types/__DEFAULT__14:22
geguileoif they changed it after creating some volumes14:22
whoami-rajatrosmaita, but we allow the __DEFAULT__ to be configurable, that's why it is visible14:22
rosmaitayes, but if it is not used at all. what does that matter?14:23
*** dave-mccowan has joined #openstack-meeting-alt14:23
whoami-rajatrosmaita, also if a volume gets created with the __DEFAULT__ type, it would confuse users more that their volume is using a type which isn't visible14:23
geguileowe could add a config option to hide it?14:23
rosmaitano14:23
rosmaitayou just said they can do GET on the __DEFAULT__, so they can still see it14:23
rosmaitai mean, at the time you do a GET /types call, if the operator has one configured, that is what you will get14:24
rosmaitaso we don't need to display the __DEFAULT__ in that case14:24
rosmaitaand if the operator removes the config14:24
rosmaitathen we will14:24
rosmaitawhich makes sense14:24
geguileobut if someone created a volume and it used __DEFAULT__14:24
geguileothen the .conf was changed14:24
geguileolisting types would not return it14:25
geguileoand it would be weird not to have the type that some volume has14:25
geguileowhen listing, I mean14:25
geguileo(the type would be there)14:25
rosmaitai think it depends on what the types list is supposed to display14:25
rosmaitai think the types that are currently available to you14:26
geguileoand __DEFAULT__ is available14:26
eharneycan't a user still manually create a volume w/ type __DEFAULT__ even if we don't list it?14:26
geguileoeharney: yup14:26
eharneyso i'm not sure it's just about visibility in the list14:26
rosmaitathat seems like a bug14:26
rosmaitai mean, __DEFAULT__ is supposed to be for lazy operators14:26
geguileoI don't see that as a bug...14:26
eharneyi think it probably is a bug14:27
rosmaitasure, the operator has configured a default type, that's what the default should be14:27
rosmaitaso, looks like a can of worms has been opened14:27
eharneypresumably if the operator made a default volume type, they don't want __DEFAULT__ to be used14:27
*** lpetrut_ has quit IRC14:28
rosmaitayes, that's exactly this bug-filer's issue14:28
rosmaitawhoami-rajat: i forget, what are the restrictions on modifying __DEFAULT__ type?14:28
rosmaitai mean the actual system default14:29
whoami-rajatrosmaita, their issue is they don't want their users to see it, they don't use it but it doesn't cause them any problem other than confusion14:29
whoami-rajatrosmaita, we can update it, but can't delete it14:29
rosmaitaso they could update __DEFAULT__ to have exactly the same properties as their preferred default?14:30
whoami-rajatwhat i suggested was, i will document this clearly14:30
whoami-rajatrosmaita, yes they can14:30
rosmaitabut they can't do it while there are any volumes of __DEFAULT__, right?14:30
whoami-rajatrosmaita, yep, it shouldn't be in use by any volume14:31
*** dave-mccowan has quit IRC14:31
rosmaitawell, except as eharney pointed out, a user could explicitly ask for it14:31
rosmaitagiven that it's all over the api-ref responses14:31
whoami-rajatI've no issues in improving the documentation but what they're suggesting is to remove it which will again allow creating of untyped volumes which i don't prefer14:32
whoami-rajatand we also discussed the visibility scenario, that doesn't seem to work either14:33
rosmaitai think we have 2 bugs:14:33
rosmaita1) if an operator has configured a default type, users should not be able to create a volume of __DEFAULT__ type14:33
rosmaita2) if an operator has configured a default type, the __DEFAULT__ should not be displayed in the GET /types response (this one is controversial right now)14:34
rosmaitai think this is a real problem, because even though it's kind of silly, customer calls are a PITA14:34
smcginnisSince __DEFAULT__ was created because we can't handle things right in our code because too many places expected to have a type, I think it should be hidden from end users.14:35
rosmaitasmcginnis: ++14:35
whoami-rajatthe configured one already has a priority over the __DEFAULT__ type14:35
rosmaitayes, but there' s no way for end users to know that14:35
geguileoand the problem is that horizon would present __DEFAULT__14:36
rosmaitayeah, and DEFAULT looks more important that default14:36
smcginnisYep.14:36
jungleboyjYeah.  I do think that the complaint is relevant.14:37
geguileoyeah, it's a reasonable complaint14:37
rosmaitaok, let's think about this some more and revisit next week14:37
whoami-rajatthanks everyone for their feedback14:38
jungleboyjrosmaita, ++14:38
geguileoI think we can hide the __DEFAULT__ type from the list if there are no volumes that use them and cinder.conf has a different default14:38
geguileos/them/it14:38
rosmaitageguileo: problem is, any deployment since train will definitely have them14:38
geguileorosmaita: not necessarily14:38
rosmaitayes14:39
rosmaitathere was a regression14:39
geguileorosmaita: they could have a default already defined14:39
geguileoin the conf14:39
whoami-rajatgeguileo, but if they comment out the default part in cinder.conf, we should show it ?14:39
geguileoand the __DEFAULT__ would not be used14:39
geguileowhoami-rajat: that's what I would do14:39
geguileothat, or having a config option14:39
rosmaitai don't like the config option14:40
rosmaitabut we can discuss next week, let's move on14:40
geguileorosmaita: but it's the cleanest way, since we pass the responsibility to the admin14:40
geguileorosmaita: ok14:40
rosmaita#topic CI issues14:41
*** openstack changes topic to "CI issues (Meeting topic: cinder)"14:41
rosmaitatosky: hopefully this is quick14:41
toskyI can just copy the content of the etherpad here14:41
toskyor do a summary:14:41
tosky- you can see many failures on cinder-tempest-plugin-lvm-lio-barbican fails, especially one test, I don't know why14:42
tosky- https://review.opendev.org/#/c/733161/ should temporarily unblock cinder-tempest-plugins gate broken by the ceph updates (but we need to fix them)14:42
tosky- please merge https://review.opendev.org/#/c/738978/ and its future train backport to make the ceph job pass again14:43
tosky- devstack-plugin-nfs-tempest-full is superbroken for unknown reasons (see https://review.opendev.org/#/c/735959/)14:43
toskythat's it - suggestions and help more than welcome14:43
eharneythe lio-barbican job has been a little flaky for a while, and i occasionally look at it, but the failures are never very actionable/interesting to me14:43
eharney(that is, it probably needs a more thorough look)14:44
rosmaitasuperbroken is even worse than usualy14:44
toskyI suspect resource issues, the tests which fails most for lio-barbican is     tempest.scenario.test_volume_boot_pattern.TestVolumeBootPattern.test_volume_boot_pattern14:44
toskyand it usually fails to connect to the spawned instance14:44
rosmaitatosky: i think you are onto something there14:44
eharneyright14:45
eharneyare we still chasing any of these things with elastic recheck?14:45
rosmaitai personally am not14:45
toskyI admit not being too much into that; I was told no need to add recheck <foo> because it should be caught by elasticsearch (maybe after adding some rules)14:46
*** rdopiera has quit IRC14:46
smcginnisI think since Riedeman left, we lost our last elastic recheck champion. :)14:47
smcginnisI think we should use it though. It does help.14:47
rosmaitaok, let's address that next week too14:47
rosmaitathanks, tosky14:47
rosmaita#topic Fix for Fail to extend attached volume using generic NFS driver14:47
*** openstack changes topic to "Fix for Fail to extend attached volume using generic NFS driver (Meeting topic: cinder)"14:47
rosmaitalseki: that's you14:47
lsekihi14:48
lsekiI think kaisers is ooo but he can read the logs later14:48
rosmaitahopefully your connection will hold for the next 10 min14:48
lsekihopefully14:48
lsekiI talked to openstack-nova folks14:48
*** priteau has joined #openstack-meeting-alt14:48
*** Liang__ has quit IRC14:49
lsekiabout https://bugs.launchpad.net/cinder/+bug/187036714:49
openstackLaunchpad bug 1870367 in Cinder "Fail to extend attached volume using generic NFS driver" [High,In progress] - Assigned to Lucio Seki (lseki)14:49
rosmaitai like the idea of nova doing everything14:49
lsekiin short, generic nfs driver is failing because it's trying to do an unnecessary `qemu-img resize` operation14:49
*** rdopiera has joined #openstack-meeting-alt14:49
enriquetaso :o14:50
lsekiso the fix is to avoid generic nfs driver from doing that14:50
lsekiand let nova do everything needed14:50
lsekiI submitted 3 draft patches for nova, cinder, and devstack14:50
lsekinova patch to implement a trivial method called upon extend_volume14:51
lsekicinder patch to make nfs driver skip the qemu-img resize when volume is attached14:51
lsekidevstack patch to enable the online extend test for generic nfs driver14:51
lsekireviews are welcome!14:52
eharneydoes the volume manager submit a nova event etc for extend after the driver's extend_volume call?14:52
lsekisoon, I'll submit a similar patch for ONTAP NFS driver; it works on my machine14:53
geguileoeharney: we do14:53
eharneyi suspect this means the extend method may need a lock against create_snapshot and other snapshot calls in the nfs driver14:53
eharneythis also needs to be tested thoroughly with encrypted volumes14:53
eharneybut many thanks for working on this14:54
lseki:-)14:54
rosmaitalseki: looks like your request for corner cases has been satisfied14:54
rosmaitalseki: thanks for the comprehensive report14:54
eharneyto be more clear: performing resize and snapshot operations concurrently may break with your current patch, but i haven't looked too closely14:55
lsekikaisers may do something similar to quobyte nfs driver, putting a depends-on to nova patch14:55
*** ttsiouts has quit IRC14:55
lsekieharney: hmm we should check that14:56
rosmaitafour minutes left ...14:56
lsekiI have another concern: what if nova fails to extend the volume for some  reason?14:56
lsekicinder will update the DB with the new size, but the actual volume file will remain with the original size14:57
eharneyhmm14:57
geguileoeharney: if the driver needs a lock to prevent snapshots while Nova does the resize we have a problem14:57
eharneygeguileo: how so?14:57
geguileobecause the call is async14:57
smcginnisWe just send an event.14:57
smcginnisWe don't ever even know if it happens.14:57
geguileoexactly :-(14:57
geguileowhich brings us to lseki's concern14:58
smcginnis"Hey nova, if you're listening, you can extend this volume if you feel like it."14:58
geguileowhat if it fails14:58
geguileoso we need to find a way to make it synchronous14:58
eharneyi suspect there's an issue if you extend the root file while halfway through a create_snapshot operation which is shuffling files around14:58
geguileoor implement a similar external events mechanism like Nova so they can let us know the result14:58
smcginnisFor other drivers it is not an issue since they extend the volume first, then send an event.14:59
smcginnisIt could be to nova, or it could be to someone else using Cinder for volume services.14:59
smcginnisWe definitely should not have a hard dependency on a nova API.14:59
rosmaitaok, looks like this needs some more thought14:59
rosmaitaand we are out of time15:00
rosmaita#endmeeting15:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:00
openstackMeeting ended Wed Jul  8 15:00:08 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-07-08-14.00.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-07-08-14.00.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2020/cinder.2020-07-08-14.00.log.html15:00
whoami-rajatthanks!15:00
lsekithanks15:00
jungleboyjThanks!15:00
e0ne#startmeeting horizon15:00
geguileorofl rosmaita just kicked us out15:00
openstackMeeting started Wed Jul  8 15:00:40 2020 UTC and is due to finish in 60 minutes.  The chair is e0ne. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: horizon)"15:00
openstackThe meeting name has been set to 'horizon'15:00
*** sfernand has left #openstack-meeting-alt15:00
e0nehi15:01
e0neis anybody around for horizon meeting?15:01
*** tosky has left #openstack-meeting-alt15:02
*** diurnalist has joined #openstack-meeting-alt15:02
e0neI'll wait for 5-7 minutes more if somebody joins me15:03
rdopierao/15:04
*** priteau has quit IRC15:04
e0nerdopiera: hi15:05
amotokihi15:07
e0neI don't have neither updates nor something to discuss this week15:07
*** knomura has left #openstack-meeting-alt15:08
e0nerdopiera, amotoki: do you have anything ti discuss?15:08
amotokie0ne: I have nothing to discuss today from my side.15:09
e0nelet's wrap up the meeting. enjoy the rest of evening!15:10
e0ne#endmeeting15:11
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:11
openstackMeeting ended Wed Jul  8 15:11:49 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:11
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-07-08-15.00.html15:11
rdopierabye15:11
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-07-08-15.00.txt15:11
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2020/horizon.2020-07-08-15.00.log.html15:11
amotokigood night15:12
*** TusharTgite has quit IRC15:14
*** ccamacho has joined #openstack-meeting-alt15:20
*** ccamacho has quit IRC15:20
*** rosmaita has left #openstack-meeting-alt15:20
*** ccamacho has joined #openstack-meeting-alt15:20
*** enriquetaso has quit IRC15:24
*** links has quit IRC15:43
*** enriquetaso has joined #openstack-meeting-alt15:51
*** gyee has joined #openstack-meeting-alt15:52
*** gyee has quit IRC15:59
*** dviroel has quit IRC16:07
*** knomura has joined #openstack-meeting-alt16:21
*** gouthamr has quit IRC16:26
*** knomura has quit IRC16:26
*** derekh has quit IRC16:41
*** whoami-rajat has quit IRC16:46
*** gouthamr has joined #openstack-meeting-alt16:52
*** markvoelker has joined #openstack-meeting-alt16:53
*** markvoelker has quit IRC16:53
*** gyee has joined #openstack-meeting-alt17:07
*** SpamapS has left #openstack-meeting-alt17:23
*** ricolin has quit IRC18:00
*** e0ne has quit IRC18:03
*** ralonsoh has quit IRC18:07
*** gmann_ has joined #openstack-meeting-alt19:17
*** gmann_ is now known as gmann19:18
*** geguileo has quit IRC19:21
*** masayukig has joined #openstack-meeting-alt19:29
*** apetrich has quit IRC19:31
*** apetrich has joined #openstack-meeting-alt19:31
*** stevthedev has joined #openstack-meeting-alt19:32
*** mnaser has joined #openstack-meeting-alt19:32
*** portdirect has joined #openstack-meeting-alt19:32
*** bcm has joined #openstack-meeting-alt19:33
*** jberg-dev has joined #openstack-meeting-alt19:33
*** jungleboyj_ has joined #openstack-meeting-alt19:35
*** kopecmartin is now known as kopecmartin|pto19:52
*** hemna has quit IRC19:52
*** vishalmanchanda has joined #openstack-meeting-alt19:53
*** gagehugo has joined #openstack-meeting-alt19:57
*** dviroel_ has joined #openstack-meeting-alt19:58
*** timirnich has joined #openstack-meeting-alt19:59
*** hemna has joined #openstack-meeting-alt19:59
*** srwilkers has joined #openstack-meeting-alt19:59
*** knikolla has joined #openstack-meeting-alt20:05
*** carloss has joined #openstack-meeting-alt20:06
*** xyang has joined #openstack-meeting-alt20:09
*** johnsom_ has joined #openstack-meeting-alt20:10
*** megheisler has joined #openstack-meeting-alt20:10
*** lseki has quit IRC20:13
*** walshh_ has joined #openstack-meeting-alt20:14
*** vkmc_ has joined #openstack-meeting-alt20:17
*** amito has joined #openstack-meeting-alt20:17
*** hrybacki has joined #openstack-meeting-alt20:23
*** lbragstad_ is now known as lbragstad20:42
*** mnaser is now known as mnaser|ic20:52
*** raildo has quit IRC21:01
*** mnaser|ic has quit IRC21:08
*** mnaser|ic has joined #openstack-meeting-alt21:08
*** mnaser|ic has quit IRC21:08
*** mnaser|ic has joined #openstack-meeting-alt21:08
*** mnaser|ic is now known as vexxhost21:08
*** gouthamr has quit IRC21:09
*** gouthamr has joined #openstack-meeting-alt21:11
*** vexxhost is now known as mnaser21:14
*** mnaser is now known as mnaser|ic21:14
*** gouthamr_ has joined #openstack-meeting-alt21:15
*** johnsom_ is now known as johnsom21:19
*** johnsom has joined #openstack-meeting-alt21:19
*** rdopiera has quit IRC21:38
*** rfolco has quit IRC21:52
*** slaweq has quit IRC21:54
*** portdirect has quit IRC21:56
*** slaweq has joined #openstack-meeting-alt21:56
*** portdirect has joined #openstack-meeting-alt21:56
*** slaweq has quit IRC22:00
*** vishalmanchanda has quit IRC22:03
*** rfolco has joined #openstack-meeting-alt22:52
*** rfolco has quit IRC22:58
*** rcernin has joined #openstack-meeting-alt23:01
*** mnaser|ic has quit IRC23:38
*** mnaser|ic has joined #openstack-meeting-alt23:38
*** mnaser|ic has quit IRC23:38
*** mnaser|ic has joined #openstack-meeting-alt23:38
*** mnaser|ic is now known as mnaser23:38
*** rfolco has joined #openstack-meeting-alt23:58

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