On Thu, 10 May 2018 20:07:03 +0800
Yuxin Wang wrote:
> I'm working on a swift project. Our customer cares about S3 compatibility
> very much. I tested our swift cluster with ceph/s3-tests and analyzed the
> failed cases. It turns out that lots of the failed cases are related to
> unique contai
On Fri, 9 Jun 2017 10:37:15 +0530
Niels de Vos wrote:
> > > we are looking for S3 plugin with ACLS so that we can integrate gluster
> > > with that.
> >
> > Did you look into porting Ceph RGW on top of Gluster?
>
> This is one of the longer term options that we have under consideration.
> I am
On Thu, 8 Jun 2017 17:06:02 +0530
Venkata R Edara wrote:
> we are looking for S3 plugin with ACLS so that we can integrate gluster
> with that.
Did you look into porting Ceph RGW on top of Gluster?
-- P
__
OpenStack Devel
On Wed, 9 Nov 2016 11:14:32 + (GMT)
Chris Dent wrote:
> The conversations about additional languages in this community have
> been one our most alarmingly regressive and patronizing. They seem
> to be bred out of fear rather than hope and out of lack of faith in
> each other than in trust. We
On Mon, 07 Nov 2016 15:53:51 -0800
Joshua Harlow wrote:
> Standards though exist for a reason (and ini files are pretty common
> across languages and such); though of course oslo.config has some very
> tight integration with openstack, the underlying ini concept it
> eventually reads/writes re
On Mon, 6 Jun 2016 13:05:46 -0700
"Thai Q Tran" wrote:
> My intention is to spark discussion around this topic with the goal of
> moving the Swift community toward accepting the JSON format.
If would be productive if you came up with a specific proposal how to
retrofit JSON for container ACLs. N
On Fri, 13 May 2016 10:14:02 +0200
Dmitry Tantsur wrote:
> [...] If familiarity for Python
> developers is an argument here, mastering Cython or making OpenStack run
> on PyPy must be much easier for a random Python developer out there to
> seriously bump the performance.
Unfortunately, pract
On Mon, 9 May 2016 14:17:40 -0500
Edward Leafe wrote:
> Whenever I hear claims that Python is “too slow for X”, I wonder
> what’s so special about X that makes it so much more demanding than,
> say, serving up YouTube.
In case of Swift, the biggest issue was the scheduler. As RAX people
found, a
On Mon, 9 May 2016 09:06:02 -0400
Rayson Ho wrote:
> Since the Go toolchain is pretty self-contained, most people just follow
> the official instructions to get it installed... by a one-step:
>
> # tar -C /usr/local -xzf go$VERSION.$OS-$ARCH.tar.gz
I'm pretty certain the humanity has moved on f
On Wed, 4 May 2016 21:52:49 +
"Fox, Kevin M" wrote:
> Swift is in a strange place where the api is implemented in a way to
> favor one particular vendor backend implementation.
Sorry, but I disagree with the above assessement. There is no one
particular vendor like that, because the only ven
On Tue, 3 May 2016 22:37:30 +
"Fox, Kevin M" wrote:
> RadosGW has been excluded from joining the OpenStack community in part
> due to its use of c++.
Sounds like sheer lunacy. Nothing like that ever happened, AFAIK.
-- Pete
__
On Tue, 3 May 2016 22:11:06 +
"Fox, Kevin M" wrote:
> If we let go in, and there are no pluggable middleware, where does
> RadosGW and other Swift api compatible implementations then stand?
They remain where they are now.
> Should we bless c++ too? As I understand it, there are a lot of clo
On Tue, 3 May 2016 12:16:24 -0400
Rayson Ho wrote:
> I like Go! However, Go does not offer binary compatibility between point
> releases. For those who install from source it may not be a big issue, but
> for commercial distributions that pre-package & pre-compile everything,
> then the compiled
On Wed, 20 Jan 2016 13:46:13 +0200 (EET)
Mustafa ÇELİK (BİLGEM-BTE) wrote:
> commit-1: This one is my patch for the bug.
> https://review.openstack.org/#/c/268163/
> I need someone to review my commit-1.
> Can somebody help me with code-review?
Sure... I am somewhat unenthusiastic about this
On Tue, 22 Dec 2015 08:56:08 -0800
Clint Byrum wrote:
> You could create a unique swift container, upload things to that, and
> then update a pointer in a well-known location to point at that container
> for the new plan only after you've verified it is available. This is a
> primitive form of Re
On Thu, 11 Jun 2015 11:08:55 +0300
Duncan Thomas wrote:
> There's only one cinder driver using it (nimble storage), and it seems to
> be using only very basic features. There are half a dozen suds forks on
> pipi, or there's pisimplesoap that the debian maintainer recommends. None
> of the above
On Fri, 10 Oct 2014 04:56:55 +
"Osanai, Hisashi" wrote:
> Today the following patch was abandoned and I contacted with the author,
> so I would like to take it over if nobody else is chafing to take it.
> Is it OK?
>
> https://review.openstack.org/#/c/80421/
>
> If it is OK, I will proceed
On Wed, 23 Jul 2014 08:54:30 -0700
John Dickinson wrote:
> So basically, it's a question of do we add the feature, knowing that
> most people who use it will in fact be making their lives more difficult,
> or do we keep it out, knowing that we won't be serving those who actually
> require the fea
On Mon, 7 Jul 2014 11:05:40 +0800
"童燕群" wrote:
> The workflow of this middle-ware working with swift may be like this pic:
Since you're plugging this into a/c/o nodes, there's no difference
between this and Pluggable Back-ends. Note that PBE is already implemented
in case of object server, see c
On Wed, 2 Jul 2014 00:16:42 +
"Osanai, Hisashi" wrote:
> So I think if performance of swift is more important rather than scalability
> of it, it is a
> good idea to use ext4.
The real problem is what happens when your drives corrupt the data.
Both ext4 and XFS demonstrated good resilience,
On Fri, 14 Mar 2014 09:03:22 +0100
Chmouel Boudjnah wrote:
> fujita (the maint of swift3 in CC of this email) has commented that he's
> been working on it.
I think we should've not kicked it out. Maybe just re-fold it
back into Swift?
-- Pete
___
Op
Dear Solly:
I cobbled together a working prototype of Guru Meditation for Swift
just to see how it worked. I did not use Oslo classes, but used the
code from Dan's prototype and from your Nova review. Here's the
Gerrit link:
https://review.openstack.org/70513
Looking at the collected tracebacks,
On Thu, 20 Feb 2014 10:14:34 +0800
Dong Liu wrote:
> 2014-02-18 11:31:13.186 | File "/usr/local/bin/swift", line 35, in
>
> 2014-02-18 11:31:13.186 | from swiftclient import Connection,
> HTTPException
> 2014-02-18 11:31:13.187 | ImportError: cannot import name HTTPException
You updated t
On Tue, 18 Feb 2014 10:57:03 +0100
Joe Hakim Rahme wrote:
> Again, I have just spent a couple of days playing with it on a devstack. I'm
> by
> no means a reference on the subject of the API v2. I hope this will help you
> get
> a better idea of where it stands today.
Thanks a lot, it clears u
Hello:
does anyone happen to know, or have a detailed write-up, on the
differences between so-called "Glance v1" and "Glance v2"?
In particular do we still need Glance Registry in Havana, or
do we not? The best answer so far was to run the registry anyway,
"just in case", which does not feel enti
Hi, guys:
I looked briefly at a bug/fix, which looks exceedingly strange to me:
https://review.openstack.org/59689
As much as I can tell, the problem (lp:1238604) is that pending delete
fails because by the time the delete actually occurs, Glance API does
not have proper permissions to talk to G
Hi, Guys:
Here's a weird piece of duplicated call to account_audit() in
swift/account/auditor.py:
for path, device, partition in all_locs:
self.account_audit(path)
if time.time() - reported >= 3600: # once an hour
self.logger.info(_('Since %(time)s
On Thu, 5 Sep 2013 15:05:55 +0200
CHABANI Mohamed El Hadi wrote:
> But for some operations such authentification, or getting pictures
> metadata, and lot of uses cases in Swift...i don't know how to convert the
> plain text into XML/JSON !! if someone could help me on, it will really
> great.
I
On Wed, 24 Jul 2013 02:31:45 +
"Luse, Paul E" wrote:
> I was thinking that each connection would get its own instance thus it
> would be sage to store connection-transient information there but I was
> surprised by my quick test.
Yeah, you have it tracked in __call__, typically hanging off c
On Thu, 18 Jul 2013 12:31:02 -0500
Chuck Thier wrote:
> I'm with Chmouel though. It seems to me that EC policy should be chosen by
> the provider and not the client. For public storage clouds, I don't think
> you can make the assumption that all users/clients will understand the
> storage/laten
On Tue, 25 Jun 2013 08:50:49 +0100
Michael Kerrin wrote:
> we raised a bug https://bugs.launchpad.net/devstack/+bug/1193112 where the
> $ /opt/stack/swift/bin/swift-proxy-server /etc/swift/proxy-server.conf -v
> Traceback (most recent call last):
> File "/opt/stack/swift/bin/swift-proxy-serv
31 matches
Mail list logo
