►
From YouTube: Keynote Simplifying Database Cloud Service Access w/ RHODA Mike Piech Red Hat OpenShift Commons 2022
Description
Keynote: Simplifying Database Cloud Service Access with RHODA
Mike Piech (Red Hat)
OpenShift Commons Gathering on Databases held on 02/23/2022
Slides: https://bit.ly/3hijP3S
Join OpenShift Commons: https://commons.openshift.org/index.html#join
Full Agenda here:
https://commons.openshift.org/gatherings/OpenShift_Commons_Gathering_on_Databases.html
A
The
first
step
is
to,
of
course,
learn
about
how
to
connect
your
database
or
database
services
to
your
applications,
and
we
have
mike
pesch
from
red
hat,
who
is
here
to
speak
to
a
very
interesting
solution
that
his
team
has
been
working
on.
Mike
is
a
vp
and
a
general
manager
for
cloud
storage
and
data
services
and
he's
leading
the
shoda
initiative
at
redhat.
That
he's
going
to
talk
to
us
about
today.
So
over
to
you
mike.
B
First
off
thanks
so
much
for
the
the
warm
introduction.
I'm
super
excited
to
be
in
front
of
openshift
commons
here.
This
is
actually
my
first
time
presenting
here,
so
so
that's
exciting
and
and
and
very
honored
to
have
the
the
keynote
slot
here,
and
I
I
personally
and
passionately
believe
in
this
particular
area
that
we're
putting
a
lot
of
investment
into
so
I
I
hope,
you'll
also
find
it
worthy
of
of
keynote
here
given
given
all
the
things
that
we're
talking
about
today.
B
I
hope
this
will
be
a
nice
framing
for
the
data
related
solutions
and
technology
discussions
that
we'll
be
having
for
the
rest
of
the
day.
Again,
my
name
is
mike
peach,
I'm
vice
president
general
manager
of
a
business
unit,
red
hat,
called
data
services
or
cloud
data
services.
We
today
have
we
were
formed
out
of
pieces
of
some
other
bus
cloud
storage
as
and
we
have
some
brand
new
technologies
that
have
come
out
of
the
office
of
the
cto
here.
B
So
this
is
very
much
a
small
and
new
part
of
red
hat
with
exciting
growth
areas
that
were
that
we're
doing
very
new
things
in
another
thing.
To
note
about
what
this
business
unit
and
what
I'm
about
to
talk
about
is
in
terms
of
a
business
model
and
a
delivery
model
is
that
these
are
managed
services
right.
So
the
technology
that
we're
talking
about
here
is
offered
in
an
as
a
service.
You
know
software
as
a
service
sas
model,
which
is
a
new
area.
B
It's
a
different
thing
from
what
red
hat
has
done
in
the
past
and
what
red
hat
is
known
for,
so
so
keep
that
in
mind
that,
from
that
angle,
what
we're
talking
about
here
is
is
new
for
red
hat
now
so
to
dive
down
into
the
specifics
of
the
the
topic
at
hand
here,
we're
talking
about
database
access
for
developers
and
management
of
that
access
for
administrators
of
openshift,
customer
custers
clusters
and
openshift
environments.
More
generally.
B
So
these
the
the
types
of
concerns
that
we're
going
to
talk
about
here
are
are
cross-cluster
and
very
much
representative
of
the
hybrid
cloud
environment
and
hybrid
cloud
strengths
that
red
hat
is
known
for.
So
let
me
first
sort
of
set
it
up
the
premise
here.
The
starting
point
for
what
we're
trying
to
do
is
that
connection
should
be
easy
right
and
connections
in
a
kubernetes
environment
in
a
highly
distributed.
B
So
that
probably,
is
that's
big
enough
that
it's
probably
fair
to
say
that
most
of
you
out
there
are
firmly
in
that
in
that
camp,
you're,
doing
cloud-based
data,
cloud-based
databases,
cloud-based
data
services
and
again
just
to
re-highlight
the
point
jalen
made
from
our
own
survey
data
earlier
76
of
the
top
workloads
in
kubernetes
environments,
include
databases
and
and
data
caches
right.
So
this
is,
you
know,
it's
easy
to
say:
yeah
every
application
needs
a
database.
B
You
know,
and
here
here's
some
of
the
real
numbers
to
just
show
how
dramatic
the
the
share
of
workloads
really
is.
Now,
in
a
cloud
environment,
there
are
at
least
two
broad
categories
of
how
you
might
set
up
a
database
and
and
more
generally,
your
your
data
environment
right,
they're,
self-managed
right.
So
you
can
go
in
your
openshift
cluster
today,
whether
it's
something
that
you're
running
on
premises
or
whether
maybe
you're
running
it.
B
That
gives
you
a
lot
of
flexibility,
but
it
also
in
implies
a
fair
amount
of
burden
of
setup
and
administration
on
the
part
of
your
own
I.t
department
and
just
to
you
know,
be
fully.
You
know
fair
and
open
and
disclosure.
You
do
have
more
control
over
the
bandwidth
right
you
as
an
internal
setup.
You
can,
you
can
optimize,
you
know,
sort
of
connection,
bandwidths
and
so
on.
B
Database
as
a
service
is
the
idea
of
having
a
database
managed
by
somebody
else
out
there
in
the
in
the
cloud,
and
you
know
an
application
developer,
and
you
know
later
the
operator,
slash
maintainer
maintains
just
a
very
lightweight
client-side
connection
and
all
the
all
the
grunt
work
of
you
know
the
redundancy,
the
the
backups
and,
and
so
on,
is
all
handled
by
that
database
as
a
service
provider
right.
So,
in
contrast
to
the
self-managed
scenario,
you've
got
easy
sign-ups,
it's
managed
for
you.
B
There
is,
you
know,
part
of
what
you
trade
off
in
order
to
get
that
is
you
trade
off
some
flexibility
right
you're
at
the
mercy
of
what
has
been
exposed
through
apis?
You
do
have
lower
complexity
and,
and
then,
of
course,
you
know
since
you're
connecting
to
this
database
over
you
know
the
internet
depending
on
you
know
you
might
both
be
in
amazon
and
both
be
in
the
same
region.
So
that
could
be
pretty
good
if
you
know
you're
in
a
private
data
center
and
you're
connecting
to
somewhere.
B
You
know,
let's
say
in
azure.
Well,
you
know
so
you've
got
to
make
sure
that
you
understand
the
bandwidth
capabilities
and
and
what
your
particular
problem
domain
means,
but
that's
a
quick
side
by
side
of
those
two
scenarios
now
managing
database
as
a
service
in
you
know
a
typical
larger
enterprise
or
even
medium-sized
enterprise.
Where
you've
got
you
know,
probably
not
even
just
one
but
multiple
open
shift
clusters.
You've
got
many
applications.
You've
got
many
development
teams
carrying
out
different
activities
at
different
stages
of
an
application
life
cycle.
B
B
So
you
know
you
can
imagine
that
if
you've
got
app
developers,
you
know
in
one
or
more
clusters
you
know
just
willy-nilly
reaching
out
and
putting
in
their
credit
card
data
and
signing
up
for
database
as
a
services.
Things
can
quickly
get
kind
of
crazy
right.
You
can
end
up
with
lots
of
redundant
instances.
You
end
up
with.
Potentially
you
know,
unconstrained
usage.
B
Scientists
are
onboarded.
Life
is
great
for
a
while,
until
one
day
at
one
of
the
many
status
meetings,
the
leadership
points
out
that
your
group
has
burned
through
the
entire
year's
cloud
budget,
and
it's
only
may
so.
You
go
into
you
know.
Somebody
goes
into
the
cost,
explorer
and
amazon
and
and
that
trickle
from
multiple
fire
hoses
all
these
different
developers,
data
scientists
doing
all
this
stuff
has
accumulated
an
s3
storage
bill
of
almost
a
hundred
thousand
dollars
a
month
right.
So
that's
the
that's.
B
You
know
a
very
real
phenomenon
out
there
and
very
much
the
kind
of
thing
that
we're
trying
to
address
with
with
the
technology
I'm
about
to
talk
about
now.
Another
aspect
of
that
the
challenges,
the
slide
that
I
just
went
through
is
you
know
so
setting
up
a
database
as
a
service
like.
Let's
just
do
a
quick
walk
through
that
right.
So
you
go
out
to
the
service
in
this
case
I'm
using
mongodb
atlas
as
an
example
and
to
be
clear
right.
B
This
is
no
dis
on
it's
a
fine
workflow
and
and
the
others.
You
have
a
similar
sequence
right.
So
you
you
go
fill
out
some
stuff,
you
verify
email!
Then
you
get
into
a
welcome
screen.
You
start
choosing,
you
know
various
configuration
parameters,
you
know
you're,
you're,
free
or
or
what
kind
of
price
tier
you
want
to
be
at.
You
set
up
a
shared
cluster.
You
set
up
some
security
parameters
and
credentials.
B
You
know
so.
Basically,
you
know
a
dozen
steps
and
you're
at
a
point
now,
where
you've
got
a
cluster
set
up,
you've
got
a
you've
got
an
a
login.
Username
you've
got
a
password.
You've
got
the
credentials.
You
need
that
you
can
now
go
back
into
your
application.
Development
environment
enter
that
data
and
and
connect
to
this
database.
Now
again,
fine
workflow
makes
a
lot
of
sense
to
do.
You
know
that
setup
time
you
know
on
an
infrequent
basis.
B
Now
you
imagine
you
know
many
many
developers
in
a
typical
development
environment
all
doing
this
every
time
they
want
to
go
to
a
database.
Well,
that's,
obviously
pretty
inefficient
and
and
fraught
with
potential
errors.
Developers
might
not
know
what
a
lot
of
the
configuration
parameters
even
mean
and
what
to
choose
etc.
B
Now
the
idea
here
is
to
take
database
as
a
service
connections
have
an
administrator
be
able
to
pre-configure
them,
pre-set
them
up
and
put
them
on
the
shelf,
so
to
speak
in
an
open
shift
environment
then,
thereby
allowing
developers
to
just
go
connect
to
that
already
set
up
local
representation,
local
instantiation
of
that
database
as
a
service
without
having
to
go
through
those
those
dozens
or
so
steps
that
I
just
highlighted
previously
so
and
we'll
see
in
a
moment
just
how
much
simpler.
That
is
for
the
developer.
B
B
So,
let's
get
concrete
this
and
we'll
see
in
our
timeline
in
a
little
bit,
but
this
technology
this
offering
is
in
early
access
right
now,
so
it
just
went
from
from
alpha
to
what
we're
calling
service
preview
in
the
last
24
hours.
So
we've
added
some
new
features
beyond
what
we
started
with
back
in
november,
but
anyway.
B
B
I
get
a
screen
with
a
number
of
different
types
of
things.
To
add.
I
go
into
the
connect,
a
database
area
that
gives
me
a
number
of
options
and,
as
we'll
highlight
you
know,
we're
coming
out
the
gate
here
with
with
three
database
as
a
service
partners,
we've
got,
we've
got
mongodb
atlas,
we've
got
crunchydb
and
crunchy
bridge
as
they
call
their
service
and
cockroachdb.
B
B
So
that
six
step
process
is
a
is
a
very
quick
and
easy
workflow
for
the
developer,
using
a
rota
connection
that
has
been
set
up
by
an
admin
now
on
the
admin
side.
So
the
admin
in
order
to
set
up
a
connection
they'd
go
through
the
12
steps
and
and
and
set
up
the
for
each
of
the
the
database
as
a
service
providers.
B
They
wanted
to
enable
within
a
given
open
shift
environment
and
then
what
I
just
one
won't
re-walk
you
through
all
that
work
flow,
but
what
I
did
want
to
show
you
right
here
is
that
here's
an
example
of
the
of
the
visibility
right
of
the
monitoring
screen
where
the
admin
can
see.
You
know
what
clusters
are
connected
to,
what
services
and
what
users
and
what
apps
right.
So
there's
and
we'll
be
sort
of
further
fleshing
this
out
over
time.
B
I
want
to
highlight
a
couple
of
kind
of
use.
Case
categories.
You
know
this
is
a
very
general
purpose
capability.
Obviously,
you
know
almost
any
app
needs
some
kind
of
data
management,
so
the
the
possibilities
are
endless,
but
I
did
want
to
highlight
two
particular
categories
where
using
a
database
as
a
service
versus
standing
up,
an
internal
self-service
database
might
be
just
the
thing
right
now.
One
of
these
is
an
enterprise
that
may
be
highly
distributed.
B
That
has
many
openshift
clusters,
many
openshift
environments,
but
where
they
want
their
developers
and
their
applications
to
share,
have
easy
access
to
sharing
data
again
across
that
distributed
estate
right.
So
that's
one
area
where,
rather
than
having
a
self-managed
database
in
let's
say
one
of
the
data
centers
or
one
of
the
domains
under
that
enterprise's
control,
if
they're
using
a
database
as
a
service,
it's
super
easy
and
it's
the
same
access
for
basically
any
of
their
environments,
whether
they're
on
hyperscale
or
public
cloud
environments
or
or
or
on-site.
B
B
B
So
a
quick
note
on
rhoda,
with
ai
and
ml
right
in
data
science
types
of
environments.
I
want
to
highlight
our
sister,
offering
here
red
hat
openshift
data
science,
roads
that
is
also
in
field
trials,
so
just
about
to
flip
the
ga.
So
you
know
more
than
beta,
but
but
just
a
hair
under
ga
is
it's
kind
of
state
right
now
and
you
can
you
can
look
at
that
separately,
but
the
idea
here
is:
these
are
sister
products
and
in
many
machine
learning
data
science,
types
of
environments.
B
You
have
a
lot
of
this
rapid
setup
and
tear
down
for
whether
it's
model
training,
whether
it's
sort
of
feature
engineering,
all
that
sort
of
thing
and
the
self-service
and
and
ease
of
setup
nature
of
the
database.
As
a
service
approach,
we
expect
to
see
a
lot
of
opportunity,
a
lot
of
synergy
for
those
sorts
of
environments
right
and
this
this
diagram
here
just
depicts
you
know
the
sheer
variety
of
personas.
B
You
have
data
engineers,
data
scientists,
the
app
developers
and
so
on,
and
all
of
the
different
phases
of
an
application
that
incorporates
machine
learning,
all
the
different
stages
and
the
different
data
implications
of
those
stages
right
so
as
more
and
more
enterprise
applications
involve
more
and
more,
you
know,
learning
and
data
science
capabilities,
there's
just
going
to
be
a
lot
more
of
this
transient
and
and
and
again
you
know,
quick
setup.
Teardown
of
data
stores,
for
which
database
as
a
service,
would
be
a
a
great
benefit
just
to
highlight
that.
B
Okay,
why
red
hat
you
know
part
of
what
we're
bringing
to
the
table
for
sure
is
that
expertise
and
that
that
that
respect
that
reputation
in
what
we
do
in
a
hybrid
cloud
environment,
so
we're
very
open
and
and
inclusive
and
you'll,
see
in
a
moment.
You
know
the
idea
here
is
to
to
bring
in
as
many
good
partners
as
we
can
get
set
up
here.
B
It's
a
fully
managed
cloud
service,
as
I
mentioned
the
beginning
of
the
of
the
presentation-
and
you
know
that
is
an
aspect
that
you're
going
to
see
increasingly
in
red
hat
offerings
and
as
we
you
know,
our
sre
team
is
is
top
notch
and
we
are
investing
heavily
in
this
area,
because
this
is
where
many
of
our
customers
are
going.
They
want
red
hat
to
manage
more
and
more
of
their
technology
estate
on
their
behalf.
So
the
as
a
service
model
is
is
just
exploding.
B
Us
goes
without
saying,
but
we're
red
hat,
it's
all
open
source,
so
everything
we're
talking
about
here
is
is
is
very
much
it's
up
on
github.
You
can
go
look
at
it.
You
can
participate
all
the
usual
benefits
of
that
dimension
to
the
the
red
hat
kind
of
way
of
doing
things
and
then
finally,
partners,
which
are
which
are
super
important
in
this
environment.
Because
again,
what
we
are
fundamentally
doing
is
enabling
partner
database
as
a
service
providers.
B
We
ourselves
are
not
running
a
database
as
a
service,
we're
running
we're,
enabling
connections
to
partner
database
as
a
services
and
just
again
to
highlight
the
first
three
out
of
the
gate.
Here,
we've
got
mongodb
atlas,
we've
got
crunchy
bridge,
we've
got
cockroach,
you
know,
they've
all
put
skin
in
the
game,
helped
work
on
building
those
open
shift
operators
to
enable
the
the
the
workflows
that
I
showed
earlier.
B
B
So
just
in
the
interest
of
time
here
try
to
keep
us
on
schedule
and
funny
enough
timeline
is
what
the
slides
about.
So,
as
I
mentioned,
we
went
out
with
our
alpha
of
this
back
in
november,
so
we've
been
live
for
a
couple
of
months
and
and
gotten
a
bit
of
input
and
feedback.
So
far,
we've
just
today
flipped
over
into
the
next
sort
of
level
of
let's
say,
doneness
of
of
rigor
and
testing
and
additional
features
and
we're
calling
that
service
preview.
B
B
You
know
that
field
trial
and
get
closer
to
ga
by
the
end
of
the
year.
So
that's
the
that's
the
kind
of
the
timeline
in
a
nutshell
on
that
service
preview.
This
is
again
something
that
you'll
see
increasingly
as
red
hat
moves
into
managed
services,
we'll
put
new
services
out
there
in
this
alpha
or
service
preview
type
of
mode
where
it's
free.
We
just
want
to
get
folks
logging
in
setting
up
accounts.
Doing
you
know,
working
through
the
tutorials,
trying
things
and
and
giving
us
feedback
right
and
that's
how
we
want
to
make
this.
B
So
I
will
end
with
this
note:
go
to
red.ht
access
and
from
that
url
you'll
log
into
your
red
hat,
console
you'll
see
how
to
get
started
with
rota,
red
hat,
openshift
database
access,
and
basically
you
know
it's
all
free
you'll
get.
You
are
able
to
set
up
a
free
trial
database
with
those
three
providers
I
mentioned.
There's
an
email
address
there
for
support
dbas
alpha
dash
support
redhat.com,
and
we
invite
you
to
come
in.
Try
it
out,
kick
the
tires
and
feedback
feedback
feedback.