Hello folks, While working on the service flattening in t-h-t, I have some question regarding the pacemaker things. If we take rabbitmq: - we have rabbitmq things in docker/services - we have rabbitmq things in puppet/services - we have rabbitmq things in docker/services/pacemaker - we have rabbitmq things in puppet/services/pacemaker If the plain services are easy to flatten, the pacemaker part is more annoying, at least on the naming/location. I see the following possibilities: - create a deployment/pacemaker and move all pacemaker-related things in there - name files something like rabbitmq-pacemaker-foo.yaml and push them in deployment/rabbitmq Both look valid. And both might have their downsides. Any advice, idea, feeling on that? Also, regarding the workflow: do we do that flattening in one, or two passes? i.e. we can move all rabbitmq related code at once, or only the plain service, and do a second patch for the pacemaker things. Here again, both look valid, but I'm more in the "2 passes" idea. So... yeah, I'd like to get some feedback on that in order to do things right, and avoid monkey-patching because paths/naming aren't good ;). Thanks! Cheers, C. -- Cédric Jeanneret Software Engineer DFG:DF