open-vllm-sdk
A high-performance, asynchronous resilience gateway client built to connect distributed application services to remote GPU infrastructure safely and efficiently. Will offers only asunchronous clients powerd by https
Table of Contents
- Overview
- Key Architecture Benefits
- Installation
- Environment Configuration
- Quick Start Usage
- Console Logging Aesthetics
- License
Overview
Managing raw HTTP streaming routes directly to high-throughput LLM clusters can cause major stability issues, such as socket exhaustion, memory crashes, or lost responses.
The open-vllm-sdk wraps all this complex networking inside a clean, production-hardened interface. It handles background network management, automatically cleans up messy raw Server-Sent Event (SSE) blocks, and feeds your applications crisp, ready-to-use text tokens in real-time.
Key Architecture Benefits
- Asynchronous Concurrency: Built natively on Python's
asyncioloop. It easily supports 100+ concurrent app instances (like Chatbots, BOM Parsers, and Tender Text Extractors) without stalling performance. - Keep-Alive Connection Pooling: Reuses active TCP paths over
httpx.AsyncClientinstead of spinning up new sockets for every line, cutting down Time-To-First-Token (TTFT). - Pre-flight Integrity Checking: Instantly scans system paths and environment flags before booting to prevent downstream configuration crashes.
- Localized Brand Logging: Implements highly scannable terminal tracking designed after modern web frameworks like FastAPI and Uvicorn.
Installation
This project is fully managed using the lightning-fast uv Python package manager.
# install from PyPI
uv add open-vllm-sdk
(or)
pip install open-vllm-sdk
.env configuration
#This is your GPU custom model loaded instance & port
LIVE_GPU_ENDPOINT_URL= http://213.196.166.17:61496/v1/chat/completions
api_key='place api token or random words.' # Not mandatory-exmaple, use custom api key
While you can provide a apikey and live endpoint recommend above, to add
on your .env file.
Support for streaming responses using Server Side Events(SSE)
Quick Start
# -*- coding: utf-8 -*-
import asyncio
from dotenv import load_dotenv
from vllm_resilience_sdk.clients import ProductionVLLMClient
load_dotenv()
#run engine
async def main(sample_payload):
# Instantiate the connection pooling client
client = ProductionVLLMClient()
await client.initialize_vllm_connection()
#Stream processed text tokens seamlessly
async for token in client.send_inference_request(sample_payload):
print(token, end="", flush=True)
yield token
#Safely flush socket channels on teardown
await client.close_vllm_connection()
#inference
import asyncio
async def test_caller():
sample_payload = {
"model": "Qwen/Qwen3-VL-8B-Instruct",
"messages": [{"role": "user", "content": "What is LLM?"}],
"max_token": 100
}
# Iterate over the tokens yielded by run_vllm_engine
async for token in main(sample_payload):
print(token, end="", flush=True)
print("\n\n--------------")
# Run the test
asyncio.run(test_caller())
Advance
Logging
To access the along with the logs. we used the standard lib logging module.
To Start | Example
# -*- coding: utf-8 -*-
import asyncio
from dotenv import load_dotenv
from vllm_resilience_sdk.logging_utils import setup_sdk_logging
from vllm_resilience_sdk import SystemInitializationEngine
from vllm_resilience_sdk.clients import ProductionVLLMClient
load_dotenv()
async def main(sample_payload):
#Initialize
setup_sdk_logging()
#Run background system verification checks
verifier = SystemInitializationEngine(target_log_dir="./logs")
verifier.run_pre_boot_pipeline()
#Instantiate the connection pooling client
client = ProductionVLLMClient()
await client.initialize_vllm_connection()
#Stream processed text tokens seamlessly
async for token in client.send_inference_request(sample_payload):
print(token, end="", flush=True)
yield token
#Safely flush socket channels on teardown
await client.close_vllm_connection()
#inference
import asyncio
async def test_caller():
sample_payload = {
"model": "Qwen/Qwen3-VL-8B-Instruct",
"messages": [{"role": "user", "content": "What is LLM?"}],
"max_token": 100
}
# Iterate over the tokens yielded by run_vllm_engine
async for token in main(sample_payload):
print(token, end="", flush=True)
print("\n\n--------------")
# Run the test
asyncio.run(test_caller())
[!IMPORTANT]
Error code as follow:2026-06-07 23:15:02 [WARNING] (Vllm_SDK.VLLMClient): Attempt 1/3 failed: ConnectError. Triggering backoff self-heal protocol [GPU Link Dropped]should check your GPU server is enbaled.
GPU Retried
certain gpu connection error are automatically retried 4 time by default, with a short backoff. Connection error due to network connectivity problm, Request Timeout, Network conflict, RateLimit and internal error are reteried by default as 4.
Connections
maximum alive wahup connection default by 30, max connection can made by 150 default.
you can use the parameter max_alive & max_conection options to increase or decrease by initial_vllm_connection function.
from vllm_resilience_sdk.clients import ProductionVLLMClient
client = ProductionVLLMClient()
client.initialize_vllm_connection(max_connection=0, max_alive=0)
you can verify the versoin that is being used at runtime with :
import vllm_resilience_sdk
print(vllm_resilience_sdk.__version__)
Metadata
Release files for open-vllm 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| open_vllm-1.0.2.tar.gz | 11.2 kB | With provenance | Details for open_vllm-1.0.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| open_vllm-1.0.2-py3-none-any.whl | Python 3 | none | any | Details for open_vllm-1.0.2-py3-none-any.whl |
Total release size: 24.5 kB
Release files / open_vllm-1.0.2.tar.gz
| Download URL | open_vllm-1.0.2.tar.gz |
|---|---|
| Size | 11.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d6cf1931bb70820e0ec9d10ab2118e9bc6c4dce074e7546058f230027c7c35c3
|
|
BLAKE2b-256 checksum How to use checksums |
5dea1851fdb1ef0222b483f26dd3fdc9f5bf7fde20c52d7cf5b7928ed048b5ca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 18, 2026.
Transparency logRelease files / open_vllm-1.0.2-py3-none-any.whl
| Download URL | open_vllm-1.0.2-py3-none-any.whl |
|---|---|
| Size | 13.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a35fd731efecbb774e8090a68cdbd8ab86e4b080c0ef6352ce52c9e89916e09a
|
|
BLAKE2b-256 checksum How to use checksums |
e28debc18be0b0a1bf5b5c494a85c732b6ac4af49cc8db549c6264482efe6583
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 18, 2026.
Transparency logSecurity for open-vllm 1.0.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for open_vllm-1.0.2.tar.gz
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 Jun 18, 2026.
Transparency logA 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.