3155b1e2d2
- 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 |
||
---|---|---|
.. | ||
glance-api-pod.yml.j2 | ||
glance-api-service.yml.j2 | ||
glance-bootstrap-job.yml.j2 | ||
glance-registry-pod.yml.j2 | ||
glance-registry-service.yml.j2 |