Open Stack

Hey Sandy,

We hadn't shifted our focus over to the client yet - our assumption had been that the best course would be to version the existing library and move forward.  However, that was definitely an assumption and if people have experience that says maybe we should explore a new client tied more closely with nova, then we should look into that.  This is my way of saying I don't know, but whichever direction we go, we can help if that's where we are needed.  Anyone who has looked at the client, Titan or otherwise, should educate us here.

To Soren's original point, we've already said that python-novaclient is a requirement for nova, and relying on an external party to keep that up-to-date is a little bit of a concern to me.  We are going to rely on this to maintain our deployments, so it seems a little risky to rely on someone not on the project to keep it up to date.

We do have other language bindings that can keep us honest as far as honoring the spec, so hopefully we still get that protection from ourselves from that quarter.

Gabe

On Wednesday, May 18, 2011 10:03am, "Sandy Walsh" <sandy.walsh at rackspace.com> said:

> Thanks Dan,
> 
> I wasn't so much worried about the technical details but rather if your group
> plans on making a new client or contributing to python-novaclient (or something)?
> 
> Cheers,
> -Sandy
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>