Hi Mike, I've been working on support of Nova API 1.1 for our project and API 1.1 looks a little bit unstable, e.g. there are tag duplications in responses, JSON inside XML attributes, usage of image ID as image reference, etc. Some bugs appeared in Diablo milestone 2, some of them are fixed in milestone 3. 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.
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. 2011/9/11 Mike Nerone <[email protected]> > Hello, all! First an extremely brief introduction since this is my first > email to this list: I'm a developer at Rackspace, and I've been there since > 2005, and I'm currently working with the Cloudkick team. which brings me to > libcloud. :) > > I'm working on support for OpenStack Nova 1.1. My intent had been to > preserve existing support for 1.0, inheriting as much behavior as possible > for the 1.1 driver. Discussion in IRC brought to light that pquerna had > instead envisioned dropping support for 1.0, and only supporting 1.1. I'm > concerned that since the driver supports third-party deployments (it > accepts > an auth_host parameter), it's possible that there may be existing private > deployments of which we're not aware. However, if everyone agrees that > there > are no such deployments or that we don't need to make them a concern, then > the OpenStack 1.0 support starts to look a lot like cruft, and I'd agree it > should be dropped. We need to have a conversation about the direction here. > I don't think there's much difference in the difficulty factor, so what > does > everyone think is the *right* thing to do? > > Thanks much! > > Mike Nerone > -- Andrey Zhuchkov
