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
[feature] Support Model Conversion/Compression via CRD #23
Comments
BTW, we can use Harbor Webhooks to trigger model analyzer: https://goharbor.io/docs/2.0.0/working-with-projects/project-configuration/configure-webhooks/ |
/priority p2 |
what's the status? @simon-cj Can we have a WIP or design doc first? (e.g. I want to know why do we need CRD for this...) |
The CRD is to avoid self-maintained queue in the implementation.https://docs.google.com/document/d/1JyjCzpO0NrsIOK29i_b2vTPpYc6-ckNcCVquOCj2ooM/edit?ts=5ec22fe9#heading=h.6j6pdsfmko7y |
CRD design doc is provided by gaocegege, recently, I‘am updating extrat and
convert python script and verify logic by ormb. so, the crd controller is
simple now, I will complete next.
…On Tue, Jun 16, 2020 at 10:46 AM Ce Gao ***@***.***> wrote:
The CRD is to avoid self-maintained queue in the implementation.
https://docs.google.com/document/d/1JyjCzpO0NrsIOK29i_b2vTPpYc6-ckNcCVquOCj2ooM/edit?ts=5ec22fe9#heading=h.6j6pdsfmko7y
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEIXG3YIGTJTBSPATJ2JNYLRW3MIRANCNFSM4NSQJONQ>
.
|
IIUC, the CRD design should be part of model-registry, not part of ormb. Are we going to create a new repository or work in ormb directly but create a new component?
|
Depends on the scope of ormb. We can discuss it on the meeting. |
for "the CRD design should be part of model-registry“, emmm, SGTM.
the second question need to discuss, @高策 <gaoce@caicloud.io> suggest work
in ormb directly last time.
…On Tue, Jun 16, 2020 at 11:33 AM Deyuan Deng ***@***.***> wrote:
IIUC, the CRD design should be part of model-registry, not part of ormb.
Are we going to create a new repository or work in ormb directly but create
a new component?
The CRD is to avoid self-maintained queue in the implementation.
https://docs.google.com/document/d/1JyjCzpO0NrsIOK29i_b2vTPpYc6-ckNcCVquOCj2ooM/edit?ts=5ec22fe9#heading=h.6j6pdsfmko7y
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#23 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEIXG32FSV5DHLCR3M6DY4DRW3R2BANCNFSM4NSQJONQ>
.
|
LGTM @simon-cj you are mixing Half-width & Full-width punctuation marks :)
|
Is this a BUG REPORT or FEATURE REQUEST?:
What happened:
We should support model conversion and compression. We can have a init container to pull the model from registry to local filesystem. Then we can use MMdnn or other tools to convert/compress the model, then we can push the new model with the unique tag or the desired tag.
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
https://github.com/gaocegege/ormb/tree/modeljob
The text was updated successfully, but these errors were encountered: