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/14719 github. org/Juniper/ contrail- controller/ commit/ c9fb0454d612b7d b2a1bc6c75f92ec 6c80d76ce2
Committed: http://
Submitter: Zuul
Branch: master
commit c9fb0454d612b7d b2a1bc6c75f92ec 6c80d76ce2
Author: Ashok Singh <email address hidden>
Date: Thu Oct 29 20:56:55 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: I8b95f324e9dbc2 e6b33c5b1a228b0 7496f908cf3
Closes-Bug: #1493206