Support for Next Hop Meta Data#2181
Conversation
|
please resolve conflicts and add description |
32f39d4 to
dc8c13c
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@ashutosh-agrawal - please help review |
There was a problem hiding this comment.
Do we need to include DST in the attribute name? I understand that corresponding neighbor attribute also has DST in the attribute name but port, vlan and acl attributes don't. In my opinion, DST in the attribute name is required for FDB and ROUTE objects only.
There was a problem hiding this comment.
Thank you @ashutosh-agrawal for the review. Name updated to "SAI_ACL_TABLE_ATTR_FIELD_NEXT_HOP_USER_META"
ashutosh-agrawal
left a comment
ashutosh-agrawal
left a comment
There was a problem hiding this comment.
Conditionally approved with the assumption that attribute name will be changed as discussed in the community meeting.
Signed-off-by: Komal Shah <kshah2@marvell.com>
dc8c13c to
fa3ed7a
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
|
@kcudnik : 1 check is failing. opencomputeproject.SAIFailing after 3m — Build #20250806.2 failed ##[error]Bash exited with code '100'. Looks like this might be an infrastructure issue (missing or broken repository during apt-get update). Let me know if it's something I should fix on my side. |
|
/azpw run |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
Signed-off-by: Komal Shah <kshah2@marvell.com>
5 participants
Metadata can be assigned in the Next Hop Table and subsequently matched in ACL entries, providing increased flexibility for policy management.