Notebook Listing Page - Resources

[ronaldpetty]

/kind feature

Why you need this feature:

The listed resource are misleading (a little). When creating a notebook, the "minimum" is actually both minimum and maximum because its listed as request and limits just the same (for notebook resource). I think a few items regarding resources could be useful to know what is be being used by notebooks (versus using other tools to figure it out).

Describe the solution you'd like:

• Add ability to set limit and request separately for notebooks
• From a k8s "resources" view in notebook resources - show both limit and request
• Add volume listing to notebooks (workspace and data)
• add summation of resources per notebook and per all notebooks (I assume for that namespace)

Also related to resource tracking. If a notebook resource becomes a pod resource, maybe tie the names a little more.

~$ kubectl get notebooks.kubeflow.org -A
NAMESPACE   NAME    AGE
team-1      test1   11m

~$ kubectl get pods -n team-1
NAME                                               READY   STATUS    RESTARTS      AGE
ml-pipeline-ui-artifact-789d54d746-qf4r6           2/2     Running   2 (25h ago)   46h
ml-pipeline-visualizationserver-6659778c46-nw5g9   2/2     Running   2 (25h ago)   46h
test1-0                                            2/2     Running   0             10m

The test1-0 pod I believe is the notebook, but the name format is different and unclear how it ties back to that one notebook. (also don't know if the pipelines are involved here, so same issue if they are, labels don't relate them clearly to me).

Keep up the good work!

[ronaldpetty]

Related to last part on names/labels. I noticed in the "EVENTS" of the notebook, it didn't list the pods that were from the stateful set. I would think the entire chain from notebook->statefulset->pod<-pvc would be a good list. I was looking for where the PVCs where actually mounted (obvious now, but unclear on first read of guide as it doesn't mention mount point).

[andreyvelich]

/transfer notebooks

[google-oss-prow]

@ronaldpetty: The label(s) kind/feature cannot be applied, because the repository doesn't have them.

In response to this:

/kind feature

Why you need this feature:

The listed resource are misleading (a little). When creating a notebook, the "minimum" is actually both minimum and maximum because its listed as request and limits just the same (for notebook resource). I think a few items regarding resources could be useful to know what is be being used by notebooks (versus using other tools to figure it out).

Describe the solution you'd like:

• Add ability to set limit and request separately for notebooks
• From a k8s "resources" view in notebook resources - show both limit and request
• Add volume listing to notebooks (workspace and data)
• add summation of resources per notebook and per all notebooks (I assume for that namespace)

Also related to resource tracking. If a notebook resource becomes a pod resource, maybe tie the names a little more.

~$ kubectl get notebooks.kubeflow.org -A
NAMESPACE   NAME    AGE
team-1      test1   11m

~$ kubectl get pods -n team-1
NAME                                               READY   STATUS    RESTARTS      AGE
ml-pipeline-ui-artifact-789d54d746-qf4r6           2/2     Running   2 (25h ago)   46h
ml-pipeline-visualizationserver-6659778c46-nw5g9   2/2     Running   2 (25h ago)   46h
test1-0                                            2/2     Running   0             10m

The test1-0 pod I believe is the notebook, but the name format is different and unclear how it ties back to that one notebook. (also don't know if the pipelines are involved here, so same issue if they are, labels don't relate them clearly to me).

Keep up the good work!

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed if no further activity occurs.
Thank you for your contributions.

Members may comment /lifecycle frozen to prevent this issue from being marked as stale.