Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Mon, Jun 12, 2017 at 8:02 AM, Jiří Stránský wrote: > On 9.6.2017 18:51, Flavio Percoco wrote: >> >> A-ha, ok! I figured this was another option. In this case I guess we would >> have 2 options: >> >> 1. Run confd + openstack service in side the container. My concern in this >> case >> would be

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

evelopment Mailing List (not for usage questions) Subject: Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd On Fri, Jun 09, 2017 at 04:52:25PM +, Flavio Percoco wrote: > On Fri, Jun 9, 2017 at 11:30 AM Britt Houser (bhou

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd On 09.06.2017 18:51, Flavio Percoco wrote: > > > On Fri, Jun 9, 2017 at 8:07 AM Doug Hellmann <mailto:d...@doughellmann.com>> wrote: > > Excerpts from Flavio Percoco's m

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 12.06.2017 14:02, Jiří Stránský wrote: > On 9.6.2017 18:51, Flavio Percoco wrote: >> A-ha, ok! I figured this was another option. In this case I guess we >> would >> have 2 options: >> >> 1. Run confd + openstack service in side the container. My concern in >> this >> case >> would be that we'd

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 12/06/17 10:07 +0200, Bogdan Dobrelya wrote: On 09.06.2017 18:51, Flavio Percoco wrote: On Fri, Jun 9, 2017 at 8:07 AM Doug Hellmann mailto:d...@doughellmann.com>> wrote: Excerpts from Flavio Percoco's message of 2017-06-08 22:28:05 +: > Unless I'm missing something, to use co

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 9.6.2017 18:51, Flavio Percoco wrote: A-ha, ok! I figured this was another option. In this case I guess we would have 2 options: 1. Run confd + openstack service in side the container. My concern in this case would be that we'd have to run 2 services inside the container and structure things

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 09.06.2017 18:51, Flavio Percoco wrote: > > > On Fri, Jun 9, 2017 at 8:07 AM Doug Hellmann > wrote: > > Excerpts from Flavio Percoco's message of 2017-06-08 22:28:05 +: > > > Unless I'm missing something, to use confd with an OpenStack > deploym

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Flavio Percoco's message of 2017-06-09 16:52:25 +: > On Fri, Jun 9, 2017 at 11:30 AM Britt Houser (bhouser) > wrote: > > > How does confd run inside the container? Does this mean we’d need some > > kind of systemd in every container which would spawn both confd and the > > real

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Fri, Jun 09, 2017 at 04:52:25PM +, Flavio Percoco wrote: > On Fri, Jun 9, 2017 at 11:30 AM Britt Houser (bhouser) > wrote: > > > How does confd run inside the container? Does this mean we’d need some > > kind of systemd in every container which would spawn both confd and the > > real serv

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Fri, Jun 9, 2017 at 11:30 AM Britt Houser (bhouser) wrote: > How does confd run inside the container? Does this mean we’d need some > kind of systemd in every container which would spawn both confd and the > real service? That seems like a very large architectural change. But > maybe I’m mi

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Fri, Jun 9, 2017 at 8:07 AM Doug Hellmann wrote: > Excerpts from Flavio Percoco's message of 2017-06-08 22:28:05 +: > > > Unless I'm missing something, to use confd with an OpenStack deployment > on > > k8s, we'll have to do something like this: > > > > * Deploy confd in every node where w

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

How does confd run inside the container? Does this mean we’d need some kind of systemd in every container which would spawn both confd and the real service? That seems like a very large architectural change. But maybe I’m misunderstanding it. Thx, britt On 6/9/17, 9:04 AM, "Doug Hellmann"

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Flavio Percoco's message of 2017-06-08 22:28:05 +: > Unless I'm missing something, to use confd with an OpenStack deployment on > k8s, we'll have to do something like this: > > * Deploy confd in every node where we may want to run a pod (basically > wvery node) Oh, no, no. That

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

questions) Subject: Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd On Thu, Jun 8, 2017, 19:14 Doug Hellmann mailto:d...@doughellmann.com>> wrote: Excerpts from Flavio Percoco's message of 2017-06-08 18:27:51 +02

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Thu, Jun 8, 2017, 19:14 Doug Hellmann wrote: > Excerpts from Flavio Percoco's message of 2017-06-08 18:27:51 +0200: > > On 08/06/17 18:23 +0200, Flavio Percoco wrote: > > >On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: > > >>On 06.06.2017 18:08, Emilien Macchi wrote: > > >>>Another benefit is

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

not for usage questions)" < > openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] > [kolla] [helm] Configuration management with etcd / confd > > On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: > >On 06

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd > On Jun 8, 2017, at 4:29 PM, Fox, Kevin M wrote: > > That is possible. But, a yaml/json driver

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

> On Jun 8, 2017, at 4:29 PM, Fox, Kevin M wrote: > > That is possible. But, a yaml/json driver might still be good, regardless of > the mechanism used to transfer the file. > > So the driver abstraction still might be useful. Why would it be useful to have oslo.config read files in more than

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

(not for usage questions) Subject: Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd On Thu, Jun 8, 2017 at 8:49 PM, Doug Hellmann wrote: > Excerpts from Steven Dake (stdake)'s message of 2017-06-08 17:51:48 +:

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Emilien Macchi's message of 2017-06-08 22:20:34 +0200: > On Thu, Jun 8, 2017 at 8:49 PM, Doug Hellmann wrote: > > Excerpts from Steven Dake (stdake)'s message of 2017-06-08 17:51:48 +: > >> Doug, > >> > >> In short, a configmap takes a bunch of config files, bundles them in a >

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

1:19 PM To: openstack-dev Subject: Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd Excerpts from Fox, Kevin M's message of 2017-06-08 20:08:25 +: > Yeah, I think k8s configmaps might be a good config mechanism

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

-Original Message- >> From: Doug Hellmann >> Reply-To: "OpenStack Development Mailing List (not for usage questions)" >> >> Date: Thursday, June 8, 2017 at 10:12 AM >> To: openstack-dev >> Subject: Re: [openstack-dev] [deployment] [oslo] [a

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Fox, Kevin M's message of 2017-06-08 20:08:25 +: > Yeah, I think k8s configmaps might be a good config mechanism for k8s based > openstack deployment. > > One feature that might help which is related to the etcd plugin would be a > yaml/json plugin. It would allow more native l

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

From: Doug Hellmann [d...@doughellmann.com] Sent: Thursday, June 08, 2017 11:49 AM To: openstack-dev Subject: Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd Excerpts from Steven Dake (stdake)'s message of 2017-06-08 17:

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

017 at 10:12 AM > To: openstack-dev > Subject: Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] > [helm] Configuration management with etcd / confd > > Excerpts from Flavio Percoco's message of 2017-06-08 18:27:51 +0200: > > On 08/06/17 18:23

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 8 June 2017 at 09:50, Michał Jastrzębski wrote: > On 8 June 2017 at 09:27, Flavio Percoco wrote: >> On 08/06/17 18:23 +0200, Flavio Percoco wrote: >>> >>> On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: On 06.06.2017 18:08, Emilien Macchi wrote: > > Another benefit is that co

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

pment Mailing List (not for usage questions)" Date: Thursday, June 8, 2017 at 10:12 AM To: openstack-dev Subject: Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd Excerpts from Flavio Percoco's message of 2017

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: >On 06.06.2017 18:08, Emilien Macchi wrote: >> Another benefit is that confd will generate a configuration file when >> the application will st

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Flavio Percoco's message of 2017-06-08 18:27:51 +0200: > On 08/06/17 18:23 +0200, Flavio Percoco wrote: > >On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: > >>On 06.06.2017 18:08, Emilien Macchi wrote: > >>>Another benefit is that confd will generate a configuration file when > >>>the

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 8 June 2017 at 09:27, Flavio Percoco wrote: > On 08/06/17 18:23 +0200, Flavio Percoco wrote: >> >> On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: >>> >>> On 06.06.2017 18:08, Emilien Macchi wrote: Another benefit is that confd will generate a configuration file when the applicat

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 08/06/17 18:23 +0200, Flavio Percoco wrote: On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: On 06.06.2017 18:08, Emilien Macchi wrote: Another benefit is that confd will generate a configuration file when the application will start. So if etcd is down *after* the app startup, it shouldn't br

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 07/06/17 12:04 +0200, Bogdan Dobrelya wrote: On 06.06.2017 18:08, Emilien Macchi wrote: Another benefit is that confd will generate a configuration file when the application will start. So if etcd is down *after* the app startup, it shouldn't break the service restart if we don't ask confd to

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

> On Jun 7, 2017, at 7:20 AM, Emilien Macchi wrote: > > On Tue, Jun 6, 2017 at 6:08 PM, Emilien Macchi > wrote: >> Following-up the session that we had in Boston: >> https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management >> >> Here's an update

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Tue, Jun 6, 2017 at 6:08 PM, Emilien Macchi wrote: > Following-up the session that we had in Boston: > https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management > > Here's an update on where we are and what is being done. > > > == Machine Readable Sample Config > > Ben's spe

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 06.06.2017 18:08, Emilien Macchi wrote: > Following-up the session that we had in Boston: > https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management > > Here's an update on where we are and what is being done. > > > == Machine Readable Sample Config > > Ben's spec has be

[openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Following-up the session that we had in Boston: https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management Here's an update on where we are and what is being done. == Machine Readable Sample Config Ben's spec has been merged: https://review.openstack.org/#/c/440835/ And also