<div dir="ltr">Aleksey,<div><br></div><div>Thank you for clarification. Personally, I'm more interested in IP-based display/grouping/filtering of deployed nodes. </div><div><br></div><div>And yes, it would be super-useful to have filtering in back-end and API, not only in UI.</div><div><br></div><div>--</div><div>Best regards,</div><div>Oleg</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 20, 2015 at 12:30 PM, Aleksey Kasatkin <span dir="ltr"><<a href="mailto:akasatkin@mirantis.com" target="_blank">akasatkin@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div>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 ( <a href="https://blueprints.launchpad.net/fuel/+spec/assign-ips-on-nodes-addition" target="_blank">https://blueprints.launchpad.net/fuel/+spec/assign-ips-on-nodes-addition</a> ) but not planned yet. There is no problem with admin-pxe addresses though.<br><br></div>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.<br></div>We didn't even decide what to do with API versioning yet.<span class="HOEnZb"><font color="#888888"><br><div><div><br></div></div></font></span></div><div class="gmail_extra"><span class="HOEnZb"><font color="#888888"><br clear="all"><div><div><div dir="ltr">Aleksey Kasatkin
<br><br></div></div></div></font></span><div><div class="h5">
<br><div class="gmail_quote">On Thu, Feb 19, 2015 at 12:05 PM, Vitaly Kramskikh <span dir="ltr"><<a href="mailto:vkramskikh@mirantis.com" target="_blank">vkramskikh@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">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.<br></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div>2015-02-17 19:44 GMT+07:00 Sergey Vasilenko <span dir="ltr"><<a href="mailto:svasilenko@mirantis.com" target="_blank">svasilenko@mirantis.com</a>></span>:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">+1, sorting is should be...<div><br></div><div>Paginating may be too, but not activated by default.</div><span><font color="#888888"><div class="gmail_extra"><br clear="all"><div><div><div dir="ltr"><br><div>/sv</div><div><br></div></div></div></div><br></div></font></span></div>
<br></div></div><span>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></span></blockquote></div><span><font color="#888888"><br><br clear="all"><br>-- <br><div><div dir="ltr"><div><div dir="ltr">Vitaly Kramskikh,<br>Fuel UI Tech Lead,<br>Mirantis, Inc.</div></div></div></div>
</font></span></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div></div></div>
<br>__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br></blockquote></div><br></div>