search

Tendrl / commons

Common code usable by all Tendrl components
http://www.tendrl.org
GNU Lesser General Public License v2.1
4 stars 23 forks source link

Profiling should be a separate job after the import flow completes. #1062

Closed anmolsachan closed 5 years ago

anmolsachan commented 5 years ago

Currently the profiling is done along with import flow. To reduce the time for the import flow, profiling can be triggered as a saperate job after the import finishes. The new profiling job should be tracked as a separate job from import and the user should be able to see the status of the job under the tasks menu.

Below is flow for the above process :

screenshot from 2018-10-11 14-11-33 ^^ During the import flow, the import flow tells user that there is job that is created for profiling and profiling information will be shown once the job is complete.

screenshot from 2018-10-11 14-12-08 ^^ The main dashboard will show profiling as "pending" and user can track the profiling job by clicking on it.

screenshot from 2018-10-11 14-11-28 ^^ The profiling job will be shown under tasks and user can see task details by clicking on it, similar to other jobs.

screenshot from 2018-10-11 14-37-46 ^^ Task Details

anmolsachan commented 5 years ago

@julienlim @mbukatov @nthomas-redhat @shtripat @GowthamShanmugam . Please review the above details.

anmolsachan commented 5 years ago

Related issues : https://github.com/Tendrl/api/issues/449 , https://github.com/Tendrl/gluster-integration/issues/702

anmolsachan commented 5 years ago

Closing this as a better way was found. Decided to keep profiling in the beginning of the import rather.