GitLab

The quota policy plugin is responsible to query for overquota users,
if needed.

Delay the creation of user's system project until the user is accepted,
to avoid polluting the database with unneeded project objects.

There is a slight chance that a user UUID (to be used for a system project)
collides with an existing project UUID. In this case, one has to delete the
user and make a new one in its place.

Extend service_get_quota and service_get_project_quota in a backwards
compatible manner in order to support querying for multiple users or
projects.

- Include total quota help text for each resource.
- Two column layout for per user/total quota.
- Fixed owner formatters in template filters.
- Proper display of unset project application resources.
- Hide base projects by default. Include base project toggling action in
  projects list view.
- Set proper project name field validators for base project in
  project modifcation form.
- Improve visual highlighting of quota diffs
- Improve membership status messages
- Improved project filtering in project list/join views
- List all public/active projects in `join project` view.
- Handle unowned projects in projects modification form
- Display all project resources in project application summary view.
- Permit zero values in project application/modification form.
- Avoid modifcation of immutable base project fields in project modification
  view.
- Display project/application creation date to project admins.
- Remove user base project when a user gets removed.
- Convert ProjectForbidden exception to 403 http responses.
- Additional user access checks handling in project/app detail view.
- Let both applicant and project admins to dismiss a denied project
  application.
- Forbid project owner to act upon an admin project modification.
- Prevent POST requests in project modification detail view.
- Handle pending app quota per applicant
  When applying for a modification, the existing pending modifications,
  which will be replaced, may have been initiated by another user. We need
  thus to handle the astakos.pending_app resource per applicant.
- Introduce `related`, `active` mode in projects list api call
  Related mode returns all projects user owns or is has a related
  membership to. Active mode returns available public/active projects.

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.

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

- Update project views to work with the updated projects logic
- Use api.projects methods when applicable
- Common project view decorator
- Common view for app/project details

Add API call for a service to request the project quota for its own
resources.

Remove functionality from management commands `quota' and `user-modify'
for setting base quota. They will now be handled through projects.

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

Update quota code to take into account the differentiated sources.
There is no more need to lock the user when updating quota; locking
the project is now adequate.

Update quota listing in management commands; introduce option --quota in
project-show.

Restructure code to avoid an extra join and dict manipulations.

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

Add option `--all' in command user-modify to support setting base quota
for all users. Exceptions can be specified with `--exclude'.

Also select user for update in user-modify.

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

View the resource defaults as a skeleton to be consulted when accepting
a new user. All users keep their quota in AstakosUserQuota.

Operate resource-modify in bulk, in order to avoiding updating the
quotaholder separately for each resource.

Register new resources with unlimited quota.

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

Also, remove unneeded param of astakos_users_quotas.

A user is accepted if moderated=True and is_rejected=False. Only
accepted users have entries in the quotaholder.

Remove custom manager that implemented select_for_update(), since this
is already implemented in Django 1.4.

At some points, verified users where mistakenly assumed.

Applications now point to a project (rather than an extra model Chain).
A Project is created upon submitting an application; it always points to
a single `reference' application.

Model Chain is kept as a sequence to generate project ids.

Add field service_origin in model Resource as well as in the
resource definitions, indicating the service where the resource
comes from. It is not a foreign key, in order to allow deleting
a component/service, without affecting registered resources and
quota.

API call /service_quotas uses this field to identify relevant
resources.

Add model Component and migrate services along with their token
and UI URL to this new model. Rename service to component where
needed.

Add field service_type in Resource and fill it based on the name
of the service that used to own the resource.

Lock project's chain for every operation affecting either a project or
an application. Subsequently, lock user when needing to sync or to issue
commission to update pending_app quota.

In views, replace locking qh_add_pending_app with check_pending_app_quota,
which will only query quota, so that to respect the above mentioned order.

Order by id when locking multiple users.

Also add a missing import in quotas.py

Related to commit aee9a38

Also fix call of qh_sync_users in migration script.

When registering pending apps, catch only NoCapacityError. No other
QuotaholderError is expected and should not be treated here.

 - Split code that lists and syncs quotas
 - Merge the latter with qh_sync_users
 - Move qh_sync_projects in quotas.py; sync only active members
 - Add missing select for update in project suspend
 - Clean up quotas.py

To change base quota for a specified user:
  snf-manage user-modify user --set-base-quota resource limit

To import base quota in batch from a file:
  snf-manage astakos-quota --import-base-quota filename

Rename `initial' to `base quota' in command output.
Move code that creates/removes AstakosUserQuota entries in file quotas.py;
sync user to quotaholder after such a change.

Refs #3411

Unify these operations when registering a pending application,
in order to make sure no commission can be left pending.

In order to facilitate migrations.

Default to empty string