►
From YouTube: Experiencias al crear un operador usando Operator SDK y Ansible - Job Céspedes, Krestomatio
Description
El objetivo de la charla es compartir las principales experiencias al crear un operador que usa Operator SDK y Ansible para manejar instancias de Moodle (LMS) en Kubernetes. M4e-operator es el nombre del proyecto para este operador. Está disponible bajo licencia open source como repositorio en https://github.com/krestomatio/m4e-operator
La charla contiene un repaso breve de lo que es un operador. Se hablará también de las razones que motivaron la creación de este operador y las opciones existentes para hacerlo. Además se mencionará el diseño del operador y su estado respecto a las buenas prácticas. Y se incluirá la temática de las dificultades encontradas.
En la charla se cubrirán aspectos técnicos del Operator SDK, de Ansible y de Moodle. Esto incluye detalles como el ciclo de vida, las fases que abarca actualmente el operador y las dependencias. También se verán temas relacionados con plugins, roles y colecciones de Ansible, así como los componentes de Moodle de los que se encarga el operador.
Contacta a Job en:
- https://www.linkedin.com/in/jobcespedes
A
A
Good
afternoon,
everyone,
it's
a
pleasure
to
greet
you
and
I
hope
you
are
enjoying
that
you
have
enjoyed
this
day
that
is
already
today.
We
are
going
to
close
with
this
last
talk,
which
is
experiences
when
creating
an
operator
using
operator,
ethics
and
answer
and
is
in
charge
of
hobbes.
This
is
a
pleasure
to
have
you
here
with
us,
so
I
leave
you
the
time
so
that
you
can
give
lectures.
Thank
you
very
much.
B
May
greetings
to
all,
and
it
was
also
a
thank
you
for
Participate
in
this
talk.
I
begin
by
saying
that
I
am
a
little
nervous
but
more
excited
to
be
able
to
have
an
opportunity
to
share
experiences
that
we
have
gained
building
an
operator
and
somehow
try
to
make
life
easier
for
others
who
might
be
considering
it.
B
Very
well.
What
is
this
talk
about
in
a
general
way?
The
talk
has
a
review
of
what
a
cv
operator.
Is.
Vernet
also
mentions
the
reasons
that
led
to
the
creation
of
one
in
In
particular
and
the
existing
options
that
were
considered,.
It
also
mentions
what
the
design
of
this
operator
is,
its
status
regarding
good
practices
and
the
challenges
we
have
encountered
while
developing
the
operator
more
specifically,.
B
B
An
operator
shares
important
concepts
of
hornets
and
it
is
part
of
the
benefits.
It
has
a
controller
that
helps
to
encapsulate
an
application
as
an
object
and
even
the
logic
to
maintain
a
desired
state
of
the
application
defined
as
part
of
the
specification
of
that
object.
It
does
this
over
and
over
again
in
a
periodic
reconciliation
cycle
that
arises
from
events
reported
to
it
by
an
observer.
This
is
known
as
a
level
based
state
keeping.
The
controller
does
not
need
to
track
the
history
of
the
object.
B
Going
back-
and
there
are
again
apologies
for
the
intersection
of
slides
and
the
introduction
of
the
module
as
architecture
shares,
one
of
a
well-
known
traditional
application
with
other
similar
applications.
A
web
server,
the
application
code,
the
database
and
a
file
system
that
also
in
mosul
is
called
the
data
to
scale
a
module
architecture,.
B
What
is
the
m4
or
pereiro,
because,
obviously,
at
this
point
they
will
know
that
it
is
a
mobile
operator.
So
vernet
is
that
it
uses
the
trainer
or
pereiro
sdk
to
the
second.
To
do
it.
It
is
open
source,,
it
is
publicly
accessible,
and
at
that
moment
it
is
an
alpha
version,,
so
it
can
be,,
which
is
why
it
is
constantly
changing
and
evolving.
B
B
B
B
State
that
we
had
at
the
level
that
we
had
reached
is
these
questions
went
by
asking
us
what.
Yes.
It
was
simple
that
this
automation
could
be
sustained
independently
of
a
clip,
a
specialized
group
of
people
that
if
it
was
easy
and
reuse,
this
automation
by
others
who
had
similar
use
cases
and
that
if
it
was
easy,
also
to
maintain
and
improve
using
distributed
groups
or.
B
B
Because
coherently,
it
offered
us
a
standardization
so
that,
in
the
automation
that
we
achieved,
it
could
be
understood
using
known
and
used
concepts
and
also
tested
by
many
people,
so
that
it
was
easily
reusable
within
a
larger
environment
such
as
square
nets,
and
its
community
also
offered
us
the
api,,
the
extension
of
the
api
together
with
the
system
to
mature,
and
also
that
it
allows
some
innovation.
Despite
having
that
maturity,.
B
B
It
was
to
review
the
notes
and
even
the
operator.
Sorry,,
the
operator.
Yes,.
That
is
a
framework
that
seeks
to
facilitate
the
development,
maintenance
and
publication
of
operators,
for
which
Vernet
offers
three
options
to
do
it.
The
first
is
with
go
the
programming
language.
The
second
is
to
take
the
tool
that
you
probably
know
to
manage
coherent
applications
and
thus
the
automation
engine
that
we
have
been
talking
about
and
what
I
imagine
many
know.
B
This
framework
defines
5
levels
of
capacity
and
I
would
like
to
mention
them
because
later
they
are
going
to
be
important
to
know
them,
at
least
to
obtain
knowledge
that
they
exist
and
those
levels
are
mentioned
briefly,
but
in
the
documentation
you
can
find
more
detail.
The
first
is
a
basic
installation.
B
B
I
would
also
like
to
mention
that
there
are
alternatives
for
this
framework.
You
could
not
use
it
at
all
and
build
an
operator
using
different
programming
languages
and
the
particular
or
specific
clients
of
cuber
net
is
available
in
the
community,
for
example,
there
is
a
client
for
tom
pay.
There
is
a
client
for
ccoo.
There
is
a
client
that
would
also
be
an
option.
Another
option
is
to
use
another
framework
for
python.
B
B
B
Well,
if
we
go
to
this
slide
of
what
technical
challenges
we
have
faced
in
the
development
of
the
operator-
and
there
are
several
many
in
this
time
that
we
have
been
working
and
I-
have
tried
to
compile
at
least
the
most
relevant.
For
this
talk,
perhaps
not
in
an
order
of
complexity,
although
the
ones
that
one
remembers
the
most
are
the
most
complicated
but
but
I
would
like
Let's
share,.
Let's
see
if
I
get
along,
in
no
order,.
B
B
Very
well.,
The
first
point
was
a
challenge
about
the
things
we
had
to
learn
to
make
you
honest,
and
we
started
learning
both
the
framework
and
Q
Vernet,
because
our
experience
was
there
and
other
types
of
9
managers
like
OpenStack.
and
web
bean,
and
when
doing
an
analysis
that
coherents
could
serve
us
for
what
we
needed
we
went
over
and
at
once
we
began
to
learn
both
the
framework
and
coherents,
and
this
leads
to
the
second
challenge
that
we
found
was
an
overlap
between
the
capabilities
of
adhesives
and
rockets.
B
Due
to
the
bias
of
our
experience
when
thinking
about
the
orchestration
of
moodle,
many
component
components
were
thought
based
on
eagerness
and
the
ability
that
the
civilian
has
to
orchestrate
and
the
features
and
plugins
and
so
on,
and
this
ability
sometimes
overlaps
with
what
what
vernet
does
is
that
it
also
does
orchestration,
and
we
began
to
see
that
this
generated
one
of
three
situations:,
the
first,
that
we
could
do
the
same
thing
in
the
way
that
we
did
it.
That
makes
it
old
in
the
way
that
it
does
or
in
the
way
that
it
does.
B
Q
vernet
is,
and
either
of
the
two
was
fine.
We
could
do
it,
but
such
a
situation
that
could
be
generated
is
that
the
anti-
patterns
or
anti-parents
recommended
to
us
would
appear
because
in
Annecy
Ball
it
could
be
done
in
a
certain
way,
but
in
Hoover
Net
it
is.
If
we
did,
it,
It
worked
that
way,
but
it
wasn't
recommended,.
B
Maybe
it
was
against
some
guide
that
goes
around
about
bunions
that
are
quite
important
and
that
help
to
understand
the
concepts
behind
turbinates
and
a
third
situation
that
we
saw
is
that
there
are
also
things
that
they
could
not
be
done
in
q
ver
nets.
They
could
be
done
with
our
experience
in
action,
and
this
allows
us
to
somehow
extend
the
functionality
of
cv.
Vernet
is
with
function
with
things
that
are
not
available
right
now
and
not
actively,
and
I
am
going
to
give
two
examples
here
of
what.
B
The
first
example
is
regarding
the
network
configuration
and
she
wolf,
facilitates
and
offers
modules
to
do
this
configuration,.
However,
it
does
not
coincide
with
a
reason
for
him
or
a
situation
in
which
we
have
to
use
the
civilian
in
the
framework
to
do
any
network
configuration
because
take
me
test
takes
care
of
all
that
configuration.
B
However,
if
the
specific
case
is
that
we
need
to
mount
it
in
a
folder
where
the
application
is
also
from
the
code
of
the
application,
the
possibilities
of
strong
cornet
that
gives
us
40
are
reduced.
It
allows
us
to
do.
It
allows
us
to
mount
there,
for
example
with
fit
php
with
our
configuration
and
if
the
specification
of
the
object
that
represents
the
application
changes,
this
configuration
changes.
B
Rulers
does
not
allow
to
keep
that
change
without
us
having
to
trace,
apply,
let's
say
a
hatch
to
each
confirm
so
that
the
pod
is
regenerated
and
reloads
this
new
document,
but
in
this
new
file
instead
with
file,
we
can
make
use
of
what
I
already
mentioned,
to
maintain
a
file.
Template
configuration,,
connect
to
the
pot
and
compare
in
a
single
task.
B
If
the
correct
version
is
present,,
if
it
is,
not,
apply
the
change
without
the
need
to
regenerate
the
pod-
and
this
is
an
example,
I
consider,
of
something
that
could
extend
the
functionality
of
cuber
net
is
when
It
is
not
offered,.
Perhaps
it
could
be
thought
good
and
coherent,.
It
will
be
that
you
need
such
functionality
natively,,
but
I
think
that
it
is
not
part
of
the
scope
of
this
presentation,.
B
Always
at
this
point
of
ancient
verses,,
the
rulers,,
we
begin
to
represent
the
application
using
the
concepts.
depressing
before,,
but
there
are
volume
klein
services
in
English,
among
others,,
and
we
soon
saw
that
we
were
limiting
ourselves
to
using
the
web
in
this
way,.
Only
to
define
dynamic
template
templates,.
B
Not
as
much
as
we
had
thought
before
to
make
use
of
the
community
plugins
of
the
roles
beyond
of
the
collection
of
rulers
for
the
civilian,
which
is
the
if
we
use
it
a
lot,
then
one
of
our
initial
considerations
that
we
wanted
to
do
it
because
there
was
a
large
and
broad
ecosystem
and
many
tools
and
we
started
to
rethink
it
and
because
we
weren't
really
making
as
much
use
anymore
of
those
options
that
acid
offered
us
at
another
point.
Moving
on
to
other
very
important
points
of
challenges
that
we
faced
was
operator.
B
B
Now
I
am
looking
for
solutions
for
this
problem.
We
found
that
the
community
has
started
to
work
on
this,
in
particular
with
them
several
articles,
they
have
published,
say
they
point
out
that
every
time
an
annecy
based
operator
interacts
with
it.
There
is
still
an
overhead
of
2
seconds
for
that
task,
and
this
happens
because
in
that
task,
The
dependencies
of
the
module
that
is
being
used
have
to
be
loaded,.
It
has
to
be
authenticated
against
horn
test
and
then
whatever
we
declare
in
that
task
is
executed,.
B
It
is
only
one
because
it
says
with
two
more
seconds,
but
they
are
already
like
in
our
case
about
40
performance
suffers
and
something
needs
to
be
done
about
this.
The
community
has
started
to
suggest
some
things
in
particular
I'm
going
to
mention
two.
The
first
is
to
try
to
work
the
calls
that
are
made
to
pencil
within
the.
B
First,
steps
of
loading,
the
dependencies
and
authenticating
that
cache
to
a
service
that
is
running
and
for
a
while
and
all
subsequent
tasks
use
this
this
service
so
that
they
don't
I
have
to
do
it
for
each
task..
The
truth
is
that
we
have
seen
that
we
are
optimistic
with
this
archiving
mode,,
although
they
are
prior,
because
we
have
seen
how
we
went
from
50
seconds
to
20
while
maintaining
the
43
tasks,
and
we
can
still
download
more
because
we
are
barely
doing
it.
using
for
the
modules
of
annecy
wall.
B
A
B
B
The
framework
documentation
facilitates
these
updates
because
it
publishes
in
each
new
version,
which
ones
These
are
the
changes
for
each
type
of
the
operator,.
So
if
it
is
as
civil
as
here
or
later,,
then
one
can
follow
these
changes
and
apply
them
to
update
to
a
new
version
of
the
framework
and
a
hack
that
we
use
is
to
generate
a
version
of
the
operator,
and
it
will
to
be
only
with
the
respective
apis
in
a
certain
version.
We
keep
it
there.
B
We
do
not
modify
it
anymore
and
when
there
is
a
new
version,
we
do
the
same.
We
compare
both
folders
and
the
result
is
the
modifications
that
exist
between
each
one
in
a
dif
file
format
and
This,
in
some
way,
makes
it
easier
for
us,
however,.
It
is
a
bit
tricky,
in
any
case,
to
the
tests
of
the
operator,.
It
is
another
of
the
challenges.
The
auto-generated
framework
facilitates
the
auto-generation
of
molecular
molecule.
Contexts.
They
are
themselves
also
a
framework
for
do
reaction
tests.
B
This
these
contexts
and
autogenerated
one
is
to
test
it
against
a
coherent
cluster
and
another
to
play
it
against
cain,
which
is
a
cluster
in
a
container,
and
somehow
this
facilitates
the
tests
of
a
crave
based
operator.
However,
over
time
and
already
having
several
operators
see
if
the
configuration
of
the
molecule
mode
for
us
has
changed
a
lot
with
respect
to
that
autogenerated,
so
we
have
decided
to
remove
it
from
the
operators
as
a
git
sub
module
and
keep
it
apart
so
that
it
can
be
shared
by
them.
B
B
Also,
the
framework
in
terms
of
tests
provided
make
file
with
certain
objectives
or
targets
and
in
which,
with
a
single
command,
one
can
instruct
using
make
the
make
command
is
executed,
for
example,
the
god
of
the
construction
of
the
image
and
publishing
the
operator,
among
other
things,,
but
also
with
time,.
We
have
seen
that
it
has
evolved
and
we
are
now
releasing
its
own
repository
so
that
various
operators
in
Asia
can
share
it
in
terms
of
debugging.
The
operator,
since.
B
However,
this
is
not
very
efficient
in
time,
even
though,
when
they
keep
us,
it
allows
us
to
see
the
majority
of
errors,
because
it
takes
a
long,
long
time
to
be
there
waiting
for
it
to
complete
In
all
these
steps,,
that
is
to
say,.
We
have
not
found
the
most
efficient
way
in
time
to
divert
and
we
are
still
adding
messages
in
the
blue
templates
that
say
here
we
go
1.
B
Another
point
is
the
most
dynamic
inventory
of
Annecy
lung
when
jumping
some
could
be
left
for
later.
If
someone
wants,
you
can
contact
me
with
pleasure
that
point
to
finish
with
this:
the
dynamic
inventory
of
files
we
needed
within
the
operator
to
execute
commands
in
the
pots
generated
by
the
investment
cost.
B
So
we
began
to
see
alternatives.
The
collection
of
turbinates
to
thus
bol.
It
has
an
inventory
plugin
for
q
vernet
es,
but
it
is
not
integrated
with
the
operator.
This
means
we
had
to
do
something
or
at
least
consider
making
our
own
li
plugin,
not
extending
it,
and
that
is
what
we
did.
We
added
a
plugin,
and
this
plugin
allows
us
that,
at
the
beginning
of
each
reconciliation,
cycle,,
the
inventory
of
posts
is
dynamically
generated
and
their
status
groups
them
so
that
we
can
access
the
posts
that
are
ready
or
those
that
are
not
ready.
B
B
B
A
The
truth
is
that
it
is
a
pleasure
to
listen
to
your
talk,
and
it
is
always
very
important
that
we
can
have
these
experiences,
and
the
truth
is
that
you
will
share
the
challenges
you
had
with
us.
It
can
be
of
use
to
us
later
on.
We
do
not
know
what
will
happen
to
us,
It's
time
to
face
in
the
future,.
So
thank
you
very
much,.
We
really
don't
have
any
questions
in
the
chat,,
but
I
congratulate
you
and
thank
you
for
an
excellent
closing
with
this
conference,
and
I.
B
B
A
Excellent
good,
we
already
have
comments
from
jefferson,
he
says
good
talk
and
we
also
have
applause.
So
thank
you
very
much
and
I
want
to
remind
everyone
that
right
now
we
are
going
to
make
a
change
of
track
for
the
closing
words,,
but
at
the
end,
well,
we
are
going
to
have
the
concert
that
we
have
been
waiting
for
so
much,
a
thousand
to
see
you,
so
I
invite
you
to
tune
in,.
It
is
a
Chapina
band,.