Shared File System

Shared File Systems are scalable volumes that can be shared with multiple instances. This class inherits from TopLevelResource and has direct access to the resource’s database object. The following attributes are directly accessible:

attr organization_service_id:
 The ID of the parent organization service (cloud)
attr region_name:
 The region that this file system resides in
attr file_system_id:
 The provider ID of the file system
attr name:The name of this shared file system
attr creation_timestamp:
 The time when this file system was created
attr number_of_mount_targets:
 Number of mount targets for this file system
attr metered_size:
 The sum of the sizes of all this file systems current objects
attr creation_token:
 Token that was generated or chosen when this file system was created
attr encrypted:Denotes if this file system is encrypted or not
attr encryption_id:
 The provider ID of the encryption for this file system
attr lifecycle_state:
 State of this file system (eg. creating, available, deleting, deleted, unknown)
attr performance_mode:
 The performance mode of this file system (eg. generalPurpose, maxIO)
class DivvyResource.Resources.sharedfilesystem.SharedFileSystem(resource_id)

Bases: DivvyResource.Resources.toplevelresource.TopLevelResource

Shared File System operations


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

static get_db_class()
static get_provider_id_field()

Retrieve dependencies for particular resources

static get_resource_type()
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 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