You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the problem/challenge you have
Currently the OpenFlow tabels are shown with IDs, which requires the user and dev has the knowledge of the mapping between table and int number. The output of OpenFlow dump is not Intuitive.
For example, current flows show like
Describe the solution you'd like
Using the OpenFlow MultipartRequest/MultipartReply message with type OFP_Table_Features type to to modify OF table names, we can get an output showing readable table names.
The modification is performed after OVS is connected to Antrea Agent. Since OVS forbids to skip any table in the OFP_Table_Features messages and we don't want to change the exisiting table features on the OpenFlow entry limitationa and instructions, we should query the existing configurations on all OVS tables using an empty OFP_Table_Features request first, and then leverage the reply messages and only modify the table names which Antrea is using.
Anything else you would like to add?
This feature should doesn't the Antrea existing behaviors on the OVS pipeline. It only impacts the output of the flow entries
The text was updated successfully, but these errors were encountered:
Describe the problem/challenge you have
Currently the OpenFlow tabels are shown with IDs, which requires the user and dev has the knowledge of the mapping between table and int number. The output of OpenFlow dump is not Intuitive.
For example, current flows show like
Describe the solution you'd like
Using the OpenFlow MultipartRequest/MultipartReply message with type OFP_Table_Features type to to modify OF table names, we can get an output showing readable table names.
The modification is performed after OVS is connected to Antrea Agent. Since OVS forbids to skip any table in the OFP_Table_Features messages and we don't want to change the exisiting table features on the OpenFlow entry limitationa and instructions, we should query the existing configurations on all OVS tables using an empty OFP_Table_Features request first, and then leverage the reply messages and only modify the table names which Antrea is using.
We expect the OpenFlow entries look like,
Anything else you would like to add?
This feature should doesn't the Antrea existing behaviors on the OVS pipeline. It only impacts the output of the flow entries
The text was updated successfully, but these errors were encountered: