►
From YouTube: GitOps, fomentando equipos de operaciones de próxima generación - William Caban, Red Hat
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
A
Good
morning,
everyone
it's
a
pleasure
for
us
that
you
continue
to
tune
us
in
which
to
see
does
not
discriminate
and
this
time
in
professional
edition.
Thank
you
very
much
for
being
here.
On
this
occasion,
I
have
the
nice
to
introduce
our
next
guest
speaker,
william
cavani.
It's
a
pleasure
for
me
in
time.
It's
all
study.
Thank
you.
B
Let's
see,
we
want
to
go
apps
as
we
started,
we're
going
to
start
by
looking
at
the
promises
of
twists
with
twists.
What
we
see
is
that
we
have
the
promises
that
our
models
or
deployments
are
going
to
be
consistent,
that
we're
going
to
have
ongoing
remediation
that
the
tools
we
use
for
him
and
dobbs
are
going
away
to
take
care
of
remedying
any
deviations
from
the
model
of
what
was
desired.
B
B
I
have
your
model
that
moves
very
fast,
but
how
can
I
really
maintain
the
security
policies
that
the
company
does
not
require
and
from
there
the
next
question
is
usually
hey,
but
with
all
this
moving
so
fast,
and
all
this
of
this
such
an
agile
way
that
it
really
is
a
backup,
as
it
really
becomes
rich
to
see
and
in
this.
So
all
this
enters
and
begins
to
shock
these
operational
groups
and,
above
all,
there
is
something
very
important,
and
it
is
the
people
in
the
operational
groups.
B
B
That
the
staff
that
is
attached
to
more
traditional
models
or
that
does
not
provide
that-
does
not
come
from
a
normal
development
model.
How
can
we
make
it
easier
for
them,
so
we
have
to
find
a
way
to
get
from
the
reality
in
which
we
live
to
this
model
of
the
goals
that
we're
looking
and
that
's
not
just
adopting
a
tool
or
adopting
the
new
tool
that
came
out
to
do
spins
and
it's
already
started.
B
B
For
this,
we
have
to
recognize
that
the
practices,,
the
paradigms
and
the
platforms
that
have
occurred
in
the
past
10
20
years
and
that
have
come
to
us
have
led
us
here
to
this
moment
they
are
not
abandoned.
All
those
are
parts.
They
are
simple
parts
that
we
have
to
integrate
to
the
quirós
models
for
them,.
Let's
see
in
more
detail
how
each
of
the
patterns
that
some
of
them
developed
as
they
integrate
algids.
B
To
understand
this,
if
we
look
from
the
perspective
of
the
operating
groups
in
a
company,,
especially
when
we
focus
on
the
Day
2
of
operations,
we
have
a
pattern
where,
at
one
point,
we
started
adopting
what
was
basic
automation,.
Then
the
orchestration
evolved
from
there
and
there
were
several
developments
in
the
industry,
for
example,,
seeing
the
infrastructure
as
a
code
or
over
or
adopting
what
is
known
as
self
organizing
networks
and
there
also
in
parallel
to
all
this.
B
B
Let's
see
how
each
of
these
patterns
really
form
the
basis
of
what
is
guided
when
we
look
configuration
as
code,
which
was
possibly
one
of
the
first
iterations
that
there
was.
What
we
see
is
that
here
everything
was
focused
on
keeping
the
configuration
files
in
a
repository.
It
could
be
a
centralized
repository,
but
the
important
thing
was
that
it
was
a
repository
where
those
configurations
were
tied
to
one
version.
B
That's
how
configuration
scout
started
this
quickly
evolved
and
it
takes
us
and
it
took
us
to
code
infrastructures
or
have
the
infrastructure
represented
as
a
code
that
also
adopts
the
part
of
it
of
using,
let's
say
gates
or
version
system
to
represent
what
we
want
in
the
infrastructure.
How
were
the
brute
machines,
as
they
were,
The
network
infrastructure
balances
them
like
the
servers,,
the
comparisons
for
them,,
how
the
firmware
works,?
B
Soft
radios
in
mobile
radio
access
networks
are
the
cellular
networks.
These
are
the
networks
that
They
handle
the
part
of
how
an
antenna,
for
example,
is
configured
and
not
only
how
the
antenna
is
configured,,
but
this
model
began
and
brings
the
idea
of
cels
configuration
self
optimization,.
What
does
this
mean,?
These
models
that
started
again
in
the
radio
industry
for
For
example,,
the
mobile
devices
look
at
the
frequencies
at
how
much
noise
they
are
seeing
at
certain
frequencies
and
they
make
dynamic
adjustments
or
based
on
the
environmental
temperatures
that
they
were
registering,.
B
They
saw
how
that
affected
the
services,
and
in
this
way
they
look
at
the
temperature
forecasts
or
from
the
environment
in
the
next
few
days
and
based
on
that
they
do
proactive,
fixes
or
proactive
configurations
by
modifying
the
radios.
That's
the
idea
of
the
sound
or
you
want
ford
galaxi
network.
Then
it
evolved,
and
companies
like
universe,
cisco
and
others.
Bring
it
to
enterprise
networks
and
This
is
how
many
of
these
models
reach
the
enterprise
networks.
B
B
There
is
a
philosophy
that,
by
its
acronym
In
English,
it
is
called
o
count
or
trans,
where
that
has
that
these
are
the
acronyms
for
what
is
known
as
culture
automation.
Culture
is
because
the
box
focuses
on
how
interaction
occurs
within
an
organization.
It
is
this
cultural
revolution
where
there
is
no
longer
childs
within
the
organization,
and
it
seeks
to
break
that
and
it
seeks
more
collaboration
from
you
also
to
adopt
the
automation
models
for
everything
in
the
box.
It
seeks
no
manual
steps.
B
What
it
seeks
is
that
everything
has
an
automation
associated
to
itself
with
the
boss,.
The
link
models
are
sought,
in
other
words,.
They
seek
to
eliminate
and
all
that
unnecessary
steps
to
make
a
decision,.
So
much
more
agile
models
are
sought
for
decision-making,,
but
the
decisions
are
not
made
because
someone
had
an
idea,.
If
not
It
seeks
that
everything
has
a
measure
associated
with
it,.
If
it
is
exceeded,,
it
seeks
to
measure
all
user
interactions,.
Optimization
is
that
it
has
occurred,
and
that
is
what
is
used
to
provide
feedback
and
optimize.
The
part.
B
Of
the
organization,,
the
part
of
you
and
all
these
knowledge
is
shared
in
the
box
with
all
this,
because,
as
it
is
a
framework,
it
is
not
a
framework
tool
because
this,
as
a
result,
manages
to
provide
a
structure
for
those
groups
that
are
initially
developing
that
were
looking
for
a
methodology
or
have
a
path
to
follow.
To
achieve
the
adoption
of
modern
methodologies,,
then
the
box
provides
that
I
must
adopt.
B
If
there
is
thirst
and
pipelines
for
everyone,
and
in
fact
it
is
you
who
brings
the
idea
of
whether
there
is
thirst
and
pipelines
for
any
process
within
an
organization.
What
was
seen
before,
such
as
workflows
or
flows
that
were
made
for
business,
etc.,,
the
jedi
for
klein
begin
to
take
a
large
part
of
those
roles,
from
there.
It
is
created,
or
you
generate
two
new
roles
in
an
organization,.
B
We
usually
see
the
reliable
site
of
engineers
that,
in
that
ere
by
its
acronym
In
English,,
it
is
the
role
that
is
he
who
really
implements
and
maintains
balls
for
the
infrastructure
and
operations
part
of
an
organization,,
and
there
is
also
a
second
role.
That
is
that
of
the
box
engineer,,
which
is
the
person
or
group
already
doing
what
same
maintaining.
B
In
parallel
and
once
that
began
to
have
a
boom
and
began
to
look
at
the
nettops,
in
fact,
returning
here
in
second
verse
cops
is
that
the
security
part
had
been
totally
abandoned
and
left
to
the
end,.
So
the
industry
is
looking
for
it,.
So
for
the
moment
it
is
decided
on
security,.
It
has
to
be
seen
beforehand,.
So
that
is
what
is
called
mobile
security
to
the
life,.
It
is
that
It
has
to
be
more
integrated
from
the
beginning
in
all
of
this,.
So
that's
where
dry
tests
come
from.
B
So
the
idea
of
we
are
going
to
use
airlines
to
create
automation,
begins
to
develop
of
the
networks
to
create
the
network
deployments,
the
network
configurations,.
So
this
is
when
we
begin
to
see
which
code
infrastructures,
evolve,
coninsa,
adds
pipelines,
and
that's
where
the
crestor
crash
course
begins,,
which
was
already
a
methodology
to
then
adapt
it
to
the
box.
Models
to
Real
events
occur
there
net
de
box
defne
box,
and
there
is
a
model
that
is
continuous
deployment.
B
B
Therefore,
For
example,
at
other
times
in
my
professional
life
that
I
have
worked
on
these
concepts,.
What
was
done
was
that
simulated
networks
were
made
where
all
the
configurations
that
were
going
to
be
applied
were
tested,.
It
was
verified
that
everything
at
the
operating
level
was
going
to
be
consistent
before
take
production.
Now,
once
it
was
approved
there,
it
is,
or
it
was
automatic
and
clutch
to
the
production
model.
B
This
is
this
difference,
or
this
is
going
to
be
something
that
is
going
to
be
different
with
diego.
We
are
going
to
see
that
here
in
the
box.
Initially,
we
must
was
all
of
Once
I
got
to
the
duty
continuum
model
and
in
the
continuum
part
of
the
book
there
is
someone
who
approved
it
and
it
went
to
production,
it
was
pushed
to
production
or
it
went
directly
if
it
would
be
a
series
of
tests
and
it
is
to
be
pushed
to
productions.
B
Well,
all
these
models
In
the
end,.
They
have
been
really
promoted
or
have
been
as
a
result
of
having
to
support
the
software
development.
Models.
Those
models
of
the
development
cycle
initially
were
only
there
are
then
box
entries
where
we
have
the
infinite
cycle
of
deployment,
monitor,,
test,,
use
and
continue,,
but
that
is
not.
It
has
ended
there.
B
How
can
you
really
test
how
you
can
make
a
model
that
is
so
flexible
that
it
can
evolve
over
time
and
not
be
something
that
was
done
today
and
to
make
a
change,?
It
requires
Now
that
everything
is
new,,
so
that
has
not
changed,.
It
has
been
evolving,
up
to
you
and
the
models,
any
new
model,.
How
will
it
revolutionize
the
one
that
is
coming,?
So
all
this
infrastructure
is
cloud
de
box,.
It
was
Quirós,.
This
is
going
to
continue
evolving,.
This
is
not
stops
now.
B
Today
we
are
talking
about
the
box
and
quirós
where
we
see
how
it
gets
here.
But
let's
see
then
that
it
really
is
that
the
turns
are
four
principles
and
they
are
basic.
They
are
easy
to
understand,
not
necessarily
that
means
that
they
are
equally
easy
to
adopt.
So
the
as
the
four
principles
that
we
see
here
are
it
is
declarative,
and
that
is
very
similar
to
what
we
saw
in
configuration
us
code
or
what
we
saw
in
scout
infrastructure.
B
They
are
versioned,
but
a
version
is
immutable.
So
let's
say
we
have
version
number
5.
This
version
number
5
can
no
longer
be
changed
without
any
change
applied
to
it,
generating
or
creating
or
defining
a
new
version,
so
version
5.
If
someone
made
a
change
already
becomes
version,
6,
789,
etc.
that
means
that
now,
as
a
group
of
operations,
when
we
know
that
version
5
is
the
correct
version
that
should
be
in
development
or
the
one
that
works
for
us
and
some
changes
were
made
and
it
is
known
that
it
was
version
5,.
B
Then
you
can
go
back
to
that
version
5,
because
it
is
known
that
everything
that
it
worked
there
is
what
is
contemplated.
There
are
no
changes,
so
there
is
no
way.
Someone
makes
a
change
and
now
version
5
does
not
work
and
that
no
longer
occurs
in
the
quirós
model,
something
that
is
begins
to
do
something
different
in
the
part
in
point
number
3,
where
it
is
a
model
in
the
box.
Well,
net
of
ops.
B
B
When
there
are
systems
that
are
disconnected
from
the
moment,
the
event
is
generated
to
let's
say
get
skinned
in.
Let's
say
there
was
a
disconnection
there
that,
yes
in
many
of
the
implantations,
it
was
lost
so
over
time
it
could
It
happened
that
what
was
thought
to
be
what
was
in
production
was
not
what
was
in
production,
because
that
puig
had
been
lost,,
those
that
generation
of
events
have
been
changing
and
their
voice
now,
well,,
not
only
in
the
event,
but
also
in
what
they
try
to
do.
B
These
tools
proactively
seek
to
see
that
they
are
in
the
correct
version,
but
in
Quirós
they
say.
Ok,
it
is
that
source
of
what
the
desired
state
is.
I
am
not
going
to
wait
to
receive
an
event,
I
am
going
to
be
proactively
verifying
that
the
desired
state
is
that
I
have
here
in
my
tool
as
the
state
that
the
system
needs
to
be
so
I
am
not
going
to
be
waiting
to
receive
an
event
if
I
can
have
I
can
receive
events
to
speed
it
up.
B
But
the
important
thing
is
that
I
am
like
in
the
quirós
walk
tool
and
the
controls
that
we
go.
Let's
see
a
minute
I'm
doing
that,
verification
that
validation
continuously
and
I'm
talking
and
comparing
what
is
already
there
and
number
4,
which
is
the
main
point
that
you
bring
up
Guido,
is
different
from
the
others
that
it
is
a
continuous
reconciliation
in
turns
it
does
not
depend
on
what
someone
wants
to
do.
A
validation
in
turns
that
reconciliation
or
remediation
is
happening
continuously,
observe
the
system
and
make
the
corresponding
remediations
this
continuous
reconciliation.
B
B
This,
is
the
way
I
do
this
mapping
and,
as
you
see,
numbers
2
and
3,
we
can
tie
it
to
models
that
already
existed.
Number
4
is
one
of
what
is
usually
unique.
The
kid
ops
is
is
an
essential
principle
of
quirós,
and
when
we
talk
about
principle,
it
means
that,
if
you
are
not
following
all
this,
you
are
not
making
turns.
You
can
be
using
tools
that
you
can
also
use
for
quirós.
But
if
you
are
not
doing
each
of
these
four,
you
are
not
doing
giffords.
B
The.
Other
thing
is
that
it
also
frees
up
the
scalability
that
we
achieve
in
our
systems
to
be
tied
to
what
you
can
really
do
a
tool
really
now
how
we
can
define
the
scalability
and
what
the
tool
a
particular
tool
manages
to
do.
We
can
keep
it
separate
and
number
3
in
the
part
of
once
we
have
these
chirós
patterns
as
well
as
new
ones,
because
new
models
are
going
to
keep
coming
out
to
keep
coming
up
with
new
ideas.
Every
time
something
comes
out,,
a
new
innovation
occurs,
we
can
adapt.
B
B
What
happens
with
twists
is
that
if
we
go
completely
to
the
right
side
here
is
the
integration
part
in
the
integrations
part
that
jobs
does
not
assume
that
we
are
going
to
replace
everything?
On
the
contrary,
videos
are
the
principles
are
designed
to
be
able
to
reuse
all
this
evolution,
and
all
this
that
is
happening
in
the
market,
in
other
words,.
We
are
building
on
models
that
have
already
been
tested,.
What
we
are
doing
is
creating
new
patterns
that
we
know
can
lead
to
scaling
all
of
this
in
the
security
part,.
B
Something
very
attractive
in
the
guido
part
is
that
what
a
version
is
is
immutable.
That
is
the
ideal
dream
of
any
security
group.
If
you
mean
that
version
20,
21,
11
27,
is
this.
That
is
not
going
to
change
over
time.
There
is
no
way
to
modify
them
if
it
is
automatically
modified.
There
is
a
new
version
created
so
that
part
of
The
version
change,
except
it's
very
powerful.
B
B
With
all
this,
we
talked
about
those
principles
are
that
they
are
adopted
for
turns,
but
then,
if
it
is
not
a
tool,
what
logical
characteristics
must
have
a
tool
or
a
process
to
be
able
to
call
it
killers,
and
the
first
is
the
idea
of
.
The
kirov
is
control.
The
idea
of
aguirre
controller
is
that
again,
everything
is
in
a
system
of
aversion
to
mento.
For
the
purposes
of
this
talk,
I
am
going
to
talk
about
kit,
but
it
is
any
version
system
to
mento
that
can
comply
with
and
force
the
principles
followed
there.
B
The
intention
is
described.
What
is
desired
is
this
is
the
desire
state
what
the
controls
are,
those
tools
of
a
close
loop
automation
that
can
take
that
information
and
run
a
reconciliation
cycle,
look
at
the
results
and
they
are
continuously
maintained,
doing
these
mediations.
This
is
what
I
call
a
turn
of
control.
Again
we
have.
B
This
is
the
source
of
this
is
the
truth.
What
you
want
to
have,
and
then
there
is
an
ongoing
remediation.
This
is
not
a
single
tool,
necessarily
that
we
are
going
to
see
in
a
moment,
but
the
idea
is
that
this
loop,
that
again
you
don't
look
at,
is
not
tied
to
a
tool.
It's
a
pattern.
Once
we
have
this
plate,
we
can
say:
ok,
we
have
a
video
controller.
B
That
is
used
for
this
is
also,
for
example,
once
it
happens,.
It
is
clear
if
we
have
a
pipeline
that
is
in
charge
of
automatically,,
let's
say,
deploy,.
Do
that
orchestration,
measure
that
and
based
on
those
measurements
and
go
automatically
remediate,
well,.
If
we
can
access
the
plan
that
we
can
use
for
the
ines
to
implement
the
kilos
part
or
we
can
use
specialized
tools.
B
Specialized
closed
loops
for
the
behavior
of
the
bass
control,
so
all
this
is
this
is
what
is
used
to
do
this
part
of
the
turns
now,
with
these
of
of
the
He
cited
closed,
contrary
to
a
past,
where
an
orchestration
tool
sought
to
tell
the
object
that
it
was
being
handled,
exactly,
go
and
change
this
king
value.
That
indicated
and
prescribed
all
the
steps
to
follow
jobs,
break
that
and
what
it
says
is
no.
No
us
we
describe
what
it
is
that
we
really
want
to
have
there
and
you
are
stop.
B
Quiroz
controllers
are
the
ones
that
are
going
to
remedy
and
reconcile
even
that
towards
that.
This
also
means
that
we
can
look
at
it,
as
there
are
many
specific
domain
orchestrators,
for
example,
the
easiest
way
to
see
this
is,
if
we
think
about
what
vernet
is
what
bernardis.
When
we
have
let's
say
sinking,
we
have
a
set
replica
and
we
have
there
information
regarding
the
number
of
aftershocks
that,
for
certain
is
going
to
have.
We
don't
tell
him
how
to
create
those
replicas.
B
What
we
say
is
me:
I
want
to
have
three
replicas
and
it's
a
closed
loop,.
This
controller
is
going,.
The
only
thing
it
knows
is
that
there
are
how
many
replicas,
in
fear
of
how
many
replicas
there
are,,
how
many
replicas
there
must
be
and
converge
towards
that,,
but
on
top
of
that,
well,
there
are
others,
for
example,.
I
can
have
a
cycle
that
it
says:
ok,
yes,
it.
B
Is
up
to
date
with
the
christmas
sale,
because
we
want
the
number
of
replicas
to
increase.
That's
another
controller,
it's
a
controller!
That's
there
and
that's
when
we
talk
about
an
aura
loop
and
a
genre.
An
aura
loop
has
additional
logic,
but
no
it
tells
it
how
to
do
it.
What
it
says
is
to
that
other
internal
controller
I
need
you
to
have
10
replicas
today
or
have
100
replicas,
because
we
lose
more
traffic.
So
it's
a
world
where
we
now
have
in
the
unix
world.
We
have
one.
B
We
seek
to
have
a
tool
that
the
only
thing
knowing
how
to
do
it
is
something
but
doing
it
very
well,
that's
the
same
idea
here
we
have
closed-loop
tools
or
controllers
and
they
know
how
to
do
a
job
and
by
putting
them
all
together,
then
we
have
all
those
extraction
domain
systems
in
your
where
we
can
use
the
model.
Teté
quiroz
to
be
able
to
do
the
operation
understands
all
this.
B
Now,
with
all
this,
how
we
really
translate,
for
example,
what
the
management
cycle
is
and
two,
because
if
we
look
at
it
in
the
traditional
way,
we
will
see
that
there
is
an
initial
version.
Then
tests
folded,
there
was
a
way
operations
were
monitored
and
all
that
was
analyzed
and
from
there
optimizations
were
made
with
guido.
This
is
simplified
with
groups.
Normally
we
focus
on
the
ox
part,
the
operational
part
of
the
box.
B
Is
there
an
initial
version
or
is
there
a
new
version
and
if
there
are
some
basic
validation
tests,
for
example,,
that
the
configurations,,
the
syntax
is
correct,,
but
the
validation
of
all
this
happened
in
the
box,.
The
validation
of
end
to
end
testing
will
be
all
that
happens
in
the
box,.
Here
we
are
in
the
part
of
the
ocs,.
The
part
from
ops
enter
the
deployment
now
operate.
We
are
going
to
do
day,
2
operations
in
a
day,
2
operation.
B
B
So
to
operate
is
to
create
a
new
version
that
new
version
is
made
and
the
same
happens
with
the
optimization
part.
Let's
say
we
have
tools
like
the
ones
that
exist
for
jobs
or
tools
that
we
have
created,
that
we
do
an
analysis
using
machine
learning
and
from
there
we
can
detect.
Ok,
if
we
do
the
deployment
or
the
interconnections
in
such
a
way,
we
will
be
much
better
in
the
perfect
services,
but
this
optimization
does
not
occur
in
those
systems.
B
Each
authorization,
as
it
occurs,
is
again
a
new
version
is
created
and
that
new
version
is
the
one
that
is
validated
and
is
the
one
that
is
approved,
and
it
is
where
the
deployment
happens
as
well.
As
we
really
see,
the
version
system
to
ment
is
the
only
operating
interface
for
our
systems,
so
that
is
that
it
is
the
essential
part
of
fabrics.
B
How
about
we
look
for
the
part
of
the
boat
to
see
how
it
looks
good
in
the
traditional
model
we
want
to
make
a
backup.
Ok,
all
it
takes
is
a
'me
kloster
button,
because
I
need
everything
to
be
identical
to
this
configuration
in
case
of
a
perfect
failure,
but
how
it
looks
in
the
100
and
2.
We
have
the
version
and
we
have
the
desired
state.
Exactly
everything
has
already
been
saved
in
a
version
in
a
control
system,
for
example,.
B
Nowadays,
there
is
no
need
to
make
a
bank
for
a
traditional
bato
of
what
the
infrastructure
is,.
It
does
not
provide
me
with
anything
of
value
and
nobody
tests
it
not
usually
the
lazy
ones
either,,
but
I
have
a
version,
because
what
I
know
is
that
if
I
need
to
restore
my
services,
I
have
to
deploy
that
version,
and
that
is
how
the
infrastructure
payment
part
is
handled.
B
Obviously,
there
are
parts
that
do
have
to
be
backed
up,
but
a
backup
already
with
metadata,
and
it
is
to
put
it
in
the
part
specifically
of
the
stores
of
what
would
be.
The
state
is
persistent
in
the
part
of
persistent
readers
there,
because
we
need
not
only
to
capture
the
data,
but
the
meta
is
associated
with
it
and
what
version
it
corresponds
to
so
You
have
to
keep
that
part
of.
B
The
flow,
yes,
yes,.
We
want
to
see
this
now,,
how
this
looks
in
a
number
1
organization,.
We
start
with
the
same
thing
that
the
box
has
preached
for
many
years,,
which
is
that
we
need
cross-function
operational
groups,.
That
is,
there
are
multiple
groups
in
multiple
expertise
in
the
same
group
in
these
groups
are
the
ones
that
design
and
create
the
configurations
and
templates
of
the
configurations
that
are
later,
for
example,
of
that
template
that
can
be
in
proprietary
tools
or
can
simply
be
an
excel
file,.
It
does
not
matter,
but
they
do
it.
B
They
do
here
and
then
they
use
tools-
and
here
in
this
part
as
well
as
there
are
tools,
and
if
we
were
to
do
everything
at
a
very
technical
level.
It
is
a
tool
like
pipelines,
it
has
been
transformations,
but
if
they
were
not
tools
like
that,
and
we
want
to
give
access-
let's
say
to
executives:
that
is
where
tools
such
as
business
rules,
the
business
road
tool
where
there
are
let
us
make
wordpress
calls
from
the
business
perspective,
and
then
someone
can
interact
with
these
systems.
B
B
Once
that
already
enters
the
apparent
rhythm
of
orders,
what
we
have
is
a
series
of
tools
or
a
series
of
configurations
where,
for
example,.
We
can
have
traditional
providers
as
long
as
they
behave
like
a
guido
controller
controller
and
they
go
and,
for
example,
they
can
go
and
configure
the
servers.
I
thought
the
latest
jeans
do
all
that
the
same
with
the
infrastructure
as
code,
everyone
reading
the
deep
reports
or,
for
example,
this
does
not
mean
a
single
that
the
rhythm,
in
fact-
and
that
is
another
talk.
B
This
is
what
a
quirós
model
looks
like
for
operational
groups
that
want
to
adopt
these
new
models,
and
since
we
are
very
short
of
time,
if
we
always
talk
about
tools,
there
are
a
lot
of
tools
on
the
market.
Normally,
this
is
not
about
the
tools.
This
is
about
the
principles
about
the
models
that
are
used.
B
But
if
you
want
to
see
some
tools,
example
landscape,
the
city
that
foundation
is
the
bering
foundation
continent
of
the
alliance
sound
edition.
They
maintain
a
list
of
tools,
but
again,
not
all
the
tools
that
are
there.
You
need
to
use,
nor
are
they
there
to
feel
all
the
tools
nor
some
of
my
favorite
tools
in
which
I
have
that
in
the
first.
In
the
first
line
there
are
two
and
they
detect
that
there
is
no
one
yet
and
castromán
is
a
combination
of
them
works
excellently
for
any
type
of
scalability
to
soak
up
investment.
B
Guilad,
anyone
at
the
end
of
the
day
is
a
system
of
positioning
that
can
be
used
and
there
is
another
tool
for
the
prof
which
can
also
be
used
for
the
deployment
of
cuber
nerys.
In
my
case,
when
I
work,
this
with
as
operators
of
5g
examples
is
all
we
are
talking
about
from
the
part
of
the
circuits
of
networks,
ticket
network
configuration
of
the
ene
efe
fold
platform,
including
activation
of
5g
services.
That
is
the
way
in
my
case,
I
use
all
this
and
normally
tools.
B
B
B
B
Sing
the
live
streaming
that
cristian
fernández
does
about
and
exclusively
about
shots
and
tools,
etc.,,
very
good.
part
of
the
programming
of
openshift
tv
sponsor
tray,
but
that
is
really
open.
So,
for
example,
this
is
very
good.
It
is
like
intuit
who
were
the
creators
of
reducing
and
how
they
use
it
in
sectors
very
good
models
of
revolutionary
boxing
or
repression.
You
have
a
life
style,
gold,
mansions
hours,
emery
freeman
at
the
start,
up
showcase.
Her
timing
is
very
good
there.
She
explains
and
presents
that
model
and
the
nettops
network
models.
A
Thank
you
very
much
William
for
such
an
interesting
presentation,
so
explanatory
and,
above
all,
so
punctual
in
this
type
of
terms,
because
personally
I
have
seen
many
people.
Sometimes
we
tend
to
confuse
the
terms
that
belong
to
vox,,
which
is
twists,,
is
a
methodology,,
is
a
practice,,
is
part
of
a
process,,
so
I
feel
that
it
clarifies
the
panorama
a
lot,
right.
A
B
Is
a
series
of
repetitions
of
actions
that
are
repeated
over
time
until
it
becomes
part
of
what
is
adopted
as
the
known
and
eventually
that
becomes
part
of
what
the
culture
is
so
having
that
as
a
base
to
adopt
from
box
or
from
sex?
It
is
starting
to
repeat
certain
actions.
It
starts
to
integrate
security.
It
is
usually
the
most
painful
thing
that
exists
is
how
to
install
to
integrate
all
the
strict
security
part
from
the
beginning
in
the
development.
If
it
succeeds
to
do
it
and
it
is,
and
they
begin
to.
B
B
A
favorite
tool
is
something
city,
because
it
allows
me
to
use
it
for
any
of
the
combinations
that
I
usually
need
to
do
it
from
the
deployment,
but
it
has
a
method
one
with
very
strong
luxe
capabilities.
So,
for
example,
without
going
into
many
details,
but
for
example,
you
can
use
it
from
when
you
connect
a
server.
B
I
can
receive
that
as
it
is
the
impi
track
place
it
in
a
kafka
box
and
use
that
to
make
changes
for
approved
and
validated
seng,
and
that
later
something
can
in
turn
optimize
the
same.
I
can
also
once
it
is
running.
Reading
that
information
well,
I
can
use
it
not
only
for
the
display
of
something
like
cover
need
is
He
also
used
it
for
deployments
of
not
covering
the
nose,,
such
as
configurations
of
several.
This.
One
is
also
used
for
deployment
of
applications
and
I
also
use
it.
B
A
B
The
interesting
thing
is
that,
for
example,
the
ibex
some
like
the
doubles
have
begun
to
modify
the
offers
in
the
offers
so
that
they
are
compatible
with
turns
because,
as
'heroes',
what
it
indicates
is
there
is
a
source
of
reality.
So
the
tool
is
the
owner
of
the
configuration
is
that
source
of
well.
They
have
been
making
that
type
of
modification
so
that
precisely
their
tools,
their
offers
can
be
used
in
guido
pge.
So
from
that
perspective
we
see
both
microsoft.
B
A
B
A
And
of
course,
well,,
thank
you
very
much
for
your
time
for
your
presentation,
I
think
it
is
quite
enriching
for
everyone,.
So
we
thank
you
for
having
accepted
the
invitation
and
for
having
shared
everything
with
us.
Thank,
you
very
much
for
the
information
and
just
remind
everyone
who
is
watching
us
that
we
have
the
following
talk
on
track.
1
in
case
you
want
to
switch
to
wild
wind,
and
thank
you
very
much
again.
Thank.