►
Description
Lighting Talk: Introdcution to Trilio - Rodolfo Casas (Trilio)
This OpenShift Commons Gathering was held on July 6, 2022 live in London, England
https://commons.openshift.org
A
Okay,
first
thing
I
wanted
to
say
is
I
hate
flying.
I
came
yesterday,
so
you
better
listen
to
me
because
it
took
a
great
effort
to
me
and
I'm
flying
again
today.
So
thank
you
very
much
so
trillo.
We
are.
A
A
data
protection
solution
for
kubernetes
and
for
openshift
we
were
founded
in
2013,
and
this
is
what
I'm
going
to
talk
about
today.
Hybrid
cloud
challenges
I
was
listening
to
redcat
talking
today
and
all
the
words
they
use
are
really
familiar
to
me
because
I
listen
to
them
every
day
at
trillium
cloud
native,
hybrid
automation,
mobility,
all
this
stuff
replication.
So
it's
it's
really
really
aligned
with
us.
Okay,
what
right
so
some
challenges?
Probably
some
of
them
are
familiar
to
you.
A
Governors
and
compliance,
ransomware,
slas
application,
migration
complexity,
okay,
click,
yeah,
traditional
data
protection
technologies,
they're
all
now
we
need
something
new.
We
are
more
like
micro
services
oriented.
We
have
hundreds
of
objects
spread
in
our
kubernetes
clusters,
conflict
maps,
secrets
all
types
of
metadata
in
open
shift,
persistent
volumes.
Things
can
be
in
different
working
nodes
at
the
same
time.
So
it's
difficult
to
do
that.
Okay,
so
we
need
tools
that
are
highly
automated
api
driven.
Okay.
I
will
talk
about
a
little
more
about
this
later
on
multi-tenant
all
cloud
native
pillars.
A
Okay,
so
in
all
our
products
we
support
three
products
at
the
moment:
red
hat
virtualization
reference,
openstack
and
openshift,
okay
kubernetes.
We
all
have
all
have
these
like
pillars
in
all
of
them:
okay,
agentness.
We
don't
have
any
agent,
you
don't
have
to
do
any
modification
to
anything.
Okay,
we
are
non-disruptive.
We
use
csi
to
take
snapshots
of
the
persistent
volumes
and
then
use
temporary
volumes
to
take
the
data
out,
multi-cluster
and
multi-tenant.
We
have
different
ways
of
extract
interacting
with
our
product
ui
for
users
that
don't
use
it
a
lot.
A
You
know
so
you're
not
very
familiar
with
backup,
but
you
have
a
team.
They
want
to
do
themselves.
Okay,
we
have
the
ui.
They
can
manage
several
clusters.
At
the
same
time,
we
also
have
the
command
line.
You
don't
have
to
learn
any
other
tool,
just
cube
cattle
or
oc,
and
you
can
manage
everything
as
with
openshift
or
kubernetes.
No
new
skills,
no
new
different
tool.
Okay
cell
service,
ui,
integrated
a
developer,
will
see
what
he
is
allowed
to
see
thanks
to
rbac
in
kubernetes.
Okay,
we
follow
that
security
principle
scalable
infinite
scale.
Why?
A
Because
we
are
processes,
containers,
spots
routes,
everything
running
inside
openshift,
okay,
so
we
grow
with
your
cluster.
Okay
and
one
of
the
most
important
things
for
me
is
open,
universal
backup
schema.
We
save
the
data
as
qco,
so
if
one
day
you
get
angry
with
the
telephone,
you
can
still
open
your
backups.
Okay,
some
customers
ask
me
okay,
30
years
from
now,
will
you
will
my
backup
be?
A
Can
I
be
able
to
use
my
backup?
Yes,
if,
as
long
as
linux
with
kvm
exists,
you
will
be
able
to
open
your
backups
because
they
are
stored
in
cuco
and
metadata
in
json
okay,
so
we
try
to
cover
everything:
okay
and
everything,
agnostic.
Okay,
we
are
really
aligned
with
redcat,
as
you
can
see
here,
for
example,
red
graphite
virtualization.
We
build
it
together.
Okay,
agnosticism,
we
are
application-centric.
A
We
are
certified
for
many
distributions.
Basically
any
cncf
compatible
kubernetes
distribution,
and
why
I'm
telling
you
this?
Because
we
are
a
hybrid
world?
Aren't
we?
If
we
are,
we
need
to
be
agnostic
about
the
distribution
right.
This
is
our
ui.
You
can
see
different
clusters.
We
are
agnostic
about
the
cluster
agnostics,
about
storage.
We
support
nfs
and
s3
compatible
as
backup
target
any
public
cloud.
You
can
run
on
openshift
on
azure
on
aws
on-prem.
Whenever
you
want,
whatever
you
want,
okay
and
also
agnostic
about
how
do
you
deploy
your
applications,
you
like
to
use?
A
Namespaces
labels,
helm,
charts
operators,
whatever
you
can
filter
whatever
you
want,
and
then
we
will
back
it
up.
Okay,
I
told
you
we
have
an
ui.
You
can
use
cube
cattle
oc
with
jamal
files.
You
can
use
our
full
api
to
integrate
with
whatever
tools
you
use
in
your
enterprise,
but
we
also
have
out
of
the
box
integration
with,
for
example,
ansible.
A
Okay,
I
didn't
have
time
to
play
my
three-minute
video,
but
if
you
search
in
google
blog
ansible
trillio,
you
see
a
blog
post
from
me,
where
I
explain
very
basic
introduction
to
integration
with
the
kubernetes
module.
So
you
can
do
anything
we
do
on
the
command
line
or
the
ui.
You
can
implement
it
with
ansible
from
backup
restore
migrate,
an
application
from
one
cluster
to
another
open
shift
on-prem
to
auto
restore
disaster
recovery.
Whatever
you
want,
it's
just
automation
is
like
a
wrapper
for
what
you
do
on
your
everyday
tasks.
A
You
know
but
we're
using
git.
You
know
what
I
mean
right:
faster,
less
error,
prone
use
cases,
and
this
is,
I
always
make
the
same
joke
you,
buy
the
backup
and
recovery
and
for
free
you
get
disaster,
recovery,
application,
mobility,
migration
and
ransomware
protection
all
in
the
same
price.
One
license
okay,
and
we
only
have
one
level
of
support
the
best
to
our
sla.
A
So
you
will
have
you
will
have
someone
answering
to
you
in
two
hours
worldwide?
Okay,
so
one
license
and
that's
it.
Why
truly
evolved
for
open
shift?
Many
things?
Okay,
I
was
thinking
why
put
to
put
so
many
things
here,
because
I
saw
the
camera
they
are
recording
it.
So
when
you
go
online,
you
can
just
click
pause
and
you
can
read
everything:
okay
slowly.
You
know
so,
for
example,
cloud
native
and
agentless
only
that
that's
really
good.
A
Okay,
github's
integration,
I'm
doing
a
lot
of
work
nowadays
in
the
telco
world
with
github
zero
touch
provisioning.
A
It's
really
red
hat
is
changing
in
the
the
view
on
this
okay
and
I'm
following
and
we
are,
we
are
yeah,
as
I
said,
ansible
and
github's
automat
integration
out
of
the
box.
Okay.
So
if
you
want
to
deploy
your
postgres
application,
why
not
deploy
your
backup
strategy
at
the
same
time,
so
you're
backed
up
from
the
minute
one?
Okay,
you
can
do
that
with
githubs
another,
the
fourth
one
reviews
management
complexity.
That's
another
really
huge
concern.
Security
is
a
concern.
Data
loss
is
a
concern,
but
complexity
is
another
one.
A
Also
lack
of
skills
or
people
training
this
stuff,
okay,
so
but
yeah.
We
try
to
reduce
complexity
because
you
will
be
using
the
same
tool
across
all
your
infrastructure
and
it
doesn't
matter
if
it's
on
the
central
hub
or
remote
or
edge
computing,
or
it's
open
shift,
on-prem
or
auto.
It
doesn't
matter.
Okay,
it's
all
the
same
thing,
our
approach
to
customer
success.
Okay,
also,
when
we
sell
something,
we
sell
it
to
the
managers,
but
there's
always
a
disconnect
between
what
the
managers
bought
and
what
the
operations
team
are
going
to
use.
A
Okay,
so
this
onboarding
training
that
is
really
important
tell
them
listen.
This
is
going
to
happen
to
you
and
when
it
happens,
because
you
know
it's
always
the
backup
tool.
No,
this
is
failing.
It's
backup
tool.
I
say:
maybe
yes,
maybe
not!
It
can
be
the
backup
tool.
It
can
be
openshift.
It
can
be
you
yeah.
Sometimes
it's
you
I'm
sorry.
You
did
something
wrong:
okay,
so
yeah
onboarding
training
telling
them
about
best
practices.
A
What
usually
happens
to
customers
ongoing
engagement?
We
don't
wait
for
you
to
call
us.
We
will
call
you
hey.
How
is
he
going?
Is
it
everything
good?
You
need
something
you
want
to
you
want
to
know
about
this
new
feature.
We
have
okay,
so
and
yeah.
Of
course,
like
red
hat,
says
we
you
don't
buy
a
product,
you
buy
our
support,
your
relationship
with
a
technical
guy.