Juju Charm - Swift storage
Go to file
OpenDev Sysadmins b9095031a1 OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

http://lists.openstack.org/pipermail/openstack-discuss/2019-March/003603.html
http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004920.html

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at https://opendev.org/ with any
questions you may have.
2019-04-19 19:29:40 +00:00
actions tweak imports in actions.py 2015-10-13 12:31:09 +00:00
charmhelpers Replace openstack.org git:// URLs with https:// 2019-03-24 20:33:12 +00:00
files [bradm] Adding nrpe checks, handle rsyncd config fragments 2014-10-30 00:52:15 -05:00
hooks Add hardening support 2016-03-24 11:11:58 +00:00
lib Use JUJU_MODEL_UUID for Juju 2.0 2016-05-24 16:29:55 +01:00
templates fix minor nit in template 2015-11-27 09:28:53 +00:00
tests Updates for stable branch creation 2016-04-21 16:56:55 +02:00
unit_tests Use JUJU_MODEL_UUID for Juju 2.0 2016-05-24 16:29:55 +01:00
.coveragerc Add actions.actions to coverage measuring and reporting. 2015-08-11 09:27:28 +01:00
.gitignore Resync charm-helpers 2016-03-03 11:50:13 +00: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 Resynced helpers 2014-03-20 13:47:54 +00:00
.testr.conf Add tox support 2015-11-03 14:03:25 +00:00
Makefile Use tox in Makefile targets 2016-03-15 20:14:13 -07:00
README.md updating swift-storage charm for landscape 2013-01-15 11:40:49 -07:00
actions.yaml Action Managed Upgrades 2015-09-22 15:58:18 -07:00
charm-helpers-hooks.yaml Updates for stable branch creation 2016-04-21 16:56:55 +02:00
charm-helpers-tests.yaml Updates for stable branch creation 2016-04-21 16:56:55 +02:00
config.yaml Add hardening support 2016-03-24 11:11:58 +00:00
copyright Update of all Havana / Saucy / python-redux work: 2013-10-15 12:48:33 +01:00
hardening.yaml Add hardening support 2016-03-24 11:11:58 +00:00
icon.svg Update icon.svg 2013-10-23 13:14:57 -07:00
metadata.yaml Update maintainer 2015-11-18 10:52:15 +00:00
requirements.txt Fix pbr requirement 2016-04-13 10:25:06 +00:00
revision Remove debug. 2013-07-19 14:13:59 -07:00
setup.cfg Add actions.actions to coverage measuring and reporting. 2015-08-11 09:27:28 +01:00
test-requirements.txt Update to charm-tools >= 2.0.0 2016-03-23 09:30:17 +00:00
tox.ini Update to charm-tools >= 2.0.0 2016-03-23 09:30:17 +00:00

README.md

Overview

This charm provides the swift-storage component of the OpenStack Swift object storage system. It can be deployed as part of its own standalone storage cluster or it can be integrated with the other OpenStack components, assuming those are also managed by Juju. For Swift to function, you'll also need to deploy an additional swift-proxy using the cs:precise/swift-proxy charm.

For more information about Swift and its architecture, visit the official project website at http://swift.openstack.org.

This charm was developed to support deploying multiple version of Swift on Ubuntu Precise 12.04, as they relate to the release series of OpenStack. That is, OpenStack Essex corresponds to Swift 1.4.8 while OpenStack Folsom shipped 1.7.4. This charm can be used to deploy either (and future) versions of Swift onto an Ubuntu Precise 12.04, making use of the Ubuntu Cloud Archive when needed.

Usage

This charm is quite simple. Its basic function is to get a storage device setup for swift usage, and run the container, object and account services. The deployment workflow for swift using this charm is covered in the README for the swift-proxy charm at cs:precise/swift-proxy. The following are deployment options to take into consideration when deploying swift-storage.

Zone assignment

If the swift-proxy charm is configured for manual zone assignment (recommended), the 'zone' option should be set for each swift-storage service being deployed. See the swift-proxy README for more information about zone assignment.

Storage

Swift storage nodes require access to local storage and filesystem. The charm takes a 'block-device' config setting that can be used to specify which storage device(s) to use. Options include:

  • 1 or more local block devices (eg, sdb or /dev/sdb). It's important that this device be the same on all machine units assigned to this service. Multiple block devices should be listed as a space-separated list of device nodes.
  • a path to a local file on the filesystem with the size appended after a pipe, eg "/etc/swift/storagedev1.img|5G". This will be created if it does not exist and be mapped to a loopback device. Good for development and testing.
  • "guess" can be used to tell the charm to do its best to find a local devices to use. EXPERIMENTAL

Multiple devices can be specified. In all cases, the resulting block device(s) will each be formatted as XFS file system and mounted at /srv/node/$devname.

Installation repository

The 'openstack-origin' setting allows Swift to be installed from installation repositories and can be used to setup access to the Ubuntu Cloud Archive to support installing Swift versions more recent than what is shipped with Ubuntu 12.04 (1.4.8). For more information, see config.yaml.