| 2013-11-26 14:17:11 |
Aleksandr Chirko |
description |
During my OVS-related prototyping I spotted this. For bug verification I used 'ovs_lib' as a standalone python package (without Openstack runnig).
I can define flow with no problems:
from neutron.agent.linux import ovs_lib
int_br = ovs_lib.OVSBridge('br-int', root_helper='sudo')
int_br.add_flow(priority=777,dl_type=2048, actions='normal')
Run 'ovs-ofctl dump-flows br-int'
'cookie=0x0, duration=115.956s, table=0, n_packets=0, n_bytes=0, priority=777,ip actions=NORMAL'
However when I try to modify this flow:
int_br.mod_flow(dl_type=2048, actions='drop')
I see
'Command: ['sudo', 'ovs-ofctl', 'mod-flows', 'br-int', 'hard_timeout=0,idle_timeout=0,priority=0,dl_type=2048,actions=drop']
Exit code: 1
Stdout: ''
Stderr: 'ovs-ofctl: unknown keyword hard_timeout\n' |
During my OVS-related prototyping I spotted this. For bug verification I used 'ovs_lib' as a standalone python package (without Openstack runnig).
OVS info:
ovs-ofctl (Open vSwitch) 1.4.0+build0
Compiled Feb 18 2013 13:13:22
OpenFlow versions 0x1:0x1
I can define flow with no problems:
from neutron.agent.linux import ovs_lib
int_br = ovs_lib.OVSBridge('br-int', root_helper='sudo')
int_br.add_flow(priority=777,dl_type=2048, actions='normal')
Run 'ovs-ofctl dump-flows br-int'
'cookie=0x0, duration=115.956s, table=0, n_packets=0, n_bytes=0, priority=777,ip actions=NORMAL'
However when I try to modify this flow:
int_br.mod_flow(dl_type=2048, actions='drop')
I see
'Command: ['sudo', 'ovs-ofctl', 'mod-flows', 'br-int', 'hard_timeout=0,idle_timeout=0,priority=0,dl_type=2048,actions=drop']
Exit code: 1
Stdout: ''
Stderr: 'ovs-ofctl: unknown keyword hard_timeout\n' |
|
