Thursday, 2018-08-09

*** longkb has joined #openstack-fwaas00:41
openstackgerritKim Bao Long proposed openstack/neutron-fwaas master: [log] FWaaS L3 Logging driver based iptables  https://review.openstack.org/55373801:19
*** yushiro has joined #openstack-fwaas01:30
yushiroHi all01:30
yushiroI just arrived at my office01:30
yushiroSorry I was late.01:30
hoangcxyushiro: :)01:32
*** yamamoto has joined #openstack-fwaas01:48
*** yamamoto has quit IRC01:51
*** SumitNaiksatam has joined #openstack-fwaas01:56
annpmlavalle, ping02:01
*** mlavalle has joined #openstack-fwaas02:01
mlavalleo/02:02
yushiromlavalle, Hi.02:02
mlavalleGood morning yushiro !02:02
annphi mlavalle02:02
mlavalleannp: hi02:03
yushiromlavalle, Thanks for holding this meeting with super friendly time for Asia.02:03
mlavalleno problem, I am glad to help you :-)02:03
longkbHi mlavalle :)02:03
mlavallehi longkb02:03
yushiro:)02:03
yushiromlavalle, OK, let me sync up current progress of fwg logging.02:04
mlavallecool02:04
mlavallethese are the patches, right: https://review.openstack.org/#/q/status:open+project:openstack/neutron-fwaas+branch:master+topic:bug/172072702:05
yushiromlavalle, Yes, thanks.02:06
yushiroPlease 'reload' this page :)02:06
yushiroWe have 7 patches are in review but 3 patches will be merged soon ( SridarK or xgerman_ will put +2)02:07
mlavalleok02:08
mlavalleI can see that 3 of them have already a +202:08
yushiroSo, only 4 patch:  3 in fwaas(1 is releasenote) and  1 in python-neutronclient02:08
yushiromlavalle, Yes.02:08
mlavallethat zuul failure in release note doesn't seem related to the patch, right?02:09
SridarKmlavalle: yushiro: hi02:09
SridarKsorry got delayed02:09
mlavalleSridarK: Hi02:09
mlavalleno problem. glad you made it02:10
SridarK:-)02:10
mlavalleso let me see if I understand correctly....02:10
yushiromlavalle, yes.02:10
SridarKyushiro: +1 on the 3 patches02:11
mlavalleout of the patches in https://review.openstack.org/#/q/status:open+project:openstack/neutron-fwaas+branch:master+topic:bug/172072702:11
mlavallewe need the 3 that already have a +202:11
mlavalleplus the rlease notes02:11
mlavalleis that the situation?02:12
annpyushiro, please rebase release note patch in latest of logging driver patch02:12
annpyushiro, I believe zuul will passed.02:12
yushiromlavalle, Yes.  that's correct.02:12
yushiroannp, Thanks I'll rebase after I fixed some comments.02:13
mlavallewe don't need to worry about the other two patches, correct?02:13
annpyushiro, thanks.02:13
SridarKyushiro: we only had 1 patch that had a zuul issue02:13
SridarKyushiro: i think we are good on the other patches and i think we can try to merge them soon ?02:14
yushiromlavalle, Ah, we have 1 client patch: https://review.openstack.org/#/c/579466   but I think client deadline is over...02:14
longkb+1 SridarK02:14
mlavalleyeap02:14
mlavalleok02:14
yushiroSridarK, Yes,  I think we can merge soon.02:14
yushiromlavalle, What time is deadline to wait these patches are merged today??02:16
mlavalleyeah02:16
SridarKso total of 6 patches02:16
*** yushiro has quit IRC02:17
SridarKyushiro: longkb: correct ?02:17
SridarKoops looks like we lost yushiro02:17
*** yushiro has joined #openstack-fwaas02:17
longkbYes. SridarK02:17
yushiroAhhh!! I'm sorry.  Suddenly disconnected with unknown error ...02:18
hoangcxyushiro: mlavalle I don't see amotoki_ propose new release hashs yet https://review.openstack.org/#/q/project:openstack/releases+status:open02:19
hoangcxI think amotoki_ is waiting for our patches to be landed02:19
SridarKmlavalle: are u comfortable if we take a day to merge the remaining patches ?02:19
mlavalleSridarK: is that day this one?02:19
SridarKmlavalle: if things are in by Thu morn US time02:20
SridarKor are we stretching the deadline02:20
SridarKyushiro: how is ur comfort level also02:20
SridarK?02:20
mlavalleSridarK: let me check the latest news from the release team.... hang on02:20
SridarKmlavalle: ok02:21
yushiroSridarK, OK!02:22
yushiroSridarK, I can work all day and review.02:22
SridarKyushiro: ok and i will be available to help merge02:23
yushiroannp, hoangcx and longkb can help as well.02:23
annpyushiro, Sure!02:23
hoangcxAbsolutely :)02:23
longkb+infinity02:24
yushiroSridarK, Thanks for your help every cycle :)02:24
SridarKyushiro: oh no worries at all happy to be of any help02:25
mlavalleSridarK, longkb, hoangcx, annp, yushiro: http://lists.openstack.org/pipermail/openstack-dev/2018-August/132864.html02:25
mlavallePlease read the first paragraph02:26
SridarKmlavalle: ah ok so we are cutting it very fine here02:27
yushiro""" deadline is this Thursday, the 9th. """02:27
hoangcxnow is 9:30pm 8th in US02:27
yushiroIt is for US time I think..02:27
mlavalleso our goal should be to have it everything we need merged by Thursday morning US time02:28
mlavallewe have about 12 hours02:28
mlavallerealistically02:28
yushiromlavalle, I see.  12 hours.02:29
hoangcxmlavalle: Indeed. All of the patches are in shape.02:29
hoangcxyushiro: please rebase your release note patch02:29
hoangcxyushiro: then all in shape02:30
yushirohoangcx, Yes, I'll fix and rebase it.02:30
mlavalleso let's get together tomorrow morning for the usual fwaas weekly meeting and see what the situation is at that point02:30
SridarKmlavalle: +102:30
SridarKmlavalle: sounds good and thx as always for the support02:31
yushiromlavalle, OK, I see.  Hope to merge all patches.02:31
SridarKyushiro: shall we sync up in a few hours ?02:31
hoangcxSridarK: Can you have to land 3 patch with +2. It will have to save time :02:31
mlavalleSridarK: can I ask you a favor?02:31
yushiroSridarK, Sure.02:31
SridarKhoangcx: yes absolutely will work with yushiro02:31
SridarKmlavalle: yes pls go ahead02:31
hoangcxs/have/help02:32
SridarKhoangcx: +102:32
mlavalleSridarK: I am going to China next week to visit the mother ship.... one question they have is the road map of fwaas. would you send me an email to miguel.lavalle@huawei.com with what you see as roadmap of the next few cycle?02:32
mlavallehoangcx: the same for vpnaas ^^^^02:33
SridarKmlavalle: will do02:33
hoangcxmlavalle: Yeah. I will need to sync with yamamoto02:33
yushiroLet me help about that, SridarK  :)02:34
SridarKyushiro: sounds good02:34
mlavalleSridarK, hoangcx: if I can have it by the end of this week, would be great02:34
SridarKmlavalle: yes for sure02:35
yushiromlavalle, Safety and enjoy your business trip in China :p02:35
mlavalleThanks guys02:35
yushiroThanks a lot, mlavalle02:35
SridarKsounds good thx all02:35
SridarKyushiro: will sync with u in abt 2 hrs and we can check on status02:36
yushiroOK, SridarK many thanks.02:36
mlavalletalk to you tomorrow morning guys02:37
mlavalleGoooooooood luck!02:37
SridarKmlavalle: thx02:37
yushiromlavalle, Yes.  Thank you so much02:37
longkbThanks a lot mlavalle :)02:37
yushiroSridarK, OK, Let me explain to you about https://review.openstack.org/#/q/status:open+branch:master+topic:bug/172072702:37
mlavalleThanks for all your hard work!02:37
annpmlavalle, SridarK, thanks a ton!02:38
SridarKyushiro: i will need to step away for a bit02:38
SridarKyushiro: will ping u in a bit02:38
yushiroSridarK, OK.  please ping me :)02:38
SridarKand we can discuss02:38
SridarKyushiro: thx02:38
annpmlavalle, Why don't you go to vietnam after china's trip ? :)02:38
yushiroannp, +102:39
mlavalleannp: that's actually a good idea. I won't be able to do it during this trip, but maybe next one02:39
annpmlavalle, OK! So I'm waiting you for next time :)02:40
annpmlavalle, beer!02:40
mlavalleannp: sure02:40
annpmlavalle, thanks for your kindness for waiting for logging.02:43
mlavalleannp: thanks for your hard work. That's where the kindness is :-)02:44
annpmlavalle, I guess it must be quite late in your timezone, right now.02:44
mlavalleannp: 9:45pm02:45
annpmlavalle, So see you at 9:00 PM IST02:45
mlavalleannp: yeap, have a nice day02:46
longkbGood night mlavalle :D02:46
annpmlavalle: thanks, G9!02:46
mlavallelongkb: you too have a nice day02:46
*** mlavalle has quit IRC02:53
*** yushiro is now known as yushiro_lunch03:02
*** yushiro_lunch is now known as yushiro04:00
openstackgerritKim Bao Long proposed openstack/neutron-fwaas master: Add python binding for libnetfilter_log  https://review.openstack.org/53069404:06
openstackgerritKim Bao Long proposed openstack/neutron-fwaas master: [log] FWaaS L3 Logging driver based iptables  https://review.openstack.org/55373804:06
openstackgerritKim Bao Long proposed openstack/neutron-fwaas master: Add releasenote for FWaaS v2 logging  https://review.openstack.org/58999104:06
reedip|afkIST????04:29
reedip|afkis mlavalle in India ??04:29
*** reedip|afk is now known as reedip04:29
*** SridarK has quit IRC04:37
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Add releasenote for FWaaS v2 logging  https://review.openstack.org/58999105:16
*** SridarK has joined #openstack-fwaas06:09
SridarKyushiro: hi06:09
SridarKyushiro: sorry i had to be out of home for some time06:09
yushiroSridarK, Hi06:09
SridarKback now06:09
yushiroSridarK, No problem.  I think your timezone is night.06:10
SridarKyes06:10
SridarKno worries06:10
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Add releasenote for FWaaS v2 logging  https://review.openstack.org/58999106:11
yushiroSridarK, Now I just updated releasenote patch.06:11
yushiroSo, I need your help for review: https://review.openstack.org/#/q/topic:bug/1720727+(status:open+)06:12
SridarKyushiro: on it06:13
yushiro(1/6) Add log validator for FWaaS v2 logging: https://review.openstack.org/53279206:13
yushiro(2/6) [log]: Add rpc stuff for logging: https://review.openstack.org/53071506:14
SridarKback in 5 min06:14
yushiro(3/6) Adding resources callback handler for FWaaS v2 logging: https://review.openstack.org/58097606:14
yushiro(4/6) Add python binding for libnetfilter_log: https://review.openstack.org/53069406:14
yushiro(5/6) [log] FWaaS L3 Logging driver based iptables: https://review.openstack.org/55373806:15
yushiro(6/6) Add releasenote for FWaaS v2 logging: https://review.openstack.org/58999106:15
SridarKyushiro: ok06:19
yushiroThese patches are target.  And first 3 patches are almost OK for me.(putting +2)06:19
SridarKyushiro: ok - i did go thru - i am good - but will defer to u based on ur tests06:20
yushiroAs you know, CLI patch hasn't been merged in this cycle.  So, I added some limitation into release note.06:20
yushiroSridarK, Sure.  Of course.  Let me share my test cases.06:22
yushiroJust a moment..06:28
openstackgerritOpenStack Proposal Bot proposed openstack/neutron-fwaas-dashboard master: Imported Translations from Zanata  https://review.openstack.org/59012106:31
reedipneed any help?06:32
SridarKreedip: hi06:36
SridarKyushiro: ok 1 - 3 are good06:37
SridarKI will let u +A in case u need to check on something06:37
yushiroreedip, Thanks :)  SridarK I'm just updating how to deploy test environment..06:38
SridarKSo we will live with some limitation on the CLI - users can always use the API06:38
SridarKyushiro: no worries06:38
SridarK5 still has issues with zuul06:39
yushiroSridarK, For more detail, client cannot run with a combination.    --resource-type firewall_group  --resource <ID of firewall group> for CLI.06:39
SridarKyushiro: yes and ur release note reflects that - as i just saw06:40
yushiroSridarK, OK.  So, my answer is Yes.  We need to use RESTAPI if we want to set specific firewall group for logging.06:41
SridarKok06:41
SridarKand so on the CLI, what we can get is logging corresponding to a specified port06:42
SridarKbut we cannot get logging corresponding to all ports that a fwg is on06:42
yushiroSridarK, We can specify portID as --target  option.06:43
SridarKyes06:43
SridarKok06:43
yushiroSridarK, If we run $openstack network log create --resource-type firewall_group my-log,  All of L3 ports which is associated with firewall group are target.06:44
yushiroSridarK, reedip : https://github.com/longkb/logging/blob/master/Ingration%20guideline%20for%20logging%20service%20in%20FWaaS.rst06:44
SridarKyushiro: thx06:46
yushiroHere is recipe of logging environment for devstack.  1 NOTE.  Please refer local.conf as document not paste.openstack.org.06:46
yushiroOK, go back to talk about logging target.06:46
yushiroFor example,  VM0(fwg1)  ----- (fwg2)router0 ---- VM106:47
yushiroah, sorry06:47
yushiro VM1(port1)(fwg1)  ----- (fwg2)(port0)router0 ---- (port2)VM206:48
yushiroIf we create log-resource with --target port1, then raised an exeption because L2 port hasn't supported yet.06:49
yushiroIf we create log-resource with --target port0(router port), then log-resource should create with no error.06:50
yushiroIf we create log-resource with no --target option, then log-resource should create with no error and port0 is targeted for logging.06:51
yushiroRegarding logging validator, I've tested above cases.06:51
SridarKyushiro: ok06:51
yushiroreedip, If you have bandwidth, it will be great if you try to deploy devstack and check some behavior :)06:54
SridarKyushiro: one question - if the fwg is associated with multiple ports06:55
reedipI can..., what do u need to check?06:55
SridarKyushiro: and if create a log-resource with no --target option06:55
SridarKthen what happens ?06:55
SridarKare all ports associated with the fwg targetted for logging ?06:56
yushiroSridarK, Correct.  However, if the fwg is associated with L2 port and L3 port,  only L3 port are targeted for logging.06:56
SridarKyushiro: yes that is good06:57
SridarKbut i think right now we prevent a fwg being on L3 and L2 ports06:57
SridarKsame fwg on L3 & L2 ports06:57
SridarKbut yes agreed that would be correct06:57
yushiroah, yes.  But I wonder we would implement some validation to avoid associating both L2 and L3... :p06:58
yushiroreedip, Basic logic for logging.  We wrote fundamental scenario for logging at github page.06:58
yushiroreedip, BTW, what is your OS for devstack?06:59
yushiroSridarK, I tested and turned out that we can spceify both L2/L3 port on same firewall group.07:01
SridarKyushiro: i thought we had that validation before but no worries07:02
yushiroIn this case, we can create log-resource with no --target.07:02
SridarKyushiro: i think for now that is okay07:02
SridarKlets not worry abt it07:02
yushiroSridarK, I see. But your point is reasonable.  we need to consider it.07:02
SridarKyushiro: i think somewhere along the changes - this may have gotten updated - but we can re-evaluate in Stein07:03
yushiroSridarK, Yes.07:04
yushiroSridarK, BTW, regarding roadmap for fwaas, can we discuss today's IRC meeting ??07:04
SridarKyushiro: yes lets do that07:04
SridarKor if we have to spend time on release or logging related - we can talk after the mtg07:05
SridarKduring ur day time07:05
SridarKwe need to have it by weekend i think07:06
yushiroSridarK, Yes. Miguel wants us within this week :)07:06
SridarKyushiro: on logging on the remaining 2 patches07:06
yushiro (2/6) [log]: Add rpc stuff for logging: https://review.openstack.org/53071507:06
hoangcxyushiro: SridarK for patches got +2 from both of you, I think it is ok to +A to save time. Since sometime gate is :(07:07
yushiro(3/6) Adding resources callback handler for FWaaS v2 logging: https://review.openstack.org/58097607:07
SridarKhoangcx: +1 yes better to do it soon before US daytime07:07
SridarKthe gate will get more backlogged07:07
SridarKyushiro: so these 3 are ready to go07:08
*** velizarx has joined #openstack-fwaas07:09
yushiroSridarK, Yes, basic part is OK for me.  I need to check carefully in driver side.07:09
*** yamamoto has joined #openstack-fwaas07:11
yushiroOther 3 patches are necessary to deploy devstack and check iptables in namespace...07:12
yushirowatch, tailf and journalctl commands helped me but my eyes are dried :p  Haha07:12
annpyushiro :)07:13
SridarKyushiro: ok :-)07:21
SridarKso shall i check for patch 4 & patch 5 in my morn07:21
*** yamamoto has quit IRC07:22
SridarKbefore the mtg ?07:22
reedipyushiro : centos07:22
yushiroreedip, Perfect!07:23
reediphmm07:23
yushiroreedip, I'm using Ubuntu16.04.  So, it is very helpful.07:23
SridarKreedip: is now a redhat guy !!07:23
reedipwhat do I need to checkout07:23
reedipI mean the devstack configuration07:24
SridarKhe may get into trouble with ubuntu distro ;-)07:24
reedipOh sorry, I have CentOS on my Laptop, but have Ubuntu on the Devstack VM :P07:24
yushiroreedip, please check https://github.com/longkb/logging/blob/master/Ingration%20guideline%20for%20logging%20service%20in%20FWaaS.rst  on Devstack local.conf section.07:24
reedipNothing like that SridarK :D07:24
SridarKhe he07:24
reedipWhy is it Ingration ??? Wont it be Integration ??07:25
reedipyushiro ^^07:25
longkboops07:25
reedip:P07:25
SridarK+107:25
reedip:D07:25
yushiroreedip, Good catch :D07:25
longkbThanks for your reviewing kkk07:25
longkb:P07:25
reediphehehe07:25
reedipOk, I have that Link. Let me pull up devstack and see some stuff07:26
SridarKyushiro: let me know if u need me to stay up for patch 4 or 507:26
SridarKelse i will go to bed and check in the morn07:26
yushiroreedip, Did you get a hat of red color? :)07:26
reedipwaiting for it07:26
reedip:)07:26
yushiroSridarK, Thank you so much.07:27
SridarKyushiro: no worries at all07:27
yushiroSridarK, BTW, could you put +A for first 3 patches??  If you feel there is no problem.07:28
yushiroAs hoangcx said,  gate is not stable ...07:28
SridarKyushiro: sure no issue - i thought u would +A07:28
yushiroSridarK, Aha :)07:28
yushiroSridarK, Thanks.  I forgot I was core :P07:28
SridarKi can if u want - i thought if u wanted to double check something07:29
SridarKyushiro: :-) i think u are very tired07:29
yushiroSridarK, Maybe Yes.  I wanna sleep in a hammock :D07:29
hoangcxSridarK: yushiro has been working throughout for a week07:29
SridarKyushiro: :-)07:29
SridarKhoangcx: +107:30
annpyushiro: you're superman :)07:30
yushiroOK, if we finish testing another 3 patches, I'll ping you before IRC meeting.07:30
longkbSuper Yushiro :P07:30
SridarKhoangcx: all of u have been doing a superb job07:30
yushiroHahaha.  thanks.  I think fwaas team are all super for me :P07:31
SridarK:-)07:31
SridarKok good then i will get some sleep - be up a bit early b4 IRC mtg07:31
SridarKyushiro: if u will be offline - just send an email to me07:32
yushiroSridarK, Sure!!!!  Thank you.07:32
longkbHi folks, I have updated the guideline. Please check it :)07:32
longkbhttps://github.com/longkb/logging/blob/master/integration_guideline_for_logging_service_in_FWaaS.rst07:32
SridarKideally if we can get things in the queue before or during the mtg it will be good07:32
SridarKi will leave my IRC - so i can catch up quickly in a few hours07:33
yushiroOK, thanks.  Good night.07:33
longkbgood night SridarK :D07:33
SridarKyushiro: longkb annp hoangcx all thx07:33
annpSriarK, yushiro: thanks a ton.07:34
*** velizarx has quit IRC07:46
annpreedip: thanks for great help also :)07:50
*** velizarx has joined #openstack-fwaas07:53
reedipannp: I didnt do anything :D07:55
annpreedip, at least you reviewed for integration guide line :)07:58
annpreedip, thanks07:59
reedipeh , that was just a simple thing :) You guys have been so involved in the actual code, this is just a visual fix :)07:59
annpreedip: From my opinion, the document should be good at first to get more attractive from contributor. :)08:00
reedip:D08:01
reedipThats true :)08:01
annp:)08:01
reedipI am running the devstack, lets see08:03
reedipyushiro: ping08:23
reedipannp: ping08:23
yushiroreedip, pong08:23
reedipWould the loggable resource be present once Devstack is finished?08:24
yushiroYes, you mean network loggable resources list ?08:25
reedipYes08:25
yushiroYes, you can run after deployed devstack.08:27
reedipThen there seems to be an issue...After the devstack run08:27
reedip$ openstack network loggable resources list08:27
reedipThe resource could not be found.08:27
reedipNeutron server returns request_ids: ['req-c4869d8a-5218-4c9e-bba5-182f3806346d']08:27
reedipOk, checking some other stuff as well08:28
yushirocan you check /etc/neutron/neutron.conf  and "log" exist on service_plugins ?08:28
reedipYeah, checking that. Its not present08:28
reedipfixing it08:28
reedipAlso, network_log is not present in the /etc/neutron/l3_agent.ini08:30
reedipbut fwaas_v2_log is08:30
yushiro[network_log] is optional.  If you'd like to output packet log to dedicated file, you can specify on /etc/neutron/l3_agent.ini  with [network_log]local_output_log_base = /path/to/logfile08:31
reedipohk08:34
openstackgerritMerged openstack/neutron-fwaas master: Add log validator for FWaaS v2 logging  https://review.openstack.org/53279208:47
openstackgerritMerged openstack/neutron-fwaas-dashboard master: Update reno for stable/rocky  https://review.openstack.org/58998208:52
openstackgerritMerged openstack/neutron-fwaas-dashboard master: Imported Translations from Zanata  https://review.openstack.org/59012108:56
openstackgerritMerged openstack/neutron-fwaas master: [log]: Add rpc stuff for logging  https://review.openstack.org/53071509:07
openstackgerritMerged openstack/neutron-fwaas master: Adding resources callback handler for FWaaS v2 logging  https://review.openstack.org/58097609:07
reedipOne change here : https://github.com/longkb/logging/blob/master/Ingration%20guideline%20for%20logging%20service%20in%20FWaaS.rst09:19
reedipChange "You can test firewall loging with the following arguments" to "You can test firewall logging with the following arguments"09:19
yushiro+1 reedip :)09:31
longkbfixed. Thanks reedip10:06
*** wkite has joined #openstack-fwaas10:37
*** wkite has quit IRC10:37
openstackgerritKim Bao Long proposed openstack/neutron-fwaas master: Add python binding for libnetfilter_log  https://review.openstack.org/53069410:44
openstackgerritKim Bao Long proposed openstack/neutron-fwaas master: [log] FWaaS L3 Logging driver based iptables  https://review.openstack.org/55373810:44
openstackgerritKim Bao Long proposed openstack/neutron-fwaas master: Add releasenote for FWaaS v2 logging  https://review.openstack.org/58999110:44
openstackgerritYushiro FURUKAWA proposed openstack/neutron-fwaas master: Add releasenote for FWaaS v2 logging  https://review.openstack.org/58999111:06
*** yushiro has quit IRC11:18
reedipIts no problem , I am just helping on the small stuff :)11:18
*** longkb has quit IRC11:40
*** annp has quit IRC11:42
*** yamamoto has joined #openstack-fwaas11:57
*** velizarx has quit IRC12:13
*** velizarx has joined #openstack-fwaas12:15
xgerman_o/13:01
*** velizarx has quit IRC13:02
*** velizarx has joined #openstack-fwaas13:03
*** yushiro has joined #openstack-fwaas13:06
yushiroHi13:06
reedip\o13:11
yushiroreedip, Hi. I'm home and logged-in :)13:12
reedipyushiro : I am at home , attending meetings :D13:17
yushiro+113:19
*** hoangcx_ has joined #openstack-fwaas13:30
yushiroreedip, Again, congratus for working at RH!13:30
reedip:)13:30
reedipthanks ..13:30
*** yamamoto has quit IRC13:31
yushiroIf you come to Japan, please ping me.  Let's go hotspring or eating Sushi :p13:31
reedipI want to :) maybe next year . I will definitely ping you13:34
yushiroyeah13:36
yushiroI always play with Octavia's friend when he come back to Japan.  Hehe.  I'll introduce him :)13:37
yushirointroduce you to him ?  ... introduce him to you ?? .. oh13:37
reedipboth are same :)13:37
reedipin a way13:37
yushirohe he13:38
*** reedip is now known as reedip|afk13:38
SridarKyushiro: hi13:39
xgerman_hi13:39
SridarKxgerman_: hi13:39
SridarKyushiro: how are things13:39
*** annp has joined #openstack-fwaas13:39
*** njohnston has joined #openstack-fwaas13:40
yushiroSridarK, xgerman_ hi13:40
yushiroYeah, I've been testing all day :) Currently, all patches look good and +1 zuul.13:41
SridarKyushiro: ok13:42
annpyushiro, thanks a lot for your great review and testing.13:43
annpall patches look good now!13:44
SridarK#link https://review.openstack.org/#/c/530694/13:44
SridarKgood13:44
yushiroannp, NP. SridarK and xgerman_ also gave us great review.13:44
SridarKready to +A ?13:44
xgerman_annp: +113:44
annpSridarK, thanks!13:45
annpxgerman_, thanks. :)13:45
yushiroSridarK, Yes.  ready :)13:45
yushiroxgerman_, BTW, python-neutonclient gate issue ( due to osc-lib) has fixed.  Maybe zuul will smile if you rebased your patch.13:47
SridarKok good on both patches13:49
yushiroAh!! SridarK you had +2.  I didn't realize.  Thanks.13:49
SridarKxgerman_: anything u wanted to check ?13:49
SridarKbefore +A13:49
yushiroYes, I'd like to ask xgerman_ about it as well.13:49
xgerman_no, I am good13:49
yushiroxgerman_, Thanks.13:49
*** longkb has joined #openstack-fwaas13:51
hoangcx_yushiro: Please +A the patches. Time is clocking13:52
yushiroOK, thanks SridarK and xgerman_13:52
longkbI am having a dinner ^_^13:52
annplongkb, me too :)13:52
SridarKhoangcx_: done13:53
hoangcx_SridarK: Perfect! We were tested the patches for all today :)13:53
annpSridarK, thanks a ton.13:53
yushiroSridarK, xgerman_ releasenote patch is mine.  So, could you review +2 and +A?  https://review.openstack.org/#/c/58999113:53
SridarKfolks no issues13:54
SridarKyushiro: shd we wait for these 2 patches to merge before we +A the release note13:54
yushiroSridarK, OK13:54
yushiroI'm afraid of grammar...13:55
xgerman_ok, can you fix the pep8 commnt13:56
SridarKyes - but looks like zuul gave a +113:56
SridarKbut meantime while these 2 merge13:57
yushirolongkb, you though over 80 cols violates pep8 error, don't you?  I think 80 cols is only source code.13:58
yushiros/though/thought13:58
longkbYeah, right :)13:58
xgerman_ok, +A13:58
longkbI have check pep8 in releasenote, and it passed :D13:59
yushiroxgerman_, So, there is no problem I think :D13:59
*** wkite has joined #openstack-fwaas13:59
amotoki_yushiro: if doc8 is enabled, it complains >80 char line13:59
hoangcx_We need to keep watching in releases in case we missed something from amotoki_14:00
hoangcx_https://review.openstack.org/#/q/project:openstack/releases+status:open14:00
annpyushiro, but I think making it more pretty is good. :)14:00
amotoki_but I think it is the case for code-blocks so it is not the case.14:00
amotoki_hoangcx_: I haven't push a release patch yet14:00
hoangcx_amotoki_: yeah. I have just wonder about that14:00
amotoki_meeting time?14:00
yushiroamotoki_, I see.  Thanks.  aha, yes.14:01
*** amotoki_ is now known as amotoki14:01
yushiroOK, let's start14:01
yushiro#startmeeting fwaas14:01
openstackMeeting started Thu Aug  9 14:01:18 2018 UTC and is due to finish in 60 minutes.  The chair is yushiro. Information about MeetBot at http://wiki.debian.org/MeetBot.14:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:01
openstackThe meeting name has been set to 'fwaas'14:01
yushiro#chair SridarK xgerman_14:01
openstackCurrent chairs: SridarK xgerman_ yushiro14:01
yushiroI'm sorry SridarK xgerman_ .  Who is today's turn? I just forgot :p14:01
yushiromy turn ?14:02
xgerman_I think with logging yushiro should take the turn. On the other hand I am gone the next two weeks14:02
SridarKno worries14:02
yushiroxgerman_, Sure. Thanks.14:02
SridarKyushiro: pls go ahead14:02
yushiroEYS!14:03
yushiros/EYS/YES14:03
yushiroOK, let's start14:03
yushiro#topi announcements14:03
yushiro#topic announcements14:03
yushiroToday (9th) is the deadline for release.  Miguel told us about that.14:04
*** mlavalle has joined #openstack-fwaas14:04
mlavalleo/14:04
annphi mlavalle14:04
yushiromlavalle, Hi o/14:04
njohnstono/14:04
SridarKmlavalle: njohnston: hi14:04
amotokiseems time for o/14:05
SridarKamotoki: hi14:05
hoangcx_Indeed o/14:05
amotoki:)14:05
mlavalleLOL14:05
mlavalleso I see 3 patches in flight14:06
longkbhi mlavalle :D14:06
SridarKmlavalle: :-) this is a tight race and very near the finish line14:06
yushiromlavalle, Yes. But it just started so..14:07
SridarKa prayer to the gate gods14:07
amotoki#link https://review.openstack.org/#/q/topic:bug/1720727+(status:open+OR+status:merged)14:07
mlavalleso we need the 3 patches in flight here?14:08
yushiromlavalle, You're right.  We need these patches.14:08
mlavalleok, here's what I propose amotoki......14:09
-amotoki- is looking at the gate progress :)14:09
mlavallesince it is getting late for you, why don't you push a release patch with what we have already merged and mark it wip14:09
mlavalleI will track down these 3 patches in flight during my day time14:10
mlavalleand if / when they land, I will amend the patch14:10
mlavalledoes that work?14:10
amotokiokay, I am preparing a release patch. let you know it when i push it14:10
amotokiyes, it works fine14:10
yushiro+1 mlavalle and amotoki  Thank you so much14:11
mlavalleamotoki: note that in  Neutron https://review.openstack.org/#/c/589573 landed14:11
amotokifor the neutronclient patch, it is not covered to FFE. it will be a part of early Stein of neutronclient14:11
amotokimlavalle: yeah, I know that.14:11
yushiroamotoki, OK, I see about client patch.14:12
annpamotoki, mlavalle: thanks a lot.14:12
mlavalleSridarK: my other request is that during the day, you stay reachable here, in case unexpected things arise and you and I need to talk14:12
SridarKmlavalle: will do14:12
xgerman_I am around, too, if you need votes14:13
yushiroI will...14:13
mlavallexgerman_: great!14:13
mlavalleto make things easier for me, I am using this query: https://review.openstack.org/#/q/status:open+project:openstack/neutron-fwaas+branch:master+topic:bug/172072714:13
mlavalleThese are the 3 patches, right?14:13
yushiromlavalle, Correct!14:14
* mlavalle has a small brain that cannot handle lists with more than 3 items ;-)14:14
SridarK:-)14:14
annpmlavalle :-)14:14
yushirohaha :)14:15
amotokiit looks simple as we can check whether the number of patches is empty or not :) heh14:15
SridarKWhat is a list ? :-)14:15
mlavalleok, this looks like a plan for the day in the US14:15
SridarKhopefully these will merge soon14:15
mlavalleyushiro, annp, hoangcx_, longkb, SridarK: thanks for your efforts! hopefully we will wrestle this thing into submission today14:16
mlavalleand thanks to amotoki for his patience :-)14:17
longkbmlavalle: sure :D14:17
amotokino worries. we are the community for a same goal :)14:17
annpmlavalle: thanks. :)14:17
yushiromlavalle, amotoki You too.  Super appreciated at any time anywhere :)14:18
annpamotoki, +10014:18
xgerman_+114:18
SridarK+114:19
yushiroOK, I hope their flight are safety and a little earlier.14:20
mlavalleok guys, running to pay attention to something else14:21
SridarKmlavalle: thx for the support as always14:21
mlavallehave a good night / day14:21
yushiroThanks mlavalle14:21
yushiroOK, let's continue14:22
yushiro#topic Rocky14:22
yushiroAlmost finished !14:23
amotokiyushiro: could you share the link of the meeting agenda etherpad?14:23
yushiroamotoki, OK14:23
yushiro#link https://etherpad.openstack.org/p/fwaas-meeting14:23
SridarKSo one request with the lot of changes going in14:23
amotokithanks14:23
yushiroSridarK, yes.14:23
SridarKto have some sanity testing done with the RC14:23
SridarKto make sure our basic functionality works including the datapath14:24
yushiroSridarK, +114:24
SridarKjust in case there is some regression14:24
yushiro#agree it is really important point.14:25
yushiroSridarK, Currently, our repository refers a master branch of neutron for zuul job(sphinx-docs, lower-constraints)14:26
yushiroAfter released neutron-rc1,  is it better to revert to use pip package of neutron?14:27
SridarKyushiro: yes i know u had to do this with amotoki14:27
amotokiIt is okay with either.14:27
yushiroFor testing perspective, I think it's better.14:28
amotokiif you use pip package of neutron, you are not affected by a sudden master change in neutorn14:28
amotokiif you consume master neutron, you don't need to wait milestone/rc releases14:28
amotokithey are pros and cons, so it is up to the team14:28
yushiroamotoki, yes.  I'd like to discuss with you, SridarK and xgerman_ about that.14:29
SridarKamotoki: are there implications once the release happens ?14:29
amotokiSridarK: could you elaborate a bit more? I didn't get you14:30
SridarKamotoki: sorry i would think we want to be associated with the pip package on release14:31
hoangcx_SridarK: AFAIK, neutron and fwaas released together. So, we don;t need to care about it14:31
SridarKhoangcx_: ok got it14:31
hoangcx_SridarK: That is the reason amotoki said either way is OK14:32
amotokihoangcx_: correct14:32
SridarKok thx just want to be sure14:32
amotokiyeah, that's the point which usually confuses us14:32
hoangcx_I vote for the master based :p14:33
SridarKno thx for clarifying14:33
yushiroWhat about neutron-lib ?14:33
amotokithere is one tricky point when we use neutron master.14:34
amotokitox jobs (like py27/py35 and so on) works as-is in the gate14:34
yushiroYes14:34
amotokibut you need to install neutron master manaully after creating tox env14:34
amotokito pass py27/py35 tests14:35
hoangcx_yushiro: AFAIK, neutron-lib is considered as library. So we can't do with master14:35
yushirohoangcx_, OK.14:35
amotokihoangcx_: yes, this case is considered as corner case14:35
amotokineutron-lbi exposes an interfaces14:36
amotokiin this case, we depends on internal behaviors of neutron which is not exposed as an interface, so we needed to use neutron master.14:36
reedip|afko/14:36
amotokiso it sometimes happens14:37
yushiroOK, I see.14:37
-amotoki- wonders how reedip|afk can type even though afk14:38
hoangcx_LOL14:38
longkb:))14:38
SridarKhe he :-)14:38
yushiroI think he is typing with magic arm :)14:38
amotokihe might type with voice :)14:39
yushirohaha14:39
yushiroOK, so, I think it's better to keep on using master branch of neutron.14:40
amotokireturning to the topic, we don't need to care lower bound of neutron pypi14:40
amotokias neutron and fwaas are released together.14:40
yushiroOk14:40
amotokiwhat was the problem in the docs job?14:41
*** hongbin has joined #openstack-fwaas14:41
hoangcx_amotoki: the docs job encountered tricky issue14:41
yushiroamotoki, Even if we referred master neutron, apidoc doesn't refer master but old version of neutron.14:41
hoangcx_amotoki: I tried to ask in #openstack-infra for help but no luck14:42
hoangcx_http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2018-08-08.log.html#t2018-08-08T01:15:0114:42
amotokiah... docs and releasenotes jobs are different from other jobs14:42
amotokithey might not honor required-projects14:43
amotokiwe need to check openstack-zuul-jobs (and/or zuul-jobs) carefully14:43
yushiromaybe it still refers pip package...14:43
amotokiyeah, perhaps so14:43
yushiroThanks hoangcx_ for your research :)14:44
amotokiso perhaps do we need to drop required-project for the docs job and revert some workaround after RC1 cut?14:44
hoangcx_amotoki: yes. That will be my task14:45
hoangcx_amotoki: because I proposed it :p14:45
amotokithnx for clarfication14:45
yushiroRegarding docs job, we should drop required-project.14:46
hoangcx_yushiro: no worries, I will do it14:46
yushiroAh, sorry.  yes, it's OK.14:46
yushirohoangcx_, thanks14:46
yushiroGood discussion.  THanks14:47
yushirotoday, let me skip specs topics and talk about horizon first14:48
yushiro#topic Horizon support14:48
yushiroamotoki, Thanks for pushing some patches.14:48
amotokiI just push maintenance patches :)14:49
amotokineutron-fwaas-dashboard rocky was released yesterday and the stable branch was cut14:50
yushiroI'll definitely check them.14:50
SridarKWe need to add work items for Stein - i think we have a few things that need to be covered14:50
yushiroSridarK, +1 horizon is also work item :)14:51
amotokilogging support might be a feature gap which should go to horizon repo.14:51
hoangcx_Do we have plan to meet in person for next PTG?14:52
yushiroCurrently, I don't have any plan but want to talk with amotoki and horizon team about that.14:53
yushirooh, 5 minutes left.14:54
yushiro#topic Open Discussion14:54
yushiroToday, I'd like to talk about fwaas roadmap for Stein.14:54
yushiros/talk/discuss14:54
amotokii have one thing to raise14:55
yushiroamotoki, go a head14:55
amotokias of now, neutron server fails to start when we enable both neutron fwaas and vpnaas.14:56
yushirooh14:56
amotokiservice provider configurations fail to be loaded.14:56
amotokiit would be nice if someone can look into the detail.14:56
yushiroamotoki, o/  Is there bug-report?14:57
amotokiat least neutron log says FIREWALL_V2 cannot be found, but vpnaas devstack might override the service provider.14:57
amotokiyushiro: not yet14:57
amotokiI just noticed it when preparing horizon for  translation check14:57
hoangcx_amotoki: with latest neutron and enable fwaas_v2,vpnaas together?14:57
SridarKyushiro: i just added a section to the meeting etherpad for stein topics14:57
njohnstonimplementing fwaas as an agent extension was supposed to avoid that issue14:57
SridarKnjohnston: +114:58
njohnstonI wonder how vpnaas's binding into the neutron agent is implemented14:58
annpnjohnston, ++14:58
SridarKi am not sure if such an effort happend with vpnaas14:58
yushiroSridarK, +10014:58
yushirohoangcx_, Do you know about that?14:58
hoangcx_njohnston: the same for vpnaas, I am the one who implemented that14:58
amotokihoangcx_: yes, for example local.conf http://paste.openstack.org/show/727445/14:58
SridarKhoangcx_: ah ok14:59
njohnstonhoangcx_: excellent!  good to have the original author. :-)14:59
hoangcx_amotoki: I will try with that tomorrow15:00
amotokihoangcx_: thanks15:00
yushiroOh, it's time.15:00
yushiro#endmeeting15:00
openstackMeeting ended Thu Aug  9 15:00:39 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fwaas/2018/fwaas.2018-08-09-14.01.html15:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fwaas/2018/fwaas.2018-08-09-14.01.txt15:00
openstackLog:            http://eavesdrop.openstack.org/meetings/fwaas/2018/fwaas.2018-08-09-14.01.log.html15:00
SridarKthx all15:00
SridarKyushiro: will keep an eye on the patches15:00
yushiroSridarK, Thanks.  I will as much as possible :)15:01
SridarKyushiro: may be good if u check in here when u wake up15:01
yushiroSridarK, Thanks !15:01
SridarKin case we have some difficulty15:01
SridarKfingers crossed15:01
yushiroyeah15:01
yushirohoangcx_, I have one question.15:02
yushiroabout vpnaas15:02
yushironow, I've deployed devstack with fwaas. (no vpnaas)15:02
*** Swami has joined #openstack-fwaas15:03
yushiroIn order to enable vpnaas, should I clone vpnaas and 'sudo python setup.py install' and configure service_plugins...  anything else??15:03
yushiroAh, forgot to restart agents.15:03
hoangcx_yushiro: https://docs.openstack.org/neutron/latest/admin/vpnaas-scenario.html15:04
yushirohoangcx_, perfect15:06
yushirohoangcx_,  In my environment, q-svc could restart15:14
yushirowith fwaas and vpnaas15:14
yushiroHowever,15:15
hoangcx_yushiro: what amotoki means is that he tried to build with devstack with http://paste.openstack.org/show/727445/ . Not manual after you have fwaas_v2 in hand already15:16
amotokihoangcx_: exactlly15:16
*** wkite has quit IRC15:17
yushiroI see.15:18
*** hoangcx_ has quit IRC15:20
openstackgerritMerged openstack/neutron-fwaas master: Add python binding for libnetfilter_log  https://review.openstack.org/53069415:24
yushiroyes!!!!15:24
longkbgreat!!!15:24
annpwow15:25
longkblet's pray for the rest :D15:25
annp:)15:25
yushiroYes,15:28
yushirolongkb, annp hoangcx Thanks for your great work, again.15:28
annpWe did it. :)15:28
*** reedip|afk is now known as reedip15:29
longkbWe did it together :) super yushiro :D15:29
annpyushiro, thank you super hero yushiro. :)15:30
openstackgerritMerged openstack/neutron-fwaas master: [log] FWaaS L3 Logging driver based iptables  https://review.openstack.org/55373815:30
openstackgerritMerged openstack/neutron-fwaas master: Add releasenote for FWaaS v2 logging  https://review.openstack.org/58999115:30
annpDone!15:30
longkbwow15:31
longkbcongrad guys :D15:31
amotokiall patches landed :)15:32
yushiroWow, faster!15:33
yushirolongkb, annp you too :)15:33
mlavallehttps://review.openstack.org/#/q/status:open+project:openstack/neutron-fwaas+branch:master+topic:bug/1720727 GONE WITH THE WIND!!!!!15:36
mlavalleGreat job15:36
yushiromlavalle, we did it! thanks!15:37
longkbmlavalle: thanks a lot :D15:37
annpmlavalle: ++15:38
longkb+oo thanks to annp, yushiro15:38
mlavalleSridarK, xgerman_: everything landed. we are good15:39
xgerman_sweet!!!15:39
yushiroSridarK, xgerman_ yeah :)15:40
annpI need more challenges beside logging :)15:41
yushiro:)15:43
annpyushiro, I guess you need to sleep now :)15:44
annpThanks for great work. Good night everyone.15:45
longkb+2 annp. Our super yushiro has work 1000% this week :D15:45
longkbGood night yushiro :D15:45
annplongkb: Yessss!15:45
*** annp has quit IRC15:46
longkbbye guys :D15:51
*** longkb has quit IRC15:55
*** SumitNaiksatam has quit IRC15:59
yushiroamotoki, I hit same exeption " No providers specified for 'FIREWALL_V2' service, exiting"16:09
yushiroCould not load neutron_vpnaas.services.vpn.service_drivers.ipsec.IPsecVPNDriver16:11
yushirocommand line: /usr/local/bin/neutron-server --config-file /etc/neutron/neutron.conf --config-file /etc/neutron/plugins/ml2/ml2_conf.ini --config-file /etc/neutron/neutron_vpnaas.conf16:12
yushironeutron_fwaas.conf didn't load.16:13
*** velizarx has quit IRC16:16
amotokiyushiro: surprisingly, if you only enable fwaas in local.conf, you don't see neutron_fwaas.conf in the command line of neutorn-server.16:18
amotokiyushiro: http://paste.openstack.org/show/727750/16:18
amotokiyushiro: however, fwaas v2 API works well.16:18
amotokiyushiro: I am wondering how service provider for fwaas v2 is configured or it is not necessary.16:19
yushiroamotoki, Yes.  there is no neutron_fwaas.conf with --config-file option.16:19
yushiroamotoki, me too..16:20
amotokiyushiro: I see no neutron_fwaas.conf with fwaas without vpnaas. is it expected?16:21
yushiroI think no.  It should be loaded as --config-file for q-svc.16:21
amotokii haven't checked in case of q-svc.16:22
amotokiI now use neutron-api in local.conf (and disable q-svc)16:22
yushiroah, sorry. neutron-api was correct.16:26
yushiroI just editted devstack@neutron-api and added --config-file /etc/neutron/neutron_fwaas.conf, then it worked correctly.16:27
yushiroMaybe devstack plugin.sh in fwaas has some issue...16:28
yushiroI'll check it tomorrow again :p16:28
yushiroThanks amotoki16:28
yushirogood night!16:28
*** yushiro has quit IRC16:28
*** hongbin has quit IRC16:37
*** Swami has quit IRC16:37
SridarKmlavalle: great all good so we are set16:42
SridarKhats off to yushiro annp hoangcx longkb16:43
xgerman_+1000016:46
reedipo/16:57
*** reedip has quit IRC17:14
*** SridarK has quit IRC17:20
*** SumitNaiksatam has joined #openstack-fwaas18:00
*** SridarK has joined #openstack-fwaas19:02
*** SumitNaiksatam has left #openstack-fwaas19:25
*** njohnston has quit IRC21:19
openstackgerritOpenStack Release Bot proposed openstack/neutron-fwaas master: Update reno for stable/rocky  https://review.openstack.org/59056721:53
*** yamamoto has joined #openstack-fwaas22:04
*** mlavalle has left #openstack-fwaas22:13
*** yamamoto has quit IRC22:21
*** SridarK has quit IRC22:26

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