Hi,
I'm looking at setting up a Swift cluster and am wondering if there is
any strong preference for one vs many config files in this case.
I note that devstack will create one config per device, e.g for a 2
device install:
$ ls -l /opt/stack/data/swift
total 16
lrwxrwxrwx 1 root root 35 Jun 11 11:50 1 ->
/opt/stack/data/swift/drives/sdb1/1
lrwxrwxrwx 1 root root 35 Jun 11 11:50 2 ->
/opt/stack/data/swift/drives/sdb1/2
$ ls -l /etc/swift/object-server/
total 16
-rw-r--r-- 1 stack stack 8148 Jun 11 11:49 1.conf
-rw-r--r-- 1 stack stack 8148 Jun 11 11:49 2.conf
$ head /etc/swift/object-server/1.conf
[DEFAULT]
# bind_ip = 0.0.0.0
bind_port = 6013
# bind_timeout = 30
# backlog = 4096
user = stack
swift_dir = /etc/swift
devices = /opt/stack/data/swift/1
mount_check = false
disable_fallocate = true
Whereas puppet-swift module seems to create just one, e.g:
$ ls -l /srv/node
total 0
drwxr-xr-x 5 swift swift 47 Jun 10 04:21 1
drwxr-xr-x 6 swift swift 62 Jun 10 04:21 2
$ head /etc/swift/object-server.conf
[DEFAULT]
devices = /srv/node
bind_ip = 192.168.5.181
bind_port = 6000
mount_check = false
user = swift
log_facility = LOG_LOCAL2
workers = 1
(both of these are Swift 1.13). Is there a scalability advantage to
having each device having its own port? Or any other reason to prefer
one of the other?
I'm hoping to use Puppet + puppet-swift to actually deploy Swift, and
actually run the proxy, account, container and object servers under
Apache mod_wsgi (which is my next struggle with Puppet no doubt...).
Cheers
Mark
_______________________________________________
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
