- 29 Apr, 2013 1 commit
-
-
Giorgos Korfiatis authored
Default to empty string
-
- 26 Apr, 2013 1 commit
-
-
Giorgos Korfiatis authored
- Rename 'pithos+' to 'pithos' - Prepend resource names with 'service_name.'
-
- 25 Apr, 2013 3 commits
-
-
Giorgos Korfiatis authored
Support issue_commission's `name' parameter for an optional description of the commission. Include this field in the dict returned by get_commission. Change astakosclient accordingly.
-
Giorgos Korfiatis authored
`snf-manage resource-import' does not provide a way to change the default base quota any more. When importing a resource for the first time, it sets the limit to zero. Use `snf-manage resource-modify' to change limits. It supports both interactive mode and reading limits from file, either for a specified resource or for all resources.
-
Giorgos Korfiatis authored
-
- 24 Apr, 2013 6 commits
-
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
Also remove unused `context' argument and replace empty list default values with None.
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
-
- 23 Apr, 2013 9 commits
-
-
Kostas Papadimitriou authored
-
Giorgos Korfiatis authored
-
Kostas Papadimitriou authored
importing setting names explicitly makes it hard to write tests that depend on specific setting values and polutes the module namespace. In this commit only settings that are currently used in tests where refactored.
-
Kostas Papadimitriou authored
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
So that it follows the naming scheme of other astakosclient calls.
-
Giorgos Korfiatis authored
Assume a resource `astakos.pending_app' related to service `astakos'. On submitting an application, issue a commission that will update the related counter if possible, and accept the commission on success. On approving/denying/cancelling an application, update the counter likewise. We always charge the application `owner'; however, if the `applicant' is a project admin, we issue commission in force mode which succeeds even if it exceeds the limit. In order to pre-emptively check in the UI, follow the same process in `dry run' mode, which issues a commission and rejects it on success. Remove option of user-update to set its limit. Refs #3349
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
It is the API code's task to transform the input dict to list.
-
- 22 Apr, 2013 15 commits
-
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
Class structure is no more needed; there is no need for initialization, since the code is used internally.
-
Giorgos Korfiatis authored
Also merge all migrations from 0026 to 0032.
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
All calls take a request_user (of type AstakosUser) argument.
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
-
Giorgos Korfiatis authored
Do not update holding limit if there exist user-specific base quota for the particular resource.
-
- 19 Apr, 2013 5 commits
-
-
Giorgos Korfiatis authored
Make sure that no Commission or Provision entry is created when issue_commission fails, even if the transaction is committed.
-
Kostas Papadimitriou authored
-
Giorgos Korfiatis authored
The following indicators are returned for each holding: "limit": the quota limit (as before) "usage": the current usage (pessimistically, includes any pending allocations) "pending": the difference of max and min allocation, indicates that there are pending commissions on this holding
-
Giorgos Korfiatis authored
Replace `available' by two fields: `limit' and `usage'.
-
Giorgos Korfiatis authored
-