Open Stack

If "new design" is the design you've proposed in the original email, then
no - we'll have to reopen the bug and then revert the change again.

2016-07-27 11:36 GMT+03:00 Dmitry Dmitriev <dmdmitriev at mirantis.com>:

> Hello Vitaly,
>
> Thank you for this answer.
> The main question here is the business logic.
> Do we have to use new design or don’t.
>
> With best regards, Dmitry
>
> On 26 Jul 2016, at 17:47, Vitaly Kramskikh <vkramskikh at mirantis.com>
> wrote:
>
> Hi, Dmitry,
>
> Your design seems to be similar to one of our attempts to fix this bug:
> https://review.openstack.org/#/c/280737/. Though this fix was reverted,
> because it led to the bug with a higher priority:
> https://bugs.launchpad.net/fuel/+bug/1556909. So your proposed design
> would lead to reopening of this bug.
>
> 2016-07-19 11:06 GMT+03:00 Dmitry Dmitriev <dmdmitriev at mirantis.com>:
>
>> Hello All!
>>
>> We have a very old bug about the Capacity table on the Dashboard tab of
>> environment in Fuel:
>>
>> https://bugs.launchpad.net/fuel/+bug/1375750
>>
>> Current design:
>>
>> https://drive.google.com/open?id=0Bxi_JFs365mBNy1WT0xQT253SWc
>>
>> It shows the full capacity (CPU/Memory/HDD) of all discovered by Fuel
>> nodes.
>>
>> New design:
>>
>> https://drive.google.com/open?id=0Bxi_JFs365mBaWZ0cUtla3N6aEU
>>
>> It contains compute node CPU/Memory capacity and Ceph disk capacity only.
>>
>> New design pros:
>> - cloud administrator can easily estimate all available resources for
>> cloud instances
>>
>> New design cons:
>> - if cloud doesn’t use Ceph then HDD value is zero
>>
>> What do you think about the new design?
>>
>> With best regards, Dmitry
>>
>>
>
>
> --
> Vitaly Kramskikh,
> Fuel UI Tech Lead,
> Mirantis, Inc.
>
>
>


-- 
Vitaly Kramskikh,
Fuel UI Tech Lead,
Mirantis, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160727/0772afe5/attachment.html>