dd0eacc460
- use flock to ensure that only one instance of fuel-logrotate is running - combine centos and ubuntu versions of fuel-logrotate to a single file - remove unused versions of fuel-logrotate file - enable delayed compression in system-wide logrotate.conf to avoid race condition between fuel-logrotate and regular logrotate - enable delaycompress also on master node - default minsize (30M) and maxsize (100M) in system-wide logrotate.conf - use file_line for logrotate.conf updates - use bash to execute fuel-logrotate - fix path to cron's logrotate script in logrotate-debug This commit changes default behavior of logrotate by enabling compress and delaycompress. The result is that compression is enabled for all log files managed by logrotate and rotated logs are compressed only on the next rotation. It allows us to resolve rotation cycle that might happen when both regular logrotate and fuel-logrotate were executed at the same time, causing both to rotate the same file. Closes-Bug: 1461400 Doc-Impact: ops guide Change-Id: I94c497a8916fa6fac87ea2ddc51f6de56ab73f98 Co-Authored-By: Alex Schultz <aschultz@mirantis.com> |
||
|---|---|---|
| debian | ||
| deployment/puppet | ||
| files | ||
| specs | ||
| tests/noop | ||
| utils | ||
| .gitignore | ||
| .gitreview | ||
| CHANGELOG | ||
| LICENSE | ||
| README.md | ||
README.md
Fuel is the Ultimate Do-it-Yourself Kit for OpenStack
Purpose built to assimilate the hard-won experience of our services team, it contains the tooling, information, and support you need to accelerate time to production with OpenStack cloud.
OpenStack is a very versatile and flexible cloud management platform. By exposing its portfolio of cloud infrastructure services – compute, storage, networking and other core resources — through ReST APIs, it enables a wide range of control over these services, both from the perspective of an integrated Infrastructure as a Service (IaaS) controlled by applications, as well as automated manipulation of the infrastructure itself.
This architectural flexibility doesn’t set itself up magically; it asks you, the user and cloud administrator, to organize and manage a large array of configuration options. Consequently, getting the most out of your OpenStack cloud over time – in terms of flexibility, scalability, and manageability – requires a thoughtful combination of automation and configuration choices.
Mirantis Fuel for OpenStack was created to solve exactly this problem.