GitLab

All calls take a request_user (of type AstakosUser) argument.

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

Remove quantity, import_limit, export_limit.
Update user-set-initial-quota management command.

- Remove presentation information from Service model (order, icon)
- To access the list of services filled with both presentation and api
  data use Service.catalog(). The method fills a dict with service
  identifiers and service metadata through the following steps
    - Initialize a service dict using
      astakos.im.presentation.service_defaults
    - Extend (merge and overwrite) it with the correspoding entry in
      astakos.im.presentation.SERVICES if exists.
    - Merge once again if user has set service metadata in
      ASTAKOS_SERVICE_META setting. This way user can change only the
      desired service parameters.

- An example of ASTAKOS_SERVICE_META containing keys which

    ASTAKOS_SERVICE_META = {
        'myservice': {
            'name': 'service_identifier',
            'url': 'https://service.url/service/ui/',
            'verbose_name': 'My service name',
            'order': 1,

            # cloudbar specific parameters
            'cloudbar': {
                'show': True,
                'title': 'My service name in cloudbar'
                # defaults to verbose_name
            },

            # dashboard specific parameters
            'dashboard': {
                'show': True,
                # we use different ordering in dashboard
                'order': 100,
                'description': 'My service description'
            }
        }
    }

- Updated dashboard to use Service.catalog() instead of hardcoded
  html.
- Updated service-* commands to keep up with model changes

- Remove foreign key dependency between Service/Resource model. Replace
  it with a service CharField to keep track of the service identifier
  that the resource was registered from.
- Remove all references to resource service name in resource lookups

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.

Register a service's resources giving option --json <file>.
The json file is expected to represent a dictionary with keys
"service" and "resources".

Currently the default base quota (uplimit) for each resource is read
from a configuration json file, given with --conf <file>. This file
represents a dictionary with numeric values for each resource name.

Upon importing the resources, the quotaholder has to be updated due to
the modified resource limits.

UI-related presentation data go to presentation.py.
Remove load_service_resources call and related astakos-init
management command.

Intention is to collect all quota-related code to a single file.

Adjust astakos code to the new nested dict structure of quotas.

Simplifications due to removal of quantity and merging capacity into holding.
Also make sure that holders and resources are represented as strings in
quotaholder calls.

Import directly quotaholder.callpoint in endpoint/qh.py
instead of an HTTP client.
Remove code related to entities, such as registering users and services.
Remove sync_projects logic.

Replace custom transaction context with:

- decorator `commit_on_success_strict', which uses
  transaction.commit_manually and ensures that
  the transaction rolls back on any exception

- context ExceptionHandler, which logs and
  suppresses exceptions

Do not display unnecessary message:
"Please use either `--from-file' or `--set-capacity' options"
while importing quotas from file.

An admin can modify a project, i.e. create an application based on
a previous application. We distinguish the initial applicant, called
the `owner', from the user who submitted the current application,
called the `applicant'.

Show owner instead of applicant in project-list: the applicant can
vary among applications for a single project, but owner is likely
to be unique.

Add field `response' in ProjectApplication model.
Add option `-m' in project-control command.

Refs #3493

Inform specifically which users, if any, have been synced, instead of
listing the whole diff. The latter can be recovered by giving the
option --verify.

Major authentication provider refactoring to support

- Modular and easily configurable messages with common context
- Fine grained provider policies to support appling specific policies to
  users and/or groups

Key points:

- Use auth_providers.AuthProvider instances where auth provider logic is
  needed. Instances get properly initialized with the available context
  (with no user/signup view, with user/login view, with user and
  identifier/profile view).

- All authentication provider messages are now accessed using the
  get_*_msg AuthProvider attributes.

- Provider policies logic is handled from  get_*_policy attributes.

- All provider messages may be overridden globally or per provider level from
  settings::

  # global change
  ASTAKOS_AUTH_PROVIDER_NOT_ACTIVE = 'Provider not active'

  # change only applies to shibboleth provider
  ASTAKOS_AUTH_PROVIDER_SHIBBOLETH_NOT_ACTIVE = 'Shibboleth is not  active'

- Provider policies may be overridden in settings::

  # ALL users wont be able to add shibboleth login method from their
  # profile
  AUTH_PROVIDER_SHIBBOLETH_ADD_POLICY = False

- New provider policies profile model added. Profiles can be assigned to
  a group or/and a specific user.

- All tests updated to match the auth providers changes.

- New management commands included

  * user-auth-policy-{add, list, remove, set, show}
    Manage authentication provider policy profiles.

  * user-group-{add, list}
    User group management commands

- Updated user-list to optionally display auth provider information

Print a message about astakos-quota calculating all user quotas,
which on a big system takes some time.

Refs #3389