Dumb question re orchestrating the starting and stopping of tiered services with ordering dependencies:
Imagine tier A depends on tier B. To bring up the app, start B then A. To bring it down, stop A then B. I can't figure out whether it's possible to represent these relationships using roles without having to basically duplicate things so there is an A-stop role, a A-start role, a B-stop role, and a B-start role. Have gotten close to figuring it out using start/stop tags, but can't model to opposite ordering dependencies between start and stop. Anyone else come up with an efficient reusable way to model this use case? -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/fee39d00-8c4f-4daf-b4eb-a02d5d4956ec%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
