A previous release had provenance metadata, but this release does not. View details.
SDXClient
A thin Python client that wraps the SDX HTTP routes, stages L2VPN payload metadata, guides endpoint selection, and keeps responses consistent.
- Returns dict everywhere: {"status_code": int, "data": Any, "error": Optional[str]}
- No user-facing tracebacks; friendly errors only.
Key Points
- Uses FABRIC authentication (token loaded via fablib; no token argument needed).
- Provides a guided flow: set first endpoint → set second endpoint → preview → create.
- One unified method:
set_endpoint(endpoint_position="first", ...)set_endpoint(endpoint_position="second", ...)
- VLAN choice is derived from
/device_info; supports preferring untagged. - Consistent return shape across all methods:
Initialization
from sdxclient import SDXClient
client = SDXClient(timeout=6.0) # tries FABRIC token
Return Shape (always)
{
"status_code": int,
"data": Any,
"error": Optional[str]
}
- status_code == 0 → client-side validation / network failure
- status_code >= 400 → server-side error (with best-effort error message)
Requirements
- Python 3.9 – 3.12
requestsfabrictestbed-extensions(for automatic FABRIC token loading)- A valid FABRIC token (fablib locates it automatically)
Core Read APIs (pass-through)
client.get_topology()
client.get_available_ports(search=None, filter=None, limit=None, fields=None, format="html|json")
client.get_all_vlans_available()
client.get_port_vlans_available(port_id)
Notes:
- filter wins over search.
- format="html" returns HTML table (string). format="json" returns structured JSON.
Selection Flow (endpoints)
client.begin_l2vpn_selection()
client.set_endpoint(
endpoint_position="first" | "second",
filter=None, search=None,
port_id=None, vlan=None,
prefer_untagged=False
)
client.get_selected_endpoints()
Rules:
- Use port_id for precise selection, or filter/search to resolve a single row.
- If multiple candidates match, you get an ambiguity error with a short candidate list.
- VLAN availability is checked inline against /available_vlans.
L2VPN Payload: Stage → Preview → Create
1) Stage payload metadata once
client.set_l2vpn_payload(
name="project-alpha-l2vpn",
notifications=["ops@example.org", "noc@example.org"]
)
- Validates name (non-empty, ≤ 50 chars).
- Validates notifications (1–10 emails; str input is normalized to a list).
2) Build payload locally (no network)
payload_result = client.get_l2vpn_payload()
# -> {"name": "...", "notifications": [...], "endpoints": [{...}, {...}]}
- Requires both endpoints to be selected and metadata to be staged.
- Re-validates endpoint shape and rejects same-VLAN per policy (see “VLAN Rules”).
- No availability calls here.
3) Preview payload with availability checks
preview_result = client.preview_l2vpn_payload()
# Re-checks VLAN availability via /available_vlans for both endpoints.
4) Create L2VPN (uses previewed payload)
create_result = client.create_l2vpn_from_selection()
- Uses the staged name/notifications + selected endpoints.
- Performs preview internally first (includes availability checks).
- No need to pass name/notifications again here.
CRUD Mirrors
- client.get_l2vpns(**query)
- client.get_l2vpn(service_id)
- client.update_l2vpn(service_id, **fields)
- client.delete_l2vpn(service_id)
Minimal End-to-End Example
from sdxclient import SDXClient
client = SDXClient()
1) Start fresh
client.begin_l2vpn_selection()
2) Choose endpoints
client.set_endpoint(endpoint_position="first", filter="SW17:7")
client.set_endpoint(endpoint_position="second", filter="SW17:27", prefer_untagged=True)
3) Stage metadata once
client.set_l2vpn_payload(
name="proj-alpha-mia-test",
notifications="noc@example.org"
)
4) Optional: local payload (no network)
local_payload = client.get_l2vpn_payload()
5) Preview with availability checks
preview = client.preview_l2vpn_payload()
6) Create
created = client.create_l2vpn_from_selection()
Error Examples (friendly)
client.get_port_vlans_available(None)
# {'status_code': 0, 'data': None, 'error': 'missing required parameter(s): port_id'}
client.set_endpoint(endpoint_position="first", filter="too-broad")
# {'status_code': 0, 'data': {'candidates': [...]}, 'error': 'ambiguous filter/search matched ...'}
client.get_l2vpn_payload() # without staging metadata
# {'status_code': 0, 'data': None, 'error': 'missing L2VPN name (set via set_l2vpn_payload)'}
VLAN Validation Rules for L2VPN
Allowed forms
- Numeric VLANs: 1..4095
- Ranges: A:B where 1 ≤ A < B ≤ 4095
- Keywords: any, untagged
- (all is not allowed)
Mixing rules
- Numeric ↔ Range (e.g., 200 with 100:300)
- any ↔ untagged
- any/untagged mixed with numeric/range
Rejection rules
- all mixed with anything (since all is not allowed at all)
- Same numeric VLAN twice (e.g., 200 & 200)
- Same exact range twice (e.g., 100:200 & 100:200)
Tips
-
Prefer format="json" for machine workflows; parse ports from /available_ports.
-
If you pass both filter and search, filter is used.
-
“No usable VLAN found” often means the port advertises none or they’re all in use.
-
If you want to skip availability checks, use get_l2vpn_payload() and post it yourself; otherwise use create_l2vpn_from_selection() to keep checks on.
Troubleshooting
- 401 / missing token → set a valid token or ensure FABRIC token is discoverable.
- Empty listings → loosen your filter/search; inspect /topology.
- Availability errors → verify get_port_vlans_available(port_id) shows a range that contains your requested VLAN token.
Changelog (relevant)
- Added set_l2vpn_payload(name, notifications): stage metadata once.
- Added get_l2vpn_payload(): build local payload without network.
- create_l2vpn_from_selection() no longer requires passing name/notifications; it uses staged metadata and runs a preview internally.
Metadata
Release files for sdxclient 1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Loss of provenance
These files do not have provenance metadata, despite files in a prior release including this data.
We recommend further investigation before installing these files. View details.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| sdxclient-1.2.tar.gz | 17.2 kB | Without provenance | Details for sdxclient-1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sdxclient-1.2-py3-none-any.whl | Python 3 | none | any | Details for sdxclient-1.2-py3-none-any.whl |
Total release size: 34.1 kB
Release files / sdxclient-1.2.tar.gz
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | sdxclient-1.2.tar.gz |
|---|---|
| Size | 17.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
654c016bf8fff17b640428edccd88981fec4cf7ed92d527ef7ce59d4fef40154
|
|
BLAKE2b-256 checksum How to use checksums |
bf28436df48c3d0db9a52d5acbc5d52c695ad4381c858b8a048483e7e2041808
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Release files / sdxclient-1.2-py3-none-any.whl
Loss of provenance
This file belongs to a release without provenance metadata, despite a prior release including this data.
We recommend further investigation before installing this file. View details.
| Download URL | sdxclient-1.2-py3-none-any.whl |
|---|---|
| Size | 16.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
439d94ae3ba1a4fca715df27bdaa94a80496ade8ae10a46ebc865b913e87cc1b
|
|
BLAKE2b-256 checksum How to use checksums |
22f73b1feae394f75bcb81caecd2a9cc156526af19618fd31a499b266b57ba8d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.6
|
Security for sdxclient 1.2
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.
Loss of provenance
A previous release of these files had provenance metadata, but this release does not.
While this could reflect a routine change by the project maintainers, it may also indicate that the release files have been compromised.
Release comparison
- Removed 0.11.0 2 files With provenance
- Added 1.2 2 files Without provenance
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.