openstack
/
kolla
Code Issues Proposed changes
kolla/specs
History
Nick Jones b905892768
Spec: Kolla-managed backup (and restore) for MariaDB 
This mini-spec documents an approach for how Kolla-triggered and managed
MariaDB backups might be handled.

Change-Id: I65f1ab92b9dce48cdd752fffd2123bd58d65b98f
bp: https://blueprints.launchpad.net/kolla/+spec/database-backup-recovery
 		2018-09-13 09:51:32 +01:00
..
README.rst Fix title spell and rst 2017-08-10 20:18:10 +09:00
ansible-multi.rst Delete the unnecessary space 2016-10-15 04:07:29 +00:00
containerize-openstack.rst Use https links for documentation 2017-06-12 23:06:35 +08:00
ha.svg Spec to Add Support for High Availability 2015-06-17 09:47:39 -07:00
high-availability.rst Word choice for back end 2016-11-15 07:48:13 +00:00
kolla-ceph-bluestore.rst Fix bluestore disk naming format in kolla 2018-08-27 16:11:08 +09:00
kubernetes-deployment.rst Fix dir specs typo error 2016-12-08 14:54:06 +08:00
logging-with-heka.rst Replace Chinese single quotes to English single quotes 2018-02-05 18:06:24 +08: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
template.rst Delete the unnecessary space 2016-10-15 04:07:29 +00:00

README.rst

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.