Subscribe to Email Updates

    Installation | 24 min read

    How to Deploy Nodeum ?

    Install on-premise Nodeum software in using the Ansible deployment tools.

    • Requirements
    • Installation
    • Post-installation checks

    Requirements

    See the page Hardware Specification Requirement

    ❗ Install ansible v2.7.1 minimum

     

    Operating system

    Nodeum supports the following distributions:

    • CentOS 7.x
    • RHEL 7.x

    System

    • Root privileges are required (using sudo).
    • SELinux is disabled (managed at deployment).
    • The system must be up to date.

    If you are running CentOS or RHEL, keep your system up-to-date as follows:

    # RHEL or CentOS

    [root@NODEUM ~]# sudo yum update -y
    [root@NODEUM ~]# sudo reboot

     

    User

    Nodeum will define one user which needs ID : 1000.  This ID is created automaticly when the package is deployed.

    If users already use these ID, you have to change their id :

    [root@NODEUM~]# usermod -u 1001 "process"

     

    admin:x:1000:1000::/dev/null:/bin/false

     

    Network

    • The firewall is disabled (this is managed at deployment).

    Setup

    • The installation will be done by Ansible (this is managed at deployment).

    Installation

    [root@NODEUM~]# yum install wget
    Loaded plugins: fastestmirror
    Loading mirror speeds from cached hostfile
     * base: mirror.unix-solutions.be
     * extras: mirror.unix-solutions.be
     * updates: mirror.unix-solutions.be
    Resolving Dependencies
    --> Running transaction check
    ---> Package wget.x86_64 0:1.14-18.el7 will be installed
    --> Finished Dependency Resolution
     
    Dependencies Resolved
     
    ================================================================================
     Package         Arch              Version                Repository       Size
    ================================================================================
    Installing:
     wget            x86_64            1.14-18.el7            base            547 k
     
    Transaction Summary
    ================================================================================
    Install  1 Package
     
    Total download size: 547 k
    Installed size: 2.0 M
    Is this ok [y/d/N]: y
    Downloading packages:
    wget-1.14-18.el7.x86_64.rpm                                | 547 kB   00:00    
    Running transaction check
    Running transaction test
    Transaction test succeeded
    Running transaction
      Installing : wget-1.14-18.el7.x86_64                                      1/1
      Verifying  : wget-1.14-18.el7.x86_64                                      1/1
     
    Installed:
      wget.x86_64 0:1.14-18.el7                                                    
     
    Complete!
    [root@NODEUM ~]# wget get.nodeum.io/public/nodeum-v1-83-3-d0932571.zip -P /root
    --2019-03-07 14:57:08--  https://get.nodeum.io/public/nodeum-v1-83-3-d0932571.zip
    Resolving get.nodeum.io... 185.59.220.23
    Connecting to get.nodeum.io|185.59.220.23|:80... connected.
    HTTP request sent, awaiting response... 200 OK
    Length: 19137127 (18M) [application/octet-stream]
    Saving to: “nodeum-v1-83-3-d0932571.zip”
     
    100%[====================================================================>] 19,137,127  7.38M/s   in 2.5s   
     
    2019-03-07 14:57:10 (7.38 MB/s) - “nodeum-v1-83-3-d0932571.zip” saved [19137127/19137127]
     
    [root@NODEUM ~]# yum install unzip
    [root@NODEUM ~]# unzip /root/nodeum-v1-83-3-d0932571.zip
    Archive:  nodeum-v1-83-3-d0932571.zip
    100%[====================================================================>] 19,137,127  7.38M/s   in 2.5s   
     
    2019-03-07 14:57:10 (7.38 MB/s) - “nodeum-v1-83-3-d0932571.zip” saved [19137127/19137127]
     
    [root@NODEUM ~]# yum install unzip
    [root@NODEUM ~]# unzip /root/nodeum-v1-83-3-d0932571.zip
    Archive:  nodeum-v1-83-3-d0932571.zip
       creating: v1-xx/
      inflating: v1-xx/ansible.cfg   
      inflating: v1-xx/install       
      inflating: v1-xx/install.yml   
      inflating: v1-xx/localhost     
       creating: v1-xx/migration-from-rhel6/
      inflating: v1-xx/migration-from-rhel6/1-backup
      inflating: v1-xx/migration-from-rhel6/2-install-centos7
      inflating: v1-xx/migration-from-rhel6/3-install-nodeum
      inflating: v1-xx/migration-from-rhel6/4-restore-1
      inflating: v1-xx/migration-from-rhel6/5-update-db
      inflating: v1-xx/migration-from-rhel6/6-restore-2
      inflating: v1-xx/migration-from-rhel6/my.cnf
       creating: v1-xx/roles/
       creating: v1-xx/roles/ansible-role-configuration/
       creating: v1-xx/roles/ansible-role-configuration/defaults/
      inflating: v1-xx/roles/ansible-role-configuration/defaults/main.yml
       creating: v1-xx/roles/ansible-role-configuration/tasks/
      inflating: v1-xx/roles/ansible-role-configuration/tasks/final.yml
      inflating: v1-xx/roles/ansible-role-configuration/tasks/folders.yml
      inflating: v1-xx/roles/ansible-role-configuration/tasks/main.yml
      inflating: v1-xx/roles/ansible-role-configuration/tasks/permissions.yml
      inflating: v1-xx/roles/ansible-role-configuration/tasks/yum.yml
       creating: v1-xx/roles/ansible-role-configuration/vars/
      inflating: v1-xx/roles/ansible-role-configuration/vars/main.yml
       creating: v1-xx/roles/ansible-role-core/
       creating: v1-xx/roles/ansible-role-core/defaults/
      inflating: v1-xx/roles/ansible-role-core/defaults/main.yml
      
      ...
      
      inflating: v1-xx/roles/rvm.ruby/vars/main.yml
      inflating: v1-xx/site.yml      
       creating: v1-xx/vars/
      inflating: v1-xx/vars/common.yml
      inflating: v1-xx/vars/core.yml 
      inflating: v1-xx/vars/db_mongo.yml
      inflating: v1-xx/vars/db_mysql.yml
      inflating: v1-xx/vars/scheduler.yml
      inflating: v1-xx/vars/solr.yml 
      inflating: v1-xx/vars/web.yml  
      inflating: v1-xx/vars/ws_xml.yml
    [root@NODEUM ~]# cd /root/v1-xx/
    [root@NODEUM v1-xx]# ./install
    (optional) Enter master password for inventory encryption
    Please wait...
      
    PLAY [localhost] **********************************************************************************************************************************************************************************************************************************************************************************************************
      
    TASK [Gathering Facts] ****************************************************************************************************************************************************************************************************************************************************************************************************
    ok: [127.0.0.1]
      
    TASK [Checking ansible version] *******************************************************************************************************************************************************************************************************************************************************************************************
    ok: [127.0.0.1] => {
        "changed": false,
        "msg": "All assertions passed"
    }
    Install on remote location (yes/no) [no]: no
    What is the hostname [nodeum.example.local]: nodeum.example.local
    What user will run the installation (need sudo privileges) [root]:
    User password:
      
    PLAY [localhost] **********************************************************************************************************************************************************************************************************************************************************************************************************
      
    TASK [set_fact] ***********************************************************************************************************************************************************************************************************************************************************************************************************
    ok: [127.0.0.1]
      
    TASK [set_fact] ***********************************************************************************************************************************************************************************************************************************************************************************************************
    ok: [127.0.0.1]
      
    TASK [Write new inventory in ~/.nodeum/hosts.yml] *************************************************************************************************************************************************************************************************************************************************************************
    ok: [127.0.0.1]
      
    PLAY RECAP ****************************************************************************************************************************************************************************************************************************************************************************************************************
    127.0.0.1                  : ok=5    changed=0    unreachable=0    failed=0 
      
    Starting installation in 5 sec.
      
    ....
      
    TASK [ansible-role-systemd-service : enable service] ***************************************************************************************************************************************************************************************************************************
    ok: [general_host] => (item={'value': {u'description': u'Service for Nodeum MountPoint Scanning', u'after': u'network.target', u'restart_sec': u'1', u'exec_start': u'/usr/mtc/mount_point_scanning/mount_point_scanning', u'wanted_by': u'multi-user.target', u'working_directory': u'/usr/mtc/mount_point_scanning', u'type': u'simple', u'restart': u'always', u'user': u'root'}, 'key': u'nodeum_mount_point_scanning'})
      
    TASK [ansible-role-mount-point-scanning : Reload daemon] ***********************************************************************************************************************************************************************************************************************
    ok: [general_host]
      
    TASK [ansible-role-mount-point-scanning : Start nodeum_mount_point_scanning service] *******************************************************************************************************************************************************************************************
    changed: [general_host]
      
    RUNNING HANDLER [ansible-role-systemd-service : restart service] ***************************************************************************************************************************************************************************************************************
    changed: [general_host] => (item={'value': {u'description': u'Service for Nodeum MountPoint Scanning', u'after': u'network.target', u'restart_sec': u'1', u'exec_start': u'/usr/mtc/mount_point_scanning/mount_point_scanning', u'wanted_by': u'multi-user.target', u'working_directory': u'/usr/mtc/mount_point_scanning', u'type': u'simple', u'restart': u'always', u'user': u'root'}, 'key': u'nodeum_mount_point_scanning'})
      
    PLAY RECAP *********************************************************************************************************************************************************************************************************************************************************************
    general_host               : ok=198  changed=91   unreachable=0    failed=0    skipped=56   rescued=0    ignored=3 
      
    [root@NODEUM v1-83-3]#

     

    ❗  Fatal error during a local installation

    If you install Nodeum in local Mode, you will always a fatal error to force the linux to restart.

    This error appears only during the first Installation.  Not for the update.

     

    Restart the server VM or Physical.

    Nodeum is now ready to use, you can access it through your browser at this url : http://xxx.xxx.xxx.xxx/ or via your favorite DNS name.

    Post-installation checks

    Run this check script on the server to validate that all processes and up and running.

     

    [root@NODEUM ~]# /usr/mtc/bin/lm
    root       8117      1  0 15:11 ?        00:00:00 /usr/mtc/bin/core_superv
    root       8154      1  5 15:11 ?        00:00:10 /usr/mtc/bin/core_manager
    root       8297      1  0 15:11 ?        00:00:01 /usr/mtc/bin/core_watchdog
    root       8647   8643  0 15:12 ?        00:00:00 Passenger core
    root       9446      1  0 15:12 ?        00:00:00 /usr/mtc/bin/core_fuse /mnt/FUSE -odefault_permissions -ohard_remove -oallow_other -obig_writes
    root       8132      1  0 15:11 ?        00:00:00 /usr/mtc/bin/library_manager
    root       8255      1  1 15:11 ?        00:00:02 /usr/mtc/bin/data_mining
    tcp        0      0 127.0.0.1:1501          0.0.0.0:*               LISTEN      0          49488      8154/core_manager  
    tcp        0      0 127.0.0.1:1502          0.0.0.0:*               LISTEN      0          48585      8297/core_watchdog 
    tcp        0      0 127.0.0.1:1503          0.0.0.0:*               LISTEN      0          48452      8132/library_manage
    tcp        0      0 127.0.0.1:1504          0.0.0.0:*               LISTEN      0          44764      8255/data_mining   
    tcp        0      0 0.0.0.0:1518            0.0.0.0:*               LISTEN      0          41754      8154/core_manager  
    tcp        0      0 0.0.0.0:1519            0.0.0.0:*               LISTEN      0          36770      8132/library_manage
    [root@NODEUM ~]#

     

    Licence

    Thank you for your patience, you are now at the end of the installation.  Enjoy using Nodeum.

    Without licence, you are free to use any features with the following restrictions :

    Maximum Cache Partition Size 4 TB
    Maximum Number of Tapes 5
    Maximum Number of Cloud Bucket 1
    Maximum Bucket Size 100 GB
    Maximum Number of NAS 1
    Maximum NAS Size 1 TB

    Interested to unlock your version, feel free to contact us.

    Proxy

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

    Configuration Proxy Settings
    [NODEUM:root]/usr/mtc/bin>cd /etc/
    [NODEUM:root]vi /etc/environment
    export http_proxy=http://xxxxx:xxxx
    export https_proxy=http://xxxxx:xxxx
    export ftp_proxy=http://xxxxx:xxxx
    no_proxy=http://xxxxx:xxxx

     

    💡Set/Export: http_proxy With Special Characters In Password

    If the proxy server password has special characters such as !,@, you need to to use unicode characters in hexadecimal.

    For example, if your password is : F@o:o!B#ar$, the export http_proxy="http://user:F@o:o!B#ar$@server1.cyberciti.biz:3128/" will not work.

    You need to convert the special characters in hexadecimals. In this example @ becomes %40, : becomes %3A, and so on. (You can use for example: https://www.online-toolz.com/tools/text-hex-convertor.php)

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

    Thus the export http_proxy looks like this:

    export http_proxy="http://user:F%40o%3Ao%21B%23ar%24@server1.cyberciti.biz:3128/"

     

     

     

    Related Categories

    Installation

    Let Us Know What You Thought about this Post.

    Put your Comment Below.

    You may also like:

    Installation FAQ

    Web GUI not accessible after a Nodeum version upgrade

    Problem :

    Installation

    Operating System Compability Matrix

    The following distributions are supported: CentOS 7.x : install a minimal version : https://wiki.centos.org/Download RHE...

    Installation

    Virtual Appliance Compatibility

    Prerequisites Check this specification to be sure to deploy correctly the virtual appliance.

    Learn and grow with award-winning support and a thriving community behind you.

    Get the free version