File System Options

The following options are available when you create or edit a file system. The name, data center location, and node type cannot be edited directly after the file system is created (instead, you can migrate the file system to a new file system). Lifecycle policies and allowed IPs can be added only after the file system is created.

Name

The name of the file system. This name must be unique across all of your team’s file systems.

Data Center Location

The data center in which the file system will be located. The file system can only be used to run jobs in this data center. Migrating the file system to a different location after it is created will incur an additional cost for data transfer.

Node Type

The type of node that will serve the file system. After the file system is created, the only way to change the node type is to migrate the file system.

Size (TB)

The size of the file system in TB (maximum: 120 TB). Only integer values are allowed.

The minimum size is 1 TB for the Standard node type and 4 TB for the Performance node type. After the file system is created, you can edit it to increase the size or migrate it to reduce the size. Disk I/O is lower for file systems smaller than 4 TB.

Part of the file system storage will be used for an applications cache. The cache can grow to 100 GB or more, depending on how many versions of CONVERGE your team runs.

If the file system usage equals or exceeds 95% of its size, your team will not be able to create new jobs on the file system. You can either expand the file system or delete some of your files to continue running jobs. If you delete files, the usage information in CONVERGE Horizon might not be updated immediately, because the file system details are refreshed every 30 minutes. You can refresh the file system manually from the File Systems page by clicking the Refresh File System () button.

Auto-expand when file system is 70% full

Select this option to automatically increase the size of the file system based on usage. The size of the file system will increase by 1 TB every time the file system becomes 70% full, up to the Auto-Expand Size that you specify.

You can also increase the size manually at any time by editing the file system.

Auto-Expand Size (TB)

The maximum size (in TB) to which the file system can expand. Cannot be larger than 120 TB. Applies only when you’ve selected the option to auto-expand the file system.

Lifecycle Policies

Lifecycle policies determine which files will be automatically deleted from the file system after a certain number of days. This option appears only when editing a file system you have already created.

Caution

Lifecycle policies apply to all files on the file system and must be communicated to all team members. When these policies are applied, files are deleted permanently and cannot be recovered.

The only way to limit lifecycle policies to one user is to have that user’s data isolated in a specific directory (e.g., user1/). The directory path can then be included in the filter pattern (e.g., user1/*.h5).

To configure lifecycle policies, enter a filter in the first column and a number of days in the second column, then click the plus (+) button. Files with paths matching the filter pattern will be automatically deleted after the specified number of days. The pattern is compared to the file path relative to /mnt/fs/files/ (i.e., the File Manager home directory). Patterns are NOT case-sensitive and should NOT start with /.

The filter pattern can include the * wildcard, which matches zero or more occurrences of any character, as well as characters that should be matched literally. For example, the filter *.h5 consists of the * wildcard followed by the literal string .h5. This pattern will match any file in any directory or subdirectory with a path ending in .h5 or .H5. More examples are included below.

Days are counted from the date the file was created. Lifecycle policies are typically applied within 24 hours of when the criteria are satisfied, although a specific execution time cannot be guaranteed.

If you add multiple filters, they are evaluated using OR logic.

Example Pattern	Matches	Does Not Match
*.h5	post001_-1.308e+01.h5 a/b/post002_-1.200e+01.h5 c/map_2.498e+02.h5	h5 d/h5
tmp/*	tmp/file.ext tmp/a/b/file.ext	c/tmp/file.ext
*BOUNDARY*	boundary.in a/BOUNDARY_NAMES.txt b/boundary.echo c/d/erosion_boundary_5.out	e/f/bound23-wall.out

Allowed IPs

For enhanced security, we recommend configuring allowed IP addresses from which users can log in to the File Manager (this applies when opening the File Manager in a new tab outside of the CONVERGE Horizon web interface). If your organization owner has already configured allowed IPs at the organization level, those settings are automatically applied to all file systems. Otherwise, you can specify allowed IPs for each file system individually. This option appears only when editing a file system you have already created.

In the Allowed IPs field, enter the IP addresses or CIDR subnets from which users can log in to the File Manager. Click the Add (+) button after each string that you enter and click Update File System when you are ready to save the changes.

If no allowed IPs are specified for a given file system, users can log in to the File Manager from any IP address.

Note that the allowed IPs do not affect file system access via SSH. Users with valid SSH keys can always SSH to the file system from any IP address.