RETIRED, Fuel Library
Go to file
Bartłomiej Piotrowski eb3e29caec Rework logrotate configuration
- instead of rotating logs daily and weekly, run the script every 15
  minutes
- merge weekly and daily configuration files
- rotate logs basing on two criteria: age (a week; only if file is
  bigger than 10M on master or 5MB on remote nodes) and size (rotate the file
  always if its size exceedes 100M on master or 20M on remote nodes, regardless
  its age)
- use dateformat to make rotated logs' filenames more readable;
  as logrotate supports only year, month, day and unix epoch, use them
  all
- fix a lot of lint complaints, including aligments, curly braces and
  proper quoting; give logrotate related files more intuitive names
- dump.log has been renamed to shotgun.log (LP#1318516)
- check if there is no logrotate instances running before executing
  cronjob

DocImpact: ops guide

Change-Id: Ie7040ebcdc1a3329ebb7507807e5c27f0c87b484
Closes-Bug: 1382515
Closes-Bug: 1446790
2015-04-22 21:28:29 +00:00
debian Update deb version to 6.1.0 2015-04-22 14:48:58 +03:00
deployment/puppet Rework logrotate configuration 2015-04-22 21:28:29 +00:00
files Backward-compatible commit for packaging of fuel-library 2015-04-16 11:23:29 +03:00
specs Set version of Fuel to 6.1 everwhere 2015-04-16 19:41:30 +03:00
tests/noop Merge "Add ceph-compute task" 2015-04-22 12:10:14 +00:00
utils Merge "Improve Noop tests" 2015-04-22 08:51:12 +00:00
.gitignore Add the task graph plotting tool 2015-03-02 17:32:04 +03:00
.gitreview Setup git-review 2013-12-11 14:31:13 +04:00
CHANGELOG Edit Changelog 2013-05-23 13:38:03 +03:00
LICENSE LICENCE added 2014-06-05 20:00:54 +00:00
README.md RabbitMQ FAQ notes prettified 2013-05-08 23:19:41 +04:00

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 doesnt 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.