Plan networking for Object Storage
For both conserving network resources and ensuring that
network administrators understand the needs for networks and
public IP addresses for providing access to the APIs and storage
network as necessary, this section offers recommendations and
required minimum sizes. Throughput of at least 1000 Mbps is
suggested.
This guide describes the following networks:
A mandatory public network. Connects to the proxy
server.
A mandatory storage network. Not accessible from outside
the cluster. All nodes connect to this network.
An optional replication network. Not accessible from
outside the cluster. Dedicated to replication traffic among
storage nodes. Must be configured in the Ring.
This figure shows the basic architecture for the public
network, the storage network, and the optional replication
network.
By default, all of the OpenStack Object Storage services, as
well as the rsync daemon on the storage nodes, are configured to
listen on their STORAGE_LOCAL_NET IP
addresses.
If you configure a replication network in the Ring, the
Account, Container and Object servers listen on both the
STORAGE_LOCAL_NET and
STORAGE_REPLICATION_NET IP addresses. The
rsync daemon only listens on the
STORAGE_REPLICATION_NET IP address.
Public Network (Publicly routable IP range)
Provides public IP accessibility to the API endpoints
within the cloud infrastructure.
Minimum size: one IP address for each proxy
server.
Storage Network (RFC1918 IP Range, not publicly
routable)
Manages all inter-server communications within the
Object Storage infrastructure.
Minimum size: one IP address for each storage node and
proxy server.
Recommended size: as above, with room for expansion to
the largest your cluster size. For example, 255 or CIDR
/24.
Replication Network (RFC1918 IP Range, not publicly
routable)
Manages replication-related communications among storage
servers within the Object Storage infrastructure.
Recommended size: as for
STORAGE_LOCAL_NET.