GitLab

..to Archipelago, as 'origin_size' parameter.

Currently, the volume object is annotated with the size of the origin,
but this information is not stored in DB. This will have to be changed
when Synnefo supports detachable volumes.

* Add a setting in 20-snf-cyclades-app-api.conf to limit the number of
metadata items for volumes. The default value is set to 10.
* Add checks in volume create and update functions to enforce the above
setting.

Use validate_server_action() to make sure that the volume's reassignment
fails when another VM action is pending. For example, that you cannot
reassign a volume if the VM (and the volume) is being destroyed.

Get server with 'for_update' option when detaching a server's volume.

Check the length of the volume's name or description when updating the
volume.

Add 'CYCLADES_VOLUME_MAX_SIZE' setting to denote the maximum allowed
size for a Cyclades volume.

Store the image's version together with the image's UUID, in order to
track the exact image (Pithos file) that has been used for a server or
volume. This is required because Pithos files retain their UUID when the
file's data or metadata are updated. The (uuid, version) tuple is
required in order to fully determine the file that has been used.

Update 'volume' app to not allow cloning a volume, because it is
currently not supported by Archipelago.

Store the volume's index in the DB when creating a new volume.

Do not allow any "write" action to deleted (marked as deleted=True)
servers, networks and volumes. Only reading information about the
deleted resources is allowed.

Do not allow users to set 'delete_on_termination' to False, since,
currently, Cyclades do not support detached volumes.

Volumes can be reassigned through the volume API except for the system
volumes. These are reassigned as part of the VM they are attached to.

Allow specifying project when creating a new volume. On a VM creation, the
system volume is given the same project as the VM.

Create the API endpoint to list and show information about existing
volume types. Also, update the view to create a new volume to use the
'volume_type' attribute.

Replace usage of the stale 'disk_template' attribute of flavors and
volumes with the newly introduced volume type.

According to the decision of the GRNET Board of Directors,
switch license to GPLv3.

This commit will be propagated to the release
and master branches based on git flow, and the next
release will be licensed as GPLv3.

Create new management commands:

* snapshot-modify
* snapshot-show
* volume-modify

Also, fix various small issues in other commands.

When creating a volume from an image or snapshot we must check that
the image/snapshot is in 'AVAILABLE' status.

Also, rename 'checksum' to 'mapfile'.

Also check GANETI_CLONE_PROVIDERS.

Extend Cyclades POST /servers API endpoint to support specifying volumes
when creating a server. The call is extended with the
'block_device_mapping_v2' field that contains a list of dictionaries,
each of which contains the following information about the devices that
the server must have:

* source_type: One of'image', 'snapshot', 'volume' or 'blank'
* uuid: The UUID of the object that is specified by source_type (if
        source_type is not blank)
* size: The size of the volume
* delete_on_termination: Whether the volume will be preserved or
                         automaticaly deleted when the server is deleted

If no volume is specified, then a volume is automatically created with
the size of the flavor and with source the image that is specified in
the 'imageRef' field of the API call.

The follow restrictions apply:
* Source_type can be other than 'blank', only if the disk template is
  ext_ or if the volume is created as a root volume of a server, so
  it will be filled with data by snf-image.
* The root volume cannot be blank.
* In order to use a volume, it must be in AVAILABLE status. This will
  never happen until detachable volumes are implemented. However, the
  user can "clone" a user volume either by creating a new volume from
  cinder and then using this new volume, or by taking a snapshot and then
  use the snapshot as a source.
* The size field is required if the source is image, snapshot or blank.
  Also, the size of the volume must be equal or bigger from the source
  size (if any).

Finally, move some code from 'servers' module to 'server_attachments'
and 'commands' to avoid cyclic imports.

Implement 'attach_volume' and 'detach_volume' server actions. Also, add
'GANETI_MAX_DISKS_PER_INSTANCE' setting, to force a hard limit on the
maximum number of disks a server can have.

* Do not store source_{volume_id, image_id, snapshot_id} as seperate
  fields. Instead store them in the 'source' field, with a special prefix
  to indicate the source type.
* Add 'origin' field to Volume model to contain the origin that will be
  passed to Ganeti disk
* Check that 'source' option is used only for ext_* volumes
* Check that if a volume is used as source, the volume is in 'AVAILABLE'
  state
* Implement deleting a volume by detaching it from the corresponding
  server. Also, forbid detaching the root volume(index=0) of a server
* Rename 'hotplug' to 'hotplug_if_possible' in Ganeti methods.
* Rename 'name' and 'description' API attributes to 'display_name' and
  'display_description'

First implementation of volumes and snapshots.