Default deployment does not use glance LV

Bug #1640362 reported by Dmitry Sutyagin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
Low
Alexey Stupnikov
Newton
Confirmed
Low
Fuel Sustaining

Bug Description

Bug found in MOS 7.0

When Ceph is not used, Fuel allocates "image storage" space on controllers by default. However, glance configuration uses Swift as the default backend, which in turn stores it's data not in /var/lib/glance, but in /srv/node, which is essentially root partition. Therefore images are stored in root partition, while /var/lib/glance (glance LV) is not used (for storage) and just takes space.

Tags: support
Changed in fuel:
assignee: nobody → MOS Maintenance (mos-maintenance)
tags: added: support
Changed in fuel:
assignee: MOS Maintenance (mos-maintenance) → Alexey Stupnikov (astupnikov)
milestone: none → 7.0-updates
importance: Undecided → High
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

It turns out that glance uses two kind of storages: image storage and image cache storage. Image storage is used to store objects and image chache is used as a temporary storage to cache images downloaded by users and load-balance their requests. Installed with default config, MOS uses separate partition as an image chache and uses swift as permanent image storage. IMO this information make this bug Invalid.

Changed in fuel:
status: New → Invalid
Revision history for this message
Dmitry Sutyagin (dsutyagin) wrote :

Fuel provides "Image storage" volume placement, not "image cache", AND image storage backend is not configurable, so user is misleaded and is not able to workaround via Fuel. Which makes this bug valid. Please also check for this behavior in newer versions.

Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

Dmitry, I see your point. I thought that reported problem was about misconfigured glance, or even about a buggy MOS component. It turns out, that some fuel properties have unclear/incorrect names; it is still a bug, but it is not going to be fixed in stable branches. I will set this bug's priority to low and nominate to Newton, so developers will decide whether they should fix it or leave as is.

Changed in fuel:
importance: High → Low
status: Invalid → Won't Fix
Revision history for this message
Alexey Stupnikov (astupnikov) wrote :

It turns out that we have to provide WA for bugs from support team. We have released a fix for bug #1537699 in 7.0-mu6. This fix basically allows to customize partitioning scheme on per-node basis, it may solve a problem with missing LVs. Another reported problem is incorrect LV names, the WA here is to edit nailgun fixtures for new deployments.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.