Thursday, 2017-02-09

*** padkrish has quit IRC00:05
*** padkrish has joined #openstack-fwaas00:06
*** reedip_ has joined #openstack-fwaas00:25
*** reedip_ has quit IRC00:26
*** lnicolas has joined #openstack-fwaas00:40
*** hoangcx has joined #openstack-fwaas00:54
*** yushiro has quit IRC01:23
*** padkrish has quit IRC01:56
*** mickeys has quit IRC02:05
*** reedip_ has joined #openstack-fwaas02:09
*** padkrish has joined #openstack-fwaas02:18
*** reedip_1 has joined #openstack-fwaas02:30
*** reedip_ has quit IRC02:31
*** padkrish has quit IRC02:44
*** padkrish has joined #openstack-fwaas02:45
*** padkrish has quit IRC02:56
*** openstackstatus has quit IRC02:58
*** openstackstatus has joined #openstack-fwaas03:00
*** ChanServ sets mode: +v openstackstatus03:00
*** padkrish has joined #openstack-fwaas03:37
*** padkrish has quit IRC03:49
*** padkrish has joined #openstack-fwaas03:56
*** yushiro has joined #openstack-fwaas03:59
*** mickeys has joined #openstack-fwaas03:59
*** padkrish has quit IRC04:01
*** reedip_1 has quit IRC04:06
*** padkrish has joined #openstack-fwaas04:20
*** faizy has joined #openstack-fwaas04:35
*** reedip_ has joined #openstack-fwaas04:40
*** amotoki has joined #openstack-fwaas04:46
*** amotoki_ has joined #openstack-fwaas04:47
*** amotoki has quit IRC04:51
*** mickeys has quit IRC05:03
*** reedip_ has quit IRC05:06
*** padkrish has quit IRC05:35
*** lnicolas has quit IRC05:47
*** amotoki has joined #openstack-fwaas05:51
*** amotoki has quit IRC05:52
*** amotoki has joined #openstack-fwaas05:52
*** amotoki_ has quit IRC05:54
*** amotoki_ has joined #openstack-fwaas05:56
*** amotoki has quit IRC06:00
*** padkrish has joined #openstack-fwaas06:17
*** zoukeke has joined #openstack-fwaas06:19
*** carl_baldwin_ has joined #openstack-fwaas06:29
*** carl_baldwin has quit IRC06:33
*** carl_baldwin_ is now known as carl_baldwin06:33
*** hoangcx_ has joined #openstack-fwaas06:55
*** mickeys has joined #openstack-fwaas06:55
*** hoangcx has quit IRC06:57
*** mickeys has quit IRC07:00
*** amotoki_ has quit IRC07:05
*** amotoki has joined #openstack-fwaas07:05
*** mickeys has joined #openstack-fwaas07:10
*** yamamoto has quit IRC07:17
*** padkrish has quit IRC07:31
*** yamamoto has joined #openstack-fwaas07:53
*** yamamoto_ has joined #openstack-fwaas07:54
*** yamamoto has quit IRC07:57
*** yushiro has quit IRC08:01
*** hoangcx_ has quit IRC08:02
*** hoangcx has joined #openstack-fwaas08:02
*** yamamoto_ has quit IRC08:09
*** faizy has quit IRC08:11
*** faizy has joined #openstack-fwaas08:12
*** amotoki has quit IRC09:11
*** mickeys has quit IRC09:55
*** yushiro has joined #openstack-fwaas09:58
*** zoukeke has quit IRC10:06
*** hoangcx has quit IRC10:07
*** faizy has quit IRC10:13
*** faizy has joined #openstack-fwaas10:14
*** Trident has quit IRC10:29
*** Trident has joined #openstack-fwaas10:30
*** yamamoto has joined #openstack-fwaas10:35
*** yamamoto has quit IRC11:36
*** yamamoto has joined #openstack-fwaas11:39
*** faizy has quit IRC11:59
*** yamamoto has quit IRC12:39
*** faizy has joined #openstack-fwaas13:13
*** reedip_ has joined #openstack-fwaas13:19
*** yushiro has quit IRC14:13
xgermanI think shared and public are meant to do the same thing but as reedip said grammatically shared is nicer.14:22
*** padkrish has joined #openstack-fwaas14:24
*** reedip_ has quit IRC14:30
njohnstonI agree.  I don't really know why it was ever important to rename shared to public in the first place.15:09
*** reedip_ has joined #openstack-fwaas15:14
*** mickeys has joined #openstack-fwaas15:36
*** mickeys has quit IRC15:42
doudeHi there! I'm looking to develop a FWaaSv2 drver for Contrail SDN controller and I've few questions15:51
doudeCan I go there?15:51
reedip_OpenContrail ???15:57
reedip_nice doude ....15:57
reedip_:)15:57
njohnstonsure, doude15:57
reedip_doude : the best way would be posting your questions on openstack-dev mailing list, and this IRC15:58
doudeyes OpenContrail, reedip_16:03
doudeOk I'll also open a mail dev thread16:03
doudeI read the FWaaS v2 spec https://specs.openstack.org/openstack/neutron-specs/specs/newton/fwaas-api-2.0.html16:04
doudeand I don't understand how fw and sg will live together on a VM port?16:05
doudefrom what I understood as it's  2 different APIs, rules are not reflect on each API, true?16:07
reedip_doude : not sure about the last statement but as per the documentation written for FwaaS v216:09
reedip_"When both FWaaS and Security Groups are associated with the same Neutron port, a packet must be allowed by both features, i.e. “deny” wins between FWaaS and Security Groups. This behavior is adopted to address typical use cases where a tenant network admin uses FWaaS to specify tenant wide rules that are to be applied regardless of the application, while an application deployer uses Security Groups to narrow down allowed traffic to only what is16:09
doudeyes16:10
doudebut rules I create on the FW API are not reflected on the SG API?16:11
reedip_no , the rules would be different16:11
doudeok16:11
doudeand the SG API limit port association to VM port? Router and other system port cannot be associated to a SG?16:13
reedip_IIUC , yes SG are limited to VMs. njohnston, xgerman : let me know if I am wrong16:17
xgerman+116:18
reedip_+1 for me being wrong ?? :P16:18
xgermanno, it’s limited to VM ports16:18
njohnstonI concur, SG are limited to VM ports16:19
reedip_:)16:19
reedip_FW on the other hand can be extended to the other type of ports doude16:19
xgermanat least router16:20
xgermanother ports are a bit YMMV16:20
doudeok thanks16:20
xgermanyeah, router and VM are supported; other ports (e.g. SFC) are a bit YMMV16:21
reedip_Need to see google whats YMMV16:21
xgermanYour mileage may vary16:21
doudeI made a test on a devstack with ML2 and the error is not explicit: "'Port' object has no attribute 'security_groups'"16:21
reedip_yes, thats what google told me about YMMV :P16:22
reedip_doude : thats an interesting issue, did you check the traceback in /opt/stack/logs/q-svc.log?16:22
reedip_and BTW did you have Reclone=True /Reclone=False in local.conf of devstack?16:23
doudeit's a fresh devstack install from master branch16:24
doudeI don't have any traceback in any Neutron service16:24
doudebut I have that traceback from osc in debug:16:24
doudehttp://paste.openstack.org/show/598262/16:25
doudeI think OSC try to read the 'security_groups' attribute before trying to update it16:26
doudeI try to set the curl command16:27
doude*I'm trying16:27
reedip_doude : neutron error logs would be there in /opt/stack/logs/q-svc.log but yes, this seems like a different issue. Do you have a locally checked out python-openstackclient folder in /opt/stack ?16:27
reedip_and do you have the latest code of python-openstacksdk ?16:28
doudeyes16:28
doudeand I don't have python-openstacksdk16:29
reedip_okay, can you just check if python-openstacksdk and python-openstackclient are both pointing to master branch ( using git branch in those folders )16:29
doudebut openstacksdk==0.9.1316:29
doudeand python-openstackclient==3.8.116:29
reedip_doude : okay, you may not have it, but it would nevertheless be checked out in /usr/local/python2.7/site-packages16:29
reedip_doude : okay, give me some time, need to check it16:30
doudesure16:33
reedip_doude : okay, my env also has 0.9.13 for openstacksdk and 3.8.1 wth openstackclient16:36
reedip_I am just redeploying the devstack , because it has been in a statis state since yesterday, so need some time. If I see the same error, then it might be something new16:37
doudereedip_: I think is an issue on the osc 'port set' command16:40
reedip_doude: I think so too, so just checking.16:41
doudeI finally manage to send the update security group on a router port with a curl command and the neutron APi return me an explicit bad request error16:42
doude"BadRequest: Port security must be enabled and port must have an IP address in order to use security groups."16:42
reedip_it should, on the router port16:42
doudeyes16:42
reedip_but the port which failed in your devstack shouldnt be a router port16:44
doudereedip_: I tried to do add sg on a router port intentionnally to confirm it is forbidden16:47
reedip_doude : thats gr8 :) but right now I am more concerned about the devstack issue, if it exists :D16:49
*** vishwanathj has joined #openstack-fwaas16:50
*** vishwanathj has quit IRC16:57
*** padkrish has quit IRC16:59
doudeok17:00
reedip_doude : the above issue came with port update ( the error reported by devstack )17:04
doudeok17:08
doudeI come back to the FWaaS v2 API spec. The spec https://specs.openstack.org/openstack/neutron-specs/specs/newton/fwaas-api-2.0.html talk about 'address group' and 'service group' but I don't see it implemented in the actual code. Is it abandonned or postponed?17:10
reedip_doude : I was able to replicate the issue. The port bieng updated by devstack seems to be a router port, and it wont have the security group.17:14
reedip_So this issue is logically correct17:14
doudeok right17:15
reedip_doude : I think the address_group is not yet there17:17
doudeand the service_group?17:20
reedip_not sure abt that doude17:21
doudeok, thanks17:21
doudeI also saw it is possible to define a firewall group as a source or destination in a firewall rule. Is it still plan to do that?17:23
reedip_doude: shouldnt we  ? :)17:34
doude:)17:35
doudeIMO yes17:35
doudebut that have a huge impact technically17:36
reedip_doude : your point being ( in terms of technical impact )  ? )( though njohnston, sridark , xgerman and others would be better in answering this )17:38
reedip_this -> this than me17:39
*** mickeys has joined #openstack-fwaas17:41
doudeyes in my point of view of contrail developer17:41
*** reedip_1 has joined #openstack-fwaas17:44
*** reedip_2 has joined #openstack-fwaas17:45
reedip_2sorry, disconnected :P17:45
*** reedip_ has quit IRC17:46
*** reedip_1 has quit IRC17:48
*** SumitNaiksatam has joined #openstack-fwaas18:02
*** reedip_2 has left #openstack-fwaas18:19
*** padkrish has joined #openstack-fwaas18:51
*** SumitNaiksatam has quit IRC19:05
*** SridarK has joined #openstack-fwaas19:17
*** padkrish has quit IRC19:38
*** faizy has quit IRC19:39
*** padkrish has joined #openstack-fwaas19:56
*** padkrish has quit IRC20:00
*** padkrish has joined #openstack-fwaas20:00
*** padkrish has quit IRC20:14
-openstackstatus- NOTICE: Restarting gerrit due to performance problems20:19
*** mickeys has quit IRC21:49
*** mickeys has joined #openstack-fwaas22:03
*** padkrish has joined #openstack-fwaas22:21
*** padkrish has quit IRC22:22
*** padkrish has joined #openstack-fwaas22:22
*** yamamoto has joined #openstack-fwaas22:56
*** SridarK has quit IRC23:32
*** padkrish has quit IRC23:51

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