On 2 July 2016 at 21:42, Ben Pfaff wrote:
> On Wed, Jun 29, 2016 at 01:17:08AM -0700, Gurucharan Shetty wrote:
> > Currently, the only use of stateful services in conntrack is
> > OVN ACLs. In table ACL, we commit the packet to conntrack
> > via ct_commit action.
> >
> > As we introduce more stat
On Wed, Jun 29, 2016 at 01:17:08AM -0700, Gurucharan Shetty wrote:
> Currently, the only use of stateful services in conntrack is
> OVN ACLs. In table ACL, we commit the packet to conntrack
> via ct_commit action.
>
> As we introduce more stateful services, the ACL feature will
> have to share the
On 30 June 2016 at 01:41, Zong Kai LI wrote:
> >
> > @@ -1429,9 +1432,9 @@ build_acls(struct ovn_datapath *od, struct hmap
> > *lflows)
> > * and then its return traffic would not have an associated
> > * conntrack entry and would return "+invalid". */
> > ovn_lflow_a
>
> @@ -1429,9 +1432,9 @@ build_acls(struct ovn_datapath *od, struct hmap
> *lflows)
> * and then its return traffic would not have an associated
> * conntrack entry and would return "+invalid". */
> ovn_lflow_add(lflows, od, S_SWITCH_IN_ACL, 1, "ip",
> -
Currently, the only use of stateful services in conntrack is
OVN ACLs. In table ACL, we commit the packet to conntrack
via ct_commit action.
As we introduce more stateful services, the ACL feature will
have to share the conntrack module with others. As
preparation for more stateful features like l
