►
From YouTube: Developer Experience Office Hours: Quarkus on IoT
Description
Join OpenShift's Developer Experience experts for our regularly scheduled program filled with cloud native, Kubernetes, and OpenShift tips and tricks for developers.
A
B
B
A
B
C
A
Yes,
winter
in
italy,
I
bet
that's
beautiful
natalie,
you
have
you
have
made
it.
You
have
arrived.
Thank
you
for
joining
us
today.
Hey.
A
B
A
B
Yeah
all
right
well
yeah,
if,
if
you
are
following
along
in
chat,
give
it
give
it
a
look:
it's
available
at
developers.redhat.com,
developer,
hyphen
sandbox,
so
I'm
gonna
click
on
that
link.
I
wonder
if
I
can
do
a
share.
My
share
my
desktop.
Let's
see
if
this
oh
boy.
B
Maybe
well,
I'm
gonna
give
it
a
shot.
First,
okay,
let's
see.
C
C
A
B
A
B
A
B
A
So,
let's
so,
if
you
go
to
the
the
developer,
sandbox
page
right,
you
get
this
little
red
box
here
to
launch
your
developer.
Sandbox
for
red
hat,
open
shift,
I'm
gonna
click
that
here.
B
The
main
thing
you
need
is
a
developer
account.
A
red
hat
developer,
account
they're
free
to
sign
up
for.
If
you
already
have
a
red
hat
login,
you
are
good
to
go.
B
And
so
this
will
give
you
a
free
access
to
a
open
shift
development
cluster,
which
has
somewhat
limited
resources
available,
but
it
spins
up
really
quickly
and
lasts
a
little
bit
longer
than
what
you'd
get
from
catacota.
The
catacota
environments
are,
you
know
one
hour
limit
and
then
they
self-destruct.
B
This
will
give
you
quite
a
bit
more
time.
So
you
want
to
log
in
with
the
dev
sandbox
option,
cool.
B
No
well,
this
is
the
main
thing
I
wanted
to
show.
Basically
you
could
you
could
skip
the
tour
yeah
skip
that
tour
and
you're
right
into
the
kind
of
ad
add
new
things.
A
Yeah
so
like
feature
off,
you
go
right
like
you
want
to
add
something
from
operator
hub,
you
can
plug
it
in
right.
There
you
want
to
pull
in
something
from
your
git,
repo
or
container
image
or
just
drop
the
whole.
You
know
yaml
from
your
application
and
off
you
go
right.
B
B
So
there
are
some
limitations,
but
if
you're
really
just
looking
to
do
language
based
development
and
not
lose
your
entire
progress
every
hour
right,
this.
B
Something
that's
worth
looking
into.
I
probably
shouldn't
have
tabbed.
B
Yeah
definitely
plenty
of
solutions,
but
there's
resource
limitations
and
a
couple
other
kind
of
stipulations
on
on.
C
B
You
get
out
of
this
totally
free
service,
I
think
it
lasts,
for
you
know,
I'm
not
exactly
sure
how
long
I
I
think
they
give
you
some
some
heads
up
when
you
create
the
cluster,
but
I
think
you
get
about
a
week
or
so
there's
more
information
on
the
landing
page
that
we
linked
yeah.
E
I
think
for
the
beta
program
started
for
two
weeks
and
then
it's
gonna
be
up
to
30
days
when
it
it
goes
to
ga
30
days.
You
can
work
with
this
environment,
the
cool
thing
you
have
three
project,
so
you
start
already
from
this
in
a
mindset
of
promoting
your
container
image
across
environment.
Like
it
was
a
you
know,
you
have
the
dev
environment,
the
stage
environment.
E
Then
there
is
the
code
environment
because,
with
this
sandbox
environment
we
would
like
to
see
also
people
coding
from
the
platform
I
know
can
can
feel
like
weird,
but
it's
possible
also
to
code
here,
because
there
is
an-
and
there
is
a
already
code,
ready
workspaces
available
for
your
application.
So
when
you
start
an
application,
you
can
just
start
coding
in
it
and
testing
the
thing,
let's
say:
quoted
locally
local
to
the
sandbox
environment
and
then
promoting
your
container
image
across
all
all
the
projects.
A
B
It's
it's
kind
of
locked
down
from
the
administrator
side.
Currently
you
get
some
some
ability
to
use
operators
that
have
already
been
pre-installed,
but
you
might
not
be
able
to
add
an
operator
that
hasn't
already
been
kind
of
made
available
for
you.
A
B
A
I'm
looking
at
those
right
now
here
on
screen
right,
like
cpu,
you
know,
there's
one
memory,
512
megs
right,
like
it's
a
good
way
to
get
started
and
like
figuring
out
how
the
openshift
interface
works.
It
is
not
something
that
you're
going
to
run
your
enterprise
workloads
on
just
from
the
resource
constraints
alone,
right.
B
You
could
run
like
development
workloads,
especially
if
you're
dealing
with
a
a
small
development
size
database.
You
know
just.
B
Purposes
or
if
you're
linking
out
to
a
shared
database,
hosted
somewhere
else
right
like.
B
Be
happy
exactly
yeah,
I
think,
potentially,
you
drop
in
a
helm
chart
that
already
has
some
knowledge
of
how
to
bind
to
staging
or
something
and
you're
in
in
a
real
good
spot
with
with
this
type
of
offering.
So
it's
it's
new
we're
still
kind
of
testing
the
waters
with
this
solution,
but
we
would
love
to
have
you
give
it
a
look?
Give
us
some
feedback?
B
Let
us
know
what
you
think
and
like
like.
We
said
it's
going
to
be
expanding
over
time.
I
don't
know
if
we'll
get
to
have
a
having
like
paid
offerings
or
something
where
you
can
keep
your
environment
for
more
than
30
days.
I
think
that's
more
kind
of
out
in
the
future,
we'll
see
where
it
goes.
We
got
a
comment
in
the
chat
about
programming
on
the
platform
and
from
gnu,
pasta
and
yeah.
That's
totally.
One
of
the
things
we
recommend
on
this
show
is
doing
development.
B
That
is
highly
a
lot
of
collaboration
with
the
platform
environment
and
take
advantage
of
as
much
of
that
platform
environment
and
that
feedback
from
production
grade.
You
know
platform
info
output
all
during
your
dev
loop,
so
you
spend
less
time
making
guesses
about
how
how
production
is
going
to
perform
when
you're
developing.
B
Yep
and
you'll
you'll
should
end
up
with
a
public
url
that
you
could
share
with
in
in
any
of
your
environments.
E
Yeah,
as
you
said,
one
of
the
cool
things
is
that
your
inner
loop
runs
also
on
kubernetes.
This
is
a
kind
of
new
and
powerful.
No
you
also
your
inner
loop,
random
kubernetes,
then
also
the
outer
loop,
of
course,
but
the
inner
loop
itself
can
run
a
kubernetes,
and
once
you
start
your
application,
you
can
edit
the
code
directly
from
the
ide
inside
the
sandbox
already
installed.
It
is,
of
course,
eclipsed
in
as
the
red
dot
product
around
this.
It's
a
code
ready
workspaces
based
on
eclipse
7..
E
A
Have
too
many
email
addresses
but
yeah?
This
is
awesome
right,
like
code
ready,
workspaces
right
here
and
that's
that's
dope
and
it's
based
on
a
cliche
and
it'll
start
initializing.
As
you
know,
you
gave
it
the
credentials
you
needed
they're,
not
credentials,
but
just
you
know:
username
email,
some
kind
of
uid
creation
process
there,
I'm
assuming.
E
Yeah
this
is
the
factory
and
factory
is
a
process
around
the
code
ready
workspace.
It's
reading
the
dev
file.
We
talked
about
the
file
with
ryan
in
the
previous
office
hours.
The
dev
file
are
the
same
used
by
auto
openshift2
cli,
so
we
are
converting
to
a
new
version
of
dos
file,
which
is
the
file
number
two
version
two.
So
the
dev
file
is
really
the
docker
file
of
your
workspace
or
your
developer.
A
That's
awesome
is
this:
you
know
loading
soon,
graphic
any
cooler
I
mean
my
son
would
freak
out
over
this
right.
Like
he's
all
about
cranes
and
everything
like
this,
this
would
make
him
happy.
B
The
one
last
warning
I
have
about
this
site.
I
think
there
is
some
capability
to
if
your,
if
your
urls
or
your
workloads
are
not
being
accessed
externally
or
directly
via
the
the
ui,
I
think
we
can
potentially
idle
your
pods
and
then
bring
them
back
later
when
you
do
start
getting
requests
and
interactions.
B
So,
if
you're
expecting
a
hundred
percent
uptime,
this
is
more
developer
quality.
You
know
not
production
quality
as
far
as
the
the
uptime
and
availability,
but
it's
a
great
way
to
test
things
out
and
when
you
do
start
interacting
with
it,
you
should
get
your
services
come
back
relatively
quickly.
B
A
B
B
A
small
exception
which
might
just
be
a
timeout
or
some
other.
A
E
Yeah
one
one
cool
one:
smart
things
to
do
if
you
have
a
if
you
plan
to
use
this
massively,
is
to
pre-load
those
base
image
for
the
workspaces.
E
So
if
you
plan
to
have
a
lots
of
you
know
of
recent,
go
python.net
java,
you
preload
that
with
a
puller,
let's
say
a
demo
set
that
can
pre-load
all
the
needed
images,
so
the
developer
can
start
straight
away
almost
immediately.
Otherwise
those
images
need
to
be
pulled
from
the
red
dot
registry
or
the
grab.
E
Whatever
image
you
are
using,
and
then
you
you,
you
have
to
wait
for
this
initialization
between
the
agent
inside
the
pod
and
the
code
redwater
space
server,
but
you
can
optimize
this
time
by
pre-pulling
those
images.
A
Right-
and
you
know
just
to
highlight
another
fact
right
like
this-
is
pulling
in
a
clip.
Sha
thea,
which
is
the
in
browser
kind
of
it,
looks
a
lot
like
vs
code
kind
of
deal,
but
it
is
an
eclipse
project
that
or
the
clips
product,
I
guess,
is
the
right
way
to
phrase
it
that
is
open
source.
So
we
make
and
contribute
quite
a
bit
of
work
in
that
regard.
To
make
this
yeah.
I
don't
think
this
is
going
to
load
load.
B
An
alternative
way
of
using
code
ready
workspaces
that
we've
covered
on
the
show
in
the
past.
If
you
have
a
local,
let's
see
a
local
environment.
Am
I
saying
this
right?
I
think,
with
a
local
code,
ready
environment,
you
can
spin
up
an
embedded
cluster
running
locally
on
your
machine,
given
if
you
have
enough
system
resources
on
your
laptop
right.
A
C
A
A
B
This,
I
think
we
some
of
this
is
going
to
be
this.
B
A
Can
hit
that
you
know
if
you're
on
the
call
right
now
feel
free
or
on
the
streams
right
now
just
go
ahead
and
click
that
link
and
see
exactly
what
I
see
yeah,
I
mean
that's
pretty
cool
right.
Like
a
couple
clicks
later
and
off
you
go.
E
Yeah
cool,
you
can
also
add
the
database
at
ease
from
the
same
catalog.
So
it's
very
easy
to
get
started
for
a
from
a
developer
perspective
from
the
dev
console
in
this
sandbox
environment.
You
basically
have
all
you
need
to
start
with
the
platform
right,
so
you
have
mongodb
postgres
mysql
adb,
or
you
can
also
use
another
database
from
docker
hub,
for
instance,.
C
A
A
For
example,
right,
like
you
know,
I
have
hue
lights,
I
have
you
know
smart
devices
and
stuff
like
that.
So
you
know
I
could
totally
hack
together
something
like
that
here
and
bring
it
in
to
like
a
crc
instance
running
here
in
the
house,
or
you
know
I
do
have
a
cluster
here
in
the
house
like
a
real,
actual
server
cluster
six
node
seven
node
deal
so
yeah.
A
You
can,
you
know,
do
like
the
the
hard
work
here
in
this
interface
and
then
put
it
where
you
want
it
after
the
fact,
and
you
get
a
little
bit
more,
you
know
tinker
ability.
If
you
know
limits
have
been
set
on
things
in
your
own
cluster,
where
you're
working
you
could
probably
pre-bake
something
here
and
then
bring
it
home
and
see.
You
know
how
it
works
in
your
environment,
so
I
haven't
been
watching
chat.
I'm
assuming
everybody
else
is.
Is
there
anything
else?
You
want
me
to
show
in
the
ui
here.
B
C
B
There's
plenty
of
valid
ways
to
do
that.
It
really
depends
on
how
you're
going
to
achieve
your
best
productivity
and
best
use
of
of
your
time
so
up
to
you
to
to
help
map
that.
But
we
want
to
give
you
all
the
tools
to
line
it
up
in
whatever
way
makes
sense
for
you.
So
thanks
for
the
feedback
in
the
chat
and
yeah
feel
free
to
pile
in
more
questions.
If
you
have
any
as
we
as
we
move
along
yeah.
B
A
B
B
Next
topic
we
had,
and
you
kind
of,
were
helping
me
like
lead
us
towards
it
a
little
bit
setting
up
if
you
did
have
iot
devices
on
your
local
network,
we
actually
have
a
next
topic
coming
up
is
to
introduce
the
q
iot
project
and
andrea
and
natalie.
I
think
we're
going
to
lead
that
bit
if
you
all
are
up
for
that.
E
Yeah
sure
I
was
pleased
to
invite
andrea
to
talk
about
it.
We
we
did
a
a
twitch
session.
Last
time
with
chris
we
talked
about
the
act
fest
and
the
result
with
winners.
So
we
won't
like
to
do
today
with
andrea
to
wrap
up
and
see
what's
falling
on
after
the
acquist.
What
is
going
on
on
the
project?
Andrea
and
you
can
you?
Can
you
recall
to
the
people?
What
is
the
quarkus
iot
project.
D
Thanks
natalie,
so
the
quercus
for
iot
hackfest
was
a
marketing
and
enablement
event.
We've
been
running
in
september
so
from
september
last
year
to
october,
and
the
the
goal
of
this
long-term
enablement
event
was
to
give
to
our
ema
partners
the
the
skills
to
to
implement
the
workload
on
the
iot
devices
and
at
the
edge
using
using
our
reddit
products
and
indeed
with
with
quarkus
framework,
and
this
event
was
built
on
top
of
something
new
we
implemented.
D
So
that's
a
big
change
from
the
from
the
edge
computing
and
iot
perspective,
because
that
reduces
dramatically
the
amount
of
resources
required
by
the
devices
and
low
level
edge
servers
to
to
to
to
to
run
on
the
servers
so
to
run
the
workload,
and
that
was
amazing
from
the
business
perspective.
The
enablement
was
being
quite
successful.
More
than
expected,
honestly,
because,
usually
when
we
run
enablement
events,
they
are
part
marketing,
yes,
partially
marketing,
but
more
likely
even
enablement
events.
D
We
don't
expect
an
immediate
return
of
the
investment
we
did
so
after
one
week
of
enablement
through
webinars
and
three
weeks
of
this
kind
of
challenge
the
activists
brought
to
the
partners.
We've
got
already
the
three
winners
running
projects
using
our
methodology
and
the
technology
we
and
the
the
skills
we
gave
them
now.
D
No
well,
they
are
building
the
broad
environment,
so
they
started
some
projects,
so
they
had
enough
material
and
skills
and
knowledge
and
understanding
of
the
solution,
not
just
the
workers
framework
right
in
iot
and
edge
computing
solution
to
propose
to
their
end
customers.
So
they
are
actually
running
the
projects
and
I
guess
they
will.
They
will
make
it
sooner
or
later.
I
this
year.
D
Lucky
lucky
us
edge
computing
projects;
they
are
slightly
different
from
the
from
the
digital
transformation
project.
So
so,
when
you
want
to
implement
something
at
the
edge
or
involve
iot
device
implementation,
it's
this
is
something
new
you
design
from
scratch,
right,
digital
transformation
or
replacing
the
existing
infrastructure
with
openshift
and
cloud
native
infrastructure
and
workload.
It's
it's
much
much
more
complicated
and
expensive
in
terms
of
resources
and
time
and
and
that's
from
the
business
perspective
from
the
technical
perspective.
D
Thanks
to
the
openshift
tv.
Thanks
to
other
speeches
we
delivered
in
the
last
month,
we
attracted
enough
people
to
form
a
community
so
wow.
This
is
not
just
the
qaot
hackfest.
Now
it's
the
qatar
project,
so
the
all
the
code
natal
and
myself
and
a
couple
of
other
guys.
That's
right
me
during
the
the
implementation
of
the
first
version
of
this
project.
We
we
we
donated
everything
to
the
community.
D
Now
we've
got
a
project
on
github
and
now
the
source
code
is
available
to
everyone,
with
several
people
bringing
new
ideas
to
make
the
the
project
and
the
environment
we
implemented
initially
more
iot
compliant,
meaning
we
are
adding
some
strong
and
dynamic
security.
D
We
are
adding
some
components
mainly
to
the
data
center
side
of
the
of
this
project,
to
to
manage
data
differently,
to
include
more
protocols
that
help
iot
devices
to
communicate
easily
with
with
the
the
workers-based
services
running
on
the
data
center.
So
it's
getting
bigger
and
bigger,
still
looking
for
a
nice
and
easy
way
to
have
fun
together,
so
we
haven't
got
a
hard
roadmap,
because
this
is
a
community
project.
We
are
not
meant
to
create
any
project
for
red
hat.
C
D
The
to
the
source
code
and
the
knowledge
we
can
share,
so
we've
got
people
who
are
always
happy
to
play
with
small
single-board
computers
and
and
if
you
create
stuff
out
of
an
arduino
board
or
just
printing
their
own
and
and
flashing
stuff.
On
top
of
that,
so
it's
nice.
It's
amazing.
D
Yeah,
I'm
happy
to
share
the
link
guys
if,
if
you
want
all,
I
know
if
you
share.
E
D
Well,
the
community
is
actually
forming
no
and
we
are
working
on
the
you
know,
the
the
web
pages
and
and
some
more
introductory
documents
and
and
papers.
In
order
to
give
this
this
community
a
kind
of
goal
and
and
then
we
will
work
on
the
roadmap
because
we
we
want
to.
D
Of
course
we
want
to
improve
the
existing,
but
we
want
to
cover
several
additional
areas.
So,
just
having
so
the
just
as
a
reminder,
the
the
basic
technical
project
out
of
the
qit
hackfest
was
implementing
a
some
weather
station
or
we
call
the
measurement
station
that,
thanks
to
some
sensors
directly
connected
to
the
raspberry
pi,
could
collect
telemetry
around
pollution
and
gas
and
send
them
to
the
to
the
data
centers
to
the
central
servers
for
for
elaboration.
So
we
have
dashboard
and
stuff
like
this.
D
We
we
are
keen
and
we
are
looking
forward
to
cover
more
use
cases
in
the
manufacturing
area
in
the
energy
and
utility
area,
so
the
the
to
to
fall
into
the
same
goal
of
attracting
more
people
with
several
skills
and
expertise,
so
that
that's
kind
of
important.
You
know.
A
Yeah,
it's
very
young
and
like
this
is
a
great
opportunity
for
anyone
watching
out
there
to
get
in
on,
like
the
ground
floor
or
something
right
like
I
can
foresee
a
future
when
there
is
a
sensor
developed
to
detect,
covet
19
in
an
area
right,
and
we
will
have
these
sensors
spread
out
in
a
large.
You
know
way
to
some
extent
right
like
I
can
see
a
future
like
that
where
it's
like.
Okay,
this
room
seems
to
have
somebody
in
it
that
has
coveted
19
right.
A
You
could
just
cause
from
the
air
detection
system
right
like
that,
would
be
an
amazing,
iot
usage
right
to
do
something
like
that,
like
you
just
put
this
thing
under
your
lobby
and
you're
good
to
go
right
like
that,
would
be
awesome
and
you
could
see
outbreaks
kind
of
happening
in
real
time
at
that
point
and
kind
of
respond
effectively
in
that
nature.
Right
like
this
is
like
me
just
like
really
riffing
off
the
what
is
possible
kind
of
thing,
but
yeah,
that's
possible
here.
E
That
would
be
the
greatest
invention
of
the
humanity
in
this.
In
these
years,
you.
A
I
mean
we
have
so
many
things,
and
I've
worked
on
some
of
these
projects.
Right
that
sense.
You
know
chemical,
biological,
whatever
you
know,
you
know
some
kind
of
leak
of
some
sort
right,
and
you
know
radon,
for
example,
right
like
there's
radon
tests,
for
you
know
you
could
just
put
a
piece
of
paper
in
the
room
and
you
get
a
result
back.
You
know
once
you
send
it
to
the
lab.
A
Well,
if
the
you
know
you're
just
detecting
the
presence
of
a
certain,
you
know
you
know
droplet
essentially,
I
feel
like
that
is
entirely
possible.
Yeah,
the
droplet.
E
Is
definitely
possible
for
the
droplets
itself.
I
think
a
sensor
with
humidity
temper,
temperature
and
quantity
of
humidity,
then
let's
say
drop
the
smallest
droplet
can
be
also
that
fine,
so
you
can
assume
the
droplet
could
contains.
Also
that
so
you
can
study.
Also
the
air
movement
for
indoor
there's,
a
science.
C
E
E
So
the
expectation
is
that
the
world
is
more
polluted
because
no
limitation
has
been
so,
and
this
is
a
bad
for
also
the
health,
not
only
the
communities.
That
is
a
in
an
issue.
It's
a
big
issue,
but
if
we
start
having
a
more
polluted
city
is
another
issue.
So
it's
interesting
also
this
research
made
by
the
the
actress-
and
I
would
like
to
measure
in
milan
or
my
city,
how
the
pollution
is
going.
I
think
it's
going
very
bad,
but
I
can
contribute
to
the
dashboard
with
right
with
such
data
yeah.
A
D
Yeah,
well,
let
me
tell
you
chris,
that
this
is
a
small
project
right,
so
we
we
are
trying
to
emulate
some
very
big
network
of
sensors
around
the
world,
so
there
are
two
or
three
already
existing
big
networks.
One
of
them
is
built
around
the
world
health
organization.
So
it's
it's
something
we
are
doing
in
in
a
very
small
portion,
but
still
we
demonstrated
that
thanks
to
quercus
technology
and
rada
technology,
the
java
programming
language
is
not
a
remote
opportunity.
D
Now
we
can
challenge
easily
go
python
and
the
other
competitors
in
terms
of
microservices
and
cloud
native
frameworks.
So
that
was
the
big
big
big
news,
and
this
happens
natively
on
armed
devices
right,
if
you
think
of
what's
going
on
in
the
hardware
world,
with
nvidia
acquiring
the
arm
company
and
with
with
apple
working
on
its
own
cpu.
Alright,
that's
going
to
change
and
we
are
demonstrating.
The
workers
can
easily
run
on
top
of
those
cpu
architectures.
B
Do
you
have
any
more
requirements
around
the
kind
of
hardware
runtime?
I
think
java
and
quarkus
can
potentially
be
the
the
platform,
but
I
heard
you
mention
arduino.
Is
there
any
currently
anything
like
fedora
iot
or
any
os
image
that
you've
standardized
on
for
these
embedded
platforms?
D
D
So
arduino
actually
can
run
quercus
applications,
but
not
native
because
arduino,
I
guess
it's
32-bit.
As
far
as
I
recall
so
yeah,
every
every
every
kind
of
so
64-bit
gives
you
an
excellent
performance.
D
32-Bit
gives
you
a
kind
of
very
good
performance,
but
you
know
running
natively
is
quite
different
right,
and
so
you
can
add
so
I'm
working
on
other
use
cases.
I
I'd
love
to
implement
in
the
project.
For
example,
I'm
working
on
some
object
motion
recognition
based
on
java
and
using
the
nvidia
jetson,
the
latest
version.
Still
you
need
an
excellent
and
stable
and
mature
operating
system.
So,
yes,
we
used
for
the
standard
implementation
for
our
iot.
D
Don't
forget,
feather
variety
will
be
streamlined
to
rail4th,
so
there's
going
to
be
an
enterprise
version
of
it
soon.
So
it's
been
announced
and
we
want
to
give
a
stable
official
and
enterprise
version
to
to
what
we
have
done
so
yeah
fedora
iot
includes
natively
the
container
technology
because
quark
is
native
means.
You
run
quercus
native
application
within
a
container,
so
we
are
using
pokemon
as
a
container
technology
actually
keep.
C
D
And
light
there
you
go
yeah
completely
stable,
quite
mature
and,
and
this
comes
from
the
community
to
become
an
enterprise
and
stable
from
the
business
perspective
and
fully
supported
version
of
of
of
it.
Simply
nice.
E
And
I
have
a
question
just
to
join
the
argument
of
today.
If
I
am
excited
about
this
idea-
and
I
want
to
get
started
so
I
have
the
artwork,
can
I
can
I
start
with
the
send?
Do
you
think
I
can
start
with
a
sandbox
to
put
my
back
end,
the
the
dashboard
all
the
quarkus
iot
code
and
start
trying
it
with
developer
sandbox.
D
I
guess
so:
yes,
yes!
So
when
I
started
implementing
the
project,
I
made
it
possible
to
play
with
the
raspberry
pi
without
sensors,
so
you've
got
an
emulator
if
you
are
not
keen
to
spend
50
plus
euros
to
purchase
the
sensor
board
to
connect
the
raspberry
pi,
everything
runs
within
a
container,
so
you
can
easily
use
a
sandbox,
because
the
total
amount
of
memory
for
the
services
running
on
the
server
side
is
a
couple
of
gigs
of
ram
not
more
including
the
the
integration
layer.
D
So
the
the
the
tool
you
need
to
expose
mqtt
endpoint
to
make
the
raspberry
pi's
so
that
the
stations
send
the
telemetry
to
the
data
center.
The
internal
data
flow
through
through
kafka
and
the
database
implemented
using
in
the
first
version
mongodb
and
all
the
other
services
that
make
the
system
scalable
and
perfectly
integrated.
They
are
based
on
workers.
So
it's
it's
quite
cheap
to
run.
D
Everything
is
is
open,
source
everything
can
be
found
in
the
community.
We
are
implementing
the
guides
as
well,
for
the
developers
who
are
keen
to
join
or
just
to
try
without
contributing
to
the
project.
So
more
more
info
and
more
news
are
coming
are
available.
Let
me,
let
me
say
guys
the
first
outcome
of
the
community
and
I'm
very
proud
of
it-
is
the
opportunity,
for
example,
and
that's
certified
now
the
opportunity
to
compile
quarkus
native
application
for
arm
directly
on
a
standard,
intel,
cpu,
meaning
just
imagine.
D
You
can
easily
make
openshift,
compile
the
application
supposed
to
run
on
armed
devices,
make
them
available
push
them
into
your
enterprise
repository
and
then
communicate
the
raspberry
pi's,
a
new
image
is
available
and
the
raspberry
pi
will
automatically
download
the
image
without
the
need
of
having
an
arm
server
dedicated
to
the
compilation
process
for
those
images
to
be
deployed
on
the
iot
devices.
So
that's
amazing
and
we
did
it
using
standard
container
images,
the
uv
images
for
for
from
from
red
hat
and
basic
standard
glpn.
D
So
this
is
something
the
community
created
to
make
everybody,
including
the
enterprise
companies
automating,
the
generation
of
the
official
images
for
the
devices-
that's
that's
simply
fantastic
and
that
reduces
the
the
costs
of
automation
and
provisioning
of
the
images
for
for
the
iot
devices.
That's
quite
cool
and
that's
officially
open
source
as
well.
B
I
put
a
I
put
a
link
in
the
chat
to
a
provisioning
service
that
I've
used
in
the
past
in
in
conjunction
with
fedora
iot.
So
if,
if
you're
interested
in
trying
fedora
iot
and
setting
up
devices
on
your
home
network,
there's
a
service
that'll
help
load
your
ssh
keys
and
an
ignition
script
onto
that
raspberry
pi
I've
used
it
in
the
past.
B
It's
still,
I
think,
in
development,
but
that
ignition
script
could
load
up
podman
and
start
your
workload
and
potentially
be
used
to
kind
of
bootstrap
those
hardware
devices.
So
another
thing
to
to
look
into,
I
added
a
link
in
chat
for
you
all.
That's
awesome!
Thank
you
for
that.
D
Actually,
ryan,
that's
very
important
because
unless
you
have
a
linux
based
host
machine
to
flash
directly
using
the
tools
provided
by
fedora.
A
Dock
yeah,
no,
I
mean
this
is
great,
though,
like
I
appreciate
how
much
time
we
put
to
this
right,
like
the
sandbox
important,
the
qiot
project.
Important
right,
like
these
are
things
that
are
going
to
help
people
in
the
long
run
right.
So
it's
I'm
very
happy
that
we
talked
as
long
as
we
did
about
both.
B
And
I'm
really
excited
about
projects
that
people
can
do
on
their
own
in
their
house,
since
I'm
stuck
in
my
house
with
with
you
know,
I'm
like
what
can
I
do
to
try
to
hack
my
environment?
Hopefully
other
people
are
also
inspired
by
similar
tasks,
so
we'll
try
to
have
more
on
this
topic
in
future
sessions
on
the
office
hours
I
have
next
up.
B
B
If
you
are
not
already
up
to
speed
on
k-native
and
serverless
technologies,
I
highly
recommend
giving
this
link
a
review,
and
especially
before
our
upcoming,
let's
see
when
we
have
it.
If
we
have
a
date
here,
it
looks
like
we
will
be
having
a
k-native
deep
dive
with
paul
mori
from
red
hat
on
february,
2nd.
B
So
we'll
we'll
give
you
another
reminder,
but
yeah
definitely
take
a
look
at
the
kind
of
introduction
and
ask
me
anything
around
on
openshift
commons
before
we
jump
into
the
expert
level
presentation
with
paul
yeah.
A
Paul's
the
k-native
lead
here
at
red
hat
and
also
a
good
friend
of
mine,
so
yeah
it's
going
to
be
awesome
to
have
him
on
the
show
talking
about
canada
and.
A
That's
right:
I
should
throw
some
oddball
questions
at
him.
He's
actually
working
on
some
code
to
mess
with
you
lights
in
the
house
kind
of
deal,
so
that
should
be
interesting
like
he
and
I
will
both
be
able
to
run
it
if
it
all
works,
so
I
might
be
over
promising
here.
It
might
just
be
terrible,
we'll
see.
B
Anyway,
exciting
topic,
guest
speaker,
who's
very
active
in
the
upstream
community.
So
keep
that
in
mind
we'll
have
it
on
the
calendar
of
events.
So
take
a
look
at
the
calendar
at
openshifttv.
You
can
add
it
to
your
own
set
of
calendars.
If
you
are
inspired
to
do
so,.
A
Yes,
definitely:
click
that
plus
on
the
bottom
right
there
and
add
it
to
your
calendar
and
I'm
sorry
restreambot
is
being
a
little
spammy
today.
That's
sorry.
B
Deep
deeper
dive
than
what
we
did
on
the
developer
sandbox,
so
if
you're
interested
in
much
more
detail
around
that
topic
definitely
come
back
on
thursday
10
a.m.
Eastern
time
for
much
more
information
about
the
dev
sandbox
and
how
that
project
is
likely
to
progress.
A
Yeah,
I've
already
put
that
as
a
scheduled
event
on
youtube.
So
if
you
want
to
watch
it
on
youtube
or
just
tune
in
here
on
twitch
facebook,
wherever
you're
at
right
now,
you
know
same
place
kind
of
deal.
B
Oh,
oh,
I
was
going
to
say
the
other.
Only
other
thing
I
have
left
on
the
lineup
for
today
was
to
go
through
a
I
wanted
to
get
feedback
from
our
viewers.
Let's
see
how
many
viewers
we
got
today
in
chat,
42.
A
A
B
Well,
for
the
folks
in
chat
and
I'll,
probably
post
this
online
later
we're
very
interested
in
hearing
more
about
what
you
would
like
to
see
in
these
office
hours
sessions
in
the
past,
we've
had
a
variety
of
topics.
One
of
them
serena,
is
here
all
the
time
showing
us
upcoming
features
from
the
the
future
of
what's
what's
coming
down
the
engineering
pipeline
for
us
what's
what's
coming
up
soon,
so
that's
a
reoccurring
topic
that
we
we
have
been
focused
on
quite
a
bit.
B
I
have
that
in
the
list,
if
you're
enjoying
that
give
it
a
a
high
score
on
the
on
the
list
of
your
preferred
topics.
Other
things
I
listed
in
there
kind
of
just
getting
started
with
specific
languages.
B
I
didn't
really
give
you
much
choice:
to
choose
a
specific
language,
there's
just
a
category
for
getting
started
with
languages.
If
there's
a
particular
language
that
you
really
want
to
see,
put
it
in
in
the
fill
in
the
blank
section
at
the
bottom,
and
let
us
know
what
particular
language
in
addition
to
marking
that
category
as
one
that
you're
interested
in.
B
Let's
see
other
topics
I
had
on
there
console
customization
contest
was
one
of
our
big
most
watched
shows
last
year.
So
let
us
know
if
that
was
a
crowd
favorite.
From
your
perspective,
we
could
definitely
do
more
kind
of
contests
where
folks
are
encouraged
to
come
on
and
share
what
they've
built.
I
think
that's
a
I
don't
know.
B
I
always
enjoy
lots
of
crowd
interactions,
so
I
don't
feel
like
I'm
just
stuck
in
my
house
thanks
again
to
folks
in
chat
for
keeping
things
active
for
us
and
let's
see
I'm
going
to
pop
open
that
form
and
take
a
look
see
if
there's
anything
else.
I've
left
out
deep
dive
into
specific
technology
stacks
so
next
week,
paul
mori
with
k,
native
and
server-less
another
option
we
have
is
interactive
workshops,
so
we've
done
in
the
past.
B
First
hundred
people
all
get
seats,
virtual
seats
and
here's
your
user
account,
let's
all
mark
march,
through
a
introduction
to
kubernetes.
Since
we
have
less
than
100
people
in
chat
today,
everyone
everyone
could
get
a
free
seat.
You
know
right,
so
that's
something
we
could
also
consider
doing
definitely
give
us
feedback
in
the
form.
We'd
love
to
hear
what
you're
interested
in
and
what
you've
been
enjoying
so
far.
A
B
A
B
My
initial
thought
was:
don't
use,
serverless
use
just
batch
jobs,
use
the
jobs,
extract,
abstraction,
yeah,.
E
And
I
I
think
you
should
do
a
kubernetes
job
just
because
you
are
violating
the
paradigm
if
you
do
this
with
serverless,
because
serverless
is
a
best
effort
by
definition.
So
you,
if
you
rely
on
backup,
I
think
you
you
will
you
want
to
rely
on
backups,
you
want
them
consistent,
yeah.
Those
functions
are
best
effort,
let's
say
so
in
the
party:
there's
no
guarantee
that
there
will
go
and
they
will
finish
you
have
to
care
about
it
when
you
start
the
function
and
when
you
gather
the
results.
E
If
everything
is
wrong,
you
have
to
restart
the
function.
So
I
don't
think
this
is
a
consistent
way
to
do
backup
so
better
much
better
doing
rely
on
kubernetes
jobs,
because
the
kubernetes
scheduler
will
control
that
the
job
is
executed
at
the
end
and.
E
Exactly
and
on
you
know,
when
you
think
about
the
serverless
or
function
as
a
service
on
a
big
memory
pressure,
those
functions
can
be
killed
because
the
paladins
say
that
is
not
important.
The
function
itself,
it's
important
that
you
can
scale
them
up
massively
when
needed
asynchronously,
so
they
can
can
be
killed
by
the
scheduler.
If
there
there's
some
memory
pressure.
A
Right,
like
of
all
the
sudden,
somebody
stands
up
a
job
and
it
sucks
up
too
much
memory.
Those
serverless
functions
are
like
well
we're
just
gonna
hold
off
for
now,
or
get
de-prioritized
completely
and
just
die
so
yeah
like
if
your
environment
is,
you
know
very
lightweight,
maybe
you
could
get
away
with
it,
but
I
wouldn't
recommend
it
right.
C
A
Yeah
cool
and
always
there's
you
know,
openshift
container
storage,
which
has
a
lot
of
that
functionality.
You
just
kind
of
built
right
in
you,
just
tell
it
where
to
go,
dump
things,
and
that
is
all
there
for
you
yeah.
So
if
there's
no
more
questions,
I'd
like
to
wrap
just
a
little
early
today,
so
I
can
hop
over
to
the
openshift
commons
briefing
which
is
going
to
be
talking
about.
I
think
windows.
Containers
today,
is
what
it
is:
double
checking
yes,
windows,
containers
and
that's
a
hot
topic
on.
A
Too
so
yeah
anybody
got
anything
else
for
the
call
or
for
the
audience
before
we
jump
off
here.
Thank
you
to
everyone
that
joined
the
call
and
experienced
this
live
stream
with
us.
I
really
appreciate
the
audience
as
always,
so
thank
you
very
much
and.
B
Special
thanks
to
andrea
for
joining
kind
of
with
the
short
notice
great
to
have
you
on
today.