Define 389 DS Ansible structure for task execution implementation

[droideck]

As we've defined that the 389 DS configuration is done with Ansible Inventory and the associated with this module, we need similarly define how the 'single run' tasks will be implemented (memberOf fixup, cleanallruv, etc.)

In the result, they should be Ansible way complaint.
We also need to decide if a simple Role or Modules should be used. Or a combination of both.

• Investigate similar options of other projects’ Ansible implementations
• Write a design doc for future task implementation.

[droideck]

@progier389 if you don't mind and the work doesn't overlap with what you are doing, I'll work on that starting this week, before I get into other staff with the backup online task and such.

[progier389]

No problem ! Anyway you could work on the design without much risk of impacting my current PR, If we ends up to choose a solution with a module then we should sync, but the ds389_module architecture allows to easily add new functions that I think once the current work is merged or even partially merged, we will be ok.