updates for v2.2.3

TimEvens · TimEvens · commit 403fd04059cb · 2022-10-20T07:14:50.000-07:00
diff --git a/api/kafka_message_schema.md b/api/kafka_message_schema.md
@@ -6,6 +6,14 @@ title: Kafka Message Schema
 
 > **Current Version 1.7**
 
+## Minor Changes that doesn't result in schema changes
+**SEP-2022:**
+* Updated peer hash to include additional byte in the hash to indicate peering type
+  The peering type is specific to OpenBMP collector. Currently, if the peer type is
+  not local-RIB, then the peering type is unchanged.  If the peering type is for
+  Local-RIB (RFC9069), then an addtional byte of value 0x80 will be added to the hash
+  after router_hash_id. This is at the end of the hashing fields. 
+* 
 
 ## Version Changes
 
diff --git a/release_notes/2.2.x.md b/release_notes/2.2.x.md
@@ -1,5 +1,5 @@
 ---
-title: v2.2.1 (latest)
+title: v2.2.x (latest)
 ---
 
 ```note
@@ -8,7 +8,58 @@ Bug fixes are applied to the containers that changed. For example, psql-app
 may be 2.2.1 while postgres is 2.2.0.
 ``` 
 
-# v2.2.1 Fixes:
+# Release Notes
+
+## grafana:
+
+* Upgraded to 9.1.7
+* Updated prefix history dashboards to include down peers. This allows browsing prefix history
+  via peers that are down
+
+
+## collector: v2.2.3
+
+* Fixed issue with NLRI hash not including rib type (Adj-RIB-In/Out, policy Pre/Post).
+  Not including the type in the hash resulted in NLRIs from a peer being updated/overwritten
+  instead of being added as new for the type. Backwards compatibility is maintained by
+  not changing the hash if Adj-Rib-In and Pre-Policy.  If the type is anything other than
+  that, the hash will reflect the difference. This will allow both pre/policy policies to
+  be in the DB as well as Adj-RIB-Out pre/post. 
+
+* Fixed issue with peer hash not including peer type defined in RFC9069 (Loc-RIB) type difference
+ 
+* Librdkafka upgraded to v1.9.2
+  
+## collector: v2.2.2
+
+* Removed deb and rpm packages in favor of using docker. These were out of date for a while
+* Updated openbmpd.conf default kafka settings to better handle higher
+  latency connections
+* Add pacing when ingress buffer starts to fill up
+
+## psql-app: v2.2.2
+
+* Records would sometimes get out of sync on Peer UP due the way records were deleted 
+  from ```ip_rib``` table. A peer UP will not result in a lock to ensure
+  clean start after Peer UP
+
+* Improved performance of inserts and speed of auto vacuum by changing ```base_attribute``` 
+  table to no longer get timestamp updated on records that are duplicate. Timestamp in
+  the base_attribute table did not add much value as it would be changed
+  per NLRI timestamp
+
+* Fixed issue where connections to Postgres were not being closed due to errors. This 
+  would cause postgres to report max connections reached
+
+* Fixes #7; Link-State ```unreserved_bw``` is now 128 characters and fixed insert to use ```bigint```
+  type for ```admin_group```
+
+
+## collector: v2.2.1
+
+* Tuned Kafka queue to prevent disconnects with Kafka during full queue times
+
+## psql-app: v2.2.1
 
 * Fixed issue with global IP rib not updating new/first seen prefixes.
   This caused an issue for new peer RIB dumps and when there are new
@@ -19,8 +70,11 @@ may be 2.2.1 while postgres is 2.2.0.
 > **Containers Updated**
 > * psql-app - Container will upgrade schema from 2.2.0
  
+## postgres: v2.2.1
+
+* Upgrade version to ```timescaledb-ha:pg14-ts2.8```
 
-# v2.2.0 Changes:
+## All: v2.2.0
 
 * Major performance increase for IP rib inserts/updates.
   A major factor in disk IOPS is related to 
