Skip to content

Commit da4038a

Browse files
committed
chg: [doc] sync with website
1 parent d6c5c1f commit da4038a

File tree

1 file changed

+17
-2
lines changed

1 file changed

+17
-2
lines changed

static/documentation/_sources/prerequisites.rst

Lines changed: 17 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,9 +26,24 @@ For the Web server you can use Gunicorn, uWSGI, Apache or Nginx.
2626
Hardware
2727
--------
2828

29+
For the core of the Vulnerability-Lookup service, we recommend the following baseline specifications for a public-facing deployment (running Kvrocks and PostgreSQL):
30+
31+
- 16 CPU cores
32+
- 64 GB RAM
33+
- 2 TB NVMe storage
34+
35+
The new VLAI capabilities are straightforward to set up, as we intentionally avoided adding complexity to the core Vulnerability-Lookup software or its dependencies. Instead, we developed a separate component called `ML-Gateway <https://github.com/vulnerability-lookup/ML-Gateway>`_, which is queried by the core service.
36+
37+
The requirements for ML-Gateway are currently minimal. For VLAI Severity, no GPU or specialized hardware is needed, as it uses `a lightweight NLP model <https://huggingface.co/CIRCL/vulnerability-severity-classification-roberta-base>`_ that is loaded at runtime. ML-Gateway requires:
38+
39+
- 4 GB of memory
40+
- 200 GB of disk space
41+
- At least 4 vCPU cores
42+
43+
These requirements may increase depending on the VLAI features added in the future.
2944

3045
Network
3146
-------
3247

33-
The deployment on the different servers requires an Internet connection since
34-
the updates are retrieved from the GitHub repository.
48+
Deployment on the different servers requires an Internet connection, as updates are retrieved from the GitHub repository. The feeders also need Internet access to various locations, including Git repositories, HTTP endpoints, and specific APIs.
49+

0 commit comments

Comments
 (0)