Adding a FileSystem

You can add one or more filesystems in Oracle Cloud Infrastructure Storage Software Appliance and connect each filesystem to a container or bucket in your account or tenancy.

  1. Log in to the management console.

    The available filesystems are displayed.

  2. Click Create Filesystem in the navigation pane on the left.

    The Create a FileSystem page is displayed.

  3. Enter the required information in the following fields:
    Field Description

    FileSystem Name

    Name of the filesystem.

    If a container or bucket by the same name doesn’t exist in your account or tenancy, then it will be created. Enter a name that is meaningful to you and unique.

    Note:

    If a container or bucket with the same name as the filesystem already exists, and if that container or bucket isn’t empty, then the data cached in the Oracle Cloud Infrastructure Storage Software Appliance filesystem may not be consistent with data stored in the container or bucket.

    Object Storage API Endpoint

    The object storage API endpoint for your service instance.
    • To find out the object storage API endpoint for your Oracle Cloud Infrastructure Object Storage Classic instance, go to the Oracle Cloud My Services page, and select Oracle Cloud Infrastructure Object Storage Classic. The service details are displayed. Look for the REST Endpoint field under the Additional Information section. (Not available on Oracle Cloud at Customer)

    • To find out the object storage API endpoint for your Oracle Cloud Infrastructure Object Storage tenancy, see API documentation for Oracle Cloud Infrastructure.

    Go to Step 4a.

    User Name

    Oracle Cloud Infrastructure Object Storage Classic user name.

    Note: This field is displayed only for Oracle Cloud Infrastructure Object Storage Classic accounts.

    Account Password

    Oracle Cloud Infrastructure Object Storage Classic password.

    Note: This field is displayed only for Oracle Cloud Infrastructure Object Storage Classic accounts.

    Compartment ID

    Oracle Cloud Infrastructure Object Storage Compartment ID

    Note: This field is displayed only for Oracle Cloud Infrastructure tenancy.

    Tenant ID

    Oracle Cloud Infrastructure Object Storage Tenant ID

    Note: This field is displayed only for Oracle Cloud Infrastructure tenancy.

    User ID

    Oracle Cloud Infrastructure Object Storage User ID

    Note: This field is displayed only for Oracle Cloud Infrastructure tenancy.

    Public Key Finger Print

    Oracle Cloud Infrastructure Object Storage Public Key Finger Print

    Note: This field is displayed only for Oracle Cloud Infrastructure tenancy.

    Private Key

    Oracle Cloud Infrastructure Object Storage Private Key

    Note: This field is displayed only for Oracle Cloud Infrastructure tenancy.

    Private Key Passphrase

    Oracle Cloud Infrastructure Object Storage Private Key Passphrase

    Note: This field is displayed only for Oracle Cloud Infrastructure tenancy.

    Go to Step 4b.

    1. Click Validate.

      If any of the values entered above do not match your Oracle Cloud Infrastructure Object Storage Classic account credentials, then an error message is displayed. Recheck and enter the appropriate values in the respective fields.

    2. Click Save.
  4. If you want to create an Archive filesystem, then select the Enable Archive check box.

    For more information, see About Archive FileSystems.

    If the filesystem name matches an existing container, and if the storage class of the container is standard, then you cannot mount the filesystem and an error message is displayed.

  5. Click Show Advanced, and enter the required information in the following fields:
    Field Description

    NFS Allowed Hosts

    The hosts allowed to connect to the NFS export.

    Example: 2001:db8:9:e54::/64, 192.0.2.0/24

    NFS Export Options

    The NFS export options.

    Example: rw, sync, insecure, no_subtree_check, no_root_squash

    Don’t specify the fsid option.

    Maximum Local Cache Size in GiB

    The maximum number of bytes that can be cached.

    When the data in the cache reaches the specified limit or the cache is full, the appliance removes files from the cache based on a least recently used (LRU) algorithm. The files that are yet to be uploaded to the account are not removed from the cache. The preserved files (by cache pinning) are also not removed from the cache.

    See Configuring the Cache for FileSystems.

    Note: The number of files in cache is limited to 20,000, regardless of the specified cache size in bytes.

    Concurrent Uploads

    The number of concurrent uploads to the cloud.

    Allowed range: 1 to 30

    This field indicates the maximum number of files that can be concurrently uploaded in the appliance. If the value is 5, the concurrent file uploads can be between 0-5.

    Delete Old File Versions

    If you select this check box for a filesystem, then every time you start the appliance and once every 24 hours after that, all the older versions of all the objects are deleted in the container or bucket that's connected to the filesystem. Only the latest version of each object is retained.

    For more information, see Enabling File Versions Compaction.

    This option is disabled by default.

    Restore Object Retention

    The number of days a file will remain in the restored state.

    Note: This field is displayed only for an archive filesystems.

    Default value: 10

    Sync Policy

    The metadata operations are flushed to the disk based on the following modes. Select one of the following modes based on your requirement:
    • Asynchronous

      In this mode, the filesystem operations are time-based and are persisted asynchronously. This mode offers the best performance.

      Note:

      This mode is not suitable for any filesystem operation that depends on synchronous transactions.

    • Posix Standard

      This mode is enabled by default. Only the synchronous transactions (like fsync, ODSYNC and OSYNC) are committed to the disk. All the other transactions are handled asynchronously.

    These sync modes do not affect on-disk consistency.

    Cloud Read-ahead

    The number of 1-MB blocks to be downloaded and used to read ahead when reading files.

    Use this setting to improve the read performance for large files that aren't cached.

    Default value: 0 (prefetching is disabled)

  6. Click Save.

Next Task

Connect the filesystem. See Connecting a FileSystem.