►
From YouTube: RGW S3: Features Vs Deep Compatibility - Robin Johnson
Description
Cephalocon APAC 2018
March 22-23, 2018 - Beijing, China
Robin Johnson, DreamHost Ceph Developer
B
Aws
s3
is
their
implementation
of
it
or
GW
necessary
for
the
same,
and
so
yes,
although
the
s3
holes
have
various
itches,
they
can
either
include
or
be
directly
used
for,
and
they
may
have
an
immediate,
immediate
effect
or
long-term
persistent
effect.
They've
only
ever
published
one
standard
version
and
they
keep
changing
it
and
the
version
has
never
been
changed.
The
behavior
who
gets
has
also
changed.
If
somebody
has
a
better
list
of
the
changes
in
it,
it
will
be
wonderful.
B
B
B
But
it's
slow
and
it
doesn't
capture
a
lot
of
the
corner
cases
and
it
doesn't
catch
any
of
the
cases
we
mark
reading
your
data
and
that's
good
that
can
by
tune
some
cases
later
on.
So
I
was
trying
to
figure
out.
How
can
we
figure
out
what
all
the
esterday
API
is
used
by
cost
of
our
customers
and
tequilas
like
they
were
asking
for
word
encryption
and
are
they.
B
B
C
B
B
It
can
start
processing
this
as
soon
as
the
headers
are
finished
and
it
tries
to
it-
and
accordingly
is
the
names
of
the
ACLS
used
to
classify
ability
all
the
requests
get
the
get
a
CL
literally
logged
in,
as
this
was
to
get
a
CL
request,
and
you
don't
have
to
do
any
other
parsing
of
it
and
I
can
see
from
which
of
the
headers.
There
are.
B
Oh,
this
was
a
write
request
that
didn't
happen
to
have
SS
he
on
it
and
after
this
unit
separately
capture
the
ability,
response
and
say:
okay,
this
wasn't
actually
a
successful
request.
I
could
just
throw
away
the
passing
I've
done
if
there's
better
way
of
doing
this
is
future.
That
would
be
great,
but
there
isn't
serve
some
brief
statistics
here.
Three
most
public,
a
buffering,
is
much
taller
than
it
really
low.
Skill
like
yeah.
B
You
can
use
just
like
Amazon's,
but
the
user
base,
for
it
is
no
particularly
skilled,
and
many
of
them
stand
up
using
it
from
existing
products
like
Fabray
backup
do
plug
it
into
the
queue
now
say
here
your
queue.
Now
you
can
use
an
external
cloud
service
for
an
extra
backup
of
your
little
NASA
at
home
and
let
right
lots
of
objects.
They
said
to
make
a
seals
on
them
and
they
do
almost
nothing
else
for.
B
Encryption,
if
your
tool
didn't
send
automatically
it
didn't
get
used,
nobody
else
is
using
the
encryption
manually,
which
was
a
surprise
after
all,
the
people
who
are
asking
for
it.
So
now
the
other
meteor
things
where
the
things
that
are
changing
between
the
specification
and
the
AWS
implementation,
the
Oceaneer
fermentation
AWS
itself-
is
mostly
more
lenient
than
their
specification
says,
and
it's
not
a
double.
Also.
C
B
B
B
Then
we
start
falling
down.
This
is
what
Detailers
mentioned
their
specifications.
Some
of
the
other
details
are
not
so
pants.
Shouldn't
HDPE,
put
include
the
content
length,
header,
yes,
or
no
put
your
hand
up.
We,
yes,
okay,
most
of
you
are
doing
better
than
the
code
base.
At
the
moment
the
specification
says
yes,
the
AWS
examples,
however,
are
not
consistent
to
many
of
them.
Thirteen
pure
content,
header
lgw,
will
most
both
correctly
parse
it.
B
So
I
ended
up
using
this
a
major
proxy
look
balancer
to
patch
those
requests.
I
can
see
that
they
did
not
have
a
any
party
to
them
and
there
was
no
contact
length
header
because
they
were
just
the
ACL
operation
and
I
can
just
I
just
injected
content
like
it
0
into
it.
It
was
like
a
turn
that
around
quicker
is
a
fixed
and
fixed
emoji
W
itself.
B
So
have
you
heard
from
users?
This
client
doesn't
want
to
work
quite
right
against
myself
luster.
They
have
that
same
hard-coded
logic.
That
I
was
mentioning
for
were
regions
like
us.
The
u.s.
is
one
the
AWS
signature
in
some
cases
includes
includes
the
region
for
build
the
v4
signature
and
suddenly
some
of
the
clients
hard-coded
magical
back
in
here
that
this
is
a
real
Amazon
one
and
so
I'm
going
to
compute
the
signature
differently
than
some
third
party
is
free
implementation
and
it
goes
slightly
sideways
one
that
are
pointed
out
to
me
earlier
this
week.
B
Aws
s4
does
weird
things
when
you
have
concurrent
spaces
in
your
signature
data
it
requires
that
you
strip
them.
Don't
you
write
original?
They
get
it
wrong
and
I
fail
against
AWS,
even
their
button.
The
signature
calculations
for
the
multi
product
loads
for
doing
browser
posts
for
doing
chuckling
coding,
none
of
the
fork
for
things
between
the
specification,
AWS,
rgw,
sorry,
three
things
end
up:
I
have
any
consistency
to
them.
B
We
have
a
decision
which
one
is
right
so
really
like
how
scription
or
DWS
the
story
end
up
being
jon
postel
many
many
decades
ago
proposed
what
was
better
known
as
the
robustness
principle.
You
should
be
very
liberal
than
what
you
accept
and
very
strict
in
what
you
send.
We
don't
do
that
the
moments
right
in
in
or
GW,
and
I
think
we
should
be
much
more
generous
as
to
what
we
are
accepting
with
within
reason.
Is
it
going
to
cause
breakages
the
AWS
s3
signature,
the
spaces?
B
B
B
They
are
constantly
AWS
that
sufficiently
old.
There
are
a
few
based
on
HTTP
1.0
and
you
can
skip
sending
a
host
header
and
you
can
send
the
former
the
full
post
name
as
the
stocked
with
your
bucket.
So
as
it's
part
of
your
URL
of
the
bucket
down
and
AWS
works,
this
nation
key
1.0
requested
EWS
serves
it
correctly
or
GW.
Does
not.
B
So
what
happens
now
if
the
client
expects
a
feature
to
exist,
and
it
does
not
actually
exist
in
our
GW
the
protocol
in
many
cases,
the
response
will
not
give
you
any
feedback
about
those
features.
You
can
recall
you
could
require
your
data
to
see
if
it
is
there,
how
about
you
go
check,
because
if
you
always
say
implementation
is
only
eventually
consistent
like
AWS
is
rtw
does
a
much
better
job,
but
consider
immediate
consistency.
B
B
B
Here's
the
key
for
it
burn
and
it
fails
because
now
it
tries
to
apply
the
decryption
function
on
unencrypted
data
and
it
returns
called
effectively
randomized
orbit
because
block
ciphers
do
that
they
don't
unless
they
happen
to
have
some
of
that.
It's
an
authentication
part
into
their
cipher,
which
in
many
cases
as
a
cc,
does
not
it
has
to
verify
what
the
result
should
have
been.
B
So
beyond
this,
what
happened
to
Anu
client
end
up
your
customers,
choose
clients
and
other
features
that
do
real
things.
Aws
itself
has
not
positive
behavior.
If
you
use
the
old
photo
to
s3
library,
it
did
not
compute
the
AWS
v4
signature
correctly,
but
AWS
themselves.
When
said,
oh
crap,
we
did
that
wrong,
but
we'll
modify
our
os3
to
accept
both
signatures,
the
wrong
at
the
wrong
signature
and
the
right
signature-
and
we
didn't
realize
this
at
first
when
we
implemented
before
signatures
in
all
GW,
and
so
we
added
a
toggle
flag.
B
B
B
Mostly
because
it
has
many
new
ones,
corners,
fine,
separated
as
well
slightly-
that
was
a
very
popular
client
limitation
for
our
customers.
They
could
just
use
it
like
an
FTP
client,
but
then
they
are
pretty
good
and
suddenly
they
said
no
Maya
multi-port
opposed
don't
work
anymore.
What
can
we
end
up
doing
about
that?
Better
testing
of
plans.
B
B
C
D
B
Just
deployed
okay,
one
of
the
problems
torchy
wi
said
over
the
years
in
our
case
out
date.
Here
is
now
six
and
a
half
years
old.
We
cannot
read
ultimate
back
correctly
anymore.
You
can
read
it
in
the
ogw
itself,
it
looks
fine
and
then
you
try
to
fetch
it
and
you
just
wind
up.
Why
is
there
a
block
missing
in
the
middle
of
my
data
or
just
stores
in
sending
it?
Because
it
can't
find
it
anymore?
B
B
B
Weird
breakages
various
files,
I,
even
let
you
set
the
bucket
name
in
the
first
place,
some
of
the
other
pieces
there
that
some
of
the
metadata,
if
it
was
written
out
in
s3,
does
not
get
read
back
correctly
in
Swift,
or
vice
versa.
I
think
has
the
Swift
and
s3
buckets
need
to
start
living
in
separate
namespaces.
It
would
probably
upset
some
people
that
they
became
disconnected,
but
I
think
the
safety
of
the
data
would
be
much
improved
if
that
was
the
case,.
B
In
my
h-net
proxy
front-end
layer,
I
can
cure
as
some
of
the
users
down
to
a
very
low
rate
by
number
of
requests.
I
cannot
lower
them
by
turtle.
Bites
feed
you
to
my
implementation,
but
I
can
separately
regular
mat
them
to
a
very
low
number
of
requests
compared
to
other
users,
but
that
is
done
in
the.