IntenseWebs/LibreQoS
3
0 Fork 0
mirror of https://github.com/LibreQoE/LibreQoS.git synced 2026-10-25 14:20:05 -05:00
Code Issues Packages Projects Releases Wiki Activity

changes

Browse Source
This commit is contained in:
rchac committed 2026-04-13 21:39:31 +00:00
1 parent 06a268f663
commit 9b6addfdaa
8 files changed
+776 -24
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/v2.0/integrations-reference.md
+3 -1
View File
@@ -182,7 +182,9 @@ timeout_secs = 20
```
Notes:
- VISP import is GraphQL-based and currently defaults to a flat topology strategy.
- VISP import is GraphQL-based.
- The importer prefers fast bulk service pulls and selectively backfills uncovered subscriber/service data from other VISP GraphQL queries.
- When VISP IRM upstream-device relationships are populated, the importer also builds site/upstream topology for imported subscribers.
- The integration writes `ShapedDevices.csv` every run.
- `network.json` remains a DIY/manual ingress file; built-in integrations do not overwrite it.
- VISP auth tokens are cached in `<lqos_directory>/.visp_token_cache_*.json`.
docs/v2.0/integrations-visp.md
+4 -3
View File
@@ -17,9 +17,10 @@ timeout_secs = 20
```
Notes:
- VISP import is GraphQL-based and currently defaults to a flat topology strategy.
- The integration refreshes its shaping data every run.
- `network.json` is for DIY/manual deployments; built-in integrations do not write it.
- VISP import is GraphQL-based.
- The importer prefers fast bulk service pulls and automatically backfills missing subscriber/service data from other VISP GraphQL queries when needed.
- When VISP IRM upstream-device data is populated, the importer also builds site/upstream topology for imported subscribers instead of staying flat-only.
- `network.json` is for DIY/manual deployments; built-in integrations do not overwrite it.
- VISP auth tokens are cached in `<lqos_directory>/.visp_token_cache_*.json`.
Run a manual import with:
docs/v2.0/integrations.md
+1 -1
View File
@@ -80,7 +80,7 @@ Current behavior:
| Splynx | Yes | Network sites and AP/site topology nodes export generic `id`. |
| Sonar | Yes | Site and AP topology nodes export generic `id`. |
| Netzur | Partial | Exported only when the upstream zone data includes a stable zone ID. |
| VISP | No | Current importer shapes services/devices but does not build topology nodes in `network.json`. |
| VISP | Partial | Imports site/upstream topology and stable generic IDs when VISP IRM relationships are populated; subscribers without usable upstream mapping still fall back to flat attachment. |
| Powercode | No | Current importer does not build topology nodes in `network.json`. |
| WISPGate | No | Current importer does not build topology nodes from stable upstream topology identifiers. |