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
  • Install the Operating system
  • System
  • User
  • Install & Update
  • Advanced Settings
  • Proxy requirement
  • Network Interface

Was this helpful?

  1. Install and Deploy Nodeum
  2. Nodeum v1

Ansible based installation

Last updated 1 year ago

Was this helpful?

Install the Operating system

System

  1. Root User Access is required during the installation.

  2. SELinux will be disabled during the Ansible deployment and this will also require to reboot the Operating System.

User

Nodeum will define one user which needs ID : 1000. This ID is created automatically when the package is deployed. If a user already use these ID, you have to change their id :

$ usermod -u 1001 "username"
admin:x:1000:1000::/dev/null:/bin/false

It is the same for group, where group ID 1000 and group ID 1001 needs to be available. If group already use these ID, you have to change their id :

$ groupmod -g 1002 "groupname"
admin:x:1000:

Install & Update

To proceed with a Nodeum installation or an update, the following instructions must be performed.

An unlimited internet connection is necessary.

$ yum install wget
$ wget get.nodeum.io/public/nodeum-v1-9xx.tar.gz 
$ tar -xvzf /root/nodeum-xxx.tar.gz
$ cd v1-9xx-xx
$ ansible-playbook check_install.yml
$ ansible-playbook install.yml

Once the ansible-playbook is fully installed, and it ends up with this screen.

It is important to notice that there is no failed result

Then Nodeum is now ready to use, you can access it through your browser at this URL: http://your nodeum ip address/or via the DNS name.

If you can't access the Console through the default http port, you may have a local firewall is running. We recommend to either configuring it properly to allow access to the server through the http/https protocol.

Advanced Settings

Proxy requirement

If your network configuration requires a Proxy server to reach the internet, you need to configure the Proxy servers as follows:

$ vi /etc/environment
export http_proxy=http://xxxxx:xxxx@server.domain.local:8080
export https_proxy=http://xxxxx:xxxx@server.domain.local:8080
export ftp_proxy=http://xxxxx:xxxx@server.domain.local:8080
no_proxy=http://xxxxx:xxxx@server.domain.local:8080

If the password have special characters as !,@, you need to use unicode characters in hexadecimal.

For example, if your password is :

F@o:o!B#ar$, the following export will not work

export http_proxy="http://user:F@o:o!B#ar$@server.domain.local:8080"

You need to convert the special characters in hexadecimals.

In this example :

@ becomes %40,

: becomes %3A,

and so on.

In our case, the password: F@o:o!B#ar$ is replaced by F%40o%3Ao%21B%23ar%24

The export http_proxy looks like this:

export http_proxy="http://user:F%40o%3Ao%21B%23ar%24@server.domain.local:8080"

Network Interface

Service mapping

Each services can be bind to specific network interface.

For doing that, the Ansible Installation playbook needs to be reapplied once the inventory files have been modified accordingly to the mapping you need.

In the hosts information file you can find in the extracted Nodeum installation package, you will find the following file(s) : /inventory/hosts_vars/srv1.

This file contains the different configuration and settings that will be applied to host.

There is a section to define the service binding.

By default the iface_name parameter is using the main network interface, but this information can be overwritten.

# If there is no default network interface defined or you want to override it
# iface_name: eth0

Afterward, in the same file, you can find different parameters to bind a list of services to a specific interface name.

# Specific name of interface for each services. Default to iface_name 
# or default network interface) if undefined
# smb_iface_name: eth0
# nfs_iface_name: eth0
# rails_iface_name: eth0
# zookeeper_iface_name: eth0
# solr_iface_name: eth0
# catalog_indexer_iface_name: eth0

Description of each parameter :

Parameter
Service Name

smb_iface_name

SAMBA

nfs_iface_name

NFS

rails_iface_name

RAILS

solr_iface_name

SOLR

catalog_iface_name

CATALOG INDEXER

(You can use for example: )

https://www.online-toolz.com/tools/text-hex-convertor.php