Memcache Snapshots

Memcache Snapshots are point in time backups of a memcache instance. This class inherits from TopLevelResource and has direct access to the resource’s database object. The following attributes are directly accessible:

attr resource_id:
 The primary resource identifier that takes the form of a prefix followed by numbers and letters
attr organization_service_id:
 The ID of the parent organization service (cloud)
attr region_name:
 The region that the snapshot resides in
attr snapshot_id:
 The provider ID of the snapshot
attr name:The name of the volume
attr snapshot_type:
 The type of snapshot (manual vs automatic)
attr state:The current lifecycle state of the snapshot
attr availability_zone:
 The zone where the snapshot lives
attr create_time:
 The time when the snapshot creation was launched
attr port:The port that the database instance listens on
attr engine:The database engine that the instance was configured to use
attr engine_version:
 The engine version
attr size:The size in gigabytes of the volume
attr progress:The progress of the snapshot creation
class DivvyResource.Resources.memcachesnapshot.MemcacheSnapshot(resource_id)

Bases: DivvyResource.Resources.toplevelresource.TopLevelResource

Memcache instance snapshot operations

Delete this resource. If wrapped in a with JobQueue() block, this will queue the deletion job to the wrapped queue, otherwise it
calls immediately.

Retrieve the time from the provider that this resource was created (if available).

static get_db_class()
static get_provider_id_field()
static get_resource_type()

Retrieve the snapshot state

handle_resource_created(user_resource_id=None, project_resource_id=None)

This should be called when a resource is created/discovered after the basic data is added to the database. This gives an opportunity for post-addition hooks (assignment to groups, alerts, etc)


This should be called when a resource is destroyed before the basic data is removed from the database. This gives an opportunity for pre-destruction hooks (removal from projects/groups, alerts, etc)

handle_resource_modified(resource, *args, **kwargs)

This should be called when a resource is modified after the new data has been updated in the DB session This gives an opportunity for post-modification hooks

top_level_resource = True