►
From YouTube: OpenShift Commons Briefing #70: Cloud-Based Virtualization, Containers, and Microservices
Description
Unravelling the Mysteries of Cloud-Based Virtualization, Containers, and Microservices
Guest Speaker: John H Terpstra, Dell EMC
Nearly everyone has heard about Containers within a Cloud-based information services platform environment. Few can provide a succinct comparative features and benefits of the development environments and the deployment model and few can provide a succinct overview. Brevity is important when describing next-generation software architectures, particularly when the person who needs to hear and understand can unlock a budget necessary for platform acquisition. There is no substitute for a good elevator pitch when asking management to invest in the future. We will review and discuss the key features and benefits of bare metal deployment, use of virtualization, containers, microservices, and unikernels.
A
A
Well,
hello
and
welcome
again
to
another
openshift
Commons
briefing,
refresh
off
the
open
check,
Commons
gathering
in
Berlin,
where
I
had
the
great
pleasure
finally
meeting
John
Terpstra
today's
speaker
insertion
and
we
are
going
to
be
kind
of
renamed.
This
topic
from
unraveling
keep
wrapping
cloud
native
surfaces
and
I'm
going
to
let
John
introduce
themselves
and
talk.
This
is
a
higher
level
conversation
than
the
usual,
but
I
think
you'll
really
find
it
interesting
to
get
the
deli
MC
perspective
on
the
cloud
and
cloud
native
services.
So
I'm
going
to.
A
B
We
have
a
couple
of
teams,
one
that
works
on
the
Hadoop,
big
data
and
analytics
area
and
the
other
their
works
on
the
open-source
OpenStack
platform,
environment
and
I'm
part
of
that
team.
I
manage
the
Quality
Assurance
team
and
I
have
a
software
engineering
group
who
work
on
all
of
the
OpenStack
add-ons
to
they
open
source
add-ons
to
the
OpenStack
platform
and
the
OpenStack
platform
that
we
do
most
of
our
work
on,
of
course,
is
the
Red
Hat
OpenStack
platform
and
we
layer
open
shift
on
top
of
the
Red
Hat
OpenStack
platform.
B
Now
my
objective
today
is
to
talk
about
the
importance
of
getting
the
right
message
across
to
management
whenever
you
are
doing
work
on
openshift,
and
you
want
to
get
a
commitment
to
your
open
shift
and
containerization
initiatives.
There's
a
lot
of
confusion
in
the
enterprise
space
regarding
what
this
containers
are
or
what
containers
are
all
about.
What
virtual
machines
are
all
about?
B
How
we
already
doing
enough-
what's
it
all
mean
so
getting
the
message
across
of
what
it
is
that
we
are
really
trying
to
do,
is
crucial,
so
I
want
to
just
cover
some
ground
work
there.
An
elevator
opportunity
is
a
an
unexpected,
unplanned
engagement
or
contact
that
you
have
with
someone
who
is
in
a
position.
B
That's
rather
important
to
you
like
someone,
invite
approve
a
budget
or
someone
who
might
approve
a
purchase,
and
we,
as
professionals
in
the
IT
industry,
really
need
to
be
ready
for
those
for
those
moments,
so
that
the
exciting
projects
that
we
are
working
on,
like
the
deployment
of
openshift
containerized
services,
that
we
are
ready
to
present
a
really
sink
case,
and
that
case
should
be
a
case
for
digital
transformation,
because
digital
transformation
is
important
to
the
future
of
the
business.
We
need
to
be
able
to
garner
interest
in
that
very
brief
encounter.
B
Typically,
these
encounters
last
fall
between
10
and
30
seconds.
So
we
need
to
be
careful
with
how
we
use
that
time,
and
our
objective
should
be
to
seek
commitment
to
the
key
things
that
we
are
trying
to
do
for
the
business.
We
are
there,
as
IT
professionals,
to
help
drive
the
business
forward
so
to
set
the
change
for
digital
trends
and
changes
that
the
company
is
going
through.
We
have
an
opportunity
to
point
out
that
technology
is
key
in
its
impact
on
the
business
because
of
the
emergence
of
the
cloud.
B
The
emergence
of
the
Internet
of
Things
and,
in
particular,
the
necessity
for
analytics
as
a
key
driver
of
the
business
that
analytics
framework
is
a
framework
that
we
are
help
helping
to
implement
and
helping
to
deliver.
Digital
transformation
is
necessary
to
take
monolithic
legacy,
traditional
type
applications
and
drive
them
forward
and
we'll
cover.
Why,
in
this
brief
discussion
and
innovation,
is
disrupting
the
way
that
we
used
to
do
things
additionally,
confuse
consumers
are
increasingly
using
social
media.
B
Social
media
and
social
connectivity
is
shortening
the
decision
cycles
and
spreading
the
news
a
lot
faster
of
the
opportunities
that
are
available,
the
things
that
people
are
interested
in.
So
what
that
means
is
that,
from
the
moment
we
find
out
about
something
to
the
moment
we
buy,
it
is
being
that
time
frame
is
being
shortened.
B
Additionally,
there
are
changes
taking
place
in
the
employment
market
place
with
more
people
working
from
home
and
a
much
greater
awareness
of
the
necessity
to
establish
an
appropriate
work/life
balance,
and
on
top
of
that,
we
are
seeing
a
tremendous
agility
in
the
workplace
and
therefore
we
need
to
understand
what
some
of
the
key
software
application
engineering
challenges
are.
Something
happened
between
2005
and
2010
in
that
the
web
and
Internet
technology
and
the
principles
associated
with
them
have
collided
with
the
enterprise
technology
that
was
before
us.
B
Memory
storage
are
all
faster
and
cheaper
software
is
getting
cheaper
and
more
disposable
and
more
applications
of
being
divided
used
and
developed
than
ever
before.
The
cloud
gives
us
the
opportunity
for
dynamic
scale-out,
topped
where,
as
a
service
and
all
of
its
variations
are
here,
and
this
directly
impacts
the
development
and
deployment
cycle
with
far
more
choices
in
technology
and
far
more
architectural
choices
that
need
to
be
made
doing
software,
that
is
software.
The
old
way
with
monolithic
applications
is
simply
unsustainable.
B
Large
monolithic
systems
have
a
lot
of
long
development
cycle
along
planning
cycle,
long
development
cycle
massive
queue,
a
requirement,
a
lot
of
feedback,
a
lot
of
people
involved
in
the
chain.
It
just
costs
too
much,
and
it
takes
too
long
and
with
today's
dynamic
demand
cycles,
often
the
software
development
cycle
for
the
monolithic
technologies
is
so
long
that
will
just
simply
miss
the
opportunity
in
the
marketplace,
and
what
we
want
to
do
is
to
help
our
businesses
to
capture
short
waveform
demand
cycles
that
can
help
propel
our
business
forward.
B
So,
therefore,
we
need
to
change
the
way
we
do.
Software
development
and
software
design
and
implementation
and
deployment
to
the
development
process
is
changing
the
silos
of
disappearing,
we're
rebalancing
the
whole
development
and
deployment
ecosystem,
making
use
of
cloud
technologies,
making
use
of
containerization
as
a
development
and
deployment
paradigm.
In
order
to
get
stuff
out
there
fast,
because
the
faster
we
can
get
the
applications
out
there,
the
faster
we
can,
our
car
companies
that
are
investing
in
this
technology,
or
at
least
we
hope
they
will.
It
can
start
again
at
gather
return
on
that
investment.
B
B
Additionally,
the
hardware
life
site
utility
life
cycles
are
shrinking
and
therefore
we
need
to
to
get
Hardware
deployed
quickly.
We
need
to
get
our
software
deployed
quickly
so
that
we
can
get
the
return
on
that
Hardware
investment.
So
the
key
to
balancing
out
the
the
demand
to
opportunity
spectrum
is
through
micro
service
design,
which
focuses
on
replaceable
components
where
any
component
can
be
replaced
at
any
time,
and
we
need
very
quick
releases.
So
speed
is
the
essence.
We
need
to
cut
costs
and
be
much
faster
at
getting
our
applications
out.
B
So
what
I
want
to
do
is
just
focus
for
a
few
moments
on
the
different
types
of
deployment
mechanisms.
The
traditional
compute
technology
that
came
out
of
the
1950s
and
1960s
used
bare
metal
deployment
and
that
bare
metal
was
in
big
iron
technologies.
But
in
with
the
1980s
we
saw
the
emergence
of
personal
computers,
which
made
it
far
more
cost
efficient
and
cost-effective
to
deploy
applications
on
cheaper
systems.
But
even
then
we
had
we
ran
into
barriers.
B
Do
we
saw
in
the
1990s
to
2000s
the
deployment
of
virtualization
technologies
and
now,
in
the
last
few
years,
were
seen
containerization?
So
how
do
these
different
methods
of
deployment
impact
the
way
that
our
software
works?
Well?
For
starters,
our
CPU
and
memory
usage
will
on
bare
metal
deployment,
was
limited
by
what
the
workload
could
consume
with
Virtual
Machine
deployment.
We
could
get
far
better
utilization
of
processor
and
memory
capabilities
by
simply
launching
more
machines
or
virtual
machines
on
the
only
the
same
system.
B
Well,
today,
we
can
get
even
better
utilization
through
the
use
of
containers,
because
containers
do
not
have
the
same
resource
overheads,
that
virtual
machines
have
and
there's
another
method,
and
that's
what
we're
doing
with
openshift
on
OpenStack.
That's
deploying
containers
on
virtual
machines,
which
allows
us
to
balance
out
some
of
the
some
of
the
other
factors
that
we
want
to
look
after.
But
on
top
of
that,
let's
look
at
execution.
Overhead
bare
metal
has
no
execution
here.
B
Overhead
virtual
machines
can
have
a
significant
execution
overhead
because
of
all
of
the
other
infrastructure,
that's
necessary
to
support
the
virtual
machines.
Containers
are
more
efficient.
They
have
a
far
lower
overhead.
However,
when
we
start
to
deploy
containers
on
virtual
machines,
we
have
to
be
cognizant
of
the
fact
that
the
virtual
machine
overhead
persists.
B
B
The
same
happens
if
that
bare
metal
machine
happens
to
be
carrying
a
whole
lot
of
virtual
machines,
all
its
virtual
machines
disappear,
but
if
just
a
virtual
machine
goes
down,
then
one
of
the
workloads
that's
running
on
the
system
is
impacted.
Likewise
with
containers
on
bare
metal.
However,
when
we
lose
a
virtual
machine,
that's
running
a
whole
bunch
of
pods,
then
we
lose
the
whole
shebang
again.
We
need
to
be
cognizant
of
what
our
risk
of
unit
outage
is
from
an
I/o
perspective.
Bare
metal,
of
course,
is
limited
by
whatever
the
devices
are.
B
However,
the
total
input
output
bandwidth
of
the
machines
are
shared
across
the
virtual
machine
are
shared
by
the
virtual
machines
with
containers
we
allocate
the
resource,
the
pods,
that
we
are
running
on
the
system
and
so
forth
from
computer
patients.
If
they're
considerations
bare
metal
of
course,
has
the
highest
computer
fishin
see
if
the
workload
can
consume
the
total
resource
and
compute
resource.
That's
on
the
system.
B
Virtual
machines,
however,
limit
the
amount
of
computer
fishin
see
that
can
be
consumed
by
a
virtual
machine
to
the
Numa
architecture
and
the
number
of
cores
that
are
allocated
to
that
virtual
machine
and
in
the
case
of
containers
where
we
tend
to
be
thread
limited
from
security
risk.
Those
are
things
that
you
want
to
consider
as
well
in
deploying
applications.
B
You
want
to
make
sure
that
your
applications
are
in
fact
secure,
and
there
are
differences
in
the
security
risk
depending
upon
which
mode
of
deployment
is
used
and,
of
course,
you
can
see
the
tendency
and
quality
of
service
comparison
there
as
well,
comparing
their
mettle
with
virtualization.
There
are
obvious
benefits
in
virtualization
capital
costs,
get
distributed
across
multiple
or
get
consumed
by
multiple
workloads.
B
So
there
is
a
greater
efficiency
in
the
use
of
the
hardware,
also
virtualization
minimizes
downtime,
because
virtual
machines
can
be
moved
hosts
across
hosts
without
loss
of
currency
of
service
and
virtual
machines
also
increase
productivity,
efficiency,
agility
and
responsiveness.
Virtual
machines
have
fasted
to
provision
than
a
bare
metal
machine
and
therefore
they've
also
provide
better
business
continuity.
B
There
are
disadvantages
to
virtualization.
One
of
the
most
common
ones
listed,
of
course,
is
the
cost
of
the
hypervisor
or
the
hypervisor
tax.
There
are
performance
limits,
as
we
saw
in
the
previous
slide
and,
of
course,
the
infrastructure
for
virtualization
tends
to
be
more
costly
because
poor
virtualization
support,
we
tend
to
invest
far
more
in
the
micro,
processor
and
memory
so
that
we
have
more
resource
to
share
with
virtual
machines.
B
You're
all
aware
of
the
fact
that
virtual
machines
and
containers
are
simply
different
ways
of
sharing
the
underlying
infrastructure
of
the
system.
Now,
on
the
left,
we
see
a
full
virtualization
system
where
a
hypervisor
is
the
bare
metal
operating
system
and
then
guest
machines
and
guest
applications
are
installed
on
that
hypervisor.
B
So
containers
versus
virtual
machines
have
benefits,
contain
a
spin
up
very
much
more
rapidly.
I'll
show
you
some
statistics
on
that.
In
just
a
few
moments,
manic
containers
maintain
service
integrity
of
the
application.
That's
a
decided
advantage
and
container
footprints
storage
will
Prince
tend
to
be
much
smaller
than
virtual
machine.
Footprints
containers
tend
to
be
immutable
due
to
the
layered
or
the
layering,
and
only
the
upper
layer
is
able
to
be
changed,
but
then
again
we
don't
want
to
change
containers.
We
want
to
build
containerized
services
as
disposable
services.
B
B
Now
so
far
as
launch
time
is
concerned,
and
it's
always
important
to
compare
launch
time
on
the
actual
hardware
that
you'll
be
using
the
actual
infrastructure
that
you'll
be
using.
But
our
virtual
machines
can
take
30
to
50
seconds
to
deploy
and
take
time
to
stop
launching
VMs
on
OpenStack,
because
the
dynamic
nature
and
the
increased
number
of
machines
that
are
being
managed
from
a
central
source
can
take
a
little
longer
to
to
kick
off.
B
Containers
eliminate
the
OS
duplication
of
the
virtual
machine,
they
require
less
memory
to
operate
and
fewer
CPU
cycles
and
typically
allow
us
to
deploy
two
to
three
times
more
applications
on
a
single
system.
So
there
are
significant
resource
utilization
benefits
to
containerisation.
They
provide
a
consistent
portable
development
environment
because
you
can
even
build
your
development
environment
on
the
laptop
and
then
later
migrated
the
containerized
environment
to
your
corporate
test,
dev
and
deployment
environment
they
because
of
the
fastest
startup
and
shutdown
their
more
orchestration
friendly,
and
also
contain
this.
B
To
provide
separation
of
namespaces
for
processes,
network
storage,
mounts
post,
IDs
memory
and
everything
else.
On
the
other
hand,
containers
have
their
own
liabilities.
Any
intrusion
upon
the
host
OS
that
is
hosting
containers
generous,
potentially
result
in
the
whole
shebang
being
brought
down.
There's
also
a
risk
of
Trojan
horses
with
many
public
containers
being
published
in
an
uncontrolled
environment.
And,
of
course,
the
last
one
to
watch
out
for
is
that
excessive
container
packing
is
a
builds
containers
that
function
more
like
virtual
machines.
B
So
we
have
a
digital
transformation
opportunity
in
that
71
percent
of
customers
agree
that
if
they
do
not
embrace
IT
transformation,
their
business
or
organization
will
no
longer
be
competitive
in
the
marketplace
that
they
serve
business.
The
business
agenda
today
is
technology
because
technology
provides
competitive
advantage
and
the
business
provides.
It
should
provide
an
incremental
IT
budget
to
sustain
that
competitive
advantage.
Software
DNA
is
critical
to
the
future
of
the
business.
There
are
four
hours
in
the
dynamics
of
change,
retire,
retain
repurpose
and
re-engineer.
B
And
lastly,
we
need
to
pay
down
technical
debt
by
repurposing
applications
that
we
have,
but
the
best
opportunity
we
have
of
all
is
to
re-engineer
from
the
ground
up
and
to
treat
the
IT
infrastructure
that
we
are
leveraging
as
the
platform
for
a
digital
production
house
native
code,
microservices
or
cloud
native
microservices
enable
more
flexible,
higher
performing
agile
code
at
a
cost
of
some
increase
in
complex
and
complexity.
That
complexity
can
be
squashed
by
automation.
However,
an
intelligent
transformation
is
necessary.
We
need
to
recognize
that
money.
B
B
Openshift
allows
us
to
create
faster
debited
deployment
cycles,
which
we
should
use
the
competitive
advantage.
New
applications
and
smart
devices
are
transforming
the
business
agile
development
with
continuous
delivery
accelerates.
Our
leverage
to
market
and
data
analytics
provides
the
wherewithal
to
provide
new
insights
to
the
areas
where
we
might
improve
and
how
we
might
in
fact
get
better
traction
of
our
applications
in
the
marketplace.
A
Maybe
it's
from
your
speakers
that
I'm
not
sure
this
was
I'm
going
to
make
you
do
a
keynote
at
one
of
the
upcoming
galleries,
because
this
is
a
wonderful
way,
thats,
a
really
intro
the
whole
aspects
of
digital
transformation
and
some
of
the
benefits
I
actually
really
appreciated.
It
seemed
so
much
talk
around
the
bare
metal
deployments
as
well,
because
I
think
that's
one
thing
that
I'm
actually
sitting
besides
people
deploying
locally
and
using
open
shift
on
the
mini,
should
I
put
them
in
the
chat.
A
The
links
for
many
ships,
which
is
our
fourth
of
mini
cube
for
deploying
openshift
locally,
but
we're
also
seeing
and
manisha
shared
the
links
to
deploying
open
ships
on
bare
metal,
well,
I
think
that's
actually
something
that
people
are
coming
around
to.
It
means
a
lot
of
people
to
deploy
an
AWS
on
their
own
in
the
house.
Hardware.
That's
that
OpenStack
on
it,
but
I
think
they've
been
an
uptick
in
people
wanting
that
the
efficiencies
of
fair
metals
and
from
starting
goes
to
use
it
a
lot
more.
You
think
that
as
well.
B
We
are
getting
requests
for
reb
and
mental
containerization
right
now.
Most
of
the
requests
we
are
seeing
is:
can
you
get?
Can
you
Amish
with
more
information?
Can
you
tell
us
what
this
is
all
about?
That's
the
thin
edge
of
the
wedge.
Isn't
it
that's
just
the
right
that
the
beginnings
of
an
exciting
time
ahead
well,.
A
I
think
that
the
interesting
thing
is
those
of
us
who
are
like
deep
in
the
throngs
of
the
technology
often
forget
that
there's
a
lot
of
people
out
there
who
are
just
coming
loose
or
containers
who
and
you
have
adopted
vm
and
they're
using
them
widely,
but
they
don't.
They
still
need
to
get
the
intro
bit
and
the
high
level
understanding
of
what
the
benefits
are.
And
meanwhile
we're
trying
to
drive
Service
Catalog
cigs
in
coover
Nettie's
and
you
know
all
kinds
of
new
features
and
they're.
A
Just
like
whoa
whoa
whoa
whoa
wait
a
minute
we
need
to.
We
need
that
be
able
to
figure
out,
like
you
said,
the
elevator
pitch
just
to
get
this
stuff
in
internalized
and
socialize
inside
of
enterprises
and
I.
Think
we've
done
a
very
nice
job
of
that.
So
I
look
forward
to
they're
doing
this
again
and
maybe
they
manisha
to
do
a
future
demonstration
of
some
of
the
work
that
you
guys
have
been
doing
inside
of
Dell
in
the
past.
A
Maitland
done
a
great
job,
creating
the
reference
architecture
or
open
shift
on
a
loom
back
90
days
that
there's
a
set
of
internal
document
somewhere
at
dale's,
built
with
all
the
details
of
doing
that.
So
is
already,
then
some
great
work
done
and
I'm
looking
forward
to
doing
a
lot
more.
So
a
bunch
of
folks
who
are
in
the
chat
I'm,
not
seeing
too
many
questions
here.
I
think
you
see
that
a
nice
level,
then,
if
there's
anyone,
has
a
question
just
pop
it
into
chat.
A
I'm
not
seeing
any
questions,
I
think
you've
done
a
very
great
job,
giving
people
the
basis
of
creating
their
own
elevator
pitches
for
the
coming
cloud
native
and
then
it's
nice
to
see
the
retire,
recycle
the
hold
us
the
tie,
bars
or
consider
for
five
hours.
You
had.
We
often
inside
of
open
shift
talk
about
three
patterns
with
some
shifts
augment
the
reality,
and
this
is
not
forget.
The
third
one
was,
but
there
was
one
other
just
totally
right.
It's
always
nice
to
hair
how
Delhi
MC
is
messaging
out.
A
The
same
sort
of
digital
transformation
called
action
again
thanks
everybody
for
joining
us
today,
and
we
hope
you
can
see
you
at
the
upcoming
open
ship,
Commons
gathering
again
in
person.
I
know
john
will
be
fair.
That's
me!
First
and
the
day
before
open
house
in
sales
and
ships
coming
now,
it's
red
hat
linux.
There
will
be
a
lot
of
open
shift
on
the
menu
at
that
one
which
is
in
boston
coming
at
the
gathering
is
on
may
first
and
read.
That
summit
is
the
second
third
and
fourth
of
may
so.