| *** sterdnotshaken1 has quit IRC | 00:41 | |
| -openstackstatus- NOTICE: Gerrit is being restarted to feed its insatiable memory appetite | 02:40 | |
| *** sterdnotshaken has joined #openstack-fwaas | 03:34 | |
| reedip | hello | 03:37 |
|---|---|---|
| *** sterdnotshaken has quit IRC | 04:09 | |
| *** lnicolas has quit IRC | 04:33 | |
| *** lnicolas has joined #openstack-fwaas | 04:56 | |
| *** yamamoto has quit IRC | 04:57 | |
| *** yamamoto has joined #openstack-fwaas | 05:07 | |
| *** bzhao has joined #openstack-fwaas | 06:16 | |
| *** hoangcx has quit IRC | 06:20 | |
| *** hoangcx has joined #openstack-fwaas | 06:28 | |
| -openstackstatus- NOTICE: Post jobs are not executed currently, do not tag any releases | 07:21 | |
| *** ChanServ changes topic to "Post jobs are not executed currently, do not tag any releases" | 07:21 | |
| *** bbzhao has joined #openstack-fwaas | 07:32 | |
| *** bzhao has quit IRC | 07:35 | |
| *** eezhova has joined #openstack-fwaas | 08:31 | |
| *** yamamoto has quit IRC | 09:07 | |
| *** yamamoto has joined #openstack-fwaas | 09:32 | |
| *** reedip has quit IRC | 09:47 | |
| *** reedip has joined #openstack-fwaas | 09:47 | |
| *** yamamoto has quit IRC | 10:34 | |
| *** yamamoto has joined #openstack-fwaas | 10:38 | |
| *** yamamoto has quit IRC | 10:47 | |
| *** yamamoto has joined #openstack-fwaas | 11:23 | |
| *** eezhova has quit IRC | 11:26 | |
| *** eezhova has joined #openstack-fwaas | 11:42 | |
| *** ivasilevskaya1 has joined #openstack-fwaas | 12:35 | |
| *** ivasilevskaya has quit IRC | 12:36 | |
| *** eezhova_ has joined #openstack-fwaas | 12:39 | |
| *** eezhova has quit IRC | 12:41 | |
| *** bbzhao has quit IRC | 12:47 | |
| *** bbzhao has joined #openstack-fwaas | 12:47 | |
| *** eezhova_ has quit IRC | 13:03 | |
| *** eezhova_ has joined #openstack-fwaas | 13:10 | |
| *** hoangcx_ has joined #openstack-fwaas | 13:45 | |
| *** chandanc has joined #openstack-fwaas | 13:57 | |
| *** eezhova has joined #openstack-fwaas | 13:58 | |
| *** yushiro has joined #openstack-fwaas | 13:59 | |
| *** reedip_ has joined #openstack-fwaas | 14:00 | |
| *** eezhova_ has quit IRC | 14:00 | |
| *** yamamoto has quit IRC | 14:20 | |
| reedip_ | https://doodle.com/poll/c5rgth6y54bpvncu is the link for voting for the Day of FWaaS meeting . Will share in the actual meeting channel as well | 14:41 |
| *** SridarK has joined #openstack-fwaas | 14:59 | |
| *** sterdnotshaken has joined #openstack-fwaas | 15:00 | |
| amotoki | I wonder we can use #startmeeting here considering the office hour concept... | 15:00 |
| *** annp has joined #openstack-fwaas | 15:01 | |
| ivasilevskaya1 | didn't we want to divide the work on the patches? Or is it done already? | 15:01 |
| reedip_ | #startmeeting fwaas ? | 15:01 |
| openstack | Meeting started Tue Sep 19 15:01:10 2017 UTC and is due to finish in 60 minutes. The chair is reedip_. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:01 |
| reedip_ | no its to be discussed | 15:01 |
| openstack | The meeting name has been set to 'fwaas__' | 15:01 |
| reedip_ | lol ... | 15:01 |
| SridarK | :-) | 15:01 |
| reedip_ | #chair yushiro SridarK xgerman_ | 15:01 |
| yushiro | ivasilevskaya1, I'd like to devide each patches and TODOs. | 15:01 |
| openstack | Current chairs: SridarK reedip_ xgerman_ yushiro | 15:01 |
| amotoki | wow | 15:01 |
| yushiro | wow | 15:01 |
| amotoki | but we should stop this meeting | 15:01 |
| amotoki | the meeting name is incorrect :( | 15:02 |
| ivasilevskaya1 | I'd like to help with whatever I can. Default fwg looks like a doable thing for example | 15:02 |
| reedip_ | amotoki : sure ??? | 15:02 |
| SridarK | i hope eavesdrop will not get messed up | 15:02 |
| SridarK | for logs | 15:02 |
| xgerman_ | yep | 15:02 |
| reedip_ | #endmeeting | 15:02 |
| openstack | Meeting ended Tue Sep 19 15:02:28 2017 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 15:02 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/fwaas__/2017/fwaas__.2017-09-19-15.01.html | 15:02 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/fwaas__/2017/fwaas__.2017-09-19-15.01.txt | 15:02 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/fwaas__/2017/fwaas__.2017-09-19-15.01.log.html | 15:02 |
| reedip_ | lol | 15:02 |
| reedip_ | anyways, lets start | 15:02 |
| *** chandanc has quit IRC | 15:02 | |
| amotoki | we already polluted eavesdrop :( | 15:02 |
| amotoki | hehe | 15:03 |
| SridarK | oh boy | 15:03 |
| amotoki | continue the meeting? | 15:03 |
| yushiro | haha, yes. | 15:03 |
| reedip_ | nevermind, I would be the one who would be screwed up | 15:03 |
| yushiro | let me continue it. | 15:03 |
| xgerman_ | k | 15:03 |
| reedip_ | yushiro : so I would be working with ivasilevskaya1 ( Please have a shorted IRC Nick ... ) in the default FWG | 15:04 |
| SridarK | lets focus on getting the L2 agent PS solid | 15:05 |
| yushiro | reedip_, OK. So, plz tell me the relation https://review.openstack.org/#/c/504847 and my patch. | 15:05 |
| ivasilevskaya1 | can l2 extension patch be made independent of default fwg? | 15:05 |
| SridarK | i would ask if we can also track on an etherpad so have some testing done | 15:05 |
| reedip_ | yushiro : wiat, there is a lizard here in the kitchen ... | 15:06 |
| SridarK | reedip_: can he also work on any of PS ? ;-) | 15:06 |
| reedip_ | SridarK :wait , lemme ask it | 15:06 |
| yushiro | ivasilevskaya1, Maybe yes. Previously, I mixtured b/w L2-agent and default fwg patches.. | 15:06 |
| reedip_ | Mom is scared :P | 15:07 |
| reedip_ | Ok, back to the topic | 15:07 |
| reedip_ | ivasilevskaya1 and yushiro : we have 3 patches now | 15:07 |
| xgerman_ | yes, l2 and default FWG can be independent | 15:07 |
| reedip_ | ivasilevskaya1 and yushiro : Default FWG : https://review.openstack.org/425769 | 15:07 |
| reedip_ | ivasilevskaya1 and yushiro : L2 Agent : https://review.openstack.org/323971 | 15:08 |
| *** hoangcx_ has quit IRC | 15:08 | |
| reedip_ | ivasilevskaya1 and yushiro : Default FWG ON L2 Agent https://review.openstack.org/504847 | 15:08 |
| reedip_ | So default FWG and L2 agent can be independent and https://review.openstack.org/504847 depends on both of these | 15:08 |
| reedip_ | annp : thanks for the patch :) | 15:08 |
| annp | reedip, :) you're welcome. | 15:09 |
| yushiro | annp, Thanks for your great help | 15:09 |
| reedip_ | yushiro : I hope your doubt is cleared now ? | 15:09 |
| ivasilevskaya1 | And what's the strategy of default fwg generation? Previously it was 'create one on list' and there were some concerns | 15:09 |
| yushiro | and, OVS based l2 Firewall driver https://review.openstack.org/#/c/447251/ | 15:10 |
| reedip_ | yushiro : yep | 15:10 |
| yushiro | ivasilevskaya1, I simply referred default security-group generation. | 15:11 |
| reedip_ | SridarK , xgerman_ , yushiro : Do we need to create a Default FWG on the list command ? | 15:11 |
| reedip_ | is the default FWG completely like the default SG ? | 15:11 |
| xgerman_ | right now yes | 15:11 |
| yushiro | reedip_, yes. | 15:11 |
| reedip_ | if someone deletes the default FWG, should it be recreated ? | 15:11 |
| xgerman_ | we have plans to extend to strata | 15:11 |
| xgerman_ | reedip_ not sure if you can delete the default SG | 15:12 |
| xgerman_ | (never tried) | 15:12 |
| reedip_ | xgerman_ but we can delete the default FWG | 15:12 |
| ivasilevskaya1 | in neutron - you can't. Or actually you can but it will come back | 15:12 |
| ivasilevskaya1 | after first list command :) | 15:13 |
| yushiro | Even if admin can delete default sg, it will be generated automatically. | 15:13 |
| ivasilevskaya1 | if port_security is enabled | 15:13 |
| yushiro | ivasilevskaya1, correct. | 15:13 |
| xgerman_ | ok, not sure if we need to copy the list way but it makes sense | 15:13 |
| yushiro | So, more detail, a behavior of default fwg is same as default sg with port_security = True. | 15:13 |
| xgerman_ | yes | 15:14 |
| yushiro | This is current impl. | 15:14 |
| xgerman_ | this is our Queens goal | 15:14 |
| SridarK | yes - so we shd strive for some consistency with sg | 15:14 |
| ivasilevskaya1 | if behavior is the same then keeping 'generate on list' may be ok for now | 15:14 |
| reedip_ | hmm ... then I would like to know if deleting the default FWG also deletes the default Policies and default rules ? | 15:15 |
| reedip_ | hmm ... then I would like to know if deleting the default FWG also deletes the default Policies and default rules ? | 15:15 |
| xgerman_ | yes, it would be confusing to have the user delete then start a vm and the FWG magically is created and applied | 15:15 |
| reedip_ | xgerman_ but thats just like the SG | 15:16 |
| yushiro | reedip_, Currently, if default fwg is deleted, default policy and rule still alives. | 15:16 |
| xgerman_ | on second thought, if we can just bot have a user delete it that migth be better | 15:16 |
| xgerman_ | bot=not | 15:16 |
| yushiro | So, If admin tries to delete default fwg many times, a lot of default policy/rule will be generated. Hmm, I think it should be deleted at the same time. | 15:17 |
| xgerman_ | this letting you delete and magically re-appear is confusing | 15:17 |
| reedip_ | yushiro : then the code can be improved. When a new default FWG is created, a new policy and rule is created Which means we would have a lot of policies and rules, everytime user deletes the FWG and then does a List | 15:17 |
| reedip_ | yushiro: right :) | 15:17 |
| ivasilevskaya1 | oh, sounds like a nice testcase :) | 15:17 |
| xgerman_ | let’s just go with not letting the user delete Default FWG | 15:17 |
| reedip_ | Let me and ivasilevskaya1 look at it. Maybe we can reuse the policies and rules | 15:17 |
| reedip_ | xgerman_ that would be different than the default SG | 15:18 |
| yushiro | reedip_, I'd like to ask you about this fix. Is it OK? | 15:18 |
| ivasilevskaya1 | xgerman_: even the admin? | 15:18 |
| ivasilevskaya1 | oh, it's only the admin who can do it actually | 15:18 |
| xgerman_ | and it seems to be a NOOP | 15:18 |
| reedip_ | yushiro : sure , we can test and update the code ... :) | 15:18 |
| xgerman_ | not sure if allowing to delete ion order to regenerate adds value | 15:19 |
| reedip_ | I think SridarK is getting ready for office | 15:19 |
| yushiro | OK, next. OVS driver for l2 | 15:19 |
| ivasilevskaya1 | xgerman_: sounds reasonable. | 15:19 |
| yushiro | #link https://review.openstack.org/#/c/447251/ | 15:19 |
| xgerman_ | also FWG are allow all if you don’t add a deny rule | 15:19 |
| reedip_ | xgerman_ we should rename default FWG as the Pheonix FWG | 15:19 |
| reedip_ | xgerman_ lets keep the current behavior for now ... | 15:19 |
| xgerman_ | k | 15:20 |
| SridarK | reedip_: yes sorry i have to leave for work soon | 15:20 |
| *** chandanc has joined #openstack-fwaas | 15:20 | |
| yushiro | chandanc, | 15:20 |
| yushiro | hi | 15:20 |
| ivasilevskaya1 | xgerman_: allow all? as in newton spec? | 15:20 |
| *** yamamoto has joined #openstack-fwaas | 15:20 | |
| chandanc | hello | 15:20 |
| chandanc | yushiro: | 15:21 |
| yushiro | chandanc, hello, how are you? | 15:21 |
| chandanc | sorry i got disconnected | 15:21 |
| chandanc | i am doing ok | 15:21 |
| yushiro | don't worry :) | 15:21 |
| SridarK | yushiro: so chandanc and i talked last night | 15:21 |
| xgerman_ | yes, so SG are deny all by default and youa dd allow rules | 15:21 |
| xgerman_ | we allow both deny and allow so without any rules we allow all | 15:21 |
| SridarK | i gave him quick update on the cookies for clean up | 15:22 |
| xgerman_ | ahm policies | 15:22 |
| yushiro | #link https://review.openstack.org/#/c/447251/ | 15:22 |
| reedip_ | SridarK : its ok :) | 15:22 |
| reedip_ | yushiro : chandanc is here ... | 15:22 |
| reedip_ | :D | 15:22 |
| yushiro | chandanc, There is some comments for this. Did you check these comments? | 15:22 |
| SridarK | xgerman_: actually if there is a policy - we will have a deny all by default | 15:23 |
| chandanc | yes, i did but could not make the patch ready yet | 15:23 |
| chandanc | the UT one should be taken up after a resync with ovs from newtron | 15:24 |
| yushiro | Ok. | 15:24 |
| yushiro | BTW, ivasilevskaya1 , you pushed interesting WIP: https://review.openstack.org/#/c/499291/ | 15:24 |
| *** yamamoto has quit IRC | 15:25 | |
| xgerman_ | SridarK thanks — I was thinking the no policy case | 15:25 |
| yushiro | I discussed with jakub who is one of neutron core about this patch and he said looks good. | 15:25 |
| xgerman_ | sweet | 15:25 |
| ivasilevskaya1 | yushiro: I did but left it hanging because I needed more info from you. I contacted jlibosva (the one who implented ovsfw for neutron) and this will work if we come up with common api | 15:26 |
| yushiro | ivasilevskaya1, I think this approach is pretty better for the future maintenance perspective. | 15:26 |
| ivasilevskaya1 | but I see you have no conj_manager in ovs driver | 15:26 |
| SridarK | ivasilevskaya1: yes this is most interesting - i think we should support this effort | 15:26 |
| ivasilevskaya1 | and I couldn't find a reason why | 15:26 |
| SridarK | less duplication | 15:26 |
| xgerman_ | +1 | 15:26 |
| reedip_ | I am checking the patch and I think its good ... | 15:28 |
| *** eezhova has quit IRC | 15:28 | |
| reedip_ | :) | 15:28 |
| yushiro | ivasilevskaya1, sorry, I have not enough knowledge about conj_manager. In order to retrieve it, is it necessary to update neutron's repos? | 15:28 |
| SridarK | ivasilevskaya1: the one thing - is that the timelines - i would really like to see us wrap up the L2 support in the next few weeks | 15:29 |
| SridarK | my concern is if we get stalled on neutron | 15:29 |
| SridarK | we kind of got stuck in this manner when we were working with iptables | 15:29 |
| yushiro | hopefully integrating with chandanc's patch.. | 15:29 |
| yushiro | SridarK, Yess.. My main concern is this. | 15:30 |
| ivasilevskaya1 | I bet we it'll take more than a month to get landed in neutron. So maybe we may go on with a neutron-ovsfw-fork approach we have now | 15:30 |
| SridarK | and if we see that a common & cleaner approach can move fwd - we can refactor | 15:30 |
| xgerman_ | yes, let’s take. a good approach now and do the better in the future | 15:30 |
| SridarK | ivasilevskaya1: yes indeed | 15:30 |
| yushiro | ivasilevskaya1, +1 | 15:30 |
| amotoki | I am not sure we don't need to care code duplication so much. This is the stage we figure out what are really needed | 15:30 |
| xgerman_ | +1 | 15:30 |
| chandanc | +1 | 15:30 |
| SridarK | exactly - and we can refactor | 15:31 |
| yushiro | amotoki, Thanks. OK, so, how about keeping current approach and will refactor ? | 15:31 |
| reedip_ | +1 | 15:31 |
| amotoki | and perhaps it would be really nice if we can explore how we can improve the maintenance-ability as ivasilevskaya1 or other suggest | 15:31 |
| ivasilevskaya1 | SridarK: sorry for getting back to default fwg - I'm a bit confused about policies. Should they be allow all (newton spec) or deny all (inline comments)? | 15:31 |
| amotoki | yushiro: I think so though I am not an expert on that area | 15:31 |
| chandanc | AFAIK the conj_mgr is the new code introduced after we forked | 15:32 |
| chandanc | i looked itto it | 15:32 |
| SridarK | default should not be allow all | 15:32 |
| yushiro | chandanc, Aha. | 15:32 |
| SridarK | but we should allow enough so that dhcp will work etc | 15:32 |
| SridarK | similar to SG | 15:32 |
| chandanc | but as we have some differences with SG we need to adapt the code | 15:32 |
| ivasilevskaya1 | SridarK: ok! finally sorted out | 15:32 |
| reedip_ | ivasilevskaya1 : can I modify the patch a bit ? | 15:32 |
| xgerman_ | SridarK +1 | 15:32 |
| chandanc | SridarK: dhcp and DNS are already part of default rule set | 15:33 |
| SridarK | if we had a fwg (not default fwg) then we would do a deny all as a default | 15:33 |
| chandanc | i this is borrowed from the SG code | 15:33 |
| SridarK | but then the user/admin will add rules as they see fit | 15:33 |
| chandanc | SridarK: i agree there is a conflict in the approach with DFG | 15:33 |
| SridarK | we use a deny all when updates are in process also | 15:34 |
| SridarK | as i see it - DFG only when an user/admin did not add a FWG | 15:34 |
| SridarK | sorry i should run out soon | 15:35 |
| ivasilevskaya1 | on the other hand - if we don't setup a FG (any additional policies) - neutron SG come into play | 15:35 |
| ivasilevskaya1 | so maybe an allow all is ok | 15:36 |
| yushiro | OK, so, please let me back to OVS fw patch: https://review.openstack.org/#/c/447251/ | 15:36 |
| SridarK | ivasilevskaya1: yes the SG will always be there but if the SG is configured with noop driver | 15:36 |
| SridarK | then we will open things up | 15:36 |
| xgerman_ | yep | 15:36 |
| reedip_ | ivasilevskaya1 : I think the current behavior ( ingress to VM deny, egress from VM allow ) would be more secured | 15:36 |
| yushiro | chandanc, Do u need some help for updating? | 15:36 |
| chandanc | yushiro: sure i can ues some help | 15:36 |
| yushiro | ues --> yours ? | 15:37 |
| chandanc | "use” Sorry | 15:37 |
| SridarK | ivasilevskaya1: so if the SG is present - (default) and a DFWG - we would be doing the same thing (kind of redundant) | 15:37 |
| chandanc | are you looking into the patch yushiro ? | 15:37 |
| reedip_ | SridarK : but thats secured | 15:37 |
| SridarK | but if the SG is configured with noop driver then we want the DFWG to do the right thing | 15:38 |
| reedip_ | redundancy is OK as far as we iensure security | 15:38 |
| reedip_ | thats why its Firewall :D | 15:38 |
| yushiro | chandanc, Currently, not sure but I know one TODO is to migrate testcode from neutron repos. | 15:38 |
| ivasilevskaya1 | SridarK: honestly I've seen no deployments with noop SG driver for years | 15:38 |
| SridarK | and a permit is only when permit happens on both SG and FWG (logical AND) | 15:38 |
| chandanc | yushiro: yes that is correct | 15:38 |
| yushiro | chandanc, In order to migrate/run neutron's testcode for OVS fw driver, is it necessary to fork latest code? | 15:39 |
| SridarK | ivasilevskaya1: that i am inclined to agree but sometimes i think deployers if they a perimeter FW then they take this approach | 15:39 |
| SridarK | but possibly rare | 15:39 |
| chandanc | yes, the nes code is considerably different | 15:39 |
| reedip_ | nes -> new | 15:39 |
| reedip_ | :) | 15:39 |
| ivasilevskaya1 | yushiro: we might want to update the whole fork code. To get conj_manager and cool bugfixes | 15:39 |
| chandanc | yes | 15:40 |
| yushiro | ivasilevskaya1, +3.141592 I think it's better. | 15:40 |
| reedip_ | 22/7 ? | 15:40 |
| SridarK | ivasilevskaya1: let me go thru the current spec and start an etherpad on things we have deviated | 15:40 |
| reedip_ | ivasilevskaya1 : I updated the constants in your patch with https://github.com/openstack/neutron/blob/6077d778e9019fdac876ad1346e562f78843c328/neutron/plugins/ml2/drivers/openvswitch/agent/common/constants.py | 15:40 |
| SridarK | how abt we use that to ensure clarity for reviewers | 15:41 |
| SridarK | then as next step we overhaul the spec | 15:41 |
| yushiro | OK, so, 1. folk ovs fw driver from latest code and also migrates testcode. | 15:41 |
| reedip_ | SridarK : sounds about right, if we can use the etherpad as a doc for L2 agent as well | 15:41 |
| SridarK | reedip_: yes one etherpad | 15:41 |
| ivasilevskaya1 | reedip_: ok | 15:42 |
| SridarK | give me a day or 2 - i will get that started | 15:42 |
| yushiro | chandanc, Can u do it? ivasilevskaya1, if possible, I'd like you to help this patch. | 15:42 |
| yushiro | It is really helpful for OVS driver side. :) | 15:42 |
| ivasilevskaya1 | yushiro, ok, I'll see into it tonight then | 15:42 |
| annp | chandanc and yushiro, if you want to some help, i can do it | 15:42 |
| chandanc | annp: sure jump in | 15:42 |
| yushiro | annp, OK, thanks annp. But I think we can also focus on logging :) | 15:43 |
| reedip_ | ivasilevskaya1 : I will look up the default FWG , if thats ok with you ... I dont know much about OVS so I would like to watch from the side :) | 15:43 |
| annp | chandanc, thanks. | 15:43 |
| SridarK | chandanc: can u pls establish where u need help - so folks are not stepping on each other's toes | 15:43 |
| yushiro | OK, chandanc and ivasilevskaya1 update OVS fw driver. 1.Update from latest OVS fw code and migrate testcode. | 15:44 |
| annp | yushiro: sure, logging first, and ovs fw also. :) | 15:44 |
| reedip_ | ivasilevskaya1 : I will update it with the test for multiple Policies and Rules which can screw things up. | 15:44 |
| yushiro | annp, Thanks for your help | 15:44 |
| chandanc | SridarK: annp : I will send a summary by tomorrow to the team | 15:44 |
| yushiro | #action | 15:44 |
| yushiro | oops, sorry | 15:44 |
| SridarK | chandanc: ok sounds good | 15:44 |
| SridarK | yushiro: :-) | 15:44 |
| SridarK | yushiro: i think u need to go to bed :-) | 15:44 |
| yushiro | #action chandanc and ivasilevskaya1 update OVS fw driver. 1.Update from latest OVS fw code and migrate testcode. | 15:44 |
| chandanc | annp: Are you familier with the driver code ? | 15:44 |
| yushiro | SridarK, Thanks but please let me sync up with TODOs for great members :) | 15:45 |
| annp | chandanc, I have a little bit about ovs firewall driver code in neutron. | 15:46 |
| ivasilevskaya1 | reedip_: cool! there were some unresolved comments in latest patchsets (the bug we noticed about wrong rules in policies) iirc | 15:46 |
| reedip_ | yep.... | 15:46 |
| annp | chandanc, So i think i can help you something.\ | 15:46 |
| chandanc | annp: ok, we can chat after i sumarize the current state | 15:46 |
| reedip_ | yushiro the # action wont work , there is no meeting :) | 15:46 |
| yushiro | reedip_, oh boy :-) | 15:47 |
| annp | chandanc: sure, let share it with me. | 15:47 |
| yushiro | chandanc, annp ivasilevskaya1 Thanks guys for your help!! | 15:47 |
| annp | chandanc, tomorrow is ok for me. because i have to go bed, now | 15:47 |
| yushiro | annp, Good night~ | 15:47 |
| annp | yushiro, good night | 15:48 |
| chandanc | ok sure annp | 15:48 |
| annp | good night folks. | 15:48 |
| reedip_ | annp , yushiro : are you not in the same office ??? :P | 15:48 |
| reedip_ | gn annp | 15:48 |
| yushiro | reedip_, I'm in my home :) | 15:48 |
| annp | reedip, i'm in my home too | 15:48 |
| reedip_ | but you would meet in the morning, right ?? :P | 15:49 |
| *** annp has quit IRC | 15:49 | |
| yushiro | reedip_, Yes, but it's OK to get up a little bit late after IRC meeting. | 15:49 |
| yushiro | It's safety working :) | 15:50 |
| reedip_ | :) | 15:50 |
| yushiro | ah | 15:51 |
| reedip_ | I think all the discussions are over :) | 15:52 |
| *** yamamoto has joined #openstack-fwaas | 15:52 | |
| yushiro | Yes. | 15:53 |
| reedip_ | so you can go to sleep :P ... I will have my dinner too | 15:53 |
| yushiro | folks, If you add some patches for FWaaS v2, please specify 'bp/fwaas-api-2' as topic branch name. | 15:53 |
| reedip_ | good idea yushiro | 15:54 |
| yushiro | Because it is easy to summarize and tracking like: https://review.openstack.org/#/q/topic:bp/fwaas-api-2+(status:open+OR+status:merged) | 15:54 |
| *** sterdnotshaken has quit IRC | 15:54 | |
| *** sterdnotshaken has joined #openstack-fwaas | 15:54 | |
| *** chandanc_ has joined #openstack-fwaas | 15:54 | |
| *** chandanc has quit IRC | 15:54 | |
| *** chandanc_ is now known as chandanc | 15:54 | |
| yushiro | I just changed topic branch name for https://review.openstack.org/#/c/504847/ | 15:54 |
| *** sterdnotshaken1 has joined #openstack-fwaas | 15:57 | |
| *** sterdnotshaken has quit IRC | 15:57 | |
| *** sterdnotshaken has joined #openstack-fwaas | 15:58 | |
| *** sterdnotshaken1 has quit IRC | 15:58 | |
| reedip_ | ok guys, I will take a leave now... will catch up with you tomorrow morning.... | 15:59 |
| reedip_ | ivasilevskaya1 : whats your TZ ? Would like to know when I can ping u | 15:59 |
| *** chandanc_ has joined #openstack-fwaas | 15:59 | |
| *** sterdnotshaken1 has joined #openstack-fwaas | 16:00 | |
| *** sterdnotshaken has quit IRC | 16:00 | |
| *** chandanc_ has quit IRC | 16:00 | |
| *** chandanc has quit IRC | 16:01 | |
| *** yamamoto has quit IRC | 16:03 | |
| yushiro | xgerman_, Would it be possible to change URL for https://blueprints.launchpad.net/neutron/+spec/fwaas-api-2.0 ? | 16:08 |
| yushiro | We added tags in commit message like "Partial-Implements: blueprint fwaas-api-2.0" but it cannot be linked... | 16:09 |
| yushiro | I think period "." is not retrieved as the link. "Partial-Implements: blueprint fwaas-api-2.0" | 16:09 |
| yushiro | OK, see you... | 16:10 |
| xgerman_ | I don’t see an edit button near the title | 16:10 |
| yushiro | OK, thanks for your check. | 16:11 |
| xgerman_ | can’t we use “link a related patch” and do it manually? | 16:11 |
| yushiro | Ah, I think it's better :) | 16:11 |
| yushiro | OK, will comment. | 16:11 |
| *** sterdnotshaken has joined #openstack-fwaas | 16:12 | |
| *** sterdnotshaken1 has quit IRC | 16:12 | |
| *** yushiro has quit IRC | 16:12 | |
| *** sterdnotshaken1 has joined #openstack-fwaas | 16:13 | |
| *** sterdnotshaken has quit IRC | 16:13 | |
| *** sterdnotshaken has joined #openstack-fwaas | 16:14 | |
| *** sterdnotshaken1 has quit IRC | 16:14 | |
| *** eezhova has joined #openstack-fwaas | 16:28 | |
| openstackgerrit | Yushiro FURUKAWA proposed openstack/neutron-fwaas master: Add directories for in-tree documentation https://review.openstack.org/505326 | 16:34 |
| *** SridarK has quit IRC | 16:43 | |
| *** sterdnotshaken1 has joined #openstack-fwaas | 17:00 | |
| *** sterdnotshaken has quit IRC | 17:00 | |
| *** sterdnotshaken has joined #openstack-fwaas | 17:03 | |
| *** sterdnotshaken1 has quit IRC | 17:03 | |
| *** sterdnotshaken1 has joined #openstack-fwaas | 17:05 | |
| *** sterdnotshaken has quit IRC | 17:05 | |
| *** reedip_ has quit IRC | 17:30 | |
| *** ying_zuo has left #openstack-fwaas | 18:07 | |
| *** sterdnotshaken1 has quit IRC | 18:27 | |
| *** eezhova has quit IRC | 18:34 | |
| *** sterdnotshaken has joined #openstack-fwaas | 18:56 | |
| *** eezhova has joined #openstack-fwaas | 19:50 | |
| -openstackstatus- NOTICE: Zuul and Gerrit are being restarted to address issues discovered with the Gerrit 2.13 upgrade. review.openstack.org will be inaccessible for a few minutes while we make these changes. Currently running jobs will be restarted for you once Zuul and Gerrit are running again. | 20:26 | |
| *** sterdnotshaken1 has joined #openstack-fwaas | 20:58 | |
| *** sterdnotshaken has quit IRC | 20:58 | |
| *** sterdnotshaken has joined #openstack-fwaas | 21:51 | |
| *** sterdnotshaken1 has quit IRC | 21:51 | |
| *** sterdnotshaken1 has joined #openstack-fwaas | 21:53 | |
| *** sterdnotshaken has quit IRC | 21:54 | |
| *** sterdnotshaken has joined #openstack-fwaas | 21:54 | |
| *** sterdnotshaken2 has joined #openstack-fwaas | 21:56 | |
| *** sterdnotshaken has quit IRC | 21:56 | |
| *** sterdnotshaken1 has quit IRC | 21:57 | |
| *** yamamoto_ has joined #openstack-fwaas | 22:19 | |
| -openstackstatus- NOTICE: Gerrit is being restarted to address some final issues, review.openstack.org will be inaccessible for a few minutes while we restart | 22:32 | |
| *** sterdnotshaken2 has quit IRC | 22:33 | |
| *** eezhova has quit IRC | 22:35 | |
| *** openstackgerrit has quit IRC | 22:47 | |
| *** ChanServ changes topic to "#openstack-fwaas" | 23:38 | |
| -openstackstatus- NOTICE: Gerrit is once again part of normal puppet config management. Problems with Gerrit gitweb links and Zuul post jobs have been addressed. We currently cannot create new gerrit projects (fixes in progress) and email sending is slow (being debugged). | 23:38 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!