kolla/specs
Michal Nasiadka d79c07effb CI: Add codespell for spell checking
Fix existing spell checking

Change-Id: Ief7b8f2d427b2557c84fda9b3774ed85ceb105f4
2024-04-15 14:56:34 +00:00
..
ansible-multi.rst Delete the unnecessary space 2016-10-15 04:07:29 +00:00
containerize-openstack.rst doc: Start using openstackdoctheme's extlink extension 2019-06-14 21:23:10 +08:00
ha.svg Spec to Add Support for High Availability 2015-06-17 09:47:39 -07:00
high-availability.rst Move to opendev 2019-04-24 15:22:57 +08:00
kolla-ceph-bluestore.rst CI: Add codespell for spell checking 2024-04-15 14:56:34 +00:00
kubernetes-deployment.rst CI: Add codespell for spell checking 2024-04-15 14:56:34 +00:00
logging-with-heka.rst CI: Add codespell for spell checking 2024-04-15 14:56:34 +00:00
logging-with-heka.svg Logging with Heka spec 2016-01-29 14:11:02 +01:00
mariadb-backup-recovery.rst Spec: Kolla-managed backup (and restore) for MariaDB 2018-09-13 09:51:32 +01:00
README.rst Fix title spell and rst 2017-08-10 20:18:10 +09:00
template.rst CI: Add codespell for spell checking 2024-04-15 14:56:34 +00:00

Specifications are Advisory

This project is under heavy active development. Specifications in this repository reflects general consensus of ideas at the time the specification was conceived rather then set of actions to take or a commitment to precisely implement the specification. As an example, kolla-ansible looks much different today than then ansible-multi spec. For Kolla old-timers, many know that Kolla in its present form may not have existed without this general consensus of ideas set by ansible-multi.

All specifications in this repository are subject to abandonment in the future if the development team finds it necessary to change course.

The single source of truth for development work is recorded in blueprints as specifications are immutable once committed to the repository. Blueprints on the other hand are dynamic and may be changed at any time along with the codebase.