►
From YouTube: 2020-01-14 Rook Community Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Okay,
the
recording
has
started-
and
this
is
the
January
14th
to
2020
Brook
community
meeting
the
first
community
meeting
of
the
new
year
here.
So
let's
go
ahead
and
get
started
like
we
normally
do
with
a
look
at
the
milestones
in
releases
right
now,
so
Travis.
Thank
you
for
updating
this
agenda
doc
this
morning.
I
appreciate
that
so
we
have.
This
is
a
link
that
we
have
in
the
agenda
duct,
but
I
wasn't
aware
myself
of
any
1.1
stuff
right.
Is
that
that's
a
old
link
so.
B
B
B
A
fairly
simple
fix:
basically,
there
was
some
change
in
permissions
of
the
directories
and
open
shift,
and
the
CSI
driver
was
not
a
well.
The
sidecar
container
was
not
running
privileged,
but
the
maintainer
was
and
the
sidecar
falls
over
and
it
needs
to
talk
to
the
main
container,
so
the
fix
essentially
is
just
to
run.
The
sidecar
is
privileged
and
there's
another
small
change
similar
to
that.
A
C
B
B
B
Some
of
them
are
just
dock
issues
like
your
security
disclosure
there,
it's
not
urgent
for
released
docking,
shoo,
there's
the
Ceph
CSI
version
detection
that
Stefan
started
a
couple
months
back
I
just
pinged
him
on
the
PR
to
see
where
we
are
with
that
did
not
in
this
meeting
is.
He
was
wait
for
his
response
there.
Unless
Blane,
you
know
of
any
progress
there,
I.
B
B
Don't
think
that's
a
merchant
issue
either
it's
really
making
sure
we've
got
a
good
support
matrix
for
CSI
and
then
the
in
the
in
progress
column.
So
the
first
one
is
the
one
I'm
working
with
Rohan
on
to
get
a
fix
in
for
the
dot
to
release,
there's
an
upgrade
issue
with
OS
DS
than
the
crush
map,
how
it
leaves
out
and
then
the
other
ones
right.
The
like
the
other
two
could
wait
if
needed
until
the
following
patch
release.
A
B
B
A
B
But
otherwise,
yeah
I
think
that's
good
for
one,
not
two
we'll
just
you
know,
get
a
release
out
around
tomorrow.
If
there
are
any
other
urgent
issues
to
get
in
well,
let's
discuss
him,
probably
in
the
dev
channel
for
slack
or
a
tag
them
appropriately
and
we'll
just
yep
we'll
go
with
that.
It
sounds
good.
B
B
Just
looking
at
our
operators
and
community
support-
and
we
really
need
support
for
the
operators,
we
have
and
that's
been
lacking
for
many
O's,
so
we
went
ahead
and
removed
it
and
there's
also
now
the
many
a
project
created
their
own
operators
separately.
So
they
they
didn't
want
to
jump
on
board
with
this
one.
Apparently,
so
we
went
and
removed
it.
B
A
And
I
think
a
greater
discussion-
that's
probably
not
in
scope
right
now,
but
something
to
think
about
is
you
know.
I
at
least
like
one
of
the
bigger
things
for
cockroach
was
how
you
know
we
still
largely
most.
The
examples,
at
least
mostly
operators
are
still
using.
The
operator
kits.
I
know
that
as
a
dependency
we've
brought
in
some
of
the
controller
runtime
stuff
and
some
you
know,
operator,
SDK
stuff,
but
that
seems
to
be
a
development
obstacle.
Still.
That's
not.
You
know
the
the
main
supported
way.
B
Yeah,
and,
and
actually
a
one
thing
I
could
have
added
to
the
notes
here-
is
that
I
in
the
last
week
or
so
removed
removed
our
dependency
on
the
operator
kit.
Like
there's
no
more
reference
to
the
operator
kid,
the
you
know,
I
was
looking
at
hey.
How
can
we
simplify
that?
Because
of
just
updating
the
golang
dependencies
is
a
real
pain
whenever
we
update
their
version
of
kubernetes
claim
so
I
just
looked
at
it
and,
though
we're
only
using
like
two
methods
from
the
operator
kit,
let's
just
bring
it
into
the
roof
project.
Yet.
A
A
B
B
B
A
A
Okay,
so
yeah,
we
can
go
ahead
and
move
on
to
the
community
topics.
I
believe
then.
So.
The
first
one
is
that
in
December
we
wrapped
up
the
security
audits
with
the
trail
trail
of
its
security
firm.
So
they
spent
a
2-person
weeks
going
through
the
codebase
doing
static
analysis,
so
dynamic
analysis,
all
sorts
of
tools,
their
code
reviews,
runtime
stuff
that
you
know
was
looking
for
security
issues
and
vulnerabilities
within
the
code
base.
A
So
you
can
easily
find
those
and
query
those
in
github
and
see
what
those
issues
are.
I
think
that
there
was
only
one
that
was
labeled
as
a
critical
vulnerability
where,
when
debug
logging
is
turned
on,
there
is
a
possibility
of
exposing
sensitive
information.
So
I
think
that's
the
only
critical
vulnerability
that
was
identified
and
that
one
has
already
been
fixed
if
I
recalls
that
right,
Travis,
yes,
that's
right
was
that
is
that
backported.
That
sounds
like
a
good
candidate
for.
B
A
A
Great,
very,
very
cool,
so
yeah.
That
was
a
great
experience
with
the
trilobites
folks.
They
are
smart.
People
definitely
have
a
good
security
background
experience
in
mindset
and
it
was
really
good
to
work
with
them,
so
that
was
cool
and
so
part.
So
the
whole
security
audit
was
part
of
the
cloud
native
computing
foundation.
Graduation
process,
so
we
are
getting
2020
has
started
and
we're
getting
very
serious
about
the
graduation
now
so
we
have
started
a
shared
dock
here
from
the
graduation
to-do
items.
A
So
all
the
to-do
items
that
we
need
to
get
through
our
tracked
here
in
this
document
that
is
linked
to
linked
to
from
the
agenda
items
here,
and
you
know
we
will
start
focusing
on
these
in
earnest
now,
because
you
want
to
target
the
being
done
before
Kuk
on
Amsterdam,
which
is
a
couple
few
months
away.
But
the
big
thing
here
for
us
that
kind
of
just
recently
accelerated
the
timeframe
a
little
bit
in
our
minds
is
that
we
need
to
present
to
six
storage
first
to
do
due
diligence
for
six
storage.
A
First,
I,
don't
I,
don't
know
how
long
that's
been
part
of
the
process,
but
it's
a
slight
surprise
for
for
me
and
Travis.
So
we
need
to
do
these
items
here.
Collect
do
the
due
diligence.
You
know
the
testimonials
security
disclosure,
like
all
these
sort
of
things
here
needs
to
be
done
before
we
can
present
to
six
storage
and
then,
after
that,
when
they've
done
their
vetting,
then
we
have
to
also
prevent
present
to
the
technical,
Oversight
Committee.
A
A
It's
it's
shared
publicly,
so
you
know
anybody
who
clicks
on
this
link
should
be
able
to
view
it
in
comments
on
it
as
well.
Well,
cool!
It's
not
public
and
publicly
editable,
but
it
is
publicly
come
really!
That's
good
cool
Jonas!
Oh
yeah!
Okay,
you
actually
added
this
slide
I'm
here
about
the
security
fix
being
back
for
it,
perfect
yeah.
A
I
saw
an
email
from
a
from
the
cloud
native
computing
foundation
just
this
week
that
google
Summer
of
Code
idea
submission
time
time
is
once
again
upon
us
seems
like
that
seems
like
a
lot
of
these
deadlines.
Just
creep
up
all
I
said
so.
We've
had
a
great
success
with
google
Summer
of
Code
for
the
past
two
years
in
a
row
now
so
I
think
this.
It
would
be
nice
to
participate
in
it
again
because
we've
gotten
some
great
contributions,
some
some
great
new
members
of
the
community,
some
great
projects
out
of
it.
A
So
you
know
we
should
take
a
take
a
take
a
little
think
here
and
see
if
there
are
any
good
fit
items,
work,
items
or
features
or
projects.
That
would
be
good
for
a
university
student
that
wants
to
get
more
into
open
source,
and
you
know,
learn
more
about
the
root
community
and
ecosystem
and
start
contributing
there.
A
It's
like
a
two
and
a
half
or
almost
three
month
process
for
them,
so
they
could
take
on
some
meaty
stuff,
but
it
definitely
has
you
know
a
ramp
up
period,
educational
period
as
well,
and
so
you
know
it's.
It's
you
can
get
a
lot
of
work
done,
but
it's
the
appropriate
scoping
is
is
definitely
wise
there.
B
A
Yeah,
the
the
mentoring
for
the
program
does
take
a
non-trivial
amount
of
time.
You
need
to
support
them
and
work
with
them
and
have
regular
meetings
with
with
the
student
as
well,
but
it
is
super
rewarding
it's
a
great
experience
to
have.
So
if
anybody
is
interested
in
that,
you
know
definite,
let
us
know
as
well.
C
C
C
Yeah,
it's
a
actually
a
PR
that
has
two
goals,
so
the
one
is
true
like
prepare
for
the
next
generation.
Always
these
to
be
ready,
and
with
that
weed
there
is
a
bunch
of
code
to
be
removed
because
the
bunch
of
code
has
been
enhanced
as
well,
where
we
make
use
it
of
more
set
volume
comments.
For
example,
in
the
old
code.
We
had
this
really
tricky
way
to
look
at
devices
using
a
LESBIAN
k,
populating
device
info
from
an
SPL
k
and
then
always
checking.
C
Does
this
device
have
a
partition
and
or
a
class
system,
or
is
it
a
partition
or-
and
things
like
this,
so
I
removed?
All
of
that
logic.
So
now
we
use
cell
Coulomb
inventory.
The
simple
human
venturi
command
is
capable
of
testing
devices
and
then
we'll
be
telling
this
in
a
really
Center
way.
Whether
or
not
a
device
is
available
or
is
a
good
candidates
to
become
an
OSD.
C
So
if
the
device
is
available,
then
the
comment
will
simply
return
true
and
if
it's
not,
then
it
forgiveness
like
ever
just
a
rejected
reason
why
it's
not
available.
So
there
is
this
part
which,
which
is
actually
extremely
helpful
when
you
boot
up
the
waste,
is
in
a
regular
way.
So
lot
of
cut
has
been
removed
from
the
paper
pod,
and
the
second
piece
of
that
change
is
is.
C
With
strapping
always
these
using
the
new
cell
volume
mode
so
now
set
volume
has
two
modes,
one
with
lbm,
one
that
is
called
the
raw
and
the
raw
mode
is
simply
consuming
the
entire
block
device
without
without
putting
any
LVM
on
top
of
the
device.
So
it's
really
like
it's
really
straightforward
were
blocked,
while
in
DB
or
all
co-located
onto
the
same
device.
C
This
is
extremely
helpful
when
you
do
some
pcs,
because
we
have
seen
many
limitations
and
we
have
hits
so
many
blockers
down
the
road
when
implementing
Oasis
in
PVC
is
because
of
LVM
and
the
way
device
are
or
basically
held
by
LVM.
So
we
had
issues
in
the
past
where
you,
you
have
an
OSD
that
is
prepared
by
MDM,
and
then
this
always
is
actually
an
EBS
volume.
You
try
to
detach
that
ammonium
and
because
the
block
is
still
held
by
LVM,
then
you
can't
really
detach
it.
C
So
because
of
that,
you
have
to
go
into
a
different
path
where
you
deactivate
the
BG
before
stopping
the
OSD,
and
then
you
can
achieve
it.
Is
it
so
this
this
made
the
world
process
really
difficult
to
maintain
in
managing
rook
and
the
structurally
also
making
use
of
the
route
binary,
and
we
also
realized
that
when
we
a
great
rook,
then
we
deliver
a
new
binary
version
because
of
the
pod
spec
has
a
new
binary
version,
then
the
deployment
gets
upgraded.
C
So
even
if
nothing
actually
changed
in
the
deployment
object
from
one
reversion
to
another,
then
all
the
Oasis
will
be
restarted
and
that's
actually
not
a
good
thing.
So
yeah
I,
guess
coming
back
to
what's
more.
Concerning
for
one
three
is
that
every
single
crystal
that
was
like
running
either
using
the
old
legacy
recordings
or
on
directories
then
won't
be
able
to
operate
anymore
as
a
transition
path.
C
We
are
I'm
currently
working
and
I'm.
Gonna
set
a
patch
like
in
a
minute
to
allow
partition
support
so
that
we
will
encourage
people
to
before
their
grid,
to
one
three
to
add
partitions
or
even
drives
it.
They
want.
But
apparently
partitions
have
come
up
in
the
discussion,
and
even
if
people
don't
have
extra
disks,
then
they
have
extra
partitions.
C
So
the
idea
would
be
to
trash
one
OSD
at
a
time
if
it's
a
directory
based
OSD
and
then
add
a
partition
in
the
cluster
CR
that
that
new
partition
will
be
picked
up
and
then
configured
and
then
USD
will
come
out
of
it
and
then
self.
We
just
do
the
recovery
in
the
background,
so
that's
our
I
guess
limited
transitions.
You
know
you,
but
it's
I
mean
that's
the
way
it
is
it's.
We
know
that
that's
gonna
be
really
destructive
and
disruptive
at
grade
four
people,
not
transitioning,
but
moving
forward.
C
A
The
best
do
you
do.
We
have
any
sense
of
like
the
percentage
of
people
that
would
be
affected
by
and
have
to
go
through,
that
that
more
manual
upgrade
path
or
is
it
like
a
pretty
small
amount,
or
we
don't
really
have
that
telemetry
to
really
have
a
sense
that
I
don't.
C
As
part
of
that,
we
will
also
like
I,
think
I
already
sent
a
message
on
the
slack
channel,
but
we
will
do
our
best,
I
guess,
I
guess
pass
the
message
on
slack
via
github
issues
or
even
tweet
about
it.
I
don't
know
so
that
people
people
are
aware
of
what's
gonna
happen
in
one
three
I
actually
think
like
we
have
a
lot
of
followers
and
Twitter's.
A
C
A
C
Right,
yeah,
and
also
like
also
just
to
give
an
extra
reason
why
we're
starting
doing
this
work
is
that
we,
like
Travis
trice,
implemented
several
you
support
like
more
than
a
year
ago,
so
this
this
should
have
also
like
even
more
time
to
people
to
transition
to
use
like
to
set
volume.
So
yeah,
it's
about
telling
us.
B
A
A
C
B
C
We
also
like
I,
guess,
perhaps
writing
a
blog
posts,
for
this
will
be
nice
and
then
we
can
tweet
it
so
that
we
have
like
okay.
This
is
what's
gonna
happen
as
a
blog
post,
because
that's
what
blog
posts
are
made
for
right,
we
don't.
We
only
have
to
do
like,
let's
say,
press
releases
with
the
blogger.
We
can
also
like
discuss
technical
subject,
also
like
upgrades
and
transitions
like
that
or
probably
a
good
place.
Yes,.
D
A
B
A
B
Yeah,
just
something
I
thought
worth
mentioning
here
so
with
you
know,
there's
been
discussion
really
on
a
github
issue
that
I
linked
there
4548
around
sub.
You
know
sort
of
longer-term
support
for
kubernetes
versions
where
kubernetes
itself
upstream
is
like
they
only
support,
fixing
or
patch
releases
for
like
the
last
three
versions
of
communities.
But
you
know
as
people
running
communities
in
production
like
they're,
not
upgrading
criminales
that
often
especially
with
downstream
versions
of
kubernetes.
Like
openshift,
you.
D
B
Exactly
so
so,
really,
if
you've
got
a
project
that
you
want
to
run
on
Trevor
at
ease,
you
need
to
really
support
to
some
degree,
the
downstream
versions
which
are
going
to
have
a
longer
lifetime,
so
in
I
mean
at
the
same
time
we
can't
support
them
forever
from
the
upstream
earth
project.
So
my
thoughts
were
captured
a
little
in
a
little
longer
writing
higher
in
this
issue.
B
B
Now
is
the
minimum
version
for
for
a
while
and
we'll
see
how
long
we
can
support
it,
but
ultimately,
I
can't
remember
the
last
time
we
had
any
breakage
because
of
something
we
didn't
look
that
we
didn't
know
was
already
limited
by
a
renée's
version
and
we
limit
rook
to
run
new
features
on
which
versions
of
communities
like
the
CSI
drivers,
like
you,
have
to
use
at
least
1.13
to
use
CSI
drivers.
We
already
have
a
code
in
place
that
restricts
that.
B
A
B
A
Day
I
can
see
yeah
and
but
that's
in
releases
only
though
right
and
their
release
branches-
yes
yeah.
So
it's
yeah,
which
I
think
that
having
yeah
yummy
you
don't
ever
really
want
a
high.
You
know
a
signal
to
preneur
a
co.
That's
not
you
know
ideal,
but
in
the
release
branches
is
the
the
time.
Then
you
would
want
the
most
likely
to
catch
anything
possible.
A
D
The
the
only
I
guess
comment,
I
have
that
you
mentioned
CSI
is
if
we
do
like.
If
we
do
keep
support
for
1.13
and
up,
then
we
no
longer
have
to
maintain
the
Flex
driver
which
could
be
like
yeah
I
mean
it
depends
on
how
much
you
know,
effort
we're
spending
on
maintaining
that
and
the
things
like
I,
don't
I
I,
don't
know
that
I
really
want
our
you
either
way,
but
that's
a
consideration.
B
A
A
A
Yeah
from
Dimitri
yeah,
so
so
we
were
I,
was
just
opening
the
floor
for
any
other
discussion
topics
in
Dimitri,
and
the
chat
has
mentioned
that
he
has
a
few
slides
that
he'd
be
happy
to
share
about
edge
vests
so
and
that's
about
ten
minutes.
So
if
there's
any
topics
for
discussion
first
well,
we
could
do
those
now
and
then
we
could
close
the
meeting
out
with
with
with
Dimitri's.
A
E
E
Alright,
alright
hi
guys
so
just
really
quick,
just
one
kinda
as
we
starting
this
new
year
by
the
way
happy
new
year.
Everyone
I
wanted
to
kind
of.
Also
tell
you
a
little
bit
more
about
what's
coming
to
us
and
kind
of
also
a
cap
on
what
what
it
is
and
how
it
is
different.
Let's
say
from
chef
I
think
it's
can
be
complimentary,
as
well
as
I
mentioned
multiple
times,
but
so
what
what's?
E
Rookie
Jefferson
adjust
as
a
recap,
so
interface
itself
supports
by
rook
and
we
provide
variety
functionality
issue
well,
we're
we
also
have
built-in
GUI
needs
and
Shirley
fizzled
means
in
a
GUI.
You
can
create
series
I'm,
not
necessarily
need
to
plumb
them
manually.
There
is
support
for
embedded
environments,
it
runs
it's
it's
implemented
in
C
itself
and
the
management
control
plane
is
implemented
in
go.
It
runs
some
very
small
footprint
devices
like
wanky
by
2d
ROM
to
CPU
cores.
It's
always
needed.
E
Obviously,
performance
is
not
going
to
be
great,
but
it's
enough
to
get
remote
locations
connected.
It
runs
in
the
clouds
on
Prime
and
H
frontiers.
It's
it
can
consume
row.
Disks
directories,
key
value
stores.
The
added
support
was
here
for
some
some
Kiwis
is
these
also
cloud
resources?
It
is
now
capable
of
running
on
top
of
s3
if
there
is
s3
provided
also
a
ministry
as
well,
while
keeping
the
metadata
in
EBS
performances
for
AWS,
you
use
case,
it
has
built-in
scale
out
and
the
first
performance
optimized
and
a
first
protocol
and
still
object.
E
Everything
what's
happening
to
edge
your
face
on
with
the
code
that
creates
a
new
worker
route
and
based
on
that
map,
a
route
which
can
be
described
as
just
one
chaudhary
signature,
which
is
64
bytes.
So
with
that-
and
it's
also
good,
like
it's
very
similar
to
the
gig
architecture-
is
that
we
essentially
providing
photons
in
a
bit
ability
and
can
connect
multiple
locations
very
efficiently.
This
is
what
the
Geo
transparency
is.
E
It's
also
energy
consistent,
and
the
way
it's
done
is
that,
but
because
of
those
milk
route,
try
signatures,
they
distribute
it
across
different
locations.
You
can
now.
You
do
not
need
to
essentially
have
a
snapshot
policies,
so
it
like,
for
instance,
a
classic
share
for
BD
CSI
snapshot.
It
means
this
is
the
belt
I
need
to
send
them
Delta
somewhere
else
in
case
of
a
Jeffers,
you
don't
need
to
send
the
Delta,
so
so
there
is
a
there's,
a
big
difference
here.
Why?
E
Because
it's
it's
blockchain
like
whatever
the
change
is
needed,
can
be
automatically
fetched
or
pre
cached
on
a
different
side.
It
it
supports
the
global
deduplication
compression
on
the
fly
so
between
the
connect,
that's
clusters,
for
instance.
It
also
provides
a
bunch
of
giro
locality
functionality
like
Frances.
If
your
data
set
scattered
across
different
clusters
can
automatically
prefetch.
All
that
is
done
under
the
hood,
so
provides
can
great
transported
to
the
application.
E
It
is
bit
like
and
blockchain
like
architecture,
and
this
is
why
it's
way
different
from
CF.
In
that
way,
it
allows
you
to
build
a
really
decent
realized
allocations
and
like
it
can
run
on
small
devices
that
can
run
on
intermediate
devices
and
provide
connectivity
to
the
cloud
it
can
run
on
top
of
chef,
and
this
is
one
of
the
things
we
should
probably
explore
to
a
greater
degree
this
year.
So
what
is
coming
to
1/3
this
year?
E
So
we
have
been
working
hard
on
our
side
and
we've
not
yet
entered
the
rook
issues,
but
we
will
be
shortly
within
maybe
a
month
timeframe.
We
are
working
on
these
new
things.
One
is
we
adding
decentralized
scale,
we're
gonna
call
this
scale?
Oh
I
know
everybody's
calling
this
D
skill,
but
for
the
lack
of
the
different
work
and
the
cool
thing
about
this
is
this
hand
position
is
quite
compatible,
so
that
means
it
isn't
breathable.
So
you
can
run
and
access
this
SQLite
compatible
interface
from
a
different
locations.
E
It
can
be,
for
instance,
different
settings.
Different
questions
give
you
example:
it
can
be
from
GCP
cloud
and
a
Tobias
cloud.
We
can
access
the
same
database
and
it
guarantees
right
equation,
consistency
at
the
same
time,
same
record,
etc.
It
can
operate
within
the
same
segment.
Ok
and
as
a
nation
visit
multiple
segment.
Multiple
setting
means
multiple
clusters,
the
other
feature
which
we're
adding
is
as
in
BCR
geez.
So
what
does
it
really
mean?
So
currently,
we
do
not
support
this
in
B
and
we've
been
asked
by
multiple
users
for
hours
to
add.
E
I
think
it's
important
for
Rukh
to
add
support
for
Windows
servers
as
well,
so
by
eight.
By
doing
that,
we
essentially
completing
the
storage
story
as
far
as
the
differences
concerned,
additionally
be
adding
support
for
a
guild,
locking,
which
is
an
efficient
SMB,
be
all
working.
So
what
does
it
really
mean?
Well,
it
provides
because
now
the
gist
key
all
this
here,
it
provides
us
a
capability
of
creating
exclusive
locking
primitives.
So
why
is
this
important?
E
It's
important,
because
some
application
cannot
build
up
the
logic
they
need
to
use
something
off
the
shelf
so
that
multiple
in
the
first
I'm
using
the
vacations
applications
can
modify
the
same
file
at
the
same
time
without
worrying
about
inconsistency,
so
that
that
is
why
this
gear
locking
is
kinda
necessary
in
the
choir
to
some
degree.
You
can
think
about
this
as
a
smart
contract
book
chain.
Can
smart
contract
functionality
to
ensure
that
whatever
you
modify
in
that
file
is
consistent
across
different
views.
So
that's
what's
coming
and
just
I
wanted
to
share.
E
E
The
cool
thing
about
this,
you
don't
need
to
worry
about
the
consistency,
so
it
takes
care
of
the
consistency
of
your
CDN
content
cloud
availability,
so
obviously
automatic
failover
can
be
done
and
so
on
a
giant
cloud.
This
is
a
big
big
thing
for
us.
We
are
positioning
interface
to
be
a
de-facto
edge,
storage
engine,
so
to
speak.
We've
registered
with
lfh
releases
with
eclipse
foundations
with
linux
foundations,
and
we
will
be
making
some
noise
this
year.
E
In
this
regard,
it's
also
contentious
Britain
volumes
across
the
clouds
ruk
you
can
from
in
Ejiofor,
so
you
can
get
all
the
functionality
out
of
the
box
yeah.
So
I
just
wanted
to
share
this
really
quick
with
you
guys
so
that
you
can
know
now
what
we're
working
on
this
year.
So
we
not
lost
while
we
are
not
very
active,
but
we
are
still
working
and
you
should
expect
more
stuff
coming
out
to
1.3.
That's.
A
B
A
E
B
E
I
was
I,
was
thinking
of
leveraging
existing
share
installations
and
kind
of
simplifying
deployment
of
Tabuk
on
top
of
existing
chef
installations
like
Francis.
If
chef
provides
stn
blog,
then
we
can
very
easily
plumb
button
code
right
and
then
connect
different
regions,
so
that
sort
of
use
case
can
always
kind
of
boggles
my
mind
and.
E
E
Yeah
I
was
I,
probably
will
add
that
that
ones
well
I
think
we
need
to
be
a
consistent.
What
we
do
with
Luke
as
far
as
the
expert
exposing
the
bucket
right.
So
we
cannot
expose
bucket
three
different
ways.
If
it
does
a
rocket
right,
there
has
to
be
one
way
and
has
to
be
fairly
the
same
across
all
the
providers
right
yeah.
A
Sounds
great
alright,
so
there
weren't
any
items
to
add,
and
then
we
got
to
see
Dimitri's
updates
on
edge
offenses
play
on
work
items.
So
I
think
that
should
be
everything
all
the
topics
for
today
and
then
we
case
I
think
we
can
go
ahead
and
adjourn
and
we
will
be
back
in
two
weeks
all
right
already
thanks.
Everybody
thank.