►
From YouTube: Nube Justicia: BUS Federal de Justicia Mario Adaro (JuFeJus)Gustavo Perez Villar (JuFeJus) OSCG 2022
Description
Nube Justicia: BUS Federal de Justicia
Guest Speakers:
Mario Adaro (JuFeJus)Gustavo Perez Villar (JuFeJus)
https://commons.openshift.org/gatherings/buenos-aires-25-aug-22/
A
A
In
the
year
1994,
what
is
the
Federal
Board
of
Courts
and
Superior
Courts
of
Justice
of
the
Argentine
provinces
and
the
Autonomous
City
of
Buenos
Aires
was
created,
from
there.
They
began
to
work
on
different
issues
together
and
internally.
They
worked
a
series
of
forums
in
different
fields
of
knowledge,
for
example,,
one
of
them
was
the
computer
forum,.
It
is
what
it
is
to
one,
and
in
that
computer
forum
we
have
shared
advances
in
each
of
the
provinces
of
each
of
the
provincial
judicial
powers,
and
also
we
dream
a
little.
A
We
do
not
dream
a
little
about
some
development.
Some
joint
project
that
always
in
that
way,
One
allows
you
to
advance
more
than
making
individual
efforts.
No
good
There.
We
come
to
the
year
2019,
where
August
29
is
the
founding
Day
of
what
the
Institute
is:
Federal,
innovation,
technology
and
Justice
that
works
within
the
framework
of
the
Federal
Board
of
Justice
And
there.
A
We
can
say
that
it
was
the
pivotal
moment
where
a
lot
of
these
dreams
that
I
just
told
you
about
well
here
you
are
going
to
see
a
little
of
the
objectives
were
realized
strategic.
The
mission
that
everything
has
to
do
with
the
exchange
of
knowledge,
But
and
with
applied
research
and
the
joint
execution
of
technological
projects,
but
above
all,
with
this
great
impulse
that
doctor
adaro
as
president
of
the
institute
gave
him,.
A
A
Well,
from
there.
We
focused
on
concentrating
that
and
start
working
together
where
each
judiciary
contributed
a
part
of
that,
yes.
So.
We
We
began
to
specialize
a
bit
with
which
we
achieved
that
efficiency
of
one.
That
is
the
sum
of
24
instead
of
24,
repeating
the
same
thing.
Every
day.,
The
Federal
Justice
cloud
is
like
the
great
initial
project
and
it
is
one
of
the
strategic
objectives
of
ifetech.
As
It
says
here,
the
board
started
in
the
second
half
of
2019.
A
A
A
That
is
the
first
project.
The
Federal
bus
within
operability
that
is
now
going
to
tell
us
in
more
detail.
What
is
going
to.
This
will
surely
be
more
interesting
after
an
electronic
administrative
management
system
and
the
migration
to
Claude
of
all
the
infrastructure,
little
by
little,,
all
the
infrastructures
and
fitec.
Well,
I
'll
leave
you
the
bus,.
B
But
thanks.
Hello,
good
afternoon,
I,
introduce
myself
again..
My
name
is
Gustavo
Pérez,
I
work
at
secretariat
of
information
technology
in
the
supreme
court
of
justice
of
the
province
of
Buenos
Aires.
Approximately
a
year
and
a
half
ago,
the
court
signed
an
agreement
with
the
institute
of
innovation
and
technology
of
the
board
to
promote
a
project
called
bufferal
de
Justicia.
It
is
a
project
we
started
to
be
developed
a
long
year
and
a
half
ago
and
Cuál
será.
B
Is
a
project
that
basically
complements
the
digitization
process
of
all
the
judicial
powers
today,
in
a
lot
of
talks
that
were
given
at
home
about
the
process
of
transformation,
several
in
the
state,
the
reality,
at
least
in
the
field
that
I
know,
which
is
justice.
For
years
now,
justice
has
been
transforming
like
all
sectors
in
the
public
and
private
sphere.
The
pandemic
was
obviously
a
trigger
for
all
these
digitization
processes.
B
It
is
more
said,
and
in
this
framework,
when
one
begins
to
digitize
a
process,,
one
begins
to
see
that
the
scope
of
this
Digital
Process
is
not
all
within
the
organization,.
The
judicial
process
has
a
lot
of
recipients
within
the
organization,,
but
it
was
also
And
that
implies
that
When
we
want
to
digitize
the
entire
process
or
advance
the
entire
process,.
We
have
to
look
for
or
extend
our
digital
processes
to
organizations
that
are
outside
of
our
organization,
for
example,.
This
is
the
clearest
case
within
the
framework
of
the
process,.
B
It
is
always
necessary
to
request
organizations
External
other
judiciary,
State
bodies,
Private
companies
that
indirectly
participate
in
the
project
are
not
a
party.
They
are
neither
the
accused
nor
the
defendant
or
the
plaintiff,
but
are
bodies
that
intervene
in
the
process,
providing
information
that
is
relevant
to
the
process
when
one
wants
to
digitize
it
begins
When
the
need
for
digital
exchange
or
digital
information
with
external
organizations
arises,
the
idea
of
the
law
firm,
a
bit,
I
like
to
present
it
as
three
projects.
B
That
is
a
fairly
ambitious
project
and
I
like
to
tell
it
from
three
edges..
The.
First
is
the
project.
Itself.
It
is
basically
a
platform
for
the
exchange
of
standard
electronic
documents
between
all
the
judiciary
in
the
country
and
all
those
public
or
private
organizations
of
a
national,
provincial,
municipal
scope
that
need
to
exchange
information
within
the
framework
of
the
process.
Imagine
I.
Don't
know.
B
Providing
information
about
these
so-called
addresses,
etc.
If
Telefónica
had
to
digitally
integrate
with
the
electronic
file
projects
of
all
the
judicial
powers,,
it
would
have
to
develop
23
24
integrations
according
to
the
technology,
the
model
and
the
electronic
Sprint
platform
that
it
has
here
by
judicial
system.
In
this
way,
telephone
I
don't
know
migrations,
afip
anses.
B
Any
of
these
organizations,
with
a
single
with
a
single
development
Integrates
with
the
entire
circuit
or
with
the
entire
judicial
system
of
the
Argentine
Republic
and
even
with
another
type
of
agency,
allows
the
integration
of
justice
at
the
national
level
and
will
allow
that
each
regional
judiciary,
at
the
provincial
level
can
be
its
small
electronic
integration
with
the
organizations
of
each
province
of
property
records
or
any
organism
of
provincial
scope.
That
is
a
bit
the
ambition
of
the
project.
B
And,
incidentally,
encourage
the
use
of
exchange
and
good
customs
or
the
good
ways
within
the
implementation
of
electronic
documents.
There
is
also
quite
a
lot
of
diversity
in
terms
of
the
implementation
of
electronic
documents
from
the
bus
We
try
to
promote
standardization,
the
application
of
digital
signatures,
the
use
of
time
stamps,
long-term
signature
verifications,
etc.
in
the
judicial
field
and
I
believe
that
in
the
State
digital
process,
the
information
exchange
unit
is
undoubtedly
the
electronic
document,
and
if
that
separate,
electronic
document
is
conceived
as
a
digitally
signed
data
exchange,
structure,
etc.
B
the
question
begins
to
get
more
interesting
So.
This
is
the
first
axis
of
the
project,,
a
super
ambitious
project
that
aims
to
link
all
of
the
national
justice
system
together
to
facilitate
the
exchange
of
electronic
documents,,
a
certain
project
that
personally
seems
most
interesting
to
me,,
which
is
the
technological
platform
of
this
project..
It
was
designed
from
scratch
to
be
executed
in
the
cloud
of
Justice
to
be
executed
in
an
area
that
transcends
each
individual
judiciary.
B
It
had
to
be
an
area
that
belonged
to
all
the
judicial
powers
And
in
this
case
the
cloud
of
justice
and
the
project
that
was
promoting.
The
real
joint
of
cuts
was
more
than
suitable
for
this
project.
So,
on
the
other
hand,
we
had
the
possibility
to
think
and
design
the
architecture
and
the
functionality
and
the
whole
project
Knowing
in
advance,
how
it
was
going
to
be
developed
Where.
B
It
was
going
to
be
executed
and
we
took
the
opportunity
to
be
able,
apply,
test
and
learn
practices,
some
techniques
and
technologies
that
none
of
the
judiciaries
had
yet
fully
developed.
So,
in
the
first
things
we
did
was
we
made
a
pattern
completely
based
on
asynchronous
event-oriented
and
completely
independent
microservices,
designed
for
what
So
that
each
of
Those
of
the
services
that
make
up
this
application
have
been
developed
by
a
different
province
by
a
different
development,
group,
even
belonging
to
different
organizations
such
as
this
case.
In
fact,.
B
There
are
five
or
six
or
seven
provinces
that
I
will
list
later
that
are
involved
in
development
Therefore,.
We
use
a
pattern
of
synchronous,
microservices
based
on
events,.
Each
microservice
has
its
own
database,.
We
integrated
an
asynchronous
message,
bus
that
Apache
built
into
the
infrastructure,,
and
it
was
a
great
development
and
learning
platform
for
all
of
us
who
participated.
we
stole
something
from
here
for
our
judicial
powers
and
we
all
contribute
some
of
our
technology
management
in
judicial
powers
to
the
law
firm.
B
Today,
the
federal
has
two
clusters.
One
of
them
is
a
development
cluster
that
is
located
in
the
province
of
Buenos
Aires,
another
cluster,
that
is,
the
justice
cloud,,
which
is
a
cluster
completely
deployed
in
virtual
machines
in
arzak,
and
absolutely
all
the
infrastructure
of
the
bus,
application,,
the
pipelines,,
the
configuration
of
the
operators,,
the
topics
of
kafka
or
the
topics
of
the
message
of
the
asynchronous
messages,,
the
structure
of
the
messages,
everything
everything
everything
absolutely
is
handled
as
code
managed
from
an
islam.
B
B
And
Well,
I
have
this.
This
is
a
bit
like
the
Federal
Justice
bus
scheme,.
Each
of
these
are
microservices
and
fulfill
a
very,,
very
particular
function.
Today,.
It
is
a
system
designed
to
scale
a
lot..
It
is
an
issue
that
will
have
a
very
low
transversal
load,,
but
As
I'm
telling
you,.
This
is
a
prototype,,
a
kind
of
architecture,
application
that
we
all
need
or
want
to
incorporate
into
our
infrastructures.
Basically.
We
have
a
border
service.
That
is
the
one
who
attends
to
the
outside
of
the
bus,.
B
It
is
the
only
point
of
contact
that
the
organizations
will
have
who
are
outside
the
bus
to
interact
to
exchange
a
document.
The
edge
authenticates
synchronous
people
is
an
apired.
The
bus
is
thought
beyond
that.
It
has
a
pediment
for
users
to
interact.
The
bus
is
designed
for
each
judiciary
management
system
to
integrate
by
API
with
the
bus,
that
is,.
The
effect
that
we
want
to
talk
about
with
this
is
that
a
judicial
job
in
the
province
of
Buenos
Aires
in
the
province
of
huancaba,
buen
chubut,
opens
its
management
system,
writes
a
document.
B
The
judge
signs
it
and
sends
it
and
it
is
written,
it
is
inserted,
As
a
procedure
in
the
electronic
file
management
system
of
Río,
Negro,,
Tierra
del
Fuego
or
Salta,.
The
only
one,
that
is,
it
is
that
level
of
transparency
that
we
want
and
we
are
going
to
achieve.
In
the
middle,.
There
is
this
little
machine
that
for
now
is
quite
humble.,
but
it
works
edge.
Pencil
makes
the
first
variations
authentic
to
the
external
user
or
to
the
external
application,
makes
minimal
basic
validations
and
throws
an
event
with
the
message
received.
B
The
broker
service
is
a
service
that
takes
care
of
that
message.
Extracts
the
electronic
document
from
the
message
validates
digital
signatures,
each
organization
that
boards
the
bus
can
put
as
its
compliance
policies.
Then
it
says
Well
I,
accept
digital
signature
and
not
electronic
or
I
demand
that
my
documents
have
a
good
time
stamp.
B
The
broker
is
going
to
make
sure
that
the
organization
of
you
does
not
exists,
that
the
electronic
document
that
is
being
sent
meets
the
conditions
that
must
be
met
in
order
to
be
delivered
that
the
digital
signatures
are
valid,
that
the
document
is
complete,
etc.,
etc.,
etc.,
etc.,
etc.
when
everything
is
OK,.
It
issues
an
event
that
is
taken
back
by
the
the
service
is
at
the
edge
and
makes
it
available
to
the
destination
body,
already
validated
and
including
the
entire
electronic
document.
Itself,,
the
bus
does
not
store
the
electronic
document,.
B
Simply
the
main
function
of
buses
is
to
facilitate
the
document
reaching
one
place
to
another
and
attest
that
this
transaction
existed,,
which
is
why
there
is
the
notary
service,,
which
is
basically
a
microservice
that
is
subscribed
to
all
the
event
channels
of
all
the
other
services
and
composes
the
transactions
as
messages
come
when
it
saw
the
message
that
caused
it
to
the
transaction
is
closed.
Due
to
success,,
failure,
I
calculate
an
ax
for
all
that
ticket,,
which
is
a
step
by
step
of
each
independent
transaction,
register.
B
The
Hash
in
the
Argentine
federal
blockchain,
take
the
stamp
data
from
Luche
Federal
Argentina,,
insert
them
into
the
ticket
and
put
it
on
at
the
disposal
of
the
two
organizations
of
the
ends.
So
the
idea
of
this
is
to
avoid
repudiations
between
organizations
think
that
in
judicial
procedures
there
are
times
there
are
deadlines
that
expire
and
a
lot
of
issues.
Well,
the
bus
attends
to
these
issues.
B
On
the
other
hand,
there
is
a
service
more
than
organizations
where,
as
part
of
the
integration,
when,
when
an
external
organization
gets
on
the
bus,
one
of
the
things
it
has
to
do
is
synchronize,
which
dependencies
are
going
to
be
available
to
receive
electronic
documents.
The
agency
service
receives
them,
validates
that
they
are
fulfilled.
The
loading
data
generates
events
and
all
the
other
services
synchronize
their
own
database.
That
pattern
of
roasting
by
services
is
great,
because
when
we
start
to
analyze
it
we
start
to
analyze
how
the
project
works.
B
You
realize
that
each
service
has
a
different
view
of
the
complete
system
In
other
words,.
They
are
not
all
seeing
the
same
thing,
and
that
is
why
what
I
am
saying
is
a
property,,
but
it
is
surprising
how
they
are
so
independent
that
each
one
of
the
same
system
in
different
ways,
because
each
one
synchronizes
its
own
data
based
on
the
events
in
relation
to
what
it
needs
So
the
Broca
service-
does
not
need
to
know
what
the
dependency
is.
Called,.
B
B
Streams
in
the
implementation
of
Open
shift
in
the
cloud
which
is
who
manages
absolutely
all
the
traffic
of
asynchronous
events
within
the
bus.
There
is
the
single
saigon,
the
keylock,
which
is
where
all
is
managed,
the
authentication
between
services,
external
organizations
and
bus
entities,
and
we
have
something
that
cost
a
bad
word.
But
it
was
very
difficult
to
incorporate,,
which
is
the
skin
register,,
which
is
a
fabulous
component.
B
Messages
that
circulate
through
the
bus,
then
all
the
validation
we
use
to
exchange
message,
format,
all
validation,
that
the
messages
that
the
services
are
sent
is
with
the
message
that
we
define
in
the
design
makes
it
choose
a
register.
The
services
delegate
that
function
to
the
register
when
they
receive
a
service
asks
if
it
is
ok
and
passes
the
alloy
or
not
and
has
a
second,
a
second
functionality.
B
That,
for
me,
is
essential
is
that
I
can
mount
on
the
Racing
skin
a
compatibility
policy
regarding
the
message
structures,
So
the
skin
registers
all
the
time
it
will
be
reinforcing
that
policy.
It
will
never
allow
me
to
put
messages
that
break
compatibility
because
having
a
process
based
or
a
system
are
micro
services.
We
speculate
that
in
the
future
when
the
application
is
running
dynamically
application,
the
services
are
going
to
have
different
versions
and
there
are
going
to
be
different
versions
of
the
services
Therefore.
B
The
services
are
going
to
handle
different
message:
structures
So,
the
skin
resist
is
there
in
the
middle
guaranteeing
that
no
service
breaks
with
messages
of
different
structures.
It
is
a
component
that
is
great
I
hadn't
used
any
solution
before
we
put
it
in
this
architecture,
and
it
was
very
difficult
because
we
put
it
in
late,
so
we
realized
that
the
services
we
generated
messages
didn't
work,
so
we
had
to
redo
a
lot
of
issues,
but,
yes,
we
would
have
entered
beforehand.
It
would
have
been
great.
The
messages
are
described
in
a
Jason
skim.
B
And
after
This
is
the
good
some
screenshots
of
the
cloud
cluster
fairness.
Basically,
what
we
did
was
about
the
Open
shift
faculty.
All
the
deployment
pailand
were
set
up
from
the
different
environments,
the
development
environment,
the
sandbox
or
Cuba
environment,
which
is
the
environment.
We
are
going
to
use
for
the
judiciary
to
develop
their
integrations.
We
are
launching
it
next
week
comes
and
a
third
environment
that
is
productive.
B
All
the
deployment
rules
here
are
handled
by
a
gitlab.
The
developers
have
a
certain
brunch
where
they,
when
they
make
noise
in
that
brunch,
the
Pipe
plans
automatically
deploy
to
dem
So.
That
immediately
has
the
possibility
to
see
the
operation
of
the
services.
A
merge
is
made
to
the
Master
branch
it
is
deployed
in
the
test.
Sambos,
it
is
underway
it
is
approved,
and
then
there
is
a
manual
trigger
of
a
padling
to
start
production.
The
tools
we
used
were
Well
then
fight.
B
B
This
is
the
Gil
lab
repo.
Where
we
have
the
codes
of
the
projects.
We
are
designing
smart
contracts
for
the
next
version
to
directly
integrate
with
other
blockchains.
We
have
all
the
pipelines,
I
decided
it
will
be
the
repode.
They
say
we
have
it
here
inside.
Each
service
has
its
vox
record,
with
all
its
particularities
for
each
environment,
and
everything
is
touched
from
here.
This
is
a
view
of
one
of
the
services
from
the
from
the
console
of
something
fabulous,
CD.
B
For
those
of
us
who
work
in
infrastructure,
I
realized
more
than
25
years
ago
that
this
is
magical,
that
is,,
why
do
it
with
a
virtual
machine
or
with
physical
servers?
You
press
a
button.
You
disassembled
a
complete
application
with
its
infrastructure,
and
you
put
it
back
together
in
10
seconds.
This
is
glorious.
B
Not
retouched
It
is
not
prepared.
This
is
the
development
group,,
which
is
the
third
list
that
I
like
to
tell
about
the
project,.
We
inadvertently
created
a
technology
development
community
that
specifically
deals
with
judicial
problems.
So
I,
really
like
to
tell
how
the
dynamics
of
this
genre
are
of
the
working
group.
Here
is
the
province
of
Mendoza
province
of
Buenos,
Aires
province
of
Chaco
province
of
chubut
province
of
La
Pampa
province
of
Córdoba
now
joins
the
Tierra
del
Fuego
project
and
San
Juan.
There
are
the
provinces
that
last
entered
what
are
last
developing
installation
libraries.
B
We
have
a
public
github
of
the
Federal
bus,
where
today
we
have
a
complete
operational
library
for
chairs.
So
any
judiciary
wants
to
integrate
with
the
bus,
ignores
the
Api
amount
of
the
seats
package
and
already
has
the
functions
of
the
bus
in
its
applications.
We
are
making
a
package
for
php
a
package
for
Java
and
We
are
looking
to
recruit
a
province
that
puts
people
to
make
the
libraries
for
python,.
We
who
are
here
started
this
and
then
we
held
internal
dissemination
meetings
at
the
Federal
Courts
Board,
where
we
gathered
all
the
provinces.
B
And
as
we
progress,
some
always
raised
their
hands
and
joined
the
group
So,
it
is
a
very
good
Federal
development,.
It
is
a
development
that
was
carried
out
within
each
judiciary,.
It
is
a
development
that
was
complemented
with
the
personal
time
of
all
of
us
who
participated
of
the
project
because
we
all
have
our
separate
work
and
nothing.
We
are
launching
the
psalm
in
the
third
week
of
next,
and
hopefully
we
can
put
it
into
production
before
the
end
of
the
year
or
at
the
beginning
of
next
year,
with
the
judicial
powers
that
we
integrate.
B
This
is
a
small
summary
Of.
All
the
technologies
that
we
integrate,
I
did
n't
tell
you,
each
developer
had
the
chance
to
choose
each
development
team
which
programming
language
they
wanted
to
use
and
which
database
system
to
use.
So.
We
have
a
chair,,
we
have
mongodb,,
we
have
desserts,
And
we,,
who
manage
the
infrastructure
and
architecture
of
the
project.
We
are
incorporating
the
components
that
they
requested.
This
is
a
bit
of
the
entire
free
software
ecosystem
that
we
integrated
into
the
project
and
from
which
we
had
the
opportunity
to
learn
a
lot.
A
Judges
and
technology
managers
coexist
horizontally.
That
was
really
something
unprecedented
and
allowed
this,
because
these
projects,
like
the
most
Federal
or
the
Federal
Cloud
of
Justice,
need
everyone,.
It
is
well
between
disciplinary
and
good
what
we
achieved
thanks
to
that
horizontal
model,.
Well
now,
thank
you
very
much.