openstack/charm-swift-storage
Code Issues Proposed changes
Juju Charm - Swift storage
240 Commits 34 Branches 4 Tags 4.1 MiB
Python 98.4%
Perl 0.8%
Jinja 0.4%
Shell 0.3%
7cd7571364
Go to file
Edward Hope-Morley 7cd7571364 [trivial] Cleanup config.yaml 
Partially-Closes-Bug: 1473426
2015-07-10 15:13:35 +01:00
files [bradm] Adding nrpe checks, handle rsyncd config fragments 2014-10-30 00:52:15 -05:00
hooks [jjo, r=] fix nrpe SWIFT_SVCS for "swift-" prefix, fixes lp#1470641 2015-07-01 17:53:27 -03:00
templates [bradm] Fixed rsync to use /etc/rsync-juju.d, check if host_context is defined before using it 2014-11-06 17:38:43 +10:00
tests [gnuoy,trivial] Pre-release charmhelper sync 2015-04-23 15:55:08 +01:00
unit_tests Test for settings on /srv/node 2015-04-02 11:56:27 -07:00
.bzrignore Ignore .coverage 2014-08-13 14:48:12 +01:00
.coveragerc Update to 100% coverage. 2013-07-19 13:44:37 -07:00
.project Resynced helpers 2014-03-20 13:47:54 +00:00
.pydevproject Resynced helpers 2014-03-20 13:47:54 +00:00
charm-helpers-hooks.yaml Merged next branch in 2015-01-09 09:59:47 +00:00
charm-helpers-tests.yaml Move charm-helpers.yaml to charm-helpers-hooks.yaml and 2014-07-08 15:36:53 +00:00
config.yaml [trivial] Cleanup config.yaml 2015-07-10 15:13:35 +01:00
copyright Update of all Havana / Saucy / python-redux work: 2013-10-15 12:48:33 +01:00
icon.svg Update icon.svg 2013-10-23 13:14:57 -07:00
Makefile auto Makefile test target (amulet): bump juju test timeout to 2700s (same value as the juju-deployer default). Also remove explicit test names, which will cause all +x files in ./tests to be executed (as bundletester does by default). 2015-04-16 21:32:08 +00:00
metadata.yaml [bradm] Adding nrpe checks, handle rsyncd config fragments 2014-10-30 00:52:15 -05:00
README.md updating swift-storage charm for landscape 2013-01-15 11:40:49 -07:00
revision Remove debug. 2013-07-19 14:13:59 -07:00
setup.cfg Update to 100% coverage. 2013-07-19 13:44:37 -07: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.