On Wed, Feb 12, 2014 at 10:36 AM, Matthew Farina <[email protected]> wrote: > 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.
The existing clients (python-novaclient, python-glanceclient, python-cinderclient etc.) are not supposed to be targeted at people trying to 'build' (does 'build' mean develop or deploy?) OpenStack they are targeted at people trying to write applications for OpenStack. Although perhaps we are not doing a great job of that. > > 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. I don't think there are two different target audiences, I think they are the same. As someone 'building' OpenStack I want to consume it the same way an application developer would. > > > > On Wed, Feb 12, 2014 at 10:32 AM, Jesse Noller <[email protected]> > wrote: >> >> >> On Feb 12, 2014, at 9:07 AM, Ed Leafe <[email protected]> wrote: >> >> > On Feb 11, 2014, at 3:30 PM, Jesse Noller <[email protected]> >> > 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 >> [email protected] >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > > > > _______________________________________________ > OpenStack-dev mailing list > [email protected] > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > _______________________________________________ OpenStack-dev mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
