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
Copy file name to clipboardExpand all lines: docs/md/architecture.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ on [this service](https://github.com/RedHatInsights/insights-rbac), however it c
16
16
`ENABLE_RBAC=no`. See [component environment variables](../../conf/manager.env)
17
17
18
18
-**listener** - connects to the Kafka service, and listens for messages about newly uploaded archives. When a new
19
-
archive is uploaded, it upserts **`system_inventory`** (including `vmaas_json` with installed packages, repos, and modules) and the matching **`system_patch`** row; it does not write to a monolithic **`system_platform`** table (that name may exist only as a **SQL VIEW** for compatibility). Upload locks and checksum logic apply to **`system_inventory`**. It registers repositories for the system by pairing `repo` with the internal system id (**`system_inventory.id`**) through **`system_repo`**. After that it sends a
19
+
archive is uploaded, it upserts **`system_inventory`** (including `vmaas_json` with installed packages, repos, and modules) and the matching **`system_patch`** row. Upload locks and checksum logic apply to **`system_inventory`**. It registers repositories for the system by pairing `repo` with the internal system id (**`system_inventory.id`**) through **`system_repo`**. After that it sends a
20
20
Kafka message (`patchman.evaluator.upload` topic) to evaluate the system with the `evaluator-upload` component. This
21
21
component also handles system deleting events (`platform.inventory.events` Kafka topic).
22
22
See [component environment variables](../../conf/listener.env)
Copy file name to clipboardExpand all lines: docs/md/database.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,6 @@
4
4
Main database tables description:
5
5
-**system_inventory** — Partitioned table for the registered host / inventory profile: internal `id`, Insights `inventory_id`, `rh_account_id`, `vmaas_json` (packages, repos, modules for VMaaS), `yum_updates` and related checksums, staleness and culling timestamps, `display_name`, OS fields, tags/workspaces, and workload flags. **`system_repo`** (and similar link tables) use this internal `id` as the system key. The **listener** upserts rows here and relies on **system_inventory** for upload locks and unchanged detection; the **evaluator** reads it via a join to **system_patch**.
6
6
-**system_patch** — Partitioned evaluation output for each system, keyed by `rh_account_id` and `system_id` where `system_id` equals **system_inventory.id** on the same account. Holds advisory and package count caches, `last_evaluation`, `third_party`, `template_id`, and related aggregates. Rows are created or updated by the **listener** together with **system_inventory**; the **evaluator** persists evaluation results here (not into a single legacy table).
7
-
-**system_platform** (compatibility) — The schema may define **`system_platform` as a SQL VIEW** over `system_inventory` joined to `system_patch` on `system_inventory.id = system_patch.system_id` (and matching `rh_account_id`). A future migration could remove the view. Go code loads the combined shape as **SystemPlatformV2** (`Inventory` + `Patch`) rather than a monolithic `SystemPlatform` ORM model.
8
7
-**advisory_metadata** - stores info about advisories (`description`, `summary`, `solution` etc.). It's synced and stored on trigger by `vmaas_sync` component. It allows to display detail information about the advisory.
9
8
-**system_advisories** - stores info about advisories evaluated for particular systems (system - advisory M-N mapping table). `system_id` references **system_inventory.id**. Contains info when system advisory was firstly reported and patched (if so). Records are created and updated by `evaluator` component. It allows to display list of advisories related to a system.
10
9
-**advisory_account_data** - stores info about all advisories detected within at least one system that belongs to a given account. So it provides overall statistics about system advisories displayed by the application.
@@ -13,6 +12,6 @@ Main database tables description:
13
12
-**system_package2** - list of packages installed on a system
14
13
15
14
## Schema
16
-
The ERD image below may lag `database_admin/schema/create_schema.sql` (for example if it still shows **`system_platform`** as a base table while the physical tables are **system_inventory** and **system_patch**).
15
+
The ERD image below may lag `database_admin/schema/create_schema.sql`; for systems it may not reflect the split between **system_inventory**(host profile / upload payload) and **system_patch** (evaluation caches and aggregates).
0 commit comments