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/(?P<cluster_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