Open Stack

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 <vkramskikh at 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 <svasilenko at 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-request at 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-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150220/d5b3ad86/attachment.html>