►
From YouTube: OCB: Built for the Cloud - A Founder's Story (Trilio)
Description
Trilio has a unique story. It's founder, after spending 15 years working with large infrastructure providers like EMC and VMware, could see the oncoming disruption driven by cloud computing. The scale, performance and mobility offered by hybrid- and multi-cloud infrastructure would require a new way of managing and protecting applications and their data. In this session, we hear from Murali Balcha and how he set out to build a new platform from the ground-up for this new cloud-native era and support the needs of both IT/cloud architects and DevOps Engineers alike.
A
Welcome
to
the
next
edition
of
the
openshift
operator
hours
show
so
today
we're
lucky
enough
to
have
with
us
trillio
and
we
are
going
to
be
talking
with
murali
balcha
who's,
the
founder
and
chief
technology
officer
of
the
company,
as
well
as
preshanto
cochavara
who's,
the
director
of
product
so
welcome.
Gentlemen.
Welcome
to
the
tv
show
today.
A
A
You
know
I
I'm
going
to
make
a
last
night
cyrus
champion.
I
decided
we
were
going
to
make
a
round
of
t-shirts
for
everybody,
and
one
of
them
is
going
to
say.
Can
you
see
my
screen
and
then
the
other
shirt
is
going
to
say,
hey
you're,
on
mute,
and
so
everybody
can
be
wearing
these,
and
if
someone
is
that
we
can
all
just
start
pointing
at
our
shirts,
you
know.
B
A
C
Yeah
yeah,
so
I
founded
trillia
in
2013.
It
almost
feels
like
eons
back
so
before
that
I
was
at
emc.
I
spent
almost
15
16
years
at
emc
emc.
We
know
it's
a
pioneer
in
storage
area
networks.
They
single-handedly
invented
the
stories.
I
was
part
of
that
journey.
I
think
I
was
fortunate
enough
to
basically
work
get
to
work
on
almost
every
storage
area
technologies
that
that
is
there.
So,
when
emc
bought
vmware,
I
was
leading
the
integration
of
virtualization
with
emc
technologies
and
again
back
in
2012
2011.
C
C
C
These
products.
They
were
there
since
1980s.
When
tape
was
the
predominant
backup
media
and
they
haven't
really
evolved
much
since
then,
I
think
they
still
have
client
server
architecture,
they
back
up
lots
of
files
and
it
is
administered
by
one
central
administration,
and
so
it
wasn't
really
meant
for
cloud.
So
cloud
is
a
different
paradigm.
C
A
A
You
know
I
I
do
marketing
activities
with
our
partners
once
they've
certified
their
software
and
we're
going
to
get
to
that
in
a
little
minute
about
your
your
support
for
open
shift,
but
you
know
names
of
bugs.
You
know
rock
rocket,
you
know
names
of
rockets
and
you
know
what
what's
what's
why
what
why
trillio.
C
C
A
A
You
know
if
your.
If
your
logo
is
like
this,
it
makes
it
really
challenging
to
do
branding
with
other
companies.
So
I
don't
know
I
I
just
thought
I'd
bring
that
up
anyway.
So
founding
the
company
was
smooth
sailing,
you
you,
you
got
a
little
bootstrap
capital
and
then
everything
just
went
perfectly
as
planned,
or
what.
C
Absolutely
no
hiccups,
nothing.
It
was
a
strike,
drag
race,
no
yeah
it
wasn't
it
wasn't
that
you
know.
I
think
we
you
know.
Every
startup
company
has
some
challenges.
Some
you
know
hitting
that
mark
with
the
business
case
right.
Some.
Some
companies
can
do
much
better.
I
think
partly
they
are
lucky
and
partly
they
probably
read
the
market
very
well,
but
a
lot
of
other
companies.
I
think
they.
They
have
some
winding
paths
like
some
trial
and
error
methods
until
they
get
the
act
together
right.
C
We
know
we
have
a
big.
A
big
opportunity
here
in
the
cloud
cloud
is
going
to
be
the
next
biggest
thing
back
in
2012-13,
right
and
but
but
you
know
the
hype
that
we
had
at
the
time
when
we
left
the
company
and
start
and
then
kind
of
exploring
and
talking
to
a
lot
of
companies,
it
didn't
really
match
with
them
with
the
reality
right.
Every
company
wants
to
do
something
in
the
cloud.
They
want
to
basically
re
organize
their
I.t
into
the
cloud
paradigm,
but
reality
is
different
right.
C
They
still
have
the
older
business
process
in
place.
They
use
the
old
technologies,
so
it
was
a
bit
of
a
surprise
for
us,
like
you
know
the
high
versus
reality
and
and
we
in
initial
few
years
it's
it's
a
bit
of
a
struggle
to
find
those
customers
who
are
looking
for
a
product
in
the
back
of
space
and
the
on
top
of
it,
especially
with
the
backup
backup
is
not
a
day
one
problem
right:
they
need
to
first
deploy
the
applications
in
the
production.
C
A
Years,
wow
and
and
trillio
vault
for
data
protection.
It's
it's
a
cloud
native.
Is
it
it's
built
on
kubernetes
for
kubernetes?
How
is
that?
Why
does
the
world
need
another
data
protection
solution?
I
mean
I
I
I've
been
around.
You
know
as
as
long
as
dirt,
and
you
know
back
in
the
day
when
I
was
a
digital
equipment
corporation.
There
were
great
backups
pieces
of
software
and
you
know
they've.
You
know
we
all
know
the
names
of
them,
but
how
come
people
just
don't
use
something?
A
C
Yeah,
well,
it's
ideal
right.
It
requires
constant
innovation.
The
I
I
think
you
know
most
of
the
backup
systems
that
they
developed.
They
are
very
much
detached
from
the
platform.
They
are
protecting
right.
It
was
okay
in
the
windows
linux
bunch
of
linux
servers,
but
I
think
when
you
look
at
the
cloud,
they
layered
some
kind
of
management
layer.
On
top
of
this
form
of
servers
right
they
have
the
multi-tenancy,
they
have
the
self-service
aspect
of
it
and
the
scale-out
architecture
of
it.
C
So
the
world
paradigm
is
there.
You
have
a
backup
administrator
who
knows
every
application
out
there
and
knows
how
to
backup
and
restore
that
doesn't
really
work
with
the
cloud
cloud
is
more
about
self
provisioning.
So
if
I
want
to
provision
10
applications,
I'll
go
and
provision
right,
I'll
I'll
manage
everything,
there
is
no
central
administrator
who
basically
helped
me
provision
the
resources
that
I
needed
for
my
application
deployment.
It
just
happens
right
and
the
backup
has
to
flow
into
the
same
paradigm
right.
C
There
is
no
central
administrator
and
so
that
we
always
put
the
platform
first
right.
We
want
to
make
sure
that
this
this
functionality
flows
with
the
platform
without
adding
additional
friction
with
the
deployment
for
the
use
and
management.
None
right.
It
looks
like
very
native
to
to
the
platform
that
you
are.
You
are
working
on,
so
that's
been
our
mantra,
our
like
foundational
piece,
our
theme
for
our
company
right.
We
started
that
with
openstack.
C
We
are
the
first
backup
as
a
service,
true
backup
as
a
service
that
is
self-service
multi-tenant
into
the
openstack
cloud
and
then
when,
when
we
are
looking
at
the
cloud
native
the
kubernetes,
we
still
want
to
stick
to
that
same
paradigm,
so
we
could
take
whatever
we
developed
for
openstack,
somehow
retrofit
into
the
kubernetes
world.
But
we
didn't
do
that
because
again,
the
same
thing
right
platform.
First.
So
if
someone
is
using
cube
ctl
to
manage
their
workloads,
provisioning
and
managing
their,
they
should
still
use
the
cube
ctl
to
manage
their
backups.
C
A
Okay,
you
know
you
mentioned
openstack
it
just
I
just
had
flashbacks
I
mean
like.
I
said:
I've
been
here
for
a
little
while
I
remember
when
I
remember
when
openstack
was
the
shiny
object
and
there
was
the
you
know,
they
started
the.
What
was
it
called
the
openstack
summits
and
they
were
all
they
were
up
in
portland.
I
remember
going
up
to
portland
and
the
amount
of
the
amount
of
hype
and
excitement
and
energy
on
those
show
floors
when
you
were
walking
around
there
of
everyone.
A
You
know
this
is
the
next,
the
next
big
thing
for
computing.
This
is
the
next
paradigm
shift
of
you
know,
distributed
computing
and
then
six
years
later,
it
just
seems
it's
kind
of
been
more
niche
into
like
the
telco
type
space
and
and
then
all
of
a
sudden
kubernetes
is
here
and
it's
the
same
thing.
And
now
now
you
go
to
you
know
you
go
to
kubecon.
Well,
I
guess
we
didn't
get
to
go
to
the
one
in
yeah.
A
It
was
just
amsterdam
right,
but
I
mean
it
was
going
to
be
absolutely
ratcheting
up
for
that
one.
So
I
don't
think
we're
going
to
see
kubernetes
going
away
any
time
soon.
I
I
think
I
think
it's
here
to
stay
and,
and
you
know
as
the
key
component
for
orchestration
in
a
in
a
hybrid
world
when
you
said
you
got
your
first
customer.
What
was
it
that
they
said?
Okay,
you
know
we
want
to.
We
want
to
go
with
you
like.
Why
did
they
select
trilio?
A
As
you
know,
it's
hard,
I
mean,
I
remember,
being
at
red
hat
when
we
first
started
here.
I
I
started
in
2001,
I
think,
and
you
know
going
in
there
you
had
to
sell
the
customers
not
on
your
company
or
on
your
product,
but
we
had
to
sell
open
source
and
that
we
weren't
that
we
weren't
wearing
skateboard.
A
We
weren't
have
blue
hair
and
and
skateboards,
and
you
know
we-
we
had
a
lot
of
rep
turnover
back
then,
because
you
know
we
were
trying
to
convince
people
that
open
source
was
a
good
model
as
opposed
to
why
they
should
be
buying
our
product.
So
right,
how
was
it
when
you,
when
you
got
your
first
deal?
What
were
the
challenges
that
you
had
with
them?.
C
There
was
a
three-day
backup
there
and
all
the
vendors
are
presenting
and
we
were
the
last
one
to
go
on
the
third
day
on
the
last
day
to
present
our
solution.
We
don't
have
any
brand
recognition,
nothing
right.
So
we
did,
we
did
go
there
and
we
did
present
as
a
as
a
natively
built
openstack
solution
that
adhered
to
all
the
openstack
principles,
the
scale
and
the
multi-tenancy
and
integration
with
the
keystone
and
everything.
C
No,
no
and-
and
he
basically
turned
to
his
rep
and
said
this
is
exactly
what
I've
been
asking
for
and
all
the
vendors
are
presenting,
how
good
they
are
with
the
virtualization
and
doing
it
for
openstack
is
going
to
be
nothing
right.
They
can
do
it,
but
no
one
presented
the
vision
that
we
have
and
frankly
we
didn't
have
a
ga
product
at
the
time
we
were
at
the
beta,
but
they
are
willing
to
risk
to
take
risk
with
us
saying
that,
because
our
vision
is
aligned
with
what
they
wanted
to
do,.
A
Okay-
and
I
know
that
we
are
going
to
have
a
technical
demonstration-
preshanto
is
going
to
be
putting
that
on
before
we
get
it
in
before
we
got
into
that.
I
did
want
to
just
talk
about
your
your
your
company
and
your
operator
for
a
second.
You
know
we
invest
a
lot
of
time
and
energy
working
with
software
companies
like
yourselves,
you
folks
have
a
red
hat,
certified
container.
A
C
A
Cool
and
if,
if
you're
not
there,
already,
I'm
also
involved
with
the
marketing
for
the
red
hat
marketplace,
operated
by
ibm
if
you're
not
connected
with
them
already
we'd
love
to
have
you
talk
with
them
about
having
your
your
your
backup
solutions
available
in
the
marketplace?
I
don't
know
if
it's
there
yet
or
if
you're.
Having
that
conversation.
B
A
Okay,
great,
so
why
should
cloud
architects,
backup,
admins
and
developers?
Look
at
data
protection?
I
mean
it.
You
know
this
is.
This
is
obviously
a
question
that
we
that
we
have
scripted
here
to
to
get
the
dialogue
going
to
me,
it
sounds
pretty
straightforward
that
of
course,
cloud
architects,
backup,
admins
and
developers
should
be
concerned
about
about
kubernetes.
But
you
know
in
your
own
words,.
C
You
can
do
that
with
the
devops,
so
you
can
create
your
application,
orchestrate
your
application
and
then
spin
as
many
instances
as
you
want
in
any
cloud.
You
want
it,
but
the
challenge
is
the
data.
So
if
you
have
a
data,
heavy
application
that
is
running
on
on
the
kubernetes
and
for
various
operations
reason,
you
want
to
migrate
the
application
to
a
different
club
right,
especially
in
the
multi-cloud
scenario
that
will
happen.
Every
business
should
be
looking
at
how
they
can.
C
They
can
have
this
multi-cloud
strategy
so
that
the
challenge
is
how
you
can
move
this
application
between
the
cloud
transparently,
all
right
so
backup
can
capture
the
application
and
then
record
the
application.
So
we
want
to
elevate
the
discussion
and
make
it
almost
the
must-have
the
functionality
in
a
multi-cloud
scenario.
So
that
way
you
can
backup
the
applications
you
can
recover
the
applications
on
a
different
cloud
for
dr
purposes
for
other
purposes,
you
can
migrate
the
applications
for
cost
savings
right
for
compliance
reasons.
So
you
can.
C
A
And
I
would
like
to
throw
out
there
that
we
are
live
right
now.
So,
if
you're,
like
hello,
facebook,
hello,
youtube,
hello
twitch,
if
you
folks
are
watching
on
any
of
those
live
streams,
if
you
post
any
questions
into
the
chats
over
there,
our
producers
will
pick
them
up
and
we'll
get
them
over
here
and
we'll
be
sure
to
address
any
and
all
questions
that
you
folks
may
have
prashanto
a
little
bit
about
yourself,
you're
the
director
of
product.
A
B
Muni's
being
kind
but
yeah
a
little
bit
about
myself,
I'm
the
director
of
product
for
the
kubernetes
offering
at
trillo.
So
I
deal
with
all
things
kubernetes
in
general,
you
know
looking
at
it
right
from
the
business
angle.
You
know.
Looking
at
the
market
drivers
looking
at,
you
know,
requirement
generation,
you
know
helping
with
go
to
market
strategies.
You
know
engineering,
architectural
discussions,
everything
so
my
focus
is
in
terms
of
building
developing
and
you
know,
selling
the
product
and
that's
what
my
day-to-day
job
entails.
B
Before
this
I
was
at
you
know
at
bigger
corporations,
where
I
was
running
engineering
as
well
as
product
management
teams,
and
you
know
when
I
learned
about
learned
about
trailer
world
for
kubernetes
and
the
venture
that
money
was
getting
into.
I
was
immediately
attracted
to
it
and
definitely
wanted
to
be
part
of
it,
and
you
know
after
a
few
talking
sessions,
I
was
happy
to
be
at
leo
and
you
know
we
are
getting
this
next-gen
technology.
A
Okay,
what
about
some
war
stories?
We
generally
like
to
hear
you
know
some
aha
moments
or
you
know
some
type
of
interesting
war
story
from
you
know.
Deals
lost
deals
won
things
that
that
you
want
to
share
with
with
our
viewers,
then
that
could
be
either
for
yourself
or
or
murali.
I
just
you
happen
to
have
this
have
to
have
the
stage
right
now.
B
I
would
say
from
from
aha
moments:
you
know
when
we
went
down,
you
know
initially
how
we
built
our
product
was
more
in
terms
of
applications
that
were
being
run
within
kubernetes.
So
you
know
people
were
running,
operator-based
application,
heaven-based
applications,
and
you
know
they
were
deploying
applications
based
on
labels
and
so
on.
So
our
focus
was
in
terms
of
protecting
a
helm,
chart,
definitely
an
operator
operator
piece
of
the
application,
as
well
as
the
application
controlled
by
the
operator
and
so
on.
B
And
what
happened
is
you
know
eventually
talking
with
customers?
What
we
realized
is,
you
know
there
is
a
good
population
of
customers
who,
because
of
the
lack
of
you,
know
proper
definition
of
an
application
within
kubernetes.
They
were
using
namespaces
as
the
boundaries
or
as
they
are
definition
or
their
scope
for
an
application.
There
was
a
one-to-one
mapping
between
a
namespace
and
application
so
immediately.
B
We
realized
that-
and
you
know
that
was
one
of
the
biggest
value
ads-
that
we
added
into
the
product
was
a
namespace
level,
backup
and
recovery
feature,
which
is,
you
know,
very,
very
well,
appreciated
by
customers
today,
and
is
you
know,
along
with
the
helm
and
operator
pieces?
You
know
they
end
up
using
the
namesake's
backup
become
the
protocol
and
the
procedure
a
lot
more
as
well.
A
So
helm,
chart
versus
say,
like
a
level
four
operator,
I
know
internally
at
red
hat,
we
have
a
large
technical
team
that
works
with
software.
Vendors
to
you
know
run
their
their
their
their
operator
through
our
test
certification
suite.
So
it's
red
hat,
certified,
I'm
very
familiar
that
that
like
building
helm
chart
is,
is,
is
easy,
but
making
an
operator
is
more
challenging.
Can
you
talk
about
that.
B
B
A
C
So
essentially,
what
it
means
is
your
if
you,
if
your
backup
functionality
is
limiting
you
to
be
mobile
with
your
applications
able
to
basically
move
these
applications
from
one
cloud
to
another,
then
you
should
stay
away
from
that
backup,
backup
application,
a
lot
of
backup
vendors.
They
go
with
very
proprietary
format,
because
this
storage
savings
that
they
basically
created
an
ip
around
it.
They
get
it
only
when
you
save
their
backups
on
their
uplines.
But
you
can't
move
that
appliance
into
the
cloud
right.
So
we
we
always
start
with.
C
So
so
versus
software
only
solution
it
doesn't
rely
on
any
of
any
of
the
proprietary
technologies
and
it
uses
standard
linux
based
standards
and
tools
for
creating
backups,
for
whether
it's
a
space
savings
or
for
all
the
functionality
that
that
people
expect
from
backup
vendors.
But
on
top
of
it
we
are
very
nimble,
so
you
can
take
an
application
that
is
backed
up
from
say
upstream
kubernetes,
and
then
you
are
running
openshift
on
aws.
You
should
be
able
to
recover
your
application
without
losing
anything
from
our
backup
from
our
backups.
C
So
that
is
the
flexibility
that
we
provide
and,
of
course
we
talked
about
the
native
integration,
be
part
of
the
platform
itself,
so
that
also
gives
us
a
lot
more
flexibility,
because
we
can-
and
we
do
discover
all
the
applications
running
in
the
kubernetes
and
and
provide
a
one
snapshot
view
to
the
end
user.
What
applications
are
protected?
C
What
applications
are
not
protected
kind
of
gives
a
risk
profile
for
the
end
user
like
if
there
is
an
exposure
for
the
applications,
because
we
have
a
good
integration
with
the
platform,
so
we
can
do
provide
that
kind
of
analytics
to
the
end
user.
You
can
see
that
in
prashantha's
demo,
when
he
did
when
you
go
to
them.
A
I
I
know
that
you
know
when,
when,
when
this
whole
challenging
time
thing
started,
we
were
like.
Oh
my
gosh
like
I
haven't.
I
haven't
been
on
an
airplane
in
a
year,
not
that
not
that
this
is
necessarily
tied
to
our
business,
but
I
was
wondering
about
you
know
like
our
account
managers,
the
the
lack
of
traveling
on
site
and
what
that
would
do
to
slowing
down
sales,
but
I
think
everyone's
adopted
to
working
virtually
absolutely
these
days,
but
outside
of
just
you
know
these
challenging
times
right.
C
C
A
C
Yeah,
I
think
we
we
focus
on
four
use
cases
with
our
solution
right.
They
look
almost
similar
but,
of
course,
backup
and
recovery.
Right.
If
something
bad
happens,
your
user
should
have
a
way
to
go
and
backup
and
recover,
and
in
a
multi-cloud
environment
our
focus
area
will
be
multi-cloud,
because
that
is
going
to
be
the
standard.
So
when
you
say
multi-cloud,
it
doesn't
have
to
be.
You
know,
between
aws
and
azure
are
vmware
and
azure.
It
could
be
like
multiple
kubernetes
clusters
that
are
running
on-prem.
C
That
can
be
multi-cloud
too,
because
they
are
two
different
platforms
and
you
need
to
have
something
that
tie
all
this
cloud.
All
these
clusters
together
to
provide
that
unified
view
and
then
provide
these
interesting
use
cases,
and
so
application
mobility
and
the
migration
is
under
under
big
use
case
that
we
are
solving,
are
we
we
address
and
the
other
one
is.
The
disaster.
Recovery
desires
recovery
for
the
applications.
If
something
bad
happens
on
the
production
side,
how
quickly
you
can
recover
that
application
onto
the
remote
side,
so
the
dns.
C
A
A
You
know
the
predecessor
to
x86
64.,
and
I
was
on
stage,
and
this
is
the
reason
why
I
asked
preshanto
is
I'm
on
stage
with
this
with
the
fellow
will.
Swope,
I
think,
was
his
name
and
we're
just
about
getting
ready
to
go
to
do
the
demo.
There
was
like
two
big
racks,
and
then
there
was
a
client
that
was
gonna
run
an
app
and
we're
gonna
fail
it
over
between
the
nodes
and
it
had
a
memory
leak
in
it,
and
so
because
I
staged
it
behind
behind
scenes.
A
While,
while
we're
waiting
for
me
to
go
on
the
memory
just
started,
leaking
leaking
leaking
leaking
leaking,
and
so
they
announced
me
on
stage.
I
go
up
there
and
the
client
is
just
like
completely
dead
and
it
was
the
most
embarrassing
demo.
I've
ever
had
to
do
in
my
entire
life
and
after
that,
after
that,
anyway,
this
was
like
big.
It
was
like
linux,
world
right,
it
was
like
15
000
people
in
the
audience
or
something
wow
yeah.
So
after
that,
I
I
can
everything
I
just.
A
Yes-
and
you
see,
this
is
exactly
why
we're
having
these
t-shirts
made
and
we
are
going
to
get
some
shipped
out
to
you.
We
make
no
joke
cyrus
and
I
were
designing
last
night.
We're
gonna
have
we're
gonna
have
1200
made
that
say.
Can
you
see
my
screen
and
1200
made
that
say
you're
on
mute,
we're
gonna,
you
guys
can
be
our
first
recipient
and
you'll
get
one
of
each
and
then
you.
A
Them
during
all
of
your
zoom
meetings-
and
you
can
just
point-
hey
you're
on
me
or
can
you
see
my
screen
and
the
same
thing
goes
for
anyone
who's
watching
us
right
now
on
facebook
or
youtube?
If
anyone
wants
to
get
one
of
these
limited
edition,
can
you
see
my
screen
red
hat
t-shirts?
Send
me
an
email,
it's
just
wait:
redhat
dot
com
and
we'll
hook
you
up
over
to
you.
Prashant,
though.
B
Great,
thank
you
michael.
So
what
we
see
in
front
of
us
right
now
is
the
openshift
console.
This
is
a
openshift
4.6
environment
which
is
running
in
aws,
and
what
I'm
going
to
do
is
I'm
going
to
look
at
the
operator
hub
over
here
operator
hub,
as
we
all
know,
is
like
the
marketplace
for
deploying
applications
into
an
open
shift
environment
well,
search
for
trilio
right
now
we
are
available
in
the
marketplace
and
you
see
a
couple
of
other
tiles.
B
B
B
There
is
a
30-day
free
trial
or
a
10-note
basic
edition
that
we
provide
for
free
and
folks
can
get
jump-started
with
the
technology
very
very
quickly.
So
overall,
this
takes
about
three
clicks.
You
know
you
go
into
the
operator
hub
search
for
tradio
click
on
the
tile
click
on
install,
and
you
know,
within
a
matter
of
five
minutes.
B
Before
taking
a
backup,
we
have
a
crd
known
as
the
backup
plan,
which
is
basically
the
protection
scope
that
a
user
defines
for
what
they
want
to
protect.
It
can
be
just
a
hand
chart
it
can
be
a
help
chart
and
an
operator
based
application.
It
can
be
a
namespace
or
it
can
be
a
combination
of
any
of
those
items.
B
So,
overall,
if
you
see
what
we've
done
is
we've
modularly
built
the
product
based
on
the
operations
and
based
on
the
activities
that
end
users
would
want
to
do
now.
The
value
in
doing
it
this
way
is
the
fact
that,
because
each
of
these
operations
is
a
mobile
location,
you
can
apply.
Kubernetes
are
back
which
we
directly
plug
into
on
each
of
these
items.
For
example,
like,
let's
assume
you
were
the
administrator
and
you
had
control
over
all
the
storage
resources.
B
Now
you
would
not
want
any
of
the
developers
in
the
organizations
to
create
targets,
so
you
can
specifically
make
sure
that
the
target
custom
resource
definition
is
available
only
to
you
for
use,
so
you
can
create
the
targets,
but
all
the
other
folks
within
your
organization
can
leverage
that
target
for
use
for
storing
their
backups
so
and
the
entire
product.
Whether
it's
you
know
hoax
policies,
backup
plan,
backup,
restore
any
of
these
activities
can
be
granularly,
segmented,
based
on
a
user's
role
like
scope,.
B
B
We
have
two
targets
available
over
here
and
similarly
from
a
policy
hooks,
there
are
few
items
that
are
created
everywhere
and
I'll
go
through
it
again,
but
overall,
the
way
a
user
would
want
to
use
these
different
tabs
over
here
is
by
clicking
on
create
target.
They
have
the
option
of
you
know
either
using
a
yaml
view.
B
We
have
the
entire
instructions
on
how
to
use
the
yaml
on
the
right
hand,
side
panel
or
if
they
do
not
want
to
use
the
yaml
view,
they
can
use
a
form
based
approach
which
open
openshift
provides
and
we
directly
plug
into
it.
So
we
have
addressed
and
adhered
to
the
framework
for
these
dynamic
forms
and
because
of
that,
our
entire
yaml
specification
files
are
available
as
a
clip
driven
or
you
know,
a
simple
form
based
approach.
If
users
are
not,
you
know
familiar
with
the
yaml
approach.
B
Now,
as
I
said,
we
have
a
few
targets
created
over
here
from
a
policy
perspective.
We
have
some
policies
created
based
on
retention.
You
don't
have
any
hooks
for
the
backup
plan
and
you
see
there
are
a
bunch
of
different
backup
plans
that
are
running
in
this
environment
associated
with
different
protection
scopes
and
just
to
kind
of
show
you
how
that
works.
We
just
call
this
openshift
tv,
backup
namespace.
B
So
once
you
provide
all
this
information,
you
go
ahead
and
click
create.
This
will
go
ahead
and
start
creating
the
backup
plan,
and
once
it
validates,
the
controllers
will
validate
that
whatever
I've
asked
for
it
to
backup
is
actually
correct
and
we'll
put
it
into
an
available
state
beyond
that,
a
user
would
come
into
the
backup
menu
they
create
backup.
B
B
So
what
happens
is
once
we
trigger
this
backup,
which
is
right
here,
openshift
tv
backup
it
will
go
through
the
trillion
process
of
you
know,
snapping
the
metadata
object,
so
all
the
manifest
files
that
comprise
of
the
application
we
protect
that
first
and
then
we
get
into
the
data
components
of
capturing
the
persistent
volumes
and
so
on.
So
it's
a
pretty
much
sequential
step,
step-by-step
process,
which
you
take
for
this
this
operation.
B
A
A
B
A
This
work
with
any
flavor
of
kubernetes.
Like
do
you
see,
you
see
people
using
community
supported
kubernetes
inside
their
environments
and
they're,
asking
you
to
to
back
up
and
given
the
the
fast
change
rate
in
kubernetes
development
by
yourself,
how
does
your
product
keep
up
with
all
the
changes
that
are
that
are
coming
along.
B
So
that's
how
we've
constructed
the
product
making
it
you
know
very
seamless
for
any
kubernetes
environment
to
deploy
and
use
this
and
then
because
we
are,
you
know,
leveraging
kubernetes
constructs.
You
know
we
are
leveraging
all
the
abstractions
that
kubernetes
provides,
maintenance
and
upkeep
becomes
pretty
easy
for
us,
because
you
know
we
are
using.
Firstly,
one
of
the
one
but
more
of
the
basic
level
components
that
kubernetes
offers,
so
those
components
do
not
change
as
much
or
rarely
change,
and
then
that
is
backwards,
compatibility
provided
through
the
kubernetes
system
and
itself.
B
That
makes
the
churn
on
our
end
very
minimal.
So
from
that
angle
you
know
all
the
abstractions
to
hook
into
the
kubernetes
system,
the
you
know
compatibility
the
all
these
different
pieces
help
us
in
you
know
pushing
out
code
really
really
fast.
So
one
of
the
things
that
we've
been
doing
on
average
is
we've
been
doing
new
releases.
B
You
know
with
cutting-edge
features
almost
about
every
couple
of
months,
and
you
know
we've
seen
things
or
have
done
things
in
the
past.
You
know
not
coconutty
centric
and
I've
seen
how
long
driven
and
you
know
how
long
those
cycles
can
be,
but
kubernetes
and
all
these
different,
newer
technologies
are
changing
the
way
we
do
things,
and
we
are
you
know.
While
we
are
building
a
product
for
kubernetes,
we
ourselves
are
realizing
the
benefits
that
it
provides
internally
for
us.
A
Okay
and
what
about
what
about
workloads
are
there?
Are
there
some
apps
that
trulio
vault
works
better
with
because
of
the
way
they're
architected
or
or
what
it?
What?
If
someone,
what,
if
someone's
using
an
app
that's,
not
cloud
native
and
they
they
sort
of,
did
a
forklift
you
know
jam
into
the
cloud
is:
does
that
pose
any
problems
or
does
your?
Does
your
backup
solution,
work
best
or
work
only
for
an
app
that's
cloud
native.
B
Obviously,
if
you
have
a
you
know
like
a
more
of
a
traditional
vm
based
solution,
then
we
have
our
other
products
around
web
and
openstack
as
well.
That
can
support
that,
but
each
product
is
specific
for
those
domains,
and
you
know
future
consolidation
is
something
that
we
have
thought
of,
but
it's
kind
of
down
the
road.
B
A
A
What's
the
magic,
how
does
it?
How
does
it
work
in?
In
plain
people
speak?
Maybe
for
doing
you
know
backup
or
data
management.
When
you
have
these
nodes
that
are
distributed,
you
know
and
like
say
you
take
an
open
shift
cluster
that
runs
on
public
cloud
and
private
cloud
and
on-premise,
and
you
know,
is
there
any
special
sauce
or
magic
that
would
that
is
required
to
have
trilio
vault,
be
able
to
address
the
the
data
management
needs
in
such
a
distributed
model?.
B
Exactly
so
the
the
secret
sauce
or
the
way
we
do
it
is
through
hooks.
You
know
we
can
basically
inject
commands
before
a
backup
happens,
and
you
know,
after
a
backup
happens
directly
within
the
container
itself.
So
if
there
is
any
kind
of
management
activities
or
pre-work
that
is
required
for
us
to
perform
the
backup
or
for
the
application
to
get
a
consistent
backup,
we
end
up
doing
those
through
hooks
and
what
we've
also
done
is,
if
I
take
you
to
our
so.
C
C
C
So
you
know
you
need
to
have
a
backup
policy
that
operates
at
that
abstraction
that
the
developer
intended
to
like
if
they
are
rolling
out
a
helm-based
release,
the
backup
need
to
run
at
that
level.
Not
nodes
are
not
pvs
are
not
containers
level
are
the
operators.
So
I
think
we
are
the
only
backup
solution
out
there
that
can
operate
at
that
operator.
C
Our
helm
level,
where
we
are
to
discover
all
the
components
of
that
application,
including
the
pvs
and
the
containers
and
secrets
and
the
config,
and
we
can
we
can
backup
the
application
as
they
are
laid
out
as
it
is
laid
out
and
and
also
if
the
application
has
basically
grown
into
more
number
of
pvs.
We
automatically
discover
that,
and
the
next
backup
will
include
all
those
things
we
preserve
that
application
nature,
and
these
are
the
hooks
essentially
provide
the
application.
Consistent
backups
for
you.
B
But
what
I
wanted
to
show
you
was,
you
know
we
have,
you
know,
tested
validated
and
we
do
support.
You
know
multiple
applications
that
have
this
distributed:
nature
like
cassandra
and
so
on.
We
provide
the
backup
plans
and
the
hooks
that
we've
tested
with
you
know,
as
our
hooks
kind
of
show
your
what
is
the
hook
you
want
to
execute,
which
is
the
port
that
you
want
to
execute
it
against.
Is
there
any
kind
of
specific
container
you
want
to
run
this
within?
A
So
you
in
in
your
hooks
there,
you
specifically
have
hooks
for
cassandra
hooks
for
hooks
mariah
db.
Do
those
come
already
or
do
those
have
to
be
pre-configured
or
you
know,
do
they
have
to
be
created
by
the
end
users
when
they
first
get
this
going,
and
the
reason
why
I
ask
is
I'm
more
concerned
about
transactional
databases
like
sql
in
nature
like
like
a
like
a
yoga,
byte
or
fauna
db?
B
B
A
B
Second,
part
of
your
question
was
around.
I
believe
you
were
talking
about
these
examples
itself
right
and
yeah.
So
so,
as
I
said
right,
these
are
different
application
based
hooks
that
we
are
providing,
they
are
constantly
being
updated.
You
know
we
test
them
out
internally,
they
are
provided
as
a
you
know,
template
for
everyone
to
use
and
we'll
continue
building
these
over
and
over
again
and
whatever
the
new
applications
that
we
see
the
amount
from
customers
they
will
be
added
here.
A
I
talked
with
the
the
reason
why
I'm
bringing
this
up
is
because
I
talk
with
customers
all
the
time,
and
this
morning
I
was
I
was
on
with
our
entire
financial
services
sales
leadership,
team
and,
and
they
identified
one
of
their
key
workloads
as
being
these
transactional
sql
databases
for
db2
and
oracle
offload.
So
you
might
want
to
take
a
look
at
throwing
putting
adding
some
support
in
there
for
those
right
out
of
the
box.
A
A
C
This
is
just
the
beginning:
either
there
is
so
much
that
we
need
to
do
here
right.
You
know
you
can
see.
The
kubernetes
is
going
to
be
the
pretty
much
standard
in
a
cloud
environment
as
a
platform
of
choice
and
people
are
also
calling
it
a
platform
of
platforms.
Right
now
you
can
say
red
hat
is
bringing
the
virtualization
technology
to
the
kubernetes
with
the
keyboard,
and
we
want
to
extend
our
support
to
cuba.
C
In
the
park,
anything
anything
that's
happening
in
the
public
cloud
right
so
that
we,
the
the
this
this
is.
This
is
a
big
play.
Kubernetes
is
enormous
and
we
want
to
be
there
in
every
every
part
of
it,
and
also
you
know
that's
on
the
platform
side,
but
also
the
features
we
need
to
keep
up
with
the
features
and
be
ransomware
is
one
of
the
biggest
threat
and
we
strongly
believe
the
backup
play
a
vital
role
in
in
protecting
against
ransomware
threats.
C
So
we
are
closely
looking
at
some
of
the
standards
like
nist
cyber
security
framework
and
how
we
can
be
part
of
part
of
in
part
of
that,
that
bigger
picture
and
looking
at
the
additional
use
case
in
the
multi-cloud
environments
and
then
also
public
cloud.
So
now
we
eagle
hasn't
landed,
he
hasn't.
So
I
think
we
are
so
excited
about
what
what
the
future
holds
for
us
for
this
year
and
next
year.
A
Okay,
anything
that
you
know
when
we're
done
here
and
you
get
that
call
from
justin
who's,
your
vp
of
you
know,
biz,
dev
and
and
marketing,
and-
and
you
know
what
what,
how
do
we
stop
that
call
from
him
that
says
raleigh.
I
can't
believe
you
didn't
talk
about
this.
One
thing
it's
this.
We
talked
about
this
like
what
would
that
be.
C
C
Yeah
management
console
we
have
management
console.
We
have
a
lot
of
good
partnerships
going
on
with
with
things
with,
with
a
lot
of
backup,
vendors
and
other
other
people.
Like
you
know,
we
recently
challenged
the
partnership
with
veritas,
which
is
big
for
us.
It's
validates
our
vision
in
the
cloud
marketplace.
A
A
They
have
demos,
they
have
labs
and
certainly,
if
anyone
needs
to
get
in
con
in
contact
with
him,
you
can
see
prashanto's
contact
information
on
the
bottom
left
or
you
could
always
send
me
an
email.
I
I
know
these
folks
really
well
and
frankly,
I
know
just
about
every
software
company
fairly
well,
so
it's
just
wait
at
redhats.com.