Open Stack

On Fri, 16 Aug 2013 13:11:26 -0700
Steve Carter <svenphx at gmail.com> wrote:

> swift-ring-builder object.builder create 18 3 1
> swift-ring-builder object.builder add z2-10.30.177.41:6200/sdb 100
> swift-ring-builder object.builder add z3-10.30.177.41:6201/sdc 100
> swift-ring-builder object.builder add z4-10.30.177.41:6202/sdd 100

This is the so-called "SAIO" mode you're using here. The alternative
is to use a multinode style setup like so:

swift-ring-builder object.builder create 18 3 1
swift-ring-builder object.builder add z2-10.30.177.41:6200/sdb 100
swift-ring-builder object.builder add z3-10.30.177.41:6200/sdc 100
swift-ring-builder object.builder add z4-10.30.177.41:6200/sdd 100

SAIO brings up multiply servers in order to test Swift itself,
which includes several faked nodes. If you only want to test
how Swift works and test your apps for interpoperation, I would
rather use this "single multinode" instead.

If you insist on continuing with SAIO, you have to delete
/etc/swift/foo-server.conf and create /etc/swift/foo-server/N.conf
instead, and you have to use "vm_test_mode" parameter with the
corresponding adjustment to rsyncd.conf (see the SAIO doc for
details).

Good luck,
-- Pete