►
Description
OpenShift Commons Gathering
Milan Italy 2019
Title: (Almost) 5 years of OpenShift at Amadeus
Speaker: Salvatore Dario Minonne (Amadeus)
A
A
Spent
the
five
years
of
my
life
working
on
the
clouds
for
a
MIDI
use,
but
I
also,
although
experience
I
spend
some
time
working
from
an
in-memory
use
with
the
unit
and
I
have
previous
life
in
ETA,
intronic,
design,
automation
and
Finance
here
in
Milan,
which
is
also
the
place
where
I
be
graduated
in
computer
science
engineer
so,
for
me,
being
here
is
like
being
back
at
home,
fax,
the
an
invitation
text,
I
know
from
the
invitation.
Thank
you
ready,
I
appreciate
it.
A
Okay,
in
the
next
20-30
minutes
of
time,
together,
I'm
going
to
speak
a
little
bit
about
a
MIDI
use
and
what
is
a
MIDI
use
more
or
less,
and
when
everything
about
cloud
started.
This
is
a
community
meetup.
So
we're
going
to
speak
more
particularly
about
the
a
MIDI
used
on
the
community
sure
we
have
a
lot
of
things
that
can
be
said,
but
I
would
prefer
to
focus
on
the
community
at
least
today,
in
the
future
or
at
least
on
in
the
cloud
or
in
the
web.
A
You
can
find
other
presentation
that
we
gave
in
the
past
that
you
will
do
in
the
future,
we're
going
to
speak
about
the
community
and
we
are
going
to
speak
also
what
we
miss
in
the
slide.
If
we
could
come
back,
we
are
going
to
explain
what
have
missed
some
mistakes
that
we
made
and
some
things
that
okay,
probably
miss
it
something,
but
at
the
end
of
the
story,
first,
cultural
reason
for
business
reason
for
budget
reason.
A
We
couldn't
do
differently
and
simply
the
model
that
OpenShift
and
kubernetes
in
general
expose
didn't
fit
that
well
with
us.
But
if
the
way
it
is,
and
in
the
last
slide,
when
they
keep
on
running
I,
will
explain
what
we
are
working
on
and
what
is
really
what
we
are
really
focus
on
for
the
next
month
or
year.
A
Okay,
what
is
I'm
gonna
use?
I,
don't
know
if
you
know
what
we
are
pretty
big
company.
We
are
more
or
less
nineteen
thousand
all
over
the
world
and
we're
an
eighty
travel
actors,
one
of
the
major
IT
travel
actors,
I,
cannot
say
the
major
because
I
don't
know
very
well
the
market,
often
the
brave
competitor
side,
but
I
know
that
we
are
one
of
the
major
and
if
you
look
at
Wikipedia
asking
them,
what
is
the
travel
IT?
What
is
the
business?
There
are
two
or
three
things
that
you
can
learn.
A
For
example,
there
is
a
DC
s.
The
partial
control
system
is
the
software
that
handled
the
the
fact
that
the
plane
I
needed
to
go
needs
to
leave
the
airport
and
land
in
another
Airport,
and
there
is
also
a
lot
of
software
that
is
undoing
all
this.
We
do
that
we
have
any
DCs
in
inside
memory
use.
There
is
also
a
reservation
system
computerized
reservation
system
as
well.
There
are
some
brave
competitors
that
do
that.
We
do
also
at
well,
and
there
is
also
the
GDS,
the
global
distribution
system.
A
A
We
are
present
in
more
than
190
countries
in
Italy,
as
well
here
in
Milan,
and
we
had
at
least
in
2018
1
8
billion
of
passenger
boarded
and
64
million
of
total
booking
process
it,
which
is
our
pretty
big
values,
and
all
these
come
at
the
price.
The
price
is
the
complexity.
We
have
more
more
than
100
thousand
software
load
per
year,
which
is
pretty
big
because
in
any
other
there
are
360
days
and
a
lot
of
software
load
birthday
here
software
load
is
X,
should
be
considered
in
enlarged
way.
A
A
Okay,
I'm
a
deuce-
to
be
honest,
is
a
thirty
years
old
company.
So
I'm
not
going
to
do
the
story
of
all
this
just
try
to
keep
it
short,
but
everything
for
us,
at
least
in
from
the
cloud
starting
in
2014,
which
is
more
or
less
the
here
where
kubernetes
and
OpenShift
started
together
at
whisper
kubernetes.
A
It
was
the
summer
2014
and
we
signed
the
project
with
a
strategic
project
for
Intercontinental
Hotel
Group
in
us
when
they
asked
us
to
supply
the
new
infrastructure
for
from
the
reservation
system,
and
this
will
has
been
done
in
the
cloud
and
we
were
looking
for
a
partner
for
for
the
cloud.
We
spoke
with
multiple
people
with
a
lot
of
brave
corporates,
but
finally,
we
met
Reddit
and
after
a
travel
that
I
did
with
other
colleague
to
riling
in
us.
A
A
We
started
we
entered
in
the
in
in
the
real
release
of
workmanship
3.0
and
one
year
later,
we
managed
to
win
on
the
road
at
cloud
innovator
price,
which
is
always
something
that
is
still
considered
an
that
value
for
a
cinema
use.
People
could
keep
to
recall
me
this
fact
and
for
the
future
I'm
going
to
speak
about
the
put
the
Nexen
from
the
in
the
name
in
the
next
slide.
A
Okay,
let's
start
to
speak
about
what
the
deals
in
the
community
a
Madhu's
is
an
extremely
strong,
the
culture,
the
corporate
culture
in
a
Medusa,
extremely
strong,
a
lot
of
people
in
Arma
deals
that
are
start
to
be
old
now
season
or
always
work
it
only
for
a
medieval.
There
are
plenty
of
people
with
25
years
of
experience
that
stake
always
in
a
materials.
A
Now
today,
in
a
Madhu's,
it's
not
completely
finished
but
is
ongoing.
When
people
speak
about
the
service
now,
it
start
to
be
an
open
shift
to
our
kubernetes
service,
and
this
is
a
really
an
added
value
believe
me
because,
for
example,
the
culture
unification,
it
happens
across
regions
before
openshift
moving
it
moving
from
a
team
to
another
team
was
like
changing
a
job
inside
a
Mario's,
and
this
is
something
that
ok
we
can
cope
with,
but
the
reality
is
art.
A
So
people
spend
a
lot
of
time,
try
to
understand
just
the
jargon
between
teams,
division
and
so
on,
and
this
has
been
a
real
added
value
for,
for
us
I'm,
an
Indian
Madhu's.
Also,
since
the
culture
is
so
strong
before
openshift,
we,
we
never
considered
something
like
cannery
testing,
something
like
probably
not
not
cannery
test,
but
replication
replication.
The
replication
controller
rollback.
A
Those
kind
of
features
that
comes
automatically
with
OpenShift
adopting
or
fining
I,
don't
know,
I
know
you're
you're
skilled,
but
these
are
basic
use
case
in
kubernetes
and
OpenShift,
and
now
people
in
the
Madhu's
always
peace
about
adopting
the
part
which
is
crazy
from
all
these
years,
all
these
years
in
in
the
distributed
computing.
Whenever
people
talk
about
this,
and
now
it
happens,
this
is
thank
you
to
the
adoption
of
a
pen
shift
and,
more
than
that
now
we
start
to
rethink
about
internal
practices.
A
Now
it
happens
often
that
people
are
asking
for
probe
liveness,
probe
readiness
probe,
and
we
spent
a
lot
of
time
just
work
around
this
problem.
The
fact
that
we
didn't
have
a
probe
has
been
a
problem
has
been
a
problem
for
a
lot
of
time,
and
now
every
application
started
to
do
the
other
probe.
If
you
not
have
a
probe,
you
can
upload
and
so
on.
This
is
another
added
value
and
we
fundamentally
managed
to
rethink
our
internal
best
practices
again.
A
A
Somehow
we
also
gave
something
to
the
community.
One
of
my
colleague
helped
add
one
word
that
engineer:
Paul
Paul
Murray,
which
is
with
a
friend
to
to
design
a
secret,
the
actor
the
component
in
the
kubernetes
secrets,
which
are
fundamentally
openshift,
OpenShift
secret
since
we're
there.
Since
the
beginning.
We
also
did
some
bug
fixing
adding
some
tests
and
so
on,
just
simple
grant
job
and
workforce,
and
we
push
it,
for
example,
to
have
absorbability
observability.
The
initial
use
case
was
aving.
A
The
label
of
the
pod
expose
Edina
in
the
logs,
say:
ok,
I
have
this
part
that
is
going
to
run
on
under
these
labels,
for
example,
we
just
need
a
way
to
connect
the
pod
information,
the
pod
metadata
inside
the
application.
That's
the
reason
for
for
downward
API,
for
example,
I
personally
output
by
always
Palmeri
coded
downward
API,
or
at
least
I,
contributed
significantly
and
since
were
there
in
the
beginning.
Again,
we
spent
some
time
on
deploying
we
pushed
the
first
version.
A
Oblivion,
caress
and
I
was
being
deprecated
with
nice
and
we
had
several
contribution
to
pay
ship
decibel
for
the
open
sea,
flexible
github,
the,
but
the
contribution
that
we
have
that
we
are
pretty
proud
of
is
to
have
pushed
the
requirement
for
sheer
DS.
The
original
use
case
was
having
like
a
dag
workflow
for
in
kubernetes
natively
in
kubernetes
for
several
reason,
which
was
totally
understandable.
We
couldn't
have
that
and
at
the
time
and
brand
numbers
now
that
microsoft
pushed
the
GPR
third-party
resources.
A
If
people
in
the
room
and
pretty
young
to
kubernetes,
probably
we
will
never
heard
about
third-party
resources.
That's
fine!
But
before
customer
sources
there
were
tell
party
resources,
but
their
party
resources.
We
are
so
baguette
that
fundamentally
read
that
folks.
Now
the
guy
at
the
moment
is
no
more
a
tree
that
but
life
is
like
that.
A
Liggett
explained
me
kindly
that
there
were
no,
where
to
there
well,
no
way
to
build
the
really
a
workflow,
a
dag,
a
graph
of
job
using
PPR.
So
this
push
the
desert,
the
customer
resources
use
cases
which
has
been
implemented
by
another
editors
David.
It's
that's
I
greet
for
a
lot
of
for
his
contribution
that
has
been
huge
and
I
know.
You
know.
A
A
The
reason
that
Forcier
DS
is
that
at
the
beginning,
we
were
trying
to
create
a
were
flocking
to
the
workflow
operator
and
it's
called
controller
because
it
comes
from
an
area
from
from
an
age
where
the
word
the
word
operator
did
not
exist.
It
was
just
a
controller
because,
okay,
now
everyone
is
speaking
about
operators,
but
it's
just
an
extension
of
kubernetes
controller.
A
These
cannery
and
the
development,
the
the
load,
the
load
of
through
cannery,
and
it's
been
presented
at
the
cube
gun
in
Barcelona
DS
here,
and
we
have
other
operators
as
well,
which
are
not
open
sourcing
for
obvious
reason,
because
it
just
handle
internal
technology.
We
have
some,
for
example,
for
our
years,
be
in
the
software.
Bus
is
more
an
ingress
controller
than
an
operator,
but
anyway
we
are
doing
a
lot
of
stuff.
On
using
CDs
and
operators,
okay,
this
is
the
therapy
slide.
If
we
have
what
we
have
changed.
A
We
had
an
internal
knowledge
of
puppet
and
we
started
the
provisioning
infrastructure
using
puppet
then
using
terraform,
and
we
are
still
struggling
today.
For
with
this,
we
have
some
legacy
again
comes
from
the
fact
that
we
have
a
long
history
in
kubernetes
and
openshift,
and
is
that
I
don't
know
if
we
have
to
do
something
different,
but
at
least
we
have
to
share
our
use
cases
explain
why
why
we
had
to
do
do
some
strange
things
and
instead
we
did
not
do
that.
A
It
has
been
an
error,
not
the
implementations,
well,
dont
implementation,
really,
but
just
the
fact
that
we
had
to
speak
more
to
the
community.
Explain
the
problem
and
so
on,
and
for
that
openshift
for
for
us
is
bringing
the
hope
to
forget
all
this,
or
at
least
to
simply
slowly
the
commission.
The
octal
cluster
that
we
have
with
these
legacy
technology
and
we
are
still
waiting
for
that
and
other
things
that
I'm
sorry
to
say
that
I
know
that
updating
through
ansible
can
be
a
tough
experience.
A
A
A
So
we
had
the
same
reaction
and
we
decided
to
create
our
own
manifest
files,
which
has
been
probably
one
of
the
worst
error
that
we
live
in
and
we
are
still
struggling
with
that.
We
are
just
the
commissioning,
and
the
point
is
that
helmet
was
already
there.
I
met
the
first
time.
I
met
Matt
Helm.
It
was
at
the
first
cube
gun.
It
was
not
like
the
man
that
we
have
today
with
the
tiller
the
stuff,
but
but
we
decided
to
to
bet
on
ourself,
and
we
have
this
legacy
today.
A
Somehow,
following
the
the
the
previous
slide,
we
we
started
the
production
with
the
machine
3.0
at
the
time.
Prometheus
was
not
there
a
floor,
for
example,
for
logging
was
not
where
as
well
and
we
start
implementing
in
our
technology,
and
we
are
just
decommissioning
at
the
moment
we
struggling
on
struggling.
We,
you
have
some
bandwidth
that
is
taking
to
death
and
a
cultural
problem
that
we
had
is
the
fact
that
internally
in
a
module,
so
we
need
to
do
that
in
production.
Everything
must
be
fallback
everything
everything
insert
aligning
a
DB,
you
have.
A
A
A
This
is
a
cultural
problem
that
we
have.
Some
friction
that
we
have,
and
another
point
that
I
would
like
to
state
is
the
fact
that
working
with
open
source
for
a
corporate
that
is
like
us
is
something
that
we
have
to
learn
is
something
that
we
need.
Time
is
interesting
for
developers,
but
is
even
more
interesting
for
PM's
that
set
the
roadmaps
and
so
on,
with
the
budget,
and
so
on.
It
can
be
tough,
sometimes
can
be
developed.
A
A
It's
like
that,
and
the
final
point
again
okay
she's
for
for
brings
hopes-
is
the
cloud
provider
api's
for
a
lot
of
time.
People
keep
to
think,
keep
to
expose
this
metaphor
saying:
okay,
the
cloud
provider
is
the
new
platform
hardware
platform
and
kubernetes
or
OpenShift,
is
the
new
operating
system.
Okay.
This
is
a
way
to
see
the
things,
but
does
not
work
exactly
like
that,
in
the
sense
that
the
cloud
provider,
as
stated
in
previous
presentation,
are
all
different
and
the
concept
most
of
the
time
are
different.
A
A
A
In
the
next
future,
in
my
team
in
my
group,
we
are
seriously
looking
at
the
Federation.
We
are
seriously
looking
a
cluster
registry
which
unlikely
is
been
today,
but
we
have
plenty
of
cluster
all
over
the
world
and
we
start
to
have
we
start
to
need
the
yellow
pages
for
the
cluster.
We
were
looking
at
the
Federation
six
and
I
know
that
there
are
cluster
registry.
Probably
now
we
are,
we
are
deploying
a
cluster
register.
A
Internally
I
spoke
with
all
the
people
in
the
cloud
in
the
multi
cluster
in
a
multi
cluster
see
down
difficulty
inside,
but
anyway,
this
is
the
way.
This
is
the
things
we
are
working
on
and
we
are
start
to
working.
We
start
on
the
ready
to
work
on
up
and
shoot
for
on
AWS
NGC
as
well.
We
have
two
teams
that
work
on
this.
A
A
Since
we
were
used
to
build
our
cluster
inside
at
home,
we
are
seriously
looking
at
open.
Shoot
for
on
bare
metal
is
going
to
be
probably
starting
in
one
month
or
two
months
and
like
that
meant
for
2020,
you
will
learn
about.
You
will
learn
more
about
our
models
and
opposite
for
on
bare
metal,
sure
and
some
of
the
cloud
that
we
are
internally
and
luckily
not
only
on
reddit
OpenStack
bolts
on
other
other,
about
other
OpenStack
flavors.
We
have
some
project
on
up
a
ship
for
on
open
stacks
as
well.
A
A
We
are
waiting
also
the
reddit
reddit
roadmap.
That's
why
I
was
taking
the
picture,
but
anyway
we
have
weekly
contact
point
with
with
with
people
in
u.s..
So
we
are.
We
are
aware
most
of
the
things
I
know
I
cannot
say
on,
and
this
is
just
my
final
slide
just
to
tell
you
thanks
you.
Thank
you
really
I
appreciate
all
this
that
is
mine.
Matthias
is
hiring
like
every
cloud
company
we
need.
We
need
the
end
digits
and
some
fingers,
sorry
and
so
on.
A
Don't
hesitate
if
you're
looking
for
for
new
opportunities,
a
new
challenge.
There
are
some
that
are
really
challenging
and
on
the
right
column
there
are
the
people.
I
would
like
to
thanks.
Personally,
that
is
not
a
corporate
stuff.
That
is
my
because
are
all
the
people
that
tell
me
in
this
adventure
in
the
last
five
years,
always
like
all,
obviously
Clayton
Paul,
Dan,
director,
David,
Ethan
and
so
on.
Really
thank
you
thanks
again
Diane
and
Tonya
to
invite
me
here
all
right.
Well,
thank
you
very
much.