Open Stack

Let's please re-evaluate configuration of containerized non-openstack,
like database, message queue, key value, web, services for tripleo heat
templates and Kolla. Here is an example containerized etcd patch [0].

tl;dr use kolla images and bootsrap OR upstream images with direct commands:

.. code-block:: yaml
kolla_config:
    /var/lib/kolla/config_files/foo.json
      command: /usr/bin/foo

vs

.. code-block:: yaml
foo:
    image: upstream/foo:latest
    command: /usr/bin/foo

Note, tht already doesn't use configs [1] copied into the images by
kolla build time. The next and logical step might be to omit kolla's
bootstrap, where applicable, as well.

There is a two options:
* use kolla images and bootstrap as t-h-t does now for all services
being containerized
pros: same way to template everything, kolla build/start just works.
risks: non-openstack services, eventually, may stop being supported by
Kolla for number of reasons. Kolla bootstrap changes aren't tested in
tripleo CI and might be breaking
cons: locking in to the kolla opinionated bootstrap entry points and
kolla_config's config.json and command.

* if applicable to the service, use upstream images (etcd example [2])
w/o any kolla parts.
pros: less moving parts like custom entry points, no locking in
onto opinionated Kolla config/bootstrap
risks: Upstream image changes aren't tested in tripleo CI and might be
breaking
cons: different ways to template openstack/non-openstack services, kolla
build/start doesn't work for the latter.

[0] https://review.openstack.org/#/c/447627/
[1] https://review.openstack.org/#/c/451366
[2]
https://review.openstack.org/#/c/445883/2/contrib/overcloud_containers.yaml

-- 
Best regards,
Bogdan Dobrelya,
Irc #bogdando