Agent changes to handle "log" as a possible action in ACL rules.
Agent config handling for ACL rules should handle "log" and "alert" as possible actions and store them in AclEntrySpec and AclEntry objects. These new action values will be used during flow policy handling and can be possible actions for flow.
Removed "DROP" and "REJECT" action definitions. Also when a flow was made as short flow, we were marking the action as DROP. Changed this to use "DENY"
Also added UT to verify log action configured in ACL rule gets reflected in flow Action.
Reviewed: https:/ /review. opencontrail. org/14659 github. org/Juniper/ contrail- controller/ commit/ 3ddb6b492065876 af8ed3d75ef2514 656f03ebbf
Committed: http://
Submitter: Zuul
Branch: R2.20
commit 3ddb6b492065876 af8ed3d75ef2514 656f03ebbf
Author: Ashok Singh <email address hidden>
Date: Tue Oct 27 02:54:19 2015 -0700
Agent changes to handle "log" as a possible action in ACL rules.
Agent config handling for ACL rules should handle "log" and "alert" as possible actions and store them in AclEntrySpec and AclEntry objects. These new action values will be used during flow policy handling and can be possible actions for flow.
Removed "DROP" and "REJECT" action definitions. Also when a flow was made as short flow, we were marking the action as DROP. Changed this to use "DENY"
Also added UT to verify log action configured in ACL rule gets reflected in flow Action.
Change-Id: I1cae90a14e9692 1830c0fdb2c43b2 2fbd2fc9320
Closes-Bug: #1493206