GitLab

This reverts commit 23b41f6fefa1a066748810c4642e58e18a4b83f9.

Substitue pre_exec() and post_exec()

_lookup_container() locks the container path
but it was not called by some write backend methods
which expected the container path to be locked.

In those cases optionally _lookup_object() calls
the _lookup_container() in order to lock the container path.

Also lock the container path before container metadata updates
and container deletes.

This reverts commit 8a7ddfb0545348849d99fb686fec51659cbead58.

Select for update is not useful in case of account creation.
If there is no such account, 0 rows are returned
so there are no rows locked.

The new registration process of Astakos allows to verify the new
user's email before actually activating the user:

1. User signs up providing an email
2. A verification email is sent to the user (with verification link)
3. A corresponding message is shown on the Astakos web page
4. If the user follows the link he/she gets 'verified'
5. The new user is now verified=True, active=False
6. If moderation=False or the admin activates the user manually then
   the user gets verified=True, active=True and is granted access to
   the system

This commit changes the message on (3) to reflect the above changes.

VMs at building error that do not exist in Ganeti must not be reported
as stale. The VM is stale only if the user has asked to destroy the VM,
and so the action is DESTROY.

Make snf-ganeti-eventd send the NICs of the instance not only on
success, but also if the job has failed or has been canceled. Also,
update snf-dispatcher to handle those messages. This step is required to
clear BUILDING NICs that fail.

Create NICs in building state before enqueuing corresponding jobs to
Ganeti. This has already been done when creating the instance, but not
when connecting it to other networks.

Change 'index' field of NIC model to be optional, because the index of
building NICs is unknown. Also, change all API responses to return only
the active NICs.

Update the index page to refer to the new figure.
Keep the detailed view figure only on the Admin Guide.

Refs: #3745

Include the user images in the list of images that are matched against
the image name from the config file. Also, change config file to use
archipelago flavors and create instances from the SynnefoCI image.

Allow snf-ci script to accept a comma seperated list of commands to run.

Fix crash when request user is not logged in.
Add tests

:
Pithos uses a pool for the backend objects.
Pooled backend objects override the default close behavior
and return the object to the pool instead.
Therefore, django was unable to destroy the database
since there were active connections.
Therefore, we force the pool to shutdown before
the django attempts to destroy it.

Update postgresql default template ('template1'), to have LC_COLLATE='C'
and LC_CTYPE='C'. This is needed for test database that is created from
django, without the ability to set a different template.

Use the same regex as in the UI, which matches domain-name-like strings.

'type' attribute of reboot OS API call was directly mapped to the
'reboot_type' option of Ganeti reboot job. However these two are
semantically different. The 'SOFT' and 'HARD' reboot types of OS API are
mapped to 'shutdown_timeout' option of Ganeti jobs. However, setting
this option from Ganeti RAPI is not supported. Until implemented, we
will map both types to 'hard' ganeti reboot, and fallback to default
shutdown timeout of Ganeti (120s).

Also, modify UI to not set the 'HARD' reboot type and fallback to
default option of API which is 'SOFT'.

Fix passing of hotplug argument to GanetiRAPIClient, in case the
GANETI_USE_HOTPLUG is unset. If the Ganeti version does not support
hotplug, passing hotplug=False, will make the jobs fail at Ganeti opcode
validation. This commit fixes this by passing the argument, only when
the setting is set to True.

Turn off fsync, synchronous_commit and full_pages_writer to speed up
postgresql. DB is not no longer crash-safe, but this is no needed for
tests.

Also, introduce 'testing_vm' setting to distinquish between the type of
deployment. In cases like the above, we want to be able to configure the
server in a different way, whether is deployed for development/testing
or for production deployment.

Before writing to temp config file, acquire a lock
and re-read it's contents to make sure we don't
overwrite anything.