openstack/fuel-library
Code Issues Proposed changes
RETIRED, Fuel Library
10,681 Commits 4 Branches 3 Tags 267 MiB
6d90814c56
Go to file
Bogdan Dobrelya 6d90814c56 Fix missing OCF logging 
W/o this patch, the most of the OCF agents
sending their own logs to nothere.

This is a major issue, because we want to
be able troubleshoot and keep OCF events
in syslog and collected at remote logs
server(s) as well.

The solution is to enable HA_LOGTAG and
HA_LOGFACILITY for each OCF script shipped
with the Fuel.

DocImpact: Ops guide. Logging events from
Fuel OCF agents will be collected both
locally in the /var/log/daemon.log and remotely,
with the file names based on the agent "foo-agent"
name as the "ocf-foo-agent.log". Note, that the
RabbitMQ will continue to log its OCF events
to the lrmd.log due to backwards compatibility reasons.

Closes-bug: #1487083
Change-Id: Ida2d5fe31de42d31131e0f3a3e7b1a771caf8dfd
Signed-off-by: Bogdan Dobrelya <bdobrelia@mirantis.com>
2015-08-21 09:40:56 +02:00
debian Use neutron-netns-cleanup utility 2015-08-13 17:35:35 +03:00
deployment Merge "Fix horizon http haproxy configuration" 2015-08-19 11:53:42 +00:00
files Fix missing OCF logging 2015-08-21 09:40:56 +02:00
specs Merge "Use neutron-netns-cleanup utility" 2015-08-14 11:39:12 +00:00
tests Merge "Fix horizon http haproxy configuration" 2015-08-19 11:53:42 +00:00
utils Fix error in the noops tests framework 2015-08-11 16:14:15 +03:00
.gitignore Fix error in the noops tests framework 2015-08-11 16:14:15 +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

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.