►
From YouTube: OpenShift Multi-Cloud Gateway Deep Dive with Eran Tamir (Red Hat) OpenShift Commons Briefing
Description
The Multi-Cloud Object Gateway is a new data federation service introduced in OpenShift Container Storage 4.2. The technology is based on the NooBaa project, which was acquired by Red Hat in November 2018, and open sourced recently.
More information can be found here https://github.com/noobaa/noobaa-operator.
The Multi-Cloud Object Gateway has an object interface with an S3 compatible API. The service is deployed automatically as part of OpenShift Container Storage 4.2 and provides the same functionality regardless of its hosting environment. Simplicity, Single experience anywhere
In its default deployment, the Multi-Cloud Object Gateway provides a local object service backed by using local storage or cloud-native storage, if hosted in the cloud.Every data bucket on the Multi-Cloud Object Gateway is backed, by default, by using local storage or cloud-native storage, if hosted in the cloud. No additional configuration is required. The Multi-Cloud Object Gateway’s object service API is always an S3 API, which means a single experience on-premise and in the cloud, for any cloud provider. This translates to a zero learning curve when moving to, or adding a new cloud vendor. That translates into greater agility for your teams. More information here https://www.openshift.com/storage
A
Well,
hello,
everybody
and
welcome
again
to
another
openshift
Commons
briefing.
This
time
we
have
Iran
Tamir,
who
is
our
open,
shifts,
container
storage,
product
manager
and
he's
going
to
talk
about
a
topic.
That's
new
to
me,
though,
I'm
very
interested
in
this
one,
the
multi
cloud
object,
gateway,
so
I'll,
let
Iran
introduce
himself.
There's
live
Q&A
at
the
end
and
as
always,
this
will
be
uploaded
on
to
the
YouTube
channel,
for
our
open
shift
and,
along
with
the
slides,
so
Iran
take
it
away.
B
Thank
you
Dan
and
today,
I
said
and
said
we
will
talk
as
part
of
the
open
shift.
Corn
briefing
we'll
talk
about
the
multi-state
way,
which
is
part
of
a
product
called
open
shift
container
storage.
So,
let's
start,
let's
start
with
what
is
open
shift
container
storage?
Actually,
so
the
open
shift
container
storage
is
a
component,
is
a
product
available
as
part
of
the
operator
hub
available
on
every
open
shift,
4.2
and
higher,
and
what
we
try
to
do
with
this
product
is
to
create
a
very
highly
scalable
and
the
production
rate.
B
B
B
B
If
I
may
say
what
is
the
main
thing
for
me,
I'm
saying
I
would
say
that
becoming
the
agnostic
layer
for
the
storage
is
the
most
important
part,
because,
if
I'm
looking
at
open
shift
as
a
platform,
the
fact
that
is
agnostic,
you
can
run
it
anywhere.
You
can
have
it.
The
same
experience
on
Prem
and
in
the
cloud
open
shift.
Container
storage
is
the
layer
for
storage
that
would
allow
allow
it
for
the
data
and
for
the
stateful
applications.
B
Container
storage
will
be
there
for
you
and
provide
this
tree
services
by
default,
no
need
to
configure
anything,
simply
deploy
openshift
container
storage
and
you
will
get
these
three
services
and
and
and
get
all
the
value
that
I
mentioned
before
now,
we'll
bring
it
down
to
the
multi
cloud
object
gateway,
which
is
one
of
the
components.
The
idea
there
is
that
you
can
start
lean
in
a
very
lightweight
way,
which
means
that
once
you
deploy
the
services
up
and
running,
you
can
start
using
it.
B
It's
very
easy
to
get
the
endpoint
access
key
and
secret
key
and
have
the
service
which
is
which
behaves
like
Amazon,
s3,
compatible
storage,
but
it's
running
in
your
openshift,
it's
running
locally
and
whenever
you
move
your
application.
So
if
you
are
using
the
dev
environment
and
then
you're
moving
to
test
staging
and
production,
it
will
behave
exactly
the
same
way
and
from
the
application
point
of
view,
you
don't
need
to
change
any
code
and
I
will
explain
what
I
mean
soon.
B
B
B
So
first,
it's
important
to
understand
that
it's
mainly
a
data
management
I
mean
we
do
provide
an
s3
API
and
that's
been
the
first
of
all.
Applications
and
I
will
explain
it
in
the
in
the
next
slide.
But
by
that
we
actually
embed
many
functionalities
and,
for
example,
every
every
data
that
is
written
to
to
this
component
will
actually
have
it
compressed.
B
We
will
have
it
in
England,
deduplication
and
everything
is
secured
in
transit
and
at
rest,
which
means
that
whenever
you're
writing
data,
we
actually
have
our
own
format
in
the
backend
and
we
always
have
a
back-end.
We
always
have
something
we
call
backing
store
and
by
default,
whenever
you're
running
on
Prem
by
default.
It's
on
a
component
internal
component,
the
rgw,
if
you
know
it,
if
you're
running
in
the
cloud,
it's
the
cloud
native
storage.
B
On
top
of
that,
we
have
data
management,
meaning
that
you
don't
need
to
take
our
decisions
before
you
start
running.
You
can
simply
start
using
OCS
and
start
using
the
multi
cloud,
object,
gateway
and
then
take
a
decision
of
like
okay.
Where
do
I
actually
want
the
data.
Do
I
want
it
on
Prem,
do
I,
want
it
on
Prem
and
mirror
to
the
cloud,
and
so
on
and
I
can
take
this
decision.
B
I
can
take
various
decisions
along
the
time
and
I
will
show
you
in
a
second
important
to
say,
and
that's
the
logo
that
you
see
here.
The
entire
multicolored
object.
Gateway
component
is
based
on
Nova
technology,
personally
I'm,
coming
from
from
that
startup
acquired
by
a
reddit
about
a
year
ago,
and
that's
the
that's
this
logo
that
you
see
currently
in
this
slide
and
that's
how
it
looks
like.
So.
B
If
you
are
looking
at
OpenShift
and
we
have
OpenShift
got
their
own
storage
installed,
we
have
nubo,
we
have
the
multi
cloud,
object,
a
gateway
provided
by
default,
and
and
that's
how
it
looks
like
so.
On
the
left
side,
we
have
the
applications.
The
applications
are
any
application
that
can
currently
use
AWS
s3.
It
can
be
a
custom
application.
It
can
be
existing
custom
application,
any
an
offender
that
has
an
application
like
backup
application
so
on
they
usually
have
three
API
integration,
so
you
can
use
that
as
well.
So
these
are
the
application.
B
They
always
use.
This
sta
P
I,
provided
above
by
the
multi
cloud,
object
gateway
on
the
right
side.
We
have
all
the
flexibility
hidden
underneath
so,
as
I
mentioned
before
by
default,
you
can
immediately
start
working,
you
don't
need
any
configuration,
but
when
you
want
to
start
progressing
and
scale
and
start
thinking
about
the
DevOps
and
and
how
do
you,
how
are
you
going
to
deploy
it
for
customer
in
productions?
You
can
start
playing
with
this
flexibility,
as
I
mentioned
before
you
can
use
local
resources
by
on-prem.
B
B
B
It
opens
many
additional
opportunities
to
work
to
have
locality,
for
example,
so
we
can
have
multi
cloud
object,
gateway
in
each
one
of
the
environments
and
we
can
replicate
data
between
these
clusters,
so
customers
or
applications
that
are
running
on
the
upper
cluster
can
use
the
data
and
have
it
locally,
which
might
be
important
for
performance,
for
example,
but
also
whatever
it's
written
here.
It
will
be
replicated
to
the
cluster
on
the
bottom
and
so
on,
so
it
actually
expands
more
and
brings
to
the
table
and
more
opportunities.
B
I
didn't
mention
the
UI
story.
I
did
mention
the
user
experience
before
and
also
for
this
component.
We
have
it's
on
you
I.
As
you
can
see,
it's
very
easy.
It's
very
clean,
and
one
of
the
things
that
we
are
currently
doing
is
to
bring
most
of
the
value
directly
to
the
OpenShift
dashboard.
So
you
don't
even
need
to
go
to
this
area
by
default.
We
are
bringing
all
this
information
directly
to
the
opposite
dashboard
and
it's
already
part
of
our
versions
that
are
running
current
in
under
openshift
itself.
B
Now
I
would
like
to
have
a
little
deep
dive.
It's
not
that
deep
Lori's,
but
it's
important
to
explain
a
bit
how
it's
working
to
understand
that
we
actually
brings
all
so
many
solutions
for
security
issues,
for
example,
and
questions
that
usually
I'll
pull
you
up
popping
up
when
you
are
talking
with
customers
about
cloud
usage,
for
example.
So
whenever
an
application
is
writing
data
to
the
multicolor
object
gateway,
we
have
fragmentation,
so
we
will
chunk
every
data
to
multiple
chunks.
B
We
have
the
deduplication,
so
if
something
is
already
written,
if,
if
it's
part
of
a
movie,
if
it's
part
of
text
file,
if
it's
part
of
a
presentation,
if
it's
a
picture
that
we
already
saved,
we
will
eliminate
it
will
not
go
on
and
write
the
data.
We
have
the
compression
and
we
have
the
encryption.
So
whenever
we
are
writing
data,
we
can
actually
decide
that
we
are
storing
the
data
in
one
of
multiple
locations
and
then
the
result
would
be
that
all
the
metadata
is.
B
We
keep
all
the
metadata
Oh
inside
the
multicolored
object
gateway
together
with
the
kids
and
the
data
itself
is
encrypted
in
small
chunks
and
it's
either
on
Prem
or
in
the
cloud,
but
it's
always
the
same
always
encrypted,
always
small
chunks
for
part
of
the
customers.
This
separation
between
the
key
and
the
data
is
very
important
and
also
the
fact
that
they
can
control
the
keys
and
even
if
someone
breaks
into
their
cloud
accounts,
the
data
is
not
really
usable.
B
I
would
like
to
mention
additional
security
features
again,
because
this
is
part
of
the
first
questions
that
we
usually
get
about
the
encryption.
So
as
I
mentioned
before
we
have
in
Christian
invested
in
motion
animation.
Masking
is
something
that
we
also
have
for
every
bucket.
We
have
triggers
so
you,
the
customers,
can
build
their
own
processing
flow.
So,
for
example,
I
want
to
create
I
want
to
scan
any
every
object
that
are
writing
to
the
bucket
and
make
sure
that
it
does
not
include
the
social
security
number
or
credit
card
information.
I
can
do
it.
B
I
can
trigger
a
function
that
will
scan
my
scan.
My
object,
let
let's
assume
it's
a
log:
it
will
scan
the
log,
make
sure
that
it
does
not
include
any
private
information
any
privacy
concerned.
It
will
mitigate
it
by
that
and
then
it
will
be
written
to
another
bucket,
for
example,
that
is
actually
in
the
cloud.
Okay,
that's
just
an
example.
If
we
have
genomics
information,
we
can
actually
chunk
it
by
preset
and
decide
that
this
part
of
the
data
will
be
written
to
a
private
location.
Another
one
will
be
replicated
to
the
cloud.
B
B
Another
mechanism
that
we
have
and
it's
going
to
help
us
will
introduce
the
warm
support,
is
the
fingerprinting.
So
we
have
a
printable
fingerprint
for
every
data
that
we
keep
and
we
keep
tracking
and
checking
it
and
make
sure
that
the
data
is
always
intact,
and
if
we
discover
that
something
is
wrong,
we
quarantine
it.
We
delete
it
and
we
restore
it
from
a
trusted
location
and
everything
is
automatic,
of
course,
and
and
it
is
to
create
a
very
high
trust
on
with
every
storage
that
we
are
using.
Underneath.
B
Last
slide
before
moving
to
questions
it's
about
technology,
as
I
mentioned
before
the
multi-cloud
objeto
is
based
on
nuba
technology.
It's
now
it's
an
open-source
project.
You
can
read
about
the
noble
project
in
in
no
batata
yo.
We
have
a
github
repo
for
our
core
technology
for
operator,
C&C
aligned
so
on.
So
everything
is
available
for
your
for
you
to
to
read
and
interact
and,
of
course,
to
contribute
code.
If
you
like,
and
the
Enterprise
version
is
part
of
open
ships
container
storage,
we
released
it
on
January
2020.
B
B
A
Right
well,
thank
you
for
that,
and
we
do
have
a
question
from
the
audience
rob
is
asking:
is
there
a
suggested
configuration
by
Red
Hat
to
optimize
the
performance
and
an
in
openshift
cluster?
Is
that
true
that
open
ship
has
the
best
performance
on
HW
that
high
availability?
Maybe
clusters
are
with
the
right
configurator.
B
So
whenever
you
start
it
starts
as
an
entry
level,
but
if
there
is
no,
if
there
is
an
activity
that
requires
more
resources
and
if
the
older
scale
will
kick
in
and
we'll
try
to
support
it
by
simply
creating
more
endpoint
that
will
serve
the
data
and
transparently.
So
we
do
have
a
whole
day
of
the
mechanism.
We
do
have
all
the
tools.
I
would
say
to
support
a
performance
and
I
hope
that
we'll
be
able
to
provide
the
numbers
as
well.
A
So
if
you're
looking
for
those
details,
I'll
add
them
into
the
blog
post,
which
will
have
this
YouTube
video
embedded
in
it,
and
we
will
hopefully
answer
some
more
questions
in
person
in
the
coming
weeks.
Again.
Open
ship,
comm,
/
storage
is
sort
of
the
landing
page
for
all
things:
storage
that
we're
working
on
and
the
Nuba
page
on
github
as
a
lot
of
the
information
as
well
around
the
multi-cloud
gateway,
object,
gateway,
stuff,
any
last
words
air
on
No.