►
From YouTube: OKD4 Deployment of Ceph and MariaDB Galera Cluster Charro Gruver Red Hat OKD Deployment Marathon
Description
OKD4 Deployment of Ceph for MariaDB Galera Cluster
Charro Gruver Red Hat
OKD Live Deployment Marathon
August 17, 2020
Day Zero Kubecon Eu
A
So
so
what
you
see
me
running
here,
I
I
pulled
from
here
specifically.
A
Let
me
clear
this
out.
If
you
guys
can
see
the
screen
on
the
left,
the
common
yaml
file
and
the
operator
openshift
yaml
file,
those
are
pulled
verbatim
from
this
project.
You
can
see
the
you
can
see
the
path
here
to
get
to
it
and
it's
release
1.4.
A
It's
the
latest
release,
I'm
not
quite
brave
enough
to
run
directly
out
of
master
at
this
point
so
back
to
the
cluster
that
we
deployed
earlier
this
morning,
you
can
see
it
is
fortunately
still
healthy,
there's
a
few
errors
being
thrown,
but
it
tends
to
do
that
in
my
home
lab
network
latency
and
such
so.
What
we're
going
to
do
first
is.
A
The
three
worker
nodes
that
we
deployed-
what
I
didn't
tell
you
when
I
deployed
them,
was
that
I
actually
deployed
them
with
an
unused
hard
drive
attached
to
the
virtual
machine,
so
it
installed
the
operating
system,
it's
using
a
sata
bus,
so
it
installed
the
operating
system
on
sda,
but
it's
got
an
sdb
sitting
there
that
is
not
currently
being
used.
A
What
we're
going
to
do
is
we're
going
to
create
a
ceph
storage
cluster
to
serve
up
block
devices
on
these
worker
nodes.
The
first
step
is,
we
need
to
label
those
nodes
to
give
them
a
roll
of
storage
node,
and
so
I
just
applied
that
label
to
them.
If
I
hit
a
quick
oc
describe
on
one
of
those
nodes,
I
can
show
you
that
it
now
has
a
role:
a
storage,
node,
okay,
so
that's
step.
One
is
we.
We
need
something
to
tell
seth
what
it's
going
to
be
working
with
step.
A
Two
is
we're
going
to
deploy
this
common
diemel,
which,
as
you
can
see,
is
creating
a
whole
lot
of
boilerplate
that
the
rook
operator
is
going
to
need,
and
one
of
the
things
that
it
did
was
it
provisioned
for.
A
And
this
will
take
a
little
bit
for
it
to
bootstrap
itself.
The
the
operator
image
right
now
is
pulling
down
and
installing,
when
the
operator
is
up,
it's
going
to
create
some
workloads,
some
pods
on
each
of
those
nodes
that
bear
the
label
so
that
they
can
discover
the
the
resources
available
on
that
node.
And
this
this
will
take
just
a
little
bit
to
run.
A
Okay
and
there
you
see
the
the
three
discover
nodes
that
are
spinning
up
now,.
A
Okay,
the
cluster.yaml
file
is
the
thing
that
actually
defines
our
particular
ceph
cluster
and
again,
the
the
rook
project
has
a
a
boilerplate
copy
of
this
for
you
to
to
take
and
modify
to
your
own
purposes.
This
is
the
version
of
ceph
we're
going
to
be
running
15.2.4.
A
A
Just
like
you
see
in
a
typical
deployment,
and
here
is
the
piece
of
magic
that
tells
it
where
to
find
those
devices
that
it's
going
to
create
the
stuff
storage
cluster
on
now,
our
operator
appears
to
be
fully
bootstrapped
and
up
and
running,
so
the
next
step
is
to
go
ahead
and
deploy
our
stuff
cluster.
On
top
of
that
all
right
now,
this
is
also
going
to
take
a
little
bit
and
you're
going
to
see
a
bunch
of
activity
here.
As
the
operator
provisions
this
cluster
there's
the
three
monitor
instances.
You
just
saw
spin
up.
A
A
Then
the
seth
cluster
is
up,
and
it
is
ready
for
use,
looks
like
we're
still
waiting
for
one
of
the
crash
collectors
to
go
into
a
ready
state,
but
everything
else
at
this
point
should
be
usable.
A
A
I've
created
a
storage
class
here
that
I'm
going
to
apply
its
name
is
rook
seth
block,
and
it's
going
to
use
the
new
rook
csi
plugin
that
we
just
deployed
as
the
provisioner.
A
All
right
now
we
should
have
persistent
volume
claim
and
the
key
here
you
can
see
now
it
is
bound
to
an
automatically
provisioned
persistent
volume
that
our
ceph
cluster
kindly
handed
out
for
us.
We
can
see
that
from
the
command
line
as
well
there.
It
is
100
gigabytes
now,
remember
if
you
were
watching
previously
when
we
deployed
the
openshift
cluster,
we
gave
our
image
registry
an
ephemeral
volume.
A
We
need
to
remove
that
ephemeral
volume
before
we
give
it.
The
new
volume
so
caveat
here.
Any
images
that
you
current
that
you
had
put
in
between
you
you're
going
to
lose
those
because
we're
yanking
away
the
the
storage.
You
will
lost
them
anyway,
because
this
is
an
ephemeral.
A
A
A
Shell
script,
that
is
going
to
be
run
by
the
image
when
it
starts
up
that
actually
provisions
the
mariadb
cluster
detects
whether
or
not
a
cluster
already
exists,
if
it's
the
first
node
in
the
cluster
so
forth,
and
so
on.
I've
got
a
short
tutorial
written
up
on
this
that
you
can
see.
So
I
won't
drain
it
here.
We'll
just
do
the
fun
and
kick
it
off.
B
A
Okay-
and
I
am
in
the
right
cluster-
important
safety
tip-
always
make
sure
you're
logged
into
the
right
cluster,
so
I
need
to
expose
a
route
for
the
image
registry.
What
I
just
did
is
I
patched
the
image
registry
operator
to
say:
create
a
default
route
so
that
I
can
externally
get
to
my
image
registry.
A
Then
I'm
going
to
use
podman
and
I'm
going
to
log
into
that
image
registry
array.
It
succeeded
and
now
I'm
going
to
do
a
podman,
build
and
build
our
mariadb
image,
and
you
see
I'm
I'm
grabbing
the
route
from
the
from
the
image
registry
to
tag
my
image
that
I'm
getting
ready
to
build
so
that
I
can
push
it
to
the
directory.
A
A
It,
let's
create
a
service,
account:
okay,
we're
going
to
create
a
service
account
for
mariadb.
The
reason
is:
mariadb
is
picky
about
its
uid
and
it's
especially
picky.
If
it
restarts
and
its
uid
has
changed,
it
tends
to
get
upset
so
we're
creating
a
service
account
and
we're
actually
going
to
run
this
privileged
with
this
new
service
account
so
that
it
can
run
as
any
uid.
A
A
A
And
you
see
the
first
node
in
our
three
node
galera
cluster
is
now
starting.
B
A
See
not
there
not
sure
why.
B
It
may
be
one
of
the
ones
that
we
need
to,
as
a
working
group
add
in
a
community.
A
B
A
Yeah
and
that's
why
I
I
deployed
it
by
using
the
operator
configuration
that
is
provided
in
the
kubernetes
stuff
examples
in
the
rook
project
itself.
A
All
right,
so
our
second
cluster
node
is
coming
up,
and
these
do
and
these
do
an
ordered,
startup
and
an
ordered
shutdown
so
that
you
can
gracefully,
stop
and
start
this
cluster
and
it
will
retain
its
state,
and
when
this
is
done,
we
have
a
three
node
maria
db
galera
cluster.
That
is
a
full
multi-master
database
cluster
running
in
our
openshift,
with
provision,
storage,
wow.
B
Well,
played
thanks
charo.
That
was
pretty
awesome.
I
think
I
I
and
I
keep
emphasizing
in
the
chat
too
is
well.
Some
of
the
operator
work
is
the
next
things
on
the
road
map
that
we're
trying
to
get
folks
to
work
on
so
getting
some
of
those
default
operators
from
operator
hub
into
community.