Open Stack

Matt, I'd like to keep the v2 api discussion in the end of our design
sessions track to have enough input on other areas. IMO we should
discuss first what we need to have and then how it'll looks like.

On Fri, Apr 25, 2014 at 9:29 PM, Matthew Farrellee <matt at redhat.com> wrote:
> On 04/24/2014 10:51 AM, Sergey Lukjanov wrote:
>>
>> Hey folks,
>>
>> I've pushed the draft schedule for Sahara sessions on ATL design
>> summit. The description isn't fully completed, I'm working on it. I'll
>> do it till the end of week and add an etherpad to each session.
>>
>> Sahara folks, please, take a look on a schedule and share your
>> thoughts / comments.
>>
>> Thanks.
>>
>> http://junodesignsummit.sched.org/overview/type/sahara+%28ex-savanna%29
>
>
> will you swap v2-api and scalable slots? part of it will flow into ux re
> image-registry.
>
> maybe add some "error handling / state machine" to the ux improvements
>
> best,
>
>
> matt
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



-- 
Sincerely yours,
Sergey Lukjanov
Sahara Technical Lead
(OpenStack Data Processing)
Mirantis Inc.