Oleg, thank you for the feedback. We'll definitely consider it.

Also, I'd like to share some basic mockups for node sort/filter/group
operations: http://postimg.org/gallery/2c32wcu8q/

On Mon, Feb 16, 2015 at 11:20 AM, Oleg Gelbukh <ogelb...@mirantis.com>
wrote:

> Julia,
>
> It would be nice to add grouping by Status to the existing 'Grouping'
> dropdown. It would save some time finding faulty/offline nodes in the list
> and performing bulk actions (like Delete) on them.
>
> Another useful feature for large deployments would be an ability to see IP
> addresses of nodes (including Management and Public addresses) in the UI
> and group/sort by those addresses.
>
> --
> Best regards,
> Oleg Gelbukh
> Mirantis Labs
>
> On Sat, Feb 14, 2015 at 11:27 AM, Julia Aranovich <jkirnos...@mirantis.com
> > wrote:
>
>> Hi All,
>>
>> Currently we [Fuel UI team] are planning the features of *sorting and
>> filtering of node list *to introduce it in 6.1 release.
>>
>> Now user can filter nodes just by it's name or MAC address and no sorters
>> are available. It's rather poor UI for managing 200+ nodes environment. So,
>> the current suggestion is to filter and sort nodes by the following
>> parameters:
>>
>>    1. name
>>    2. manufacturer
>>    3. IP address
>>    4. MAC address
>>    5. CPU
>>    6. memory
>>    7. disks total size (we need to think about "less than"/"more than"
>>    representation)
>>    8. interfaces speed
>>    9. status (Ready, Pending Addition, Error, etc.)
>>    10. roles
>>
>>
>> It will be a form-based filter. Items [1-4] should go to a single text
>> input and other go to a separate controls.
>> And also there is an idea to translate a user filter selection to a
>> query and add it to a location string. Like it's done for the logs search:
>> *#cluster/x/logs/type:local;source:api;level:info*.
>>
>> Please also note, that the changes we are thinking about should not
>> affect backend code.
>>
>>
>> I will be very grateful if you share your ideas about this or tell some
>> of the cases that would be useful to you at work with real deployments.
>> We would like to introduce really usefull tools based on your feedback.
>>
>>
>> Best regards,
>> Julia
>>
>> --
>> Kind Regards,
>> Julia Aranovich,
>> Software Engineer,
>> Mirantis, Inc
>> +7 (905) 388-82-61 (cell)
>> Skype: juliakirnosova
>> www.mirantis.ru
>> jaranov...@mirantis.com <jkirnos...@mirantis.com>
>>
>> __________________________________________________________________________
>> 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
>
>


-- 
Kind Regards,
Julia Aranovich,
Software Engineer,
Mirantis, Inc
+7 (905) 388-82-61 (cell)
Skype: juliakirnosova
www.mirantis.ru
jaranov...@mirantis.com <jkirnos...@mirantis.com>
__________________________________________________________________________
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

Reply via email to