[openstack-dev] [Bareon][Fuel] Dynamic allocation algorithm
eli at mirantis.com
Thu Jan 14 16:19:32 UTC 2016
In addition I've generated several examples in order to show how current
prototype allocates the volumes .
On Wed, Jan 13, 2016 at 2:14 PM, Evgeniy L <eli at mirantis.com> wrote:
> Hi Artur,
> You are correct, we probably may consider using bytes instead of megabytes.
> Regarding to question "ssd vs hdd", user can describe which space is better
> to allocate on ssd and which is better on hdd, the mechanism is completely
> data driven,
> it can be done using "best_with_disks" , in fact it covers much more
> since user can build sets of disks where space can be allocated based on
> parameter of HW which discovery can provide.
> On Wed, Jan 13, 2016 at 1:56 PM, Artur Svechnikov <
> asvechnikov at mirantis.com> wrote:
>> Very good documentation. For Integer Solution you can use bytes instead
>> of megabytes. Hence N bytes will be unallocated in the worst case.
>> I didn't find solution for problem:
>> - Don’t allocate a single volume on ssd and hdd
>> Best regards,
>> Svechnikov Artur
>> On Tue, Jan 12, 2016 at 9:37 PM, Evgeniy L <eli at mirantis.com> wrote:
>>> For the last several weeks I've been working on algorithm (and prototype)
>>> for dynamic allocation of volumes on disks.
>>> I have some results  and would like to ask you to review it and
>>> some feedback.
>>> Our plan is to implement it as an external driver for Bareon .
>>>  http://bareon-allocator.readthedocs.org/en/latest/architecture.html
>>>  https://wiki.openstack.org/wiki/Bareon
>>> OpenStack Development Mailing List (not for usage questions)
>>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev