Chapter 3. Object Storage service

1. Edit swift_params.yaml:

   cat > swift_params.yaml << EOF
   parameter_defaults:
       ExtraConfig:
         swift::proxy::copy::object_post_as_copy: False
   EOF

2. Include the parameter file when you deploy or update the overcloud:

   openstack overcloud deploy [... previous args ...] -e swift_params.yaml

Procedure

1. Install the supporting utility packages:

   # yum install xfsprogs rsync

2. Format the /dev/sdb and /dev/sdc devices as XFS:

   # mkfs.xfs /dev/sdb
   # mkfs.xfs /dev/sdc

3. Create the mount point directory structure:

   # mkdir -p /srv/node/sdb
   # mkdir -p /srv/node/sdc

4. Edit the /etc/fstab file and add the following data to it:

   /dev/sdb /srv/node/sdb xfs defaults 0 2
   /dev/sdc /srv/node/sdc xfs defaults 0 2

5. Mount the devices:

   # mount /srv/node/sdb
   # mount /srv/node/sdc

6. Create or edit the /etc/rsyncd.conf file to contain the following data:

   uid = swift
   gid = swift
   log file = /var/log/rsyncd.log
   pid file = /var/run/rsyncd.pid
   address = MANAGEMENT_INTERFACE_IP_ADDRESS
   
   [account]
   max connections = 2
   path = /srv/node/
   read only = False
   lock file = /var/lock/account.lock
   
   [container]
   max connections = 2
   path = /srv/node/
   read only = False
   lock file = /var/lock/container.lock
   
   [object]
   max connections = 2
   path = /srv/node/
   read only = False
   lock file = /var/lock/object.lock

   Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the management network on the storage node.

7. Start the rsyncd service and configure it to start when the system boots:

   # systemctl enable rsyncd.service
   # systemctl start rsyncd.service

Procedure

1. Install the packages:

   # yum install openstack-swift-account openstack-swift-container \
     openstack-swift-object

2. Edit the /etc/swift/account-server.conf file and complete the following actions:

   1. In the [DEFAULT] section, configure the bind IP address, bind port, user, configuration directory, and mount point directory:

      [DEFAULT]
      ...
      bind_ip = MANAGEMENT_INTERFACE_IP_ADDRESS
      bind_port = 6202
      user = swift
      swift_dir = /etc/swift
      devices = /srv/node
      mount_check = True

      Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the management network on the storage node.

   2. In the [pipeline:main] section, enable the healthcheck and recon modules:

      [pipeline:main]
      pipeline = healthcheck recon account-server

   3. In the [filter:recon] section, configure the recon cache directory:

      [filter:recon]
      use = egg:swift#recon
      ...
      recon_cache_path = /var/cache/swift

3. Open the default firewall port for the account service:

   # firewall-cmd --permanent --add-port=6202/tcp

4. Edit the /etc/swift/container-server.conf file and complete the following actions:

   1. In the [DEFAULT] section, configure the bind IP address, bind port, user, configuration directory, and mount point directory:

      [DEFAULT]
      ...
      bind_ip = MANAGEMENT_INTERFACE_IP_ADDRESS
      bind_port = 6201
      user = swift
      swift_dir = /etc/swift
      devices = /srv/node
      mount_check = True

      Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the management network on the storage node.

   2. In the [pipeline:main] section, enable the healthcheck and recon modules:

      [pipeline:main]
      pipeline = healthcheck recon container-server

   3. In the [filter:recon] section, configure the recon cache directory:

      [filter:recon]
      use = egg:swift#recon
      ...
      recon_cache_path = /var/cache/swift

5. Open the default firewall port for the container service:

   # firewall-cmd --permanent --add-port=6201/tcp

6. Edit the /etc/swift/object-server.conf file and complete the following actions:

   1. In the [DEFAULT] section, configure the bind IP address, bind port, user, configuration directory, and mount point directory:

      [DEFAULT]
      ...
      bind_ip = MANAGEMENT_INTERFACE_IP_ADDRESS
      bind_port = 6200
      user = swift
      swift_dir = /etc/swift
      devices = /srv/node
      mount_check = True

      Replace MANAGEMENT_INTERFACE_IP_ADDRESS with the IP address of the management network on the storage node.

   2. In the [pipeline:main] section, enable the healthcheck and recon modules:

      [pipeline:main]
      pipeline = healthcheck recon object-server

   3. In the [filter:recon] section, configure the recon_cache_path and the recon_lock_path directories:

      [filter:recon]
      use = egg:swift#recon
      ...
      recon_cache_path = /var/cache/swift
      recon_lock_path = /var/lock

7. Open the default firewall port for the object service:

   # firewall-cmd --permanent --add-port=6200/tcp

8. Ensure that the ownership of the mount point directory structure is correct:

   # chown -R swift:swift /srv/node

9. Create the recon directory and ensure proper ownership of it:

   # mkdir -p /var/cache/swift
   # chown -R root:swift /var/cache/swift
   # chmod -R 775 /var/cache/swift

1. In the dashboard, select Project > Object Store > Containers.
2. Click Create Container.

3. Specify the Container Name, and select one of the following in the Container Access field.

   Type	Description
   Private	Limits access to a user in the current project.
   Public	Permits API access to anyone with the public URL. However, in the dashboard, project users cannot see public containers and data from other projects.

4. Click Create Container.

1. In the dashboard, select Project > Object Store > Containers.
2. Click the name of the container to which you want to add the pseudo-folder.
3. Click Create Pseudo-folder.
4. Specify the name in the Pseudo-folder Name field, and click Create.

1. In the dashboard, select Project > Object Store > Containers.
2. Browse for the container in the Containers section, and ensure all objects have been deleted (see Section 3.4.6, “Deleting an object”).
3. Select Delete Container in the container’s arrow menu.
4. Click Delete Container to confirm the container’s removal.

1. In the dashboard, select Project > Object Store > Containers.
2. Click the name of the container in which the uploaded object will be placed; if a pseudo-folder already exists in the container, you can click its name.
3. Browse for your file, and click Upload Object.

4. Specify a name in the Object Name field:

   • Pseudo-folders can be specified in the name using a / character (for example, Images/myImage.jpg). If the specified folder does not already exist, it is created when the object is uploaded.
   • A name that is not unique to the location (that is, the object already exists) overwrites the object’s contents.
5. Click Upload Object.

1. In the dashboard, select Project > Object Store > Containers.
2. Click the name of the object’s container or folder (to display the object).
3. Click Upload Object.
4. Browse for the file to be copied, and select Copy in its arrow menu.

5. Specify the following:

   Field	Description
   Destination container	Target container for the new object.
   Path	Pseudo-folder in the destination container; if the folder does not already exist, it is created.
   Destination object name	New object’s name. If you use a name that is not unique to the location (that is, the object already exists), it overwrites the object’s previous contents.

6. Click Copy Object.

1. In the dashboard, select Project > Object Store > Containers.
2. Browse for the object, and select Delete Object in its arrow menu.
3. Click Delete Object to confirm the object’s removal.