Administrator’s Command Line Guide

3.2. Deploying Object Storage
• An external (public) network through which end users will access the S3 storage. Standard HTTP
and HTTPS ports must be open in this network.
An object storage cluster is almost completely independent on base block storage (like all access points,
including virtual environments and iSCSI). Object and name servers keep their data in the Acronis
Storage cluster in the same way as virtual environments, iSCSI, and other services do. So the OS and NS
services depend on vstorage-mount (client) and can only work when the cluster is mounted. Unlike
them, gateway is a stateless service that has no data. It is thus independent on vstorage-mount and can
theoretically be run even on nodes where the Acronis Storage cluster is not mounted. However, for
simplicity, we recommend creating gateways on nodes with object and name servers.
Object and name servers also utilize the standard high availability means of Acronis Storage (i.e. the
shaman service). Like virtual environments and iSCSI, OS and NS are subscribed to HA cluster events.
However, unlike other services, S3 cluster components cannot be managed (tracked and relocated
between nodes) by shaman. Instead, this is done by the S3 configuration service that is subscribed to
HA cluster events and notified by shaman whether nodes are healthy and can run services. For this
reason, S3 cluster components are not shown in shaman top output.
Gateway services which are stateless are never relocated and their high availability is not managed by
the Acronis Storage cluster. Instead, a new gateway service is created when necessary.
2. Make sure that each node that will run OS and NS services is in the high availability cluster. You can add
nodes to HA cluster with the shaman join command.
3. Install the vstorage-ostor package on each cluster node.
# yum install vstorage-ostor
4. Create a cluster configuration on one of the cluster nodes where object storage services will run. It is
recommended to create 10 NS and 10 OS services per each node. For example, if you are going to use
five nodes, you will need 50 NS and 50 OS. Run this command on the first cluster node.
# ostor-ctl create -r /var/lib/ostor/configuration -n <IP_addr>
where <IP_addr> is the node’s IP address (that belongs to the internal S3 network) that the configuration
service will listen on.
You will be asked to enter and confirm a password for the new object storage (it can be the same as
your Acronis Storage cluster password). You will need this password to add new nodes.
The configuration service will store the cluster configuration locally in /var/lib/ostor/configuration. In
addition, <IP_addr> will be stored in /<storage_mount>/<ostor_dir>/control/name (<ostor_dir> is the
25