swift replication on undercloud

[Joe Talerico]

Swift has tons of IO on the undercloud which is related to replication and auditing, when there is no need to have replication and auditing since the undercloud is using only a single replica in Swift.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/385846

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/385846
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=312f42a8c0cc5975e1338225d6b7ca6c9c30e6a8
Submitter: Jenkins
Branch: master

commit 312f42a8c0cc5975e1338225d6b7ca6c9c30e6a8
Author: Christian Schwede <email address hidden>
Date: Thu Oct 13 11:08:11 2016 +0200

    Disable Swift auditors and replicators on the undercloud

    Swift is using only a single replica on the undercloud. Therefore
    recovering from a corrupted or lost object is not possible, and running
    replicators and auditors only wastes resources.

    Closes-Bug: 1632885
    Change-Id: Ic93082282e9ea481c13832f8ce1265a47f0ef3d5

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/389638

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/389638
Committed: https://git.openstack.org/cgit/openstack/instack-undercloud/commit/?id=29b6796c2485f5f3cd2fb692450ebe6cb3c7ec06
Submitter: Jenkins
Branch: stable/newton

commit 29b6796c2485f5f3cd2fb692450ebe6cb3c7ec06
Author: Christian Schwede <email address hidden>
Date: Thu Oct 13 11:08:11 2016 +0200

    Disable Swift auditors and replicators on the undercloud

    Swift is using only a single replica on the undercloud. Therefore
    recovering from a corrupted or lost object is not possible, and running
    replicators and auditors only wastes resources.

    Closes-Bug: 1632885
    Change-Id: Ic93082282e9ea481c13832f8ce1265a47f0ef3d5
    (cherry picked from commit 312f42a8c0cc5975e1338225d6b7ca6c9c30e6a8)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/instack-undercloud 5.1.0 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/instack-undercloud 6.0.0.0b2 development milestone.

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: master
Review: https://review.openstack.org/610012

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/610012
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=47f93e1792a99f2226b5842978cd99dd2d9ef3fb
Submitter: Zuul
Branch: master

commit 47f93e1792a99f2226b5842978cd99dd2d9ef3fb
Author: Bogdan Dobrelya <email address hidden>
Date: Fri Oct 12 13:48:22 2018 +0200

    Disable Swift auditors/replicators on undercloud

    Maintain parity with instack-undercloud
    Ic93082282e9ea481c13832f8ce1265a47f0ef3d5

    Swift is using only a single replica on the undercloud. Therefore
    recovering from a corrupted or lost object is not possible, and running
    replicators and auditors only wastes resources. And may create some
    trouble. For example, the DB replicators and auditors will lock the DB,
    and new objects won't be stored during that time.

    Related-Bug: #1632885
    Closes-Bug: #1797167

    Change-Id: I584cdb03b99721fbdc28bf7f6019d914586341d2
    Signed-off-by: Bogdan Dobrelya <email address hidden>

[OpenStack Infra (hudson-openstack)]

Related fix proposed to branch: stable/rocky
Review: https://review.openstack.org/610909

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/610909
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=9f0975a52c33abcb4ad74a246837b321de3b4ffc
Submitter: Zuul
Branch: stable/rocky

commit 9f0975a52c33abcb4ad74a246837b321de3b4ffc
Author: Bogdan Dobrelya <email address hidden>
Date: Fri Oct 12 13:48:22 2018 +0200

    Disable Swift auditors/replicators on undercloud

    Maintain parity with instack-undercloud
    Ic93082282e9ea481c13832f8ce1265a47f0ef3d5

    Swift is using only a single replica on the undercloud. Therefore
    recovering from a corrupted or lost object is not possible, and running
    replicators and auditors only wastes resources. And may create some
    trouble. For example, the DB replicators and auditors will lock the DB,
    and new objects won't be stored during that time.

    Related-Bug: #1632885
    Closes-Bug: #1797167

    Change-Id: I584cdb03b99721fbdc28bf7f6019d914586341d2
    Signed-off-by: Bogdan Dobrelya <email address hidden>
    (cherry picked from commit 47f93e1792a99f2226b5842978cd99dd2d9ef3fb)