On Sun, Sep 11, 2011 at 2:10 PM, Andrey Zhuchkov <[email protected]>wrote:
> So from my point of view there is a need to handle different milestones in > different ways even if you drop API 1.0. Actually, I still don't know how > to > implement such support gracefully and very appreciate your suggestions. > Even if we decide to support multiple API versions, I think the goal should be to support, at most: A. Past final, published version specifications, and B. The current state of the version that's in development. The purpose of the latter is to have support implemented or nearly so when the spec is finalized. Support for an unstable spec is inherently unstable, and no attempt should be made to support milestones interim specs on an ongoing basis. > I can share my driver implementation - it supports milestone 2 (including > floating IPs) and also contains Keystone authentication support. Support of > Diablo 3 is not fully implemented. I planned to send a patch but > unfortunately I have not implemented tests yet. > Are you referring to your osth-proxy-keystone branch that I see on github? It'd be great to work together and finish it up, but I'm concerned that the branch looks like it's diverged quite a bit from trunk (e.g. the recent OpenStack/Rackspace inversion refactor in trunk - looks like you had a similar idea, but it's done differently). If you could merge trunk and adapt your changes, it'd be a lot easier to see where things stand and see if I could help. Mike
