-
Notifications
You must be signed in to change notification settings - Fork 83
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
feat: add the model processor proposal #257
base: main
Are you sure you want to change the base?
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.
Thanks @chlins for authoring this proposal. Overall it looks good. The key aspects of the proposal make it appealing. My takeaways:
- This proposal brings AI models as first class citizen in Harbor. The user stories to use this CNAI model spec which follows OCI spec to surface AI model
- Uses existing OCI spec (artifactType and mediaType ) along with following CNAI model format https://github.com/CloudNativeAI/model-spec/blob/main/docs/spec.md
- No additional APIs needed as it leverages additions API - This is great
I left a comment regarding future model format changes and how new additions can be handled in generic way without requiring code changes. PTAL, I might be off as new to Harbor at code level, as long as we can handle such use case, its all looking good.
fc4e42c
to
6c82d47
Compare
|
||
## Architecture | ||
|
||
There will be a new AI model processor added to the artifact processors in Harbor core. |
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.
It's better to give details about how the new processor processes the data following the model spec into the Harbor artifact object which supports the related APIs shown in the API sections.
|---->[CONFIG]-
[model spec] ----> (processor)----> [artifact object] ------>(API)
|---->[LAYERS]-
Just for reference, I am using below
Below how
as opposed to
|
Signed-off-by: chlins <chlins.zhang@gmail.com>
6c82d47
to
11106e9
Compare
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
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
| 404 | layer with README characteristics not found | | ||
| 500 | internal server error(other runtime error or unexpected error) | | ||
|
||
`GET /api/v2.0/projects/{project_name}/repositories/{repository_name}/artifacts/{reference}/additions/readme` |
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.
should endpoint end in readme.md
, like for other processors?
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.
yes, it should be readme.md
.
We also should consider changing model name, reference here https://github.com/goharbor/harbor/pull/21663/files#r1967296025 "MODEL" -> "CNAI" for ArtifactTypeCNAI Harbor can have multiple ML model processors for different specs, having this "MODEL" is so general, it will look strange when other models specs processors will be added. |
Issue: goharbor/harbor#21229