Re: [openstack-dev] [Bareon][Fuel] Dynamic allocation algorithm

2016-01-14 Thread Evgeniy L 
Hi,

In addition I've generated several examples in order to show how current
prototype allocates the volumes [0].

Thanks,

[0] http://bareon-allocator.readthedocs.org/en/latest/examples.html


On Wed, Jan 13, 2016 at 2:14 PM, Evgeniy L  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" [0], in fact it covers much more
> cases,
> since user can build sets of disks where space can be allocated based on
> any
> parameter of HW which discovery can provide.
>
> Thanks,
>
> [0]
> http://bareon-allocator.readthedocs.org/en/latest/architecture.html#best-with-disks
>
> On Wed, Jan 13, 2016 at 1:56 PM, Artur Svechnikov <
> asvechni...@mirantis.com> wrote:
>
>> Hi.
>>
>> 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  wrote:
>>
>>> Hi,
>>>
>>> For the last several weeks I've been working on algorithm (and prototype)
>>> for dynamic allocation of volumes on disks.
>>>
>>> I have some results [0] and would like to ask you to review it and
>>> provide
>>> some feedback.
>>>
>>> Our plan is to implement it as an external driver for Bareon [1].
>>>
>>> Thanks,
>>>
>>> [0] http://bareon-allocator.readthedocs.org/en/latest/architecture.html
>>> [1] https://wiki.openstack.org/wiki/Bareon
>>>
>>>
>>>
>>> __
>>> OpenStack Development Mailing List (not for usage questions)
>>> Unsubscribe:
>>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Bareon][Fuel] Dynamic allocation algorithm

2016-01-13 Thread Artur Svechnikov 
Hi.

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  wrote:

> Hi,
>
> For the last several weeks I've been working on algorithm (and prototype)
> for dynamic allocation of volumes on disks.
>
> I have some results [0] and would like to ask you to review it and provide
> some feedback.
>
> Our plan is to implement it as an external driver for Bareon [1].
>
> Thanks,
>
> [0] http://bareon-allocator.readthedocs.org/en/latest/architecture.html
> [1] https://wiki.openstack.org/wiki/Bareon
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Bareon][Fuel] Dynamic allocation algorithm

2016-01-13 Thread Evgeniy L 
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" [0], in fact it covers much more
cases,
since user can build sets of disks where space can be allocated based on any
parameter of HW which discovery can provide.

Thanks,

[0]
http://bareon-allocator.readthedocs.org/en/latest/architecture.html#best-with-disks

On Wed, Jan 13, 2016 at 1:56 PM, Artur Svechnikov 
wrote:

> Hi.
>
> 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  wrote:
>
>> Hi,
>>
>> For the last several weeks I've been working on algorithm (and prototype)
>> for dynamic allocation of volumes on disks.
>>
>> I have some results [0] and would like to ask you to review it and provide
>> some feedback.
>>
>> Our plan is to implement it as an external driver for Bareon [1].
>>
>> Thanks,
>>
>> [0] http://bareon-allocator.readthedocs.org/en/latest/architecture.html
>> [1] https://wiki.openstack.org/wiki/Bareon
>>
>>
>> __
>> OpenStack Development Mailing List (not for usage questions)
>> Unsubscribe:
>> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

[openstack-dev] [Bareon][Fuel] Dynamic allocation algorithm

2016-01-12 Thread Evgeniy L 
Hi,

For the last several weeks I've been working on algorithm (and prototype)
for dynamic allocation of volumes on disks.

I have some results [0] and would like to ask you to review it and provide
some feedback.

Our plan is to implement it as an external driver for Bareon [1].

Thanks,

[0] http://bareon-allocator.readthedocs.org/en/latest/architecture.html
[1] https://wiki.openstack.org/wiki/Bareon
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev