Add option to choose partition alignment mode

Bug #1593332 reported by OpenStack Infra
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bareon
New
Undecided
Unassigned

Bug Description

https://review.openstack.org/330112
Dear bug triager. This bug was created since a commit was marked with DOCIMPACT.
Your project "openstack/bareon" is set up so that we directly report the documentation bugs against it. If this needs changing, the docimpact-group option needs to be added for the project. You can ask the OpenStack infra team (#openstack-infra on freenode) for help if you need to.

commit d2185b1316cf72e1e899eb309e4bffcdd7ff8a0e
Author: Alexander Gordeev <email address hidden>
Date: Thu May 5 15:52:40 2016 +0300

    Add option to choose partition alignment mode

    Under certain circumstances due to that alignment, the end of
    particular partition could cross 1M boundary. And due to actual
    partition' bounderies being rounded up, fuel-agent mistakenly
    assumes that partition couldn't fit within provided boundaries
    and raises errors.WrongPartitionSchemeError.

    However, some h/w data storages are well known for reporting
    relatively huge optimal IO sizes (16M or even bigger), so the 1M
    room can't be enough. Thus, optimal aligning is not an option.
    In such cases, it's better to proceed with minimal mode.

    It's the minimum aligment needed to align the partition properly
    to physical blocks which avoids performance degradation.

    Partial-Bug: #1543233
    DocImpact

    Conflicts:

     bareon/drivers/deploy/nailgun.py
     fuel_agent/tests/test_manager.py

    Change-Id: I1dd94731f497f3deb47cec9a23957e3706c2fb3b

Tags: bareon doc
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.