►
From YouTube: OpenShift Coffee Break: Meet the QIoT Hackfest Community
Description
Get your espresso ready for the EMEA OpenShift Coffee Break as we meet the Quarkus for IoT Hackfest community (https://qiot-project.github.io/) to discuss new developments and community involvement for the Hackfest. We will talk about Quarkus, IoT, devices, sensors, Kafka and lots of data to be managed by OpenShift and its ecosystem for streaming, data handling and data processing.
A
A
B
Good
morning,
good
morning,
everyone
welcome
to
this
other
edition
episode
of
the
openshift
coffee
break.
Here
with
me.
Today
I
have
the
quercus
for
iot
community.
We
will
come
to
them
in
a
few
seconds.
Just
a
reminder.
What
is
this
open
shift?
Coffee
break
is
a
morning
show
here
in
in
a
mia
time
zone
where
we
talk
about
all
about
openshift,
openshift
architecture
and
all
cloud
native.
My
name
is
natalie
vinto,
I'm
a
product
marketing
manager
for
openshift,
and
today
I'm
really
pleased
to
have
the
quercus
for
iot,
community
and
I'll.
C
Yes,
natalie
thanks
a
lot
and
my
name
is
andre
battaglia,
I'm
the
community.
Lead
of
this
workers
meets
iit
group
and
I
work
for
reddit
as
a
principal
solution
architect.
So
I
work
with
partner,
supporting
them
and
training
them
when
it's
about
complex
solutions,
complex
projects
like
edge
computing
or
digital
transformation
and.
E
E
B
E
D
Hi
so
jeff
newson,
I
work
for
a
company
called
intiv,
formerly
amien
principal
consultant.
There
kind
of
day-to-day
work
is
open
shift
infrastructure
side
a
few
years
ago.
I
was
programming
java
and
that
made
me
or
that
that
kind
of
background,
when
the
hack
fest
came
up
made
me
want
to
get
involved.
B
F
B
B
Awesome
awesome
so
thanks
everyone
for
this
quick
introduction
that
helped
us
giving
more
context
about
the
people
involved
in
this
project.
But
my
first
question
to
you
is
this:
what
is
this
quercus
for
iot
acquest
for
people
that
doesn't
know
what
is
this
initiative
and
we
will
share
also
in
the
chat,
links
and
information?
Please,
if
you
have
any
question,
please
send
your
question
in
the
chat.
I
will
report
to
the
to
the
activities
today,
but
the
first
thing
you
want
to
clarify:
what
is
the
quest
for
iot
access.
C
Yeah
thanks
natalie.
There
is
a
quite
strong
difference
between
the
community
and
the
hackfest
event.
So
while
we
started
implementing
something
for
red
business
partners
and
running
enablement
event
through
the
red
hat
hackfest,
specifically
for
emea
partners
and
focusing
on
edge
computing
solutions,
the
community,
on
the
other
hand,
is
a
place
where
we
want
to.
C
More
oem
involved,
so
hardware
suppliers,
different
software
vendors
like
reddit,
or
they
could
be
aws
azure.
They
could
be
a
specific
software
vendor
in
the
am
aiml
space.
So
that's
why
we
want
to.
We
run
this
event,
which
is
a
mid-term
enablement
and
marketing
event,
to
put
participants,
distributors
and
technology
vendors
together
to
discuss
collaborate
and
try
to
make
business
opportunities
concrete
and
projects
run
at
the
customer
side
successful.
So
that's!
Basically
the
difference.
C
B
C
B
C
Could
you
please
let
me
know
if
you
can
see
my
screen
yeah
that
looks
clear,
so
this
is
qaot
project
dot.
Github.Io
is
our
community
website
or
blog
in
this
space?
Here
we
tend
to
collect
everything
that
is
purely
technology
related,
so
we
have
several
blog
posts
around
specific
themes
like
integration
or
securing
microservices
in
an
alkaline
container
based
environment,
and
also
we
have
a
an
open
area
where
interested
people
they
could
be
subject
matter,
experts
they
could
be
partners,
they
could
be
reductors
themselves
or
customers.
C
They
can
propose
a
new
use
case
implementation
and
challenge
the
technical
community
to
implement
that
the
outcome
of
the
community
is
certified
and
standardized
and
becomes
the
theme
of
the
red
hat
hack
fest.
So
this
is
the
business
event
run
by
red
hat
for
his
emea,
advanced
and
premier
partners,
and
during
the
event
we
have
several
sponsors.
C
B
C
C
We
called
it
hack,
fest
and
not
hackathon,
simply
because
it's
a
midterm
event,
so
we
have
a
week
dedicated
to
the
enablement.
So
we
deliver
webinars
and
the
speakers
are
usually
subject
matter,
experts
from
our
sponsors
from
reddit
itself
or
from
partners,
and
then
we
have
four
weeks
of
the
associate
implementation
phase.
So
partners
are
challenged
to
implement
part
of
the
solution
we
created
in
the.
C
So
the
registration
phase
will
close
on
mid-october
roughly
october,
the
14th.
Last
but
not
least,
this
event
is
for
it's
a
hackfest,
because
it's
for
teams,
it's
not
for
individuals,
meaning
in
turn.
We
require
team
leaders
to
register
first,
they
will
receive
a
registration
call
for
the
team
members
to
register
and
connect
to
the
team
previously
created
a
team
made
up
of
three
to
five
people.
C
C
Oh
yeah
thanks,
sorry
because
I
forgot
to
mention
one
thing:
from
the
community
blog
or
landing
page.
You
have
access
to
our
google
group
to
our
tweet
account
or
twitter
space
to
the
github
repo
into
the
community's
luck
channel.
Where
everybody
is
is
welcome
to
join,
ask
question,
participate
and
collaborate,
and
that's
all
from
my
side.
B
Well,
that's
great
integration.
I
give
lots
of
context
of
what
is
the
hackfest,
also
nice,
understanding
the
difference
between
a
knack-a-thon
and
a
knack
fest.
I
didn't
know
about
it.
So
thanks
for
this
explanation,
I
don't
know
if
you
were
all
aware
of
this
difference,
it's
interesting
yeah.
So
this
is
the
project
I'm
looking
forward
to
hear
from
this
community.
So
we
have
some
representative
of
the
community
today,
if
I
understood
correctly
right.
B
So
folks.
Well,
what
are
your
thoughts
about
the
this
hackfest?
How
did
you
start
involvement?
I
would
I
would
like
to
listen
to
stories
if
someone
wants
to
share
their
story.
Somebody
like
jeff,
introduces
why
join
at
the
act
fest
so
that
give
content.
But
what
did
you
could
you
please
share?
What
did
you
like
the
most?
What
did
you
enjoy
doing
in
this
act?
Fest.
D
Yeah,
so
natalia
thanks
for
that,
so
I
I
actually
took
part
in
the
hack
fest
as
a
participant
first
time
around
for
the
company
with
the
partner
and
for
me
at
the
time
it
was
a
chance
to
kind
of
get
to
the
other
side
of
openshift
day-to-day.
I
was
kind
of
doing
the
infraside
doing
the
deployment,
but
actually
getting
the
chance
to
do
a
bit
of
coding
and
actually
deploy
and
deploy
some
code
on
openshift
and
and
do
that
side
of
the
house.
D
Almost
it
was
a
real,
real,
interesting
opportunity
and
and
good
separate
and
different
from
the
day
job.
So
that's
that's
why
I
wanted
to
get
involved
and
kind
of
once
I
was
involved.
The
technology
was
interested
in
running,
running
containers
on
raspberry
pi
and
actually
kind
of
getting
the
the
communication
between
the
pie
and
the
open
shift
going.
That
was
really
really
interesting
and
something
that
I
wanted
to
take
forward.
But
within
the
company
there
was
there
was
no
opportunity.
We
weren't
doing
any
work
in
that
particular
area.
D
B
That's
amazing:
it's
a
it's
an
amazing
story
because
from
the
participant
you
you,
you
joined
the
community.
Now
we
are
one
of
the
organizers
of
this
hackfest
active
party,
so
that
that's
amazing
story
and
it's
also
amazing
to
know
how
to
build
a
community.
I
don't
think
it's
trivial
to
do
that,
but
before
before
I
would
like
to
come
back
on
that
andrea,
but
I
would
like
to
listen
also
from
matia
and
and
the
other
people
joining
today.
What
do
what
their
impression
about
that
fest.
E
Yeah,
I
can
go
so
well,
I'm
doing
the
the
the
kot
project,
because
you
know
what
I'm
trying
to
do
is
just
looking
for
kind
of
a
new
opportunity,
new
way
or
working
and
what
they
like.
Also
new
technology
to
experiment.
Something
new
that
I
can
see
that
in
the
future
can
be
useful
for
the
for
the
customer
because
try
a
new
new
technology.
They
are
kind
of
on
the
edge.
I
like
the
cutting
edge
technology,
it's
nice
to
challenge
yourself.
E
First,
try
new
things
and
then
you
you're
ready
when
this
come
on
the
customer,
because
usually
this
it
takes
years
to
come
to
be
to
use
this
such
technology.
So
it
cannot
get
you
prepared,
thinking
in
advance
and
as
well.
It
is
fun
first
of
all
and
then
also
I'm
really
happy.
That
now
is
becoming
official
like
because
we
start
as
a
community
and
we
was
kind
of
reduct
partner.
Yes,
but
now
it's
kind
of
red
at
access.
E
So
I'm
kind
of
proud
of
this,
because
if
something
becomes
bigger
and
bigger,
so
it's
gaining
attraction,
and
so
it
means
that
his
interest
is
also
for
the
end
user
for
partner,
maybe
in
future,
also
directly
the
customer.
So
let's
see
how
it
goes,
and
I
look
forward
for
the
next
act.
First
with
the
new
user
case,
and
hopefully
with
new
challenges
that
would
unlock
as
well.
We
proposed
a
solution
a
way
of
working,
but
what
I'm
looking
as
well
from
from
developer
or
partner
is
a
new
way
also
the
same
solution.
E
You
know
because
we
don't
we
provide
a
kind
of
blueprint,
but
this
doesn't
mean
is
is
just
the
way
to
do.
They
also
propose
a
better
solution,
which
is
also
interesting,
which
start
to
create
a
discussion
around
that
and
maybe
for
the
next
acquest.
Another
part
is
going
to
join
in
the
community
to
showcase
what
we
could
do
better
so
yeah.
B
Awesome
awesome
and
yeah
also
the
it's
cool
that
you
mentioned,
that
about
the
blue
blueprint,
which
is
open.
We
will
come
back
to
the
architecture
because
I
would
like
to
see
how
this
software
stack
is
composed
at
the
edge
and
then
on
the
server
side
on
openshift
and
but
before
coming
back
to
that,
I
would
like
to
listen
from
the
other,
any
other
feedback
on
this
access
from
other
people.
Those
are
two
awesome
feedback.
You
should
be
really
proud
about
this
community,
so
let's
listen
from
the
other.
F
Yes,
natalie
well,
I
started
in
in
the
community
a
few
months
ago
when
I
was
a
partner
who
participated
in
the
previously
hackfest
and
well.
For
me,
it
was
a
big
challenge
to
to
present
a
solution
in
the
in
the
past,
but
well
I'm
not
a
developer.
I'm
from
infrastructure
teams
so
was
a
a
very
big
challenge
and
I
hope
in
the
past
a
our
community
consider
the
solution
and
they
provide
me
the
opportunity
to
to
participate
and
and
get
a
as
a
red
hat
there
today
to
promote
this.
This
hackfest.
B
Thanks,
oh,
this
is
another
very
good
feedback
right
now
so
from
from
participant
who
joined
the
hackfest
now
in
in
again
in
the
organization-
and
you
know
contributing
actively
so
maybe
andrea.
This
is
the
spirit
of
this
community
joining
contributing
and
then
getting
hands-on
on
stuff
and
contributing
to
the
this
access
for
new
edition
and
new
things.
F
C
It's
quite
difficult
from
time
to
time
I
mean
we
could
have
technical
interest
now
we
could
have
technical
passion,
but
not
all
the
community
members
are
interested
in
what
comes
or
what
happens
next
to
whatever
we
produce
right.
So
of
course,
the
the
event
focuses
on
the
enterprise
technologies
like
openshift,
and
we
will
have
the
chance
to
talk
about
it
shortly.
C
So
we
have
single
node,
openshift,
railforage,
openshift
platform,
intel
hardware
technology
for
for
for
the
edge
computing
solution.
We
have
ibm
cloud
but
then,
before
that
you
want
to
implement
a
potential
plc
for
a
use
case
based
on
what
a
programming
language,
a
cloud
native
framework
and
a
container
technology
that
helps
with
with
spinning
up
a
quick
demo
on
your
laptop
right.
So
you
don't
you
don't
install
openshift
on
your
laptop,
maybe
some
people
they
could
do.
But
you
know
it's
it's
unusual.
Actually,
so
that's
what
we
do.
C
C
Container
engine
of
choice
is
potman
for
us,
but
docker
is
smaller
than
welcome
as
well,
because
it's
something
communities
use
upstream
communities
use
and
then
afterwards
we
migrate
and
we
move
everything
to
the
enterprise
worlds,
on
top
of
openshift
and
the
enterprise
red
hat
software.
So
listening
to
jeff,
listening
listening
to
matia
listening
to
mario,
for
example,
jeff
and
mario,
they
are
amazing
and
incredible
as
you
are,
because
let
me
share
with
the
audience
that
natalie
is
one
of
the
esteemed
members
of
this
community
as
well.
C
And
so
these
gentlemen.
Here
they
are
incredible:
infrastructure,
professional
but
mario
developed
cloud
native
software
or
not
js,
he's
not
that
web
a
cloud
native
developer,
but
he
uses
not
js
to
prove
what
he
does
on
the
platform.
Jeff
has
been
a
long
time
java
developer,
but
he
left
because
he
loved
openshift
more.
Unfortunately.
C
So
if
you
prefer
platform
to
java
fine,
but
then
we
went
together
through
some
pieces
of
the
business
logic
that
he
was
keen
to
implement
to
understand
more
around
quarks.
Now
the
cloud
native
software
by
by
the
community
and
then
made
enterprise
by
reddit
with
the
name
of
the
reddit
build
of
corkus,
and
he
made
it
so
he
he
sent
the
to
the
to
the
to
the
repo
some
some
pull
requests,
and
that
was
fantastic,
but
he
is
our
amazing
security
experts
and
quarkus
developers.
C
So
all
the
security
and
this
and
certificate
distribution
and
all
the
stuff
the
customers
actually
are
most
in
mostly
interested
in,
are
from
matia,
because
matthias
says
whenever
we
speak
about
security
and
certificates.
But
he
is
the
guru
here,
and
everything
is
a
piece
of
cake
for
him
because
he's
he
has
amazing
skills
and
fantastic,
fantastic,
a
fantastic
ability
to
understand
what's
needed
before
we
start
asking
him
for
specific
implementation,
though
so,
and
they
are
just
few
of
the
incredible
community
members
we
have.
C
Unfortunately,
all
in
barney
and
ben
cannot
be
here
for
different
reasons,
but
I
want
to
mention
them
at
least
once
because
they
are
amazing
as
well
and
they
can
work
on
pipelines,
helm,
charts.
They
can
work
on
containers
and
platform
as
well.
They
work
on
integration
because
we
have
integration
pieces
in
the
community
as
well.
B
That's
that's
a
phenomenal
reference
for,
and
today
we
are
celebrating
this
community
right,
so
we
are
here
to
celebrate
this
community
there's
gunter
in
the
chat
that
say
hello
and
look
forward
to
run
the
hackfest
with
our
partner
and
extend
the
quercus
for
iot
community,
and
this
is
introduced.
The
next
question
I
would
like
to
to
to
ask
you
so
how
difficult
or
how
easy
is
building
a
community?
B
What's
your
experience
today,
we're
celebrating
this
awesome
community
with
lots
of
experience
from
application
development
platform
security
there's
also,
we
will
see
probably
later
now
in
the
architectural
review.
There's
also
a
messaging
system
part.
So
there's
data
streaming,
data
handling,
so
andrea
and
all
the
people
in
the
community
how
difficult
or
easy
is
building
a
community.
C
Just
let
me
quickly
start
and
I
will
hand
over
to
the
other
gentlemen
here.
Let
me
say:
I'm
not
a
community
manager.
I
have
no
community.
I
had
no
community
experience.
Actually,
if
there
is
any
community,
specialist
or
manager,
he
would
like
to
give
us
a
structure.
It's
more
than
welcome
to
contribute.
We
are
open
so
so
I
started
on
my
own
one
year
and
a
half
ago
just
implementing
a
few
microservices.
C
C
Everything
related
to
those
technical
topic
or
also
from
the
business
perspective
or
presets
perspective
is
interesting.
It's
interesting
because
people
they
learn
people.
They
can
reuse
as
material
state
correctly
their
knowledge
for
their
job
and
customers
partners,
whatever
people
they
can
talk
now.
So
the
building
a
community
is
not
easy
because
you
have
to
be
an
expert.
You
have
to
be
a
professional.
A
community
manager
working
with
passionate
people
is
a
piece
of
cake.
E
Yeah
I
I
agree
that
build
the
community
is
difficult,
but
what
I
think
the
power
on
open
source
or
community
in
general,
you
always
try.
If
you
always
try
to
give
some
space,
you
know
to
experiment
to
do
things
to
try
out,
because
you
have
a
common
goal.
You
have
to
solve
a
solution,
but
you
don't
dictate
how
to
do
that.
You
know
so
that's
why,
with
open
source
you
share
different
year,
you
can
give
attraction
to
that
is
to
experiment
to
a
given
solution.
E
So
the
final
idea,
the
final
implementation,
will
be
just
the
effort,
not
just
the
one
person
like
andra,
say:
I'm
a
good
security.
No
because
yeah,
I
know
some
stuff,
but
I'm
trying
to
understand
all
the
points
and
also
your
feed,
because,
first
of
all,
I
think
it's
important
to
listen
to
before
I
don't
want
to
dictate.
This
is
the
way
to
do
that.
You
know
you
need
to
listen
from
feedback
and
understand.
What's
the
best
way
to
do
that
also
guide
them
as
well.
E
B
That's
that's
pretty
interesting
because
you
know
we
have
a
community
in
the
open
shift.
There's
an
open
shift
community
called
openshift
commons
gathering
all
the
experience
from
customers
use,
openshift
users,
communities,
so
sharing
experience
and
contributing
all
together
that
I
think
that
is,
I
I
will
send
the
link
to
the
chat
that
community
is
built
globally
as
a
structure.
B
It
started
some
years
ago
right,
but
I
will
I
was
curious
to
know
how
is
starting
a
community
not
being
not.
Everyone
is
community
manager
from
day
zero.
No,
how
is
building
this
community?
I
think
this
is
a
great
example,
and,
and
probably
this
community
can
become
go
in
the
next
step,
become
on
a
global
level.
Now
that
the
hackfest
I
understood
is
global
as
globally
spreaded
or
the
intention
is
to
to
be
global,
the
community
can
be
global.
B
B
C
C
I
created
that
and
I
have
the
green
light
from
red
hat,
to
work
on
on
this
project
right
so
mattia,
jeff
and
mario
and
the
others
like
ben
or
banya,
and
so
on
and
so
forth.
They
contribute
to
the
community
occasionally
when
they
have
got
time
still
driven
by
a
strong
passion.
Let
me
remark
this
so
the
first,
the
first
topic
we
built
was
around
kovite
19
in
terms
of
measuring
the
air
quality
during
the
closing
and
the
reopening.
So
that
was
simply
a
an
arm.
C
We
decided
to
go
and
listen
to
the
market,
going,
listen
to
the
enterprise
world
and
see
what
was
the
most
challenging
kind
of
project.
They
were
about
to
approach
and
what?
What?
What
were?
They?
They
their
technical
needs,
and
we
got
the
feedback
that
edge
manufacturing
vertical
was
the
most
interesting,
the
mostly
invested
and
the
most
challenging
actually
because
edge
computing
could
be
everything
his
iot,
his
security.
His
workload
distribution
is
several
layers
across
across.
C
B
C
It's
not
managed
openshift.
We
want
to
have
control
of
the
openshift
platform
on
the
cloud,
because
we've
got
the
strong
skills
at
the
moment,
so
we
wanted
to
have
the
freedom
and
the
opportunity
to
showcase
different
stuff.
That's
why
we
didn't
go
for
the
managed
openshift,
but
we
didn't
go
for
plain
ibm
cloud
and
install
openshift
on
top
of
that.
B
B
C
So
the
overall
use
case
in
the
manufacturing
space
simulates
the
production
of
t-shirts,
something
simple
that
could
be
challenging
from
the
workload
implementation
as
well,
because
you
have
to
simulate
several
layers
and
you
have
to
simulate
machineries
producing
t-shirts
in
phases
in
steps.
So
we
identify
steps
as
weaving
the
t-shirt,
coloring,
the
t-shirt
printing,
something
on
top
of
that,
for
example,
and
last
but
not
least,
the
packaging.
So
for
each
and
every
stage
the
edge
device
simulates
the
production
and
sends
the
data
to
the
factory
for
validation.
That's
simply
it
so.
C
We
simulate
factories
aka
facilities
where
several
machineries
they
take
care
of
the
t-shirt
production
using
through
through
the
the
phases
I
just
mentioned,
and
of
course
everything
is
controlled.
Each
and
every
facility
or
factory,
which
is
this
exact
area
here,
I'm
I'm
actually
showing
on
the
screen,
is
controlled
by
the
data
center,
so
one
data
center
controls
more
facilities
and
in
each
and
every
facilities
you
have
one
factory
controller
or
facility
controller
and
several
machineries.
C
C
Of
course,
the
community
provides
with
a
jfrog
repository,
so
we
store
there
all
the
helm,
charts
and
the
common
java,
so
maven
artifacts
that
we
use
and
we
deliver
and,
of
course
we
have
a
quay.io
account.
That
is
helpful
when
you
want
to
test
directly
the
whole
environment
on
your
machine
directly
without
compiling
everything
beforehand.
B
B
I
would
like
to
remind
the
people
attending.
If
you
have
any
question,
please
send
in
the
chat
we
will
bring
to
the
to
the
to
the
show
we
will
answer
we
can
live.
I
you
know
what
I
I'm
very
interested
about
this
architecture,
because
there
are
single
node
open
shift
in
between.
So
if
you,
if
you
come
back,
there's
the
rail
for
edge,
so
the
the
let's
say
the
far
edge
part,
then
there's
the
single
node
open
shift,
which
would
be
this
one.
C
C
On
the
other
hand,
after
each
and
every
validation
of
each
and
every
stage
for
each
and
every
t-shirt.
The
validation
service
here
sends
data
back
to
the
time
series
database
through
the
streaming
service,
which
is,
of
course,
amq
stream,
aka
kafka
in
the
in
the
upstream
version.
So
that's
something
standard.
C
Right,
certainly
use
case
blueprint
means
giving
standards
to
pieces,
and
it's
considering.
We
are
passionate
about
the
divide
and
conquer
approach.
Right.
You
have
a
big
problem.
You
create
a
blueprint
for
that.
But
then,
as
soon
as
you
go
deeper
into
the
details,
you
want
to
elaborate
or
apply
blueprints.
C
So,
just
to
give
you
an
overview,
we
don't
just
use
amq
streams.
We
don't
just
use
openshift
or
single
node
openshift
for
red
for
edge.
We
use
lots
of
different
technologies
that,
of
course,
are
certified
certified
on
the
radar
platform
that
our
are
come
from
our
technology
partners,
so
we
use
search
manager.
C
We
have
from
red
at
amq
broker
and
also
the
again
the
hardware
underneath
starting
from
the
edge
device
to
the
platform
are
come
from
our
oem
partners,
our
technology
partners,
who
do
actually
quite
a
lot
of
work
to
make
everything
certified
fitlife2
hardware
is
certified
on
red
for
edge.
We
are
making
sure
that
the
knack
we
are
using.
F
B
Yeah
I
would
like
to
ask
to
jeff
and
mario,
since
they
jeff
was
the
developer
and
going
into
the
platform
might
the
same
way.
What
did
you
like
from
the
openshift
experience
as
a
developer
as
a
let's
say,
devops
or
platform
user?
What
did
you?
How
did
you
find
because
I'm
really
interested
about
the
developer
experience
on
the
platform,
so
we
have
seen
the
architectural
review?
How
my
question
is
how
and
if
open
should
make
easier?
For
you
start
coding
start
deploying
applications
start
implementing
this
architecture.
D
I'll
go
first
on
that,
I
guess
so
what
I
I
guess
from
the
the
first
hack
fest,
just
deploying
or
creating
the
the
quarkus
and
deploying
it
out
there.
It
was
fairly
felt
fairly
manual,
but
that
was,
I
guess,
my
experience
at
the
time
and
lack
of
experience
at
the
time
and
through
kind
of
getting
involved
with
the
community
and
getting
a
bit
more
experience.
D
I
actually
started
working
with
techton
and
the
power
lines
and
deploying
the
code
that
way,
so
we
actually
put
together
a
pipelines
that
would
take
the
code,
build
the
code,
build
the
containers
and
deploy
them
for
each
piece
of
the
the
architecture
here
by
a
similar
architecture
for
the
original
covid
project
and
having
having
those
text
on
pipelines
in
place
along
with
some
github
actions.
It
meant
that
you
know
we
just
submitted
the
code
and
very
much
an
automated
ci
cd
type
pipeline.
There.
B
Cool,
so
you
you,
it
looks
you
enjoy
the
the
automation
part.
You
know,
building
the
code
up
up
and
running
that
that
is
cool
because
yeah,
I
think,
as
you
mentioned,
openshift
pipelines
based
on
tecton
is
one
of
the
coolest
thing
to
implement
the
ci
cd
part.
Now
we
we
know
that.
There's
also
that
github's
part,
I
I
I
know
matia
is
a
it's
very
enthusiastic
or
all
this
extended
automation.
F
B
Get
it
yeah
so
basically
the
the
same
feedback
about
the
the
automation
plus
right.
So
this
this
was
one
of
the
benefit
well
cool.
This
is
interesting
also
to
collect
feedback.
You
know
for
for
the
product
for
the
usage,
and
I
would
like
also
to
listen
from
matia
mattia.
You
know
it's
a
kind
of
openshift
attacker.
He
as
andrea
mentioned
it
was
one
of
the
it
was
in
charge
about
the
security
part,
the
search
manager.
Can
you
explain
us
a
little
bit?
B
E
So
what
the
idea
was
to
leverage
is
capability.
Automation,
because
set
manager
allows
you
really
easy
to
manage
certificate.
We
provide
a
standard
api
and
also
is
integrated
with
multiple
certificate
authority,
like
let's
encrypt
venaphy
and
for
our
use
case.
We
use
hashicorp
vault
because
also
as
well,
it's
quite
easy
to
do
in
deploy
actual
vault
with
openshift.
It
also
is
a
standard
for
security
perspective
and
and
as
well.
You
can
also
extend
for
support
custom
ca.
In
case
you
have
a
specific
company
certificate
authority.
E
So
what
we
do
is
to
leverage
a
cert
manager
to
provisioning
a
certificate
for
a
specific
device.
So
when
a
device
moves
want
to
join,
the
platform
is
going
to
call
our
registration
services
and
then
the
registered
to
services
was
kind
of
the
first
sale
for
the
set
manager
to
provisioning
the
certificate
for
the
device
and
in
this
way,
was
kind
of
allow
you
to
extend
from
one
device
to
thousand
device.
B
D
E
Exactly
also
you
you,
because,
if
set
manager
or
specific
that
your
certificate
can
provide
a
revoked
list,
so
you
could
always
understand
if
a
device
can
get
hacked
then
use
right
away.
You
revoke
the
device,
the
certificate
on
the
rebook
list,
and
then
this
will
stop
working.
You
know,
because
you
always
verify
if
this
device
is
trusted
or
not
from
the
broker's
perspective.
E
B
Yeah
that
that
was
interesting
also
because
the
security
aspect,
I
think
and
andre
and
all
something
to
take
in
consideration
from
the
beginning,
right,
moreover,
in
iot
or
edge
where
security
is
not
really
considered
the
first
step,
putting
that
in
place.
For
the
first
moment,
I
think
it's
something
very
useful
and
unwise,
but
andrea.
We
we've
seen
this
beautiful
architecture,
but
what
the
people
where
the
people
should
start
from
the
architecture
to
the
implementation?
B
C
C
C
We
are
working
on
at
the
moment
if
you
search
and
filter
for
manufacturing
keyword,
you
get
all
the
repositories
we
created
already,
but
as
we
are
working
on
the
implementation
which
will
be
finalized
roughly
by
mid
october,
you
can
have
so
because
we
are
adding
the
helm,
charts
and
all
the
the
security
stuff
and
everything
else
we
we
mentioned
already.
You
won't
find
whatever
we
mentioned
around
automation
and
security.
C
So
we
created
several
tools
for
compiling,
not
cross-compiling
but
compiling
the
quercus
application
natively
in
a
container
for
a
different
architecture.
So
this
is
thanks
to
ben
talyart-
he's
not
here
with
us
today,
so
he
embedded
qa
mo
within
a
container
you
starting
from
upstream
projects,
an
option
project
called
multi-arc
and
then
adding
all
on
top
of
that
all
the
stuff
that
the
workers
engineers
create
to
make
the
native
build
of
corkus
application
smoothly
and
run
directly
by
a
container
image.
B
C
In
this
case
shift
as
well
yes
cool,
so
people
can
can
join
here
if
they
want,
as
gifted
to
try
themselves
on
the
java
development
or
operators
development.
They
can
just
ask
us
and
we
will
give
them
tasks,
and
we
of
course
provide
support
in
the
purely
community
way
in
the
pure
community
way.
So
we
provide
support.
We
have
weekly
calls
of
course,
one
hour
just
like
in
a
mentoring
way.
Now
we
want
people
to
be
independent
and
to
create,
as
matthias
stated,
we've
got
some
boundaries
right.
C
C
So
let
me
go
quickly
back
to
the
architecture
and
show
you
so
each
and
every
service
could
send
events
or
telemetry
to
the
time
series
database
through
amq
streams,
but
we
just
implemented
one
so
the
telemetry
coming
from
the
validator,
so
the
valid
stage,
validation
with
successful
or
not
successful,
and
we
implemented
just
one
event
collector.
Of
course,
we've
got
the
abstract
blueprint
for
that
service
as
well.
C
So
if
someone
else
wants
to
challenge
himself
in
implementing
events
sent
from
the
registration
service
or
the
plant
manager
or
the
product
line
service
to
the
time
series
database
in
a
more
log
fashioned
way,
we
can
do
so.
Of
course
you
could
definitely
save
logs
within
openshift
using
fluentd
and
prometheus,
but
we
want
to
do
something
different.
We
don't
want
to
reinvent
the
wheel.
We
don't
want
to
overwrite
or
redo,
whatever
is
already
available
out
there,
no
in
the
internet
through
standard
demos.
C
Already
we
want
to
do
something
else,
and
we
want
to
use
cloud
native
frameworks
for
this,
so
people
who
are
not
familiar,
for
example,
with
time
series
databases
they
can
play
with
workers,
time
series,
database,
kafka
and
eventually
also
comment
native
integration
on
top
of
the
workers
framework
and
try
and
appreciate,
for
example,
the
amazing
performance
improvement
manual.
Vm
brings
to
the
workers
framework
so
that
that's
something
we
are
always
keen
to
share
with
our
contributors
and
people
interested
in
technology
approaching
the
community.
B
Cool
cool
there's,
there's
lots
of
things
that
are
very
nice,
so
there's
kafka
streaming
data
into
a
temp
series
database.
It
was
influx
db,
if
I
recall
correctly
and
then
there's
you're
using
quarkus,
quarkus
native
mandrel,
vm
lots
of
of
the
cool
feature
of
quercus,
which
is
a
java
framework
for
optimized
or
just
cloud
native
application
that
works
also
on
the
edge.
So
even
the
application
on
the
edge
is
made
with
quercus
with
a
minimal
footprint.
Firecall
correctly,
can
you
give
us.
C
C
Designed
to
provide
additional
performance
improvements
to
the
quarkus
framework,
so
what
what
actually
this
vm
does
at
build
time
is
to
pre-instantiate
all
the
objects.
The
application
would
instantiate
at
bootstrap
time
and
get
rid
of
everything
else
right.
So
that's
why
you
get
a
huge
performance
improvement
at
bootstrap
time
and
you
have
a
very
lightweight
workload.
C
The
idea
is
to
have
something
very
performant
on
the
iot
and
edge
devices
and
to
to
give
you
an
understanding
on
the
v32
device,
with
red
for
edge
and
podman
engine
on
top
of
that,
a
quarkus
native
application
spins
up
in
a
few
milliseconds
thinking
of
the
complexity
of
the
edge
machinery
simulator,
because
you
need
schedulers,
you
need
rest
apis.
You
need
and
context
dependence,
injection
and
several
other
components,
because
this
is
a
proper
enterprise
application.
C
The
bootstrap
time
is
not
more
than
20
milliseconds
compared
to
the
previous
use
case,
where
we
were
running,
compiling
natively
and
then
running
the
native
version
of
the
quercus
application
on
a
different
cpu
architecture,
so
that
was
arm
v8
64-bit
compatible.
The
application
was
then
similar
kind
of
module
set.
The
application
was
taking
not
more
than
50
milliseconds
to
start
up
and
at
runtime
the
application
was
consuming
on
the
standard
x86
or
the
fitli
2
powered
by
intel
device.
It
was
taking
25
megs,
so
at
runtime
on
the
arm
device.
C
Instead,
it
was
using
more
or
less
70
to
80
megs
of
memory.
Of
course,
this
is
not
pure
iot.
With
the
small
pieces
of
hardware
right.
We
are
talking
about
enterprise
iots
in
the
manufacturing
space,
so
the
application
should
be
a
bit
more
performant,
but
it
needs
to
do
a
bit
more
work
than
a
single
lamp,
no
in
in
an
iot
efficient
way
or
the
small
temperature
sensor
you
install
in
your
refrigerator.
C
We
have
this
kind
of
number
and
measures
and
and
boundaries
here,
but
that's
definitely
something
amazing
and
considering
the
enterprise
great
pieces
of
hardware
usually
provisioned
for
this
kind
of
use
cases.
They
are
expensive
because
they
are
enterprise
grade
and
because
of
this.
On
the
other
hand,
they
are
equipped
with
less
resources
than
usual.
Then
a
raspberry
pi
could
actually
be
equipped
with.
B
That's
thank
you.
Thank
you
for
this
explanation
because
that,
of
course,
the
edge
part
is
really
an
important
piece
of
the
wall
architecture
and
it's
cool.
This
can
be
implemented
also
with
this
java
cloud
native
technology,
which
is
quercus
and
some
optimization
for
the
native
compilation,
so
folks
we're
we're
going
into
the
end
of
this
show.
I
would
like
to
talk
with
you
hours,
because
this
is
very,
very
interesting,
but
hey
you
know
what
we
can.
We
can
invite
you
for
a
next
time.
B
I
would
like
to
thank
you
all,
jeff,
mario
matia,
of
course,
andrea
for
joining
us
today
and
talking
about
quirks
for
iot
community,
just
one
last
thing
where,
where
the
people
should
go
where
they
want
to
start,
is
there
any
mailing
list
or
email
that
can
where
they
can
reach
out
to
you?
There's
the
github
project,
but
in
the
in
the
blog
is
there
any
email
that
can
they
can
use
to
reach
out?
Everything
is
available
on
the.
B
B
Of
course,
of
course,
so
please
remember
to
register
to
the
access
and
I
will
share
again
the
access
link
in
the
chat.
So
you
you
have
it
there
when
you
open,
there's
the
landing
page
that
andres
showed
it
start
november,
the
second
until
november,
the
26th.
Please
use
that
link
to
register
to
the
act.
Fest
please
go
into
the
quarkus
for
iot
blog
project
to
get
mailing
list
email
to
start
collaborating
in
this
awesome
community.
B
Before
we,
we
stop
just
a
quick
reminder.
What
we
have
today
in
the
calendar
for
the
openshift
tv
we
have
our
level
up
show
and
then
ask
an
admin,
but
today
is
also
the
dev
nation
day.
Let
me
share
in
the
chat.
The
link
dev
nation
day
is
a
day
for
developer.
Talking
about
kubernetes
openshift,
an
old
cloud
native.
We
have
three
truck
the
the
java
truck
the
python
char,
a
truck
and
then
the
javascript
truck
lots
of
get
international
guests.
B
There
will
be
live
demos,
we
will
show
kafka,
manage
our
managed
kafka,
offering.
We
will
show
quercus
springboot,
there's
a
lot
of
technology
involved,
one
of
the
one
of
these
technologies
we
mentioned
today
with
the
quakers
variety
community.
So
thank
you.
Thank
you.
Everyone
for
having
joined
us
today,
our
next
appointment
in
this
openshift
coffee
break.
We
will
come
back
in
two
weeks.
B
So,
let's
see
when,
when
is,
is
the
october,
the
sixth
we
will
come
back
to
with
the
openshift
coffee
break,
show
in
the
wild,
enjoy
their
schedule
and
openshift
tv
enjoy
them
nation
day.
Thank
you,
andrea,
jeff,
matthia
and
mario,
yes
feel
free
to
write
in
the
chat.
If
you
want
to
ask
more
and
talk
to
you
talk
to
you
soon,
thank
you
folks,
bye,
bye,
thank.