kolla-kubernetes/services/mariadb
David C Wang 3155b1e2d2 Git mv'd all bootstrap dir files into services dir
- No bug-fixes, blue-prints, nor code changes.
- Originally, kolla-kubernetes only used 3 types of kubernetes
resource files (job, pod, svc).  Bootstrap files (job) were separated
from service files (pod, svc).  Subcommands were tied directly to the
files their respective directories (bootstrap command -> ./bootstrap
dir, run command -> ./services dir).
- This was done because of the way kolla-kubernetes used to work.
Upon subcommand launch, all of the files in its respective
directory were jinja processed and then loaded into kubernetes (in
random order).
- Now that we have added a bunch of resources that require ordering
(disk, pv, pvc, etc), and kolla-kubernetes directly references each
type of file based on the configuration of
./etc/kolla-kubernetes/kolla-kubernetes.yml, we no longer need to
separate bootstrap and service files.

Change-Id: I595388a686330cfdeb662b9a0a8b52cc1d45c913
2016-07-19 20:51:04 +00:00
..
mariadb-bootstrap-job.yml.j2 Git mv'd all bootstrap dir files into services dir 2016-07-19 20:51:04 +00:00
mariadb-disk.sh.j2 Git mv'd all bootstrap dir files into services dir 2016-07-19 20:51:04 +00:00
mariadb-pod.yml.j2 Kolla-Kubernetes multi-node persistence for Mariadb 2016-07-18 17:21:10 +00:00
mariadb-pv.yml.j2 Git mv'd all bootstrap dir files into services dir 2016-07-19 20:51:04 +00:00
mariadb-pvc.yml.j2 Git mv'd all bootstrap dir files into services dir 2016-07-19 20:51:04 +00:00
mariadb-service.yml.j2 Convert MariaDB to work without HostNetwork=True 2016-06-07 16:47:19 -07:00