allow tuning of node_timeout

[Andrea Ieri]

There is currently no way to move past the default node_timeout(s) for accounts/containers/objects.
In heavily loaded clouds the default of 10 seconds may prove to be too short, but the charm does not allow operators to tune such setting.

[Edward Hope-Morley (hopem)]

Need to ensure http_timeout is set to a value higher than node_timeout as well (as per [0])

[0] https://github.com/openstack/swift/blob/2.25.0/etc/object-server.conf-sample#L275

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/734147

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/20.05
Review: https://review.opendev.org/734589

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/734147
Committed: https://git.openstack.org/cgit/openstack/charm-swift-storage/commit/?id=2c7acd2dfc6391584052d39d8428bbacb68720ae
Submitter: Zuul
Branch: master

commit 2c7acd2dfc6391584052d39d8428bbacb68720ae
Author: Edward Hope-Morley <email address hidden>
Date: Mon Jun 8 17:43:43 2020 +0100

    Allow configuring node_timeout

    Swift default is used if no config provided.
    As per swift docs, if node_timeout is set,
    http_timeout ensured to be greater than
    node_timeout.

    Change-Id: Idf5945a6c2f64fcad8f2ab7cb137f1ce1f1dc424
    Closes-Bug: #1878657

[OpenStack Infra (hudson-openstack)]

Change abandoned by Dmitrii Shcherbakov (<email address hidden>) on branch: stable/20.05
Review: https://review.opendev.org/734589
Reason: Actually, we can abandon this now that 20.08 is out.