[OpenStack-DefCore] Results from Community Meetings > discussion/+1 about reconsidering Havana Swift as a core capability

Kamhout, Das das.kamhout at intel.com
Fri Sep 12 19:03:32 UTC 2014


I am with you Tim…

It is almost like someone just needs to put together a dependencies map, and really look at this from the perspective of what an operator needs to supply a different set (ala carte – or everything in the integrated release) of consumable services to their end users (people building cool apps on OpenStack).

I may  be missing something, but this conversation almost feels academic vs. what will benefit shops wanting to run and consume OpenStack services ala carte, or with everything that is needed.

-Das

From: Tim Bell <Tim.Bell at cern.ch<mailto:Tim.Bell at cern.ch>>
Date: Friday, September 12, 2014 at 11:57 AM
To: Joshua McKenty <joshua at pistoncloud.com<mailto:joshua at pistoncloud.com>>, Rob Hirschfeld <Rob_Hirschfeld at Dell.com<mailto:Rob_Hirschfeld at Dell.com>>
Cc: "Defcore-committee at lists.openstack.org<mailto:Defcore-committee at lists.openstack.org>" <Defcore-committee at lists.openstack.org<mailto: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<mailto: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




More information about the Defcore-committee mailing list