NAS Storage Configuration
Last updated
Last updated
Go into:
System -> Hardware -> Storages -> NAS
To add a SMB Storage, click the button
Fill the following parameters to configure the storage :
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.
First, go to
Storage Services -> NAS
To add a NAS Target,
click the button
Fill the following parameters to configure the storage :
Go into:
System -> Hardware -> Storages -> NAS
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.
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.
Go into:
System -> Hardware -> Storages -> NAS
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)
First, go to
Storage Services -> NAS
To add a Target,
NAS Name*
Select the NAS
Name*
Give a name for your target
Target
Use the target Path
Mount Options
Username
Password
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
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.
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.
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
