►
From YouTube: OKD Working Group 2020 06 23 Full Meeting Recording
Description
OKD Working Group 2020 06 23
Full Meeting Recording
https://groups.google.com/forum/#!forum/okd-wg
https://okd.io
A
A
A
Welcome
everybody
happy
Tuesday,
and
this
is
the
okk
ad
working
group
meeting
you're
in
the
wrong
place,
stay
anyways
because
we
like
the
company
today,
what
we
haven't
proposed
agenda
I,
put
the
link
to
the
attendee
meeting,
notes
thing:
if
you
could
add
your
names
into
that.
That
would
be
helpful.
I
also
Maya
is
here.
Who
is
the
person
whom
I
mentioned
last
week?
Had
the
tea
arm
64
questions
use
case,
so
I'm
gonna
use
this
time
to
also
ask
her
to
explain
a
little
bit
about
what
she's
looking
to
do
and
what
she
needs.
B
So
yeah
I
think
madam
isn't
here
yet
but
yeah.
What
Vadim
has
done
is
we've
updated.
The
nightly
builds
to
be
based
off
of
0.5,
though
new
Knightley's
are
actually
built
from
the
master
code
now
and
that's
on
the
way,
ramping
up
to
the
actual
4.5
OCP
release,
which
will
be
basing
off,
which
will
be
be
using.
Ok,
DGA
yeah
as
a
base.
For
so
everything
should
all
the
platforms
should
work.
I
think
we
have
an
issue
with
GCP
currently
but
which
will
be
resolved.
B
It's
an
it's
a
known
issue
and
that
we've
got
lost
in
the
latest
rebase.
But
what
what's
new
is
the
vSphere
IP
I
install
path,
though
I'd
like
to
ask
anybody
who
has
access
to
a
vSphere
environment,
to
use
to
test
that
out
within
you
nightly,
builds
I,
think
the
next
beta,
which
would
be
because
6
I
think
it's
also
on
its
way,
which
it's
either
already
been
released
or
is
going
to
be
released
very
shortly,
yeah
and
we're
still
on
our
way
to
to
releasing
ok
DG.
B
A
very
soon,
though,
will
will
have
to
wait
for
OCP
4.5
the
release,
which
is
I'm,
not
sure,
if
that's
a
publicly
available
that
I'll
just
say
it
I
think
we're
aiming
for
a
release
on
July,
13th
and
ok
DG.
A
is
expected
to
be
released
a
few
days
after
that,
though
yeah
not
far
from
now,
and
that
is
I
think
it
for
the
update
from
my
side.
A
B
It's
not
it's:
okay,
DG,
a
is
not
gonna
happen
on
the
13th
of
July,
I,
think
Wyman;
okay,
that's
OCP,
4.5
I'm
GA,
and
then
we
have
to
back
port
a
few
comments
from
asta
on
to
the
release
4.5
branch,
making
that
the
the
F
course
4.5
branch
so
yeah,
it's
it's
going
to
be
July
13th,
plus
a
few
days,
a
few
very
short
day.
Sinfully
yeah.
D
Yeah
I
mean
that's
the
goal
every
two
weeks,
but
we
we
have
a
change
that
we
need
to
land.
That
would,
in
other
words,
there's
a
change
that
we
need
to
make
that
we
don't
want
okay
B
to
have
to
release
GA
and
then
make
that
change
for
their
users
right.
It
would
be
more
smooth
for
okay
D
if
the
GA
included
the
change
I
can
link
to
it
in
the
blue
jeans
chat
as
well.
A
B
To
put
put
a
it's
a
topic
to
that
issue,
that
is
the
the
naming
of
the
Ethernet
interfaces
we've
been
using.
The
old
schema
in
F
course
so
far
with
eth0
and
so
forth.
While
our
costs
and
new
scheme
is
actually
would
actually
be
e,
NS
192,
they
will
be
releasing
okay
d
GA,
hopefully,
with
that
new
naming
scheme
without
actually
breaking
old
installs,
that's
at
least
our
goal.
Yeah
I
hope
you
can
promise
well
I
hope
you
can
actually
do
that,
but
yeah
we.
A
F
F
B
B
So
Joseph
to
answer
your
question
on
Azure,
there
hasn't
been
any
progress
that
I'm
aware
of,
and
it's
still
sort
of
blocked
on
the
fedora
side
to
get
us
get
the
images
uploaded
to
your,
and
we
won't
be
blocking
the
ga
release
on
on
azure
and
their
ability
and
Mike's
question.
Yes,
the
the
aim.
The
goal
is
to
get
rid
of
the
of
course
branches.
Eventually,
that
will
probably
happen
sometime
after
GTA,
though
so
in
the
4.6
release.
B
We
hope
we
don't
need
F
cross
branches
anymore
for
4.5.
We
will
have
yeah
we'll
have
that
on
the
F
KERS
branch
or
yeah.
Our
release
is
because
we
will
actually
use
release
4.5
branch,
and
then
we
still
have
to
back
for
the
few
comments
which
by
then
will
be
merged
into
master
already.
So
at
least
on
the
MCO
side
in
4.6
we
won't
be
needing
the
branch
anymore
in
4.5.
We
will
still
need
it.
B
The
installer
is
still
a
little
bit
more
on
the
unclear
about
when
we
can
get
rid
of
the
branch,
but
that's
yeah
we're
not
walking
J
on
that,
and
it
should
also
happen
quite
soon.
I
expect
only
four
points
takes
time
friend
some
some
time
or
4.7
at
the
latest,
but
that's
not
not
really
yeah.
It's
not
a
blocker.
A
And
yeah
any
other
question
and
who
was
the
person
who
was
asking
for
the
vSphere
link?
Not
sure
I
gave
you
the
right
one,
but
it
was
the
one
that
I
found
searching
and
you
can
all
apologize.
Everybody
I
can't
see
the
chat
questions
when
I'm
sharing
my
screen,
which
is
why
I
keep
popping
back
and
forth,
which
I'm
sure.
A
G
A
All
right:
well,
hopefully,
we
can
get
some
vSphere
stuff
going
so
I
don't
see.
Vadim
is
Vadim
on
here,
yet
I
think
he's
still
locked
up
into
planning
meetings
for
the
day,
so
I'm
gonna
say
he's
not
he's
a
no-show
for
today,
I
in
in
light
of
the
June
13th
and
perhaps
June
July
and
July
13th
I
get
ahead
of
myself
time.
Perhaps
July
15th
release
date
of
the
GA
I
the
following
week,
whatever
that
Monday
is
I
think
maybe
another
one
of
the
ok
da
ma
sessions.
A
A
So
we
may,
if
we
may
be
able
to
go
tada
or
something
on
the
13th,
but
I'm
not
counting
on
that,
but
so
you
all
should
have
invites
in
or
the
primaries
on
that
all
should
have
invites
in
your
inbox
for
the
13th,
including
Christian,
Christian
and
Adam,
who
I
want
on
the
call.
If
you
can,
but
we
can
say
how
wonderful
left
cause
is
and
how
dependent
we
are
on
them
and
I'm.
B
A
Dusty's
on
the
cough
cause,
one
Brent,
Ben
beard
and
I
call
him.
Walters
have
all
been
invited,
so
we'll
see
if
they
all
make
it
and
that's
a
pretty
loose
form
at
Dusty's.
Just
gonna
give
an
overview
on
what
f.cuz
is
and
why
and
maybe
a
little
bit
about
the
release
cycle
I'll
see
if
I
can
get
Ben
and
Collin
to
do
a
little
song
and
dance
as
well
and
then
we'll
just
open
up
for
Q&A
and
that's
the
format
for
whatever
we
do
on
the
20th.
A
Besides
throwing
up
some
balloons-
and
you
know
announcing
using
joseph´s,
we
reworked
logo
for
us
and
figuring
out
some
stickers
or
something.
So
that's
that's
the
great
news
and
a
blog
post,
of
course.
So
there's
there's
all
that
so
today,
I
did
manage
to
get
one
person
who
had
the
use
case
to
join
us.
That
I
talked
about
last
time,
the
arm
64
years
case
so
Maya.
If
you
could,
if
we're.
A
H
No
worries
the
little
little
background,
but
I've
been
working
with
a
company
that
does
retail
analytics
for
two
years.
So
here's
in
the
stores,
what
are
they
paying
attention
to?
How
do
we
grab
their
attention
controlling
content
on
digital
signage,
so
you
get
18
to
24
year
olds
woke
up,
you
show
them
content
relevant
relevant
to
them
inside
and
so
forth.
H
We've
seen
increases
in
sales
and
so
on.
The
main
problem
was:
is
that
it's
running
in
Android,
which
is
absolutely
awful
for
doing
anything
and
I've?
Finally,
gotten
my
client
off
of
Android
and
into
the
idea
of
Linux
and
taking
the
monolithic
Android
app,
which
was
a
pain
to
maintain
and
creating.
You
know
all
the
little
bits
and
pieces
that
we
have
a
camera
input,
and
then
we
have
a
an
aged
detection,
vendor
detection
attention
span
and
so
on
and
so
forth.
H
So
we
have,
you
know
a
whole
bunch
of
inputs
being
processed
by
a
bunch
of
outputs
talking
to
the
CMS,
and
it
just
seems
like
it's.
Oh
right.
This
is
a
micro-services
containerized
bit
of
architecture
thing
and
it's
it's
a
bit
more
powerful
than
your
typical
IOT
things.
This
is
the
device
that
we
run
on
that
I
spent
two
years
designing.
It's
got
a
six
collar
and
arm
64
on
it
with
four
gigabytes
of
RAM.
So
it's
no
slouch
in
terms
of
power.
H
H
H
One
of
the
reasons
we're
on
arm
is
simply
that
Intel
and
AMD
are
too
expensive,
and
one
of
our
direct
competitors
is
now
actually
one
of
our
customers,
because
their
device
cost
ten
times
ours
and
we
spent
a
lot
of
money
doing
the
cost
optimization,
so
you
know
getting
it
on
arm
getting
it
lower,
powered
still
being
able
to
provide
all
the
services
and
things
that
we
want.
You
know
this
is
this
is
like.
H
Okay,
we
take
an
architecture
that
is,
containable
is
design
of
one
scriptable
and
all
the
rest
of
it
and
we
drop
it
on
each
unit,
and
then
we
drop
it
on
a
thousand
units
or
whatever,
and
to
have
a
server-side
management
console
is
right.
All
of
the
all
of
the
devices
in
Washington
State
we're
gonna
run
a
campaign
in
Washington
State,
so
you
click
on
all
the
devices
in
Washington
State,
you
update
their
configuration,
it
pushes
out
functionality
or
content
or
whatever,
and
you
can
do
national
campaigns
or
regional
stuff.
H
Privacy
is
important
were
subject
to
Dnepr
rules
in
the
UK
I
can't
afford
20
million
per
data
breach
so
I
think
everything
properly
locked
down
I've
been
chatting
with
Peter
Robinson,
who
does
a
lot
of
the
arm
work
for
fedora
and
we've
got
a
trusted
platform
module
in
there,
so
we
can
completely
encrypt
and
own
the
boot
chains.
We
only
run
signed
images
from
the
images
that
we
sign
can
run
on
the
device
REM
you
just
can't
run
on
anybody
else's
device
and
so
on
and
so
forth.
H
So
it's
designed
with
security
and
privacy
from
the
outside
and
to
be
as
flexible
as
we
can
possibly
make
it.
The
camera
is
just
one
input:
we've
also
been
prototyping
and
playing
with
some
millimeter
wave
radar.
So
in
the
retail
space,
if
you
have
shop
displays
up,
you
can't
see
through
them
where
the
camera
can't
see
them
through
them,
but
the
radar
system
can't.
So
you
have
a
better
idea
of
occupancy
count
based
on
different
types
of
sensors
and
things
like
that
and
yeah
we've
just
started
with
arm
because
one
it
runs
Android
better.
H
Do
it's
less
expensive
that
we're?
You
know
we're
at
a
cost
per
unit
of
about
two
to
50
and
if
you
look
at
it
next
or
even
Andy's,
offering
their
device
has
started
that
we've
integrated
before
t
modem
we've
got
a
Wi-Fi.
We've
got
Ethernet
help
you
get
power
over
ethernet,
so
we've
really
made
this
thing
as
easy
as
like:
stick
it
to
a
wall
plug
it
in
and
turn
it
on.
H
However,
you
can-
and
it
just
goes
and
so
to
have
that
you
know
just
turn
it
on
and
go
and
plug
in
plain,
and
so
that
requires
a
lot
of
sort
of
back-end
coordination
but
yeah
having
the
device
register
itself
on
the
network.
The
first
time
do
all
of
its
bootstrapping
load,
its
default
configuration
all
of
that
fun
stuff
stuff
that
I
never
want
to
do
manually.
H
Ever
again,
that's
basically
where
we're
at
looking
at
the
suite
of
tools
and
following
okd
openshift,
well,
the
operator
frameworks,
although
the
bit
of
let's
ditch
docker
in
favor
of
something
more
secure.
You
know
these
are
all
the
things
that
have
been
been
drawing
me
to
openshift
and
they're
Kady
and
Diane
and
I
have
been
loosely
talking
about
this
for
a
couple
of
years
and
now
we're.
Finally,
at
a
point
where
it's
like
right,
I
need
some
infrastructure
set
up.
H
I
need
some
people
who
can
set
up
the
the
you
know
the
cloud
side
of
it
that
will
you
know
that
have
been
execute
and
deploy
hundreds
or
thousands
of
units
at
once.
Added
bonus
problems,
VPNs
for
you
know,
ten
thousand
remote
systems
doesn't
work
very
well,
say
all
the
communications
and
things
like
that.
So
a
few
challenges
left
to
be
had,
but
it
looks
like
from
a
starting
point.
Okay,
Dean
is
the
collection
of
tools
that
should
make
it
as
easy
as
possible.
H
H
So
it's
it's
getting
really
getting
a
norm,
64
build
of
it
and
then
we're
ready
to
cover
it
up
and
go
also
in
terms
of
the
weight
of
it.
We
don't
need
the
full
Kate's
distribution
and
all
the
extra
features
day.
3
looks
for
a
more
attractive
because
it's
just
that.
It's
just
what
we
need
to
run
and
because
we
are
building
walled
silos
and
loathe
Gardens,
we
can
control
what
does
and
doesn't
need
to
to
be
supported
in
that.
A
H
Happy
to
wear
the
t-shirt
too,
but
some
people
may
not
get
it
they're,
just
having
a
lighter
weight
version
of
all
the
stuff
that
runs.
You
know
a
big
heavyweight
datacenter
instances
to
be
able
to
run
on
in
164
devices,
with
a
couple
of
gigabytes
of
RAM,
16,
gigabytes
of
storage
and
still
managed
to
do
everything
that
we
want
to
do.
That's
it
in
a
large
nutshell,
any
questions
there's.
A
What's
what
we
would
have
to
slice
off
of
okay
d
to
make
a
k3
thing,
so
I'm
gonna
unmute,
because
I
can
see
that
iam
has
joined
us.
So
if
people
have
opinions,
I
have
opinions,
I'm
tired
of
mine
I
would
ask
Maya
to
come
to
share
it
here,
B,
so
that
some
more
technical
insights
might
be
able
to
join
this.
This
conversation,
so
please
Christian.
So.
B
I
I
may
just
maybe
because
container
Linux
was
mentioned,
so
the
successor
to
container
Linux
is
Fedora
core
OS,
which
we
are
facing:
okay,
Deion,
so
that's
that's
great
and
then
there's
also
stop
for
the
use
case.
I'm,
not
sure
whether
it
does
sound
to
me
that
maybe
kubernetes
isn't
really
needed
in
that.
If
it's
like
sensors
and
stuff
for
yeah
that
I
that
run
on
in
on
all
the
machines
anyway,
it's
maybe
more
of
a
provisioning
thing.
B
You
don't
and
familiar
kubernetes
is
needed
when,
when
you
need
this
scheduling
of
workloads
across
many
machines,
if
all
the
machines
run
the
same
workout
anyways,
you
don't
really
need
it.
Maybe
and
then
Fedora
IOT,
which
Peter
Robinson
does
may
be
a
great
alternative
there,
because
they
they
also
have
a
a
provisioning
system
in
place
with
the
ignition
ignition
configuration
which
we
also
use
for
okay,
Dee
and
Ossie
P,
and
they
have
a
service
called
ZZ
ray
to
to
do
that.
A
I
That
sounds
like
an
incredibly
interesting
project.
If
I
understood
correctly,
fedora
IOT
works
on
that
device,
so
we
could
use
it
instead
of
Fedora
CRA's
later
on.
It
would
be
just
a
matter
of
building
a
payload
and
we
can
reuse
OCP,
binaries,
look
maturity
of
them
cos
or
due
to
license
constraints.
Some
packages
still
have
to
be
rebuilt,
but
given
a
large
build
farm
that
can
be
done
and
once
we
got
there,
a
mass
installation
would
be
the
tricky
part
if
the
devices
have
ipmi
or
any
kind
of
remote
control
interface
supported
by
ironic.
I
We
could
use
bare
metal
ipi
schema
to
massively
provision
a
lot
of
instances
and
make
them
join
the
cluster
like
we
do
with
the
standard
machines
that
would
be
very
impressive
and
eventually,
the
all
of
the
clusters
we
create.
We
could
use
a
open
cluster
management
or
whatever
the
thing
is
now
called
from
IBM
to
control
various
clusters
and
use
cube
Federation
to
move
workloads
between
them
and
tweak
them
so
that
pretty
much
all
soli
issues
except
it
needs
to
be
done.
The
the
tricky
part
would
be
getting
fedora
IOT
on
that
device
is
so.
I
I
D
So
I
mean
I
think
there's
a
few
things
that
we
could
do.
Probably
the
first
is
we
actually
published
some
sort
of
lightweight
guide
they're
like
hey.
If
you
happen
to
have
resource
constraint,
a
resource
constrained,
you
know,
hardware
set
up,
one
of
the
things
that
are
optional
right,
I
think
that's
valuable
for
anybody
who's.
Not
even
trying
to
do
this
in
my
face
on
arm
boards
with
4
gigabytes
of
memory,
so
I
think
that'd
be
valuable.
Regarding
Fedora
core
OS,
we
do
have
a
plan
to
actually
support
a
are
64
hardware.
D
We
don't
have
a
plan
to
support
a
32-bit
arm,
but
it
sounds
like
you're
already
on
AR
64,
so
you're
good
there
right,
yeah
and
we
have
unofficial,
builds
right
now,
but
we
obviously
want
to
bring
the
other
architectures
under
the
the
official
build
pipeline
and
produce
those
at
the
same
cadence
that
we
do
the
others.
So
we
have
a
plan
to
get
there
I'm,
just
not
sure
what
your
time
horizon
is
on.
F
I
have
a
question
from
Maya
and
I.
Think
I
think
this
kind
of
I
I
think
we
shouldn't
overlook.
What
Christian
said
about
you
know
is
kubernetes
the
right
tool
for
the
right
job.
But
do
you
do
you
predict
like
meeting
the
features
that
kubernetes
is
adding
because,
like
I
I'm
struggling
to
think
like
I,
wouldn't
I
wouldn't
think
you'd
want
to
put
all
these
devices
into
a
single
cluster
which
mean
would
they
be
single
node
clusters?
And
then
the
question
is
what
what
are
you
really
getting
out
of
that
like?
C
Problems
here
is
that
without
openshift
today,
we
don't
actually
have
a
story
for
provisioning
any
of
these
systems
at
scale
like
at
all
period,
the
lack
the
only
tool
we
kind
of
had
for
this
is
being
a
Oh
elde
right
now,
because
so
once
that,
once
pulp
is
yeah
well,
we
actually
have
no
way
of
mirroring
our
pmos
tree
or
OS
trees
at
all.
We
have
no
way
of
pushing
them
out
at
scale.
We
have
no
way
of
replicating
them.
C
A
C
Does
see
you
ready
the
the
weird
name
that
I
can't
say
that
thing
does
limited
provisioning
for
it?
It's
not
quite
I
think
the
extent
that
that
Maya's
asking,
but
it
could
be
evolved
to
do
so.
We
still
don't
have
the
replication
or
the
locality
things
that
are
required
to
make
that
actually
efficient
right
now.
C
This
actually
automatically
happens
when
you
have
open
shift
clusters
and
you're
deploying
them,
because
it
will
replicate
the
OS
tree
payloads
within
the
infra
notes
and
then
deploy
them
to
all
of
the
worker
nodes
and
then
reschedule
them
and
bring
them
up
and
stuff
like
that.
There
is
no
equivalent
to
this
for
the
non
open
shift
case
right
now,
because
the
only
tool
that
did
this
is
now
AOL,
which
Pope
Pope
pulp,
was
the
only
implementation
of
a
mirroring
replicator
mass
mass.
Whatever
for
less
trees,
nobody
wrote
anything
else
and
pulp.
A
H
H
So
it
actually
lives
external
to
main
storage
and
we're
adding
functionality
to
it
to
be
able
to
scan
the
system
image
and
confirm
that
it's
a
proper
signed
image
and
if
it
isn't,
as
the
ability
to
call
home
over
the
modem
over
Ethernet
to
download
an
image
which
would
really
help
for
the
you
know,
first
provisioning
and
bootstrapping
process.
If
you
know
all
of
the
baseboards
and
say
oh
right,
I
don't
have
an
OS
I'll
go
get
one.
H
So
we're
looking
at
that
as
a
the
the
provisioning
and
and
the
management
is
really
the
biggest
problem,
and
so
whether
or
not
we
need
a
full
feature,
k3
or
kaa
is
probably
heavily
debatable,
but
we
do
want
to
be
able
to
change.
Add
you
know,
add
things
to
the
the
single
node
cluster
or
the
single
device.
Add
services,
delete
services
and
the
management
and/or.
The
monitoring
of
those
services
also
important,
because
that
determines
billing.
H
You
know
if
you're
doing
loads
of
age
detection
stuff,
because
that's
important
to
you,
you
know
we're
going
to
charge
you
for
that
and
we're
not
going
to
charge
you.
If
you
don't
care
about
gender
detection,
though
the
or
you
know
whatever,
whatever
the
business
cases
are
for
the
particular
modules
that
were
running
so
knowing
how
much
compute
that
takes
if
it's
using
the
TPU
or
not,
if
you're,
using
an
accelerated
version,
the
configurations
won't
change
dramatically.
H
You
know
they'll
change,
maybe
once
a
week
or
a
couple
of
times
a
month
so
and
there's
no,
you
know
it's
not
like
a
giant.
You
know
web
there's
no
need
for
horizontal
scaling
or
vertical
scaling.
It
does
what
it
does
so.
The
IOT
and
the
OS
trade
model
may
be
perfectly
sufficient
I'm.
So
long
as
we
can
add,
you
know
containerized
devices
where
we
don't
have
to
worry
about
dependency
clashes,
I
hate
PHP
for
all
the
different
versions
that
have
ever
come
out.
I
thought
I'm
not
really
enjoying
much
more.
H
H
H
So
the
you
know
the
provisioning,
the
scaling,
the
the
resource
monitoring
and
you
know
the
management
across
the
fleet.
It's
you
know
it's
it's.
What
Neil
was
describing
about
the
replication
and
the
getting
the
base
level
OS
installed
across
everything.
If
that
tool
is
now
disappearing,
then
that's
quite
lea.
Whirring.
A
B
Just
throw
in
some
more
context
you
to
to
really
make
it
difficult
to
follow
so
so
fedora,
IOT
and
Fedora
core
OS
related,
and
we
want
to
move
them
close
together
right
now.
There
are
some
subtle
differences,
though,
which
I'm
not
sure
how
that
would
affect
using
fedora
I
owe
tea
as
an
okay,
deep
bass,
for
example,
because
in
in
Fedora
I
owe
tea.
We
run
the
ignition
stage
in
the
real
root
on
the
first
boot,
while
in
Fedora
core
OS
and
reddit
Korres,
we
actually
run
it
in
the
inner
DRAM
ffs.
B
So
yeah
and
there
will
be
some
changes
in
the
fedora
in
in
the
Fedora
core
OS
world
as
well
to
sort
of
align
that
in
the
future,
but
that's
nothing
we
can
do
today
or
tomorrow.
It's
like
a
long-term
thing
and
I
don't
want
to
promise
too
much
here,
but
it's
definitely
on
our.
You
know
on
our
radar.
It's
just
not
something!
That's
that's
the
super
high
priority
right
now,
but
it
would
so
I'm
not
sure
how
easily
it
can
be
done
to
sort
of
switch
out
F
course
with
fedora
IOT.
B
What
if
we
have
a
once,
we
have
the
F
cross-arm
builds.
That
will
be
much
easier,
of
course,
to
to
just
use
F
course
for
that
platform
instead
of
using
IOT
I.
Think
eventually
it's
a
goal
for
us
to
not
have
separate
arm
distributions,
but
just
have
one
Fedora
I
Oh
T.
That
is
also
the
Fedora
core
OS,
but
yeah
we're
not
there
yet
so
just
throwing
that
in
there
to
make
confusion
complete
so.
A
I
think
well
on
the
13th.
We'll
have
another,
am
a
session
with
the
F
cost
folks
and
dusty
through
his,
and
if
you
want
to
reach
out
directly
to
him,
he's
the
community
manager
of
4f
cause,
and
so
it
might
be
a
good
connection
for
you.
Maya
I,
still
like
I'm
gonna,
keep
going
back
to
circling
the
drain.
A
C
A
Yes,
you
know
competing
thing,
maybe,
but
it
also
it
starts
to
inform
us,
and
maybe
what
we
can
ask
of
Maya
too,
is
to
look
at
that
and
see
what
else.
If
we've
dropped
anything,
she
might
need
for
this
kind
of
IOT
deployment
or
there's
even
more
that
we
deeper
cuts.
We
could
make
so
I.
Just
you
know,
I
think
that
once
we
get
to
GA,
which
I
know
is
you
know
not
until
the
13th,
the
15th,
the
20th
whenever
dates
now,
oh,
you
missed.
C
A
C
J
J
An
a
minimally
viable,
okay
D
would
also
make
it
make
it
more
approachable
for
folks
that
are
that
are
doing
like
code
ready
containers
right
if
we
could
build
a
code
ready,
containers,
okay,
Devers-
and
that
was
even
more
compact,
so
that
you
didn't
have
to
have
a
you
know,
an
alienware
workstation
to
run
it.
That.
D
Yeah
I
mean
there's
also
a
real
good.
You
know
community
outreach
opportunity
here
which
is
very
close
to
what
Maya's
doing,
which
is
there's
a
whole
lot
of
very
cost,
friendly
fun,
hobbyist
type
boards
like
Raspberry,
Pi
or
the
all
of
the
stuff
from
the
pine
64
folks,
you
know
if
we
could
effectively
deliver
something
a
are
64
base
that
could
run
on
something
with
with
4
gigabytes
of
RAM.
You
know,
there's
an
opportunity
there
to
bring
a
lot
of
people
in
that
might
not
have
otherwise
been
able
to
trial
Oh
Katie.
F
Yeah
I
think
you
know
I
kind
of
like
I
like
the
way
we're
talking
about
this
now
and
when
Diane
was
first
mentioning
you
know
like
what
can
we
cut
away?
My
first
thought
was:
almost:
can
we
invert
this
and
say
you
know
and
I
feel
like
this
is
something
that's
missing
in
open
ship
container
platform
as
well,
but
like
can
we
show
a
documentation
or
an
architecture
that
says
these
are
the
core
components
you
need
to
make
it,
and
this
is
how
everything
fits
together
as
you
build
it.
F
You
know,
because
even
looking
at
openshift
container
platform,
it's
it's
really
difficult
to
figure
out
like
how
do
these
pieces
fit
together.
You
know
what
is
this
operator
doing,
that
you
know
so
I
think
starting
to
build
that
map,
so
that
someone
could
build
the
core
pieces
and
then
start
to
figure
out
how
do
I
plug
this
and
how
do
I
plug
that
to
me
would
be
really
valuable
and.
H
Yeah,
no,
that
I
mean
that's
the
the
putting
it
together
for
it,
and
we
have
a
few
constraints
that
will
probably
crop
up
in
sort
of
more
IOT
or
distributed
applications.
We
need
to
speak
to
the
underlying
hardware.
You
know
we
need
to
be
able
to
talk
to
the
CSI
camera
interfaces
and
be
able
to
put
stuff
out
on
the
HDMI
output
and
with
the
the
TPU
module
or
an
FPGA.
Those
are
connected
by
a
PCIe
channel.
H
K
H
Nvidia
Dockers
been
around
for
ages,
so
you
can
run.
You
know,
docker
apps
on
NVIDIA
GPUs,
so
no
new,
but
it
is
something
that
needs
to
be
built
up,
and
you
know
the
ability
to
run
container,
apps,
coordinate
them,
update
them,
add
and
delete
them
and
have
them
talk
to
native
hardware.
That's
that's
my
starting
point
and
then,
and
then
something
and
then
a
really
nice
web
app
to
be
able.
You
know,
for
the
customer
say
right:
I
want
this.
F
A
D
C
F
D
F
D
F
H
A
In
your
dreams,
mine,
too,
the
other
news
today
that
I
was
going
to
share
with
the
group
was
the
operator
framework
finally
got
the
number
of
votes,
and
as
of
this
morning,
it
is
officially
going
to
be
an
incubated
project
in
San
CF.
So
we
got
one
last
vote
in
and
that
I
think
it
was
announced
on
a
the
toc
mailing
list.
It
hasn't
been
publicly
announced
anywhere,
but.
I
H
A
There
were
a
lot
of
roadblocks
in
the
way,
but
with
a
lot
of
patience,
we've
been
at
this
effort
to
get
it
incubated
for
I'd
say
what
is
it
June,
probably
last
October
I
think
is
when
the
first
time
I
touched
the
CN
CF
TOC
and
pushed
the
request
out
to
be
incubated.
But
it's
been
a
long
haul
and
it's
a
it's
good.
It
is
definitely
a
good
thing
for
operators
period.
It's
a
pretty
this.
J
C
I'm
not
saying
well,
but
they
and
that
sort
of
proves
that
moving
into
the
CN
CF
doesn't
necessarily
imply
that
that's
what
will
happen
right.
Yep,
like
you
just
literally,
gave
me
the
the
counterpoint.
It's
like
just
moving
it
from
from
from
data
stacks
to
ASF,
didn't
fix
Cassandra
they
they,
they
used
the
ASF
policies
to
control
it
even
further.
Now
I
expect
that
Red
Hat
is
not
so
stupid
as
data
stacks
and
will
not
make
the
same
mistake.
But
you
know
it
just
cuz.
C
C
A
Yep
but
proprietary
appearances
or
us
being
control
freaks
about
something
or
being
labeled
that
about
operator
framework
has
I
think
hindered
even
further
adoption.
So
you
know
it's
what
can
I
say
and
I'm
just
happy
that
they're
going
to
start
giving
like
a
coop
con
and
other
things
we
can
have
an
operator
con.
A
You
know
event,
you
know
stuff
like
they
have
prom
calm
and
things
like
that.
So
we
can
start
building
a
bigger
community,
more
open
community,
about
that
the
CLA
is
in
CAS
and
all
those
things
are
you
know
that's
part
of
the
CN
CF
governance
that
says:
I
can't
do
much
about
that.
So
on
that
cheerful
note
and
thank
you
for
bringing
making
it
down
or
out
of
a
good
thing
there,
Neil
I'm,
just
gonna
say
that
out
loud.
A
C
A
So
before
we
go
because
we
got
four
more
minutes
Joseph,
you
have
an
issue
and
I'm
trying
to
track
it
down
here
that
you
were
talking
about
that
you're
gonna
pop
into
their.
Do
you
want
to
just
mention
it?
So
you
get
on
the
record
with
the
recording
which
I'll
post
what
it
was
that
you
were
yeah
I'm
going
back
in
here.
K
A
Cool
all
right
well,
thank
you,
everybody
and
thank
you
Maya
for
coming.
What
I'd
like
to
do
is
I'm
gonna
put
in
the
issue
tracker.
The
idea
of
creating
documentation
on
what
an
MVP
of
okd
would
look
like.
I
think
that
it's
a
good
conversation
to
have
I'll
bring
up
I'll
mention
it
on
the
F
cause
AMA,
so
that
people
outside
of
the
universe
that
we
live
in
will
ya
thanks.
A
Christian
will
we'll
get
work
upwind
of
it
and
we'll
see
what
we
can
do
to
move
this
forward,
because
you
know
we
always
need
a
challenge
and
GA
is
next
and
theoretically,
everything
is
just
automated
after
this
right.
The
builds
just
happen.
The
feedback
comes
back,
it's
all
wonderful,
so
we
need
something
new
to
do
in
the
okd
working
group,
not
that
there
isn't
more
work
so
anyways.
Thank
you.
Thank
you.
Everybody
for
joining
us
today,
I'm
gonna.
Let
you
all
go
before
my
network
goes
down
because
it
has
been
wonky
today.