-
Notifications
You must be signed in to change notification settings - Fork 5
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
Dtorresf/ch01s01 #3
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good job Diego! I tested the exercises. They work fine. I left mostly format and style comments.
Is this section meant to be somewhere else? I am checking the design doc for course 4 but the contents of this PR do not completely align with the document?
I am assuming this section is unit 1 / section 1 as specified in the Design Doc
You might also make it clear that although we are actually serving a model with Flask in the exercise, that is not considered part of the Model Serving feature.
Co-authored-by: Jaime Ramírez <[email protected]>
Co-authored-by: Jaime Ramírez <[email protected]>
Co-authored-by: Jaime Ramírez <[email protected]>
Co-authored-by: Jaime Ramírez <[email protected]>
Co-authored-by: Jaime Ramírez <[email protected]>
Co-authored-by: Jaime Ramírez <[email protected]>
Co-authored-by: Jaime Ramírez <[email protected]>
Co-authored-by: Jaime Ramírez <[email protected]>
Co-authored-by: Jaime Ramírez <[email protected]>
@diego-torres - please address review comments and push changes to same PR. |
@mamurak - please review this first section in model deployment course |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest you double check this with @rsriniva cause the main objective of this section is:
- Describe the concepts and terminology around model serving on RHODS
We can keep the "old-style" exercises to build that history line, that's a great idea actually.
However, we are still missing some of the terminology concepts in this section (e.g. what's a model server). Again, double check with @rsriniva .
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @diego-torres, thanks for creating this section draft!
I added a couple of comments, mostly minor formal ones. The two main recommendations I have are:
- moving the code to the course git repository to be checked out by the student as they're doing in the other parts of the course,
- building the container image directly on OpenShift based on the git import strategy.
See review comments for details.
Co-authored-by: Max Murakami <[email protected]>
Co-authored-by: Max Murakami <[email protected]>
Co-authored-by: Max Murakami <[email protected]>
Co-authored-by: Max Murakami <[email protected]>
Co-authored-by: Max Murakami <[email protected]>
Co-authored-by: Max Murakami <[email protected]>
@jramcast , in commit 3052a17, I am describing more concepts from the design document.
In the next section, while creating a model server with OpenVINO, will explain the options that are offered to configure service accounts that allow applications to authenticate to the model server, and how while creating the model server, there are options for the configured server sizes that can specify GPU. Please review and let me know if additional modifications are required for this PR to be approved. Thank you. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Let's get this merged
@mamurak - I think this PR requires your approval. Please check Diego's update |
Good job @diego-torres . The changes look good to me. I assume the next section to explain OpenVINO will go in a separate PR, right? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
OpenVino included here: #4 |
No description provided.