e8966f4568
This defaults to 60s, and there is a constant background of errors making noise in the logs of the form: ERROR pipeline/output.go:121 Failed to publish events: write tcp 10.11.3.128:40770->10.11.128.94:5044: write: connection reset by peer Advice seems to be to increase client_inactivity_timout [1]. Tested in one environment and the log noise is gone. [1] https://discuss.elastic.co/t/solved-filebeat-logstash-connection-reset-by-peer/87012 Change-Id: Ia93867826a0c32192e3c37ea101f9a95a29e3d00
Team and repository tags
OpenStack-Ansible Operator Tooling
This repository is a collecting point for various scripts and tools which OpenStack-Ansible Developers and Operators have found to be useful and want to share and collaboratively improve.
The contents of this repository are not strictly quality managed and are only tested by hand by the contributors and consumers. Anyone using the tooling is advised to very clearly understand what it is doing before using it on a production environment.
- Documentation for the project can be found at:
- Release notes for the project can be found at:
-
https://docs.openstack.org/releasenotes/openstack-ansible-ops/
- The project source code repository is located at:
-
https://git.openstack.org/cgit/openstack/openstack-ansible-os_ops
- The project home is at:
Galaxy roles
OpenStack Ansible backup
This role will perform backups for OpenStack-Ansible deployments and it needs to run on the deploy node. It will backup data on container and then synchronize backup files to the deploy node.