Re: [openstack-dev] [tripleo][kolla] extended start and hostpath persistent dirs

2017-04-10 Thread Jiří Stránský
Responses inline :) I started snipping parts out because the quotations are getting long. 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 We insist on using

Re: [openstack-dev] [tripleo][kolla] extended start and hostpath persistent dirs

2017-04-10 Thread Bogdan Dobrelya
Dan, Martin, Jiri, and all folks, how could we make a final call for this please? The decision impacts code review for new patches, like redis [0] or etcd [1] [0] https://review.openstack.org/#/c/442151/ [1] https://review.openstack.org/#/c/447627/ As I see (suggest) it: On 04.04.2017 22:53,

Re: [openstack-dev] [tripleo][kolla] extended start and hostpath persistent dirs (was: kolla_bootstrap for non-openstack services)

2017-04-04 Thread Dan Prince
On Tue, 2017-04-04 at 18:03 +0200, Bogdan Dobrelya wrote: > On 03.04.2017 21:01, Dan Prince wrote: > > On Mon, 2017-04-03 at 16:15 +0200, Bogdan Dobrelya wrote: > > > Let's please re-evaluate configuration of containerized non- > > > openstack, > > > like database, message queue, key value, web,

Re: [openstack-dev] [tripleo][kolla] extended start and hostpath persistent dirs (was: kolla_bootstrap for non-openstack services)

2017-04-04 Thread Bogdan Dobrelya
On 03.04.2017 21:01, Dan Prince wrote: > On Mon, 2017-04-03 at 16:15 +0200, Bogdan Dobrelya wrote: >> 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