[ Pobierz całość w formacie PDF ]
network should connect the outside world to the proxy servers, and the storage network is
intended to be isolated on a private network or multiple private networks.
Database: For OpenStack Object Storage, a SQLite database is part of the OpenStack
Object Storage container and account management process.
Permissions: You can install OpenStack Object Storage either as root or as a user with sudo
permissions if you configure the sudoers file to enable all the permissions.
58
OpenStack Install and Deploy Jun 18, 2012 Essex
Manual
Object Storage Network Planning
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 document refers to two networks. One is a Public Network for connecting to the
Proxy server, and the second is a Storage Network that is not accessible from outside the
cluster, to which all of the nodes are connected. 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.
Public Network (Publicly routable IP range): This network is utilized for providing Public IP
accessibility to the API endpoints within the cloud infrastructure.
Minimum size: 8 IPs (CIDR /29)
Storage Network (RFC1918 IP Range, not publicly routable): This network is utilized for all
inter-server communications within the Object Storage infrastructure.
Recommended size: 255 IPs (CIDR /24)
Example Object Storage Installation Architecture
" node - a host machine running one or more OpenStack Object Storage services
" Proxy node - node that runs Proxy services
" Auth node - an optionally separate node that runs the Auth service separately from the
Proxy services
" Storage node - node that runs Account, Container, and Object services
" Ring - a set of mappings of OpenStack Object Storage data to physical devices
To increase reliability, you may want to add additional Proxy servers for performance.
This document describes each Storage node as a separate zone in the ring. It is
recommended to have a minimum of 5 zones. A zone is a group of nodes that is as isolated
as possible from other nodes (separate servers, network, power, even geography). The ring
guarantees that every replica is stored in a separate zone. This diagram shows one possible
configuration for a minimal installation.
59
OpenStack Install and Deploy Jun 18, 2012 Essex
Manual
Installing OpenStack Object Storage on Ubuntu
Though you can install OpenStack Object Storage for development or testing purposes on a
single server, a multiple-server installation enables the high availability and redundancy you
want in a production distributed object storage system.
If you would like to perform a single node installation on Ubuntu for development
purposes from source code, use the Swift All In One instructions or DevStack. See http://
swift.openstack.org/development_saio.html for manual instructions or http://devstack.org
for all-in-one including authentication and a dashboard.
Before You Begin
Have a copy of the Ubuntu Server installation media on hand if you are installing on a new
server.
This document demonstrates installing a cluster using the following types of nodes:
" One Proxy node which runs the swift-proxy-server processes and may also run the
optional swauth or tempauth services, this walkthrough uses the Identity service code-
named Keystone. The proxy server serves proxy requests to the appropriate Storage
nodes.
" Five Storage nodes that run the swift-account-server, swift-container-server, and swift-
object-server processes which control storage of the account databases, the container
databases, as well as the actual stored objects.
60
OpenStack Install and Deploy Jun 18, 2012 Essex
Manual
Note
Fewer Storage nodes can be used initially, but a minimum of 5 is recommended
for a production cluster.
General Installation Steps
1.Install the baseline operating system, such as Ubuntu Server (10.04 through 12.04) or
RHEL, CentOS, or Fedora, on all nodes.
2.Install the swift service and openSSH.
# yum install openstack-swift openstack-swift-proxy openstack-swift-account
openstack-swift-container openstack-swift-object memcached
3.Create and populate configuration directories on all nodes:
mkdir -p /etc/swift
chown -R swift:swift /etc/swift/
4.Create /etc/swift/swift.conf:
[swift-hash]
# random unique string that can never change (DO NOT LOSE)
swift_hash_path_suffix = fLIbertYgibbitZ
Note
The suffix value in /etc/swift/swift.conf should be set to some random
string of text to be used as a salt when hashing to determine mappings in the
ring. This file should be the same on every node in the cluster!
Next, set up your storage nodes, proxy node, and an auth node, in this walkthrough we'll
use the OpenStack Identity Service, Keystone, for the common auth piece.
Installing and Configuring the Storage Nodes
Note
OpenStack Object Storage should work on any modern filesystem that
supports Extended Attributes (XATTRS). We currently recommend XFS as
it demonstrated the best overall performance for the swift use case after
[ Pobierz całość w formacie PDF ]