feat: Display kernel-pull-progress

[youngjun0627]

backend.ai-issue#227

Client (Python & Javascript) Task

• Check the existence of the task ID in the create-kernel API response.

• If it exists, show a progress bar reflecting its progress stream.

Using response from manager, client obtains background-task pulling kernel and displays progress bar reflecting kernel-pulling. But, I do request twice.

• From first request, client obtains kernel_id and background task.

• From second request, client gets all the information from existed session.

But, I think we need another way to get all the information(contains background-task id) from manager with a single request.

[achimnol]

Check out the comment in lablup/backend.ai-manager#477.

[achimnol]

The client.func module provides a set of functional API wrappers while client.cli module provides the CLI-specific argument parsing and outputs.
So, could we move the invocation to tqdm to the cli module? Of course, the bgtask handling routines must stay here, so we need something like "reporter" interface as in the manager to separate the console output handling and the abstract bgtask handling.

[codecov]

Codecov Report

Merging #181 (b4520c3) into main (b6a2bd9) will decrease coverage by 0.12%.
The diff coverage is 18.18%.

❗ Current head b4520c3 differs from pull request most recent head b93a492. Consider uploading reports for the commit b93a492 to get more accurate results

@@            Coverage Diff             @@
##             main     #181      +/-   ##
==========================================
- Coverage   45.46%   45.34%   -0.13%     
==========================================
  Files          74       74              
  Lines        6801     6815      +14     
==========================================
- Hits         3092     3090       -2     
- Misses       3709     3725      +16     

Impacted Files	Coverage Δ
src/ai/backend/client/func/session.py	42.06% <18.18%> (-2.32%)	⬇️
src/ai/backend/client/cli/params.py	39.47% <0.00%> (+0.34%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b6a2bd9...b93a492. Read the comment docs.

[youngjun0627]

When status of the ComputeSession is 'TIMEOUT' or 'PENDING', client prints the info(logs) and return in current code. So, will I implement the code by your feedback in this situations?

[achimnol]

When status of the ComputeSession is 'TIMEOUT' or 'PENDING', client prints the info(logs) and return in current code. So, will I implement the code by your feedback in this situations?

Yes, there was no way to keep track of the kernel preparation process before, so we just printed a messaged and exited.
Now let it use the bgtask API to show the progress and preparation status afterwards upon TIMEOUT or PENDING.

[youngjun0627]

• idea

1. func/session.py
   Check if the response from manager has 'background_task' key. If True, the Compute-Session has a attribute 'backgroundtask' and is returned.
2. cli/run.py
   When the compute-session' status is 'TIMEOUT' or 'PENDING', display the progress using bgtask-handler. And if background task is done, the compute-session calls 'get_or_created' method containing two arguments 'image', 'name' to get(update?) its attributions.

But, by your comment, background task handler stays func/session.py and the reporter attribution is added to compute-session? I tried it but in this case, get_or_create method returns after background task is finished. Do I misunderstand?