Administrator’s Command Line Guide

3.2. Deploying Object Storage
(round-robin) manner.
8. Add nodes where object storage services will run to the configuration. To do this run the ostor-ctl
add-host command on every such node:
# ostor-ctl add-host -r /var/lib/ostor/configuration --hostname <name> --roles OBJ
You will need to provide the object storage password set on step 3.
9. Create a new S3 volume with the desired number of NS and OS:
# ostor-ctl add-vol --type OBJ -s <cluster_mount_point> --os-count <OS_num> \
--ns-count <NS_num> --vstorage-attr "failure-domain=host,tier=0,replicas=3"
where
• <NS_num> and <OS_num> are the numbers of NS and OS and
• failure-domain=host, tier=0, replicas=3 parameters set volume’s failure domain, tier, and
redundancy mode (for more details, see the Installation Guide).
The command will return the ID for the created volume. You will need it on the next step.
10. Create S3 gateway instances on chosen nodes with Internet access and external IP addresses.
Note: For security reasons, make sure that only NGINX can access the external network and that
S3 gateways only listen on internal IP addresses.
# ostor-ctl add-s3gw -a <internal_IP_address>:<port> -V <volume_ID>
where
• <internal_IP_address> is the internal IP address of the node with the gateway,
• <port> (mandatory) is an unused port unique for each GW instance on the node, and
• <volume_ID> is the ID of the volume you created on the previous step (it can also be obtained from
ostor-ctl get-config).
11. Launch object storage agent on each cluster node added to the object storage configuration.
# systemctl start ostor-agentd
# systemctl enable ostor-agentd
12. Make sure NS and OS services are bound to the nodes.
By default agents will try to assign NS and OS services to the nodes automatically in a round-robin
27