GitLab

db464c6f introduced a bug: deleting holdings (and then bulk creating them)
interferes with locking; a thread that waits for holdings will not get
the deleted ones.

Revert to separate updating of holdings when issuing and resolving
commissions.

Check that holding exists before using it!

Update holdings and create provisions and log in bulk when issuing or
resolving commissions to speed up the operation,

According to the decision of the GRNET Board of Directors,
switch license to GPLv3.

This commit will be propagated to the release
and master branches based on git flow, and the next
release will be licensed as GPLv3.

Define __unicode__ in astakos models rather than __str__.

Update Copyright for files merged into develop in 2014 concerning the new
projects mechanism.

Make sure that issue_commission handles a single provision per (holder,
source, resource) tuple by merging similar provisions.

The API is responsible to provide valid data to the backend.

Also add option to delete project and user holdings that do not correspond
to actual astakos entities.

For efficiency reasons, commit 20c6de3 deletes and recreates holdings
instead of updating them one by one. In order not to exhaust the IDs, we
reuse the deleted ones.

When registering a new resource or updating base quota for a single
resource, compute and set holdings just for this resource.

Enable filtering quota by resource, over limit status, usage and
limit values.

Avoid stateful update of holdings when a resource limit changes; rather
recompute and set all affected users' quota.

Instead of updating every single holding, delete all after loading them,
then reinsert them updated with bulk_create.

Because migrating the timestamp fields of model ProvisionLog from string
to datetime takes too long, we keep them in string format.

Alter migrations 0005 through 0007 introduced in commit 164e64d.

Add commands `commission-list' and `commission-show' to display
pending commissions. The former supports option `--overdue' to
restrict the age of pending commissions.

Refs #3557

Add new fields issue_datetime in Commission and issue_datetime,
log_datetime in ProvisionLog. Migrate away from custom string-based
issue_time and log_time fields.

Order by primary key when selecting multiple holdings for update;
this most probably ensures that locking will happen in that order.

As per commit 2f90645, we select all holdings for the given holders,
rather that specifying all tuples (holder, source, resource), in order
to avoid query explosion.

Since negative usage makes no sense, we always check this lower
boundary when issuing a commission.

When resolving a pending commission, handle the case where the commission
has been issued with no provisions.

In order to facilitate migrations.

Avoid function call as a default value in model.

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.

Also remove unused `context' argument and replace empty list default
values with None.

It is the API code's task to transform the input dict to list.

Class structure is no more needed; there is no need for initialization,
since the code is used internally.

Do not update holding limit if there exist user-specific base quota
for the particular resource.

Make sure that no Commission or Provision entry is created when
issue_commission fails, even if the transaction is committed.

Using this parameter, the service can query the quotas of a specific
user.

Returns quotas for all resources associated with the service that makes
the call.

When changing the default base quota (uplimit) for a preexisting resource,
do a bulk update of the related holdings.
When importing a new resource, create the new related holdings.

Prompt the admin for the uplimit in the management command, if a config
file is not given.

Incorporate accept/reject functions in resolve_pending_commissions,
in order to enforce a total ordering on locking holdings.
Add a wrapper (resolve_pending_commission) that operates on a single
serial.

- {accept, reject}_commission take a single serial
- resolve_pending_commissions takes a set of serials to accept
  and a set of serials to reject
- commission exceptions record the provision on which they are raised
  and additional details
- issue_commission takes a new option `force': when True, the quotaholder
  will skip limit checks