Sno Station
Sno Station은 AI 에이전트를 하나의 팀으로 묶는 오픈소스 워크스테이션으로, 로컬 머신에서 에이전트 협업을 가능하게 함
OpenShift Edge 팀 도구를 모아 팀 운영과 개발자 워크플로우를 지원하는 버킷
Bucket for OpenShift Edge Team tooling that supports team operations and developer workflow.
플러그인Python · ShellGitHub @openshift-eng직접 설치운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
설치형 프로젝트는 배포 도메인 없이도 확인할 수 있습니다. 개인 저장소는 GitHub 로그인으로, 조직 저장소는 위의 저장소 확인 파일로 직접 확인해 주세요.
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Automation, AI skills, and deployment tools for OpenShift edge engineering. This repo is the OpenShift Edge team's shared toolkit — it provides cluster deployment automation for edge topologies (two-node HA, SNO, LVM), CI and release workflow tooling, and a Claude Code plugin marketplace that gives engineers AI-assisted skills for day-to-day work.
make setup-githooks installs a pre-commit hook that runs markdownlint on staged .md files.
Prerequisites: Node.js (for markdownlint), Python 3, Bash.
Each deployment tool has its own prerequisites — see the component README for what you need.README 전문 보기 ↗Automation, AI skills, and deployment tools for OpenShift edge engineering. This repo is the OpenShift Edge team's shared toolkit — it provides cluster deployment automation for edge topologies (two-node HA, SNO, LVM), CI and release workflow tooling, and a Claude Code plugin marketplace that gives engineers AI-assisted skills for day-to-day work.
| Use case | Component |
|---|---|
| Two-node HA cluster (arbiter or fencing) | two-node-toolbox/ |
| EC2 dev host or hypervisor | ec2-deploy/ |
| Automatic EC2 shutdown and weekly Slack report | watchman/ |
| Single Node OpenShift with DU config | sno-deploy/ |
| LVM Operator development workspace | environments/lvm-operator/ |
| Nightly payload health monitoring | payload-monitor/ |
| Component Readiness triage report (HA vs edge) | ci-tooling/readiness-report/ |
| Multi-repo workspace management | workspace plugin via the marketplace |
| Claude Code plugins for edge workflows | plugins/ via the marketplace |
git clone [email protected]:openshift-eng/edge-tooling.git
cd edge-tooling
make setup-githooks
make setup-githooks installs a pre-commit hook that runs markdownlint on staged .md files.
Prerequisites: Node.js (for markdownlint), Python 3, Bash.
Each deployment tool has its own prerequisites — see the component README for what you need.
From within Claude Code:
/plugin marketplace add openshift-eng/edge-tooling
Then enable whichever plugins you need. See the plugin README for details.
| Plugin | What it does |
|---|---|
| challenge | Adversarial hypothesis reviewer for root cause analysis |
| edge-ic | IC workflow automation — TODOs, status reports, Jira updates |
| edge-ocp-ci | Monitor nightly payload health across edge topologies with AI-enriched analysis |
| edge-ocp-rc | RC testing for OCP edge topologies (TNF, TNA, SNO) — launch Prow jobs, track results, classify failures |
| edge-scrum | Scrum process management — refinement, sprint planning, standups |
| github | GitHub workflow skills — PR automation, labeling, queue management |
| lvms | LVMS release, QE, and operational workflows |
| lvms-ci | LVMS CI automation — failure triage, Prow job analysis |
| mcp-atlassian | Atlassian Jira MCP server for Claude Code |
| microshift-ci | MicroShift CI failure analysis and JIRA bug creation |
| Directory | What it does |
|---|---|
| two-node-toolbox/ | Deploy two-node OpenShift clusters (arbiter/fencing topologies) |
| ec2-deploy/ | Spin up EC2 instances for development and hypervisor use |
| watchman/ | Stop stale EC2 instances and send weekly Slack reports |
| sno-deploy/ | Deploy Single Node OpenShift with DU configuration |
| payload-monitor/ | Nightly payload health monitoring for edge topologies |
| environments/lvm-operator/ | Development workspace for the LVM Storage operator |
| Directory | What it does |
|---|---|
| ci-tooling/ | Collection of standalone CI helpers |
| ci-tooling/readiness-report/ | Sippy Component Readiness report for HA vs TNF/TNA/SNO |
| Resource | What it covers |
|---|---|
| AGENTS.md | Repo overview, tool routing, component-level guides |
| CONTRIBUTING.md | Contribution model, code standards, architectural patterns |
| docs/claude/workflows.md | Deployment walkthroughs and Component Readiness reports |
| docs/claude/prerequisites.md | Required credentials and tools |
| Component READMEs | Per-tool setup, prerequisites, and usage |
PRs use the fork model — push to your fork, open a PR against main. See CONTRIBUTING.md for details.
| microshift-dev | MicroShift dev tools collection |
| microshift-release | MicroShift release testing automation |
| pr-review | PR lifecycle toolkit — vet findings, triage CodeRabbit reviews, yolo-agent |
| skills-review | Lint SKILL.md files for quality and correctness |
| threat-model | Security threat analysis for OpenShift PRs |
| two-node | Two-node topology workflow automation — RHEL verification, Jira integration |
| workspace | Multi-repo workspace manager for cross-project AI-assisted development |