Hi All,
I am looking for all your inputs for the below issue.
Issue: Create multiple flows with different flowId, keeping rest of the
attributes same.
In this case, there will be multiple flow entries in config DS, but a single
flow on the switch.
When we delete one of this overlapping fl
smime.p7m
Description: S/MIME encrypted message
___
openflowplugin-dev mailing list
openflowplugin-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
From: Jozef Bacigál [mailto:jozef.baci...@pantheon.tech]
Sent: Friday, October 7, 2016 3:58 PM
To: Somashekar B ;
netvirt-...@lists.opendaylight.org;
openflowplugin-dev@lists.opendaylight.org
Subject: RE: [openflowplugin-dev] Need inputs on handling deletion of flows
which have common attributes
such a use case.
Thanks,
daya
From: netvirt-dev-boun...@lists.opendaylight.org
<mailto:netvirt-dev-boun...@lists.opendaylight.org>
[mailto:netvirt-dev-boun...@lists.opendaylight.org] On Behalf Of Somashekar
B
Sent: Thursday, October 13, 2016 12:49 PM
To: jozef.baci...@pantheon.te
Openstack does not provide any sequencing between SGs but that’s a
problem for the operator to solve I think,the code should only ensure default
SG has the lowest priority, and we could apply SGs in reduced priority order as
and when they are applied, ie first group gets highest prio, and
Hi,
I am trying RPC opendaylight-direct-statistics:get-flow-statistics to get
statistics for below flows
cookie=0x690, duration=10169.451s, table=41, n_packets=4, n_bytes=300,
priority=62020,ct_state=+inv+trk actions=drop
cookie=0x690, duration=10169.456s, table=41, n_packets=0, n_
