From: Valery Tschopp <valery.tschopp@switch.ch>
To: Yehuda Sadeh-Weinraub <yehuda@redhat.com>
Cc: ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: ceph:rgw issue #10698
Date: Wed, 18 Feb 2015 09:32:47 +0100 [thread overview]
Message-ID: <54E44E2F.2020009@switch.ch> (raw)
In-Reply-To: <784895333.6829144.1424192912653.JavaMail.zimbra@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
Hi Yehuda,
Would it be possible to have the bug fixes #10698 + #10062 for the S3
POST issue be backported for the new release of firefly?
This feature is very important for us, our video conversion engine
relies on the user S3 browser POST.
Best regards,
Valery
On 17/02/15 18:08 , Yehuda Sadeh-Weinraub wrote:
>> Subject: ceph:rgw issue #10698
>>
>> Hello Yehuda,
>>
>> The issue http://tracker.ceph.com/issues/10698 "rgw: not failing
>> POST requests if keystone not configured" is marked as resolved,
>> but I don't think it is backported in firefly.
>>
>> Issue http://tracker.ceph.com/issues/10062 should already be
>> backported, if I'm not wrong...
>>
>
> Neither made it in. The bug wasn't set to be backported to firefly.
> We can set it to get backported if there's a demand, however, I'm not
> sure that it's going to be a trivial backport.
>
> Yehuda
>
--
SWITCH
--------------------------
Valery Tschopp, Software Engineer, Peta Solutions
Werdstrasse 2, P.O. Box, 8021 Zurich, Switzerland
email: valery.tschopp@switch.ch phone: +41 44 268 1544
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 3643 bytes --]
next prev parent reply other threads:[~2015-02-18 8:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-17 12:07 ceph:rgw issue #10698 Valery Tschopp
2015-02-17 17:08 ` Yehuda Sadeh-Weinraub
2015-02-18 8:32 ` Valery Tschopp [this message]
2015-02-18 16:56 ` Yehuda Sadeh-Weinraub
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54E44E2F.2020009@switch.ch \
--to=valery.tschopp@switch.ch \
--cc=ceph-devel@vger.kernel.org \
--cc=yehuda@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.