►
From YouTube: OpenShift on Azure at Sabre with Jim Zimmerman and Jim Anderson at OpenShift Commons Gathering 2019
Description
OpenShift on Azure at Sabre
Jim Zimmerman (Microsoft)
Jim Minter (Red Hat)
Jim Anderson (Sabre)
at OpenShift Commons Gathering 2019
Red Hat Summit
B
It
was
a
pre
announced
last
year
summit
and
we're
delighted
to
be
coming
back
this
year
to
talk
some
more
about
it.
With
me,
I've
got
Jim
Zimmerman
from
Microsoft
he's
the
principal
product
manager,
who's
been
driving
the
program
from
Microsoft
side
and
in
a
few
minutes
we'll
be
delighted
to
invite
him
to
stage
Jim
Anderson
as
well,
who
is
from
Sabre
he's
an
enterprise
architect
and
Sabre
has
been
really
pivotal
and
really
helping
us
out
as
part
of
the
private
preview
work
that
we've
been
doing
for
as
you--as
Red
Hat
openshift
as
well.
B
Giving
lots
of
great
feedback
and
collaboration
on
that
as
well,
so
what
I'd
like
to
do
is
hand
over
first
to
Jim,
Zimmerman
he'll
tell
us
more
about
the
the
program.
What
we've
been
working
on
in
the
middle
I'll
say
a
few
words
about
some
of
the
features
and
some
of
the
technical
features
of
the
product,
and
then
we're
really
looking
forward
to
hearing
all
about
the
use
case
and
experience
of
you
actually
using
as
your
Red
Hat
openshift
from
Jim
from
Sabre
so
away
you
go
Jim
thanks,
Jim,
yes,.
C
C
When
we
first
started-
and
it's
kind
of
interesting,
because
you
know
a
little
over
three
years
ago-
we're
all
in
a
room,
and
someone
brought
in
some
of
these
special
red
hats
for
us
right
and
I.
Don't
think
they
were
supposed
to
give
us
these,
but
anyway,
I
think
it
was
just.
You
know
as
a
as
a
token
appreciation
of
starting
the
partnership
and
one
of
the
first
demos
they
showed
us
was
open
shift
and
we
had
never
seen
it
before.
C
We
didn't
even
know
what
it
was
and
it
was
I
think
it
was
before
it
worked
with
kubernetes
too
so
anyway,
it
was
a
really
good
demo.
I
was
like
God.
What's
that
product
they're,
like
don't
worry
about
it,
we'll
talk
about
it
like
later,
let's
just
start
with
RAL,
so
you
know
we
started
with
rel,
you
know
and
Azure
a
lot
of
our
mutual
customers
were
asking
for
it
and
they
wanted.
They
wanted
better
support
right.
So
the
customers
are
asking
us
hey.
C
Could
you
figure
out
a
way
to
support
rel
on
Azure,
because
we
want
to
use
it
and
we
hate
having
to
have
to
ticketing
systems
where
you
know
we
file
a
ticket
with
Red
Hat,
they
say,
don't
support
it
run
adder
we
filed
state
with
a
juror,
they
say:
oh,
it's
not
supported
on
or
Red
Hat
doesn't
support
it.
So
anyway,
we
got
together
and
created
this
first-class
support
right.
That
was
the
first
initiative.
We
did
then
one
of
the
second
ones
we
did
is
we.
C
We
thought:
okay,
well,
we're
launching
this
sequel
server
on
Linux,
Red,
Hat,
Enterprise
Linux
is
one
of
the
popular
ones.
On-Prem,
why
don't
we
make
something
work
together,
so
we
got
sequin
rel
and
then
we
also
looked
at
or
not
looked
at,
but
it
also
offer
well
what's
si
P
a
couple
years
ago,
I
was
lucky
enough
to
do
to
you
a
keynote
demo
here
and
we
demoed
a
JBoss
app
talking
to
sequel
server
running
on
rel.
That
then
talked
to
Windows
containers
about
two
years
ago.
C
It's
kind
of
in
openshift
I
think
so
so
it's
been
a
fun
journey
so
far,
which
brings
us
to
today.
So
for
the
last
year,
our
two
engineering
teams
have
been
working
really
hard.
Together
we
have
daily
scrums,
we
have
a
slack
channel,
we
work
together
every
day
and
we're
building
a
platform
that
will
be
fully
supported
and
engineered
by
both
companies
right,
and
so
this
is
really
important
because,
as
we
engineer
things
together,
we
find
bugs
that,
otherwise
we
wouldn't
have
found
right-
or
maybe
we
say-
oh
it's
their
problem.
C
Oh
it's
their
problem
since
we're
building
the
service
together.
It's
our
problem
right.
So
we.
If
that
means
we
have
to
backport
certain
fixes.
We
have
to
change
things
the
way
they
work
in
hash,
or
maybe
we
have
to
use
specific
load
balancers
things
like
that.
We
actually
find
this
solution
and
all
this
great
work
that
we're
doing
feeds
back
into
openshift,
so,
whether
you're
using
our
service
or
not,
you
can
still
get
all
the
benefits
from
this
relationship
with
the
open
ship
bits
on
after
ok.
So
you
know
we
have.
C
You
know
we're
building
this
enterprise
in
mind.
You
know
security
compliance,
our
first
right.
We
also
want
the
developer
experience
to
be
good.
Not
every
developer
wants
to
have
to
manage
their
own
data
apps
inside
the
cluster
right,
so
we're
gonna
make
it
easy
to
integrate
with
Azure
data
services,
and
you
know,
since
this
is
fully
managed,
we
are
gonna.
Do
that
baits
for
you,
so
no
more
painful
running
a
sensible
script
to
update
the
cluster
and
that
stuff.
We
will
do
that
for
you
all
right.
C
C
Ok
whew:
this
is
how
you're
probably
running
it
like.
This
is
really
the
only
way
to
run
it.
So
you
know
you're
in
charge
of
basically
everything.
The
only
thing
that
is
supported
is,
if
you
call
Red
Hat
you'll
get.
You
know,
support
forum,
so
if
you
called
Microsoft
you'll
get
support
for
magic.
So
what
we've
done
is
we've
taken
away
the
complexity,
and
this
is
what
you're
gonna
see
now
with
the
service
right,
so
all
of
the
I
asked
components
can
disappear.
From
your
view,
we
take
care
of
the
cluster
creation.
C
Cluster
management
monitoring
logging
network
configuration
all
the
security
patches.
Then.
Obviously,
the
platform
support
what's
nice
about
this
is
since
we
do
have
integrated
support,
we
can
wake
each
other
up,
so
we're
using
the
same
ticketing
systems
on
Microsoft.
We
use
this
system
called
ICM.
So
if
we
have
an
alert
that
your
cluster
down
or
there's
something
wrong
with
it,
it
can
wake
up
both
Red
Hat
and
Microsoft,
and
since
we
are
together
as
a
team
troubleshooting
this
there
won't
be
a
back-and-forth
of
tickets.
C
B
Thanks
Jamie,
so
how
interesting
that
has
been
done
as
the
sliders
been
updated
since
I
last
up
today,
we're
live
all
right.
So
before
we
talk
about
the
before
I
talked
about
the
developer.
Experience
I
just
wanted
to
say
a
few
more
words
about
the
the
team
behind
the
before
behind
the
the
the
platform.
So
it's
quite
an
interesting
use
case
because
we
are
a
global
team
with
engineers
and
support
and
service
Ataris
globally,
distributed
to
to
work
on
and
to
build
and
support.
B
You
are
using
this
service,
so
we've
got
engineers
all
the
way
from
Australia
to
to
Germany
from
Mexico
to
China
in
the
US
and
the
UK
all
over
the
world,
and
really
not
only
in
a
globally
distributed
team.
Are
we
one
single
team
working
on
this,
but
we're
also
one
single
team
working
across
two
different
organisations
as
well?
So,
as
Jim
said,
we've
got,
we
do
twice
weekly
scrum
calls
between
engineering
in
Microsoft
and
in
Red
Hat.
B
So
not
only
is
it
that
we
use
the
same
systems,
you
know
as
part
of
the
service.
The
Microsoft
team
uses
Linux
systems,
the
Red
Hat
team
uses,
you
uses
Windows
systems
and
we
all
work
together.
Using
all
of
these
things,
we
haven't
yet
got
term
Jim
working
on
Emacs,
yet
but
I
know
the
then
I
know
the
day
is
coming
so
I
actually.
B
M,
well
there
you
go
okay.
If
that
day
is
here,
you
can
bet
that
you
heard
it
here.
First,
okay,
so
in
terms
of
the
the
actual
experience
for
end
users
using
OpenShift
measure
of
the
the
the
story
here
is
that
there's
no
story,
so
what
we
are
doing
is
we're,
taking
and
reusing
all
of
the
well-known
OpenShift
bits
that
you
use
on
premise
that
you
might
use
as
part
of
open,
shipped
dedicated
or
origin.
B
So
one
of
the
key
things
here
is
for
whether
you're
skilling
up
people
to
use
OpenShift
or
whether
you're
experienced
OpenShift
users
already
the
really
the
field,
look
and
feel
and
the
way
that
the
platform
works
without
as
you
a
Red
Hat
openshift
is
exactly
the
same,
so
whether
you're,
using
it
on
its
own
in
the
azure
cloud
or
whether
you're
using
it
as
part
of
a
hybrid
cloud
strategy
and
all
of
that
stuff.
It's
dart
fits
together
directly.
B
So
an
end-user
who's
using
as
you
arrived
had
openshift
sees
the
same,
open
share,
console
and
that
they
would
be
using
if
it
were
on-premise
or
if
it
were
on
their
laptop
and
in
fact
the
platform
as
well.
From
the
point
of
view
of
the
administrator
of
the
platform,
it
looks
and
feels
very,
very
similar
to
any
other
Azure
service.
B
So
one
of
the
key
things
here
is
that
we
are
a
first
party
yeah
first
level,
first
class,
you
as
your
resource
so
just
like,
and
as
your
administrator
would
organize,
it
would
request
a
a
network
or
a
load
balancer
or
a
VM
or
a
firewall.
Getting
an
open
ship
cluster
is
exactly
the
same,
so
it's
the
same
tooling
and
the
REST
API,
or
the
AZ
command
line
tooling,
as
you're.
Seeing
on
the
animation
right
now
to
be
able
to
create
a
cluster
so
an
end
user.
B
So
another
key
part
of
the
offering,
as
well
as
being
very,
very,
very
close
and
identical
to
the
on-premise
OpenShift.
Another
key
thing
is
tight
integrations
between
as
your
Red
Hat
OpenShift
and
the
rest
of
a0
as
well.
So
one
example
of
those
is
the
animation
here.
So
it's
the
fact
that
we
use
is
your
active
directory
for
single
sign-on,
so
it's
reusing
and
the
same
as
under
lying
as
your
capabilities
as
part
of
the
cluster.
So
we've
got
close
integration
for
identity.
B
We've
got
close
integration
for
networking
as
well.
So,
for
example,
you
can
have
your
open
shift
cluster
deployed
on
cloud
and
use
as
your
Express
route
technology.
To
then
have
traffic
go
between
that
cluster
and
your
on-premise
data
center,
for
example,
or
you
can
have
the
cluster
access
other
components
item
these
your
cloud
or
anywhere
else
or
you
or
your
own
code,
that's
also
running
in
the
cloud
and
as
well
as
you
in
as
well
as
sign-on
as
well
as
networking.
B
You
closed,
storage
integrations
and
also
closed
integrations
with
a
great
deal
of
other
as
your
as
your
capability.
So,
for
example,
if
you
want
to
run
your
your
database
on
on
Azure
and
then
you
want
to
consume
the
the
applicant,
the
data
from
applications
running
an
open
shift.
There's
also
tight,
integrations
there
as
well
now.
C
C
That
wasn't
even
planted
I
just
noticed
that
I
was
like
that's.
We
don't
want
people
to
think
that,
so
so,
there's
a
lot
of
resources
you
can
check
out
today
before
we,
you
know
bring
up
Jimmy
Anderson
from
Sabre,
where
there's
a
keynote
tomorrow
with
Jim
and
Sasha
tomorrow
evening.
Come
check
that
out
we
have
a
big
Microsoft
booth.
We
have
a
whole
OpenShift
section
that
you
can
come.
Ask
us
any
questions
that
you
want
about
the
service
or,
if
you
just
want
to
kind
of
pick,
our
brains
ask
for
features.
Things
like
that.
C
We
have
an
open
shift
lab
on
I
did
forgot
to
put
the
day
it's
on
Thursday
I
think
it's
on
Thursday.
It
is
Thursday
from
10:45
to
12:45,
I,
don't
know
if
it's
full
yet
check
it
out.
I
think
we
allow
up
to
like
50
people,
that's
right,
yeah,
mm-hm
and
then
yeah.
So
then,
ass
expert,
forever
red
at
open
chest.
Ask
our
experts
anything,
and
so
with
that
will
we
want
to
bring
up
Jimmy
Anderson
from
Sabre
talk
a
little
bit
about
what
he's
doing
with
open
shift
I.
Never.
D
D
Third
leg
of
H,
a
Jim
Jim
Anderson
LeSabre
I've,
been
at
Sabre
18
years
I'm
with
our
enterprise
architecture,
team,
I'm
gonna
tell
you
a
little
bit
about
Sabre
a
little
bit
about
our
cloud
and
container
journey.
What
we've
done
with
Azure
managed
OpenShift
and
then
what
we
hope
we
could
do
with
Azure
managed
OpenShift
a.
D
D
We're
kind
of
on
the
on
the
back
end,
where
a
system
that
helps
the
travel
industry
markets,
sell
and
operate
their
products
and
Sabre
is
pretty
huge.
This
is
on
a
per
second
basis
per
second
well
go
per
day
per
day.
We
handle
billions
of
transactions
and,
over
the
course
of
the
year
we
support
billions
and
billions
of
dollars
of
travel,
spend
we
connect
travelers
with
travel
suppliers.
D
When
our
system
status
is
green,
nobody
knows
who
we
are.
They
don't
really
care
who
we
are,
but
when
our
system
status
turns
red,
Sabres
name
is
all
over
the
news.
People
are
waiting
in
the
airport
getting
mad
at
the
airline
desk
clerks,
but
it's
usually
not
their
fault.
It
could
be
us,
you
never
know,
but
that's
enough
about
Sabre
our
cloud
and
container
journey.
So
far,
one
of
the
great
things
about
cloud
is
literally.
Anybody
can
start
using
clouded
at
any
minute.
Just
grab
your
credit
card
swipe
it.
D
You
know
the
full
power
of
AWS
Google
Cloud
Azure
at
your
fingertips,
who
started
their
their
cloud
journey
with
a
corporate
card
and
expensing
it
all
right.
I'm
gonna
come
get
you
guys
later,
but
the
four
years
ago,
when
I
started
clout
at
Sabre.
Now
this
is
where
we're
at.
We
had
our
developers
we're
charging
cloud
on
their
corporate
cards,
not
because
they
were
being
malicious.
They
just
couldn't
get
what
they
wanted
out
of.
Our
corporate
IT
department
obviously
went
ahead
and
started
using
it
around
that
same
time.
D
D
By
the
end
of
last
year,
we
had
a
wide
area
network
that
connected
all
of
our
clouds
together
and
our
data
centers.
So
we
could
easily
move
workloads
from
one
place
to
another
in
AWS
us
two
out
in
Oregon.
That's
where
we're
developing
our
next
generation
platform
at
the
heart
of
our
next-generation
platform
is
RedHat
OpenShift.
D
So
at
the
end,
in
our
hybrid
cloud
strategy,
we're
gonna
have
our
private
cloud.
We're
gonna,
have
AWS
and
we're
gonna
have
a
sure,
obviously
with
OpenShift
mixed
in
there.
We
also
have
one
more
cloud
that
we
don't
like
to
talk
about.
We
have
a.
We
have
a
cloud
of
regret,
so
is
it
IBM's
cloud?
Is
it
IBM's
cloud?
You'll
have
to
buy
me
a
beer
later
to
find
out
which
cloud
this
one
is.
D
D
And
it's
not
just
it's
the
same
on
the
travel
industry,
all
of
our
airlines,
all
of
our
hotels.
All
of
our
travel
agencies
are
going
through
digital
transformations
in
order
to
keep
up
with
them
and
to
satisfy
our
customers
Sabres
having
to
reinvent
itself
and
that's
what
we're
doing
with
our
next-generation
platform,
that's
built
on
OpenShift
and
cloud.
D
D
D
Everybody
has
a
layer,
cake
diagram
of
their
architecture.
I'm
not
gonna,
go
through
the
whole
thing,
but
on
the
on
the
bottom,
it's
cloud:
migration,
that's
the
infrastructure,
that's
private
cloud,
that's
public
cloud
with
AWS
and
Azure
and
a
key
component
for
us.
There
is
Red
Hat
OpenShift
in
five
to
ten
years.
We
don't
know
exactly
where
our
customers
will
demand
that
we
run
their
workloads.
So
we
need
a
platform
that
we
can
bring
with
us
wherever
we
need
to
to
deliver
our
capabilities
in
the
geography
that
our
customers
need.
It.
D
How
the
mainframes,
you
saw
a
picture
of
one
of
the
old
mainframes
at
the
beginning.
We
still
have
the
mainframes,
but
by
2023
we're
getting
off
mainframe
and
what
are
we
doing
at
the
workloads
that
we're
pulling
out
for
there?
The
workloads
that
we
have
on
the
mainframe
we're
dropping
them
straight
into
our
next-generation
platform,
which
means
we're
dropping
them
straight
into
Red.
Hat,
open
shift.
D
All
right,
Azure
managed
OpenShift.
So,
a
year
ago,
in
San
Francisco,
when
Microsoft
announced
Azure
managed
OpenShift,
we
got
pretty
excited.
We
were,
you
know.
We
had
already
chosen
openshift
for
our
next
generation
platform
and
we're
wondering
if
we
could
use
Azure
managed
OpenShift
to
take
some
of
that
heavy
lifting
off
of
our
hands
of
operating
clusters.
D
So
we
contacted
our
support
team,
our
Microsoft
team
and
we
got
into
the
beta
program
for
Azure,
managed
OpenShift,
and
here
are
a
few
ways
that
we've
used
azor
managed
to
open
shift.
What
we've
been
in
the
beta
program
in
the
fall,
Red,
Hat
and
Microsoft,
and
a
few
other
sponsors
sponsored
a
hackathon
in
our
Krakow
Poland
office.
D
D
Our
IT
risk
and
security
team-
they
they
wanted
to
dig
deep
into
into
OpenShift
into
the
clusters,
see
what
kind
of
pen
or
penetration
tests
they
could
do,
try
and
find
all
the
holes,
and
they
want
to
do
some
destructive
testing
and
we
didn't
want
them
doing
that
on
our
the
clusters
that
we're
building
in
AWS.
So
we
let
them
spin
up.
Openshift
clusters
on
Azure
Azure
managed
to
OpenShift
was
super
easy.
They
could
do
it
themselves,
they
could
shut
them
down
and
they
didn't
have
to
use
any
time
from
our
operations.
Team.
D
With
the
applications
that
we're
putting
onto
next-gen
platform
onto
OpenShift,
how
we're
going
for
a
continuously
available
application
architecture,
which
means
we're
gonna,
have
to
span
multiple
regions
in
the
cloud
in
order
to
make
that
happen.
So
pretty
soon,
we'll
have
more
regions
in
AWS
with
openshift.
D
And
as
our
developers
start
to
see,
increasing
velocity
everybody's
gonna
want
their
own
cluster
she's
gonna
want
a
cluster
that
guy's
gonna
want
a
cluster.
The
guy
in
the
back.
There's
gonna
want
a
cluster,
and
that's
that
slide.
That
slide
really
scares
me.
How
do
you
operate
hundreds
and
thousands
of
OpenShift
clusters.
D
All
right,
if
a
transformation
journey
sounds
exciting
to
you
and
you
like
working
with
Microsoft
and
Red
Hat,
come
and
join
us
come
and
join
us.
We
have
offices
in
Krakow,
Poland,
Bangalore,
India,
Dallas
Texas
and
in
a
few
weeks
we're
opening
up
an
office
just
down
the
street
here
in
Boston
our
Boston
innovation
lab
all
right.
Thank
you.
Everybody!
Thank
you!
Jim
and
Jim.