Nodeum Docs
HomepageBlog
  • ✨What is Nodeum?
    • Data Management Software
  • 👣GETTING STARTED
    • Step by Step
  • 🏨ARCHITECTURE
    • Standalone
    • High Availability
    • Fully Scalable & Resilience
  • Install and Deploy Nodeum
    • Platform Support
    • Nodeum v1
      • Ansible based installation
    • Nodeum v2 - Data Mover
      • Ansible based Installation
        • Customize your Installation
      • Docker Based Deployment
    • SLURM Integration
    • Software License Application
  • Interfaces
    • ND Client
    • Console
      • Manual for Administrator
        • Login
        • Dashboard & Reports
        • Catalog
        • Data Mover Management
        • Advanced Task Management
        • Data Container
        • Primary Storage Configuration
        • Pool Management
        • TCO Calculator
        • Toolbox
        • System Settings
          • Information
          • Configuration
          • Date & Time
          • Backup
          • Services
          • Hostname and DNS Configuration
          • NAS Storage Configuration
          • Object Storage Configuration
          • Tape Library Configuration
          • User Management
          • Audits
      • Manual for End User
    • For Developers
      • RESTful API
      • Configuration through RestAPI Console
      • Software Developement Kits (SDK)
      • Nodeum API
        • API Terms of Use
        • release v1.x
        • release v2.x
  • DATA MOVER
    • Policy-Based Task orchestration
      • Pool Management
      • Scheduler
      • Data Integrity
      • Priority Management
      • Filtering (Basic or Advanced)
      • Hook service (callback)
    • Content traceability
    • Metadata Management
  • IDENTITY MANAGEMENT
    • Right - Authentication & Authorization
    • LDAP Plugin for JWT Token
  • Container Configuration
    • Prerequisites
    • About Container
    • Authorization and Authentication
    • Access your Container
  • HYBRID STORAGE MANAGEMENT
    • File System Managment
    • Object Storage Management
      • Customize your S3 connection
    • Tape Library Management
      • Tape Writing Format : LTFS
      • Tape Compression
      • Tape Rehydratation
      • Import a LTFS Tape
      • Task Maintenance for Tapes
  • ⏰Alert & Monitoring
    • Alerts
    • Monitoring
    • Log Management
  • 🏥Recover after Hardware Failure
    • Failover - Active/Passive
    • Failover Procedure - One Site
    • Backup & Restore
  • 🔐Security Guide
    • Advanced Network Configuration
    • Add a SSL Certificate on Web Console
    • Enable SSL Certificate Container accessible on S3 Protocol
  • Compatibility guide
    • Software requirement
    • Supported Storage
  • PRODUCT SPECIFICATIONS
    • Character Set Support
    • Limitations
    • Files Status
    • Task Status
Powered by GitBook
On this page
  • SMB Storage
  • Configuration
  • How to map NAS Target ?
  • NFS Storage
  • Configuration
  • How to map NFS Target ?
  • Mounted File System Storage
  • Configuration
  • How to map a Target ?
  • NAS Overview
  • Status
  • Security Mode

Was this helpful?

  1. Interfaces
  2. Console
  3. Manual for Administrator
  4. System Settings

NAS Storage Configuration

Last updated 3 months ago

Was this helpful?

SMB Storage

Configuration

System -> Hardware -> Storages -> NAS

Parameters
Definition

Name

Complete the name of the storage

Comment

Protocol

Choose the protocol SMB or NFS

Version

Choose the version of the protocol

For SMB : Version 1 - 2.1 and 3.0

For NFS : Version 3 - 4

Host

Complete the Hostname

Once, the storage is configured, you need to map the target you want connect to Nodeum to run the Workflow.

How to map NAS Target ?

First, go to

Storage Services -> NAS

To add a NAS Target

NFS Storage

Configuration

Go into:

System -> Hardware -> Storages -> NAS

Parameters
Definition

Name

Complete the name of the storage

Comment

Protocol

Choose the protocol SMB or NFS

Version

Choose the version of the protocol

For SMB : Version 1 - 2.1 and 3.0

For NFS : Version 3 - 4

Host

Complete the Hostname

Once, the storage is configured, you need to map the target you want connect to Nodeum to run the Workflow.

How to map NFS Target ?

Storage Services -> NAS

Add a NFS Target,

In Docker deployment, if you can't browse the NFS target and you get such kind of error message: Can't mount nas01.domain.local:/share/volumes/data/. Then you have to addnolock as a Mount Options for this storage.

Mounted File System Storage

Configuration

Go into:

System -> Hardware -> Storages -> NAS

Parameters
Definition

Name*

Complete the name you define in the toml (ansible playbook)

Comment

Protocol

Choose unspecified (+++ Mandatory)

Host

Complete the Hostname

Mandatory to have the same name as the name writing in the toml (parent_name)

How to map a Target ?

First, go to

Storage Services -> NAS

To add a Target,

Parameters
Definition

NAS Name*

Select the NAS

Name*

Give a name for your target

Target

Use the target Path

Mount Options

Username

Password

NAS Overview

After to have configured the differents NAS Storage (SMB, NFS or Mounted File System), a complete view is provided to see the status of the NAS Storage

Status

Status
Definition
Comments

NAS is Online

NAS is Offline

To reconnect the NAS, just push on the button to refresh the connection

The name of a NAS Storage is unique.

You can't have several NAS Storage with the same Name. If you delete a NAS Storage which are already used by workflow, the system refused to create a new NAS with the same name.

After the creation of a user, it's required to give the rights and privileges to the user to access to your NAS Storage.

If the user haven't access, the tasks and operation inside Nodeum will be impossible.

Security Mode

Allowed values are in mount options if needed :

The default in mainline kernel versions prior to v3.8 was sec=ntlm. In v3.8, the default was changed to sec=ntlmssp.

mount options
definition

sec =

none

attempt to connection as a null user (no name)

krb5

Use Kerberos version 5 authentication

krb5i

Use Kerberos authentication and forcibly enable packet signing

ntlm

Use NTLM password hashing

ntlmi

Use NTLM password hashing and force packet signing

ntlmv2

Use NTLMv2 password hashing

ntlmv2i

Use NTLMv2 password hashing and force packet signing

ntlmssp

Use NTLMv2 password hashing encapsulated in Raw NTLMSSP message

ntlmsspi

Use NTLMv2 password hashing encapsulated in Raw NTLMSSP message, and force packet signing

Nas Target