►
Description
Keynote: Cloud Native Transformation - The Journey Begins Here! - Ken Owens, CTO of Cloud Infrastructure Services, Cisco
Developers are driving the market for cloud consumption and leading each industry into the new era of software defined disruption. There are no longer questions about elastic and flexible agile development as the way to innovate and reduce time to market for businesses. However, current cloud solutions do not enable application development platforms natively or provide the ability to create applications that are cloud native with elastic services. In addition, businesses are moving to application development architectures leveraging microservices, which are becoming more strategic to their business strategy. When making the decision to build and operate an application in a cloud platform, microservices become central to your application architecture and strategy.
This presentation will describe the Cloud Foundry contributions that address current devops challenges, the data platform that is required to support the business analytics, and the build, deploy, and run, including application monitoring and advanced user plane network enhancements.
The overall architecture of the combined contributions will be described with a customer use case.
Ken Owens
CTO
Cisco
Greater St. Louis Area
Ken Owens is Chief Technology Officer, Cloud Infrastructure Services at Cisco. Ken is responsible for creating and communicating technical/scientific vision and strategy for Cloud Infrastructure Services (CIS) business. He brings a compelling view of technology trends in enterprise IT (e.g., infrastructure, computing, SaaS, virtualization, and cloud) and evangelizes the technology roadmap for the business. Before joining Cisco in 2014, Ken spent over 7 years at Savvis as the Chief Scientist, CTO, and VP Security and Virtualization Technologies. Prior assignments include 5 years as a network security architect at A.G. Edwards & Sons, Inc., and Edward Jones brokerage firms in St. Louis, Mo, and 10 years in the design and architecture of communications systems and components for Erlang Technologies, Tellabs, and Wiltel. Ken holds bachelor’s and master’s degrees in electrical engineering from Missouri University of Science and Technology.
A
For
coming
today,
I
hope
you've
had
a
great
great
day
and
I
know
I've
had
a
great
day
and
enjoy
Cloud
Foundry
stomach
quite
a
bit.
So
I
want
to
kind
of
talk
a
little
bit
today,
sort
of
like
the
black
holes
discussion
right.
What
is
this
cloud
native
transformation
mean
to
you
right,
trying
to
put
a
little
bit
of?
Like
actual,
you
know,
science
behind
how
we're
gonna
get
there
sort
of
thinking
about
the
cloud
native,
and
you
got
to
kind
of
start
with.
What
does
it
mean
right?
A
A
How
do
we
take
what
we've
learned
and
what
we
know
today
and
move
forward
with
that,
and
then
something
I
want
kind
of
announced
as
exciting
is
some
work
that
we've
been
doing
with
with
mezzos
and
with
the
Cloud
Foundry
community,
and
so
what
is
cloud
native
cognitive
is
is
simply
defined
by
these
three
different
areas.
Right,
you
have
sort
of
container
packaged,
so
it's
sort
of
how
do
you
take
an
application
and
and
look
at
making
it
sort
of
a
subset
of
components?
A
How
do
you
break
that
that
that
application
into
smaller
pieces,
it's
sort
of
the
orchestration
and
dynamic
management
of
that
application,
so
you
have
to
one
thing,
is
having
container
packaged
the
next
thing
is
orchestration
and
and
the
management
of
that
in
a
dynamic
environment
and
I
think
the
last
thing
which
gets
overlooked
a
lot
is
it's
this
whole
new
sort
of
application,
architecture,
architecture,
application,
design
pattern
that
is
microservices
enabled.
How
do
you
take
an
application
architecture
and
break
it
into
the
smaller
components
that
you
think
can
make
containerized
right?
A
So
the
third
of
the
three
areas
that
I
that
we
think
about
when
we
talk
about
cloud
native
in
the
industry
when
you
think
about
those
three
things,
do
you
think
about
the
people
in
your
in
your
organization?
Your
pricing?
Well,
we've
had
a
hard
time
just
moving
the
cloud.
Much
less.
Moving
to
you
know
this
all
microservices
model
I
think
it's
important
to
realize
that
you
have
to
work
with
you.
A
People
help
your
people
understand,
and
these
are
like
a
employees,
developers
and
operators
and
DevOps
team's
help
them
understand
what
this
means
to
them
right.
You
can't
just
use
the
term
magic.
You
know
magically
microservices
fixes
all
of
these
problems
right.
You
still
have
a
lot
of
of
organizational
legacy.
A
A
A
How
do
you
then
deploy
that
in
a
you
know
a
lot
of
different
environments,
so
it's
I
mean
think
about
cloud
you're,
not
looking
at
just
your
own
internal
data,
centers
anymore,
you're
thinking
about
other
environments
as
well,
typically,
and
so
how
you
kind
of
manage
weave
deployments
across
multiple
environments
once
were
infrastructure
is
how
do
you
operate
that
that
service
across
multiple
environments?
How
do
you
update
it?
A
How
do
you
men
maintain
sort
of
your
your
software
differentiation
when
you're
kind
of
deploying
this
service
out
into
the
the
public,
Internet
and
there's
this
whole
problem
of
it
looks
fine
when
I
was
developing
and
why
isn't
it
working
in
in
production,
right
and
so
a
lot
of
what
we've
seen
in
this
process
is
that
development
is
much
more
complicated
now
than
it
was
before.
We've
done
a
great
job
as
an
industry,
I
think,
especially
from
an
infrastructure
side
of
things.
A
That's
a
problem,
I
think
it's
an
industry
we
can
solve
for
sure,
there's
also,
obviously,
technology
pieces
as
well
right,
and
so
every
everything
in
this
in
our
industry
has
a
lot
of
Technology
pieces,
and
so,
when
you
think
about
your
data
centers
and
how
they're
transforming
always
right,
you
want
to
sort
of
think
about
something.
I
call
hybrid
DevOps,
which
is
you're
in
a
current
state.
A
There's
a
future
state
you're
going
to
always
want
to
get
to
kind
of
building
a
continuous
pipeline
of
going
from
where
you're
at
to
the
future
is
something
you
should
probably
invest
in
now
right,
instead
of
always
having
the
next
gen,
something,
let's
create
a
platform
that
has
sort
of
next-gen
built
into
it.
So,
as
next-gen
comes
around
it's
just
a
new
service
or
a
new
capability
that
just
shows
up
and
you're
in
u.s.
DLC,
you
don't
have
to
think
about
how
do
I
involve
this
new
platform.
A
So
what
are
some
of
the
lessons
that
that
we,
as
a
community
are
learning
not
just
not
just
the
Cisco
customers,
I
work
with
but
being
in
the
community.
I've
worked
with
a
lot
of
different
customers
from
different
areas,
and
so
I
think
the
first
one
is
whatever
you're
doing
from
a
deployment
mat
model.
Have
you
orchestrating
that
deployment
needs
to
be
part
of
your
test
process
right?
A
There's
the
sort
of
this
new,
this
new
problem
that
we
didn't
really
quite
understand
until
recently
that,
instead
of
it
being
it
worked
on
my
machine,
it's
an
OP
problem.
Now
it's
sort
of
like
what
orchestrated
on
my
machine.
Why
doesn't
it
work
in
that
environment
right
and
so
the
more
that
you
can
take
your
your
orchestration
components
that
you
leverage
for
deployments
into
whatever
environment
you
deploy
into
and
make
that
part
of
your
build
process?
A
And
your
testing
of
that
build
process,
I
think
the
better
off
you
are
at
solving
this
problem,
the
other
problem
that
we've
we
kind
of,
looked
at
it,
at
least
from
a
Cisco
standpoint.
Is
this
entire
infrastructure
thing
I
mentioned
before
with
we
made
it
really
easy
for
infrastructure?
We
made
it
more
difficult
for
the
developers.
How
do
we
sort
of
help
the
developer?
Now?
A
How
do
we
think
more
about
the
software,
develop
it
and
make
it
easier
for
them
to
deploy
their
application,
make
it
easier
to
integrate
with
how
they
develop
and
so
kind
of
this
whole
like
as
you
build
your
application,
let
the
developer
write
in
the
programs
that
they
like
to
write
in
right.
So
a
good
example
of
that
is
Cloud.
A
The
way
you
you
know,
kind
of
take
a
big
monolithic
application
and
breaking
into
smaller
components
is
important
in
this
conversation,
because
if
you
are
going
to
think
about
applications
in
terms
of
smaller
services
and
how
those
services
interact,
it's
important
to
consider
it
first,
how
do
I
break
that
apart?
Do
I
how
many
services
do
I
need
and
there's
a
new
term
that
we've
been
starting
to
use
called
nano
services
right?
You
don't
want
to
create
a
bunch
of
nano
services
where
you're,
making
individual
component
level
calls
to
do
like
one
function
right.
A
You
also
want
to
kind
of
understand
how
to
control
where
these
clouds
would
be
and
deploy
to
some
extent
right
in
this.
This
is
one
of
those
like
you
know,
kind
of
debatable
areas,
but
you
know
I,
think,
there's
still
a
desire
for
having
policy
and
having
an
ability
to
kind
of
control,
compliance
and
governance,
type
of
areas
and
security,
components
within
that
infrastructure
and
it
in
those
deployments
and
so
having
the
ability
to
sort
of
control.
A
So
this
is
kind
of
tying
back
to
the
previous
conversation
right.
I
think
Einstein
had
a
lot
of
great
ideas,
but
this
is
probably
the
best
one
right
that
when
you're
doing
this,
it's
such
a
complicated
environment
today,
let's
make
it
simpler
right.
Let's
try
to
make
this
a
lot
easier
to
do
and
I
think
when
you
look
at
cloud
native
architectures,
that's
trying
to
get
to
that
that
discussion
where
we
make
things
simpler
in
the
end,
it
may
seem
complicated
if
you
get
underneath
the
covers,
but
it
shouldn't
seem
as
simple
as
possible.
A
Those
through
this
whole
composition
thing
making
these
services,
as
we
usable
as
possible
and
as
self-contained
as
possible,
is
really
important,
but
don't
forget
that
there's
still
linkages
between
these
these
services
right
and
you.
It
might
be
a
loose
coupling,
but
there's
still
a
coupling
there,
they're
not
not
lose
track
of,
and
so
that's
sort
of
the
like.
A
The
lessons
we've
learned
along
the
way
and
they're
still
learning
I
should
say,
and
so
then,
what,
when
we
talk
about
next,
is
sort
of
what
what
I've
been
working
on
at
Cisco
is
creating
a
mezzos
framework
to
support
all
the
cloud
native
services
and
it's
kind
of
common
and
containerize.
What
I'm
like
trying
to
containerized
cloud
founders?
What
we're
trying
to
do?
A
I'm
working
with
the
foundation
right
now
to
sort
of
get
certification
for
this
work,
but
the
idea
was
sort
of
taking
each
of
the
different
CF
components
and
putting
them
inside
a
framework
and
we're
demoing
this
in
our
booth.
If
you
want
to
come
down
and
see
it
tomorrow,
but
all
the
different
aspects
of
of
a
Cloud
Foundry
deployment,
you
can
leverage
with
then
Maysles
framework
and
then
what
we
did
was
would
kind
of
tie
it
into
the
pipeline,
of
course.
A
So
as
new
capabilities
come
out,
we
get
we
picked
them
up
and
we,
you
know,
create
the
relevant
framework
changes
and
highlight
those
changes
in
the
in
the
pipeline
and
then
the
the
other
thing
is.
A
lot
of
administration
has
been
done
in
a
lot
of
enterprises
to
take
Cloud,
Foundry
and
kind
of
leverage,
the
authentication
mechanisms.
So
we
want
to
make
sure
we
supported
that
as
seamlessly
as
possible.
A
So
good
student
learning
more
about
any
of
these
projects.
We
have
a
couple
of
sites.
You
can
go.
Look
at
matt
rely.
Oh,
this
is
an
open
source
project
that
cisco
started,
but
it's
a
large
community
now
it's
definitely
not
I.
Think
I
have
like
eight
developers
on
it,
but
there's
like
70
developers
working
on
the
project.
A
So
it
was
definitely
not
a
Cisco
only
project,
but
the
whole
point
of
a
mantle
was
sort
of
taking
the
Best
of
Breed,
open
source
components
and
bringing
them
together
and
making
it
easier
and
simpler
to
run
services
and
and
just
whole
new
infrastructure
that
we're
calling
micro
services
infrastructure
I'm.
Making
this
whole
cloud
native
model
a
lot
easier.
A
We
also
have
a
developer
experience
to
kind
of
go
along
with
this.
It
sort
of
looks
at
that
problem.
I
mentioned
earlier
of
trying
to
solve
this
developer,
making
it
easier
for
developers
to
build
and
deploy
and
run
their
applications
without
having
to
worry
about
the
underlying
complexities
of
the
infrastructure,
and
so
that's
at
Cisco,
ship,
calm
and
sorry,
the
souping
Cisco
ship,
dot,
IO
and
then
so.
Those
are
sort
of
the
two
big
projects
we
have
the
the
work
we're
doing
and
in
cloud
foundry
terrorizing
a
foundry
as
part
of
that
mantle
IO
site.
A
So
you
can
look
at
that
code
if
you
want,
and
so
in
summary,
the
clowny.
The
transformation
is
something
that
is
occurring
in
most
places
already.
Most
of
you
guys
are
here
because
you're
part
of
that
already,
so
there's
no
reason
for
me
to
make
it.
You
know
more
obvious
than
this
is
happening.
You
can
look
around
and
see
other
people
here,
so
we
know
it's
happening.
A
There
are
the
things
you
need
to
think
about
with
your
people
and
and
your
organization
on
how
you
look
at
that.
There
are
things
in
the
process
and
and
making
sure
that
your
orchestration
is
happening
as
part
of
your
development
process
versus
and
after
the
fact
thing
and
there's
a
lot
of
lessons
to
be
learned
on
sort
of
how
do
you
adopt
new
technologies
and
make
this
more
continuous
from
the
beginning?
And
then
the
interesting
you've
hinted
in
the
look
on
the
meso
stuff.