GitLab

Notify applicant on an application action; notify project owner on project
actions if owner exists.

GetQuotas now returns a dictionary with the project's uuids as keys.
This patch changes burnin to support that.

Assume base project when reconciling astakos resources.

Take projects into account when computing resource usage and comparing
with the quotaholder values.

Generalize the checks operated during resource reconciliation so that they
can be used in all Synnefo components.

Adapt checks for user/project limits, include checks for project limits.

Use --filter-by to filter by owner and name.

Refs #5014

Pass all related fields in a single call, because select_related does not
chain as expected (yet). See https://code.djangoproject.com/ticket/16855

Also pass prefetch_related in a uniform way.

return only resources that are related to projects the user has active
membership to.

- 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

Remove get application calls and set application_action to post to the
project endpoint.

Take project into account when checking and enforcing quota violations. Add
option to restrict check to a certain project.

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

Add support in resource-modify for changing the project_default.

Remove interactive operations, rename default-quota to base-default.

Report quota change when moving across accounts or across containers
assigned to different projects.

Introduce ``project`` container policy. The value of this policy denotes
the project from which the container quota originate.

Further changes:
* domain argument in get_{account|container|object}_meta backend methods
  has become optional unless user defined metadata are requested
* the pithos frontend does not query anymore the astakosclient
  for the account usage; this is handled by the backend methods

Add API calls to assign a VM, network, or floating IP to a new project.

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.

Add a management command that directly modifies an initialized project.

Since a user can now specify the project where a resource is assigned,
user-provided data do reach the quotaholder. A NotFound response is
thus not necessarily an internal error; the user may just not be a
member of the input project. Query the quotaholder to find out whether
this is the case and, if so, raise BadRequest.

Add optional parameter `project' in API calls that create VMs, networks,
and floating IPs. If missing, user's base project is assumed (same uuid
as the user).

Add issue_commission wrapper for assigning resources to a new project.

Both issue_one_commission and the new call issue_commission_generic act
as wrappers on top of _issue_commission. They create the appropriate
project-level provisions, based on the original ones provided by the
astakosclient user.

Add field `project' and initialize it to `userid' for all VMs, networks and
floating IPs. This means that all resources are assigned to the owner's base
project.

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.

Recreate quota holdings for all initialized projects and memberships.

Add flag `initialized' on ProjectMembership. It is set to true once a user
is accepted. It is used to distinguish users that have registered
project quota (but may have been removed since then).

Make base project along with the user with the same uuid. Enable the
project upon user acceptance.

Every user is associated with a special-purpose `base' project. Its
mission is to manage the user's base quota.

Field project_capacity now requires a value; field project_application
was mistakenly set nullable.

A project entry will contain all information needed to operate a project.
An application will store just the information provided by the applicant.