Manikandan R created YUNIKORN-1871:
--------------------------------------
Summary: Improving test coverage for whole user/group enforcement
feature
Key: YUNIKORN-1871
URL: https://issues.apache.org/jira/browse/YUNIKORN-1871
Project: Apache YuniKorn
Issue Type: Sub-task
Components: core - scheduler
Reporter: Manikandan R
Scope of this jira is to ensure unit tests has been covered for all the below
cases and add unit test for missing ones.
Validation:
1. Ensure user/group limits are within queue limits.
2. Ensure leaf queue user/group limits are within parent queue user/group limits
3. Config should have limits for 1 named group if limits are defined for wild
card groups.
4. Wild card user/group limit settings should be the last entry in the limit
object.
Specific user/group limits:
1. set user limits only and ensure it has been honoured.
2. set group limits only and ensure it has been honoured.
3. set both user & group limits and ensure it has been honoured.
3a) user limit is higher than group limit
3b) group limit is higher than user limit
4. Repeat the above for max resources and max applications individually and
together as well
Specific user/group limits + wild card user/group limits to ensure order of
precedence:
5. set user limit & wild card user limit only and ensure it has been honoured.
5a) When the user limit is specified, it should be considered for that specific
user
5b) When the user limit is not specified, the wild card user limit should be
considered for that specific user
6. set group limit & wild card group limit only and ensure it has been honoured.
6a) When the group limit is specified, it should be considered for that
specific group
6b) When the group limit is not specified, the wild card group limit should be
considered for that specific group
7. Repeat the above for max resources and max applications individually and
together as well
Wild card user/group limits:
8. set wild card user limit only and ensure it has been honoured.
- settings should be honoured by all active users.
9. set only 1 named group & wild card group limit only and ensure it has been
honoured.
- wild card group limit settings should be honoured by all users belonging to
either 1 unnamed or multiple unnamed different groups cumulatively. Named group
usage should not be considered for this calculation.
10. Repeat the above for max resources and max applications individually and
together as well
Headroom:
11. Only when there is no headroom for a specific user.
12. Only when there is no headroom for a specific group.
13. When there is no headroom for a specific user & group.
13a) When user headroom is higher than group headroom
13b) When group headroom is higher than user headroom
14. Repeat the above for max resources and max applications individually and
together as well
Config changes:
15. set user limit only and ensure it has been honoured. change the same user
limit settings and ensure the new config has been honoured.
16. set group limits only and ensure it has been honoured. change the same
group limit settings and ensure the new config has been honoured.
17. set user limit only and ensure it has been honoured. remove the user limit
settings, add new user limit and ensure the new config has been honoured.
18. set group limits only and ensure it has been honoured. remove the group
limit settings, add a new group limit and ensure the new config has been
honoured.
19. set user limit & wild card user limit only and ensure it has been honoured.
change the same user limit & wild card user settings and ensure the new config
has been honoured.
20. set group limit & wild card group limit only and ensure it has been
honoured. change the same group limit & wild card group settings and ensure the
new config has been honoured.
21. set group limit for more than 1 group (group A & group B) & wild card group
limit only and ensure it has been honoured. remove the group, group B. apply
config changes and ensure users of group B use wild card user group settings.
also do some activities by users of another group, say group C. Ensure users of
both group B and group C should not exceed the wild card group quota
cumulatively, whereas users of group A should not exceed group A quota.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
