►
From YouTube: CDS Jewel -- RGW Multitenancy
B
Yeah,
it's
right.
B
So
how
we
discussed
this
before,
probably
in
the
previous
EDS
too,
but
and
we
were
expecting
rather
stuff
to
talk
about
it,
but
frankly,
is
not
here,
but
let's
go
over
it.
B
B
B
B
Whereas
with
lift
it's
completely
different,
you
have
an
account
and
under
the
or
tenant
and
under
the
tendon,
if
you
you
can
create
a
bucket
food,
it
only
applies
to
that
tenant.
You
create
a
second
tenant.
You
can
have
the
same
sign
name
for
a
bucket
is
obviously
gotta,
be
in
different
pack
of
instance,.
B
B
B
B
B
That
the
requirement
here
was
for
users
to
be
able
to
create
different
tenants
within
the
gateway.
You
know
what
different
tenant
means.
Our
is
basically
the
ability
to
create
different
namespaces
and
and
in
those
namespaces
we
can
can
put
both
our
users
and
when
I'm
saying
is
I'm
talking
about
that
Prince
gateway
on
oceans
and
users
that
are
not
notice
abusers
to
create
different
users
and
create
different
pockets
within
those
namespaces.
B
B
B
A
a
bucket
under
one
tenant
to
come
with
the
same
name
as
the
other
users
at
the
other
tenant,
which
is
which
is
fine,
but
that
brings
up
some
questions
or
you
know.
The
Gateway,
for
example,
is
able
to
to
book
acts
the
domain
name
example
and
deduct
the
package
name
from
the
domain
name
now.
The
question
is:
are
so
hardly
do
it
if
you
have
different
packets
on
different
tenants.
So
what
it
look,
what
you
can
do
is
say:
okay,
you
have
different
default,
can't
know.
B
On
a
specific
tenant,
everything
is
going
to
be
on
the
same
tenant,
which
I
think
I,
don't
see
what
why
not
and
our
link
across
them
operation
server.
For
example,
if
you
create
an
object,
you
can
specify
the
the
echoes
for
that
object
and
say:
okay,
user
foo
from
tenant
bar
I
can
reach
that
object,
whether
you
there
are
bugs
from
turning
back
to
that,
can
come
back
and
do
it.
B
It
can
happen
now.
What
we
can
do
is
make
it
so
that
for
each
packet
that
you
access
it
by
default,
that,
if
you
don't
specify
the
tenant,
the
tenants
that,
let's
see
you're
going
to
access,
is
the
that's
the
city
cuter
tenant.
That's
the
city
box
tenant.
So
if
you
created
a
tenant
created
the
bucket
you're,
putting
it
data
there
and
you
studying
in
a
CO,
and
you
don't
specify
the
tenant
attendant
for
that
object.
B
B
B
A
B
B
Probably
yes,
that
some
information,
which
gives
would
what
I
have.
B
B
A
B
The
tenant
for
that,
but
that
really
doesn't
make
sense,
so
there's
gonna,
be
need
to
be
some
kind
of
a
huge
process
of
going
over
all
all
the
code
base
and
replacing
everything
which
is
kind
of
huge
technical
work,
but
not
really
young
and
anything.
That's
very
too
complicated
in
terms
of
of
topics
on
our
stuff.
That
needs
to
be
done.
It
needs
to
be
propagated
to
both
the
object.
B
B
B
B
We
are
kind
of
trying
to
be
a
protocol
blind
here
or
API
blind
there's,
not
much
not
any
difference
between
accessing
cerritos
through
a
three
tenant
when
you
access
it
through
ss3.
We
know.
B
A
B
B
Well
right,
s33
doesn't
really
have
the
concept
of
a
sub
user.
You
can
steal,
apply
the
same.
You
the
same
sucks.
Are
you
this,
though,
when
you
use
the
Gateway
not
recommended
it,
rather,
when
adding
when
creating
tenants,
I'd
rather
see
ss3,
taking
advantage
of
the
advantage
of
that
rather
than
then
using
the
sub
users.
Now
that
know,
there
is
still
the
notion
of
having
multiple
sub
users
on
a
single
race
gateway
user
that
the
new
tenant
skin
doesn't
doesn't
allow
you
mom,
and
that
is
not
going
to
change.
B
C
C
A
B
B
B
So
now
adding
a
tenant,
we
shouldn't
break
that,
but
on
the
other
hand,
if
on
new
configurations,
we're
going
to
make
it
so
that
a
keystone
tenants
would
map
into
a
gateway
tenant,
end
user,
then
it's
it's
not
going
to
break
anything
because
it's
new
new
system
configurations-
and
it's
still
going
to
follow
the
book.
Both
schemes,
because
now
you're
going
to
have
different
users
on
different
tenants,
are
and
they're
going
to
have
their
own
buckets
they're
going
to
have
their
own
bucket
darling
space.
Everything.