File Storage and Storage Resources
Resources are external services that are used by Ooyala Flex to store, transfer or process media. Examples include storage devices, transcoder software, and file transfer technologies. Resources extend the core functionality of Ooyala Flex and enable it to scalably meet the demands of modern media management operations by utilising commodity technologies.
Note: A core aspect of media logistics involves orchestrating media files between various locations (storage) and processes (transcode, QC, etc).
Resource Definition Object Properties
A resource definition specifies a single resource. You can therefore link from a resource definition in the Settings section to the Resource Details screen in the Resources section (assuming you have the right permissions). You can also link from the resource details screen to the resource definition (assuming you have the right permissions).
|Scope||Account||The scoping of this object|
|Visibility||Whether the object supports visibility|
|Extended Config.||Whether the object has an extended configuration tab|
|Scripting||Whether the object can be configured using scripting|
|Enable / Disable||Whether the object can be enabled and disabled|
|Start / Stop||Whether the object can be started and stopped|
|Copy||Whether the object can be copied|
|Export / Import||Whether the object can be exported and imported|
|Delete||Whether the object can be deleted|
|Unique Name||Whether the object name must be unique within its scope|
|Variants||Whether the object supports Variants|
Creating a New Resource Definition
To create a resource definition, follow these steps:
1) On the toolbar, click the New option.
2) From the drop down, select Resource.
3) In the Create new Resource section, fill in the various details such as name, visibility, plugin, and so on.
4) Configure your resource definition: Once you've created your resource, select the Configuration sub-tab in order to define the values that you wish to assign to your new resource.
The resource types available are described in the Resource Plugins section.
Launching a Workflow from an Asset
Assets can be launched through a workflow in several ways in Ooyala Flex:
A) From the Action toolbar.
B) Selecting an inbox with an associated workflow as part of the transfer ingest process.
C) Associating a hot folder Resource to an inbox resource.
Once Ooyala Flex is connected to an external resource, the resource can be configured, monitored and managed through the Ooyala Flex console. In fact, in most cases, once connected to Ooyala Flex, all future management can be carried out through Ooyala Flex. Through regularly polling resources, Ooyala Flex is able to provide users with the ability to search and manage items within a resource, all from within the Ooyala Flex console.
Ooyala Flex offers a "pluggable" approach to resource management so that new resource types and vendor solutions can be added in future by developing new resource plugins. Ooyala Flex already plugs into the industry leading, storage, transcode and QC solutions. This approach means that Ooyala Flex offers a high degree of future-proofing as new networked media management technologies evolve. For example, Ooyala Flex can offer plugins for traditional network file storage or internet-based object storage.
Regardless of the resource type, all Ooyala Flex resources manage one or more items on behalf of Ooyala Flex. In the case of transcode resources, they are transcode job items, in the case of capacity resources, they are files that are being stored.
Resources manage one or many items. The exact item type is governed by the resource type. For example a storage type of resource will manage file items.
Run-Rule Expression Text Box for Resources
Process resources, such as package, inject, quality control, and extract resources support the use of run-rule expressions. Run-rule expressions can be applied by entering an expression in the run-rule expression text box which can be found in the Create a new Resource… section, when you are creating a new process resource. The Run-Rule Expression text box is only visible when a process resource is selected.
In the example below, you can see that an extract resource has been selected, and so, the Run-Rule Expression box is visible:
On the other hand, if another type of resource is selected, such as an inbox resource, then the Run-Rule Expression box is hidden, as shown below:
Note: The run-rule text box will be hidden by default.
Ooyala Flex supports 3 high-level resource types. These types are further sub-divided into more specific types. The high level type defines the general purpose of the resource:
• Capacity Resource: A resource that is used for storing media files such as a network mounted storage array, or cloud-based object storage, for example.
• Processing Resource: A resources that is used for processing media such as transcoders, for example.
• I/O Resource: A resource that is used for moving media files such as file delivery technologies for example.
Resources and Jobs
Many Ooyala Flex jobs rely on resources to get work done. For example transcode jobs delegate the work of transcoding a file to a transcode resource. If this is the case, there will be a link to the resource used in the Job Details screen for a job.
Like all Ooyala Flex objects, resources support the concept of visibility. When a job runs, it runs with an owner that is a Ooyala Flex user. Resources are only made available to jobs that have visibility of it. This means that resources can be shared between accounts where necessary but can also be isolated to individual accounts.
Resources can exist in one of the following states:
• Stopped: The resource is configured and enabled but stopped. It is not available to process job requests.
• Running: The resource is configured and enabled and running. It is available to process job requests.
• Failed: The resource is configured and enabled but failed. It is not available to process job requests.
Ooyala Flex takes a snapshot of the status of all resources and their associated items through polling. Ooyala Flex automatically polls all connected resources to both verify the continuing connection to the resource as well as to check for any updates from the resource’s items currently being managed. The frequency of polling may be configured by the administrative user.
If Ooyala Flex cannot obtain a valid response from a resource or the resource indicates that it has failed, Ooyala Flex sets the resource to a failed state. At this point, the resource cannot handle any future requests. Once a resource has failed it must be started manually by a Ooyala Flex user with the correct permissions.
Launching a Workflow via Hotfolder Resource Items
You can manually launch a workflow that is associated with a hotfolder resource item, by navigating to the resource item itself.
To do this, follow these steps:
1) Navigate to a hotfolder resource.
2) Click the Resource Items link, located in the top-right corner.
3) You will see a list of resource items associated with the hot folder resource. Locate the desired resource item.
4) Click the Chevron located to the right of the Workflow column, and click the Launch Workflow link.
Alternately, you can click the Launch Workflow button, located in the top-left of the Resource screen.