|
| 1 | +======================================================================== |
| 2 | +OpenStack & Kubernetes Operations Documentation and Internationalization |
| 3 | +======================================================================== |
| 4 | + |
| 5 | +.. image:: https://github.com/infra-cloud-kr/openstack-kubernetes/actions/workflows/docs.yml/badge.svg |
| 6 | + :target: https://github.com/infra-cloud-kr/openstack-kubernetes/actions/workflows/docs.yml |
| 7 | + :alt: Documentation build status |
| 8 | + |
| 9 | +This project documents how to install and operate the two leading global |
| 10 | +open source infrastructure projects — **Kubernetes** and **OpenStack** — along |
| 11 | +with their best practices, and contributes to the internationalization (i18n) |
| 12 | +of the related upstream technical documentation, including its translation |
| 13 | +into Korean. |
| 14 | + |
| 15 | +Just as the two communities formally met through SIGs (Special Interest |
| 16 | +Groups) to drive technical integration, their documentation localization |
| 17 | +efforts run in parallel: the **OpenStack I18n SIG** and the **Kubernetes |
| 18 | +SIG Docs localization subproject**. This project sits at the meeting point of |
| 19 | +these two localization communities and aims to experience both of their |
| 20 | +Korean localization workflows. |
| 21 | + |
| 22 | +Following the conventions of the OpenStack documentation ecosystem, the |
| 23 | +repository is built with `Sphinx <https://www.sphinx-doc.org/>`_ and |
| 24 | +reStructuredText (rST), built via `tox <https://tox.wiki/>`_, and validated by |
| 25 | +GitHub Actions. The goal goes beyond simply writing documents: contributors |
| 26 | +also gain hands-on experience with the OpenStack-style documentation |
| 27 | +contribution workflow (rST/Sphinx, reviewable PRs, CI-based quality checks). |
| 28 | + |
| 29 | +.. note:: |
| 30 | + |
| 31 | + The documentation is currently an initial skeleton. The body of each |
| 32 | + section is intended to be filled in incrementally (see the ``note`` / TODO |
| 33 | + markers in each document). |
| 34 | + |
| 35 | + |
| 36 | +Goals |
| 37 | +===== |
| 38 | + |
| 39 | +The project centers on **"hands-on Korean localization"**: |
| 40 | + |
| 41 | +* Document installation, operation, and best practices for the *OpenStack on |
| 42 | + Kubernetes* and *Kubernetes on OpenStack* environments, based on real |
| 43 | + experience building and operating them. Beyond understanding the two |
| 44 | + projects, contributors practice documenting in a way that follows global |
| 45 | + norms, building the fundamentals needed to contribute to upstream open |
| 46 | + source projects. |
| 47 | +* Select the upstream documents referenced along the way and aim for 100% |
| 48 | + Korean localization. This includes setting up a translation platform such |
| 49 | + as Weblate and organizing know-how on AI-assisted translation, leaving a |
| 50 | + meaningful footprint in global open source documentation and i18n while |
| 51 | + translating with first-hand understanding of both technologies. |
| 52 | + |
| 53 | + |
| 54 | +Documentation layout |
| 55 | +===================== |
| 56 | + |
| 57 | +The documentation source lives under ``doc/source/`` and is organized into the |
| 58 | +following sections. |
| 59 | + |
| 60 | +* **introduction** — why the two technologies are used together, the history |
| 61 | + and present of SIG activities, and a suggested learning path |
| 62 | +* **OpenStack on Kubernetes** — running the OpenStack control plane on top of |
| 63 | + Kubernetes using openstack-helm, Kolla, and more |
| 64 | +* **Kubernetes on OpenStack** — running Kubernetes on top of OpenStack using |
| 65 | + Magnum, cloud-provider-openstack, Cinder CSI, the Octavia load balancer, |
| 66 | + and more |
| 67 | +* **storage** — integrating Cinder, Swift, and Ceph with Kubernetes |
| 68 | +* **labs** — step-by-step hands-on guides |
| 69 | +* **documentation** — rST/Sphinx basics, OpenStack/Kubernetes documentation |
| 70 | + conventions, and review guidelines |
| 71 | +* **translation-i18n** — how the two Korean localization communities (the |
| 72 | + OpenStack I18n SIG and the Kubernetes SIG Docs localization subproject) are |
| 73 | + organized, plus OpenStack i18n, Kubernetes localization, Weblate, and |
| 74 | + AI-assisted translation workflows |
| 75 | + |
| 76 | + |
| 77 | +Building locally |
| 78 | +================ |
| 79 | + |
| 80 | +With `tox <https://tox.wiki/>`_ installed, build the HTML documentation with: |
| 81 | + |
| 82 | +.. code-block:: console |
| 83 | +
|
| 84 | + $ tox -e docs |
| 85 | +
|
| 86 | +The output is generated under ``doc/build/html/``. Open |
| 87 | +``doc/build/html/index.html`` in a browser to review it. |
| 88 | + |
| 89 | +To build directly without tox: |
| 90 | + |
| 91 | +.. code-block:: console |
| 92 | +
|
| 93 | + $ python -m venv .venv |
| 94 | + $ . .venv/bin/activate |
| 95 | + $ pip install -r doc/requirements.txt |
| 96 | + $ sphinx-build -W -b html doc/source doc/build/html |
| 97 | +
|
| 98 | +To lint the rST sources: |
| 99 | + |
| 100 | +.. code-block:: console |
| 101 | +
|
| 102 | + $ tox -e pep8 |
| 103 | +
|
| 104 | +
|
| 105 | +Contributing |
| 106 | +============ |
| 107 | + |
| 108 | +See `CONTRIBUTING.rst <CONTRIBUTING.rst>`_ for how to contribute. |
| 109 | + |
| 110 | + |
| 111 | +License |
| 112 | +======= |
| 113 | + |
| 114 | +This project is licensed under the `Apache License 2.0 <LICENSE>`_. |
0 commit comments