Container Configuration


Nodeum provides a logical representation of files virtualization.

This defines an abstraction layer between file servers and the clients that access those file servers.

The file virtualization layer manages files and file systems across different storages.

This file system is reachable through the network with standard transport protocols such as NFS, SMB and S3.

About Container

Containers are storage space where the end user can access to read, write or modify any files.

These spaces are accessible through NFS/SMB and through S3 protocol ; in this case the containers are seen as a bucket with a user access authentication.

The solution used disk caching which allows fast access for all data transactions. This caching definition is flexible to fit into your use case. We support several types of disk system to define this cache.

The container, which is seen as network folder, has set of access rights defined for one or more users and/or groups of users. The authentication and authorization can be managed locally, with Active Directory or with LDAP.

Quota and disk allocation are settings to limit caching usage per container and global capacity.

In summary

Containers are the point of access for data stored behind Active Archive workflow.

  • Containers use the local Nodeum Disk Caching system when data are copied.

  • Each container allows privilege management. Users & Groups access permissions configuration can be set for each container.

Containers are accessible :

  • as a Network Shared Folder in using SMB protocol,

  • as a NFS Target in using NFS protocol,

  • as a Bucket in using S3 protocol.

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.

How to create a Container ?

This describes the different steps to create containers inside Nodeum.

The Container definition is available in the Data Container menu.

To create a new Container

Click on the '+' button and complete the information requested.


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.


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.


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).

Privileges Definition

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.

Prepare container for use with S3 protocol

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 :

  1. Create a specific user

  2. Enable the S3 access for this User and Nodeum will generate automatically the Key id and Password you need to receive S3 data.

  3. Create a container and give the privileges to the user you have just created above.

  4. Remap the S3 policies for this newly created container.

Last updated