Links

Access your Container

How can “User” access Containers?

The containers can be reached for accessing Archived Data, it is a virtual file system containing a complete file(s) and folder(s) structure. The file system used an internal cache system and is extended with secondary storage volumes.
The solution supports Operating System running in:
  • Windows 7, 8, 10, 11
  • MacOS
  • Linux

Windows based Operating System in using SMB

Go through the command line and type the command to access Network File Explorer: \\nodeumhostname\
In this screenshot, "nodeum-prod.mt-c.local" is the hostname.
You will then see the list of containers available in your Nodeum.
In this example, "archive" is a valid defined container. Then click on the icon to access it.
If you have configured Nodeum with Active Directory, this window will not appear ; if you have configured Nodeum with local user account, you will have to use your Nodeum's local username and password to access the Container.
Once authorized, you will see the contents available in the container as a normal Network Shared Folder.

MacOS-based Operating System in using NFS

Access the Go menu in the top bar of your MacOS and go to "Connect to Server" option.
Then you type into the address list, the Nodeum hostname, such as smb://nodeumhostname, and click on "Connect" button:
If credentials are well set, you can then access the contents of the Network Shared Folder.

Linux based Operating System in using SMB and NFS

In your Linux terminal, mount the container (named archive in the example) in using SMB protocol. Verify that you have the right package installed:
$ sudo yum install cifs-utils
$ sudo mount.cifs //nodeum.local/archive /mnt/testmnt -o user=johndoe,
pass="secret" 
In this example:
  • nodeum.local: hostname of server
  • /archive: Container name into Nodeum
  • /mnt/testmnt: access point in your Linux system. In the best practice, the name "testmnt" must be chosen according to the container name.
  • -o user=johndoe,pass="secret": johndoe is a user who have access to the container and "secret" is the password of the user.
It is also possible to add this mount point in /etc/fstab:
...
//nodeum.local /archive /mnt/testmnt cifs credentials=johndoe 0 0
...
In your Linux terminal, mount the container (named archive in the example) in using NFS protocols. Verify that you have the right package installed:
$ sudo yum install nfs-utils nfs-utils-lib
$ sudo mount -t nfs -o vers=4 nodeum.local:/archive /mnt/testmnt
It is also possible to add this mount point in /etc/fstab:
...
nodeum.local:/archive /mnt/testmnt/ nfs rw,sync,hard,intr 0 0
...

Access your container in S3

Prior to accessing your container as a bucket, you must define a pair of access key and secret key.
For this you need to go to Container User Management section, then select edit the user profile to whom you want to generate the pair of keys.
In this interface, you can see the keys with possibility to generate new ones.
Once you have your pair of keys generated, you need to remap the container authorization list with the new defined user.
For doing this, you must click on this button:
Go through an S3-supported application and define a new S3 connection profile.
Define a new profile with following configuration:
  • Protocol: S3 (HTTP) or S3 (HTTPS) if you have configured the SSL option in the Nodeum configuration.
  • Nickname: Your own profile definition.
  • Server: Nodeum Server Name
  • Port: 9000 is the default port for this service
  • Access Key ID: This is the access key defined in the Nodeum Container User Management. It is typically the username.
  • Secret Access Key: This is the secret key you have generated in the Nodeum Container User Management
Once done, you can connect to this profile, and you will see the list of bucket your user can access.
Last modified 1mo ago