Administrator’s Command Line Guide

3.2. Deploying Object Storage
OS 1000000000000003 ACTIVE 452 4f0038db65274507 10.30.29.124:52831
NS 0800000000000002 ACTIVE 647 fcbf5602197245da 10.30.27.69:56463
NS 0800000000000001 ACTIVE 452 4f0038db65274507 10.30.29.124:53044
NS 0800000000000000 ACTIVE 647 fcbf5602197245da 10.30.27.69:37876
12. Install one nginx Web server per each S3 endpoint you need. On nodes where you install nginx, replace the
contents of its configuration file /etc/nginx/conf.d/nginx.conf with the following (replace the IP addresses as
required):
upstream s3 {
server 127.0.0.1:9000; #S3 gateway 1 internal IP address
server 127.0.0.2:9000; #S3 gateway 2 internal IP address
server 127.0.0.3:9000; #S3 gateway 3 internal IP address
# Optional load balancing parameters (see
# http://nginx.org/en/docs/http/load_balancing.html)
}
server {
listen 80;
server_name 172.0.0.1; #S3 endpoint. If you have DNS configured,
#replace the IP address with the corresponding hostname.
client_max_body_size 5g;
#charset koi8-r;
#access_log /var/log/nginx/log/host.access.log main;
location / {
fastcgi_pass_header Connection-close;
fastcgi_pass s3;
fastcgi_no_cache 1;
include fastcgi_params;
fastcgi_request_buffering off;
fastcgi_max_temp_file_size 0;
}
13. Launch nginx:
# systemctl start nginx.service
# systemctl enable nginx.service
The object storage is deployed. Now you can add S3 users with the ostor-s3-admin tool. For example:
29