Fuel for OpenStack

Separate /var and /var/log on the master node

Bug #1422856 reported by Fabrizio Soppelsa on 2015-02-17

This bug report is a duplicate of: Bug #1383741: File system corruption in containers on master node. Edit Remove

This bug affects 1 person

	Status	Importance	Assigned to	Milestone
Fuel for OpenStack	Won't Fix	High	Fuel for Openstack	Fuel for OpenStack 6.1
5.1.x	Confirmed	High	Fuel for Openstack	Fuel for OpenStack 5.1.1-updates
6.0.x	Confirmed	High	Fuel for Openstack	Fuel for OpenStack 6.0-updates

Bug Description

Separate /var and /var/log partitions on the master node.

See also https://blueprints.launchpad.net/fuel/+spec/fuel-master-separate-logs

Fabrizio Soppelsa (fsoppelsa) on 2015-02-17

Changed in fuel:
assignee:	nobody → Fuel for Openstack (fuel)
importance:	Critical → High

Revision history for this message

Bogdan Dobrelya (bogdando) wrote on 2015-02-18:

Won't fix for 6.1 as it is superseded by the blueprint. 5.1 and 6.0 backports is nice to have, if possible (backporting of features cannot be done, but this improvement should be considered to be backported I believe).

Changed in fuel:
status:	New → Won't Fix

Revision history for this message

Mike Scherbakov (mihgen) wrote on 2015-02-18:

Let's keep it confirmed in 6.1, otherwise we are going to miss it.
+1 for backporting it to 6.0.1.

Changed in fuel:
status:	Won't Fix → Confirmed

Revision history for this message

Andrey Korolyov (xdeller) wrote on 2015-02-18:

Quotas maybe? http://stackoverflow.com/questions/8148715/how-to-set-limit-on-directory-size-in-linux looks far more achievable for existing installs and more flexible for installations than even lvm vol.

Revision history for this message

Matthew Mosesohn (raytrac3r) wrote on 2015-02-18:

This is still superseded by blueprint for 6.1: https://blueprints.launchpad.net/fuel/+spec/fuel-master-separate-logs
Unless our bug handling strategy is changed, we're still handling features in blueprints and not in bugs. Moving back to wontfix for 6.1 again.