Open Stack

Reviewing the havanacore  capabilities file in Stackforge, the capabilities that may not have matching code designated are:

Objectstore-container
Objectstore-object

There are no keystone capabilities in the current set of core capabilities.  There are auth api capabilities, but those are all within the scope of nova.

Tim:  Keystone *is* a strategic direction, but in the Havana timeframe, all keystone capabilities except for non-admin-roles required admin rights, so are not admissible in the Havana DefCore (admin rights capabilities and tests for those will need to be  thr/^^hashed out for future releases.

--Rocky

From: Tim Bell [mailto:Tim.Bell at cern.ch]
Sent: Friday, September 12, 2014 11:57 AM
To: Joshua McKenty; Rob Hirschfeld
Cc: Defcore-committee at lists.openstack.org
Subject: Re: [OpenStack-DefCore] Results from Community Meetings > discussion/+1 about reconsidering Havana Swift as a core capability


I'm a real newbie on this topic but isn't a Keystone token a pre-requisite and strategic direction for any other operation ?

Code is another question....

Tim

From: Joshua McKenty [mailto:joshua at pistoncloud.com]
Sent: 12 September 2014 20:37
To: Rob Hirschfeld
Cc: Defcore-committee at lists.openstack.org
Subject: Re: [OpenStack-DefCore] Results from Community Meetings > discussion/+1 about reconsidering Havana Swift as a core capability

Just so I'm clear, Doug - you would therefore also like to propose some designated sections for Keystone?

--

Joshua McKenty
Chief Technology Officer
Piston Cloud Computing, Inc.
+1 (650) 242-5683
+1 (650) 283-6846
http://www.pistoncloud.com

"Oh, Westley, we'll never survive!"
"Nonsense. You're only saying that because no one ever has."

On Sep 12, 2014, at 11:35 AM, <Rob_Hirschfeld at Dell.com<mailto:Rob_Hirschfeld at Dell.com>> <Rob_Hirschfeld at Dell.com<mailto:Rob_Hirschfeld at Dell.com>> wrote:


> -----Original Message-----
> From: Doug Hellmann [mailto:doug at doughellmann.com]
> The actual current proposal, if I understand correctly, is to require
> the Swift APIs be provided, but not require the use of Swift's code to
> do so. We may be converging on dropping the requirement of the APIs,
> but I don't think that's settled.


The current Havana recommendation includes some Swift APIs; however, I believe we should (and will ask the Board to) reconsider that based on feedback I have been getting.

> I believe, and Rob please correct me if I misunderstood, that some
> distros would also like to provide an OpenStack product that doesn't
> include object storage in any way (neither Swift nor Ceph). I'm not
> especially inclined to care about that use case, but it's out there.


I don't see distros doing omitting whole projects; however, more integrated products or services have already proven that they will be more selective.  IMHO, that's the market giving us critical feedback and we should be careful in over fencing the market.
_______________________________________________
Defcore-committee mailing list
Defcore-committee at lists.openstack.org<mailto:Defcore-committee at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/defcore-committee/attachments/20140912/8029acbc/attachment.html>