Live deployment · Documentation · Dashboard source · Contribute · 한국어
English · 한국어 · 日本語 · 简体中文 · Español
Afterglow is an open-source organization building an OpenStack dashboard and the services around it. Our core project, Afterglow, aims to become an alternative to Horizon and Skyline: a modern, unified interface for cloud users and operators.
We build from real operational needs. Afterglow is deployed at cloud.dmslab.re.kr as the DMS Cloud console, bringing infrastructure management, Kubernetes, reusable environments, and AI services into one experience. Access to the running service follows the operator's account and project policies.
We welcome developers, OpenStack operators, researchers, designers, technical writers, and first-time contributors. You do not need to contribute code to make a difference.
| Project | Focus | Start here |
|---|---|---|
| Afterglow | The core dashboard: SvelteKit UI and FastAPI gateway for OpenStack resource management and integrated services. | README · Issues |
| Drover | K3s cluster and node-group lifecycle management on OpenStack. | README · Issues |
| Palimpsest | Reusable VM environments, SquashFS layers, boot images, and local layered VM workflows. | README · Issues |
| Lumen | AI chat and agent execution, provider routing, tools, memory, and usage tracking. | README · Issues |
| Waygate | Project-scoped WireGuard gateway lifecycle and client configuration for OpenStack. | README · Issues |
Each repository documents its own setup, supported environments, release status, and license. The table describes project scope; deployment and maturity can differ by component.
- A clearer cloud experience. Make compute, images, networks, volumes, shares, and load balancers easier to discover and manage.
- Services that work together. Connect Kubernetes provisioning, reusable runtime environments, AI capabilities, and project connectivity through a common dashboard.
- Feedback from real operations. Turn day-to-day cloud usage into better workflows, documentation, and reproducible fixes.
- Room for more contributors. Build a community across frontend, backend, infrastructure, design, testing, and documentation.
Start small: try a workflow, improve a page, reproduce a bug, or review a change.
| Your interest | Useful first contributions |
|---|---|
| Frontend & UX | Improve SvelteKit screens, accessibility, resource tables, error states, and user journeys. |
| Backend & OpenStack | Improve API integrations, permissions, resource lifecycle handling, and failure recovery. |
| Infrastructure & testing | Document deployments, reproduce compatibility issues, and improve automated checks. |
| Documentation & translation | Clarify setup steps, add examples, and improve translations. |
| Cloud operations & research | Share reproducible use cases, usability feedback, and operational lessons without credentials or tenant data. |
- Choose a repository above and read its README, architecture notes, and any contribution or agent instructions.
- Check existing issues and pull requests. For a larger feature or behavior change, open an issue first to discuss the problem and scope. If you are unsure where a cross-project idea belongs, start with an Afterglow issue.
- Fork the repository and create a focused branch. Follow that repository's development setup; the dashboard's local stack has sibling-service and OpenStack configuration requirements.
- Make one clear change. Run the relevant documented checks. Include tests for behavior changes and update affected documentation.
- Open a pull request explaining the problem, the change, and how you verified it. For UI changes, include screenshots; for bugs, include sanitized reproduction steps.
Bug reports: include the component, version or commit, environment, expected and actual behavior, and a minimal reproduction. Remove secrets, tokens, private addresses, and user data from logs and screenshots.
Questions and ideas: use the relevant repository's Issues. Korean and English are both welcome. You can contribute through issues and pull requests without joining the organization first.
Our goal is to turn experience building and operating Afterglow into useful contributions to the wider OpenStack ecosystem:
- Report reproducible upstream bugs with clear environment details and minimal examples.
- Propose broadly useful fixes, tests, and documentation to the relevant OpenStack projects.
- Discuss API compatibility and integration needs with upstream maintainers before creating project-specific workarounds.
- Share operational lessons and user-experience feedback that can help other clouds.
Afterglow changes are proposed through this organization's GitHub repositories. Changes to upstream OpenStack projects follow the official OpenStack contributor guide and the target project's contribution process, including Gerrit review where applicable.
Afterglow is independently developed for the OpenStack ecosystem. This page does not claim official OpenStack project status, endorsement, or upstream acceptance. Upstream contribution is a direction we want to pursue together.
English · 한국어 · 日本語 · 简体中文 · Español
These pages introduce the organization; individual projects document their own language support. English is the reference for this profile. Translation fixes and additional languages are welcome through pull requests. When changing shared information, update the translated introductions too.