This guide is tailored for Cloud Operations Engineers who manage multiple racked servers, data centers, and enterprise-grade facilities and wish to run Commercial Storage Nodes.
Please note that joining the Commercial Storage Node Operator Program is a prerequisite for this setup.
This guide is for Commerical Storage Nodes, if you're looking to join the public network follow Quickstart Node Setup instead.
- Admitted into the Commercial Storage Node Operator Program (request to join the program)
- Understand the difference between Public and Commercial Storage Nodes
A commercial Storage Node runs the same software as a public Storage Node, but is not subject to the same restrictions.
Run one Storage Node per hard drive.
If you have a virtualized environment, try to target the nodes size to be similar to the average drive size underlying that virtualized environment. So if the infrastructure is mostly on 10 TB HDD then set the node size to be 10 TB.
Follow Steps 1 through 6 in the Storage Node setup guide for each Commercial Storage Node:
For step 6, Commercial Storage Nodes require additional environment variables
Since it's recommended to run one Storage Node per drive a sample ansible configuration is provided for some ideas on how to manage the nodes. Metrics for the Storage nodes can also be setup by following the node dashboard guide.
To ensure optimal functionality and security, it's mandatory to update your nodes to at least the minimum required version (usually updates every 2 to 3 weeks). We recommend utilizing the built-in auto-updater in the Storage Node docker image for hassle-free updates.
Once you have 1 or more Storage Nodes running, reply back to your contact with a csv file or document of all your Storage node IDs. The vetting process will begin and if the nodes are acceptable, they will be enabled to receive data.