►
From YouTube: Mesos Developer Community Meeting (Nov 3, 2016)
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
E
I
E
C
E
H
G
Okay,
so
I'm
gonna
demo,
a
new
feature
we
adding
to
my
cells
1.1.
Well,
my
release
yeah,
but
it's
about
to
be
released.
It's
called
arm
park
pass
group
mystic
container,
so
I'm
gonna
show
you
some
demo
on
that
share.
My
screen.
K
J
B
G
Yeah
so
actually
I'm
going
to
start
a
master
first
on
my
local
machine.
So
actually
let
me
switch
to
fool
me.
G
G
G
G
Sorry
I
should
have
run
this
four
hands
that
I
don't
need
to
do
this
start
the
agent.
If
you
go
back
to
the
UI,
it
won't
work
for
most
basic.
L
G
B
C
G
G
So
I'm
going
to
launch
two
tasks.
What
is
called
producer?
One
is
called
consumer,
so
the
producer,
what
the
producer
does
is
a
use,
some
cpu
memory
and
this
very
thing
posting
basically
use
a
touch.
Some
date
touch
something
in
a
volume
it
creighton
volume
in
apparent
containers,
sandbox
called
share
volume
and
it's
mounted
inside
a
container
in
/
volume.
G
The
image
the
container
use
is
alpine
and
it
would
just
basically
I
could
get
the
current
date
and
touch
a
file
using
the
same
I'll
use
that
name
you
choose
the
day
as
the
name
and
just
sleep
one
second,
and
do
that
forever.
That's
called
producer
and
there's
a
consumer
container
in
the
same
cast
group
which
basically
LS
this
I'll
share
volume
so
attached
the
same,
sheer
volume
and
then
basically
to
a
lab
to
an
LS.
G
So
the
kanay
I'm
going
to
use
yeah,
so
the
command
is
pretty
simple.
I
just
use
that
chess
master
and
get
attached
that
statute
equal
to
j,
some
fun
and
just
follow
this
one,
and
you
can
see
to
task
and
task
group
Oh
start
running
right
now
and
if
you
go
back
to
the
UI
you
can
see
on
both
producer
and
consumer
are
running.
If
you
click
either
all
done,
we
can
see
they're
part
of
the
same
executor
and
both
of
them
not
running
if
you
click
the
sandbox.
G
Actually
let
me
click
the
sandbox
of
the
consumer.
If
we
go
to
ste
out
you're
going
to
see
the
files
created
by
the
producer
is
keep
cleaning
those
dates,
since
it's
one
second,
each
so
you
can
see
art
showing
up
every
second.
G
If
you
look
at
the
sandbox
layouts,
you
can
click
the
temple
executors
sandbox.
You
can
see
actually
on.
So
that's
the
executors
box,
so
the
executor
has
two
containers
running.
So
if
you
click
containers
and
there's
two
containers
bringing
if
you
click
either
up
done,
you
can
see
the
logs
for
each
nestor
container
and
and
the
any
character
see
the
sheer
volume
is
actually
on
top
level
on
a
secure
container
as
well.
G
If
you
click
a
sheer
volume
gang
can
see
all
the
file
created
by
the
producer
and
there's
another
folder
called
tasks
which
basically
they
are
the
the
system
link
between
the
task
ID
to
the
actual
container
ID
in
the
sandbox.
So
this
is
just
simplify
on
people,
finding
those
nasty
container
using
task
ID,
and
it's
pretty
much
it.
So
that's
the
demo,
any
question.
H
Question
yeah
sure
so
I,
don't
so
for
people
who
find
this
stuff
like
myself,
I,
don't
actually
know
what
level
the
group
is
grouping
stuff.
Is
it
at
the
container
level
is
a
very
secure
level.
Okay,.
G
G
G
Yeah
so
basically
like
how
we
support
our
task
group
so
basically
like
to
support
all
like
feature
me
to
type
of
we
need
to
to
set
up
like
a
API
seem
asos
what
means
called
Task
Group
so
basically
on
the
the
framework
has
a
way
to
send
multitask
atomically
to
the
executor.
So
previously,
if
you
want
to
send
two
tasks
to
an
executor,
it's
likely
that
one
task
reach
the
executor
and
the
other
task
get
dropped
somewhere.
G
So
this
is
not
ideal
for
Pollock
feature
because,
if,
like
you
want
to
start
all
the
time,
all
the
containers
in
the
pod
on
simultaneous
that
you
don't
want
any
test
any
like.
For
example,
it's
it's
not
okay
to
start
some
side
car
without
like
starting
your
main
container,
so
I
want
the
property
of
paul
is
like
you
have
to
make
sure
all
the
task,
all
the
containers
in
asking
up
a
secure,
which
the
executor
simultaneously
it's
all
or
nothing
semantics.
G
So
that's
the
task
group
api
and
the
other
API
we
add
to
may
so,
since
the
agent
API,
which
allows
in
arbitrary
executor
to
uncreated
container.
So
this
is
the
agent.
If
you
are
we
introduced,
we
had
three
calls
to
agent
API,
which
is
basically
launch
Ness,
a
container
wing
as
they
contain
and
quien
esta
container.
So
they
say
how
it
works.
Is
this
so
so
say
you
have
a
container
re
running.
G
Your
executors
are
really
running
then
executed
educated
on
the
create
a
nasty
container
underneath
my
container,
so
I
could
go
back
so
on.
So
this
is
the
like
the
high
level
architecture
of
the
nasty
container.
Basically
like
previously,
you
have
a
container,
you
have
an
executor
and
s
if
you
have
multiple
tasks,
but
those
tasks
don't
have
any
resource
isolation
between
them.
So
it's
up
to
the
executor
to
execute
those
tags.
There's
no
resource
isolation
at
all.
G
So
this
is
the
animation,
so
they
take
it
like
when
the
executor
wants
to
create
a
sea
container
extended
launch
to
the
mezzos
agent
on
the
mezzos
agent
world
would
be
responsible
for
launching,
has
to
contain
a
properly
nested
under
the
top-level
container.
I
say
in
this
case
the
ethic
you
want
to
launch
the
Nanjing
X
nasty
container.
It
will
just
call
launch
and
contain
the
continued
riser
will
prepare
the
ngx
sub
container.
For
that
and
there's
another
API
call
watch.
G
So
basically
things
like
executed,
so
basically
agent
is,
is
the
one
that
launched
the
engine
X
nasty
container.
So
how
do
I
get
the
access
status
of
diagnostic
container?
So
all
what
we
do
is
we
we
create
an
API
call.
Watch
sorry
call
wait,
so
the
a
secure
way
stay
on
a
way
for
the
continued
to
be
terminated
and
when
the
container
actually
gone,
the
aging
will
get
the
cactus
status
of
domestic
container
and
send
back
the
correct
Mexico
to
back
to
the
executor.
G
So
the
execute
can
decide
what
to
do
next,
based
on
the
exit
code.
Another
nice
thing
about
this
nested
container
API
is
support.
Arbitrary
level
of
nesting,
so
you
can
have
more
than
two
level
of
nesting.
So
what
use
case
for
that
is
like
say,
I
can't
have
a
debug
container
say
on
the
debugger
nginx
nesta
container
I
can
create
a
three-level
us
to
continue
called
debug
in
underneath
the
net
and
ngx
nasty
container,
so
that
you
can
do
bar
proper
debugging.
G
G
Another
nice
thing
about
the
mastic
container
API
is
that
I
think
is.
Is
we
allow
execute
to
dynamically
Korean
esta
container
versus
like
a
coup?
Benetti's
Polly
had
to
statically
pre-define
those
container
when
you
specify
on
the
past
back
so,
but
here
like
I,
think
we
allow
executors
to
do
more
smart
logic
and
that's
more
flexible
than
what's
there
increment
at
ease
a.
J
Question
so
in
this
nesting,
like
them
continue
our
hierarchy.
How
would
the
process
hierarchy
look
like,
though
so
like
about?
Would
you
mean,
like
offices,
so
in
this
case
of
my
engineers,
are?
Your
container
would
also
be
cool.
Like
am
I
a
kind
of
container
Iser
about
processes
at
work
or
how's
that,
like
so.
G
So
we're
going
to
have
a
init
process
which
called
kept
mesos
container
eyes
or
launch,
which
is
gonna,
which
is
going
to
be
the
arm.
The
pit
one
inside
a
pending
space,
and
then
that
makes
us
continue
eyes
are
launched.
Helper
process
is
going
to
forking
exact,
the
actual
on
user
processes,
but
the
namespace
is
properly
nastiest.
So
if
you
look
at
the
nasty
container
engine
X
here,
so
it's
probably,
if
you
use
pen
name
space
isolator,
it's
probably
nested
it
spin
namespaces,
properly
nested,
underneath
the
top-level
executor
container
yeah.
G
D
G
I
think
it's
up
to
the
isolator
to
decide
what
what's
the
cement
is
elastic
containers.
So,
if
you
want
your
custom
logic,
you
can
actually
be
your
own
likes
a
pending
space
isolator
to
based
on
the
label
of
the
container
or
something
else
to
decide
how
to
do
that.
Like
one
named
space,
he
wants
to
enter.
Do
you
on
the
new
kidneys
or
you
want
the
same
namespace,
because
you
want
to
debugging
something
I,
just
cool.
How
is
this
dual
intake
cycle
by
exposed.
G
E
The
container
can
you
specify
what
namespaces
you
want
to
enter
versus
share?
Oh
now,
you
can't
really
do
that
from
the
users
perspective
right
so
now
face
yeah
them
exactly
what
goes
on,
but
so
we're
in
the
process
of
building
multiple
classes
of
containers
where
the
default
one
would
be
share.
All
the
namespaces
except
the
kid
in
the
mountain
in
space,
those
get
cloned
new
for
your
Nesta
container.
E
G
G
So,
for
example,
of
cebu
isolator
right
now
all
domestic
containers
to
the
same,
see
you
as
the
parent
container.
We
can
potentially
introduce
a
flag
to
seigar
isolator
to
say:
oh,
you
have
a
policy,
you
want
the
nasty
containers.
So
basically,
if
a
bullying
flag
say
if
you
want
the
net
to
continue
meeting
us
in
a
separate
in
SJC
group
or
you
want
that
to
be
the
same
parent
see
group,
so
you
can
actually
have
control
flies
on
those
Isolators
to
properly
undo
configuration.
We
can
support
that.
G
G
I
N
You
look
we're
designing
executor
of
Education
currently,
so
the
operator
API
is
an
authentication
enabled,
but
the
default
executor
does
not
currently
authenticate
so
we're
having
authentication
to
the
executor
area
and
we'll
be
implementing
on
education
in
the
default
executor
with
authorization
to
follow
some
time.
What.
M
N
M
I
I
Kissing
peasants,
right
now
for
the
default
executor
case,
we
do
Nestor
containers
for
tasks,
so
each
faceted
or
national
container
and
use
default
exact
erson.
So
there
the
signal
is
the
status
of
it
well
container
launches.
It
looks
at
the
launch
status
and
then
sends
a
task
running,
but
if
they're
more
better
levels
of
nesting,
there
is
no
mechanism
to
signal
that
it
has.
We
have
a
band
or
procurement
messages
or
something
like
that.
There
is
no
honest
red
container
specific
events
flowing
through
the
system,
yeah.
J
G
So
I
think
having
just
created
ticket
this
today,
so
the
plans
to
move
that
container
riser
launch
helper
process
out
of
the
pen
a
space
so
that
we
can
allow
users
to
ruin
things
like
in
it,
like
some
other
India
to
like
system
being
inside
the
container,
because
this
is
what
I'm,
not
that
great.
If
you
did,
if
they're
not,
it
is
not
a
k1,
so
is,
for
that
case
also,
gas.
J
J
G
I
The
castle
make
a
itself
ilysm
current,
but
their
plans
to
do
it,
but
we
haven't
even
design
dirt
so
right
now
it's
a
fuel
injector
go
take
a
bleep
ing
quote.
I
H
Good
thanks
g
for
doing
that.
I
think
those
helpful
for
you.
H
So
we
have
about
half
an
hour.
I
want
you
to
go
through
the
roadmap,
the
areas
that
we
enjoy
today's
last
night
and
figure
out.
Should
they
stay
there.
She
literally
check
it
out.
Are
they
done
Sarah
a
little
red
parts
on
these,
so
I
admitted
only
get
a
link.
I
love
lyrics,
yeah
yeah,
so
yeah.
That's
awesome.
Thank.
L
H
Bet
in
what,
with
a
median
home
ticket
yeah,
so
there's
stuff
in
here
that
I'm
not
sure
what
the
starts
of
it
is.
So,
let's
try
to
get
through
these
next
time.
I'm
30
mins
should.
I
E
I
B
Know
yeah
pretty
low
zone.
I
O
F
E
G
I
think
cheetah
is
adding
some
metrics
for
on
dat
first
and
then
we
agree
on
how
to
do
the
garbage
crashing
later.
Okay,
cool.
A
A
Have
a
patch
for
that,
and
so
currently
we
use
the
copy,
Baek,
honest
I
as
thief
of
I
care
for
the
prohibition
in
it
for
you
to
buy
candy
noises.
So,
but
ideally
you
want
to
use
the
overly
address
as
a
people
back
and
it
is
available,
if
not
be
just
look
for
the
aux
back
and
it's
this
is
such
a
module
Colonel
a
provision,
the
fire
custom
image
yeah.
So
this
is
why
the
Colorado,
so
we
should
have
a
smart
mechanism
to
choose
the
right.
I
can
because
I
know
it
is
probably.
E
A
E
G
G
G
G
O
G
Yeah
Wow:
what
are
the
improvements
that
you're
making?
Yes,
we
need
to
support
all
the
other
subsystems
on
and
I
also
proposed
that
we
also
support
a
case
where,
like
we
can
do
just
see
groups
isolator
without
specifying
the
subsystems,
so
it
just
basically
pick
up
all
the
up
subsystem
supported
on
the
system.
I
I
I
And
other
custom
support
improvements
case
only
implemented.
Think
right
now
that
we
might
be
working
on
is
the
restart
policy.
The
dapple
guys
are
going
to
work
on
right.
Here
we
went
to
tech
deck
and
many
times
there
for
the
paths
to
its
unproven
and
but
we're
not
actually
working
on
an
appeal
device.
Why
yeah
he's
like
attached
to
this
effect?
Yes,
yeah,
we
checked
research,
I,
hear.
H
You
you
might
have
to
rejoin
the
eye
or
something
yeah.
I
Implements
are
there
really
nothing
to
have
revelation.
Hydroponic
will
be
reversed
every
day,
I
working
on
it
yeah.
So
it's
just
never
goes.
We
have
to
write
the
original
and
then
you
only
ever
yeah
and
you
all
wrote
some
benchmarks
right.
Yeah
I
really
use
I'm
going
to
scream
under
tickets.
Cookie,
okay,
still
lack
any
attached
container
exact.
That's
like
the
biggest
thing
most
of
us
here.
I
I
I
H
E
I
I
So
yeah,
if
I,
want
to
add
that
epic,
here,
okay,
I
just
wanna
just
tell
us
the
ticket
and
we
can
write.
Okay,
that's
one
of
the
big
thing.
That's
happening
politically
start
asks
an
egg
in
this
locality
start
castles.
The
design
doc
would
be
the
designer
go
a
bit
like
about
sunday
telegraph
list,
yeah.
D
G
Edited
or
well
I
I
get
soaked
logo
factor
is
like
a
right.
Now
factor
is
not
pluggable,
which
is
like
a
you
cannot
plug
in
your
own
fetching
mechana
done
like
a
p2p,
so
I
can
go
here
is
trying
to
make
better
pluggable
so
that
I
can
plug
in
your
arbitrary
again
like
using
p2p,
I'm
using
any
arbitrary
mccannon
to
fetch
the
artifacts
or
docker
images.
G
G
I
H
G
G
H
I
It
can
remove
it,
I,
don't
think,
given
us
anymore,
just
assuming
okay,
they
have
nothing
on
gonna
plant
to
that
okay,
first
class
of
his
sources.
I
don't
even
think
any
connection,
I'm
doing
it
in
the
medium
term.
How
did
you
know
you
wanna?
Do
it
with
something
against
Ali
to
the
farlam?
You
ever
answer.
There's
no
fertilizer.
I
I
setting
back
90
on
the
door
time,
but
health
checks
did
did
we
have
something
thing
alucard
someone
is
working
out
to
be
on
it
right,
creative
stuff,
it
with
a
bunch
of
traditional
yeah,
but
it's
not
in
the
media
accounts
across
the
line.
Chloe
is
a
winner
to
be
in
HD
on
checks,
get
support
and
members
to
get
for
supporting
Chris
chicopee
on
checks
for
the
minor
Chelsea.
G
E
H
G
E
H
Ok,
so
there's
something
else
on
the
agenda,
but
let's
open
it
up,
yes,
yeah,
so
it's
51
yeah
we
have
nine
minutes.
I,
don't
have
any
thing
that
won't
bring
up.
G
H
That's
good
actually
so
I
want
I
want
to
start
doing
a
bit
more
demos,
maybe
one
or
two
per
week
to
curb
meeting,
as
opposed
to
just
one
demo,
I'm
thinking
something
along
the
lines
of
something
similar
to
entreat
this.
For
us,
where
we
have
some
new
feature
that
people
want
to
learn
about
and
figure
out
how
it
works,
it.
H
Think
we
could
also
do
demos
of
things
that
are
things
that
already
exist
in
the
code
base
that
people
maybe
should
know
about
or
will
be
useful
if
they
don't
know
about
so
I.
Could
you
know
bootstrap
back
demo
I
talked
about
so
were
the
utilities
that
are
available
and
and
just
kind
of
orient
the
meeting
for
for
us
for
them
right,
as
opposed
to
kind
of
our
user
meeting,
where
we
talk
about
I,
don't
use
tastes
like
that.
I
E
I
G
H
Okay,
yeah
there
was
lots
of
stuff
I
think
it
would
be
useful
if
we
talked
about
you
know
the
difference,
components
and
how
they
interact
and
when
they
should
watch
out
for
some
of
the
principles,
it
means
those
two
for
them
to
do
to
and
follow
I
things
like
that.
Okay
with
you
are
useful
in
terms
of
at
you
like
evaluating
fresh
and
you
design,
doc
with
20
25
people
in
the
room,
I
think
it
might
not
be
the
best
use
over
time.