-
Notifications
You must be signed in to change notification settings - Fork 0
🎨 Palette: [UX improvement] Enhance Documentation UX & Accessibility #31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| @@ -1,20 +1,46 @@ | ||||||||||||||
| # ⚖️ arbiter | ||||||||||||||
|
|
||||||||||||||
| [](https://opensource.org/licenses/MIT) | ||||||||||||||
|  | ||||||||||||||
| [](https://opensource.org/licenses/MIT) | ||||||||||||||
|
|
||||||||||||||
| > [!CAUTION] | ||||||||||||||
| > This project is currently **Experimental**. It is not recommended for production use and is subject to significant changes as the architecture evolves. | ||||||||||||||
|
|
||||||||||||||
| Dual nature—combining bare-metal virtualized hardware management (aSHARD VRAM pinning) with quantum-accelerated Kubernetes scheduling. | ||||||||||||||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There is a terminology conflict between this tagline and the 'Key Features' section. Line 40 emphasizes 'bypassing virtualization overhead' with 'direct hardware management,' which contradicts the 'virtualized hardware management' mentioned here. Clarifying whether the system manages virtualized resources or provides direct bare-metal access will improve documentation clarity.
Suggested change
|
||||||||||||||
|
|
||||||||||||||
| ## 📖 Overview | ||||||||||||||
|
|
||||||||||||||
| `arbiter` is a specialized orchestration layer designed for high-performance computing environments. It bridges the gap between low-level hardware management and cloud-native scheduling, providing a unified interface for managing virtualized resources with precision. | ||||||||||||||
|
|
||||||||||||||
| ## 🏗️ Architecture | ||||||||||||||
|
|
||||||||||||||
| ```mermaid | ||||||||||||||
| graph TD | ||||||||||||||
| subgraph CloudNative [Cloud Native Layer] | ||||||||||||||
| K8s[Kubernetes Cluster] | ||||||||||||||
| end | ||||||||||||||
|
|
||||||||||||||
| subgraph Orchestration [Orchestration Layer] | ||||||||||||||
| Arbiter((Arbiter Core)) | ||||||||||||||
| end | ||||||||||||||
|
|
||||||||||||||
| subgraph Infrastructure [Infrastructure Layer] | ||||||||||||||
| BareMetal[Bare Metal Servers] | ||||||||||||||
| GPU[GPU Resources / VRAM] | ||||||||||||||
| end | ||||||||||||||
|
|
||||||||||||||
| K8s <--> Arbiter | ||||||||||||||
| Arbiter <--> BareMetal | ||||||||||||||
| Arbiter <--> GPU | ||||||||||||||
|
Comment on lines
+31
to
+33
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. In Mermaid flowcharts, the standard syntax for a bidirectional arrow is
Suggested change
|
||||||||||||||
|
|
||||||||||||||
| style Arbiter fill:#f96,stroke:#333,stroke-width:4px | ||||||||||||||
| ``` | ||||||||||||||
|
|
||||||||||||||
| ## 🚀 Key Features | ||||||||||||||
|
|
||||||||||||||
| - 🏗️ **Infrastructure Awareness**: Directly manages bare-metal resources for maximum performance. | ||||||||||||||
| - 📍 **VRAM Optimization**: Uses aSHARD pinning to eliminate GPU memory fragmentation. | ||||||||||||||
| - ⚛️ **Next-Gen Scheduling**: Leverages quantum-accelerated algorithms for complex Kubernetes workloads. | ||||||||||||||
| - ⚖️ **Unified Orchestration**: A single control plane for both hardware and cluster-level operations. | ||||||||||||||
| - 🏗️ **Bare-Metal Precision**: Bypass virtualization overhead with direct hardware management for latency-sensitive AI workloads. | ||||||||||||||
| - 📍 **Intelligent VRAM Pinning**: Maximize GPU utilization and eliminate fragmentation using aSHARD-driven memory allocation. | ||||||||||||||
| - ⚛️ **Quantum-Accelerated Scheduling**: Resolve complex multi-constraint resource allocations faster than traditional heuristics. | ||||||||||||||
| - ⚖️ **Unified Control Plane**: Seamlessly bridge the gap between low-level hardware states and high-level Kubernetes orchestration. | ||||||||||||||
|
|
||||||||||||||
| ## ⚖️ License | ||||||||||||||
|
|
||||||||||||||
|
|
||||||||||||||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Screen readers primarily use the
altattribute (the text in the first set of brackets) rather than thetitleattribute (the quoted text after the URL) to describe images. To improve accessibility as intended in the PR description, consider moving the descriptive text to thealtattribute.