►
From YouTube: 2018-01-11 Apache Mesos Doc-a-thon
Description
2nd Quarterly Mesos Doc-a-thon.
Agenda and Notes:
https://docs.google.com/a/mesosphere.io/document/d/1-biNAKITW5mFpYlAE0gH-ycReTHVOv7pak_NTNL17x4/edit?usp=drive_web
A
A
In
case
you
watched
the
recording
later
and
you
want
to
pick
up
one
of
these.
Please
feel
free
we're
always
looking
for
contributions
not
just
now,
and
then
we
will
form
teams
and
get
started,
make
sure
everybody's
name
and
project
that
they
want
to
work
on
is
on
the
agenda.
Doc
people
have
on
things
for
a
while
at
6
p.m.
A
C
A
So
I
put
a
we're
chatting
in
the
mesas
documentation
chat,
a
slack
Channel
and
I
put
the
agenda
in
there.
So
I
think
what's
gonna
happen
is
Gregg's
gonna
present
the
easy,
easy
fixes
and
then
we're
all
gonna
just
go
around,
introduce
ourselves
and
say
what
project
we're
hoping
to
work
on
today,
and
so
we
will
make
sure
to
call
on
you
guys
first
and
please
put
your
name
down
in
the
dock,
with
the
project
proposal
that
you
have
sound
good.
D
E
I
am
Greg
Mann
for
those
of
you
who
don't
know
me:
username
Greg,
oh
man
on
mrs.
slack
you're
a
review
board,
and
we
have
a
few
little
dock
project
proposals
that
we
put
in
the
shared
document.
So
this
is
in
a
calendar
event
on
the
mesos
community
calendar.
That's
one
way
to
find
it.
If
you
can't
find
it,
you
could
also
find
us
on
slack
or
over
email,
we'll
get
it
to
you.
E
So
one
of
the
items
is
to
link
to
new
binaries
and
getting
started,
and
the
downloads
page
so
I
don't
think
the
getting
started
page
has
a
link
to
any
binaries.
So
we
could
just
have
a
link
to
the
latest
binary
packages
in
those
pages
would
be
nice
small
little
thing
to
add.
We
also.
This
is
a
little
bigger
task.
We
want
to
move
our
project
roadmap
from
wiki
to
the
documentation.
So
right
now
we
have
this
completely
neglected,
wiki
page
that
we
have
a
roadmap
on.
E
We
would
like
to
bring
it
into
the
just
the
rest
of
the
docs,
so
that'll
get
a
little
more
love,
it'll,
be
in
one
place
where
it's
apps
to
get
more
frequent
attention
and
it'll
be
easier
for
us
to
update
it.
So
that
would
be
a
really
cool
thing
to
add.
Also
general
spell
checking
and
copy
editing.
We
definitely
make
mistakes,
so
anything
you
care
to
copy
edit
anywhere
would
be
wonderful.
E
Be
one
operator
API
Docs,
so
one
thing
that
I
personally
think
would
be
kind
of
nice
is
to
change
some
of
our
existing
examples
into
just
curl
snippets
that
you
can
just
copy
and
paste
into
the
terminal
to
make
some
of
these
API
calls
I
find
myself
when
I
have
to
make
API
calls
just
translating
constantly
the
examples
into
curl
commands.
So
it
would
definitely
make
my
life
easier
if
not
anyone
else's,
but
I
suspect
it
might
make
some
other
people's
lives
easier
too.
So
that's
an.
F
E
Cool,
so
we
need
to
change
some
of
our
quota
Docs,
and
you
could
help
me
out
with
that,
if
you
so
desire.
So
those
are
some
of
the
easy
tweaks
we
had
down
there.
Also
just
some
other
things.
We
added
a
fundamentalist
section,
I
think
so.
I
didn't
add
that,
but
I
have
some
ideas
in
my
own
head
of
what
a
fundamentals
section
might
involve
and
what
might
be
good
I
think
we
could
use
some
more
like
fundamental
overview
of
maysa.
E
E
E
And
for
the
v1
scheduler
API,
but
we
don't
really
have
a
high-level
story
about
hey.
This
is
how
the
life
of
a
scheduler
works.
This
is
the
scheduler
lifecycle.
What
the
offer
cycle
is
like
how
you
respond
to
it
so
I
think
a
doc
like
that
would
be
good
and
getting
new
framework
developers
up
to
speed
and
also
yeah
a
fundamental
section,
I'm,
not
sure
what
other
folks
had
in
mind
in
regards
to
that.
But
I
think
some
operator
fundamentals
would
be
good
too,
and
I
also
added
another
item.
Some
resource,
like
fundamental
resource
documentation.
E
We
have
in
the
agent
configuration
realm.
We
have
a
doc
that
tells
you
how
to
configure
an
agent
with
resources
and
attributes
and
that
kind
of
gives
an
overview
of
resources
and
maysa
a
little
bit.
And
then
we
also
have
a
couple
of
other
places
where
we
review
the
types
of
resources
that
are
available
like
in
the
multiple
disk
support
section.
We
go
into
a
whole
bunch
of
detail
about
the
different
disk
types
that
are
available
and
I
think
it
would
be
cool
to
have
a
single
document
on
resources
in
May.
E
So
these
are
all
the
options
everything
you
might
see
and
then
the
different
feature
specific
Doc's
could
link
into
that
when
people
want
to
get
more
info
on,
like
the
nitty
gritty
resource,
details
and
I,
think
that's
all
we
have
up
there.
So
certainly
other
ideas
are
welcome.
You
can
work
on
any
documentation.
You,
like
yeah
I,
feel
free
to
find
us
on
slack
or
via
email
or
on
Zoom.
Here
is
there
anything
else
you
wanted
to
say
Judith
or
should
we
just
get
started.
E
E
F
E
B
C
Contributions
from
me,
but
I
tuned
in
because
I
I
was
responsible
for
the
Apaches
link,
mezzos
integration
and
wrote
the
scheduler
code
for
flink
and
took
advantage
of
Netflix
penso
in
doing
that.
I
also
use
DC
u.s.
commons,
and
so
I've
encountered
of
various
things
in
the
course
of
working
with
schedulers
and
I
have
a
little
laundry
list
of
things
mostly
to
do
with
the
offer
lifecycle
that
I
think
would
have
been
handy
to
see
in
the
documentation.
C
E
That
sounds
really
good.
I
think
improvements
to
documentation
that
come
out
of
practical
experience
like
that
are
some
of
the
best.
So
we
would
definitely
love
to
see
those
changes
brought
in.
So
we
can
find
you
I'm
also
on
DCOs
slack.
We
can
find
you
there
or,
if
you
make
your
way
to
Mesa
slack,
either
spot.
Let's
sync
up
on
the
changes
you
have
in
mind,
that
sounds
great
yeah
I'll.
E
H
G
A
A
Yeah,
just
don't
join
the
audio,
just
that's
really
smart.
Actually,
because
what
we're
gonna
have
you
do
is
you're
gonna
present
the
project
that
you
did
and
just
walk
us
through
your
changes
and
then,
at
the
end,
once
everybody's
presented
we're
all
going
to
vote
with
your
post-its
and
if
your
remote
and
you're
not
shy
about
which
one
you're
voting
for
just
slack
me
or
if
you
are
shy,
I,
don't
know
what
to
do.
A
A
E
E
E
E
B
E
Actively
contributing
as
you
see
so
that
we
could
just
collaborate
on
here
and
I
think
this
is
actually
gonna.
Take
us
some
more
time,
so
we
just
really
have
we're
just
getting
started
here,
but
we
wanted
to
provide
a
high-level
overview
of
how
one
gets
started
with
writing
a
masive
scheduler,
the
existing
maysa
scheduler
development
guide.
Pretty
much
just
follows
the
old
scheduler
driver
API,
so
it's
pretty
out
of
date
and
it
doesn't
provide
an
overview
of
some
high-level
concepts
like
what
does
the
lifecycle
of
a
framework?
Look
like
you
know.
E
What
is
the
offer
stream?
How
do
I
respond
to
it?
Just
some
basic
stuff?
They
kind
of
eases
people
into
it
before
we
actually
expect
them
to
start
looking
at
protobuf
definitions
and
stuff.
So
yeah
we
have
a
section
on
framework
lifecycle
handling
offers
how
to
understand
resources
and
tasks
working
on
evaluating
the
fitness
of
offers,
how
to
launch
tasks
what's
involved
in
launching
tasks,
sorts
groups
and
then
managing
tests,
so
we'll
have
a
section
on
status
updates
reconciliation
that
kind
of
so
this
is
all
stuff.
E
That's
covered
in
more
detail
and
some
of
our
other
Docs.
But
this
provides
like
a
gentle
introduction
and
then
links
out
to
all
of
that
other
documentation,
so
people
can
dig
in
further.
So
that's
what
Aaron
and
myself
we're
working
on
and
next
I'll
pass
it
over
to
senthil,
who
is
sitting
right
next
to
me.
G
B
B
G
Link
to
the
Bing
tray,
rpm
pay,
rpm,
URL
and
I'll
give
instructions
on
how
to
download
the
latest
rpm
and
install
it,
which
will
install
the
dependencies
and
then
I
also
gave
a
simple
instruction
to
how
to
get
start
them.
Asos
master
with
the
world
there,
which
is
already
created
by
the
RPM
and
the
missus
agent,
pointing
to
the
master
and
the
worker
and.
G
I
I
So
nothing
ultra
exciting,
but
just
some
nice
copy
paste
ball,
curl
examples
here:
some
of
them
get
a
little
nicer
as
the
juice
and
that
you
have
to
post
gets
more
complex.
So
you
still
copy
and
paste
about
him
to
worry
about
trying
to
format
one
line
of
JSON-
it's
about
it
here,
just
going
through
and
splitting
up
all
of
them.
B
K
So
I
just
add:
well
because
I
come
in
late,
so
I
just
do
a
small
thing.
Just
add
some
recommendation
for
the
job.
The
job
is
supporting
the
process
and
next
I
just
spend
all
my
time.
Drawing
this
fancy
super
fancy
diagram,
a
nickname
like
in
brief
how
the
GRP
see
asynchrony,
specific
or
wor
word
in
the
process
and
then
provide
very
like
like
Singapore
example
about
how
to
use
that.
That's
all,
and
also
have
a
note
about
like
performance
planet
like
Tori
that
was,
you
should
know
about
the
promising
pact.
A
Let's
see
if
I
can
get
my
screen
share
here:
okay,
so
I
updated
the
presentation,
page
I
added
all
the
recent
bases,
cons,
I
added
some
carriage
returns
or
new
lines,
so
that
the
two
sets
of
links
didn't
run
together
into
one
big
word
and
I
changed
all
the
YouTube
links.
So
they
don't
autoplay
because
autoplay
is
my
nemesis
and
that's
my
project.
So.
A
Did
we
get
everybody
yeah
cuz
erin
was
on
your
team,
great
okay.
So
just
to
remind
you
guys,
I'm
gonna
read
through
these
one
more
time
we've
got
the
developer
guide.
We've
got
standalone
containers,
documentation,
we've
got
a
beginner's
guide
to
developing
maysa
frameworks.
We've
got
maces
rpm
binaries,
we've
got
new
curl
examples.