Skip to content
GitLab
Closed
Issue created by dockx thibault@tdockxMaintainer

[ORCHESTRATOR] - Supann life cycle - automation via Orchestrator

The goal of this issue is to develop an automatism being able to manage supannRessourceEtat, the expiry of accounts and their related behavior upon other plugins such as mail. (Partage / Zimbra).

The following steps must be taken into consideration. (OBSOLETE) Please confer to the simple design document that can be found here : Cycle_de_vie_-development-design_document__DRAFT_.odt

Note that this document is subject to update and is definitely not in its final form

BELOW contains historical design - some content is obsolete - see above design document

  1. In the tasks classes of Orchestrator, add a method to retrieve tasks that are set to be redundant and return it. (getTasks() methods without granular filter).
  2. Verify the last moment of execution and the schedule date, if scheduleDate < time() then if lastExec is < time() - "redundantOptions" trigger web service call to activate sub-tasks.
  • A new class could be developed to manage the web service call towards FusionDirectory. The idea is to be able to click on "executeNow" the daily task in order to have a trace of the execution of that daily task.
  • A possible addition to the env file will be required to get all the info related to the web service secure connection
  1. In case any sub endpoints of tasks are being triggered, it is wise to first go through the redundant tasks by default and trigger the related tasks.
  2. In case of endpoins tasks/supann :
  • as said above, trigger redundant tasks, even if not supann.
  • only retrieve the subTasks (method getTasks() ) which contains the objectType tasksSupann.
  • Any tasks of objectType supann witch are listed, verify the schedule date for that granularTasks (Can be a generic method being used here)
  • Verify the “behavior” set in the backend of configuration of FusionDirectory to retrieve what needs to be done.
  • Update the DN based on the behavior, see example below. (Account A -> I/S && Mail A -> I/S) etc.
  • Create as well a granular task (cn=time()+name of main tasks) related to the main task supannTask to have a trace of what happened. (SupannStatus X changed to Y) with status (2 - completed).
  • A documentation on how Orchestrator works to handle this life cycle is required.
Edited by dockx thibault