Nominode Installation and Configuration
Installing a Nominode
3. Ensure that you have have local console access or can create a remote session via the telnet (23) or ssh (22) port on the server where you will install the Nominode.
4. Ensure that you can access the http (80) or https (443) port on your server.
The Nominode installer uses curl, bzip2, and Docker. If these programs are not available on your server, the Nominode installer will attempt to automatically obtain and install them for you. If it is unable to do so, you will need to manually install them.
Only the most recent version of Docker is supported, though other versions may be compatible.
Known issues exist when trying to use certain older versions of Docker with Nominode software.
6. Open a local, telnet or ssh session with your server.
7. Create a service user account with root access to your server to use for the rest of these steps and for running the Nominode software.
Avoid using the sudo command to perform the installation, as doing so will then require using sudo for version upgrades, as well.
8. Create a folder where you would like to install your Nominode. /opt/nomnomdata is recommended.
9. Navigate to the folder that you created and execute this command:
curl -L http://download.nomnomdata.com/nominode-app-linux-x86_64-latest -o nominode-app
If your server is unable to access the installer using the curl command, you can manually place the Linux installer on your server by downloading it from https://my.nomnomdata.com/nominode/download
and then copying it to the folder that you created.
10. Execute these commands:
chmod a+x nominode-app
11. Respond to the questions posed by the installer and then wait for it to fully complete.
The installer creates a local MySQL database for the Nominode to use for storing its own data. If you are setting up a Nominode for testing or trial purposes, the local database is sufficient. However, if you are planning to use your Nominode in a production context, then follow the steps to switch from a local database to a remote database
If Docker was installed as part of the setup process, then be sure to take the extra steps to ensure that the Docker service is set to automatically start whenever your server is restarted:
If the Docker service is not running, then the Nominode software will not function properly.
Initial Configuration for a Nominode
- Connect to http://<your server's DNS>/setup
- Log in to your Nominode using your Nom Nom Data account.
- Name your Nominode uniquely and select the Organization that will manage it.
- Click the Create New Nominode button.
- Wait for the Registering, Reboot Workers, Reboot Scheduler and Reboot Core tasks to complete.
- Log in again to your Nominode using your Nom Nom Data account.
- You are now ready to Add Users, Engines and Tasks to your Nominode.
We are happy to install and configure your Nominode for you.
Changing a Nominode's Configuration
Switching from a Local Database to a Remote Database Open a local, telnet or ssh session with your server. Navigate to the folder where your Nominode software is installed and execute these commands: ./docker-compose exec mysql mysqldump -u root ...
Nominode Task Updates via CLI
Below, we will discuss retrieving, updating, creating and deleting a Task using the Nominode SDK. Command line interaction with Tasks and other components is a cornerstone for integrating your Nominode with source control systems and continuous ...
Uninstalling a Nominode
Shutting down a Nominode and Removing the Nominode software Open a local, telnet or ssh session with your server. Navigate to the folder where the Nominode software was installed and execute this command: ./docker-compose down -v Then navigate to a ...
Nominode Minimum System Requirements
CPU: 4 Cores Memory: 8 GB Operating Systems Supported: Amazon Linux 2 CentOS 7 Debian 9, 10 Red Hat Enterprise Linux 8 SUSE Linux Enterprise Server 12, 15 Ubuntu 16, 18 Additional Software: Docker, curl, bzip2 Nominode software installation has ...
Performing Debug Steps on a Nominode
There are many pieces of information that can be gathered and commands that can be run when a Nominode is in an unhealthy state to investigate the source of the issue and to recover from it. All of the commands described below should be run in the ...