Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-10-25 Thread Dan Prince
On Wed, Oct 17, 2018 at 11:15 AM Alex Schultz wrote: > > Time to resurrect this thread. > > On Thu, Jul 5, 2018 at 12:14 PM James Slagle wrote: > > > > On Thu, Jul 5, 2018 at 1:50 PM, Dan Prince wrote: > > > Last week I was tinkering with my docker configuration a bit and was a > > > bit

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-10-25 Thread Dan Prince
On Thu, Oct 25, 2018 at 11:26 AM Alex Schultz wrote: > > On Thu, Oct 25, 2018 at 9:16 AM Bogdan Dobrelya wrote: > > > > > > On 10/19/18 8:04 PM, Alex Schultz wrote: > > > On Fri, Oct 19, 2018 at 10:53 AM James Slagle > > > wrote: > > >> > > >> On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz >

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-10-25 Thread Alex Schultz
On Thu, Oct 25, 2018 at 9:16 AM Bogdan Dobrelya wrote: > > > On 10/19/18 8:04 PM, Alex Schultz wrote: > > On Fri, Oct 19, 2018 at 10:53 AM James Slagle > > wrote: > >> > >> On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz > >> wrote: > >> > Additionally I took a stab at combining the

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-10-25 Thread Bogdan Dobrelya
On 10/19/18 8:04 PM, Alex Schultz wrote: On Fri, Oct 19, 2018 at 10:53 AM James Slagle wrote: On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz wrote: > Additionally I took a stab at combining the puppet/docker service > definitions for the aodh services in a similar structure to start >

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-10-22 Thread Juan Antonio Osorio Robles
On 10/19/18 8:04 PM, Alex Schultz wrote: > On Fri, Oct 19, 2018 at 10:53 AM James Slagle wrote: >> On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz wrote: >>> Additionally I took a stab at combining the puppet/docker service >>> definitions for the aodh services in a similar structure to start >>>

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-10-19 Thread Alex Schultz
On Fri, Oct 19, 2018 at 10:53 AM James Slagle wrote: > > On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz wrote: > > Additionally I took a stab at combining the puppet/docker service > > definitions for the aodh services in a similar structure to start > > reducing the overhead we've had from

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-10-19 Thread James Slagle
On Wed, Oct 17, 2018 at 11:14 AM Alex Schultz wrote: > Additionally I took a stab at combining the puppet/docker service > definitions for the aodh services in a similar structure to start > reducing the overhead we've had from maintaining the docker/puppet > implementations seperately. You can

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-10-17 Thread Alex Schultz
Time to resurrect this thread. On Thu, Jul 5, 2018 at 12:14 PM James Slagle wrote: > > On Thu, Jul 5, 2018 at 1:50 PM, Dan Prince wrote: > > Last week I was tinkering with my docker configuration a bit and was a > > bit surprised that puppet/services/docker.yaml no longer used puppet to > >

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-08-07 Thread Dan Prince
On Thu, Aug 2, 2018 at 5:42 PM Steve Baker wrote: > > > > On 02/08/18 13:03, Alex Schultz wrote: > > On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya wrote: > >> On 7/6/18 7:02 PM, Ben Nemec wrote: > >>> > >>> > >>> On 07/05/2018 01:23 PM, Dan Prince wrote: > On Thu, 2018-07-05 at 14:13

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-08-03 Thread Alex Schultz
On Thu, Aug 2, 2018 at 11:32 PM, Cédric Jeanneret wrote: > > > On 08/02/2018 11:41 PM, Steve Baker wrote: >> >> >> On 02/08/18 13:03, Alex Schultz wrote: >>> On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya >>> wrote: On 7/6/18 7:02 PM, Ben Nemec wrote: > > > On 07/05/2018 01:23

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-08-02 Thread Cédric Jeanneret
On 08/02/2018 11:41 PM, Steve Baker wrote: > > > On 02/08/18 13:03, Alex Schultz wrote: >> On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya >> wrote: >>> On 7/6/18 7:02 PM, Ben Nemec wrote: On 07/05/2018 01:23 PM, Dan Prince wrote: > On Thu, 2018-07-05 at 14:13 -0400, James

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-08-02 Thread Steve Baker
On 02/08/18 13:03, Alex Schultz wrote: On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya wrote: On 7/6/18 7:02 PM, Ben Nemec wrote: On 07/05/2018 01:23 PM, Dan Prince wrote: On Thu, 2018-07-05 at 14:13 -0400, James Slagle wrote: I would almost rather see us organize the directories by

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-08-01 Thread Alex Schultz
On Mon, Jul 9, 2018 at 6:28 AM, Bogdan Dobrelya wrote: > On 7/6/18 7:02 PM, Ben Nemec wrote: >> >> >> >> On 07/05/2018 01:23 PM, Dan Prince wrote: >>> >>> On Thu, 2018-07-05 at 14:13 -0400, James Slagle wrote: I would almost rather see us organize the directories by service

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-07-09 Thread Bogdan Dobrelya
On 7/6/18 7:02 PM, Ben Nemec wrote: On 07/05/2018 01:23 PM, Dan Prince wrote: On Thu, 2018-07-05 at 14:13 -0400, James Slagle wrote: I would almost rather see us organize the directories by service name/project instead of implementation. Instead of: puppet/services/nova-api.yaml

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-07-06 Thread Ben Nemec
(adding the list back) On 07/06/2018 12:05 PM, Dan Prince wrote: On Fri, Jul 6, 2018 at 12:03 PM Ben Nemec wrote: On 07/05/2018 01:23 PM, Dan Prince wrote: On Thu, 2018-07-05 at 14:13 -0400, James Slagle wrote: I would almost rather see us organize the directories by service

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-07-06 Thread Ben Nemec
On 07/05/2018 01:23 PM, Dan Prince wrote: On Thu, 2018-07-05 at 14:13 -0400, James Slagle wrote: I would almost rather see us organize the directories by service name/project instead of implementation. Instead of: puppet/services/nova-api.yaml puppet/services/nova-conductor.yaml

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-07-06 Thread Cédric Jeanneret
[snip] > > I would almost rather see us organize the directories by service > name/project instead of implementation. > > Instead of: > > puppet/services/nova-api.yaml > puppet/services/nova-conductor.yaml > docker/services/nova-api.yaml > docker/services/nova-conductor.yaml > > We'd have: >

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-07-05 Thread Dan Prince
On Thu, 2018-07-05 at 14:13 -0400, James Slagle wrote: > > I would almost rather see us organize the directories by service > name/project instead of implementation. > > Instead of: > > puppet/services/nova-api.yaml > puppet/services/nova-conductor.yaml > docker/services/nova-api.yaml >

Re: [openstack-dev] [TripleO] easily identifying how services are configured

2018-07-05 Thread James Slagle
On Thu, Jul 5, 2018 at 1:50 PM, Dan Prince wrote: > Last week I was tinkering with my docker configuration a bit and was a > bit surprised that puppet/services/docker.yaml no longer used puppet to > configure the docker daemon. It now uses Ansible [1] which is very cool > but brings up the