►
From YouTube: 2017 10 12 Apache Mesos Docathon
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
A
It
sound
okay,
so
yeah
again,
there's
no
rules,
you
know
I
suppose,
even
for
this
I
guess
I'll
vote
for
its
whoever
works
in
the
under
project.
You're
not
gonna,
get
any
watches.
Sorry
yeah,
that's
not
true!
Maybe
I'll
still
give
you
watching
out
so
I'm
gonna
work
on
the
process
by
example.
So,
basically,
working
out
the
what's
currently
in
readme
MD
of
the
process
and
just
create
a
ton
of
examples.
That's
showing
how
all
the
things
inside
the
processor
being
are
gonna
be
used,
and
my
name's
Ben.
B
So
so,
basically,
Jason
and
I
kinda
work
on
the
the
first
thing
is
the
Bravo,
the
secret
bro,
I,
hope,
documentation
and
I
also
commit
the
patch
for
the
for
the
Linux
namespace
semantics
right
now
we
don't
have
any
too
many
linux
namespace
documentation
in
our
talk,
so
especially
for
the
indian
space
share
about
those
latest
somatic
changes.
We
don't
we
did
not
document
it
yet,
so
we
will
focus
on
the
namespace
and
secret
things,
and
if
we
come
up
with
more
idea
of
you
up
day
on
the
dock,.
C
D
I'm
joseph
or
mister
I
plan
to
be
working
on
a
refresh
to
the
modules
documentation
which
hasn't
really
changed
in
seemingly
years,
but
we've
definitely
been
fleshing
this
modules
out
or
all
of
our
modules
out,
and
it's
actually
in
a
lot
of
use
at
the
moment.
But
we
don't
have
any
doctor
if,
like
that,
I.
E
So
my
name
is
andy
I'm,
going
to
rewrite
the
getting
started
stuff,
not
the
getting
started
guide
that
Greg's
done
a
great
job
on,
but
right
now,
kyouda
getting
started
its
build.
Doc's
getting
started
is
not
how
to
build
it
on
four
different
platforms:
getting
started
to
be
a
table
more
like
the
community
page,
which
is
just
like
hey
you're
new,
to
make
those
here's
how
you
get
started,
doing
different
things.
So
that's
good
what
I'm
gonna
be
driving.
If
you
want
to
join
me,
I
could
probably
use
some
help.
F
H
Let's
see
so
one
thing
we
just
talked
about
was
trying
to
find
out
examples
that
we
could
write
in
the
documentation
for
using
the
v1
api's,
like
the
actual
commands
that
someone
could
use
with
curl.
So
maybe
we
will
update
the
v1
API
documentation
with
curl
commands
that
someone
can
copy
and
paste
to
try
it
out.
I'm
also.
I
also
want
update
the
roadmap
doc,
something
that
few
people
have
asked
me
in
the
past
that
we
haven't
been
updating
in
a
while.
I
J
K
L
My
name
is
Nolan
I'm,
pretty
new
to
mesosphere
as
an
ecosystem,
so
I
was
kind
of
hoping
more
to
focus
on
the
getting
started.
Docs
so
I
think
I
will
join
that
group
over
there
and
just
kind
of
go
into
it
eyes
wide
open
from
somebody
who
has
no
experience
and
kind
of
try
to
find
things.
That
trip
me
up.
A
Or
if
the
Apple
guys
join,
they
can
say
what
they're
gonna
do
yeah
so
I.
Take
that
back
about
the
voting.
So
actually,
when
we
present
some
time
between
6
&
7,
we
will-
and
everyone
will
vote,
will,
will
tear
up
some
little
sticky
notes
or
something
and
give
each
person
a
little
piece,
and
you
can
stick
it
on.
Everyone
can
vote
and
then
and
then
it
will
do
price
after
that.
N
A
We're
we're
we're
digging
in
I,
think
most
people
have
kind
of
found
groups
and
teams
that
they're
working
on.
If
everyone
can
in
the
dock,
if
they
can
sort
of
put
their
names
next
to
the
thing
they're
working
on
then
James,
you
can
either
jump
in
and
work
with.
Somebody
on
some
more.
You
could
do
your
own
thing
and
the
plans,
basically
we're
just
going
to
do
this
for
a
couple
hours
and
we're
going
to
show
people
what
we
did
and
vote
on
stuff
and
then
have
some
beers
and
hang
out.
N
M
M
N
H
J
Can
they
watch
the
recording,
okay,
alright,
so
what
I
did
was
I
took
the
I,
basically
reorganized
the
table
of
contents
right
now,
there's
this
big
section
called
running
maysa
and
it's
got
a
lot
of
different
stuff
in
here.
It's
got
things
like
how
to
build
with
CMake.
It's
got
how
the
agent
does
like
agent
recovery.
It's
got
like
security.
M
J
M
J
Show
examples
it's
kind
of
obvious
and
then
it's
api's
running
frameworks,
which
I
guess
was
just
a
list
of
the
frameworks
that
are
there
and
then
for.
J
Developing
frameworks
yeah
that
was
all
right,
I,
guess
modules
and
contributing
is
kind
of
a
bunch
of
stuff
yeah,
so
I
reorganized
it
make
this
a
little
bigger.
So
I
kept
the
fundamentals,
section
I
pad
a
section
for
build
an
insulation
which
included
the
just
the
build
related
stuff
here.
I
put
windows
support
in
there
for
now,
but
we
might
want
to
I,
don't
know
if
it's
just
build
or
if
it's
got
more
stuff
related
to
windows
support.
J
Then
I
had
a
section
for
administration
which
has
configuration
how
to
set
up
a
high
availability
master
or
a
fault,
tolerant,
hn
and
some
other
stuff
that
you
can
do
as
an
admission,
I
cream
enough
rain
work,
maintenance,
upgrades
logging
monitoring,
operational
guide
since
kind
of
a
wild
card.
How
to
configure
the
fetcher
cache
resource
management.
That
was
a
separate
section,
I
called
out
how
to
use
attributes
and
configure
that
Eugene
resources.
How
to
use
resource
roles
which
includes
fair,
showing
by
the
way.
M
J
J
Talks
about
all
the
networking
related
Doc's,
we
have
storage,
just
talks
about
persistent
volumes
and
multiple
disks
for
now,
but
I
think
some
of
these
other
things
like
container
volumes,
might
be
storage
related.
So
we
should.
We
can
tweak
that
later.
Api
is
so
I
wanted
to
call
out,
like
the
references
here
as
b0
and
b1
all
the
stuff
about
writing
a
framework
I
tried
to
collect
under
a
bullet
here,
like
you
know
how
to
design
highly
available
ones,
reconciliation,
a
state
reasons
and
stuff.
Like
that,
what
else
we
got
I
put
the
modules.
M
J
Docs
or
working
groups
under
there
there's
a
contributing
section
which
is
all
about
you
know.
If
you
want
to
interact
with
JIRA
or
write
a
patch,
the
style
guides,
we
have
testing
patterns
some
committers
and
how
to
become
one
and
code
reviews
and
so
on
and
on
the
books.
This
isn't
rendering
right
but
and
this
the
books-
that's
I,
didn't
know
where
to
put
that
one.
So
I
left
it
at
the
bottom
yeah,
that's
it
it's
already
shipped.
Actually,
so
the
website
will
get
updated
within
a
few
hours.
I
guess.
A
A
E
Okay,
so
this
is
the
getting
started,
changes
I'm,
gonna
start
by
just
showing
you
what
the
getting
started
Docs
currently
are:
they're
not
getting
started,
they're
how
to
build
mazes
from
source,
including
system
requirements,
including
one
two:
okay,
two
different
distributions
of
Linux
Mac
up
nope,
their
distribution
of
Linux
or
its
distribution
of
Linux.
E
M
E
Do
you
need
to
know
yeah
well,
I,
try
to
I
try
to
tell
us
what
we
need
to
know.
This
is
a
new
getting
started.
One
I
modeled
it
off
of
the
community
page
which
I
really
like
this
I
think
is
well
designed.
It's
short,
it's
one
page
worth
ish
and
I
actually
copied
it
and
reused
the
format.
Most
of
this
was
wrestling
with
middleman
to
make
it
work
again,
but
yeah.
E
This
is
the
new
getting
started
page,
just
a
basic
like
call
out
to
a
hour
long
thing
that
been
made
on
YouTube
for
how
to
use
Neos,
as
well
as
the
white
paper
that
you
should
probably
read
and
look
there's
no
scrolling.
This
flow
there's
a
little
bit
of
scrolling
I,
there's
a
little
more
content.
I
think
I
want
to
add
to
this,
but
it
just
gets
you
going
quickly
like
oh
I
am
looking
to
develop
my
so
school.
Here's
the
it's
that
building
documentation
which
is
actually
how
to
build
my.
E
So
it's
not
how
to
get
started
on
my
sews
and
also
hey
community,
if
you're
looking
at
this
top
bar
like
what
is
that
a
form,
this
at
least
tells
you
go
over
here
for
mailing
lists
and
slack
and
whatnot
nolan.
Here's
writing
a
getting
familiar
tutorial
to
kind
of
go
over
the
high-level
components
of
meso,
so
we'll
have
that
here
as
well.
E
And
finally,
I
wanted
to
call
out
in
a
really
big
major
way
from
the
landing
page
somebody
else's
project
Greg,
Greg's
right
there,
the
beginning
contribution,
guide
and
advanced
con
and
guide
rewrite,
because
these
are
great
to
get
further
started
once
you've
gotten
started.
You
can
read
these
to
actually
like
get
patches
in,
so
this
I
think
is
the
new
getting
started
landing
page,
including
links
on
the
side.
E
But
now,
if
you
click
this
you're
not
overwhelmed
same
problem
that
we
have
with
documentation
you're
no
longer
overwhelmed
with
building
everything
you
just
want
to
get
started.
I
definitely
think
this
needs
a
little
more,
not
a
ton,
more
content.
I
don't
want
to
overload
it,
but
if
there's
anything
you
think
is
important
for
somebody
who's
getting
started
with
Miso's
to
know.
Let
me
know
Andy.
We
should
add
it
to
this
and
get
it
in,
because
I
think
this
is
so
much
easier
to
reap
so
yeah.
That's
it
and
it's
called
getting
started.
A
L
L
So,
as
any
said,
my
name
is
Nolan
I'm
working
kind
of
on
just
getting
familiar
on
like
kind
of
a
guide.
There's
a
lot
of
information
out
there
I
think
that
it
should
provide
a
pretty
high-level
overview
of
here's
the
kind
of
pieces-
and
you
know
this
is
what
this
part
does.
This
is
what
that
part
does.
Just
you
know
if
you're
familiar
with
it,
you
can
skip
ahead
or
skip
around,
but
I
had
kind
of
tried
to
focus
on
usability
through
the
lens
of
mezzo.
O
L
K
Yeah
yeah
I
think
why
did
is
adding
like
the
missing
documentation
for
mrs.
containerized,
they're,
Isolators
I.
Think
that's
part
of
the
work
I
did
during
hackathon
during
my
Cisco
this
year,
so
I
kind
of
refactor,
this
entire
dog
into
like
a
make
that
in
index
TOC
file
and
have
a
link
to
the
corresponding
documentation
for
each
Isolators
and
I.
Think
we
have
still
have
a
lot
of
missing
isolated
documentation.
So
this
part
of
this
target
line
just
adding
like
some
of
the
missing
sea
groups
and
file
system
isolator
documentation.
K
K
Is
see
group
devices
so
that
there's
no
one
that
we
we
did
the
work
but
didn't
finish
the
documentation.
So
so
this
one
in
specifically,
you
have
some
default
wireless
devices
which
is
not
call
out
the
documentation
it's
inside
the
code,
so
I
make
it
part
of
the
documentation
like.
If
you
turn
on
this
Isolators,
you
have
those
default
wireless
devices
that
you
can
use
in
your
container
and
also
there's
an
agent
flag
that
you
can
config
to
adding
onto
an
additional
devices.
You
want
to
enable
like
rewrite,
make
notes.
K
O
G
G
B
B
So
for
guys,
who
don't
know
me
yet
I'm
Gilbert,
so
so,
basically,
I
will
with
Jason
and
left
so
I
gonna
cover
his
part.
So
we
had
Jason
at
the
isolated
single
plot,
IO
subsystem,
so
basically
yeah.
We
have
we
added
this
for
missus
1.4,
but
we
did
not.
We
did
not
document
the
yet
in
this
documentation
we
acted.
B
B
The
other
part
is
the
controller
which
we
did
not
support
it
yet,
and
so
we
just
mentioned
it
here,
and
then
this
is
a
simple
well
I
owe
stat,
stat
user
might
be,
might
be
interesting
with
and
and
then
that's
it.
So
we
also
I
also
have
some
other
documentation
for
there
for
the
namespace.
So
we
don't
have
we
don't
have.
B
We
did
not
like
document
any
linux,
namespace
semantics
in
masers
before
so
I,
just
at
a
table
under
the
linux
launcher
to
introduce
the
the
seven
linux
namespaces
reoccur
in
masers
and
apart
from
the
user
name
space,
we
did
not
support
yet
and
all
the
others
already
supported
on
masers
and
we
have
different
semantics
for
top-level
continue
and
the
nested
continue.
So
this
is
just
a
table
on
like
what
namespace
be
defied.
It
as
a
shareable
and,
for
example,
like
man,
space
will
never
be
shared
and
we
also
have
some
future
plan.
B
For
example,
the
IPC
and
C
group
names
based.
We
can
change
the
behavior
in
the
future,
so
we
just
rip
it
as
a
to
be
determined
in
the
documentation.
So
so
this
is.
This
is
something
we
if
we
go
together,
if
GA
me
know
and
and
guest
on
earlier
in
the
meeting,
but
we
just
don't
have
any
documentation
about
that.
Yet
so
it's
good
to
capture,
and
so
this
is
another
thing.
Oh,
this
is
another
pin
in
space.
O
I
I
And
there
we
are
so
something
that
I
had
in
play
already
before
the
doctor
found
today
is
what
Andy
mentioned
earlier.
This
update
for
our
contributors
guide,
so
the
main
thing
we're
doing
here
is
splitting
our
contributor
guide
into
two
different
guides.
We
have
a
beginner,
first-time
guide
for
people
who
have
never
contributed
to
mazes.
Maybe
they
really.
I
To
reach
in
and
make
a
little
bug
fix
or
a
documentation,
change
and
move
on,
so
the
beginner
guide
is
all
about
making
PRS
on
github.
So
it
really
just
tells
you.
If
you
want
to
propose
a
change,
you
can
open
a
PR
against
our
public
github
mirror,
and
then
it
has
a
little
bit
of
information
about
like
links
to
getting
started,
links
to
the
committers
page.
If
you
want
to
get
in
touch
with
a
committer
how
to
find
me
so
slack.
I
I
New
contributors
and
then
so
I
spent
just
a
little
time.
Looking
at
this
with
the
node
today
and
one
of
the
things
that
he
recommended
and
also
Andy
when
I
was
looking
at
it
with
him,
I
think
it
totally
makes
sense.
Is
that
we'll
just
move
everything
below
this
first
Jurists
section
and
we'll
move
all
the
rest
of
this
and
just
merge
it
with
the
advanced
contributor
guide,
so
we're
gonna
end
up
with
a
really
concise
little
beginners
contributor
guide?
That's
just
like
one
page
long:
here's
how
to
open
a
PR.
I
Http
API,
so
I
took
a
look
at
so
I've,
been
working
with
some
folks
who
are
consuming
these
HDPE
api's
lately
and
so
I.
Look
at
the
docks
with
them
and
I
see
things
here
and
there
that
we
could
improve.
So
one
of
the
things
I
wanted
to
prove
improve
in
these
scheduler
HTTP
API
Docs
was
adding
some
information
about
offer
operations.
We
didn't
really
explain
previously
with
the
accept
call
info.
What
offer
operations
are
out
there?
I
What
they're
used
for
so
I
went
ahead
and
added
some
info
for
launch
for
launch,
grew
and
then
link
to
the
reservation,
documentation
and
persistent
volume
documentation.
Here
we
can
add
the
new
operations
when
those
get
fleshed
out
a
bit
and
then
I
went
through
this
file
and
also
just
updated.
Some
formatting
made
it
a
little
more
consistent
here
and
there
and
yeah
that's
it.
O
A
O
D
Like
currently
so
we
have
quite
a
few
things
on
this
page
that
are
in
various
states
of
disrepair.
We
have
a
disclaimer,
that's
saying,
like
you,
shouldn't
use
modules
at
all,
even
though
we've
got
like
tens
of
modules
now
in
use
and
eCos,
and
it
also
has
a
blurb
of
maysa
modules,
which
actually
isn't
so
accurate
anymore.
Like
it's
a
it's
easy
to
use.
M
D
Easy
to
extend
it's
easy
to
do
things
and
you
don't
need
the
internal
information
about
mesas
to
get
modules
to
work.
That's
completely
untrue
and
it's
like
the
opposite
of
what
we
should
be
saying.
We
should
be
cautioning
people
that
this
is
actually
kind
of
dangerous
and
you
kind
of
have
to
know
what
you
have.
What
you're.
D
Do
it?
Okay,
so
we
we
also
have
a
bunch
of
things
where
we
have
examples,
and
this
stuff
is
kind
of
good.
It's
nice
to
have,
and
we
have
we've
got
this
little
blurb
about
library,
names
legit.
It
should
actually
be
in
code
documentation
and
it
shouldn't
be
here,
but
we
have
a
JSON
schema
where
we
or
a
protobuf
schema
where
we
actually
describe
how
we
load
libraries
in,
and
this
should
just
go
in
there
and
then.
D
List
this
giant
list
of
allocator
and
anonymous
module
and
authentication
module
and
hook
module
and
Icelander
module
and
all
the
modules
that
we
have
it's
a
it's,
not
even
a
complete
list,
and
then
we
have
a
very
short
section
about
writing
modules
and
some
versioning
stuff.
So
what
I
did
is.
First
of
all,
I
reworded
a
bunch
of
the
disclaimers
and
the
explanation,
basis
modules
and
secondly,
I
took
the
list
of
all
the
modules
and
instead
made
them
links
to.
D
Page,
that's
either
implements
describes
or
otherwise
talks
about
the
feature
that
the
module
is
affecting.
So
these
links
are
actually
broken
because
of
this
bug
here
that
we'll
have
to
fix
yeah,
they
point
to
like
allocator
points
the
allocation
module
page,
which
talks
about
the
allocation
module
in
this
one
actually
doesn't
exist.
Yet
we
don't
have
a
page
on
hooks
or
the
anonymous
module,
or
even
the
master,
contender
and
detector
parts
like
Authenticator
and
all
HTTP,
authenticate
ease
and
all
that
stuff
goes
to
the
authentication
markdown
page.
D
We
have
references
to
modules
scattered
all
over
the
place
and
it
it
may
or
may
not
help
us
to
gather
that
up
into
a
series
of
more
concise
documentation,
but
that's
not
exactly
what
I
did
here
because
well
didn't
quite
have
enough
time
to
rewrite
every
single
one
of
those
dogs.
Okay.
So
now
this
page
looks
like
it's
got
some
examples:
it's
got
how
to
write
a
module
to
begin
with
how
to
build
one
and
then
a
bit
of
stuff
about
the
versioning
and
then,
if
you
want
to
go
in
and.
B
F
So
I
was
working
on
the
god.
The
process
read
me,
die
MD
and
well,
it's
just
an
introduction
to
how
the
dry
coding
process
and
before
previously
our
MD
are
like
filled
with
a
lot
of
actual
implementation
code.
I.
Think
like
icy
process.
Oh
yeah,
they
say
are
examples,
but
we
probe
well
men.
Won't.
You
have
some
easier
example
that
that
that
when
we
want
to
there's
some
circumstances
that
some
use
case,
how
do
we
use
the
right
process
to
handle
that
so
I
come
up
with
three
examples?
F
The
first
one
is
I
choose
this
because
I'm
not
good
at
writing.
Back.
That's
studies,
I
write
code,
so
the
first
one
is
a
retry
loop.
That's
really
like
probably
used
a
couple
places
so
and
we
I'm
just
come
up
with
the
example
using
a
loop
and
I
explained
exponential
back-off
that
I
use
some
mutable
lambda
here.
So
it's
also
example
about
how
to
use
multiple
I'm
about
to
achieve
that.
F
F
A
A
B
A
D
A
B
This,
but
what.
A
B
B
A
A
How
there's
different
responses
that
exists
that
can
make
your
life
easier,
or
you
can
specify
your
own
response
and
set
the
headers
override
things
like
content
type,
how
you
there's?
We
have
a
specific
call
out
for
Jason
JSON
responses,
what
you
can
do
with
HTTP
requests
like
check
their
method.
You
have
to
do
that
manually
or
specifically,
look
for
path
parameters,
which
is
how
we
do
our
path
parameter,
parsing,
which
is
not
actually
done.
This
example
is
not
done,
and
I
had
barely
gotten
to
even
using
route
within
the
actors
and.
P
A
A
A
D
There,
but
this.
A
C
D
D
A
M
A
A
Maybe
we'll
try
to
do
like
a
quarterly
decathlon,
quarterly
hackathon.
That's
a
trip
to
San
Francisco,
hey
yeah,
that's
pretty
good!
Okay,
sweet
yeah
people
could
say
I'll
really,
however,
that
long
they
want.
We
got
pizza,
beer,
wine
and
if
the
last
mace
is
for
person,
that's
here
just
has
to
let
the
last
non
mace
was
fair
person
out
otherwise,
yeah
stay
as
long
as
you
want
I'm
gonna,
keep
writing
some
ducks
cool
I.