Looks like a unanimous decision.
Here is the blueprint.
https://blueprints.launchpad.net/nova/+spec/remove-nova-direct-api
best,
Joe
On Mon, Apr 9, 2012 at 3:49 PM, Devin Carlen de...@openstack.org wrote:
+1 It doesn't have to go home but it can't stay here.
On Apr 9, 2012, at 12:31 PM,
Hi All,
The other day I noticed that in addition to EC2 and OpenStack APIs there is
a third API type: nova-direct-api. As best I can tell, this was used
early on for development/testing before the EC2 and OpenStack APIs were
mature.
My question is, since most of the code hasn't been touched in
+1 to removal. I just tested to see if it still works, and due to our policy
checking and loading objects before sending them into compute.api, it no longer
functions. Probably wouldn't be too hard to fix it, but clearly no one is using
it so lets axe it.
Vish
On Apr 9, 2012, at 11:19 AM,
/me wears black armband.
Would love to see DirectApi v2 be the de facto OS API implementation.
The spec could be the same, it's just a (better) implementation detail.
-S
On 04/09/2012 03:58 PM, Vishvananda Ishaya wrote:
+1 to removal. I just tested to see if it still works, and due to our
On Mon, 2012-04-09 at 11:58 -0700, Vishvananda Ishaya wrote:
+1 to removal. I just tested to see if it still works, and due to our
policy checking and loading objects before sending them into
compute.api, it no longer functions. Probably wouldn't be too hard to
fix it, but clearly no one is
+1 It doesn't have to go home but it can't stay here.
On Apr 9, 2012, at 12:31 PM, Kevin L. Mitchell wrote:
On Mon, 2012-04-09 at 11:58 -0700, Vishvananda Ishaya wrote:
+1 to removal. I just tested to see if it still works, and due to our
policy checking and loading objects before sending
6 matches
Mail list logo
