Jesse, Why not next approach: 1) Switch all clients to apiclient[1] (internal unification) 2) Unify API of all clients (external unification) 3) Unify work with keystone 4) Graduate apiclient 5) Switch all clients to apiclient lib 6) Make one simple plugable mechanism. e.g. subclass based factory + steavdore 7) Add one by one subclasse that present client in this factory 8) In one pretty day stop gates & switch to unified client.
This is actually step by step solution that works for community and could be done independently by tons of developers. [1] https://github.com/openstack/oslo-incubator/tree/master/openstack/common/apiclient Best regards, Boris Pavlovic On Wed, Feb 12, 2014 at 12:40 AM, Jesse Noller <[email protected]>wrote: > As I said last week; we're ready to kickoff and have regular meetings for > the "unified python SDK" project. The initial meeting is scheduled on the > wiki: > > https://wiki.openstack.org/wiki/Meetings#python-openstacksdk_Meeting > > Date/Time: Feb. 19th - 19:00 UTC / 1pm CST > > IRC channel: #openstack-meeting-3 > > Meeting Agenda: > https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK > > About the project: > https://wiki.openstack.org/wiki/PythonOpenStackSDK > > If you have questions, all of us lurk in #openstack-sdks on freenode! > > See you then. > > Jesse > _______________________________________________ > 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
