Open Stack

I would like to point out that the unified SDK has a different target
audience from the existing clients. Application developers who want to work
with OpenStack APIs are far different from those who are trying to build
OpenStack.

For example, application developers don't know what keystone, nova, or
swift are and these names will confuse them creating a barrier for them to
build great things against OpenStack. The language usage matters in a good
SDK.

Given the different target audiences there's room for overlap when trying
to create great experiences for two segments.



On Wed, Feb 12, 2014 at 10:32 AM, Jesse Noller
<jesse.noller at rackspace.com>wrote:

>
> On Feb 12, 2014, at 9:07 AM, Ed Leafe <ed at openstack.org> wrote:
>
> > On Feb 11, 2014, at 3:30 PM, Jesse Noller <jesse.noller at RACKSPACE.COM>
> wrote:
> >
> >> I did propose in the original thread that we join efforts: in fact, we
> already have a fully functioning, unified SDK that *could* be checked in
> today - but without discussing the APIs, design and other items with the
> community at large, I don't think that that would be successful.
> >>
> >>> [1]
> https://github.com/openstack/oslo-incubator/tree/master/openstack/common/apiclient
> >
> > While there are some differences, this library shares the same
> client/manager/resource class design and flow as the work we've done. IOW,
> I think the approaches are more alike than different, which is encouraging.
> >
> >
> > -- Ed Leafe
>
> The projects are not exclusive to one another - they are completely
> complimentary.
>
> And as of yet, we have not solidified the client/manager/resource
> structure - we should talk about that at the meeting next week.
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> 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/20140212/2dfefe0d/attachment.html>