Thursday, 2018-03-22

*** Swami has quit IRC00:02
*** yamamoto has joined #openstack-fwaas00:52
*** yamamoto has quit IRC00:57
*** yamamoto has joined #openstack-fwaas01:53
*** yamamoto has quit IRC01:59
*** yamamoto has joined #openstack-fwaas02:37
*** yamamoto has quit IRC02:46
*** yamamoto has joined #openstack-fwaas02:56
*** annp has joined #openstack-fwaas03:14
*** AlexeyAbashkin has joined #openstack-fwaas03:17
*** AlexeyAbashkin has quit IRC03:21
*** AlexeyAbashkin has joined #openstack-fwaas06:16
*** AlexeyAbashkin has quit IRC06:21
*** threestrands has quit IRC06:25
*** bbzhao has quit IRC07:25
*** bbzhao has joined #openstack-fwaas07:26
*** AlexeyAbashkin has joined #openstack-fwaas07:56
*** hoangcx has quit IRC08:03
*** hoangcx has joined #openstack-fwaas08:04
*** AlexeyAbashkin has quit IRC08:17
*** AlexeyAbashkin has joined #openstack-fwaas08:18
*** hoangcx has quit IRC08:35
*** hoangcx has joined #openstack-fwaas08:36
*** AlexeyAbashkin has quit IRC11:00
*** AlexeyAbashkin has joined #openstack-fwaas11:00
*** hoangcx_ has joined #openstack-fwaas12:45
*** yamamoto has quit IRC12:54
*** yamamoto has joined #openstack-fwaas13:21
*** SarathMekala has joined #openstack-fwaas13:47
*** yamamoto has quit IRC13:53
*** yushiro has joined #openstack-fwaas13:53
*** SridarK has joined #openstack-fwaas13:56
SridarKHi FWaaS folks13:59
xgerman_o/13:59
yushiroHi13:59
SridarK#startmeeting fwaas14:00
openstackMeeting started Thu Mar 22 14:00:11 2018 UTC and is due to finish in 60 minutes.  The chair is SridarK. 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: fwaas)"14:00
openstackThe meeting name has been set to 'fwaas'14:00
SridarK#chair xgerman_ yushiro14:00
openstackCurrent chairs: SridarK xgerman_ yushiro14:00
SridarKlets wait a few mins for more folks to join14:01
SarathMekalahi all o/14:01
yushirohi :)14:01
SarathMekalahi yushiro14:01
SridarKok lets get started14:02
yushiroYes14:02
SridarK#topic announcements14:02
*** openstack changes topic to "announcements (Meeting topic: fwaas)"14:02
SridarKWe had some issues with patches merging due to changes in dependencies - thankfully that is fixed and things are good now14:03
xgerman_+114:04
yushiro:)14:04
SridarKAlso thx to Swami to get a longstanding DVR related issue (change to namespace naming) fixed14:04
SarathMekala+114:04
SridarKI did not have anything else in particular14:05
*** annp_ has joined #openstack-fwaas14:05
xgerman_Some cross openstack activities:14:06
xgerman_https://review.openstack.org/#/c/53145614:06
xgerman_and https://review.openstack.org/#/c/548916/14:06
xgerman_One is for a uniform health check and the other chnages the maintenance window14:06
SridarKthx xgerman_ for bringing this up for all of us to be aware14:07
yushiroYes.14:07
yushiroMaybe it will discuss in Vancouver summit again.14:07
xgerman_probably…14:07
SridarKso once this is laid out - we will need to add some support for it14:07
SridarKHaving a uniform health check is great14:08
xgerman_+114:08
*** yamamoto has joined #openstack-fwaas14:08
xgerman_I hope that will extend to agents but we will see…14:09
amotokidoes anyone help http://lists.openstack.org/pipermail/openstack-operators/2018-March/015012.html?14:09
SridarKxgerman_: +114:09
amotokiahhhh... sorry for the meeting time14:09
SridarKamotoki: thx for pointing out14:10
xgerman_no, this is good info since I don’t subscribe to operators…14:10
SridarKneither do i14:10
amotokilet's discuss in open discussion14:10
xgerman_+114:10
SridarKwe will reach out to him14:10
yushiroamotoki, thanks.  I didn't know about that.14:10
SridarKamotoki: +114:10
SridarKAlso as usual the clock keeps ticking and we keep getting older and R-1 is Apr 16 - 2014:11
SridarKlets move on14:11
SridarK#topic Rocky priorities14:11
*** openstack changes topic to "Rocky priorities (Meeting topic: fwaas)"14:12
annp_may be we should unset port from default fwg first14:12
SridarKannp_: possibly - lets pick it up in open discussion14:12
annp_yeah.14:13
annp_please go ahead14:13
SridarKFirst up is Refactor for service driver pattern14:13
SridarKdoude:14:13
SridarKpls go ahead14:13
*** yamamoto has quit IRC14:13
SridarKdoude: i have started looking thru the patch - a bit slow on my part but i am on it14:13
SridarKwe will target this to get in before R-114:14
yushiroYes14:14
xgerman_+114:14
SridarKdoude: anything u would like to add or discuss ?14:15
SridarKok lets move on - i think doude may have stepped away14:16
SridarKBTW, I am trying to run thru #link https://etherpad.openstack.org/p/fwaas-rocky-planning14:16
xgerman_we probably should make that the channel topic ;-)14:17
SridarKxgerman_: +114:17
SridarK#topic tempest14:17
*** openstack changes topic to "tempest (Meeting topic: fwaas)"14:17
SridarKI had volunteered on this - not much update this week14:18
SridarKFirst step is to look at the changes to tempest - once I have a handle on that - will start some scenarios based on the manual testing we have been doing14:19
SridarK#topic Remote FWG14:19
*** openstack changes topic to "Remote FWG (Meeting topic: fwaas)"14:19
SridarKxgerman_: pls go ahead14:19
xgerman_I haven’t made much progress. Have been busy on urgent LBaaS stuff. I am hoping to get back to it next week…14:20
SridarKsounds good xgerman_ - perhaps we can target R-214:20
xgerman_Yes. that’s probably safer14:20
SridarKok14:20
SridarK#topic Horizon changes14:21
*** openstack changes topic to "Horizon changes (Meeting topic: fwaas)"14:21
SridarKSarathMekala: amotoki: pls go ahead14:21
amotokiSarathMekala: you around?14:21
SarathMekalayes amotoki14:21
SridarKamotoki: has fixed a number of issues for Queens14:21
SridarKso i think we need to validate where we are and see if there some things that are missing or need refactor14:22
amotokiI fixed several issues I thought important, but you can still find several bugs14:22
amotokihopefully SarathMekala and others can work on them https://bugs.launchpad.net/neutron-fwaas-dashboard14:23
SridarKamotoki: thx14:23
SarathMekalaamotoki: +114:23
amotokiI am happy to review and make suggestions14:23
SarathMekalaI will go through the fixes amotoki has done for Queens14:23
*** yamamoto has joined #openstack-fwaas14:24
amotokiSarathMekala: if you have questions, feel free to reach me14:24
yushirowill help it !14:24
SarathMekalaI was looking at enhancing the port details shown in the "Add Port" drop down..14:24
SridarKSarathMekala: ok we will need to see how things stand with the L2 support, Default FWG14:24
amotokiin addition, please review mox removal https://review.openstack.org/#/q/status:open+project:openstack/neutron-fwaas-dashboard+branch:master+topic:mox-removal14:24
yushiroamotoki, +1 OK14:25
amotokiit is part of the community goal. you don't need to worry much about them. they are just changes on testing :)14:25
yushirowill check it.14:25
SarathMekalasure amotoki14:25
SridarKamotoki: thx14:25
amotokijuts housekeeping things14:25
SarathMekalaSridarK: will look at the areas you pointed out14:26
SridarKok thx SarathMekala14:26
SridarK#topic DSCP filtering14:27
*** openstack changes topic to "DSCP filtering (Meeting topic: fwaas)"14:27
SridarKThis is something we can target - chandanc had some discussions with me on taking this on14:27
xgerman_nice. so redip is not going to do it?14:27
yushiro+114:28
SridarKxgerman_: i had mentioned to chandanc to check in with reedip as well14:28
*** yamamoto has quit IRC14:28
xgerman_ok, yes, redip has been quiet here so having some other point person is good14:28
SarathMekalachandanc asked me to inform that he wont be albe to join the meeting today14:28
SridarKbut i think he has been busy with other stuff - since i dont see him in ou rmtgs14:28
xgerman_+114:28
SridarKI can help with some of the plugin changes here14:29
SridarKSince the RFE is approved - we can work towards a spec and outline the changes14:29
SridarKLets discuss more when chandanc is around14:30
njohnston_Let me know how I can help out - DSCP filtering has been something I have been hoping for, for a long time14:30
xgerman_+!14:30
xgerman_njohnston_:  That would be great and appreciated14:30
SridarKnjohnston_: ok14:30
yushiro:)14:30
njohnston_DSCP filtering for firewalls was actually what got me into FWaaS in the first place :-)14:31
SridarKnjohnston_: same here - too and i filed the earlier bp :-)14:31
njohnston_:-)14:31
yushironjohnston_, SridarK That's great! I will also help on that.14:32
amotokiDSCP filtering might work, but I think we would like to know how it works from both fwaas and qos perspectives14:32
SridarKok14:32
SridarKamotoki: yes and possibly that might be a good use case for the Common Classifier work too14:32
njohnston_it definitely will, in the OVS case14:32
amotokiyeah, in other words, operator perspective :)14:33
njohnston_:-)14:33
*** njohnston_ is now known as njohnston14:33
yushiroYeah, good CCF case.14:33
SridarKok lets discuss more to outline the work items14:34
amotokido we have progress in CCF meetings or others?14:34
SridarKamotoki: i think the last was the discussion at PTG with xgerman_ and yushiro14:34
xgerman_yes, it was brief and we basically said yes, do it :-014:35
SridarKwith CCF i think once the team is ready we can look at adopting14:35
amotokiwe haven't tracked it in the neutron team meeting, so I just wonder how we can move it forward in rocky14:35
SridarKwas qos the first adopter ?14:35
xgerman_I think so…14:36
SridarKnjohnston: are u involved with the qos work ?14:36
amotokiokay, it seems we need to raise it to the neutron meeting if we don't have good progress for a while14:36
njohnstonI've been out of the QoS game for a while, reengaging with them as well.  I'll ping some folks and check on it14:37
yushiroOK, so I will try to reach out Isaku and David about current CCF progress.14:37
amotokiyushiro: +114:37
SridarKnjohnston: ok that will be good14:37
SridarKamotoki: yushiro +114:37
yushirohopefully, I'll invite them to this meeting.14:37
-amotoki- (or we can go to their meetings :)14:38
yushiroamotoki, +114:38
njohnstonI'm planning on going to their meeting next14:38
*** yamamoto has joined #openstack-fwaas14:39
yushironjohnston, +114:39
SridarKMy impression is that we can at least get a spec done in R and have a plan for implementation in S if not sooner14:39
xgerman_+114:39
SridarKok moving on14:39
amotokiwe seem to need a shared place to discuss it14:39
amotokitotally agree14:39
amotokilet's move on14:40
SridarK#topic FWaaS logging14:40
*** openstack changes topic to "FWaaS logging (Meeting topic: fwaas)"14:40
SridarKyushiro: pls go ahead14:40
yushiroSridarK, OK14:40
yushiro#link https://review.openstack.org/#/q/topic:bug/1720727+(status:open+OR+status:merged)14:41
yushiroCuong, annp_ , hoangcx and I are trying to implement fwaas logging.14:41
SridarK+114:41
amotokiyushiro: what is the next stage of this?14:41
amotokiyushiro: spec?14:42
yushiroCurrently, we're just staying until doube's patch.14:42
amotokiI'd just to clarify what is the next step/14:42
annp_I think spec is first step14:43
yushiroamotoki, Ah, now we're ready for review spec.14:43
yushiroJust a moment.14:43
*** yamamoto has quit IRC14:43
SridarKok that is good - we can discuss/review when u are ready14:43
xgerman_+114:43
annp_+114:44
yushiro#link https://review.openstack.org/#/c/509725/14:44
njohnston+114:44
amotokiyushiro: common understanding helps us focus on important things(s). spec review 509725?14:44
SridarKyushiro: thx14:45
yushiroamotoki, Yes14:45
amotokiyushiro's one seems our focus14:45
yushiroHopefully this spec will be merged until R-1.14:45
annp_+114:46
SridarKyushiro: i think that is reasonable14:46
amotokilooks good consensus14:46
*** yamamoto has joined #openstack-fwaas14:46
*** yamamoto has quit IRC14:46
yushiroSridarK, Yes.  In addition, I'm glad to be merged doube's patch :)14:47
yushiroduring R-1.  That is "nice timing" :-)14:47
amotokiyushiro: which do you mean by doube's patch?14:47
yushiroamotoki, Sorry.  I mean https://review.openstack.org/#/c/480265/14:48
yushiroplugable backend driver14:48
amotokiyushiro: got it14:48
SridarKyushiro: also i am thinking the fwaas logging will be similar in approach and work to the SG logging14:48
amotoki(i haven't got how it is related to the logging spec though)14:49
SridarKi am thinking at the driver level u may be able to leverage the SG work14:49
amotokiSridarK: +114:49
yushiroSridarK, Yes, same approach.  So, in case of fwaas, our target is  L2 and L3.  L2 is totally similar for SG.14:51
amotokithe API level topic and plugable backend driver topics needs to be discussed seperately14:51
yushiroamotoki, Yes, there is no relation b/w pluggable backend driver and logging patch.  I just concerned about conflict/rebase work.14:51
SridarK+114:52
amotokiyushiro: understandable14:52
yushiro:)14:52
SridarKok lets move on14:53
SridarK#topic Open Discussion14:53
*** openstack changes topic to "Open Discussion (Meeting topic: fwaas)"14:53
amotokiwhere do we maintain/collect meeting topics, wiki or etherpad? this is just a question.14:53
yushiroamotoki, https://etherpad.openstack.org/p/fwaas-meeting   but currently, not so maintained ...14:53
SridarKI dont see ndefigueiredo around so we will skip any discussion on stateless firewalling14:54
SridarKyushiro: +114:54
amotokithanks14:54
SridarKamotoki: today i am focussing on some things we prioritized in #link https://etherpad.openstack.org/p/fwaas-rocky-planning14:54
amotokibut it matches what http://eavesdrop.openstack.org/ says :)14:55
xgerman_Let’s talk about libraries which should support FWaaS V214:55
amotokigo ahead14:55
SridarKxgerman_: pls go ahead14:55
xgerman_we need to get support into shade, gophercloud, heat, etc.14:55
amotoki"libraries" seems to mean "python bindings"14:56
xgerman_gophercloud is a Go binding but yes… end users often use automation14:56
xgerman_so we need to figure out/track adoption14:56
njohnstonFog would be nice as well for Ruby developers, I understand it has quite a wide base of use14:57
*** reedip_ has joined #openstack-fwaas14:57
reedip_Late as usual... :(14:57
yushiroxgerman_, Just a question.  In order to support gophercloud for fwaas, do we need to add some codes/libraries into neutron-fwaas?14:57
*** Swami has joined #openstack-fwaas14:57
amotokias you may know, shard has been merged into python-openstacksdk which will be renamed to 'openstacksdk' soon14:57
yushirohi reedip_ :)14:57
xgerman_amotoki: +114:58
amotokis/shard/shade/14:58
reedip_Hi yushiro14:58
xgerman_yushiro: no. But we need to track adoption and help with it as necessary14:58
njohnstonyushiro: no.  I've done some gophercloud development work, it's just managing the API calls and unmarshalling the output into go structs14:58
xgerman_+114:58
yushironjohnston, xgerman_ OK, thanks.14:59
amotokiso, re: client bindings, we seem to track supports in various clients.14:59
xgerman_yes.14:59
amotokifor python stuffs, neutron team will cover this. we are planning to support fwaas in SDK in rocky hopefully14:59
xgerman_sweet15:00
amotokiany volunteers are welcome. feel free to contact me.15:00
reedip_Openstack SDK?15:00
amotokiyes15:00
reedip_Oh cool15:00
SridarKwe are at time but give our monopoly on this channel - lets take a few mins to wrap up15:00
amotokislawek will support reviews much15:00
yushiroamotoki, ping! sdk15:00
*** hoangcx_ has quit IRC15:01
SridarKxgerman_: can u pls track this as a topic for any work or investigation that is needed15:01
amotokiyushiro: it is related to SDK and CLI. let's make good progress15:01
yushiroOK15:01
xgerman_SridarK: will add to our Rocky etherpad15:01
SridarKgreat thx xgerman_ and we can scope15:01
xgerman_yeah, or at least reach out to those communities and make them aware of FWaaS V215:02
yushiroannp_, can we discuss after this meeting about  http://lists.openstack.org/pipermail/openstack-operators/2018-March/015012.html?15:02
annp_yes15:02
xgerman_+!15:02
SridarKamotoki: thx for the pointer to the issue reported on operators15:02
amotokigood remindier :15:02
amotoki:)15:02
yushiroamotoki, Yes, thanks15:02
SridarKwill reach out15:02
annp_I think currently we don't allow associated multiple fwg to a port15:03
amotokiperhaps we seem to clarify our concept and what we support now15:03
SridarKannp_: yes we dont support that15:03
yushiroannp_, Yes, but this error "<port-id> is invalid" is different case I think.15:03
annp_aha,15:04
SridarKand i dont think it is related to def fwg15:04
reedip_You might want to get some debug logs15:04
SridarKas he tried with router port as well15:04
yushiroI mean FirewallGroupPortInvalid is raised.15:04
amotokiyour point is correct. perhaps we haven't explained our concept yet :(15:04
annp_ok, I got it. I didn't read careful, So sorry. :(15:05
yushiroannp_, NP!15:05
amotokiwe would like to know how he was confused.15:05
amotokiit will help us15:05
yushiroYes.15:05
SridarKIt seems like a fairly straight fwd application15:06
amotokiyeah, let's ask him KINDLY :)15:06
SridarKMust be something we are missing here15:06
SridarKamotoki: ofcourse :-)15:06
yushiroI'll track on this mail too.  I wonder he specified "router:gateway" ...  Anyway, yes, it's better to ask him :)15:07
xgerman_+!15:07
annp_+115:07
SridarKOk will start a conversation and we can see how we can help15:07
SridarKi think we need to get some details15:07
yushiroYes15:07
amotokithough not directy related to fwaas, there were interesting posts in openstcak-operators ml recently15:07
SridarKand hopefully sort it out quickly15:07
xgerman_amotoki: tell us more ;-)15:08
amotokiit would be nice if you have chances to subscribe15:08
xgerman_yes, I will do so15:08
SridarK+115:08
yushiro+1  will do !15:08
amotokisurprisely, kevin is active on mailing lists this week :)15:08
SridarKoh yes15:08
SridarKi was wondering too15:09
SridarKok let me end the mtg15:09
amotoki:)15:09
SridarKthanks all for joining15:09
SridarKwe will track the user issue15:09
SridarK#endmeeting15:09
*** openstack changes topic to "Queens (Meeting topic: fwaas)"15:09
openstackMeeting ended Thu Mar 22 15:09:28 2018 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:09
openstackMinutes:        http://eavesdrop.openstack.org/meetings/fwaas/2018/fwaas.2018-03-22-14.00.html15:09
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/fwaas/2018/fwaas.2018-03-22-14.00.txt15:09
openstackLog:            http://eavesdrop.openstack.org/meetings/fwaas/2018/fwaas.2018-03-22-14.00.log.html15:09
xgerman_o/15:09
SarathMekalabye all15:09
SridarKbye all15:09
yushirobye bye15:09
amotokithanks all!15:09
yushirothanks15:10
annp_bye15:10
*** yushiro has quit IRC15:10
*** annp_ has quit IRC15:10
njohnstonyushiro: Here is an example of some code that I wrote with another person to support the Nova API's "Simple Tenant Usage" operations for gophercloud, to give you an idea of how it will look: https://github.com/gophercloud/gophercloud/pull/624/files15:10
reedip_njohnston :gr8 to see u back :)15:11
njohnstonreedip_: Good to be back :-)15:11
njohnstonI'm on the job market, looking for a job that can let work on openstack and actually dedicate some time to it15:12
reedip_Oh...15:14
reedip_I have come back to this meeting after several weeks...15:15
reedip_I have also lost track of Openstack community for now(trying to work on deployment). But hopefully would be able.to align both interests together soo15:15
*** reedip_ has quit IRC15:20
*** Swami has quit IRC15:29
*** SarathMekala has quit IRC15:37
*** yamamoto has joined #openstack-fwaas15:47
*** yamamoto has quit IRC15:53
doudeHi SridarK, sorry I could not attend the meeting15:56
*** yamamoto has joined #openstack-fwaas16:17
*** ignazio has joined #openstack-fwaas16:19
ignazioHello, I am looking for Sridar16:20
ignazioanyone could help me with fwaas v2 on ocata ?16:22
*** yamamoto has quit IRC16:22
*** ignazio has quit IRC16:24
*** yamamoto has joined #openstack-fwaas16:32
*** AlexeyAbashkin has quit IRC16:34
*** yamamoto has quit IRC16:36
*** yamamoto has joined #openstack-fwaas16:47
*** yamamoto has quit IRC16:52
*** SridarK has quit IRC17:01
*** yamamoto has joined #openstack-fwaas17:02
*** yamamoto has quit IRC17:06
*** yamamoto has joined #openstack-fwaas17:17
*** yamamoto has quit IRC17:22
*** yamamoto has joined #openstack-fwaas17:32
*** yamamoto has quit IRC17:37
*** yamamoto has joined #openstack-fwaas17:47
*** yamamoto has quit IRC17:52
*** yamamoto has joined #openstack-fwaas18:02
*** yamamoto has quit IRC18:06
*** yamamoto has joined #openstack-fwaas18:06
*** yamamoto has quit IRC18:06
*** AlexeyAbashkin has joined #openstack-fwaas18:15
*** SridarK has joined #openstack-fwaas18:17
*** AlexeyAbashkin has quit IRC18:20
*** yamamoto has joined #openstack-fwaas19:07
*** Swami has joined #openstack-fwaas19:10
*** yamamoto has quit IRC19:13
*** yamamoto has joined #openstack-fwaas20:09
*** yamamoto has quit IRC20:14
*** AlexeyAbashkin has joined #openstack-fwaas20:45
*** AlexeyAbashkin has quit IRC20:52
*** yamamoto has joined #openstack-fwaas21:10
*** yamamoto has quit IRC21:16
*** AlexeyAbashkin has joined #openstack-fwaas21:17
*** AlexeyAbashkin has quit IRC21:21
*** yamamoto has joined #openstack-fwaas21:55
*** SridarK has quit IRC22:10
*** AlexeyAbashkin has joined #openstack-fwaas23:16
*** AlexeyAbashkin has quit IRC23:20
*** Swami has quit IRC23:26

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