About Container
Last updated
Last updated
Each container, viewed as a network folder, has a defined set of access rights for one or more users and/or user groups. Authentication and authorization can be managed locally, via Active Directory, or LDAP.
This solution implements quota and disk allocation settings to limit caching usage per container and global capacity.
The solution utilizes disk caching for fast data transactions. This caching system is flexible to fit various use cases and supports multiple types of disk systems. The storage spaces are accessible through NFS/SMB and the S3 protocol, where containers are treated as buckets with user access authentication.
Containers are storage spaces where end users can read, write, or modify files. These files are accessible over the network using standard transport protocols:
as a Network Shared Folder in using SMB protocol,
as a NFS Target in using NFS protocol,
as a Bucket in using S3 protocol.
The file virtualization layer manages files and file systems across different storage systems, creating an abstraction layer between file servers and the clients accessing them. Nodeum provides a logical representation of this file virtualization. Even if the file stored on a secondary storage, the user see the file, the user can retrieve it easily and the user keep the access to the data.
List and add new Container in the menu:
Data Container
Click on the '+' button and complete the information requested.
To configure the Rights and Privileges for each container, you have to select the action button on the right of the container line.
You can then define the permissions allowed to access the container. Possible permissions are: read/write, read-only or no access.
Select the user(s) and choose the authorization you require, for example :
Read/Write
Read Only
No access.
Finally, you can also define default privileges for the guest account.
If you have an application or server configured to store its data in S3. Nodeum can receive the data directly into a specific container.
To do this, you need to configure some parameters to enable communication between the application and Nodeum.
Here are the different steps to follow:
Create a specific user
Enable the S3 access for this User and Nodeum will generate automatically the Key id and Password you need to receive S3 data.
Create a container and give the privileges to the user you have just created above.
Remap the S3 policies for this newly created container.
| Description | |
|---|---|
Container Name
It is the name of the Container. The name is set at the creation and can't be changed. If you are looking to use it as S3 target please refer to the Specifications to follow the naming conventions.
Comment
This allows adding a description or comment.
Advanced Settings -> Automatic Push Data
To configure this option, you have to select a destination pool. When contents are written in the container, these contents will be automatically recopied to the selected destination storage.
Advanced Settings -> Cache Cleaning
Define a target secondary storage that will be used to offload contents stored in the cache. This will be activated only if the cache is full or reach the limit capacity defined.
Advanced Settings -> Protocol Activation
The 3 protocols (NFS - SMB - S3) are automatically available. Security is applied specifically to each section per protocol.
Quota
This quota specifies the maximum size of data that can be written to this container.
Cache resources allocation
Specifies (in percent) the size of the cache this container can use (0 is no limit).
