►
Description
London OpenShift Commons Gathering 2019 Lightning Talk: Microsoft
OpenShift on Azure
A
Since
then,
we've
kind
of
worked
together,
first
M
Jana's
team
and
the
engineering
team
within
Microsoft
to
basically
bring
the
the
platform
onto
writer
itself.
Couple
of
features
in
terms
of
what
we're
looking
to
be
able
to
actually
provide
is
self-service
deployment.
So
we
have
an
AZ
command
line
a
said,
open
shift,
create
that
will
spin
up
your
your
open
shift
cluster,
for
you
do
all
the
integrations
with
the
angel
services,
the
infrastructure
to
be
able
to
scale
the
cluster
up
and
down.
A
So
in
terms
of
what
we're
actually
providing
with
this,
offering
we're
providing
the
monitoring
of
the
application-
and
this
is
the
responsibility
of
both
Red
Hat
and
Microsoft-
to
be
able
to
provide
this
for
you
as
a
customer
monitoring
the
health
of
the
cluster
making
sure
the
cluster
is
up
and
running
and
fixing
it
if
it
breaks
network
configuration,
so
you
don't
have
to
mess
around
with
the
IP
address
allocation.
You
can
do
that
if
you
want
to-
or
we
can
take
care
of
that
for
you
as
well.
A
Software
and
security
updates
patching
those
types
of
things,
as
well
as
the
platform,
support
and
infrastructure
management.
This
is
a
pure
managed
service
that
we're
offering
to
you
so
Red
Hat
engineers
will
look
after
your
service.
For
you,
the
azure
engineers
will
look
to
the
platform
for
you
as
well,
basically
allowing
you
to
get
on
with
the
good
stuff,
which
is
actually
deploying
applications
on
to
openshift.
A
So
in
terms
of
what
you
are
responsible
for
from
a
customer
perspective,
it's
the
standard
stuff
that
you
would
assume
quota
management,
user
management,
application
lifecycle,
those
types
of
things
we
don't
take
care
of
that
stuff.
For
you,
it's
not
totally
managed
in
terms
of
you,
give
us
a
deployment
manifest,
and
we
do
everything
for
you.
That's
still
your
responsibility
now.
The
reason
why
I
got
mg
up
on
the
stage
is
that
how
do
I
put
this
Microsoft
historically
hasn't
been
great
at
open
source.
My
former
CEO
saying
open
source
is
a
cancer.
A
You
can't
you
know
you.
It
doesn't
sit
very
well.
Last
year
at
Microsoft,
I
looked
after
the
open
source
business
in
the
UK,
so
I've
kind
of
done
this
pitch
lots
and
lots
of
times
but
I'm
not
going
to
bore
you
with
the
finer
details.
But
when
you
talk
about
Microsoft
and
Red
Hat,
working
collaborating
really
really
closely.
Usually,
what
I
would
explain
would
that
we'd
have
integrated
support
teams
who
would
basically
use
submit
a
support
ticket
into
Azure?
A
It
will
be
picked
up
by
the
engineering
team
in
in
Red,
Hat
and
we'd
work
together
to
be
able
to
resolve
this.
What
we're
doing
with
managed
openshift
is
totally
different.
We
have
Co
engineering
teams
who
are
working
together
to
develop
this
solution
to
make
sure
that
we
operationally.
This
is
sound
for
you,
so
I
got
MJ
upon
stage
because
I
wanted
to
get
his
opinion
in
terms
of
how
do
our
companies
actually
work
together?
So
the
first
thing
I
do
want
to
ask
you
is
how
is
it
working
with
Microsoft
so.
B
A
The
other
thing
in
terms
of
how
the
teams
are
actually
working
together,
95%
of
what
you're
actually
working
on
is
on
github
is
a
public
repo
for
you
to
be
able
to
work
on.
You
can
go
and
see
what
progress
we're
making
in
terms
of
this
as
well,
when
I,
say
95%,
there's
a
5%
component,
which
we
call
the
resource
resource
provider,
which
is
heavily
coupled
into
the
answer.
Infrastructure
I
talk
to
the
product
manager
last
night,
and
you
know
there
may
be
some
movement
on
that.
A
Let's
just
let's
just
leave
it
like
that,
so
you
know
it's
interesting.
Obviously,
we
acquired
github,
that's
a
totally
separate
conversation
altogether,
but
you
know
this
is
all
being
developed
in
the
open
as
well,
and
what
we
want
is
for
people
and
the
community
to
be
able
to
learn
from
what
we
are
doing
together
to
be
able
to
run
open,
shifters
scale
globally.
A
One
of
the
the
other
things
I
think
that
that
we
kind
of
really
want
to
talk
about
is
that
it's
easy
to
be
able
to
develop
the
code
together
right.
It's
open
source,
pull
requests.
You
know
all
of
that
good
stuff
which
goes
on,
and
it's
relatively
easy
to
be
able
to
go
through
that
process.
What
we're
trying
to
achieve
as
companies
together
actually
is
some
of
the
actual
some
of
the
difficult,
the
softer
things
which
are
around
that.
A
So
you
know
how
do
you
run
an
open
shift
platform
at
the
scale
that
we're
talking
about
we're
talking
about
basically
fifty
four
regions
globally,
that
that's,
basically
the
sales
pitch
over
from
a
Microsoft
perspective?
You
know
it's
difficult
to
be
able
to
run
a
single
platform
and
to
be
able
to
scale
that
for
customers,
you
know
how
do
we
handle
a
Red,
Hat
employee
being
able
to
log
into
a
customer
subscription
to
be
able
to
diagnose
those
issues?
You've
got
a
Microsoft
badge.
A
Now
you
got
a
Microsoft
saw
device
which
is
a
secure
device
to
be
able
to
log
into
the
azure
back-end
as
well.
You
know
how
do
we
fix
those
operational
things
to
be
able
to
actually
make
all
of
this
work?
The
other
things
like
identifiable
information
in
in
log
files?
How
do
we
actually
manage
all
that
stuff?
We
want
to
fix
this
as
an
organization
and-
and
those
are
the
things
that
I
think
will
be
actually
be
able
to
give
back
to
the
community.
To
be
able
to
say
look.
This
is
how
you
do
it.
A
This
is
how
you
fix
those
those
difficult
problems
so
yeah
we
are
going
to
learn
as
both
both
companies
trying
to
figure
out
how
this
works,
how
this
works
at
scale
and
I
think
we
will
be
back
next
year
in
terms
of
once
we've
gone
into.
Jae-Won
people
are
using
it.
What
we've
learned
from
that
to
be
able
to
give
some
of
those
learnings
back.
So
thank
you
very
much.