Table of Contents
Overview
Module vmanage-agent allows node to make request to vmanage and add this device to USDN system.
Enhanced Security Features
The agent now implements three separate cryptographic key types for maximum security:
- Controller WireGuard Keys - Management plane (node ↔ controller)
- Tunnel WireGuard Keys - Data plane (node ↔ node via VPP)
- Blockchain RSA Keys - Configuration encryption/decryption
Security Guarantee: Private keys NEVER leave the device. Only public keys are transmitted to backend.
See SECURITY_KEY_MANAGEMENT.md for complete details.
Requirements
Make sure python and the package manager pip are installed. Salt-minion >= 3005.1 is also required.
- python >=3.10
- pip >= 3.10
- salt-minion == 3005.1
Installation
Install package with the command below:
sudo pip3 install vmanage-agent
Pre-requisites
Salt-minion is running
Checking if salt-minion is running
sudo systemctl status salt-minion
If the output return error, try to stop salt-minion and run in debug mode (salt-minion -l debug)
Usage
Run manually
sudo /usr/local/bin/vmanage-agent -m [master-address] -mf [master-fingerprint] -e [environment]
Arguments
-m, --master(required): Salt master address-mf, --master-finger(required): Salt master fingerprint to verify master-e, --env(optional): Environment - eitherproductionorstaging(default:production)
Examples
Production (default):
sudo /usr/local/bin/vmanage-agent -m salt.usdatanetworks.com -mf a1:b2:c3:d4:e5:f6
Staging:
sudo /usr/local/bin/vmanage-agent -m salt-staging.usdatanetworks.com -mf a1:b2:c3:d4:e5:f6 -e staging
Environment-Specific API Endpoints
- Production:
https://api.usdatanetworks.com - Staging:
https://staging-api.usdatanetworks.com
File Location
- Log: /var/log/minion.log
- Config: /opt/minion/config.ini
Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
Please make sure to update tests as appropriate.
License
Metadata
Release files for vmanage-agent 0.2.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| vmanage_agent-0.2.1.tar.gz | 89.3 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| vmanage_agent-0.2.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 105.8 kB
Release files / vmanage_agent-0.2.1.tar.gz
| Download URL | vmanage_agent-0.2.1.tar.gz |
|---|---|
| Size | 89.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
729789d01878a85f9333700f5fb4c4648f7ec05cd2ed656e3d4c6e1971af43ed
|
|
BLAKE2b-256 checksum How to use checksums |
2b8cd51ed29c4d68318849e3108f5a9f874d388c101f4ab27a41c52a455bea0a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 4, 2025.
Transparency logRelease files / vmanage_agent-0.2.1-py3-none-any.whl
| Download URL | vmanage_agent-0.2.1-py3-none-any.whl |
|---|---|
| Size | 16.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f70ed743bcbc99facbfae0d238a235eeb4ba3bd800006937ee61642a9881cd99
|
|
BLAKE2b-256 checksum How to use checksums |
6a45ea29a2e2f0774d2692050eaeabefc38cf5cc4d28ad7977850e7a2346e259
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Dec 4, 2025.
Transparency log