Curated index of open-source OpenStack customizations
No repos indexed yet
Be the first to add an OpenStack customization!
OpenStack certification resources and pathways
We're curating study paths, practice exams, and community tips for Certified OpenStack Administrator (COA) and related credentials.
Frequently asked questions about OpenStack Support
OpenStack can be a simple all-in-one or an enormously complex multi-region beast. This standard keeps handovers clean and deployments auditable regardless of scale.
Recommended Tools
Git Repository
Name it after the deployment, like GalamStack_docs. Version history is your audit trail.
Folder Structure
Sub-folders for images/, diagrams/, benchmarks/, appendix/ etc.
LaTeX
A4 / Letter, standard margins (geometry pkg). Handles code blocks, tables, and cross-refs cleanly. Survives tooling rot.
Standard Document Sections
Summary
For whom, by whom, scale of deployment: all-in-one / multi-node / multi-region, storage type, customizations...
Team table: name · role · email for every person involved.
Environment
What is the initial provided environment: OS baseline, kernel, what needs to be built...
Mandatory checklist table with tick-offs per responsible person.
Equipment Details
Every node: hostname, make/model, CPU/RAM/storage, NIC speeds, assigned role (controller, compute...)
Include a future additions section even if dates are TBD.
Network
Full IP scheme: management, provider, overlay (VXLAN/VLAN), storage. CIDRs, VLANs, gateways...
Diagrams with detailed legends (draw.io, Visio, etc.). Can be a sub-section of §2.
Deployment Details
Structure varies by tool (Kolla-Ansible, TripleO, manual…) but two things are non-negotiable:
Tool justification
"I'm confident with Kolla-Ansible" is enough, but something must be stated.
Appendix: tool internals
How it works, config file locations (/etc/kolla/ etc.), microservices it manages…
Commands in code blocks
Every significant command in a lstlisting / minted block with CWD and env vars.
Proof of Work
Rally benchmark suite: Nova boot, Neutron network create, Cinder volume create, etc.
Embed results in a code block or link to benchmarks/ by commit SHA. Note Rally version used.
Sign Offs
Stability confirmed at two milestones. Delivering engineer and receiving team lead both sign.
Include date, signatories, and brief incident summary (or "none").
Every ticket is a future knowledge base entry. Documenting troubleshooting in a consistent, Git-tracked structure means the next person who hits the same issue doesn't start from zero.
The System
One Git repo per deployment
Keep a tickets/ folder inside the same deployment documentation repo. All ticket branches live here, so history, authorship, and diffs come for free.
One branch per ticket
Open a branch for each issue. Merge to main once resolved and confirmed. That merge commit is your closure record.
Folder & Branch Naming
Format: date_ticket_title
Both the folder inside tickets/ and the branch share the same name, so there's no ambiguity about which branch belongs to which issue.
ISO date first keeps the list sorted chronologically. Ticket ID links it to your tracker. Short title makes it human-readable at a glance.
Files Inside Each Ticket Folder
ticket_
description
Ticket Description
What is broken, who reported it, when, on which system. Environment state at the time: logs, error messages, affected services...
Include any steps to reproduce if known.
initial_
response
Initial Response
First hypothesis, commands run to investigate, what was ruled out. Even dead ends are worth recording...
Use code blocks for every command and its output.
solution
Solution
Root cause, exact fix applied, every command used. Step by step, with config changes diffed if applicable...
This is the file a future engineer searches for first.
confirmation
Confirmation
Proof the issue is resolved: service health output, reporter sign-off, monitoring screenshot or log snippet...
Merge the branch to main after this file is committed.
Quick Reference
What a resolved ticket folder looks like on disk:
Community directory of support providers & open-source OpenStack customizations.
openstack.support is an independent community directory for finding OpenStack professionals, customization repositories, and certification resources. Everything is being built now.
Deployment stacks
None listed.
OpenStack components
None listed.
Role
Will quote an approximate time upfront and work overtime for free if the issue is not completed or resolved within that estimate.
Index an open-source OpenStack customization
Comma or space separated · up to 10
README
No README available for this repository.
Files
View on GitHubCould not load file tree.
You'll need to sign back in to access your account.