Object Server contains the actual objects seen in our OpenStack Object Storage environment and configuration of this is similar to configuring the Account Server and Container Server.
syntax 1
This is the configuration file used by the object server and other object background services, such as; replicator, updater and auditor.

Getting started..

Ensure that you are logged in to your swift virtual machine. To accomplish this, run:


To gain in-depth knowledge and be on par with practical experience, then explore  OpenStack Training course.

How to do it…

Subscribe to our youtube channel to get new updates..!

As with configuring the Container Server, we follow a similar procedure for Object Server, creating the four different configuration files that correspond to a particular port and an area on our disk.

1. We begin by creating an initial Object Server configuration file for our first node.
Edit /etc/swift/object-server/1.conf with the following contents:
devices = /srv/1/node
mount_check = false
bind_port = 6010
user = swift
log_facility = LOG_LOCAL2
pipeline = object-server
use = egg:swift#object
vm_test_mode = yes

2. We then use this file to create the remaining three virtual nodes, each specified with their appropriate unique values, as follows:
cd /etc/swift/object-server
sed -e “s/srv/1/srv/2/” -e “s/601/602/” -e
“s/LOG_LOCAL2/LOG_LOCAL3/” 1.conf | sudo tee -a 2.conf
sed -e “s/srv/1/srv/3/” -e “s/601/603/” -e
“s/LOG_LOCAL2/LOG_LOCAL4/” 1.conf | sudo tee -a 3.conf
sed -e “s/srv/1/srv/4/” -e “s/601/604/” -e
“s/LOG_LOCAL2/LOG_LOCAL5/” 1.conf | sudo tee -a 4.conf

How it works…

What we have accomplished here, is to create the first Object Server node configuration file, which we named 1.conf, under the /etc/swift/swift-container directory. This defined our Object Server for node 1, which will run on port 6010. We then took this file and made subsequent Object Servers run on their respective ports, with a search and replace, using sed. We end up with four files, under our swift-object configuration directory, which defines the following:
object-server 1: Port 6010, device /srv/1/node, Log Level LOCAL2
object-server 2: Port 6020, device /srv/2/node, Log Level LOCAL3
object-server 3: Port 6030, device /srv/3/node, Log Level LOCAL4
object-server 4: Port 6040, device /srv/4/node, Log Level LOCAL5

Explore OpenStack Sample Resumes! Download & Edit, Get Noticed by Top Employers!  Download Now!

Tip :

The three preceding sections have shown us how to configure Account Servers, Object Servers, and Container Servers, each running on their respective ports. These sections all ties up the modules configured in our rsyncd.conf file.