GitLab

Delete object used to create a new object version flagged as deleted
regarless of the status of the previous version.
However, delete requests of a deleted object
should return 404 (NOT FOUND) response.

* Log unicode arguments
* Do not log get_block return value (too long)

Enrolling a user sets its membership state directly to ACCEPTED, also
in case of REQUESTED.

Prefetch data in bulk queries in order to avoid continuously querying
the database.

Define function `reinstate' to re-activate a terminated project. If its
name is taken by another active project, it fails.

We need to make sure that the name to be approved is unique
among all non-terminated projects. We thus acquire a global
lock before approving.

Introduce model ProjectLog as well as fields in ProjectApplication
in order to record all actions.

As per 63bcab0, do not attempt to delete index when run on sqlite.

Record user who performed the action and optional reason.

Replace IOError and PermissionDenied with project-specific exceptions.

Ignore exceptions in custom _create_object and _update_object;
let the views handle exceptions and specify commit strategy.

Identify a membership by its id only.

Base tables on projects rather than applications; update templates.

Replace ProjectMembershipHistory with ProjectMembershipLog, which
records every state transition. Never delete any ProjectMembership
entry; set it instead to an appropriate state.

Submit a project modification by specifying a project id rather than
an application

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.

Fix order in Changelog between version 0.14.5 and 0.14next that has been
created by merging and automatic conflict resolution.

Also fix tpo in admin guide.

Conflicts:
	snf-pithos-backend/pithos/backends/modular.py
	version

Import settings from django.conf instead of synnefo.

Extend servers info API response with 'SNF:port_forwarding' attribute,
describing port fowarding rules (DNAT) that are applied to vms. The
description of such rules is done via the new CYCLADES_PORT_FORWARDING
setting. This setting can be either a dictionary mapping to ports to
tuples of (host, port), or a callable object that must return such a
tuple.   The caller will pass to the callable the following positional
arguments, in the following order:
* server_id: The ID of the VM in the DB
* ip_address: The IPv4 address of the public VM NIC
* fqdn: The FQDN of the VM
* user: The UUID of the owner of the VM