On Tue, Jul 21, 2015 at 5:28 PM, Luse, Paul E
paul.e.l...@intel.commailto:paul.e.l...@intel.com wrote:
I was about to ask that very same thing and, at the same time, if you can
indicate if you’ve seen errors in any logs and if so please provide those as
well. I’m hoping you just didn’t delete
I was about to ask that very same thing and, at the same time, if you can
indicate if you’ve seen errors in any logs and if so please provide those as
well. I’m hoping you just didn’t delete the hashes.pkl file though ☺
-Paul
From: Clay Gerrard [mailto:clay.gerr...@gmail.com]
Sent: Tuesday,
Hi Chmouel,
Storage policies can be fully tested and exercised on an SAIO; the docs that
were recently merged to the feature/ec branch also include a second example
policy using 2x replication to show this. No reason why devstack can’t be used
but I’d propose it doesn’t make anything easier
Congrats guys!!
-Original Message-
From: John Dickinson [mailto:m...@not.mn]
Sent: Thursday, March 27, 2014 1:34 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Swift] new core members
I'm pleased to announce that Alistair Coles and
look
Thanks!
Paul
From: Gil Vernik [mailto:g...@il.ibm.com]
Sent: Saturday, February 8, 2014 11:29 PM
To: Luse, Paul E
Subject: question about storage policies for Swift
Dear Paul Luse,
I am trying to better understand your new additions to Swift about storage
policies.
I started with your
What a corporate thing to do :) Good call though John
-Paul
-Original Message-
From: John Dickinson [mailto:m...@not.mn]
Sent: Thursday, February 6, 2014 9:16 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: [openstack-dev] [Swift] meeting time updated
To: OpenStack Development Mailing List
Cc: Luse, Paul E
Subject: Re: [openstack-dev] [Swift] question on Application class concurrency;
paste.app_factory mechanism
On Wed, 24 Jul 2013 02:31:45 +
Luse, Paul E paul.e.l...@intel.com wrote:
I was thinking that each connection would get its own instance
I think most folks are on the same page wrt EC being consider a level or
storage policy as we've been discussing in other forums. I saw the previous
note on account versus container and was actually thinking it made more sense
to me at least to enable billing per container as opposed to
