Friday, 2019-02-22

*** hongbin has quit IRC00:06
*** sdake_ has quit IRC00:08
*** slaweq has joined #openstack-meeting00:11
*** slaweq has quit IRC00:16
*** sdake has joined #openstack-meeting00:25
*** bbowen has quit IRC00:31
*** bbowen has joined #openstack-meeting00:31
*** lbragstad has quit IRC00:35
*** zhubx007 has quit IRC00:37
*** zhubx007 has joined #openstack-meeting00:37
*** lbragstad has joined #openstack-meeting00:39
*** yamamoto has quit IRC00:41
*** igordc has joined #openstack-meeting00:43
*** yamamoto has joined #openstack-meeting00:44
*** yamamoto has quit IRC00:48
*** markvoelker has joined #openstack-meeting00:53
*** gyee has quit IRC00:54
*** Liang__ has joined #openstack-meeting00:58
*** macza has quit IRC01:04
*** bbowen has quit IRC01:21
*** takamatsu_ has joined #openstack-meeting01:26
*** markvoelker has quit IRC01:26
*** takamatsu has quit IRC01:26
*** ijw has quit IRC01:28
*** ijw has joined #openstack-meeting01:29
*** ijw has quit IRC01:30
*** ijw has joined #openstack-meeting01:31
*** ijw has quit IRC01:39
*** mjturek has quit IRC01:40
*** yamamoto has joined #openstack-meeting01:41
*** ijw has joined #openstack-meeting01:41
*** sdake has quit IRC01:44
*** sdake has joined #openstack-meeting01:45
*** sdake has quit IRC01:45
*** sdake has joined #openstack-meeting01:45
*** KurtB has quit IRC01:58
*** slaweq has joined #openstack-meeting02:11
*** slaweq has quit IRC02:15
*** erlon__ has quit IRC02:19
*** markvoelker has joined #openstack-meeting02:23
*** Liang__ has quit IRC02:24
*** rfolco|rover has quit IRC02:30
*** sdake has quit IRC02:32
*** sdake has joined #openstack-meeting02:35
*** ijw has quit IRC02:35
*** sdake_ has joined #openstack-meeting02:38
*** sdake has quit IRC02:38
*** lbragstad_ has joined #openstack-meeting02:54
*** lbragstad has quit IRC02:55
*** markvoelker has quit IRC02:57
*** yamamoto has quit IRC02:57
*** whoami-rajat has joined #openstack-meeting02:57
*** vishakha has joined #openstack-meeting02:58
*** yamamoto has joined #openstack-meeting03:02
*** sdake_ has quit IRC03:03
*** psachin has joined #openstack-meeting03:04
*** sdake has joined #openstack-meeting03:09
*** apetrich has quit IRC03:16
*** janki has joined #openstack-meeting03:20
*** sdake has quit IRC03:33
*** akhil_jain has joined #openstack-meeting03:42
*** markvoelker has joined #openstack-meeting03:54
*** yamamoto has quit IRC03:56
*** ekcs has joined #openstack-meeting03:57
*** yamamoto has joined #openstack-meeting03:59
ekcs#startmeeting congressteammeeting04:01
openstackMeeting started Fri Feb 22 04:01:55 2019 UTC and is due to finish in 60 minutes.  The chair is ekcs. Information about MeetBot at http://wiki.debian.org/MeetBot.04:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.04:01
*** openstack changes topic to " (Meeting topic: congressteammeeting)"04:01
openstackThe meeting name has been set to 'congressteammeeting'04:01
ekcshi. topics here as usual: https://etherpad.openstack.org/p/congress-meeting-topics04:02
akhil_jainekcs: Hi!04:02
ekcshi akhil_jain ! happy friday hope things are well.04:02
akhil_jainHappy friday, yes everything fine. what about you?04:03
ekcsI’m doing alright!04:03
ekcsok so first a quick reminder:feature freeze04:03
ekcs7 March 201904:03
ekcsRC1 due 21 March 201904:04
ekcslet’s dive in to the topics then.04:04
ekcs#topic Managing alarms04:04
*** openstack changes topic to "Managing alarms (Meeting topic: congressteammeeting)"04:04
ekcsakhil_jain: I assume that’s your topic?04:04
*** yamamoto has quit IRC04:05
akhil_jainYes right, ekcs  as already discussed on mail. According to me. there can be faulty situation04:05
ekcsyup. do you have a sample policy and scenario to help our analysis?04:07
akhil_jainMy usecase is. when an alarm is raised and it stays in congress with ACTIVE state. so lets consider operator created policy1 and handled the alarm situation. BUt state of alarm is still ACTIVE. so when he creates POLICY2 it can  again execute actions based on that alarm04:07
akhil_jainwhich may have been handled by  policy104:08
ekcsright. ok I pulled up our email.04:09
akhil_jainits 1.3 according to your mail. The one you specified to make new table04:09
ekcsso the situation is either 3 or 4 in the email04:09
ekcs3. Alarms which had been activated and triggered some action, but the04:09
ekcsalarm remains active because the action do not resolve the alarm.04:09
ekcs4. Alarms which had been activated and triggered some action, and the04:09
ekcsaction is in the process of resolving the alarm, but in the mean time the04:09
ekcsalarm remains active.04:09
akhil_jainyes right04:10
*** diablo_rojo has quit IRC04:10
*** slaweq has joined #openstack-meeting04:11
ekcsso.. i want to consider a slightly different scenario. what if policy1 an policy2 have been active the whole time. that seems like the usual case.04:11
akhil_jainalso we can publish that discussion on openstack-discuss to get input from various developers as well04:11
ekcsthen when the alarm is activated, it would trigger action from BOTH policy1 and policy204:12
akhil_jainyes right even that can be harmful in various scenarios04:12
ekcsok. so let’s focus on the simple case first that does not have to do with timing and ordering.04:13
akhil_jainlike 1 policy pausing vms and other evacuating04:13
ekcshow would you like the system to behave in the case that alarm activates while both policy1 and policy2 are in place?04:13
*** tetsuro has joined #openstack-meeting04:14
akhil_jainthats a tough question :D anyways i would like only one policy to be executed on one alarm04:14
akhil_jainthat will cause issue of priority04:15
ekcsI see. so… in my opinion in this case it’s up to the policy writer to write the policy in a way which decides what happens.04:16
*** slaweq has quit IRC04:16
ekcsfor example, if the writer wantns both actions to trigger, then she can write execute[action1] :- alarm1; execute[action2] :- alarm204:16
ekcssorry i meant execute[action1] :- alarm1; execute[action2] :- alarm104:17
ekcshowever, if she does not want both to trigger, then she can write something like execute[action1] :- alarm1, severity('low'); execute[action2] :- alarm1, severity('high')04:18
akhil_jaini am not sure if policy writer can evaluate whether to take action on which alarm. they will get just list of alarms. lets suppose one alarm is 15 days old and still saying status=active. which was raised because compute node1 was down. But in actual the compute node1 is up now. as operator resolved the issue. but based on alarm policy writer can harm that node or vms created on that04:20
akhil_jainsaving alarms and computing actions on those is bit complex and can be wrongly used in real time scenarios.04:22
ekcsok that makes sense.04:22
akhil_jainreaching to one solution will involve other communities as well i think. maybe monasca aodh n all04:23
ekcsso would 1.3 solve the problem? one table for all active alarm. another table for most recent alarms.04:23
akhil_jainyes maybe one table for all alarms and other for those on which policy is executed. i am not sure04:23
*** imsurit_ofc has joined #openstack-meeting04:24
akhil_jainor one field of policy_executed with alarm. dont know just a thought04:24
ekcsyea there are several possibilities.04:25
ekcsbut i’m still trying to isolate the problem. is it distinguishing between new and old? or distinguishing between action taken and action not taken.04:25
akhil_jainalso gmann wants to discuss it in PTG if you are planning one04:25
ekcsgot it.04:26
ekcsthat’s great.04:26
akhil_jaini would say both are the possibilities04:26
akhil_jain1.new n old04:26
akhil_jain2. action taken or not04:27
*** markvoelker has quit IRC04:27
akhil_jainhopefully i will be available too. for the PTG04:28
ekcsok. hopefully we can work through examples to see whether both are needed or just one. we can certainly implement things for both, but if one suffices then it’d be good to know it.04:29
ekcsin general, I think it’s a good idea to leave the flexibility in the hands of the policy writer.04:30
ekcsperhaps adding congress functions as possible actions would be one solution.04:31
akhil_jaini didnt get the last point04:32
ekcssomething like this:04:33
ekcspolicy1:04:33
ekcsexecute[add tuple handled('alarm1') to congress] :- alarm104:33
ekcsexecute[action1] :- alarm1, NOT handled('alarm1')04:33
ekcspolicy2:04:33
ekcsexecute[add tuple handled(alarm1) to congress] :- alarm104:33
ekcsexecute[action2] :- alarm1, NOT handled('alarm1')04:33
ekcsthat’s a way for the policy writer to say: remember which alarm was already handled, and don’t do something again on the same alarm.04:34
akhil_jainright seems good04:35
akhil_jainadding another table can help this. also present thing will not be effected04:36
ekcswell. unfortunately that still doesn’t solve the problem when both policy are active at the same time. the alarm will trigger both at the same time.04:37
ekcsi hope to understand some more why policy writers cannot make sure to add conditions to their rules so that one alarm cannot trigger both actions.04:38
ekcswho are the ones expected to write the policy?04:38
akhil_jaini am not sure about that. i am not much into deployment side04:39
ekcsok. is there any way to find out who write the policy in projected use case? I think the policy workflow really changes our solutions.04:41
ekcsfor example, if it’s one “person” writing all the policy, then it’s not hard to make sure multiple rules don’t trigger on the same alarm.04:42
ekcsbut if it’s many different “people” writing policy independently, then it’s very hard to make sure of the same thing.04:42
ekcsanother factor is: how often are the policies changed? is it expected to be changed frequently by the operator? or more just operate the way its deployed?04:43
ekcsoh and yes it’s ok to share that email on ML.04:44
akhil_jainyes, there are serious multiple cases .04:45
ekcsI think maybe the next step is to start an etherpad or something to start documenting the problem scenarios and also possible solutions.04:45
ekcsand the closer we can understand the real policies and policy writing workflow the better we can solve the problems =)04:46
akhil_jainyes everytime reaching on one soln. is alterted again on thinking next time04:46
ekcshaha well this is an important and interesting problem. glad we’re discussing and hopefully solving.04:47
ekcsshould we move on to see if we can squeeze in the other topics before time’s up?04:47
akhil_jainyes right04:47
ekcsok =)04:47
ekcs#topic Adding created_at in nova servers04:47
*** openstack changes topic to "Adding created_at in nova servers (Meeting topic: congressteammeeting)"04:47
ekcswanna start us off akhil_jain ?04:48
akhil_jainoh yes. you already said its good to go. but is it possible to calcyulate based on current code to evealuate if server is older than one month or so04:49
*** lpetrut has joined #openstack-meeting04:49
akhil_jainjust adding created_at will be enough?04:49
akhil_jaini am not sure if operators will work04:50
ekcsoh hmm. is the created_at reported by nova api?04:51
akhil_jainyes04:51
akhil_jainfield name is created04:51
ekcswhy do we need to calculate then?04:52
ekcssorry just clarifying so I understdand what the considerations are.04:52
ekcsooooh04:52
ekcsI get it now.04:52
ekcswe’re going to add the field.04:52
akhil_jainpolicy automacially calculating if  servers are old enough n execute action on them04:52
ekcsbut the policy writer wants to find out whether a server is more than 1 month old. that requires builtins to handle parsing and calculating time.04:53
akhil_jainyes04:53
ekcsright. I’ll need to check the current builtins to see whether it handles the case.04:53
ekcsi’ll get back to you on that.04:53
akhil_jainok great, thanks04:54
akhil_jainlast topic then, about tacker test04:54
ekcsbtw this is one case for why i have high hopes for the postgres version. they have already built all the builtins. and even when they haven’t someone online already built an extension for it.04:54
akhil_jainyes i guess that can solve this04:54
ekcsmuch harder for us to keep up wth what’s needed and much harder for the users when we use our own language and policy engine.04:55
ekcsok anyway moving on then like you said04:55
ekcs#topic tacker test04:55
*** openstack changes topic to "tacker test (Meeting topic: congressteammeeting)"04:55
ekcsso a couple things.04:55
akhil_jaini saw your patch. i will test using same and add another etst for vnf as well04:55
ekcs1. i added zuul config to enable tacker plugin in CI job. but it’s failing right now.04:55
akhil_jainyes saw that04:56
ekcsi’m not sure why yet.04:56
ekcsand yes I added a patch just to test whether the generic approach works for this case. I think it should but haven’t been able to tell because of the devstnack plugin failure.04:56
ekcshttps://review.openstack.org/#/c/638516/1/congress_tempest_plugin/tests/scenario/congress_datasources/test_tacker.py04:56
akhil_jainhm thats y i will test it on my env and let you kniow04:57
ekcsok great!04:57
akhil_jainearlier i didnt understood. now got it. thanks04:57
ekcsawesome.04:57
ekcsone last thing is:04:58
ekcsif you have features you want to finish by feature freeze and don’t have time for the tacker tempest test, then we could merge the driver by FF and then merge the tempest test before RC1. not preferred but in a pinch it can be done.04:58
ekcsjust keep that in mind in prioritizing what you’d like to do =)04:59
ekcsthat’s all from me.04:59
akhil_jainyes any reviews on tacker driver. i can complete that first. plus i am completeing tempest test as well05:00
ekcsok. I think the tacker driver is good to go. I was just waiting for tempest before merging. but if we can merge that first if tempest not ready by FF.05:00
akhil_jainnothing else from my side.05:00
ekcsok then. well time’s up too.05:01
akhil_jainok sounds good to me05:01
ekcs#endmeeting05:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"05:01
openstackMeeting ended Fri Feb 22 05:01:17 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)05:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2019/congressteammeeting.2019-02-22-04.01.html05:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2019/congressteammeeting.2019-02-22-04.01.txt05:01
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2019/congressteammeeting.2019-02-22-04.01.log.html05:01
ekcshave a great weekend!05:01
akhil_jainthanks and happy weekend!05:01
ekcs=)05:02
*** vishalmanchanda has joined #openstack-meeting05:03
*** slaweq has joined #openstack-meeting05:11
*** yamamoto has joined #openstack-meeting05:12
*** slaweq has quit IRC05:15
*** yamamoto has quit IRC05:16
*** markvoelker has joined #openstack-meeting05:24
*** lpetrut has quit IRC05:25
*** gmann has quit IRC05:28
*** ekcs has quit IRC05:34
*** ociuhandu has joined #openstack-meeting05:36
*** yamamoto has joined #openstack-meeting05:37
*** ociuhandu has quit IRC05:40
*** lpetrut has joined #openstack-meeting05:54
*** markvoelker has quit IRC05:58
*** akhil_jain has left #openstack-meeting06:01
*** dougwig has joined #openstack-meeting06:22
*** Luzi has joined #openstack-meeting06:41
*** sridharg has joined #openstack-meeting06:42
*** yamamoto has quit IRC06:50
*** yamamoto has joined #openstack-meeting06:50
*** markvoelker has joined #openstack-meeting06:55
*** sdake has joined #openstack-meeting06:59
*** slaweq has joined #openstack-meeting07:11
*** igordc has quit IRC07:12
*** slaweq has quit IRC07:15
*** markvoelker has quit IRC07:28
*** e0ne has joined #openstack-meeting07:29
*** sdake has quit IRC07:33
*** e0ne has quit IRC07:43
*** e0ne has joined #openstack-meeting07:44
*** aojea has joined #openstack-meeting07:44
*** e0ne has quit IRC07:44
*** ShilpaSD has quit IRC07:48
*** e0ne has joined #openstack-meeting07:50
*** belmoreira has quit IRC07:54
*** yamamoto has quit IRC07:56
*** yamamoto has joined #openstack-meeting07:58
*** kopecmartin|off is now known as kopecmartin08:00
*** yamamoto has quit IRC08:02
*** belmoreira has joined #openstack-meeting08:05
*** lbragstad_ has quit IRC08:07
*** slaweq has joined #openstack-meeting08:08
*** yamamoto has joined #openstack-meeting08:09
*** e0ne has quit IRC08:10
*** yamamoto has quit IRC08:13
*** sdake has joined #openstack-meeting08:17
*** tssurya has joined #openstack-meeting08:18
*** yamamoto has joined #openstack-meeting08:22
*** markvoelker has joined #openstack-meeting08:25
*** apetrich has joined #openstack-meeting08:26
*** yaawang has joined #openstack-meeting08:50
*** jiaopengju has quit IRC08:54
*** markvoelker has quit IRC08:59
*** ociuhandu has joined #openstack-meeting09:10
*** sdake has quit IRC09:26
*** yamamoto has quit IRC09:28
*** tetsuro has quit IRC09:33
*** electrofelix has joined #openstack-meeting09:36
*** stephenfin is now known as finucannot09:48
*** markvoelker has joined #openstack-meeting09:56
*** takamatsu_ has quit IRC10:04
*** gibi is now known as giblet10:04
*** takamatsu has joined #openstack-meeting10:05
*** yamamoto has joined #openstack-meeting10:08
*** yamamoto has quit IRC10:13
*** niska has quit IRC10:15
*** e0ne has joined #openstack-meeting10:19
*** niska has joined #openstack-meeting10:23
*** takamatsu_ has joined #openstack-meeting10:23
*** takamatsu has quit IRC10:24
*** markvoelker has quit IRC10:28
*** sridharg has quit IRC10:30
*** rcernin has quit IRC10:31
*** sridharg has joined #openstack-meeting10:43
*** takamatsu_ has quit IRC10:48
*** takamatsu has joined #openstack-meeting10:49
*** erlon has joined #openstack-meeting10:54
*** takamatsu has quit IRC10:54
*** takamatsu has joined #openstack-meeting10:58
*** macza has joined #openstack-meeting11:09
*** sdake has joined #openstack-meeting11:11
*** a-pugachev has joined #openstack-meeting11:11
*** macza has quit IRC11:14
*** markvoelker has joined #openstack-meeting11:25
*** yamamoto has joined #openstack-meeting11:30
*** yamamoto has quit IRC11:34
*** priteau has joined #openstack-meeting11:46
*** bbowen has joined #openstack-meeting11:48
*** gmann has joined #openstack-meeting11:49
*** imsurit_ofc has quit IRC11:58
*** erlon_ has joined #openstack-meeting11:58
*** markvoelker has quit IRC11:59
*** erlon has quit IRC11:59
*** janki has quit IRC12:01
*** vishalmanchanda has quit IRC12:02
*** sdake_ has joined #openstack-meeting12:03
*** sdake has quit IRC12:03
*** rfolco|rover has joined #openstack-meeting12:06
*** raildo has joined #openstack-meeting12:11
*** yamamoto has joined #openstack-meeting12:16
*** EmilienM is now known as EvilienM12:27
*** priteau has quit IRC12:31
*** priteau has joined #openstack-meeting12:39
*** liuyulong has joined #openstack-meeting12:49
*** _pewp_ has quit IRC12:51
*** _pewp_ has joined #openstack-meeting12:52
*** markvoelker has joined #openstack-meeting12:56
*** ociuhandu has quit IRC13:01
*** mriedem has joined #openstack-meeting13:10
*** markvoelker has quit IRC13:28
*** psachin has quit IRC13:35
*** awaugama has joined #openstack-meeting13:41
*** artom is now known as temka13:43
*** yamamoto has quit IRC13:43
*** yamamoto has joined #openstack-meeting13:43
*** sdake_ has quit IRC13:51
*** mlavalle has joined #openstack-meeting13:58
mlavalle#startmeeting neutron_drivers14:00
openstackMeeting started Fri Feb 22 14:00:46 2019 UTC and is due to finish in 60 minutes.  The chair is mlavalle. 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: neutron_drivers)"14:00
openstackThe meeting name has been set to 'neutron_drivers'14:00
njohnstono/14:00
yamamotohi14:00
amotokio/14:00
mlavalleHow are you all?14:01
slaweqhi14:01
slaweqgreat :)14:01
njohnstonslept through the alarm, so just woke up ;-)14:01
haleybhi14:01
mlavalleeverybody is here14:02
mlavalleso let's get rolling14:02
mlavalle#topic RFEs14:02
*** openstack changes topic to "RFEs (Meeting topic: neutron_drivers)"14:02
mlavalleFirst up is https://bugs.launchpad.net/neutron/+bug/181711914:03
openstackLaunchpad bug 1817119 in neutron "[rfe] add rbac for security groups" [Wishlist,In progress] - Assigned to Doug Wiegley (dougwig)14:03
mlavalleThe description is sparse... but there are patches for it already14:03
mlavallehere's the proposed doc: https://review.openstack.org/#/c/635311/13/doc/source/admin/config-rbac.rst14:04
*** lbragstad_ has joined #openstack-meeting14:05
slaweqfor me it's completly fine - I just asked dougwig to fill rfe to have everything done right from this procedural side :)14:06
mlavalleyeap, thanks for that14:06
njohnstonwhat I really like about this is that it takes one of the things fwaas tried to achieve and realizes it in core neutron14:07
njohnstonin a simple and straightforward way14:07
*** lbragstad_ is now known as lbragstad14:07
mlavalleI warned him last night I was bringing it up today in the meeting, in case there were questions14:07
amotokigenerally it makes sense. on the ohter hand, it reminds me of fwaas-v2. what do you think about it?14:07
amotokinjohnston already mentioned the similar point :)14:07
mlavallewhether this should be implemented in fwaas-2?14:08
njohnstonwell, it's less complicated than how fwaas v2 does things, and as we know customer uptake of fwaas is very limited.  I personally think it is smart to pull this in to core neutron14:08
amotokiI believe it is worth discussed14:09
amotokiI am okay to support RBAC in security groups API  in neutron because both RBAC and SG exist in neutron and it does not change the SG behavior model.14:09
njohnstonI don't want this to become a "what is the future of fwaas" but fwaas is in sort of a special position because it was built to compete with a core neutron function - security groups.  Both fwaas and security groups have evolved over the years, grown and enhanced over time.  I see this as an extension of that.14:10
mlavallethe other consideration is that I don't know how much manpower we have left in fwaas14:10
njohnstonmlavalle: +114:10
slaweqexactly, and sg aren't deprecated or something like that so I don't see any reason why we should not accept new feature for it14:11
mlavallethe truth is that here we have a cocnrete proposal, that in my opinion makes sense without breaking anything and we have the body to implement it14:11
slaweqmlavalle++14:11
amotokiI second this14:11
njohnstonmlavalle++14:11
haleybmakes sense to me too, and dougwig's been great at getting stuff done and fixing things lately too14:11
yamamoto+114:11
mlavalleok, approved by ovation14:12
* mlavalle updating the RFE14:12
amotoki:)14:12
mlavalleNext one is https://bugs.launchpad.net/neutron/+bug/181593314:14
openstackLaunchpad bug 1815933 in neutron "[RFE] Allow bulk-tagging of resources" [Wishlist,New]14:14
mlavallewe discussed this one last week14:14
mlavalleamotoki: did you have a chance to send message to ML?14:14
amotokisorry, I failed to find time to send it to the ML due to busy week....14:15
mlavalleno problem14:15
mlavalleif you lack bandwidth, I can start the thread14:15
mlavallejust let me know14:15
amotokimlavalle: thanks. I am writing a draft now, so I will take care of it.14:16
mlavalleamotoki: thank you very much!14:16
mlavalleThat's it for today's RFEs14:17
*** jamesmcarthur has joined #openstack-meeting14:17
mlavalle#topic On demand agenda14:17
*** openstack changes topic to "On demand agenda (Meeting topic: neutron_drivers)"14:17
mlavalleralonsoh added a topic to the agenda in regards https://bugs.launchpad.net/neutron/+bug/181534514:18
openstackLaunchpad bug 1815345 in neutron "neutron doesnt delete port binding level when deleting an inactive port binding" [Medium,In progress] - Assigned to Adrian Chiris (adrian.chiris)14:18
*** sdake has joined #openstack-meeting14:18
*** _pewp_ has quit IRC14:18
mlavalleI don't think it is necessary to discuss it here, but I would encourage the team to comment in the patch https://review.openstack.org/#/c/634276/14:19
mlavallewhich I intend to do later today14:19
slaweqok14:19
mlavalleanything else we should discuss today?14:20
yamamotonothing from me14:20
*** _pewp_ has joined #openstack-meeting14:20
amotokime neither14:20
slaweqnot from me14:21
mlavalleok, amotoki, yamamoto and slaweq, you can go and enjoy your weekends14:21
mlavallenjohnston, haleyb and I have to toil a little longer14:21
slaweqmlavalle: thx :) have a great weekend14:21
njohnstonhave a great weekend all!14:21
mlavalle#endmeeting14:22
yamamotogood night14:22
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings/"14:22
amotokihehe :) have a nice weekend all14:22
openstackMeeting ended Fri Feb 22 14:22:08 2019 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:22
openstackMinutes:        http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-02-22-14.00.html14:22
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-02-22-14.00.txt14:22
openstackLog:            http://eavesdrop.openstack.org/meetings/neutron_drivers/2019/neutron_drivers.2019-02-22-14.00.log.html14:22
*** priteau has quit IRC14:25
*** markvoelker has joined #openstack-meeting14:25
*** eharney has joined #openstack-meeting14:25
*** jamesmcarthur has quit IRC14:26
*** cmurphy is now known as cmorpheus14:27
*** cheng1 has joined #openstack-meeting14:35
*** bnemec is now known as beekneemech14:39
*** priteau has joined #openstack-meeting14:40
*** jamesmcarthur has joined #openstack-meeting14:40
*** sdake has quit IRC14:43
*** sdake has joined #openstack-meeting14:45
*** dklyle has quit IRC14:46
*** david-lyle has joined #openstack-meeting14:46
*** mjturek has joined #openstack-meeting14:54
*** hongbin has joined #openstack-meeting14:54
*** efried is now known as fried_rice14:56
*** markvoelker has quit IRC14:59
*** _pewp_ has quit IRC15:03
*** _pewp_ has joined #openstack-meeting15:04
*** mlavalle has left #openstack-meeting15:06
*** mjturek has quit IRC15:13
*** Luzi has quit IRC15:16
*** _pewp_ has quit IRC15:17
*** sdake has quit IRC15:21
*** sdake has joined #openstack-meeting15:22
*** mjturek has joined #openstack-meeting15:26
*** priteau has quit IRC15:27
*** david-lyle is now known as dklyle15:33
*** mjturek has quit IRC15:35
*** vishakha has quit IRC15:36
*** mjturek has joined #openstack-meeting15:36
*** _pewp_ has joined #openstack-meeting15:40
*** dklyle has quit IRC15:43
*** david-lyle has joined #openstack-meeting15:43
*** lbragstad is now known as elbragstad15:47
*** yamamoto has quit IRC15:51
*** cheng1 has quit IRC15:52
*** markvoelker has joined #openstack-meeting15:56
*** mjturek has quit IRC15:57
*** njohnston has quit IRC15:58
*** njohnston has joined #openstack-meeting15:59
*** njohnston has quit IRC16:00
*** mjturek has joined #openstack-meeting16:00
*** njohnston has joined #openstack-meeting16:04
*** kopecmartin is now known as kopecmartin|off16:06
*** belmoreira has quit IRC16:08
*** e0ne has quit IRC16:11
*** hemna has joined #openstack-meeting16:11
*** jrbalderrama has joined #openstack-meeting16:18
*** aojea has quit IRC16:18
*** e0ne has joined #openstack-meeting16:20
*** jaypipes is now known as leakypipes16:20
*** yamamoto has joined #openstack-meeting16:28
*** markvoelker has quit IRC16:28
*** a-pugachev has quit IRC16:29
*** a-pugachev has joined #openstack-meeting16:30
*** macza has joined #openstack-meeting16:31
*** e0ne has quit IRC16:31
*** rossella_s has quit IRC16:32
*** yamamoto has quit IRC16:32
*** imacdonn has quit IRC16:38
*** imacdonn has joined #openstack-meeting16:38
*** gyee has joined #openstack-meeting16:40
*** jrbalderrama has quit IRC16:45
*** jrbalderrama has joined #openstack-meeting16:45
*** mattw4 has joined #openstack-meeting16:47
*** diablo_rojo has joined #openstack-meeting16:52
*** rossella_s has joined #openstack-meeting16:53
*** jrbalderrama has quit IRC16:55
*** mattw4 has quit IRC17:07
*** erlon_ has quit IRC17:07
*** erlon has joined #openstack-meeting17:08
*** imacdonn has quit IRC17:08
*** mattw4 has joined #openstack-meeting17:09
*** jrbalderrama has joined #openstack-meeting17:12
*** rossella_s has quit IRC17:18
*** jrbalderrama has quit IRC17:21
*** yamamoto has joined #openstack-meeting17:24
*** markvoelker has joined #openstack-meeting17:25
*** jrbalderrama has joined #openstack-meeting17:27
*** yamamoto has quit IRC17:29
*** a-pugachev has quit IRC17:34
*** jrbalderrama has quit IRC17:47
*** takamatsu_ has joined #openstack-meeting17:48
*** takamatsu has quit IRC17:48
*** sridharg has quit IRC17:48
*** jrbalderrama has joined #openstack-meeting17:50
*** sdake has quit IRC17:54
*** sdake has joined #openstack-meeting17:55
*** ijw has joined #openstack-meeting17:57
*** electrofelix has quit IRC17:58
*** markvoelker has quit IRC17:59
*** igordc has joined #openstack-meeting18:01
*** takamatsu_ has quit IRC18:03
*** tssurya has quit IRC18:05
*** jrbalderrama has quit IRC18:05
*** mriedem is now known as mriedem_lunch18:05
*** takamatsu_ has joined #openstack-meeting18:06
*** goldenfri has joined #openstack-meeting18:07
*** jrbalderrama has joined #openstack-meeting18:10
*** jrbalderrama has quit IRC18:10
*** jamesmcarthur has quit IRC18:22
*** whoami-rajat has quit IRC18:27
*** wwriverrat has quit IRC18:29
*** jrbalderrama has joined #openstack-meeting18:36
*** macza has quit IRC18:38
*** _alastor_ has quit IRC18:43
*** jrbalderrama has quit IRC18:45
*** jamesmcarthur has joined #openstack-meeting18:51
*** lpetrut has quit IRC18:51
*** markvoelker has joined #openstack-meeting18:56
*** lpetrut has joined #openstack-meeting19:07
*** macza has joined #openstack-meeting19:10
*** macza has quit IRC19:10
*** macza has joined #openstack-meeting19:11
*** yamamoto has joined #openstack-meeting19:12
*** jamesmcarthur has quit IRC19:12
*** jamesmcarthur has joined #openstack-meeting19:15
*** jamesmcarthur has quit IRC19:16
*** yamamoto has quit IRC19:16
*** e0ne has joined #openstack-meeting19:18
*** mriedem_lunch is now known as mriedem19:25
*** mjturek has quit IRC19:25
*** markvoelker has quit IRC19:28
*** sdake has quit IRC19:31
*** wwriverrat has joined #openstack-meeting19:36
*** mjturek has joined #openstack-meeting19:41
*** yamamoto has joined #openstack-meeting19:52
*** yamamoto has quit IRC19:57
*** erlon has quit IRC20:05
*** lpetrut has quit IRC20:08
*** e0ne has quit IRC20:08
*** markvoelker has joined #openstack-meeting20:25
*** ijw has quit IRC20:31
*** ijw has joined #openstack-meeting20:32
*** ijw has quit IRC20:37
*** ijw has joined #openstack-meeting20:42
*** ijw has quit IRC20:47
*** ijw has joined #openstack-meeting20:58
*** markvoelker has quit IRC20:59
*** ekcs has joined #openstack-meeting21:01
*** ijw has quit IRC21:03
*** yamamoto has joined #openstack-meeting21:04
*** yamamoto has quit IRC21:09
*** ijw has joined #openstack-meeting21:14
*** raildo has quit IRC21:15
*** ijw has quit IRC21:21
*** yamamoto has joined #openstack-meeting21:39
*** temka has quit IRC21:40
*** artom has joined #openstack-meeting21:40
*** yamamoto has quit IRC21:43
*** macza has quit IRC21:44
*** macza has joined #openstack-meeting21:45
*** ijw has joined #openstack-meeting21:49
*** ijw has quit IRC21:54
*** ijw has joined #openstack-meeting21:55
*** markvoelker has joined #openstack-meeting21:56
*** mjturek has quit IRC21:59
*** ijw has quit IRC22:00
*** ekcs has quit IRC22:00
*** awaugama has quit IRC22:02
*** ijw has joined #openstack-meeting22:05
*** diablo_rojo has quit IRC22:18
*** markvoelker has quit IRC22:30
*** potsmaster has joined #openstack-meeting22:34
*** sdake has joined #openstack-meeting22:37
*** yamamoto has joined #openstack-meeting22:56
*** yamamoto has quit IRC23:00
*** diablo_rojo has joined #openstack-meeting23:05
*** slaweq has quit IRC23:23
*** markvoelker has joined #openstack-meeting23:27
*** mattw4 has quit IRC23:28
*** mriedem has quit IRC23:52
*** markvoelker has quit IRC23:59

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