New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Create Model Server redirects to Data Science Project Screen #1091
Comments
This flow is intended but maybe is misleading to the user, we might wanna review the description to make it more clear? |
@lucferbux Looking at my mockups I realize that I never addressed the scenario of what to show under Model Serving when no models are deployed. Rather than offering a Create model server action in this empty state, I think we should simply inform the user that no deployed models exist and re-direct them to the Projects page where they can create a model server and deploy a model. I'll mock something up to address this scenario. I think part of the confusion results from the nav item being called "Model serving" rather than "Deployed models", but that was edicted from on high. |
Great thanks! |
@vconzola Just want to follow up, is there any update on this issue about the mockup? |
@DaoDaoNoCode I think this is going to be addressed as part of bigger changes to Model serving to make it more consistent with Pipelines. Watch the recording of the 5/25 UX meeting to hear the details. |
@manaswinidas @DaoDaoNoCode Sorry. I created a mockup for this empty state and then never put a link in the issue. It should look like this: https://www.sketch.com/s/113593f8-5970-49d6-a352-709b07639127/a/uuid/00D5CBEB-9D5F-4886-BCB4-ECE815B2C991 @kaedward Please review the content for this empty state. |
Ok, I'm gonna take this issue, I'm starting with it but I probably raise the pr next week. |
@vconzola I reviewed the empty state but didn't update here, whoops |
Accidental merge -- PR is being reverted and ticket is reopened for the work to be reviewed. |
For future reference, here you have the right text: #1796 (comment) |
Is there an existing issue for this?
Current Behavior
When navigating to the
Model Serving
tab if I currently don't have a model server created it includes a button toCreate server
.When clicking that button, the page navigates to the
Data Science Projects
page with no additional context or information available:There is no clear "next steps" a user needs to take or any feedback provided to the user as to what they need to do. It is not clear that you must either create a project and then from that page create a model server or select a project and then create a model server.
There is no indication that a Model Server is a project scoped object and no indication that I need to create one in my project before I can server a model.
Expected Behavior
Instead of redirecting the user to the Data Science Projects page, pop up a modal just like with the option to
Deploy model
.Steps To Reproduce
See current behavior
Workaround (if any)
No response
What browsers are you seeing the problem on?
Chrome
Open Data Hub Version
1.5.0
Anything else
In all honestly the project / object scope workflow for the odh-dashboard makes very little sense to me.
Why can I create a
Deploy model
outside of theData Science Project
interface with a dropdown menu in the modal but I have to create the server under the Data Science Project menu?If a
Data Science Project
is a namespace/project proxy in the ODH/RHODS interface, why not fall back on the same navigation language as the OpenShift console.Provide a drop down menu to select which "project" you are in.
Allow the types of objects to be navigable items in the left panel:
If you really want to combine some of those things like Model servers and models on a single page that would still work since these pages aren't likely to be dense.
Each of these pages should only display the objects belonging to that specific project to clearly show the scope of those objects.
The text was updated successfully, but these errors were encountered: