Devin Carlen wrote:
added a few inline
Sounds like we need... a wikipage !
Please see, edit, augment, comment on:
http://wiki.openstack.org/OpenStackAPIGapAnalysis
--
Thierry Carrez (ttx)
Release Manager, OpenStack
___
Mailing list:
I havn't seen much activity on this, so though I'd do a quick brain
dump of what I'm aware of:
Auth/global:
* Ability to lockout a user for some time period after failed auth.
* Describe zones and regions (replaced with Sandy's zone work).
Admin
* Describe instance types (list flavors).
* CRUD
added a few inline
On Mar 2, 2011, at 12:24 PM, Eric Day wrote:
I havn't seen much activity on this, so though I'd do a quick brain
dump of what I'm aware of:
Auth/global:
* Ability to lockout a user for some time period after failed auth.
* Describe zones and regions (replaced with
John Purrier wrote:
Here is what we said on Feb 3 as the goal for Cactus:
*OpenStack Compute API completed. We need to complete a working set of
API's that are consistent and inclusive of all the exposed functionality . *
This was not reflected in the Cactus plan at:
the auth services return?
From: Jesse Andrews anotherje...@gmail.com
Date: Mon, 28 Feb 2011 19:53:01 -0800
To: Erik Carlin erik.car...@rackspace.com
Cc: openstack@lists.launchpad.net openstack@lists.launchpad.net
Subject: Re: [Openstack] OpenStack Compute API for Cactus (critical!)
I'm also
...@rackspace.commailto:erik.car...@rackspace.com,
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] OpenStack Compute API for Cactus (critical!)
pvo,
Yep. I'm responding to the slide having 3 services, 5 endpoints
] OpenStack Compute API for Cactus (critical!)
Has anyone done a gap analysis against the proposed OpenStack Compute API and
a) the implemented code, and b) the EC2 API?
It looks like we have had a breakdown in process, as the community review
process of the proposed spec has not generated discussion
Subject: Re: [Openstack] OpenStack Compute API for Cactus (critical!)
John -
Are we just talking about compute aspects? IMO, we should NOT be exposing
block functionality in the OS compute API. In Diablo, we will break out
block into a separate service with it's own OS block API. That means
and Diablo as they are currently under heavy discussion and
design.
John
From: Erik Carlin [mailto:erik.car...@rackspace.com]
Sent: Monday, February 28, 2011 3:16 PM
To: John Purrier; openstack@lists.launchpad.net
Subject: Re: [Openstack] OpenStack Compute API for Cactus (critical!)
John
...@rackspace.commailto:erik.car...@rackspace.com,
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: RE: [Openstack] OpenStack Compute API for Cactus (critical!)
Hi Erik, today we have compute, block/volume, and network all encompassed in
nova. Along with image and object storage these make
@lists.launchpad.net
Subject: Re: [Openstack] OpenStack Compute API for Cactus (critical!)
Your diagram is deceptively simple because it makes no distinction about how
block API would be handled in the EC2 API, where compute and block operations
are very closely coupled. In order for the diagram
-0800
To: Erik Carlin erik.car...@rackspace.commailto:erik.car...@rackspace.com
Cc: John Purrier j...@openstack.orgmailto:j...@openstack.org,
openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] OpenStack Compute API for Cactus (critical!)
Erik,
Thanks
Date: Mon, 28 Feb 2011 17:07:22 -0600
To: John Purrier j...@openstack.org, openstack@lists.launchpad.net
Subject: Re: [Openstack] OpenStack Compute API for Cactus (critical!)
That all sounds good. My only question is around images. Is glance ready to
be an independent service (and thus
@lists.launchpad.netmailto:openstack@lists.launchpad.net
Subject: Re: [Openstack] OpenStack Compute API for Cactus (critical!)
I'm also confused because nova (compute/block/network) is in 1 repository
doesn't mean it isn't 3 different services.
We've talked about moving the services inside nova to not reaching inside
14 matches
Mail list logo
