v0.15.1

Give bundle reply timeout and cancellation their own error values (#112)

These are returned as anonymous errors today, so callers can't tell them
apart from a real rejection. But they're different: a rejection means it
failed, while a timeout or cancellation means we don't know (the switch
may have applied the request anyway). Which request got no reply also
matters: only a commit can leave the switch in an unknown state, while an
open, close or discard changed nothing.

Export ErrBundleReplyTimeout and ErrBundleReplyCanceled, plus a per-request
error for each, so callers can check both the outcome and the request type
with errors.Is. The error strings gain an " on <request>" suffix (e.g.
"bundle reply is timeout on commit"); behavior is otherwise unchanged.

Signed-off-by: Hongliang Liu <hongliang.liu@broadcom.com>

v0.15.0

Update VERSION to v0.15.0 (#98)

Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>

v0.14.0

Add support for PortStatus message. (#82)

Add function PortStatusRcvd in AppInterface to notify the applications when a
PortStatus message is received from the OpenFlow switch.

Signed-off-by: Wenying Dong <wenyingd@vmware.com>

v0.13.0

Bump Go to 1.23 (#81)

Go 1.21 is no longer maintained.

We also update all module dependencies.

Bump up module version to v0.13.0.

Signed-off-by: Antonin Bas <antonin.bas@broadcom.com>

v0.12.0

Stop deleting group entries on switch connection (#75)

There is no reason to treat groups any differently from flows, meters, etc.

Bump up version to v0.12.0.

Signed-off-by: Antonin Bas <abas@vmware.com>

v0.11.0

Bump up go and golangci version (#72)

1. Bump up go version to v1.21
2. Bump up golangci-lint version to v1.54.2

Signed-off-by: wenyingd <wenyingd@vmware.com>

v0.10.0

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 https://github.com/openvswitch/ovs-issues/issues/295

Signed-off-by: Antonin Bas <abas@vmware.com>

v0.9.0

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>

v0.8.1

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>

v0.8.0

Bump up Go dependencies to their latest versions (#61)

Also enable Dependabot for Go dependencies and Github Actions, to
automate future updates.

Bump up module version to v0.8.0.

Signed-off-by: Antonin Bas <abas@vmware.com>