-
Notifications
You must be signed in to change notification settings - Fork 62
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
#289 - Add register, update and delete model group functionality to support Model Access Control #332
Merged
dhrubo-os
merged 52 commits into
opensearch-project:main
from
rawwar:kalyan/289-model-access-control-
Nov 13, 2023
Merged
#289 - Add register, update and delete model group functionality to support Model Access Control #332
Changes from 1 commit
Commits
Show all changes
52 commits
Select commit
Hold shift + click to select a range
a2ffe54
init
rawwar 7bef831
add search, delete and update
rawwar 61c3090
Merge branch 'main' of https://github.com/opensearch-project/opensear…
rawwar a89bb39
add tests for register model group
rawwar 3bbea93
update cluster to 2.11
rawwar ca765ec
test skipif
rawwar 4c6a7fd
fix
rawwar af60958
add tests
rawwar cde4e1f
update matrix
rawwar 28040ee
cancel in progress
rawwar d8fc9b2
update concurrency
rawwar cda4c08
job level concurrency
rawwar 1ebeb1a
fix
rawwar 1b72089
fix
rawwar e27daa3
fix tests
rawwar 7edafe9
tests passing
rawwar 2e0f9c4
isort fix
rawwar f9bc8c8
fix action
rawwar 24ea966
fix action
rawwar 84848e2
fix action
rawwar 08256f6
fix
rawwar 9547db3
update changelog
rawwar 06f097d
fix os dockerfile
rawwar 594baad
test
rawwar 203aa86
pass opensearch version
rawwar 19fdf80
fix
rawwar 6bdcfcd
fix
rawwar 76fcd84
fix
rawwar 50bacd4
update OS dockerfile
rawwar b5133b9
fix failing tests
rawwar 2b529a3
update dockerfile for 2.11.0
rawwar b61c1e3
remove disable warning
rawwar d5d5830
fix upload model
rawwar 8f46cf9
fix lint
rawwar d2f832e
fix lint
rawwar 286716e
Merge branch 'main' of https://github.com/opensearch-project/opensear…
rawwar 24cb85c
include reference
rawwar 078443f
pr fixes
rawwar c5cbde6
lint fix
rawwar c8dd748
fix lint
rawwar 05a42b2
fix tests
rawwar 4e47809
skip
rawwar bdf1201
fix lint
rawwar df6c069
fix lint and increase coverage
rawwar 62b5601
fix lint
rawwar 1993945
fix
rawwar 2c6b346
feedback fixes
rawwar 3b16fed
fix
rawwar d8479ff
lint fix
rawwar 99a3660
fix test cases
rawwar ba60da7
pr feedback fixes
rawwar 075a763
revert
rawwar File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
Any specific reason we are not validating all the exception cases while creating model group? Like the ones we have here: https://github.com/opensearch-project/ml-commons/blob/6efb1ebeefb8a7930f6767262457d0d5b568ac75/plugin/src/main/java/org/opensearch/ml/model/MLModelGroupManager.java#L148
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.
@rbhavna , since, these validations are already being done by ml-commons, having them here as well felt like double validations. Most checks I wrote here just check for type issues and helps to make a valid API call.
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.
Just curious, the three exception cases that we are testing here are also being validated by ml-commons. Any reason we still have them here and not the others?
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.
Right. I do feel we shouldn't be having these checks in
opensearch-py-ml
. Because, if checks onml-commons
change, we again need to update this on the client as well. I was thinking, client libraries only purpose would be to make the calls and if any errors from theopensearch
, it should be able to pass them to user without any change. Also, maybe add few utility functions to make things easier for the user.@dhrubo-os , @rbhavna , what do you think about removing these validations form
opensearch-py-ml
? Or Should I go ahead with implementing the validations fromml-commons
?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.
As
opensearch-py-ml
is a client plugin for ml-commons, we should have only the client side testing similar like any web application. Some basic input validations which can be easily caught before the request reaching to the server. We don't need to add that type of validations for which we need to make a back-end call like testing if the user is admin or not.Yeah we need to have the same basic validations in ml-commons too, as py-ml isn't the only client for ml-commons.