►
Description
Cloud Tech Thursday explores the full modern open source cloud stack, from hardware to serverless. Learn about new ideas, projects, and releases around Kubernetes, OpenStack, hybrid cloud enablement, and many other topics.
A
Good
morning,
good
evening,
good
afternoon,
wherever
you're
hailing
from
welcome
to
another
edition
of
the
cloud
native
thursday
show
here
on
openshift
tv,
I
am
chris
short
executive
producer
of
openshift
tv
and
frequent
host
and
I'm
joined
by
two
of
my
favorite
red
hatters,
amy
marrick
and
josh
burkus
amy.
Would
you
like
to
go
first
in
the
round
of
introductions,
sure.
B
My
name
is
amy
marish,
I'm
on
the
same
team
with
chris
and
I
serve
as
the
principal
technical
marketing
manager
focusing
on
openstack
in
the
open
source
world,
I'm
known
as
spots,
because
I
have
dalmatians
and
I
serve
on
the
open
infrastructure
foundation
board
of
directors,
as
well
as
the
chaos
governing
board.
Josh
up
to
you.
C
Hi
this
is
josh
burkus.
I
am
red
hat's
kubernetes
community
manager,
I'm
involved
with
both
the
contributor
experience
sig
within
kubernetes,
and
the
computer
strategy
within
sig
within
the
cloud
native
computing
foundation
and
in
both
places
have
been
pleased
to
see
kendall
several
times,
bringing
the
wisdom
of
everything
they've
learned
in
openstack
with
her
and
really
looking
forward
to
this.
B
D
D
A
lot
of
my
focus
is
on
upstream
development,
making
it
easier
for
new
contributors
to
get
in
the
door,
so
I've
done
a
lot
of
development
on
our
upstream
institute
program
and
our
contributor
guide,
I
have
also
started
working
in
the
open
or
the
kubernetes
community.
That's
been
more
recent.
Only
since
2019
I
try
to
share
as
much
of
my
knowledge
as
possible
with
the
sig
contributor
experience
and
I
try
to
keep
tabs
on
provider
openstack
in
the
sig
cloud
provider
and
kind
of
bridge
our
communities
together.
D
So
when
I'm
not
doing
all
of
this
open
source
stuff,
I
used
to
like
to
travel,
but
obviously
that's
not
a
thing
right
now
so
someday
soon.
Hopefully,
but
I
also
really
love
photography,
harry
potter
and
who
doesn't
love
doctor?
Who
and
if
you,
if
you
don't,
you
should
really
get
into
it,
because
it's
amazing.
D
But
yeah
so
openstack,
it's
it's
a
super
awesome
community.
I
have
been
involved
for
a
long
time
now
and
so
I've
kind
of
put
together
this
list
of
like
tools,
resources,
programs,
communities,
all
the
different
things
that
we
have
to
help
bring
people
in
and
kind
of,
get
them
up
to
speed
and
whatnot.
So
we
have
a
lot
of
resources
and
tools.
Obviously,
so
when
you're
new
to
a
community,
you
probably
want
to
go
look
at
like
how
do
I
get
involved?
What
what
accounts
do
I
need?
D
What
tools
do
they
use
that
sort
of
thing,
and
all
of
that
is
covered
in
our
contributor
guide?
We
have
it
kind
of
broken
up
into
different
areas
of
interest
based
on
like
are
you
going
to
go
and
program?
Do
you
want
to
do
code
and
docs,
or
maybe
you're
like
a
non-code
contributor
person
or
more
of
a
user
of
openstack
and
want
to
get
involved?
So
we
have
it
kind
of
broken
into
those
sections.
D
But
I
highly
recommend
working
through
this
whole
thing,
if
you're
interested
in
really
really
getting
involved
in
being
a
member
of
the
community
and
maybe
moving
into
roles
like
ptl
or
like
a
technical
committee
member
someday
so
yeah,
so
you
you
can
go
directly
to
the
contributor
guide,
it's
in
our
documentation
or
we
have
a
contributor
portal,
that's
kind
of
like
a
landing
spot
from
the
like
main
openstack
site.
Oh
jeez,
I
love
tabs
they're,
really
great
tab
over
nope,
not
that
one.
D
D
Several
of
them
so
like
it
I'll
like
go
into
like
the
the
groups
of
people
on
a
later
slide,
but
several
of
them
will
bring
you
to
groups
of
people
that
will
help
you.
If
you
need
the
there's,
also
the
the
infra
manual,
which
is
a
little
bit
more
of
the
nitty-gritty
details
of
like
setting
up
a
project
if
you're
interested
in
contributing
that
way.
But
most
people
aren't
really
going
to
need
that
it's
just
more
in-depth
stuff.
D
After
you
work
through
contributor
guides
our
larger
community
contributor
guide,
there
are
more
project
specific
ones
because
each
of
our
sub
projects,
the
individual
services
like
nova
and
cinder
and
manila
and
keystone.
What
have
you
they?
All
every
project
has
a
different
like
culture,
and
so
there
might
be
small
differences
in
the
processes.
How
they
do
things
get
things
done,
so
they
have
more
project,
specific
details
and
all
of
the
general
stuff.
That's
widely
applicable
across
all
of
the
openstack
projects
is
in
the
contributor
guide.
D
Once
you
get
a
little
bit
deeper
into
things
and
are
interested
in
like
messing
around
with,
like
maybe
changes
that
you've
made
or
testing
things,
the
dev
stack
documentation
might
be
a
place.
You
want
to
go
and
dig
through
it's
its
own,
unwieldy
beast.
That
could
probably
be
a
whole
different
topic
for
cloud
tech,
thursday,
but
yeah
as
a
community.
We
chat
synchronously
on
irc.
I
know
slack
is
very
popular
in
a
lot
of
different
communities
and
discord
and
all
kinds
of
different
things,
but
we're
super
old
school
and
we
like
irc.
D
We
use
garrett
as
our
code
review
system.
So
we
don't
use
github
like
a
lot
of
communities.
So
review.opendev.org
is
where
we
go
to
do
code
reviews.
We
also
have
some
other
like
community
sort
tools,
so
etherpad
and
ethercalc
are
basically
open
source
equivalents
of
google
docs
and
google
sheets.
Meatpad
is
a
like
video
chatting
sort
of
service
that
we
host
as
a
community.
D
D
D
The
agendas
for
upcoming
meetings,
also
in
here
you
can
go
and
find
the
irc
channel
logs,
because
every
single
one
of
our
official
channels
are
logged.
So
if
you
don't
happen
to
have
an
irc
bouncer
set
up,
you
can
keep
up
to
date
on
what
people
have
been
talking
about.
You
can
go
back
and
read
those
logs,
they're,
really
handy
for
referencing
things
that
I
don't
remember
that
I
said
three
years
ago.
D
A
B
D
D
D
We
exist
to
try
to
help
catch
all
of
the
newcomer
questions.
We
try
to
pay
really
close
attention
to
the
like
openstack
mailing
list
and
make
sure
that
people
that
introduce
themselves
and
they're
like
hi,
I'm
new.
Where
do
I
start?
We
respond
to
them.
We
also
try
to
monitor
various
question
sites
so
like
we
had
ask.openstack.org,
which
is
now
all
read-only.
D
But
previously
we
had
been
monitoring
that
for
newcomer
questions,
new
contributor
questions
and
I
will
also
start
monitoring
like
stack
overflow
for
new
contributor
questions
related
to
openstack
and
that
group
of
people
we
all
hang
out
in
openstack
dash
upstream
dash
institute.
That
channel
is
on
freenode
at
irc
and
the
other
thing
that
we
as
the
first
contact
sig
do
is
manage
a
list
of
project
liaisons.
D
So
a
lot
of
us
are
involved
in
different
openstack
services,
but
if
one
of
us
isn't
directly
involved
and
can't
really
give
a
lot
of
advice
to
somebody
on
say
qa
like
I,
I
don't
really
know
a
whole
lot
about
the
keyway
project.
I
know
somebody
that
does
work
on
the
qa
project
and
I
will
introduce
you
to
them.
C
So
one
thing
I've,
you
know.
One
thing
I
found
in
some
other
projects
is
that
asking
younger
developers
to
get
on
irc
is
kind
of
a
major
hurdle
has
openstack
done?
Is
it
looking
at
doing
things
like
using
repeaters
to
bring
irc
together
with
some
newer,
more
popular
chat
mechanism,
like
slack
right
now,
is
kind
of
an
obstacle
but
telegram
or
discord
or
something
else.
D
I
people
have
definitely
looked
into
that.
I
personally
haven't
done
a
whole
lot.
I
like
I
started
at
ibm
and
they
were
like
okay,
I
set
up
irc
and
I
was
like
okay
and
then
and
then
I
did
and
now
I'm
like,
I
love
irc,
it's
great
so
like
I
know
there
are
a
couple
people
like
on
my
team,
specifically
that
don't
use
slack
and
get
things
piped
from
slack
into
irc,
but
I
haven't
heard
a
whole
lot
about
going
the
other
way,
but.
B
D
C
D
Okay,
yeah,
I
mean
it's
definitely
a
popular
topic
using
irc
that
comes
up
with
somewhat
comical
regularity,
but
we
like
as
a
as
a
community.
We
don't
have
any
like
official
process
for
being
like
well,
you
don't
want
to
be
on
irc,
but
you
need
to
be
able
to
talk
on
irc.
So
this
is
what
you
should
do.
D
We
do
kind
of
promote
the
use
of
like
web
clients
for
when
people
don't
want
to
fuss
with
like
installing
a
desktop
client
and
that,
and
sometimes
the
web
clients
like
irc
cloud,
for
example,
are
a
little
bit
more
user-friendly
and
like
have
a
prettier,
ui
and
stuff.
So
we
usually
promote
those
as
options
and
alternatives.
D
C
A
B
B
So
the
diversity
and
working
group
reports
directly
to
the
board
of
directors.
So
we
are
an
open,
infra
channel
those
things
that
are
specifically
openstack
on
openstack,
anything
that
is
like
kata
or
airship
or
starlingx,
though
not
all
of
those
are
on
irc.
They
would
have
their
own
channel
naming.
D
We
have
like
a
lot
of
different
mechanisms.
Obviously,
so
we
have
like
a
bunch
of
documentation
written
down
things,
if
that's
your
style
of
getting
involved,
we
have
like
people
you
can
reach
out
to
if
that's
your
style
of
getting
involved,
but
sometimes
that
might
be
intimidating
and
you'd
rather
like
go
to
an
event
or
or
something
so
we
have
a
variety
of
ways
of
getting
in
through
events
and
programs
into
the
community
upstream
institute
is
the
one
that
I
have
spent
the
most
time
working
on.
D
So
if
those
are
happening
in
your
area
and
you're
interested
in
like
attending
a
contributor
onboarding
session,
if
you
can
talk
to
the
organizers,
they
will
contact
me
and
or
my
partner
in
crime,
ilda
kovacha,
and
she
and
I
are
the
ones
that
normally
travel
to
those
and
host.
It,
though
obviously
travel
disclaimer,
travel,
disclaimer,
rona
right
now,
but
I
I
hope,
someday
to
get
traveling
around
again
and
doing
those.
And
we
have
that
split
into
two
parts.
D
We
would
draw
in
different
sorts
of
audiences
and
make
it
easier
for
people
to
commit
to,
because
the
other
part
that
we
noticed
was
that
as
a
like
two
day,
long
training
or
a
day
and
a
half
long
training.
That
is
a
long
time
to
try
to
hold
people's
attention.
So
we're
like
okay.
Well,
let's
make
this
easier
more
palatable,
and
so
we
have
made
those
changes.
The
next
thing
is
like,
after
you've
gone
through
the
contributor
guide,
and
you
kind
of
know
have
your
stuff
set
up.
D
I
don't
know
how
to
implement
this
focused
event
for
our
technical
teams,
so
that
covers
like
basically
the
openstack
services,
but
we
also
have
like
sigs
and
the
openstack
technical
committee
meeting
there
as
well,
and
it's
basically
a
place
for
those
teams
to
meet
and
have
like.
Well,
it
used
to
be
face-to-face
discussions.
It
is
kind
of
via
video
now
and
if
they
need
to
like
work
with
another
team
to
like
get
something
done,
they'll
hop
over
into
that
video
call
or
that
room
and
go
have
those
discussions.
B
B
D
C
D
So
I
went
there
though,
if
you
don't
know
what
do
you
want
to
work
on?
You
just
want
to
get
involved.
We
have
other
resources
for
that
which
I
will
get
to
on
the
next
slide
through
the
help
wanted
list
and
like
in
upstream
investment
opportunities.
So
there
are
like
two
kind
of
paths
that
you
might
be
coming
from,
like
you
know
what
you
want
to
work
on
and
you're
like.
D
Yes,
I'm
gonna
go
to
the
ptg
and
I'm
gonna
join
nova
and
I'm
gonna
get
to
know
this
person
and
this
person-
and
I
have
this
thing
that
I
want
implemented
or
you're
like
openstack-
seems
super
cool
and
I
want
to
get
involved
and
I
don't
know
what
to
go
work
on,
and
so
you
would,
you
know,
message
the
first
contact
sig
or
send
it
an
email
to
the
mailing
list
and
be
like
hey.
I
want
to
get
involved.
B
B
Okay,
yeah,
so
then
that's
how
you
get
involved
in
a
project
like
I've
got
patches
in
probably
five
or
six
projects,
because
a
lot
of
times
I
go
through
the
documentation
and
I
notice
something's
wrong
with
the
install
guide
for
them.
So
then
I
go
and
fix
a
client
or
I
do
something
else
within
that
particular
service,
and
you
know
so
that's
how
you
get
involved
in
a
lot
of
different
projects.
Even
though
that's
not
your
main
project,
it's
still
a
project
you've
contributed
to.
D
Yeah
yeah
there's
a
no
rules
that
say
you
can
only
participate
in
one
project
at
a
time.
I
have
my
fingers
and
many
pies
many
many
pies
at
any
given
time
so
yeah.
We
we
definitely
encourage
like
if
you
find
something
and
you
know
how
to
fix
it,
go
ahead
and
do
it
and
we
will
help
you
through
that
process.
D
So
upstream
institute
and
the
project
onboarding
at
the
ptg's
are
the
two
more
like
industry
sort
paths
in
where,
like
you,
are
employed
or
are
doing
it
as
a
hobby
and
then
the
the
last
three
are
more
for
students
at
university
still
so
art
richie
is
a
program
that
we
participate
in
that's
hosted
by
the
software
freedom,
conservancy
and
we've
been
involved.
For
I
don't
know
many
years
now.
D
The
northern
hemisphere-
I
was
like
this
one
nope
this
one
so
for
northern
hemisphere,
summer
and
winter
they
run.
I
think
it's
like
four-ish
month,
long
internships
and
they're
actually
paid
internships,
and
basically
the
whole
point
of
the
program
is
to
increase
diversity
in
open
source
projects
and
also
to
just
like
get
more
students
involved
in
open
source,
in
addition
to
increasing
diversity.
So
I
have
had
a
number
of
interns
that
have
been
super
awesome
and
I
am
still
friends
with
and
like
mentor,
even
though
they're
like
graduated
from
university
now.
D
So
it's
a
really
excellent
program,
similar
to
the
google
summer,
google
summer
of
code,
another
north
american
summer
thing.
We
have
participated
in
this
program
once
or
twice,
and
it's
kind
of
hard
to
get
selected,
because
so
many
people
want
to
participate.
So
we
usually
focus
more
of
our
effort
on
outreachy,
but
it's
it's
another
excellent
program
for
university
students
to
get
involved
in,
and
we
have
partnerships
with
a
couple.
D
Different
universities,
if
you
happen
to
go
to
one
of
these
like
boston
university,
has
put
out
calls
to
the
openstack
community
for
work
for
various
classes,
where
they
want
people
to
get
involved
in
open
source
projects
and
various
like
senior
design
courses
as
well.
I
have
a
group
of
three
seniors
at
boston
university
right
now
that
are
working
on
the
openstack
sdk
and
then
I
have
a
group
of
like
junior
and
seniors
at
north
dakota
state
university,
who
have
similar
to
like
a
senior
design
project.
D
D
So
one
of
our
focuses
over
the
last
release
or
two
has
been
around
policy
and
policy
defaults,
and
so
like
that
was
one
thing
that
we
put
on
this
list.
We
really
could
use
more
qa
quality
assurance
developers,
as
could
everybody
I
imagine
but
yeah.
So
we
we
keep
this
list
up
to
date.
We
go
through
it
every
year
and
we
try
to
be
like.
D
D
Yeah
these
investment
opportunities
are
more
long-term
focused,
as
opposed
to
like
a
small
little
thing,
which
I
will
get
to
it's
further
down
the
list
on
my
slide,
but
yeah
they're
they're
more,
like
I
have
50
of
my
time
to
work
upstream
on
a
project
and
basically
have
free
range
to
do
whatever
I
want.
This
is
a
list
that
would
be
good
for
you,
so
yeah
and
community
goals
were
listed
on
there.
D
The
openstack
community,
with
the
direction
of
the
the
technical
committee,
sets
community
goals
every
release,
cycle
and
where's
the
list
here
down
here.
Basically,
we
have
like
priority
things
that
we
want
to
get
done
and
we
want
to
get
them
done
by
the
end
of
the
release,
so
for
our
current
one
that
we're
working
on
wallaby,
which
ends
in
like
a
month
already
jeez.
D
The
two
focuses
have
been
more
of
that
policy
stuff
that
I
mentioned
earlier
and
also
moving
oslo
root
rap
to
oslo,
privsep,
thrilling
thrilling
stuff,
but
that
basically
there
the
things
that
aren't
as
like
shiny
as
a
new
feature,
but
things
that
we
really
need
to
get
done
as
a
community
across
all
of
the
openstack
services.
So
we
try
to
draw
attention
to
those.
D
So
if
you
have
maybe
a
few
extra
cycles
to
spare
and
want
to
help
with
one
of
those
community
initiatives,
but
don't
want
to
do
something
from
the
community
investment
opportunities,
then
maybe
that's
the
path
for
you.
This
last
bullet
point.
I
have
about
the
low
hanging
fruit
tag,
so
that
is
the
very
small,
easy
places
to
get
started.
D
You
can
search
for
that
tag
and
it
will
bring
up
a
lengthy
list
of
easy
to
get
started
on
bugs
or
tasks.
Usually,
this
test
is
weird
or
this
documentation
is
wrong.
There's
a
typo
here
that
sort
of
thing,
so
it
kind
of
helps.
You
get
your
feet
wet
in
and
maybe
make
a
connection
with
somebody
that
can
give
you
some
bigger
piece
of
work
or
maybe
after
you
get
a
few
of
those
things
done.
B
Maybe
you
see
a
bug
that
you
know
you
were
kind
of
interested
in
previously,
but
you
didn't
have
the
confidence
to
do
so
now,
you're
going
to
go
ahead
and
take
that
bug,
yeah
and
you
know
another
good
place
to
start
is
documentation.
If
you
see
something
wrong
in
the
documentation,
yeah
catch
up,
they're
always
welcome.
C
C
One
of
our
biggest
problems
has
been
maintaining
the
you
know,
sort
of
currency
of
good
first
issue,
as
in
the
problem
with
good.
First
issues
are
generally
easy
fixes,
which
means
they
tend
to
actually
get
fixed
relatively
rapidly,
and
so
keeping
items
on
that
list
has
been
sort
of
an
ongoing
challenge.
D
I
do
think
it's
kind
of
like
an
ebb
and
flow
sort
of
situation.
Some
project
teams
are
focused
on,
like
I'm,
just
gonna
like
file
a
bug
for
that
and
whatever
like
I'll
fix
it
later
and
then
other
ones
are
like
I'm
not
even
gonna
file
a
bug
for
that.
I'm
gonna
fix
it
right
now
and,
like
it
kind
of
just
depends
on
the
the
like
culture
of
the
project
that
I
mentioned
before
it.
D
It
varies
a
lot.
I
think
some
of
the
sources
that
we
we
find
those
is
like
an
operator
will
mention
something
like
amy
was
talking
about
with
like
an
issue
and
an
install
guide
and
they'll
be
like.
I
don't
know
how
to
file
the
bug
or
I
don't
know
how
to
fix
the
thing.
So
I'm
just
going
to
file
a
bug
for
it,
and
then
one
of
the
upstream
developers
on
that
project
will
be
like.
D
C
Yeah,
I
I
mean
it,
you
know
it
answered
my
question
that
you
haven't
found
a
lower
effort
shortcut
for
for
maintaining
this
list,
because
the
struggle
we
always
have
right
is
that
I
go
to
a
kubernetes
sig
lead
and
I'm
like
hey.
We've
noticed
that
there's
no
good
first
issues
marked
with
your
sig,
you
know,
and
those
are
a
good
way
to
get
new
contributors
involved.
I
said
well,
the
problem
is
it
takes
me
more
effort
to
maintain
the
good
first
issues
list
than
it
would
take
me
to
fix
the
issues
in
the
first
place.
D
E
D
B
Mean
I
was
definitely
guilty
of
that
this
week
because
I
noticed
a
problem
with
install
guide,
so
I
patched
it
yeah,
but
to
make
sure
we
don't
have
that
same
issue
with
the
install
guide.
Maybe
what
I'll
do
is
open
a
bug
and
tag
it
for
the
wallaby
release,
and
hopefully
someone
will
pick
it
up.
But
if
it's
not
done
within
a
certain
amount
of
time,
I'll
probably
go
ahead
and
pick
up
that
bug.
D
B
Well,
it's
was
the
fact
that
we
didn't
have
victoria
even
listed
in
the
install
guy,
so
it
can't
it
can't
stay
that
way
for
long.
But
yet
again
it
was
a
very
easy
bug
that
someone
else
could
have
picked
up,
but
the
fact
that
we
hadn't
updated
that
documentation
was
just.
I
got
to
get
this
done
versus
trying
to
find
someone
so
I'll.
Take
it
on
myself
to
go
ahead
and
open
up
a
proactive
bug,
and
if
we
don't
have
it
done
within
a
week
of
the
release,
I'll
go
ahead
and
do
the
bug.
C
D
There
are
meetings
happening
all
the
time
and
if
there's
a
a
topic
that
interests
you
say,
you're
really
interested
in
acceleration
or
something
you
go
and
join.
The
like
cyborg
team,
or
maybe
authentication,
is
really
your
jam
and
you
can
go
and
join
the
keystone
team
and
go
and
see
what
they're
talking
about
in
their
meetings,
look
at
their
agenda
and
just
introduce
yourself
and
be
like
hey,
I'm
interested
in
getting
involved.
D
B
D
What
have
you
is
a
pretty
big
code
base,
and
so
you
want
to
like
take
it
down
to
a
smaller
scale
than
that
and
code
reviews
are
a
good
place
to
kind
of
like
okay,
I'm
going
to
get
familiar
with
like
this
section
of
code,
then
this
section
in
this
section
and
then
you
kind
of
learn
how
to
connect
them
together
and
before
long
you're.
Like
oh
okay,
I
understand
how
cinder
works.
C
Yeah
I'll
also
say
honestly
in
general.
Just
doing
that,
like
you
know,
adding
the
patch
and
trying
out
the
feature
is
specked
is
useful
and
it's
really
helpful
for
the
more
senior
contributors
to
have
somebody
say
you
know
hey.
I
actually
tried
this
patch
and
it
works
as
specified,
because
that
means
the
senior
reviewer
can
focus
only
on
code,
quality
and
side
effects
and
other
issues,
and
they,
you
know,
can
kind
of
skip
over
the
part
where
they
say
hey.
Does
this
actually
meet
what
the
spec
is.
D
Yeah
and
like
new
perspective
is
so
helpful
a
lot
of
times
because,
like
somebody,
that's
really
familiar
with
the
code
is
going
to
go
and
make
a
change
and
then
like
not
comment
it
because
they
know
how
it
works
and
it
makes
sense
to
them
and
they
kind
of
described
it
in
the
commit
message.
But,
like
you
know,
a
new
contributor
can
come
in
and
be
like.
Why
did
you
do
it
this
way?
B
And
one
thing
I
had
never
even
thought
of,
but
it
was
during
one
of
the
mentoring
panels
we
did
at
summit,
was
that
code
reviews
and
how
you
react
to
other
people's
feedback
can
be
important
in
a
job
interview
like
they
were
looking
at
people's
patches
and
the
reviews
on
them
to
see
how
people
you
know
took
the
feedback
and
how
they
applied
it.
So
it
wasn't
just
their
code
that
was
being
looked
at,
but
the
interactions
with
others
yeah.
That
was
a
really
interesting
aspect
that
I
had
never
even
thought
of
before.
D
D
D
C
So
I
have
some
discussion
topics
here.
The
one
thing
I
was
going
to
ask
you
is
you're,
pretty
aware
of
also
what
we're
doing
within
kubernetes
in
terms
of
mentoring
and
onboarding
and
that
sort
of
thing
yeah
and
aside
from
the
beyond
behind
schedule,
state
of
things
I
what
things
have
you
found
that's
essential
in
getting
started
and
onboarding
and
stuff
that
that
you've
learned
through
openstack
is
essential
that
we're
not
doing
in
kubernetes,
and
we
don't
have
an
initiative
to
do.
B
B
You
know
the
in
the
within
community
mentoring
programs,
so
we
had
actually
switched
from
our
one
to
one
to
more
of
a
cohort
which
is
more
what
kubernetes
was
doing,
hoping
that
that
would
relieve
some
of
the
pressure
on
the
mentors.
But
again
we
just
really
didn't
seem
to
get
picked
up
with
that.
So.
E
B
Mentoring
for
all
the
communities
is
still
something
that
we
all
need
to
work
on.
You
know
it's
great
outreachy,
google,
summer
of
code,
google
summer
of
docs
those
things
are
paid,
so
I
think
they
get
a
little
more
attention
yeah
and
a
little
more
interactivity,
because
you
know
the
interns
know
they're
getting
paid
for
this.
They
need
to
participate
than
just
being
available
to
mentor
people,
which
is
something
I
think
the
communities
are
really
good
about.
But
no
one
takes
advantage
of.
D
D
What
do
you
need
from
me
exactly
because
I
can
commit
to
a
like
set
amount
of
time,
but
outside
of
that,
I'm
gonna
need
to
get
like
extra
manager,
approval
and
all
this
other
stuff.
So
I
think
that
things
that
are
really
clearly
defined,
like
those
programs,
are
why
we
see
more
success
there
than
like
the
ethereal
wishy-washy
like.
Oh,
like.
E
D
C
The
major
obstacle
we've
had
with
outreachy
and
summer
of
code
and
lfx
and
the
other
programs
is
that,
of
course,
they
have
their
own
timelines.
That
don't
happen
to
sync
up
with
our
release
timeline,
which
makes
it
hard
for
and
of
course
you
want
to
assign
one
of
those
interns
a
major
project
right,
because
they've
got
like
a
10-week
block
to
work
full-time
on
something.
C
B
C
C
Yeah,
but
you
don't
you,
don't
always
get
that
right.
Sometimes
what
the
intern
basically
learns
is
they
want
to
work
on
a
different
project
plus
if
they
are
still
in
school
and
they're
going
back
for
another
term.
You
know
no
matter
what
the
level
of
interest
is
in
your
project.
That
doesn't
mean
they
necessarily
have
availability,
yeah.
D
I
think
one
of
the
ways
that,
like
we
try
to
combat
that
is
like
yeah.
We
have
this
big
thing
that
we
want.
We
want
all
of
placement
implemented
in
the
openstack
sdk,
but
do
that
one
resource
at
a
time,
and
so
we
try
to
like
break
things
down
into
really
really
small
mergeable
pieces
of
code
so
that
if
they
do
leave
in
the
middle,
we
can
be
like
okay.
Well,
let's
assign
somebody
else
to
like
finish
the
rest
of
this
up.
That's
fine
and
also
the
other
thing.
D
D
Yeah
exactly
and
that's
more
culture,
sort
of
thing
that
we
have
where
we're
like
you
know
here
you
go
hot
potato,
your
turn.
You
go
ahead
and
fix
this,
or
maybe
I'm
on
vacation
and
someone
else
is
gonna
fix
the
thing
that
I
was
working
on
while
I'm
on
vacation
and
I'm
not
gonna,
get
upset
about
that
because
we're
all
one
big
happy
community.
D
C
C
And
two
weeks
from
now
our
next
show
we
will
be
introducing
a
new
brand
new
cloud
native
project
called
scribe,
which
is
automated
by
automated
replication
based
reliability
for
your
kubernetes
cluster.
So
come
and
learn
all
about
that
project.
Two
weeks
from
today
and
we
will
see
you
then
amy
last
thoughts.