- 2 Minutes to read
- Print
- PDF
Adding and Editing Storage Nodes
- 2 Minutes to read
- Print
- PDF
All data in transit to and from a storage node, and stored in the storage node is encrypted by the CTERA Portal.
To add or edit a storage node:
For NFS storage nodes, EMC Isilon (NFS), Generic (NFS), and NetApp (NFS):
- Log in to the server as
root
, using SSH. - Create a folder for the NFS mount on the server.
- Mount the NFS storage node to each server, except the preview server, by running the following script on each server:
portal-mount.sh mount_storage_node NFS_IP:/NFS_FOLDER
where NFS_IP is the IP address of the NFS mount point, and NFS_FOLDER is the name of the folder you created on the NFS server.
- Log in to the server as
In the global administration view, select Main > Storage Nodes in the navigation pane.
The STORAGE NODES page is displayed.
Either,
- Add a storage node, click New Storage Node.
The New Storage Node window is displayed.
Or,
- Edit an existing storage node; click the node's name.
The storage node window is displayed with the storage node name as the window title.
The details displayed depend on the type of storage node. When editing a storage node you can only edit enabled values, such as Storage Node Name.
- Add a storage node, click New Storage Node.
Enter the generic details for the storage node. These details are the same for every type of storage node.
Type – The type of storage node you are adding. When you select the type, more fields are displayed so that you can add the specific details for the storage node, as described for each storage node listed in step 7.
Storage Node Name – A unique name to identify the storage node.
Storage Class – The storage class that will include this storage node. After defining the storage node, the storage class cannot be changed.NoteThe storage classes are defined using CLI. For details, see Defining a Storage Class.
Dedicated to Portal – Dedicate the storage node to one team portal selected from the drop-down list. The storage node is used for this team portal and no other team portal uses it. The team portal will only write to storage nodes that are dedicated to it and not to other storage nodes.
NoteWhen defining an Amazon S3 storage node with AWS Snowball, you must dedicate the storage node to one virtual portal.
Once data is written to a dedicated storage node, you cannot change this setting.
Complete the additional fields that are displayed when you choose the type and then click SAVE.
- Amazon S3
- Caringo (S3)
- Ceph, see OpenStack Swift
- Cloudian
- Cohesity SmartFiles (S3)
- DDN Web Object Scaler
- EMC ECS (S3)
- EMC Isilon (NFS)
- Generic (NFS)
- Generic (S3)
- Google Cloud Storage (S3)
- HGST Active Archive
- HGST Active Scale
- Hitachi HCP
- Hitachi Vantara HCP (S3)
- IBM Cloud Object Storage (S3)
- IBM Cloud Object Storage (Simple Object API)
- Isilon (S3)
- Local Filesystem
- Microsoft Azure Blob Storage
- MinIO (S3)
- NetApp (NFS)
- NetApp StorageGRID/NetApp StorageGRID Webscale (S3)
- Nutanix (S3)
- OpenStack Swift
- OpenStack Swift (KeyStone)
- Oracle Storage Cloud Service
- Quantum ActiveScale (S3)
- Scality ARTESCA (S3)
- Scality RING
- Seagate Lyve Cloud Object Storage
- Wasabi (S3)
- Zadara (S3)