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

[feature] Support README as a addition layer #102

Open
gaocegege opened this issue Aug 5, 2020 · 1 comment
Open

[feature] Support README as a addition layer #102

gaocegege opened this issue Aug 5, 2020 · 1 comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/P2 Must be staffed and worked on either currently, or very soon, ideally in time for the next release.

Comments

@gaocegege
Copy link
Member

Is this a BUG REPORT or FEATURE REQUEST?:

Uncomment only one, leave it on its own line:

/kind bug
/kind feature

What happened:

When we save the model, we just save the model itself. We can add a new content layer for README. When we export the model, we export the model to ./model and README to ..

/kind feature
/priority p2

What you expected to happen:

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know?:

@caicloud-bot caicloud-bot added kind/feature Categorizes issue or PR as related to a new feature. priority/P2 Must be staffed and worked on either currently, or very soon, ideally in time for the next release. labels Aug 5, 2020
@gaocegege
Copy link
Member Author

gaocegege commented Aug 5, 2020

It is also related to Harbor. Harbor 2.1 does not support the addition layer for user-defined artifact. We need to implement the feature post 2.1

Just like Helm Chart, each model should have its README to illustrate what the model is and how to use it. We should have a separate layer to store such the info and show it in UI.

We can use Harbor Addition mechanism to support it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature. priority/P2 Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Projects
None yet
Development

No branches or pull requests

2 participants