PMS Ray Cluster: Distributed Computing Infrastructure
pms-ray-cluster는 Ray Cluster 컨테이너 생성을 위한 이미지 빌드 리포지토리입니다.
과거 별도의 패키지도 존재했지만 pms의 버전이 업데이트 되면서 패키지는 더 이상 사용하지 않습니다.
🚀 Key Engineering Features
- Multi-Environment Cluster Provisioning
- On-Premise (Docker Compose):
docker-compose.head.yaml,worker.gpu.yaml,worker.npu.yaml등 노드 역할과 하드웨어 타겟에 따라 컴포즈 파일을 세분화하여, 로컬 또는 폐쇄망 환경에서도 손쉽게 스케일 아웃이 가능합니다.
- On-Premise (Docker Compose):
- Custom Hardware-Accelerated Images
- 공식 Ray 이미지의 한계를 넘어, 미디어 파이프라인과 AI 추론에 최적화된 커스텀 Dockerfile(
Dockerfile.trt,Dockerfile.onprem,Dockerfile.basic)을 제공합니다. - TensorRT 런타임, 비디오 디코딩 패키지, NPU 드라이버 등 필수 의존성이 사전 빌드되어 노드 프로비저닝 속도를 극대화합니다.
- 공식 Ray 이미지의 한계를 넘어, 미디어 파이프라인과 AI 추론에 최적화된 커스텀 Dockerfile(
📁 Architecture & Directory Structure
pms_ray_cluster_main/
├── pms_ray_cluster/ # 더 이상 사용하지 않음!
├── docker/ # 커스텀 Ray Worker 노드 이미지 빌드 명세
│ ├── Dockerfile.basic # 범용 CPU/기본 워커 이미지
│ ├── Dockerfile.trt # 고성능 추론용 TensorRT 탑재 워커 이미지
│ └── Dockerfile.onprem # 온프레미스/폐쇄망 전용 독립 워커 이미지
├── asset/ # 더 이상 사용하지 않음!
├── prometheus/ # 더 이상 사용하지 않음!
└── docker-compose.*.yaml # 온프레미스 및 로컬 개발용 컴포즈 파일 모음 (Head, CPU, GPU, NPU)
🛠 Tech Stack
- Distributed Computing: Ray
- Infrastructure & Orchestration: Docker, Docker Compose
- Hardware Targets: NVIDIA GPU (TensorRT), Furiosa NPU, Multi-core CPU
📦 Getting Started
1. Run Cluster Locally or On-Premise
Docker Compose를 조합하여 원하는 규모와 하드웨어 스펙의 클러스터를 기동합니다.
# 1. Ray Head 노드 실행
docker-compose -f docker-compose.head.yaml up -d # CPU Node
docker-compose -f docker-compose.head.yaml -f docker-compose.head.gpu.yaml up -d # GPU Node
# 2. 워크로드에 맞는 Worker 노드 추가 (스케일 아웃 가능)
docker-compose -f docker-compose.worker.yaml up -d # CPU Node
docker-compose -f docker-compose.worker.yaml -f docker-compose.worker.gpu.yaml up -d # GPU Node
docker-compose -f docker-compose.worker.yaml -f docker-compose.worker.npu.yaml up -d # NPU Node
Metadata
Release files for pms-ray-cluster 1.5.8
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 |
|---|---|---|---|---|
| pms_ray_cluster-1.5.8.tar.gz | 5.8 kB | Without provenance | Details for pms_ray_cluster-1.5.8.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pms_ray_cluster-1.5.8-py3-none-any.whl | Python 3 | none | any | Details for pms_ray_cluster-1.5.8-py3-none-any.whl |
Total release size: 13.3 kB
Release files / pms_ray_cluster-1.5.8.tar.gz
| Download URL | pms_ray_cluster-1.5.8.tar.gz |
|---|---|
| Size | 5.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
0e4b092c2546718b022bd8067bfe6988b56a452601b05c84a020d9daf2fac9e1
|
|
BLAKE2b-256 checksum How to use checksums |
cc9bb6d5b687d955325168c27a4ff290007e7d267392c336ea337056a1ae8bbb
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / pms_ray_cluster-1.5.8-py3-none-any.whl
| Download URL | pms_ray_cluster-1.5.8-py3-none-any.whl |
|---|---|
| Size | 7.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a78a9c59165641e4082d10fff8bc6eff3b7092829b641b7c50777cca0d76b817
|
|
BLAKE2b-256 checksum How to use checksums |
5e47bbd9c98ea5e6b5fbc73c1122757bba1de8497df605e01a6863c9cef971e1
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for pms-ray-cluster 1.5.8
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
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.