►
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
I
hear
are
many
people
here.
I
would
like
to
tell
you
a
little
bit
about
how
OpenShift
keeps
you
flying
how
OpenShift
helps
us
at
Lufthansa
Technik,
but
first
of
all,
I'd
like
to
introduce
myself.
My
name
is
Tyson
Paul
I
work
for
a
left
on
the
technic
and
I'm
the
architect
for
the
aviator
platform
and
I'm,
also
a
product
owner
for
the
aviator
core
services,
and,
if
you'd
like
to
contact
me,
please
feel
free
to
drop
me
a
line
at
Torsten
at
avatar
dot,
io.
A
Just
to
give
you
a
little
context
about
looked
on
the
technic
Lufthansa
Technik
is
the
daughter
company.
If
they
left
on
the
airline
that
some
of
you
might
know,
and
we
are
the
leading
independent
provider
of
aircraft
maintenance,
repair
and
overall
services.
That
means
we
will
walk
up
to
over
2,000
aircraft
any
day
and
check
it
over
more
than
1,000
aircraft
components.
This
can
be
tiny
walls
to
flight
computers
worth
tens
of
thousands
of
dollars,
and
we've
got
more
than
110
thousand
different
components
in
stock
for
your
replacement.
A
There
would
be
26,000
employees
working
for
you
to
deliver
parts
to
more
than
2,000
aircraft.
That
are
under
exclusive
contract
and
we've
also
got
some
great
stuff
to
create
and
upgrade
VIP
aircraft.
So
of
any
one
of
us
got
a
spare
747
lying
around
feel
free
to
contact
me
after
the
show.
I
said
the
word
theater,
which
is
a
made-up
word
from
Avatar
and
Evita,
because
the
digital
twin
of
the
aircraft.
A
This
is
our
first
purely
digital
product
that
we
created,
and
it
is
an
open,
modular
and
neutral
platform
to
collect
everything
we
know
about
an
aircraft,
so
open
module
and
neutral
should
mean.
We
would
like
to
open
it
to
everyone
who
has
got
something
interesting
to
do
in
the
aviation
context
and
the
customers
can
choose
which
of
the
components
they
want
to
have
and
as
Lufthansa
Technik
has
always
been
an
independent
provider.
A
Just
to
give
you
an
idea.
What
you
can
do
in
aviation
with
digital
product
is
I
will
show
you
a
little
prediction
use
case
and
I
will
talk
about
an
igniter
plaque,
an
igniter
plug
inside
an
aircraft
engine.
You
will
always
notice
that
this
is
an
aircraft
engine.
These
are
the
small
red
dots
down
there.
The
engineer's
told
me
that
they
would
be
there.
It's
a
little
bit
similar
to
the
igniter
that
you
have
in
your
car.
They
will
spark
and
ignite
fuel
but
differently
to
the
igniters
of
your
car
and
aircraft.
A
Engine
has
a
constant
flow
of
fuel
that
will
be
ignited
once
and
then
will
flow
all
the
time
at
another
time
in
the
flight
process.
These
igniters
will
spark-
and
this
this
is
when
you're
flying
through
bad
weather,
because
you
don't
want
the
engine
to
go
out
then,
and
it's
really
hard
to
get
the
engine
going
midair
again,
so
they
will
be
sparking
all
the
time
and
we've
got
two
of
them
because
of
one
priority
in
aviation
is
safety
and
for
priority
to
safety.
A
So
for
safety
reasons.
Again
we
decided.
Okay,
we
have
no
idea
how
often
they
spark
and
they
will
have
a
guaranteed
lifetime
of
I,
would
say:
1
million
sparks
just
for
simplification.
We
say
ok
after
this
and
that
many
flight
we
will
replace
them
anyway.
So
when
we
replace
those
things,
we
will
throw
them
away.
I
have
already
said,
and
we
found
out.
Ok,
they
look
so
good.
A
They
are
kind
of
new
and
we
found
out
that
they
could
be
used
easily
five
ten
times
of
the
amount,
so,
as
I
said,
there's
no
counter
for
the
igniters,
but
when
you
got
all
the
data
together,
you
know.
How
often
is
this
engine
started
and
how
long
did
the
pilot
fly
and
anti-icing
know?
And
this
is
a
prediction
use
case
I
like
because
I
can
explain
it
so
sparks
per
minute
times.
The
minutes
it
is
on.
A
This
will
count
this
box
so
okay,
so
we
can
without
sacrificing
any
safety
and
still
using
a
really
good
safety
margin.
We
can
replace
the
igniters
only
if
we
need
it.
This
will
save
quite
a
lot
of
money,
especially
if
you're
thinking
about
2
or
4
engines
per
aircraft.
Two
of
these
igniters
per
engine
times
300
400
aircraft,
I
found
out
that
I
will
be
short
on
time.
So
I
won't
be
telling
you
anything
about
brakes.
But
if
you're
interested
find
me
at
the
beers
I.
A
Would
like
to
talk
about
OpenShift,
I'm
thinking,
some
of
you
might
be
interested
in
it
and
I
even
got
two
of
the
OpenShift
ones,
and
I
got
a
little
disclaimer
before
that.
I
would
say:
I
will
be
over
extra
rating
developers,
so
don't
take
everything
I,
say
and
still
feel
comfortable
to
get
on
planes
when
you're
flying
home.
A
A
So
with
with
the
ite
that
supports
the
business,
how
do
we
create
software?
We
will
do
a
project
and
then
there
will
be
developers
and
people
who
will
do
stuff
and
then
the
project
ends
and
the
software
needs
to
be
working
after
that
or
it
needs
to
last,
and
so
what
did
we
think
about?
We
said:
okay,
we
want
some
standardization
and
we
invented
something.
We
call
they
looked
on
the
technique
platform.
A
This
is
one
EAP
thing
that
we
are
server,
that
we
customized
a
little
bit
and
it
would
be
deployed
classically
inside
a
VM.
We
also
said:
ok,
we
want
some
standard
architectures
that
can
solve
most
of
the
problems.
We
want
standard,
IC,
ICD
so
and
any
change
can
be
done
by
almost
anyone.
We
want
the
source
code
in
a.
A
We
want
to
have
some
regulation
on
the
source
code
and
we
want
some
code
analysis
and
therefore
we
can
get
the
software
running
by
a
few
people
who,
for
whom
all
these
deployments
look
roughly
the
same
and
those
guys
they
fell
in
love
with
openshift,
and
why
did
they
do
it?
Because
when
we
were
working
on
the
VM
side
of
things
and
introduced
the
open
shift
way,
we
were
able
to
lift
and
shift
almost
everything.
So
we
also
already
got
this
EAP.
That
is
commonly.
A
They
will
get
first
of
all,
no
more
server
drift,
so
ever
drift
is
something
I
would
say:
I
ordered
the
death
machine
in
February
and
the
production
in
december
after
that
and
stuff
has
evolved
after
that,
and
the
death
machine
never
got
patched
and
they
are
somehow
different
and
also
I've
throughout
the
project.
I've
done
something
on
the
death
machine.
I
forgot
about
it
and
stuff
breaks
on
production.
I
don't
like
that.
A
Another
thing
we
were
doing
rolling
deployments
manually
with
our
VMs
as
well,
but
that
requires
someone
to
be
there
to
go
on
the
load,
balancer
and
switch
stuff
and
say:
ok,
boot
up
the
new
server
and
then
switch
over
again,
and
hopefully
they
would
be
doing
anything
right
and
they've
got
automation
and
so
on,
but
for
with
OpenShift
that
comes
for
free
another
thing.
These
self-healing
features
with
aliveness
and
readiness
probes,
most
of
the
instructions
for
the
operations
team.
I've
read
say
if
this
happens.
A
And
the
the
IT
also
like
the
scalability,
so
there
my
scalability
is
not
a
major
problem
for
us,
because
the
business
is
going
steady
most
of
the
time,
but
still
there
are
projects
who
will
have
the
need
for
more
power
doing
at
some
point
in
time,
and
then
they
will.
They
will
idle
most
of
the
time
because
they
will
order
a
specific
set
of
VMs.
I
was
talking
about
the
Aviator
project.
This
is
a
digital
business
case,
so
IT
kind
of
is
the
business,
and
software
has
also
created
differently.
A
We
would
be
creating
software
and
adapting
squats.
That
would
be
there
all
the
time
and
the
products
might
might
be
merge
or
disappear
during
time
because
they
work
out
or
they
don't
work
out
and
we've
got
a
plus.
There
are
almost
no
legacy
systems
so
over
there
there
are
product
owners,
the
guys,
with
the
crowns
on
the
ad
and
the
happy
developers.
They
also
love
the
open
shift
platform.
Why
do
they
do
it?
They
if
their
primary
focus
be,
is
being
fast.
A
They
don't
have
to
wait
for
anything
because
they
can
spin
up
what
they
want
inside
the
openshift
cluster.
They
also
want
to
be
open.
They
would
like
to
say
okay.
If
some
project
comes
over,
then
they
can
join
us
in
our
infrastructure
if
they
need
to.
We
also
want
to
be
flexible.
We
want
to
try
something
out
and
go
back
or
due
to
January
deployments
also,
but
at
least
we
want
to
deploy,
as
often
as
we
can
and
there's
no
presentation
complete
without
saying
DevOps.
A
We
we
have
developers
sitting
over
at
our
place
and
they
hate
to
be
woken
up
at
night.
So
they
like
this
surf
feeling
piece
and
one
thing
for
a
viateur.
That's
important,
I
would
like
it
to
be
cloud
neutral
and
OpenShift
gives
us
an
insulation
layer
towards
the
cloud
product
and,
of
course,
for
us
it's
also
important
to
be
scalable,
but
we
are
working
with
Airlines
and
b2b.
So
we
are
not
talking
about
scaling
in
the
evening
when
everyone
wants
to
watch
a
video,
but
rather
whether
these
use
cases
are
needed
or
not
needed.
A
A
This
one
will
be
running
inside
the
azure
cloud.
If
you
want
to
talk
about
Ezra
cloud,
someone
has
talked
about
beer.
We
will
throw
in
some
cloud
services,
mostly
data
stores,
just
a
word
of
advice.
If
you
want
to
be
cloud
neutral,
be
very
careful
with
cloud
services
and
think
about
what
you're
using
and
we
will
add
some
infrastructure
as
a
service.
So
we
will
rent,
VMs
and
spin
them
up
with
ansible
and
put
the
big
data
and
Kafka
stuff.
On
that.
A
One
thing
I
would
like
to
be
talking
a
little
bit
about
is
the
way
how
we
do
it
and
I've
created
two
approaches.
The
one
I
would
call
the
visit
approach
and
on
the
visit
approach.
I
am
the
developer
and
I'm
coding
all
the
time
and
I
like
my
code
and
I
would
like
to
commit
it
push
it
to
a
repository,
and
then
there
will
be
a
box
around
me
and
I've
got
that's
my
responsibility
and
then
the
wizard
will
come
around.
A
Let's
call
him
Jonas,
so
this
wizard
around
here
will
be
given
me
templates
and
scaffolding
stuff.
So
I
can
I
have
got
an
idea
how
to
create
my
code
that
it
works
with
all
the
magic
that
will
come
later.
I
would
like
to
have
it
and
that
wizard
has
put
in
magic
in
autumn
ization
and
so
on
and
created
all
the
other
builds
that
we've
heard
about
these
approaches
here
already
and
then
there
will
be
unicorns
that
will
try
and
deploy
stuff
to
the
openshift
cluster
and
the
rabbit
wood
comes
out
of
the
Hat.
A
I've
got
no
idea
if
that
works
in
English,
but
so
everything
is
outside
my
box,
I'm
not
responsible
for
that,
and
if
something
breaks
down
in
production,
it's
most
likely
the
Wizards
for
so
this
is
a
I'm
making
a
little
bit
fun.
But
I
think
this
approach
is
really
valid
because
of
the
good
thing
about
it
is
you
can
take
the
developers
they
work
in
this,
this
we're
they
are
used
to,
and
you
still
got
processes
that
will
create
and
recreate
the
same
environments
and
so
on.
So
this
is
really
valuable
to
have
it.
A
Surprise,
the
developers
also
responsible
for
working
on
the
build
pipelines
and
they
will
also
be
deploying
the
stuff
to
the
OpenShift
cluster
and,
as
this
is
openshift,
there's
the
magic
going
on
and
one
other
thing
I
think
your
visitors
never
is
never
late.
He
arrives
at
this
exact
time
he
means
to
so.
A
This
is
really
helpful
to
have
someone
to
enable
teams
and
so
on,
but
I
think
the
whole
thing
is
about
the
the
responsibility
that
you
have,
so
the
develop
was
responsible
for
everything
and
he
has
to
be
to
have
knowledge
about
everything,
so
this
is
kind
of
the
flip
side
of
things.
It's
easy
to
say:
okay,
everyone
needs
to
be
responsible
for
everything,
but
they
have
to
have
the
knowledge
and
they
will
have
to
accept
the
responsibility
for
that.
So
these
are
the
two
approaches.
A
A
One
thing
I
would
like
to
give
to:
you
is
some
opinionated
advice,
so
this
is
my
opinion.
I
would
advise
you
to
find
your
mode
or
your
modes
of
operation,
but
stay
flexible
inside
that.
So,
if
you
put
the
developers
too
much
into
their
cage,
they
will
stay
there
and,
on
the
other
hand,
if
you
give
them
too
much
flexibility,
they
might
be
doing
stuff.
You
don't
want
them
to
have,
but
one
thing
is
the
people
you
have
to
give
them
knowledge.
A
If
you
want
them
to
take
responsibility
and
they,
you
should
encourage
that
responsibility
and
with
every
spider-man
knows
with
great
power,
comes
great
responsibility,
so
we
be
careful
if
you're
giving
them
the
power
they
need
to
accept
that
they
have
got
the
responsibility
to
do
it
and
one
thing
keep
an
eye
on
the
current
development.
You
will
all
be
going
to
the
Red
Hat
summon
and
there
will
be
tons
of
stuff
going
on,
be
careful
and
stay
focused,
because
this
is
too
much.
A
A
So
thank
you
for
listening.
I
think
the
Aviator
story
will
be
continued
and
maybe
you
find
a
presentation
on
day
two
of
openshift
and
if
you
would
like
to
vote
for
us
for
the
innovator
of
the
year
of
what
feel
free
to
get
out
your
phones
now
and
one
thing,
that's
more
important
to
me.
We
we
are
creating
a
platform
for
anything
aviation
related.
So
if
you've
got
a
nice
use
case,
good
ideas
come
to
us.
You
are
invited
to
a
platform
and
then
we
take
off.