Re: [openstack-dev] [Fuel] [UI] Sorting and filtering of node list
Aleksey, Thank you for clarification. Personally, I'm more interested in IP-based display/grouping/filtering of deployed nodes. And yes, it would be super-useful to have filtering in back-end and API, not only in UI. -- Best regards, Oleg On Fri, Feb 20, 2015 at 12:30 PM, Aleksey Kasatkin akasat...@mirantis.com wrote: Oleg, The problem with IP addresses (for all networks but admin-pxe) is that they are not available until deployment is started or /clusters/(?Pcluster_id\d+)/orchestrator/deployment/defaults/ is called. Nailgun just doesn't allocate them in advance. It was discussed some time before ( https://blueprints.launchpad.net/fuel/+spec/assign-ips-on-nodes-addition ) but not planned yet. There is no problem with admin-pxe addresses though. I agree that filtering is better be done in backend but it seems that it will not be done recently. AFAIC, it will not be 6.1. We didn't even decide what to do with API versioning yet. Aleksey Kasatkin On Thu, Feb 19, 2015 at 12:05 PM, Vitaly Kramskikh vkramsk...@mirantis.com wrote: I think all these operations for nodes (grouping, sorting, filtering) can be done on the backend, but we can do it completely on the UI side and shouldn't wait for backend implementation. We can switch to it after it becomes available. 2015-02-17 19:44 GMT+07:00 Sergey Vasilenko svasile...@mirantis.com: +1, sorting is should be... Paginating may be too, but not activated by default. /sv __ 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 -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __ 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] [Fuel] [UI] Sorting and filtering of node list
Oleg, The problem with IP addresses (for all networks but admin-pxe) is that they are not available until deployment is started or /clusters/(?Pcluster_id\d+)/orchestrator/deployment/defaults/ is called. Nailgun just doesn't allocate them in advance. It was discussed some time before ( https://blueprints.launchpad.net/fuel/+spec/assign-ips-on-nodes-addition ) but not planned yet. There is no problem with admin-pxe addresses though. I agree that filtering is better be done in backend but it seems that it will not be done recently. AFAIC, it will not be 6.1. We didn't even decide what to do with API versioning yet. Aleksey Kasatkin On Thu, Feb 19, 2015 at 12:05 PM, Vitaly Kramskikh vkramsk...@mirantis.com wrote: I think all these operations for nodes (grouping, sorting, filtering) can be done on the backend, but we can do it completely on the UI side and shouldn't wait for backend implementation. We can switch to it after it becomes available. 2015-02-17 19:44 GMT+07:00 Sergey Vasilenko svasile...@mirantis.com: +1, sorting is should be... Paginating may be too, but not activated by default. /sv __ 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 -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __ 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] [Fuel] [UI] Sorting and filtering of node list
I think all these operations for nodes (grouping, sorting, filtering) can be done on the backend, but we can do it completely on the UI side and shouldn't wait for backend implementation. We can switch to it after it becomes available. 2015-02-17 19:44 GMT+07:00 Sergey Vasilenko svasile...@mirantis.com: +1, sorting is should be... Paginating may be too, but not activated by default. /sv __ 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 -- Vitaly Kramskikh, Fuel UI Tech Lead, Mirantis, Inc. __ 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] [Fuel] [UI] Sorting and filtering of node list
+1 for that, it should be done with pagination too. IMHO pagination simple filtering by object's status can be done generically on the API side for all GET methods that derive from CollectionHandler. P. On 02/17/2015 10:18 AM, Lukasz Oles wrote: Hello Julia, I think node filtering and sorting is a great feature and it will improve UX, but we need to remember that with increasing number of nodes increases number of automation tasks. If fuel user want to automate something he will use fuel client not Fuel GUI. This is why I think sorting and filtering should be done on backend side. We should stop thinking that Fuel UI is the only way to interact with Fuel. Regards, On Sat, Feb 14, 2015 at 9: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: name manufacturer IP address MAC address CPU memory disks total size (we need to think about less than/more than representation) interfaces speed status (Ready, Pending Addition, Error, etc.) 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 __ 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] [Fuel] [UI] Sorting and filtering of node list
Hello Julia, I think node filtering and sorting is a great feature and it will improve UX, but we need to remember that with increasing number of nodes increases number of automation tasks. If fuel user want to automate something he will use fuel client not Fuel GUI. This is why I think sorting and filtering should be done on backend side. We should stop thinking that Fuel UI is the only way to interact with Fuel. Regards, On Sat, Feb 14, 2015 at 9: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: name manufacturer IP address MAC address CPU memory disks total size (we need to think about less than/more than representation) interfaces speed status (Ready, Pending Addition, Error, etc.) 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 __ 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 -- Łukasz Oleś __ 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] [Fuel] [UI] Sorting and filtering of node list
+1, sorting is should be... Paginating may be too, but not activated by default. /sv __ 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] [Fuel] [UI] Sorting and filtering of node list
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
Re: [openstack-dev] [Fuel] [UI] Sorting and filtering of node list
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
[openstack-dev] [Fuel] [UI] Sorting and filtering of node list
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
