►
From YouTube: Containers and OpenShift with Cisco Infrastructure
Description
Using containers or starting to use them for your applications? Facing challenges in designing and deploying scalable and reliable solutions? Have a mix of legacy and cloud native applications? Come attend the session to learn how Cisco and Red Hat have partnered to offer validated solutions by leveraging best of breed technologies. Learn about joint solutions using Cisco UCS, Cisco ACI and Red Hat OpenShift.
A
Thanks
guys,
thanks
for
joining
play,
I'm
visually
Jakob,
part
of
Cisco
part
of
the
Cisco
UCS
solutions
team
today,
I'll
be
talking
about
the
giant
effort
that
we
have
put
together
working
between
Cisco,
rIDOT
and
Intel,
to
offer
a
set
of
solutions
for
our
customers
to
use
for
deployment
of
containers
using
openshift.
So
here
I'm
going
to
talk
about
how
we
can
help
you
help
our
customers
deploy
applications,
develop
applications
in
an
accelerated
manner,
so
before
I
mean
before
I
start.
Let
me
let
me
talk
a
little
bit
about
how
the
industry
is
progressing.
A
What
is
it
digital
transformation?
Our
customers
are
looking
at.
So
as
you
see
here,
so
this
lights
are
a
little
bit.
Format
is
little
bit.
Ok,
so
here
the
three
access
that
you
can
look
at
how
digital
transformation
is
happening
across
the
data
center
for
the
businesses,
both
on-premise,
as
well
as
on
the
cloud,
even
customers
having
a
hybrid
cloud
deployment.
So
if
you
go
back
a
few
years,
it
was
all
about
bare
metal.
It
was
on
prime.
It
was
managed
by
centralized
IT
team.
A
Now,
as
things
progressed,
things
have
evolved
into
virtual
machines
and
now
containers
on
the
deployment
side,
be
it's
a
choice
between
on-premise
public
cloud,
my
big
cloud
as
well
and
in
terms
of
management.
It's
all
about
the
IT
teams,
the
line
of
businesses
as
well
as
the
SV
piece
and
the
DevOps
teams.
They
are
defining
how
things
are
consumed,
developed
and
deployed,
and
containers
and
micro
services
play
a
big
role
in
what
how
these
things
are
happening.
So
with
that,
let
me
talk
about
a
little
bit
about
what
is
the
industry
trend
right?
A
Ok,
so
in
terms
of
how
the
adoption
is
increasing,
as
you
can
see
your
based
on
some
of
the
reports
by
Gartner
and
IDC,
there's
a
huge
amount
of
growth
over
the
next
3
years
in
terms
of
container
adoption,
interrupt
number
of
instances
of
containers
that
will
be
utilize
for
deploying
the
web-scale
and
McClure's
applications,
and
there
is
in
terms
of
customer
base,
most
of
the
enterprises
here.
I
say
60%.
However,
since
this
survey
was
done
now,
the
number
has
even
grown
bigger.
A
A
However,
kubernetes
has
taken
the
lead
and
it's
a
leading
Orchestrator
that
is
being
used
and
offered
by
multiple
vendors,
including
the
diet,
openshift,
so
openshift
uses
cooperatives
as
part
of
the
core
platform
and
containers
are
used
in
multiple
areas
for
your
cloud
annuity
applications
for
your
DevOps
deployments,
as
well
as
for
your
platform
as
a
service
deployment.
So
with
that,
however,
all
this
is
good.
However,
it's
not
easy
for
a
regular
customer
right,
it's
all
cool
and
good.
However,
it
takes
a
lot
of
effort
lot
of
engineering
skills
required
to
deploy
and
manage.
A
So
that
is
this,
as
you
can
see
here,
it's
container
management
monitoring,
persistent
storage
on
the
technology
side,
but
also
on
the
deployment
side.
It's
the
complexity
of
deploying
it.
It
is
a
complexity
of
the
management
of
it
and
trying
to
fit
everything
together
and
then
the
level
of
resources
required
to
make
things
happen.
So
this
is
the
challenge
as
well
as
the
excitement
that
but
containers
and
microsoft
says,
brings
to
the
table.
Customers
want
to
do
that,
but
they
are
hesitant
to
make
it
happen
because
of
the
challenges
that
that
are
out
there.
A
So
our
main
goal
here
is
to
take
the
best
out
of
the
audible
options
and
provide
the
best
suitable
options
for
our
customers,
so
form
a
whole
stack
perspective.
We
have
the
OpenStack
container
platform
and
we
have
using
kubernetes
Orchestrator
and
the
docker
runtime
engine,
and
then
we
are
leveraging
Cisco's
infrastructure
technologies,
UCS
a
CI
and
Nexus,
and
also
the
plugins
that
we
have
developed.
A
That
I
will
talk
about
in
the
next
few
slides
and
working
with
Intel
and
working
with
the
various
automation
pieces
out
there
on
scible
puppet
chef,
whatever
the
multiple
options
based
on
customer
interests
and
requirements.
So
so
with
that,
let
me
talk
about
the
two
main
solutions
that
we
are
working
together
today
for
our
customers
to
use.
So
one
is
a
software-defined
and
bare
metal
deployment
model
on
the
left
to
your
left,
it's
the
its
UCS
for
compute
capacity
and
for
storage.
A
It's
also
server
based
storage
using
less
reffers,
so
a
software-defined
storage
running
open
container
platform.
On
the
other
side
we
have
hyper-converged
offering
and
with
a
CI
or
Cisco
Software,
Defined
Networking,
offering
so
a
CI
Cisco
HX,
which
is
our
hyper-converged
stack
and
running
virtual
machines.
So
it's
a
opens.
Openshift
VMware
with
that's
the
I
per,
was
running
on
HX,
then
I
check,
storage
on
the
persistent
storage
side.
So
let
me
go
into
a
little
bit
go
into
a
few
pieces
that
make
up
the
solution
right.
Let
me
talk
about
them
in
now.
A
Most
of
you
should
know.
Probably
no
openshift,
so
I
will
shift
the
the
open
space,
but
I'll
talk
about
the
UCS
space
that
many
of
you
may
not
be
familiar.
So
some
of
the
things
that
matter
in
a
openshift
container,
Mac
sources
deployment,
is
the
elastic
capabilities
that
you'd
need
across
the
stack
so
with
open
shift
and
with
the
applications
you'll
get
that
elasticity
on
the
application
side,
but
not
so
much
on
the
infrastructure
side.
So
that's
where
UCS
provides
value
for
the
for
our
customers.
A
As
you
can
see
here,
UCS,
it's
not
just
a
server.
It's
a
system
that
brings
multiple
things
to
table
its
endpoint
over.
It's
a
100%
programmable
infrastructure
that
fits
right
into
the
DevOps
model
where
customers
or
the
application
developers
need
the
like
the
control
of
the
internet
architecture.
Then
we
have
it's
a
fabric,
centric
architecture
that
brings
compute
network
storage
access,
everything
together
under
single
by
a
single
management
plane,
and
it's
a
provides
the
intent-based
capabilities
based
on
the
technologies.
A
We
have
that
we
call
as
service
profiles,
so
so
using
these
various
capabilities,
you
can
build
the
infrastructure
that
works
best
in
a
container
Mac
services
environment.
So
let
me
talk
about
a
little
bit
about
the
individual
pieces
here
for
a
bed.
So
when
I
talk
about
fabric
centric
design,
we
are
talking
about
both
Ethernet
and
FC,
or
storage
traffic,
going
in
the
same
single
pipe
and,
however,
it's
all
managed
from
a
single
point
of
management.
A
It's
all
handled
the
same
and
all
the
packets
go
the
same
with
limited
coming
connectivity,
so
single
cable
potentially
can
carry
the
whole
load
of
multiple
servers.
Ethernet
storage,
as
well
as
management
traffic,
can
all
also
go
in
one
cable,
so
makes
it
for
easy
manageability
from
a
physical
perspective,
but
also
from
a
management
perspective
and
also
the
density
that
we
have
built
into
this
servers.
It
provides
power
and
cooling
savings
as
well
so
in
terms
of
intent
based
management
right.
So
we
have
the
constructs
that
we
call
a
service
profile.
A
It
is
essentially
a
software
abstraction
of
the
server
identity,
so
server
a
given
server.
There
are
tents,
closed
250
attributes
like
your
IP
address,
like
your
worldwide
name,
like
your
management,
IP
and
so
on,
typically
in
a
typical
server.
These
are
those
are
hard
burned
into
your
server,
whereas
with
UCS,
it's
a
software-defined
entity,
so
that
provides
the
flexibility
when
you
are
growing
your
business
or
optimizing
your
business,
our
load,
balancing
your
business
so
and
we
have
multiple
management
points
to
help
based
on
your
scale
of
deployment.
A
It
could
be
single
site,
it
could
be
multiple
sites,
it
could
be
across
geographies
across
continents,
all
this
with
UCS
manager,
central
director
and
then
with
Cisco
inter
side.
That's
our
new
SAS
based
management
plane
that
can
manage
your
complete
server
portfolio
across
multiple
data
center
across
multiple
sites,
inspector
of
the
workloads
and
applications
you're
running.
So
this
inter
site
and
UCS
margin
general
provides
you
flexibility
to
run
your
traditional
enterprise
applications
as
well
as
your
cloud
native
and
web
scale,
applications
all
on
the
same
platform
using
the
same
set
of
management
capabilities.
A
Okay
and
like
I,
mentioned
our
test
upon
earlier.
It's
a
completely
programmable
system,
it's
all
the
API,
so
all
the
actions,
anything
that
you
can
do
through
command
line
or
you
or
through
the
graphical
interface.
You
can
drive
those
actions
through
api's,
so
we
have
API
is
XML
API
is
we
have
various
SDKs
and
we
have
models
in
ansible
as
well.
The
design
used
extensively
in
our
OpenStack
and
openshift
solutions
that
we
jointly
worked
together.
A
A
So
so,
while
talking
about
the
container
platform,
so
that's
the
UCS
system
now,
how
does
it
tie
into
the
container
and
much
cirrhosis
offerings
that
we
are
having
so
some
of
the
questions
that
customers
have
when
they
are
looking
at
the
plumbing
container
since
the
various
deployment
models?
Should
it
be
bare
metal
or
a
virtualized
deployment?
Should
they
be
using
software-defined
storage
or
hyper-converged
storage,
or
it's
a
Nate
using
native
or
traditional
networking,
or
use
software-defined
storage
or
ACI?
This
is
course
option
so
based
on
these
various
questions
and
design
options
that
customers
think
about.
A
Based
on
these
things,
we
have
built
couple
of
optional
solutions
to
address
for
the
same
so
so
these
are
the
two
things
I
talked
about
earlier.
So
first,
let
me
talk
about
touch
upon
the
one,
the
bare
metal
and
and
the
software-defined
storage,
and
then
touch
upon
the
hyper-converged
and
ACI
one
a
little
bit.
So
the
the
reasons
why
UCS
lends
itself
well
like,
as
you
can
see,
I'm
not
going
to
go
through
the
whole
slide
here,
it
provides,
say
automated
end-to-end
automated
capability
for
the
physical
virtual,
as
well
as
the
container
and
microarchitecture.
A
Okay,
so
on
the
bare
metal
and
software-defined
option,
there
are
two
options
to
equipment
options
we
offer
so
on
the
Left.
It's
more
of
your
enterprise
production
grade
deployment
for
your
critical
applications.
So
there
is
no
single
point
of
failure,
failure
there
and
it's
highly
scalable
and
it's
highly
scalable
and
manageable,
whereas
on
the
right
you
have
a
slightly
smaller
configuration
for
customers
were
looking
at
starting
off
new
or
looking
at
deploying
a
dev
test
environment
where
the
failure
domain
is
not
as
critical.
So
it's
this.
A
Does
this
collocates
some
of
the
core
controlling
points
on
the
same
physical
server?
But,
however,
if
the
Devin
test
environment,
it's
not,
it
should
not
be
that
big
of
an
issue
for
your
deployments.
So
this
is
the
bare
metal
and
the
software-defined
design
that
I
talked
about.
The
other
option
we
have
is
on
our
hyper
flex,
Cisco
hyper
flex
platform,
it's
which
is
our
hyper-converged
infrastructure,
where
it
provides
a
single
pane
of
a
single
management
space
for
your
what's
your
infrastructure
as
well
as
a
storage
piece.
A
So
here
this
is
not
only
hyper-converged,
but
it's
also
in
a
CI
environment
which
is
our
software-defined
networking
environment.
So
this
provides
the
other
options
for
our
customers,
who
are
already
on
the
journey
of
a
CI
or
software-defined
networking
and
also
interested
in
hyper-converged
infrastructure.
So
this
once
again
starts
with
a
as
you
see
there,
one
at
three
to
four
nodes:
it
can
go
up
to
64
roads
and
beyond,
depending
on
your
scale
and
the
beauty
of
this
is
you
don't
have
to
have
everything
together
on
day
one?
A
You
can
start
with
the
bare
minimum
set
of
nodes
and
you
can
grow
as
you
go,
so
you
don't
have
to
design
change
the
design
you
just
had
to
bring
in
the
new
set
of
nodes
added
to
the
cluster
and
you're
off
you
go,
so
your
designs
can
be,
can
be
good
as
your
business
scales
and
grows.
So
so
next
is
for
my
next
steps.
When
we
are
right
here,
Cisco
stop
by
the
booth.
A
We
have
some
demonstration
and
a
deeper
dive
on
the
all,
both
these
solutions
that
October
talked
about,
and
furthermore
there
are
some
giveaways
that
we
will
hand
out
now
as
well.
Any
questions
please,
please
ask
me
also:
we
have
a
detailed
breakout
session
tomorrow
that
goes
into
a
little
bit
more
further,
more
details
into
UCS,
a
CI
and
the
joint
solutions
that
we
have
and
and
the
few
sites
here
for
you
to
get
additional
information
with
that.
Thank
you.
Any
questions
appear
to
answer
you
guys.
Thank
you.