Understanding Storage Architecture
Understanding Storage Architecture
Administrators can define how Rosetta stores content on the various servers: Deposit, Staging, and Permanent. Administrators configure the following components separately for the Staging Server and the Permanent Repository:
- Storages, which are the storage areas. A storage can be a Network File System (NFS) or another type of data storage solution that Rosetta can access through HTTP requests (such as Amazon S3).
- Storage groups, which aggregate individual storages that contain similar types of data, such as metadata or intellectual entities (IEs).
- Because a storage group can contain multiple storages, Administrators configure storage group policies that define the storage to be used for each content object.
- Storage rules, which determine the storage group to be used. Each storage rule consists of the following parameters:
- Input parameters (such as content object type), with which the Rosetta system compares actual parameters of a content object
- Output parameters, which define the storage group to be used, if actual parameters of a content object match input parameters of the storage rule
The diagram below shows the organization of the storage components in the Rosetta system:
Storage Components
The information flow consists of the following stages:
- After a content object is moved from the Deposit Server to the Staging Server, the Rosetta system sequentially compares the actual content object parameters with the input parameters of the storage rules.
- When the content object parameters match the input parameters of a storage rule, the Rosetta system moves the object to the storage group, as defined in the output parameters of the storage rule.
- Within the storage group, the Rosetta system moves the object to a storage, as defined in the policy type.