Skip to content
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

The Edge PoC should be based on some standard Open Data Hub demo / training #136

Open
adelton opened this issue Oct 9, 2023 · 2 comments
Labels
help wanted Extra attention is needed kind/documentation Improvements or additions to documentation kind/question Further information is requested priority/high Important issue that needs to be resolved asap. Releases should not have too many o

Comments

@adelton
Copy link
Contributor

adelton commented Oct 9, 2023

The https://github.com/opendatahub-io/ai-edge contains a PoC of setup that in the https://github.com/opendatahub-io/ai-edge/tree/main/pipelines part works primarily with the two models, builds container images, and does some "GitOps" actions.

The ACM part then shows extending exployment of these models as applications to ACM-managed clusters, a.k.a. near edge.

We have a couple of issues filed to extend the matrix of use-cases, for example #57 ... but for things that extend the non-ACM part of the PoC, shouldn't we either use existing Open Data Hub demos / training paths / example repos, or turn the majority of the pipelines part into one? Aren't we duplicating efforts?

If we used and contributed to an existing demo / training repo / example repo for the basic model handling, we would help improve example for people who do not necessarily care about edge, and this repo could then be a fork or an addition to the base one, focusing on the actual edge parts.

@piotrpdev piotrpdev added help wanted Extra attention is needed kind/documentation Improvements or additions to documentation kind/question Further information is requested priority/high Important issue that needs to be resolved asap. Releases should not have too many o labels Oct 9, 2023
@LaVLaS
Copy link
Contributor

LaVLaS commented Oct 11, 2023

I completely agree that we should be reusing existing demos and training paths for edge use cases as a form of dogfooding our own materials AND ensuring that the entire workflow stays relevant.

If we used and contributed to an existing demo / training repo / example repo for the basic model handling, we would help improve example for people who do not necessarily care about edge

IMO, we should be including edge use case in the same location as "existing demo / training repo / example repo for the basid model handling" to ensure that anyone learning about ODH can learn how to do basic model handling and/or distributed model handling (Edge). One the discoveries from the PoC are included as features in the ODH components the workflows for basic & distributed model handling should share the same user experience

@adelton
Copy link
Contributor Author

adelton commented Oct 11, 2023

IMO, we should be including edge use case in the same location as "existing demo / training repo / example repo for the basid model handling" to ensure that anyone learning about ODH can learn how to do basic model handling and/or distributed model handling (Edge). One the discoveries from the PoC are included as features in the ODH components the workflows for basic & distributed model handling should share the same user experience

Once we consider the approach stable, with CI and other stuff, sure, let's offer it to the "upstream" demo / repo. But currently we have a bunch of unresolved bigs and high priority issues opened, and it would not be fair to polute the existing demo / repo with something that generates a high churn and has a high maintenance cost.

We can eventually merge the Edge cases in completely, but that shouldn't be the primary goal of this issue. Here I would propose to focus on finding what existing ODH demos there are and how to build on top of them first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed kind/documentation Improvements or additions to documentation kind/question Further information is requested priority/high Important issue that needs to be resolved asap. Releases should not have too many o
Projects
None yet
Development

No branches or pull requests

3 participants