Skip to content

Contributing

This repository follows the OzarLand community contribution guide: CONTRIBUTING.md in ozarland.

In short:

  1. Give context: OpenStack release, components, deployment method, environment conditions, what you checked.
  2. No sensitive data: no secrets, real hostnames, domains, IP or MAC addresses, customer or person names, unredacted logs (how to redact).
  3. Flag risky commands: ⚠️ state-changing, 🛑 destructive (risk warnings).
  4. Say where it was observed; never present a procedure as universal.
  5. Use the templates in templates/, open a pull request, sign off your commits (git commit -s).

Repository-specific notes:

  • Put the page in the directory of its primary symptom (lifecycle/, scheduling/, migration/, networking/, volumes/, recovery/); cross-cutting investigation guides go in diagnostics/, guides to reading a service's logs in logs/.
  • Name the file after the symptom, lowercase, hyphenated: instance-stuck-in-build-waiting-for-vif-plugged.md.
  • Add the page to the index table in README.md in the same pull request. The status badges and progress bars are generated: after adding a page or changing a status:, run tools/status_blocks.py --write from the ozarland repository (usage at the top of the script) and commit what it changes in README.md.