Tags: antrea-io/ofnet
Tags
Change default max_len to 65535 for controller action (#69) Instead of 128. 65535 means that there is no buffering and that the full packet is sent to the controller. This is actually the only value supported by OVS, even though OVS will not reject other values. This can create confusion as the flows will show `max_len=128`, but the controller will always receive the full packet. Another value for max_len can be explicitly provided using the new `MaxLen` field in the `NXController` struct, but there should be no reason to do so when using OVS. See openvswitch/ovs-issues#295 Signed-off-by: Antonin Bas <abas@vmware.com>
Add support set selection_method for group modification (#66) Add support to set Propertiese in a GroupMod message. The "Properties" field is set in the message only when the GroupMod message type is add or modify, and it must be empty in other types. The selection_method configurations are maintained as a Property in GroupMod message. Signed-off-by: wenyingd <wenyingd@vmware.com>
Remove flowMonitor key after the MultipartReply is received (#64) After "monitorEnabled" is enabled, an OpenFlow FlowDesc message is sent to dump the flow stats if a user calls OFSwitch.DumpFlowStats or Flow.MonitorRealizeStatus. At this time the message's transactionsID is added into a concurrent map monitoredFlows. The issue is the transactionID is not removed after the reply of FlowDesc message is received. This change is to fix the issue. Signed-off-by: wenyingd <wenyingd@vmware.com>
Add functions to remove unused map in Switch (#59) Add functions to create Table/Group/Meter object on the Switch but not store in the db (tableDb/groupDb/meterDb). This is because the application may maintain its own cache for the Table/Group/Meter resources, and a storage in ofnet is duplicated. Add APIs in AppInterface to control if or not to initialize the flow graph and the tlv map on the Switch. Signed-off-by: wenyingd <wenyingd@vmware.com>
PreviousNext