Forge Home


Deploy OpenStack Swift-all-in-one


10,086 latest version

1.5 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.2.6 (latest)
  • 0.2.3
  • 0.2.2
  • 0.2.1
  • 0.2.0
  • 0.1.0
  • 0.0.5
  • 0.0.4
  • 0.0.3
  • 0.0.2
  • 0.0.1
released Apr 4th 2014

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'serverascode-saio', '0.2.6'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add serverascode-saio
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install serverascode-saio --version 0.2.6

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



serverascode/saio — version 0.2.6 Apr 4th 2014


####Table of Contents

  1. Overview
  2. Setup - The basics of getting started with SAIO
  3. After Puppet has run
  4. Limitations - OS compatibility, etc.
  5. Development - Guide for contributing to the module


This module will install OpenStack Swift All-in-one (SAIO) on a single server. Currently the instructions for Swift-all-in-one list commands and files to copy and paste. This module automates running those commands and copying the files to install Swift-all-in-one quickly using Puppet.

Ideally it would be used with Vagrant as a place to develop and test OpenStack Swift, but without requiring multiple instances of Ubuntu 12.04 on which to run it. Instead all services run on one instance.


###What SAIO affects

This module will install many packages and services, so we are expecting that it would be used as part of a local virtualized development environment which can be built and destroyed many times over, ala Vagrant.

Some of the things it affects:

  • rsyncd
  • rsyslog
  • Creates a sparse file
  • Adds a loopback device
  • Installs all the packages needed for OpenStack Swift
  • Downloads, builds, and installs python-swiftclient and swift
  • Installs several helper bash scripts to start and use Swift
  • All the services required for OpenStack Swift will be running on this one server

###Beginning with SAIO

First, this module uses the Vcsrepo module and stdlib so those need to be installed.

puppet module install puppetlabs/vcsrepo
puppet module install puppetlabs/stdlib

We can now use the module by initiating use of the saio class and optionally provide parameters for swiftuser and swiftgroup:

node 'precise64' {
    class { 'saio':

There are a few optional parameters. Below are their defaults:


The package_cache_srv is a apt-cache-ng server's IP address. Usually I have a local vm running apt-cache-ng which projects like SAIO use to grab packages from instead of having to download them from the Internet every single time.

Post puppet

start_swift set to false

If start_swift was set to false, then the rings will not be created, and the various swift services will not be started, and will be left to be done by hand.

Once the puppet install has run its course, you can now use the bash scripts to generate the ring files and (hopefully) startup Swift. Note that swift is going to run as the vagrant user.

vagrant@precise64:/etc/swift$ remakerings 
Device d0r1z1-"" with 1.0 weight got id 0
Device d1r1z2-"" with 1.0 weight got id 1
Device d2r1z3-"" with 1.0 weight got id 2
Device d3r1z4-"" with 1.0 weight got id 3
Reassigned 1024 (100.00%) partitions. Balance is now 0.00.
Device d0r1z1-"" with 1.0 weight got id 0
Device d1r1z2-"" with 1.0 weight got id 1
Device d2r1z3-"" with 1.0 weight got id 2
Device d3r1z4-"" with 1.0 weight got id 3
Reassigned 1024 (100.00%) partitions. Balance is now 0.00.
Device d0r1z1-"" with 1.0 weight got id 0
Device d1r1z2-"" with 1.0 weight got id 1
Device d2r1z3-"" with 1.0 weight got id 2
Device d3r1z4-"" with 1.0 weight got id 3
Reassigned 1024 (100.00%) partitions. Balance is now 0.00.

Now all the Swift servers can be started:

vagrant@precise64:/etc/puppet$ startmain 
WARNING: Unable to increase file descriptor limit.  Running as non-root?
Starting proxy-server...(/etc/swift/proxy-server.conf)
Starting container-server...(/etc/swift/container-server/1.conf)
Starting container-server...(/etc/swift/container-server/2.conf)
Starting container-server...(/etc/swift/container-server/3.conf)
Starting container-server...(/etc/swift/container-server/4.conf)
Starting account-server...(/etc/swift/account-server/1.conf)
Starting account-server...(/etc/swift/account-server/2.conf)
Starting account-server...(/etc/swift/account-server/3.conf)
Starting account-server...(/etc/swift/account-server/4.conf)
Starting object-server...(/etc/swift/object-server/1.conf)
Starting object-server...(/etc/swift/object-server/2.conf)
Starting object-server...(/etc/swift/object-server/3.conf)
Starting object-server...(/etc/swift/object-server/4.conf)


vagrant@precise64:~$ startrest
WARNING: Unable to modify file descriptor limit.  Running as non-root?
Starting container-updater...(/etc/swift/container-server/1.conf)
Starting container-updater...(/etc/swift/container-server/2.conf)
Starting container-updater...(/etc/swift/container-server/3.conf)
Starting container-updater...(/etc/swift/container-server/4.conf)
Starting account-auditor...(/etc/swift/account-server/1.conf)
Starting account-auditor...(/etc/swift/account-server/2.conf)
Starting account-auditor...(/etc/swift/account-server/3.conf)
Starting account-auditor...(/etc/swift/account-server/4.conf)
Starting object-replicator...(/etc/swift/object-server/1.conf)
Starting object-replicator...(/etc/swift/object-server/2.conf)
Starting object-replicator...(/etc/swift/object-server/3.conf)
Starting object-replicator...(/etc/swift/object-server/4.conf)
Starting container-replicator...(/etc/swift/container-server/1.conf)
Starting container-replicator...(/etc/swift/container-server/2.conf)
Starting container-replicator...(/etc/swift/container-server/3.conf)
Starting container-replicator...(/etc/swift/container-server/4.conf)
Starting object-auditor...(/etc/swift/object-server/1.conf)
Starting object-auditor...(/etc/swift/object-server/2.conf)
Starting object-auditor...(/etc/swift/object-server/3.conf)
Starting object-auditor...(/etc/swift/object-server/4.conf)
Unable to locate config for object-expirer
Starting container-auditor...(/etc/swift/container-server/1.conf)
Starting container-auditor...(/etc/swift/container-server/2.conf)
Starting container-auditor...(/etc/swift/container-server/3.conf)
Starting container-auditor...(/etc/swift/container-server/4.conf)
Starting account-replicator...(/etc/swift/account-server/1.conf)
Starting account-replicator...(/etc/swift/account-server/2.conf)
Starting account-replicator...(/etc/swift/account-server/3.conf)
Starting account-replicator...(/etc/swift/account-server/4.conf)
Starting account-reaper...(/etc/swift/account-server/1.conf)
Starting account-reaper...(/etc/swift/account-server/2.conf)
Starting account-reaper...(/etc/swift/account-server/3.conf)
Starting account-reaper...(/etc/swift/account-server/4.conf)
Starting container-sync...(/etc/swift/container-server/1.conf)
Starting container-sync...(/etc/swift/container-server/2.conf)
Starting container-sync...(/etc/swift/container-server/3.conf)
Starting container-sync...(/etc/swift/container-server/4.conf)
Starting object-updater...(/etc/swift/object-server/1.conf)
Starting object-updater...(/etc/swift/object-server/2.conf)
Starting object-updater...(/etc/swift/object-server/3.conf)
Starting object-updater...(/etc/swift/object-server/4.conf)

####Once swift has started

If swift_start was set to true, or the remakerings, startmain, startrest commands were run by hand, then at this point swift should be fully operational and files can be uploaded.

Next, upload a file:

vagrant@precise64:~$ echo "swift is cool" > swift.txt
vagrant@precise64:~$ swift -A -U test:tester -K testing upload swifty swift.txt 
vagrant@precise64:~$ swift -A -U test:tester -K testing list swifty       


  • Only works on Ubuntu 12.04
  • Has only been tested with the official Vagrant Ubuntu Precise64 image


The github repository for this module can be found here so feel free to send a pull request. :)