Synnefo

Advances in syncing quotaholder with astakos

Factor out trigger_sync() as lock_sync() to be used for other
sync processes in addition to sync_projects().
Implement sync_users(), which registers users and their quotas.
Use both sync processes in astakos-qh-sync management command.

Fix messages

Optimize project-list query

Note that select_related() does not automatically bring
`related_name's, such as ProjectApplication.project.
Need to specify select_related('project'), which brings
`project' (but not `owner', or other related field).

Fix bug in user-set-initial-quota command

Include uuid in user-details command output

Changes in registering to quotaholder

Add an 'uplimit' (default) field in Resource;
change AstakosUserQuota fields to IntDecimalField;
pass all four limits of initial quotas to the quotaholder;
register services and resources explicitly upon creation;
a wrapper for get_quota.

Change projects, eliminate development migrations

Change Project's state field and ProjectMembershipHistory's person field;
replace all migrations starting 0015 with a single new one.

Need to check for missing data migrations.

Provide commands for importing/exporting existing user resource policies

astakos-qh-sync: skip email-unverified users

Astakos-qh-sync will create quotas for all eligible users.
Users that have unverified emails are not considered eligible.
When users are activated by an admin via user-update --set-active,
their email is also marked as verified, therefore they become eligible.

Service management commands update

- New service-update command
- service-list now displays service order field

Project deactivation/termination

Fix user details command

Delete more obsolete code

Fix activation_sent assignment in user update

Fix models

Single model for ProjectApplication & Definition - Membership sync

User state fixes

- Never reset activation_sent date
- Check for inactive users too for email/username uniqueness
- Check both email/username uniquness in user creation process
- Activated users should have both email_verified/activation_sent fields
set

Allow follower application with same deifinition name approvement

Project Notifications

Manual transaction management in project application approve command

Progress VI

whitespace tab fix

Extend/Update management commands

Case insensitive email checks

#2883

Merge remote-tracking branch 'origin/0.12' into devel-0.13

Conflicts:
snf-astakos-app/astakos/im/activation_backends.py
snf-astakos-app/astakos/im/api/admin.py
snf-astakos-app/astakos/im/auth_backends.py
snf-astakos-app/astakos/im/forms.py
snf-astakos-app/astakos/im/functions.py...

Fix type in group list command

Fix ordering in snf-manage listing commands

Fixes

Fix management commands

Merged demo

View and management commands for adding/removing user resource quota

Refs: #2793

Rename management commands

Remove email validation

Register resources in quota holder

AstakosUser signed_terms property instead of function

Progress VIII

• integration with quota holder
• new credit event for integration with aquarium

set default group in newly created users

Progress VII

• add policies during group creation
• improve performance (reduce db access)

Progress VI

rename management commands

rename management commands

rename management commands

Display service token in listservices command

Register the date a user activation email sent and reset it when the user becomes active (for future use)

• epoch: signifies the user has been created before adding the specific field (so we have no actually information whether an activation email has been sent or not)...

Provide an API call for the service clients to send user feedback

• new model Service
• new management commands for handling the services
• remove ASTAKOS_CLOUD_SERVICES setting
• change get_services API call to return
  the Service objects
• separate admin from service API calls...

change showuser command: do not show date_signed_terms if there are no terms to sign

snf-manage commands: do not send activation email in active users & do not allow inactive users to send invitations

ask acknowledgment for switching local account to shibboleth one

• unique email and is_active combination (use django model validation)
• use different template for rendering shibboleth signup form
• do not show groups in profile page
• do not show provider in third-party signup forms...

add support for groups

createuser command: validate email