Friday, 2020-04-17

*** tetsuro has joined #openstack-meeting00:21
*** maohongbo1 has joined #openstack-meeting00:48
*** maohongbo has quit IRC00:50
*** maohongbo1 is now known as maohongbo00:50
*** ociuhandu has joined #openstack-meeting01:01
*** jamesmcarthur has joined #openstack-meeting01:01
*** ysandeep|away is now known as ysandeep01:03
*** maohongbo1 has joined #openstack-meeting01:04
*** ociuhandu has quit IRC01:05
*** maohongbo has quit IRC01:06
*** maohongbo1 is now known as maohongbo01:06
*** Liang__ has joined #openstack-meeting01:10
*** ricolin has joined #openstack-meeting01:14
*** jamesmcarthur has quit IRC01:24
*** maohongbo1 has joined #openstack-meeting01:28
*** maohongbo has quit IRC01:30
*** maohongbo1 is now known as maohongbo01:30
*** maohongbo1 has joined #openstack-meeting01:36
*** maohongbo has quit IRC01:38
*** maohongbo1 is now known as maohongbo01:38
*** yaawang has quit IRC01:46
*** yaawang has joined #openstack-meeting01:47
*** yaawang has quit IRC01:52
*** yaawang has joined #openstack-meeting01:53
*** rbudden has quit IRC02:05
*** tetsuro has quit IRC02:06
*** maohongbo has quit IRC02:08
*** apetrich has quit IRC02:08
*** maohongbo has joined #openstack-meeting02:08
*** tetsuro has joined #openstack-meeting02:12
*** jmasud has joined #openstack-meeting02:15
*** jmasud has quit IRC02:20
*** ysandeep is now known as ysandeep|afk02:21
*** jmasud has joined #openstack-meeting02:36
*** igordc has joined #openstack-meeting02:46
*** jmasud has quit IRC02:50
*** igordc has quit IRC02:52
*** igordc has joined #openstack-meeting02:52
*** igordc has quit IRC02:57
*** jmasud has joined #openstack-meeting03:00
*** ykatabam has quit IRC03:10
*** rcernin has quit IRC03:10
*** psachin has joined #openstack-meeting03:17
*** jamesmcarthur has joined #openstack-meeting03:24
*** rcernin has joined #openstack-meeting03:25
*** ttsiouts_ has joined #openstack-meeting03:31
*** ttsiouts has quit IRC03:34
*** andrebeltrami has quit IRC03:39
*** ykatabam has joined #openstack-meeting03:39
*** yaawang has quit IRC03:40
*** yaawang has joined #openstack-meeting03:41
*** ociuhandu has joined #openstack-meeting03:44
*** rh-jelabarre has quit IRC03:48
*** ociuhandu has quit IRC03:49
*** tetsuro has quit IRC03:51
*** jmasud has quit IRC04:02
*** jmasud has joined #openstack-meeting04:14
*** ysandeep|afk is now known as ysandeep04:22
*** kevinz has joined #openstack-meeting04:42
*** ysandeep is now known as ysandeep|reboot04:49
*** ysandeep|reboot is now known as ysandeep04:53
*** jmasud has quit IRC04:55
*** jmasud has joined #openstack-meeting04:56
*** vishakha has quit IRC05:10
*** mnasiadka has quit IRC05:10
*** thgcorrea has quit IRC05:10
*** tinwood has quit IRC05:10
*** tetsuro has joined #openstack-meeting05:13
*** vishakha has joined #openstack-meeting05:15
*** mnasiadka has joined #openstack-meeting05:15
*** thgcorrea has joined #openstack-meeting05:15
*** tinwood has joined #openstack-meeting05:15
*** jamesmcarthur has quit IRC05:30
*** jamesmcarthur has joined #openstack-meeting05:30
*** ociuhandu has joined #openstack-meeting05:37
*** ociuhandu has quit IRC05:47
*** ysandeep is now known as ysandeep|brb05:49
*** jamesmcarthur has quit IRC05:53
*** gyee has quit IRC05:53
*** jmasud has quit IRC05:56
*** jmasud has joined #openstack-meeting06:11
*** ysandeep|brb is now known as ysandeep06:12
*** jmasud has quit IRC06:13
*** jmasud has joined #openstack-meeting06:15
*** dklyle has quit IRC06:26
*** ociuhandu has joined #openstack-meeting06:37
*** jamesmcarthur has joined #openstack-meeting06:43
*** ociuhandu has quit IRC06:43
*** jamesmcarthur has quit IRC06:47
*** maohongbo1 has joined #openstack-meeting06:51
*** maohongbo has quit IRC06:54
*** maohongbo1 is now known as maohongbo06:54
*** jamesmcarthur has joined #openstack-meeting06:55
*** jamesmcarthur has quit IRC06:59
*** links has joined #openstack-meeting07:00
*** jamesmcarthur has joined #openstack-meeting07:01
*** jhesketh has quit IRC07:04
*** jamesmcarthur has quit IRC07:05
*** jamesmcarthur has joined #openstack-meeting07:07
*** ociuhandu has joined #openstack-meeting07:09
*** jamesmcarthur has quit IRC07:11
*** slaweq has joined #openstack-meeting07:11
*** jamesmcarthur has joined #openstack-meeting07:13
*** maohongbo1 has joined #openstack-meeting07:14
*** maohongbo has quit IRC07:15
*** maohongbo1 is now known as maohongbo07:15
*** jamesmcarthur has quit IRC07:17
*** jamesmcarthur has joined #openstack-meeting07:19
*** rpittau|afk is now known as rpittau07:19
*** apetrich has joined #openstack-meeting07:21
*** jamesmcarthur has quit IRC07:23
*** maciejjozefczyk has joined #openstack-meeting07:24
*** ociuhandu has quit IRC07:30
*** ralonsoh has joined #openstack-meeting07:38
*** jamesmcarthur has joined #openstack-meeting07:46
*** jamesmcarthur has quit IRC07:46
*** jamesmcarthur has joined #openstack-meeting07:46
*** jamesmcarthur has quit IRC07:49
*** maohongbo has quit IRC07:49
*** maohongbo1 has joined #openstack-meeting07:49
*** jamesmcarthur has joined #openstack-meeting07:49
*** maohongbo1 is now known as maohongbo07:51
*** jamesmcarthur has quit IRC07:57
*** ysandeep is now known as ysandeep|lunch07:57
*** ociuhandu has joined #openstack-meeting08:04
*** ttsiouts_ has quit IRC08:11
*** e0ne has joined #openstack-meeting08:13
*** ttsiouts has joined #openstack-meeting08:21
*** tetsuro has quit IRC08:22
*** ociuhandu has quit IRC08:23
*** ociuhandu has joined #openstack-meeting08:23
*** ysandeep|lunch is now known as ysandeep08:25
*** ykatabam has quit IRC08:27
*** jamesmcarthur has joined #openstack-meeting08:28
*** e0ne_ has joined #openstack-meeting08:30
*** e0ne has quit IRC08:30
*** jmasud has quit IRC08:33
*** maciejjozefczyk has quit IRC08:37
*** ociuhandu has quit IRC08:45
*** ttsiouts has quit IRC08:47
*** maohongbo1 has joined #openstack-meeting08:48
*** maohongbo has quit IRC08:48
*** maohongbo1 is now known as maohongbo08:49
*** ykatabam has joined #openstack-meeting09:00
*** ttsiouts has joined #openstack-meeting09:00
*** ykatabam has quit IRC09:08
*** maohongbo1 has joined #openstack-meeting09:11
*** maohongbo has quit IRC09:12
*** maohongbo1 is now known as maohongbo09:12
*** ttsiouts has quit IRC09:16
*** ysandeep is now known as ysandeep|afk09:21
*** ociuhandu has joined #openstack-meeting09:25
*** maohongbo has quit IRC09:32
*** maohongbo has joined #openstack-meeting09:33
*** jamesmcarthur has quit IRC09:34
*** ttsiouts has joined #openstack-meeting09:39
*** ociuhandu has quit IRC09:43
*** ociuhandu has joined #openstack-meeting09:49
*** Liang__ has quit IRC09:52
*** jamesmcarthur has joined #openstack-meeting10:03
*** ykatabam has joined #openstack-meeting10:05
*** e0ne_ has quit IRC10:21
*** e0ne has joined #openstack-meeting10:22
*** rpittau is now known as rpittau|bbl10:30
*** brinzhang has quit IRC10:35
*** ociuhandu has quit IRC10:48
*** ociuhandu has joined #openstack-meeting10:48
*** ttsiouts has quit IRC10:49
*** ttsiouts has joined #openstack-meeting10:50
*** ociuhandu has quit IRC10:52
*** ykatabam has quit IRC11:09
*** ykatabam has joined #openstack-meeting11:15
*** bbowen_ has joined #openstack-meeting11:18
*** bbowen has quit IRC11:19
*** ociuhandu has joined #openstack-meeting11:23
*** e0ne has quit IRC11:25
*** e0ne has joined #openstack-meeting11:25
*** bbowen has joined #openstack-meeting11:37
*** bbowen_ has quit IRC11:39
*** rfolco has joined #openstack-meeting11:47
*** belmoreira has joined #openstack-meeting11:47
*** belmoreira has joined #openstack-meeting11:48
*** rh-jelabarre has joined #openstack-meeting11:54
*** rcernin has quit IRC12:11
*** ttsiouts has quit IRC12:12
*** rpittau|bbl is now known as rpittau12:19
*** e0ne has quit IRC12:23
*** e0ne has joined #openstack-meeting12:23
*** raildo has joined #openstack-meeting12:23
*** psachin has quit IRC12:26
*** ysandeep|afk is now known as ysandeep12:35
*** ttsiouts has joined #openstack-meeting12:42
*** ttsiouts has quit IRC12:48
*** ociuhandu has quit IRC12:48
*** ociuhandu has joined #openstack-meeting12:49
*** ttsiouts has joined #openstack-meeting13:23
*** ttsiouts has quit IRC13:32
*** ttsiouts has joined #openstack-meeting13:32
*** ttsiouts has quit IRC13:49
*** dklyle has joined #openstack-meeting13:55
*** yamamoto has joined #openstack-meeting13:55
*** mlavalle has joined #openstack-meeting14:00
slaweq#startmeeting neutron_drivers14:00
openstackMeeting started Fri Apr 17 14:00:33 2020 UTC and is due to finish in 60 minutes.  The chair is slaweq. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
njohnstono/14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: neutron_drivers)"14:00
openstackThe meeting name has been set to 'neutron_drivers'14:00
slaweqhi14:00
mlavalleo/14:00
haleybhi14:00
amotokihi14:01
ralonsohhi14:01
slaweqlets wait few more minutes for yamamoto and amotoki14:01
slaweqok, hi amotoki :)14:01
yamamotohi14:01
slaweqhi yamamoto14:01
slaweqok, so we can start14:01
slaweq#topic RFEs14:01
*** openstack changes topic to "RFEs (Meeting topic: neutron_drivers)"14:01
slaweqwe have 3 RFEs for today14:02
slaweqhttps://bugs.launchpad.net/neutron/+bug/186912914:02
openstackLaunchpad bug 1869129 in neutron "neutron accepts CIDR in security groups that are invalid in ovn" [Undecided,In progress] - Assigned to Jake Yip (waipengyip)14:02
slaweqwe discussed about it last time but we didn't make any agreement on it14:02
slaweqthere is my summary of our last discussion in comment #10 and some new comments from owner in comment #1114:03
njohnstonYeah, I would like to drop my proposal to add an api extension around /0 netmasks - if someone asks for it that's fine but I'd rather not solve a problem that doesn't really exist.14:05
slaweqI was thinking about it too and I'm not sure if we should change behaviour of API with config option (extension)14:06
*** ttsiouts has joined #openstack-meeting14:06
amotokiI missed the last meeitng. IMHO it looks better to continue to accept non-network address with netmask as CIDR not to break existing tools and basically it should be handled in the driver layer.14:06
*** ociuhandu has quit IRC14:07
mlavallenjohnston: +114:08
njohnstonyeah, I think the idea that the OVN driver code would silently translate the addresses OVN can't handle into addresses it can makes the most sense from a compatibility perspective14:08
slaweqamotoki: I also tend to choose this option and fix it on drivers side, without changes of existing API14:08
slaweqand maybe some doc update to explain it exactly what are the implications of using wrong cidrs14:09
*** moguimar has joined #openstack-meeting14:09
amotokianother idea/compromise which hits my mind is that we can convert such CIDR into a correct network address when stored in DB. it might affect less to existing tools perhaps.14:09
slaweqamotoki: it's what haleyb proposed last time14:09
ralonsohI don't agree with "hiding" a user input possible mistake14:10
ralonsohif we consider the current input is correct, then we should store it as-is in the DB14:10
*** ociuhandu has joined #openstack-meeting14:11
haleybi am flexible, we know we have to at least fix the driver, was thinking if not changing the current code would lead to duplicate SG rules?14:11
amotokiregarding a check for duplicate SG rules, I think we should improve the check.14:12
amotokiDuplicated rules are not what we expect14:12
haleybralonsoh: i don't think the input is incorrect, it's in a grey area, it's just that it won't be used as given, that was why i'd prefer changing it14:12
njohnstonamotoki: My main concern is that if a user creates a security group rule for 1.2.3.4/24 when they later list the sg rules it should still say 1.2.3.4/24, which means that we have to store it in the DB the way the user submitted it14:13
ralonsohexactly14:13
njohnstonotherwise a user can't be sure the rule they created is actually in the DB14:13
slaweqnjohnston: I agree with that14:13
haleybnjohnston: right, that is the only issue, guess noone is using IPv6 enough to notice my change :)14:13
amotokinjohnston: ralonsoh: I understand the concern.14:13
ralonsohif 1.2.3.4/24 and 1.2.3.10/24 is a duplicate rule in the backend, we need to handle this in there, in the driver14:14
slaweqmaybe we could add new attribute to rule, like "cidr" and store "fixed" cidr there14:14
amotokiif the neutron API returns different reponse, it would be confuing.14:14
slaweqso for e.g. 1.2.3.4/24 in this new field we would store 1.2.3.0/2414:14
ralonsohor we keep the current API or we modify it, making a rule check14:14
ralonsohbut nothing in the middle14:14
amotoki /24 means we only care the first 24 bits14:14
slaweqthis new field would be read-only14:14
*** TrevorV has joined #openstack-meeting14:15
njohnstonI think the idea of a 'normalized cidr' is a good one14:16
amotoki+114:16
ralonsohbut you rejected this idea last week!14:16
mlavallethat's ok, people can change opinions14:16
mlavalleI do all the time14:17
ralonsohthen cgoncalves can reply14:17
* njohnston is very good at changing opinions except when he isn't14:17
slaweqralonsoh: sorry, but I probably missed it somewhere last week14:17
njohnstonI like the idea of a net enw column because then we have a uniform behavior for all drivers14:17
njohnstonso compatibility is maintained14:18
slaweqralonsoh: but I really don't remember about proposal of adding new field to SG rule14:18
haleybso then the drivers would get the rule with this normalized cidr, correct?14:18
cgoncalvesmy view stands from last time this was discussed. I am just a single voice and a Neutron user, not developer14:18
ralonsohwe agreed to keep the API as is and change the problem we have in OVN14:18
ralonsohthat's all14:18
cgoncalvesralonsoh, +114:18
mlavalleeven14:18
ralonsohadding a "rule checker" will change the API14:18
mlavalleptls are allowed to change opinions14:18
slaweqralonsoh: I agree to not change exisitng API, but adding new field shouldn't be big problem14:18
njohnstonyes, this would not change the API except to add an extra field returned14:18
ralonsohor "hiding" the input rule, normalizing it14:18
amotokithe new field proposed is almost duplicated to the existing cidr field, but it clarifies what neutron actually recognizes.14:19
mlavallemakes the actual behavior visible14:19
slaweqamotoki: yes, it's something like to be "more verbose" to the user - You set 1.2.3.4/24 and we know about it but we will use 1.2.3.0/24 effectively14:19
ralonsohwe can do this on the fly, we don't need to store anything14:20
njohnstonand that's the thing - if we are going to normalize things it would be good to not make a secret about it.  that will also make very obvious to anyone who is looking that a rule resolves to 0.0.0.0/0 or whatever14:20
haleybright, when the driver asks we can convert14:20
slaweqyes, we can, and we are doing it indirectly e.g. in iptables driver now (iptables is doing it for us IIUC)14:21
slaweqbut with this new field we could be more verbose for users14:21
mlavalleit's not necessarily predictable behavior, but it becomes visible14:22
slaweqso here are possible options for this bug:14:25
cgoncalvesto keep in mind: unless the OVN bug is addressed in its driver (i.e. without relying on the normalization from neutron), the OVN bug will continue to exist in stable branches given that the normalization patch wouldn't be backportable14:25
slaweq1. fix it only on ovn driver, and silently convert cidr from rule to be good for ovn,14:25
slaweq2. add new api field and use it e.g. in ovn driver - and in fact in other drivers like iptables or ovs we can use this new field too probably14:26
slaweqI think that other possibilities are already rejected, right?14:27
cgoncalvesslaweq, is the OVN bug present in stable branches?14:27
slaweqcgoncalves: I'm not sure, but probably yes14:27
njohnstonslaweq: yes I think that is what we have narrowed it down to14:27
cgoncalvesslaweq, ok. if it is option 2 won't help for stable branches14:27
cgoncalvesmay I politely ask why don't someone fix the OVN driver and be done with it?14:28
yamamotowas "3. no change in api/db, fix ovn" rejected?14:28
slaweqcgoncalves: for stable branches we can fix it with silent conversion on backend side14:28
*** e0ne has quit IRC14:28
cgoncalvesyamamoto, +100000014:28
slaweqyamamoto: it's point 1) from my summary14:29
haleybi think 1 is two parts - 1a) fix the OVN driver (required), and 1b) change the API/RPC to give the normalized CIDR to drivers14:29
yamamoto"silently convert" in ovn?14:29
haleyb1a can be backported easily14:30
slaweqok, so I think I wasn't clear, by silently convert I meant convertion on ovn driver's side to apply what it can appect14:30
slaweqsorry for not being clear14:30
slaweqmy 1) is exactly what yamamoto proposed14:30
yamamotook14:30
haleybslaweq: +1 on that, which is what the iptables driver does for a few things14:30
*** ttsiouts has quit IRC14:31
*** ysandeep is now known as ysandeep|away14:31
cgoncalvesslaweq, ok, I agree with you. it is the same yamamoto suggested14:31
njohnstonI don't know if the openvswitch developers will be willing to fix OVN to accept what they may consider to be "incorrect" CIDRs, but if they do then we also don't know how long until that code is released and what customers may be using it.14:31
njohnstonSo that is why we are working around the OVN behavior in the neutron OVN driver by doing a conversion.  The only question is: do we be transparent tot he user about what is happening?14:31
slaweqnjohnston: yes, so IMO we can do it 2 steps:14:32
mlavalletransparency is always the best policy IMO14:32
slaweq1. fix in ovn driver only - and backport this fix to stable branches14:32
slaweq2. add api extension to add this normalized cidr field to SG rule14:33
njohnston+10014:33
slaweqthat will not be backported ofcourse14:33
mlavallein fact transparency should always be baked in our policies14:33
amotokitotally agree14:33
*** e0ne has joined #openstack-meeting14:34
amotoki2nd step would also give us the clear understanding on how drivers should behave.14:34
amotoki* to driver developers14:34
slaweqso lets vote if that 2 steps solution would be good to go with :)14:35
njohnston+114:35
amotoki+114:35
mlavalleI am good14:35
haleyb+114:36
*** ttsiouts has joined #openstack-meeting14:36
slaweqyamamoto: any thoughts?14:37
yamamotook for me, but i'm afraid the new field can confuse users even more. after all, the problem, if any, belongs to doc, IMO.14:38
cgoncalvesyamamoto, +114:38
slaweqok, so I will sumup in bug what we agreed here and I will mark it as approved RFE14:39
slaweqthx for great discussion14:39
slaweqnext one14:40
slaweqhttps://bugs.launchpad.net/neutron/+bug/187031914:40
openstackLaunchpad bug 1870319 in neutron "[RFE] Network cascade deletion API call" [Wishlist,Triaged] - Assigned to Slawek Kaplonski (slaweq)14:40
slaweqthis was in fact proposed by dulek from Kuryr team and we talked about it in Shanghai IIRC14:40
amotokiIIRC the main problem is the number of API calls and most of them are related to port deletion.14:42
slaweqI will probably need to write spec with description of all possible resources which should be deleted together with such force network delete14:42
slaweqamotoki: yes, that's the problem for Kuryr basically14:42
amotokiroughly speaking, there seems two ways: (1) cascade network deletion (2) bulk port delete14:43
slaweqas they need to make many API calls to cleanup14:43
amotoki(2) would reduce most API calls14:43
amotokiof course the cascade network deletion would be more friendly to API consumers, but it might be more complicated than bulk port deletion.14:44
slaweqseems that You are right, I can ask dulek if bulk port deletion would solve their problem14:44
njohnston++14:46
slaweqI pinged dulek, maybe he will join us soon14:46
amotokiboth options have a problem that what response code should return when we hit partial deletion failure.14:47
*** jamesmcarthur has quit IRC14:47
slaweqamotoki: I think that nova supports bulk vms deletion, no?14:47
*** jamesmcarthur has joined #openstack-meeting14:47
amotokiI am not sure at the moment14:47
*** ttsiouts has quit IRC14:48
amotokiit looks like "nova" CLI supports it but the API does not.14:48
slaweqahh, ok14:48
*** dulek has joined #openstack-meeting14:49
slaweqhi dulek :)14:49
duleko/14:49
slaweqwe are talking about https://bugs.launchpad.net/neutron/+bug/187031914:49
openstackLaunchpad bug 1870319 in neutron "[RFE] Network cascade deletion API call" [Wishlist,Triaged] - Assigned to Slawek Kaplonski (slaweq)14:49
dulekRight! So what's the problem? Need any info about use case we have in Kuryr?14:49
slaweqand we would like to know if  bulk port deletion would solve Kuryr biggest issue related to this cleanup14:49
dulekHa, the answer is most likely not what you'd wanted to hear - not really.14:50
*** ttsiouts has joined #openstack-meeting14:50
dulekOr partially.14:50
dulekThis is because when we're cleaning up a network in Kuryr, ports are subports of a trunk.14:51
dulekSo we cannot delete them before removing them from trunk.14:51
dulekSo bulk delete would improve stuff a bit, but we'd still get multiple calls here.14:51
dulekIf I'm not mistaken we need to remove them from a trunk one-by-one?14:52
amotokiIIUC we need to delete subport one-by-one now14:52
njohnstonany bulk port deletion solution would potentially have to account for some of the ports being trunk ports anyway14:52
amotokiI see. even if we implement bulk port delete, it should be cascade port deletetion14:53
duleknjohnston: True, but currently delete on a port that's a subport will fail.14:53
dulekSo if bulk-delete would work the same, we would still need to do n calls, where n is number of ports.14:54
amotokiIn my understanding, the main problem is the number of API calls and most of them are related to port deletion.14:56
amotokiif the bulk port deletion is supported including cascading port deletion (of subports), it would reduce most of the APi calls.14:56
dulekThat is true.14:57
njohnstonwhat if we added an option to port deletion that would optionally allow the deletion behavior to include removing the port from the trunk?  Then the bulk port deletion could be called with that option supplied for all ports.14:57
amotokiWhile we haven't investigated which is simpler, the cascade network delete or the bulk port delete with cascade delete, can either of them addresses your problem?14:57
dulekBasically it doesn't matter too much if we're doing 3 calls or 1 call, but if we're doing n + x calls, where n is number of ports.14:58
amotokiof course, I understand the cascade network delete woudl be better for you.14:58
dulekamotoki: Sure, 1 call is better than 3 (bulk port, subnet, network), but it's totally a huge improvement over what we have now.14:59
njohnstonif we did the bulk port delete with trunk deletion added, then the only remaining steps would be Detach the subnet from the router and Remove the network14:59
dulekRight, forgot about router operation. Anyway it's still constant number of ops, not linear.14:59
amotokinjohnston: i think so15:00
njohnstonyep15:00
slaweqnjohnston: true, so probably if we would have bulk port deletion we would be close to cascade network deletion as well15:00
slaweqok, we are over time now15:00
slaweqwe will get back to this one15:00
slaweqthx for attendance15:01
mlavalleo/15:01
amotokio/15:01
ralonsohbye15:01
slaweqand have a great weekend all :)15:01
slaweqo/15:01
slaweq#endmeeting15:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"15:01
openstackMeeting ended Fri Apr 17 15:01:12 2020 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/neutron_drivers.2020-04-17-14.00.html15:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/neutron_drivers.2020-04-17-14.00.txt15:01
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2020/neutron_drivers.2020-04-17-14.00.log.html15:01
*** mlavalle has left #openstack-meeting15:01
*** ociuhandu has quit IRC15:10
*** andrebeltrami has joined #openstack-meeting15:12
*** belmoreira has quit IRC15:12
*** ociuhandu has joined #openstack-meeting15:13
*** ricolin has quit IRC15:19
*** moguimar has quit IRC15:24
*** moguimar has joined #openstack-meeting15:26
*** ociuhandu has quit IRC15:40
*** ociuhandu has joined #openstack-meeting15:42
*** ociuhandu has quit IRC15:47
*** jamesmcarthur has quit IRC15:58
*** jamesmcarthur has joined #openstack-meeting15:59
*** dustinc has joined #openstack-meeting16:00
*** e0ne has quit IRC16:04
*** e0ne_ has joined #openstack-meeting16:04
*** ociuhandu has joined #openstack-meeting16:05
*** yamamoto has quit IRC16:06
*** yamamoto has joined #openstack-meeting16:07
*** yamamoto has quit IRC16:08
*** yamamoto has joined #openstack-meeting16:08
*** yamamoto has quit IRC16:08
*** yamamoto has joined #openstack-meeting16:09
*** yamamoto has quit IRC16:09
*** yamamoto has joined #openstack-meeting16:09
*** ttsiouts has quit IRC16:12
*** yamamoto has quit IRC16:13
*** ociuhandu has quit IRC16:15
*** ociuhandu has joined #openstack-meeting16:16
*** rpittau is now known as rpittau|afk16:17
*** ociuhandu has quit IRC16:21
*** jmasud has joined #openstack-meeting16:26
*** ianychoi_ has joined #openstack-meeting16:29
*** armax has quit IRC16:29
*** armax_ has joined #openstack-meeting16:30
*** armax_ is now known as armax16:31
*** gyee has joined #openstack-meeting16:31
*** ianychoi has quit IRC16:31
*** yaawang_ has joined #openstack-meeting16:33
*** yaawang has quit IRC16:34
*** kevinz has quit IRC16:40
*** ociuhandu has joined #openstack-meeting16:40
*** jmasud has quit IRC16:55
*** jmasud has joined #openstack-meeting16:57
*** ociuhandu has quit IRC17:03
*** ttsiouts has joined #openstack-meeting17:04
*** igordc has joined #openstack-meeting17:04
*** yamamoto has joined #openstack-meeting17:08
*** igordc has quit IRC17:09
*** yamamoto has quit IRC17:16
*** alecuyer has left #openstack-meeting17:19
*** links has quit IRC17:26
*** ociuhandu has joined #openstack-meeting17:30
*** e0ne_ has quit IRC17:38
*** e0ne has joined #openstack-meeting17:38
*** jmasud has quit IRC17:43
*** ociuhandu has quit IRC17:43
*** jmasud has joined #openstack-meeting17:48
*** e0ne_ has joined #openstack-meeting17:49
*** e0ne has quit IRC17:49
*** ralonsoh has quit IRC17:53
*** jmasud has quit IRC18:05
*** jamesmcarthur has quit IRC18:07
*** jamesmcarthur has joined #openstack-meeting18:08
*** ociuhandu has joined #openstack-meeting18:09
*** jamesmcarthur has quit IRC18:13
*** ttsiouts has quit IRC18:14
*** ociuhandu has quit IRC18:22
*** darvon has quit IRC18:23
*** ociuhandu has joined #openstack-meeting18:23
*** darvon has joined #openstack-meeting18:24
*** ociuhandu has quit IRC18:28
*** jmasud has joined #openstack-meeting18:30
*** Lucas_Gray has joined #openstack-meeting18:38
*** jamesmcarthur has joined #openstack-meeting18:42
*** e0ne_ has quit IRC18:56
*** e0ne has joined #openstack-meeting18:56
*** jamesmcarthur has quit IRC19:00
*** jamesmcarthur has joined #openstack-meeting19:01
*** jamesmcarthur has quit IRC19:15
*** moguimar has quit IRC19:22
*** ttsiouts has joined #openstack-meeting19:26
*** e0ne has quit IRC19:26
*** raildo has quit IRC19:30
*** ociuhandu has joined #openstack-meeting19:35
*** ociuhandu has quit IRC19:42
*** ttsiouts has quit IRC19:47
*** ttsiouts has joined #openstack-meeting19:47
*** raildo has joined #openstack-meeting19:50
*** jamesmcarthur has joined #openstack-meeting20:02
*** TrevorV has quit IRC20:04
*** jmasud has quit IRC20:27
*** dustinc has quit IRC20:29
*** ociuhandu has joined #openstack-meeting20:45
*** ociuhandu has quit IRC21:06
*** ociuhandu has joined #openstack-meeting21:08
*** rfolco has quit IRC21:11
*** ociuhandu has quit IRC21:13
*** yamamoto has joined #openstack-meeting21:14
*** jmasud has joined #openstack-meeting21:15
*** yamamoto has quit IRC21:18
*** jmasud has quit IRC21:29
*** jmasud has joined #openstack-meeting21:31
*** rh-jelabarre has quit IRC21:31
*** raildo has quit IRC21:35
*** jmasud has quit IRC21:44
*** jamesmcarthur has quit IRC21:47
*** ykatabam has quit IRC21:55
*** ttsiouts has quit IRC21:56
*** ykatabam has joined #openstack-meeting21:56
*** jmasud has joined #openstack-meeting22:02
*** ykatabam has quit IRC22:24
*** ociuhandu has joined #openstack-meeting22:32
*** Lucas_Gray has quit IRC22:32
*** ociuhandu has quit IRC22:38
*** ttsiouts has joined #openstack-meeting22:43
*** ttsiouts has quit IRC22:52
*** igordc has joined #openstack-meeting23:08
*** gyee has quit IRC23:10
*** igordc has quit IRC23:27
*** ykatabam has joined #openstack-meeting23:52

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