Juju Charm - Swift storage
Go to file
Edin Sarajlic a866308957 Update Makefile to reference Zaza and Python3
Change-Id: I0ab3e8abd4732ef2ccbcaeae58341796210a3af3
2020-08-27 09:40:37 +10:00
actions Upgrade the charm to py3 runtime 2018-10-24 14:57:05 +01:00
charmhelpers Release sync for 20.08 2020-07-27 20:59:50 +01:00
files Add monitoring for object-replicator logs disappearing 2020-07-21 15:31:06 -05:00
hooks Add monitoring for object-replicator logs disappearing 2020-07-21 15:31:06 -05:00
lib Ensure lockup_timeout is never < 2*rsync_timeout 2020-07-23 15:57:46 -04:00
templates Ensure lockup_timeout is never < 2*rsync_timeout 2020-07-23 15:57:46 -04:00
tests Add Victoria test bundles 2020-07-15 10:12:04 +02:00
unit_tests Ensure lockup_timeout is never < 2*rsync_timeout 2020-07-23 15:57:46 -04:00
.gitignore Add support for block device encryption 2018-05-08 12:52:37 +01:00
.gitreview OpenDev Migration Patch 2019-04-19 19:29:40 +00:00
.project Resynced helpers 2014-03-20 13:47:54 +00:00
.pydevproject Enable xenial/queens amulet testing 2018-03-12 09:34:00 +00:00
.stestr.conf Replace ostestr with stestr in testing framework. 2019-03-07 17:13:16 -05:00
.zuul.yaml Switch to Ussuri jobs 2019-12-26 17:18:48 +08:00
actions.yaml Action Managed Upgrades 2015-09-22 15:58:18 -07:00
charm-helpers-hooks.yaml Sync charm/ceph helpers, tox, and requirements 2019-09-30 22:42:05 -05:00
config.yaml Ensure lockup_timeout is never < 2*rsync_timeout 2020-07-23 15:57:46 -04:00
copyright Re-license charm as Apache-2.0 2016-07-01 18:15:00 +01:00
hardening.yaml Add hardening support 2016-03-24 11:11:58 +00:00
icon.svg Update charm icon 2017-08-02 17:25:40 +01:00
LICENSE Re-license charm as Apache-2.0 2016-07-01 18:15:00 +01:00
Makefile Update Makefile to reference Zaza and Python3 2020-08-27 09:40:37 +10:00
metadata.yaml Updates for 20.08 cycle start for groovy and libs 2020-06-02 14:37:32 +01:00
README.md Review and improve README 2020-02-24 22:08:42 -05:00
requirements.txt Release sync for 20.08 2020-07-27 20:59:50 +01:00
revision Remove debug. 2013-07-19 14:13:59 -07:00
setup.cfg Add Python 3 Train unit tests 2019-07-30 10:18:23 -04:00
test-requirements.txt Release sync for 20.08 2020-07-27 20:59:50 +01:00
tox.ini Sync helpers for 20.05 2020-05-18 14:50:38 +02:00

Overview

OpenStack Swift is a highly available, distributed, eventually consistent object/blob store.

The swift-storage charm deploys Swift's storage component. The charm's basic function is to initialise storage devices and manage the container, object, and account services. It works in tandem with the swift-proxy charm, which is used to add proxy nodes.

Usage

Configuration

This section covers common configuration options. See file config.yaml for the full list of options, along with their descriptions and default values.

zone

The zone option assigns a storage zone (an integer) to a storage node. A zone is associated with data replicas.

block-device

The block-device option specifies the device(s) that will be used on all machines associated with the application. Value types include:

  • an actual block device (e.g. 'sdb' or '/dev/sdb'). A space-separated list is used for multiple devices.
  • a path to a local file with the size appended after a pipe (e.g. '/etc/swift/storagedev1.img|5G'). The file will be created if necessary and be mapped to a loopback device. This is intended for development and testing purposes.

The resulting block device(s) will be XFS-formatted and use /srv/node/<device-name> as a mount point.

storage-region

The storage-region option specifies a storage region (an integer). It is used only for multi-region (global) clusters.

Deployment

Let file swift.yaml contain the deployment configuration:

    swift-proxy:
        zone-assignment: manual
        replicas: 3
    swift-storage-zone1:
        zone: 1
        block-device: /dev/sdb
    swift-storage-zone2:
        zone: 2
        block-device: /dev/sdb
    swift-storage-zone3:
        zone: 3
        block-device: /dev/sdb

Deploy the proxy and storage nodes:

juju deploy --config swift.yaml swift-proxy
juju deploy --config swift.yaml swift-storage swift-storage-zone1
juju deploy --config swift.yaml swift-storage swift-storage-zone2
juju deploy --config swift.yaml swift-storage swift-storage-zone3

Add relations between the proxy node and all storage nodes:

juju add-relation swift-proxy:swift-storage swift-storage-zone1:swift-storage
juju add-relation swift-proxy:swift-storage swift-storage-zone2:swift-storage
juju add-relation swift-proxy:swift-storage swift-storage-zone3:swift-storage

This will result in a three-zone cluster, with each zone consisting of a single storage node, thereby satisfying the replica requirement of three.

Storage capacity is increased by adding swift-storage units to a zone. For example, to add two storage nodes to zone '3':

juju add-unit -n 2 swift-storage-zone3

Note

: When scaling out ensure the candidate machines are equipped with the block devices currently configured for the associated application.

This charm will not balance the storage ring until there are enough storage zones to meet its minimum replica requirement, in this case three.

Appendix Swift usage in the OpenStack Charms Deployment Guide offers in-depth guidance for deploying Swift with charms. In particular, it shows how to set up a multi-region (global) cluster.

Actions

This section covers Juju actions supported by the charm. Actions allow specific operations to be performed on a per-unit basis.

  • openstack-upgrade
  • pause
  • resume

To display action descriptions run juju actions swift-storage.

Bugs

Please report bugs on Launchpad.

For general charm questions refer to the OpenStack Charm Guide.