diff options
| author | Qiu Yu <qiuyu@ebaysf.com> | 2016-01-29 12:06:31 -0700 |
|---|---|---|
| committer | Qiu Yu <qiuyu@ebaysf.com> | 2016-02-02 02:14:31 +0800 |
| commit | b209da1306c454366210e88f5a7a0e14bdd88fc4 (patch) | |
| tree | a50786fc295cf36729ad16ad08918a84a92a8daf /tools | |
| parent | 1057dcd50a8963e5220f7ca5cc7b66183a06340e (diff) | |
| download | kolla-b209da1306c454366210e88f5a7a0e14bdd88fc4.tar.gz kolla-b209da1306c454366210e88f5a7a0e14bdd88fc4.zip | |
Fix Swift for multinode P+ACO deployment
Current Swift playbook is based on the preassumption of AIO setup.
However, if one goes with default multinode setup
(ansible/inventory/multinode), it follows the P + ACO deployment model,
which proxy-server runs on controller nodes where ACO
(account/container/object services) run on storage nodes.
It will break because swift proxy-server no longer has access (it
shouldn't have) to /srv/node path. This change ensure disk mounting part
only happens on storage node. It also moves chown from proxy-server
Dockerfile to rsyncd because no matter with PACO, P+ACO or P+A+C+O
model, rsyncd is always running on each storage node.
Change-Id: I3aa20454902caa9c84d3901bb91e4e4c93ac5f34
Partially-Implements: blueprint swift-physical-disk
Closes-Bug: #1537544
Diffstat (limited to 'tools')
0 files changed, 0 insertions, 0 deletions