Merge branch 'release-1.129.0'

CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## v1.129.0 (09/03/2023)
+
+### Features:
+-  [#5031](https://github.com/telstra/open-kilda/pull/5031) v2 API: add get switch flows per ports
+
+### Bug Fixes:
+-  [#5090](https://github.com/telstra/open-kilda/pull/5090) Bugfix/2660 empty rule none drop fix (Issue: [#2660](https://github.com/telstra/open-kilda/issues/2660))
+-  [#5092](https://github.com/telstra/open-kilda/pull/5092) Really ignore generated kafka-conf/server.properties file (Issues: [#5006](https://github.com/telstra/open-kilda/issues/5006) [#5068](https://github.com/telstra/open-kilda/issues/5068)) [**configuration**]
+-  [#5071](https://github.com/telstra/open-kilda/pull/5071) Added vlan in range check for flow statistics (Issue: [#5067](https://github.com/telstra/open-kilda/issues/5067))
+-  [#5043](https://github.com/telstra/open-kilda/pull/5043) 4991 Updated Grpc Exception Handler (Issue: [#4991](https://github.com/telstra/open-kilda/issues/4991))
+-  [#5076](https://github.com/telstra/open-kilda/pull/5076) adding functional tests to check negatives cases for flow_update [**tests**]
+-  [#5113](https://github.com/telstra/open-kilda/pull/5113) restructuring and extending tests for maxLatency (tier2) update on patch endpoint [**tests**]
+-  [#5055](https://github.com/telstra/open-kilda/pull/5055) Fix validation for maxLatency and maxLatencyTier on Flow update.
+
+### Improvements:
+-  [#5052](https://github.com/telstra/open-kilda/pull/5052) Fix/docs [**docs**]
+
+For the complete list of changes, check out [the commit log](https://github.com/telstra/open-kilda/compare/v1.128.0...v1.129.0).
+
+### Affected Components:
+flow-hs
+
+---
+
 ## v1.128.0 (27/02/2023)
 
 ### Features:

docker/.gitignore

@@ -6,4 +6,4 @@ lab-service/log.json
 lock-keeper/README.md
 lock-keeper/*.py
 grpc-stub/*.py
-docker/kafka/kafka-conf/server.properties
+kafka/kafka-conf/server.properties

docs/design/LAG-for-ports/README.md

@@ -132,22 +132,21 @@ Response example:
 ~~~
 
 ## Details
-All logical port related commands are sent to the switches using gRPC speaker.
+All logical port-related commands are sent to the switches using the gRPC speaker.
 
-Kilda configuration defines logical port numbers range and amount of chunks in this range. During LAG create operation
-random chunk number will be selected and first unassigned number from this chunk will be used as logical port number.
-Port number allocation done on per switch basis, so different switches can have LAG logical ports with same numbers. 
+Kilda configuration defines a range of logical port numbers and the number of chunks in this range. During a LAG create operation,
+a random chunk number will be selected and the first unassigned number from this chunk will be used as the logical port number.
+Port number allocation is done on per-switch basis. This way, different switches can have LAG logical ports with same numbers. 
 
-It is not allowed to have one physical port in two LAGs so this rule will provide unique logical port number for any 
-correct port configuration. LAG logical port configuration should be validated before any create operation to avoid 
-inconsistency. 
+It is not allowed to have one physical port in two LAGs, so this rule will provide a unique logical port number for any 
+correct port configuration. In order to avoid inconsistency, LAG logical port configuration should be validated before any create operation.
 
-Currently, open-kilda doesn't have any port related information representation in database. We need to save LAG logical port configuration into database to have ability to restore configuration on the switch. Information about LAGs stored as a separate models in order to provide minimal impact on already existing data structures.
+Currently, OpenKilda doesn't have any port-related information representation in the database. We need to save LAG logical port configuration into the database to have the ability to restore a configuration on the switch. In order to provide minimal impact on existing data structures, the information about LAGs is stored as a separate model.
 
 ![domain-model](./domain-model.png)
 
-Open-kilda uses a switch-port pair to represent a flow endpoint. LAG ports created in this way may be used as a flow endpoint on one or both flow sides to provide flow resiliency.
+Open-kilda uses a switch-port pair to represent a flow endpoint. LAG ports created in this way may be used as a flow endpoint on one or on both flow sides to provide flow resiliency.
 
 ## Additional changes
 
-During switch/flow validate and sync LAG ports configuration should be checked and installed if required. 
+During switch/flow validation and sync, LAG ports configuration should be verified and installed if required.