►
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).
B
B
B
A
You
rather
oh,
let's
see
here
so
for
the
on/off
toggle
from
Arthur.
My
understanding
UI
is
not
ready.
There's
some
unresolved
discussions
regarding
new
direction.
Access
for
core
users,
so
I
think
that
all
has
been
resolved.
Kami
issued
the
mocks
are
finalized.
Those
are
posted
in
the
issue
description
and
the
consensus
was
that
if
we
were
just
going
to
make
this
in
ultimate
only
for
now
as
it
would
still
be
available,
the
feature
is
still
available,
like
the
underlying
mod
security
or
still
iam.
A
Technology
is
still
there
for
core,
or
at
least
mod
security
Julianne
stole
his
old
reserved
ultimate,
but
moving
forward
we're
just
kind
of
separating
the
UI.
We
felt
like
at
least
near-term
that
was
okay
to
put
the
UI
in
there,
and
you
know
we
can
cross
that
bridge
when,
and
everything
was
end
up
moving
down
to
core.
Maybe
they
just
don't
get
the
UI
to
go
with
it,
even
though
they
may
get
access
to
phillium.
B
It
looks
like
all
all
front-end
work
if
most,
if
not
all,
front-end
work
and
lindsey
is
looking
like
she's
gonna
have
Daniel
take
ownership
of
that
the
front-end
side
starting
next
week
he's
on
vacation
this
weekend,
he's
gonna
coordinate
with
Arthur
and
Sam.
That's
good!
There's
a
good
bit
of
time
zone
overlap
between
Daniel
and
Arthur.
A
A
So
for
this
we're
really
trying
to
tackle
this
in
an
iterative
manner.
So
this
first
path
is
almost
exclusively
just
UI
work,
with
one
exception.
That'll
call
out
here
in
a
minute,
so
right
now
it'll
be
adding
this
whole
new
monitor
in
our
font,
section
Vermont
security
Wow.
We
already
have
that
today,
it's
just
in
a
different
place
in
the
UI,
that's
under
the
managed
apps
page,
and
this
manage
button
will
take
you
to
the
operation.
Kubernetes
managed
apps
page.
Where
is
Amir,
did
the
work
to
add
that
into
the
UI?
A
So
that'll
just
take
you
to
a
new
page
right
now
then
I'll
show
you
the
current
status
and
navels
are
disabled
and
then
for
container
network
policies.
This
manage
button
will
just
take
you
out
to
the
documentation,
so
functionality
wise.
The
way
you
would
turn
it
on
or
off.
Nothing
has
actually
changed
there,
we're
just
adding
some
UI
to
make
it
discoverable.
The
one
cannot
the
backend
work
that
would
be
involved
in
adding
the
ability
to
show
whether
or
not
it's
installed,
enabled
or
disabled
here
under
status,
cool.
A
So
we
really
tried
to
make
this
just
an
absolute
minimal
change
and
one
of
the
big
benefits
for
the
customers
getting
it
here
in
the
UI
is
it
makes
it
more
discoverable?
So,
if
they're
already
here
working
in
the
security
page,
if
they've
been
working
with
some
of
the
this
aster
dashed-
or
you
know
some
of
the
other
technologies
from
secure,
it's
gonna
show
up
on
that
same
page
way,
they're
already
working.
So
it's
going
to
help
it
to
be
a
lot
more
discoverable
by
our
target
audience.
B
Good
questions
definitely
Arthur
you
you're
you're.
Are
you?
Are
you
good
with
all
that?
We
said
today
on
this
one
yeah
awesome.
B
This
would
not
be
that
and
we
may
want
that
first,
but
we
kind
of
did
a
couple
passes
on
this
and
said
it
since
this
is,
is
useful
but
will
be,
will
be
more
useful
in
the
future
and
is
a
key
priority
from
Sam's,
because
it's
one
of
our
quote:
unquote:
North
Star
metrics,
which
is
a
big
priority
for
product
management
in
a
perfect
world.
We
wouldn't
have
chosen
to
do
this
one
first,
the
record
psyllium
process
volume,
usage
metrics,
but
it
does
make
sense
based
all
things
considered
and
I.
Think
Arthur.
B
A
B
Sam
thanks
are
there
in
Sam,
you
know,
I
know
a
bit
about
the
Northstar
metrics
you
know,
but
for
the
rest
of
this
group,
it's
probably
just
a
term
like
my
understanding
is.
Is
that
Northstar
metrics
there's
one
metric
to
show?
You
know
you
know
it's.
It's!
The
I'm
gonna
do
Lord
of
the
Rings
reference
in
a
minute,
but
I'm
gonna
stop
myself.
It's
the
one
metric
to
show
the
value
that.
A
I,
don't
know
how
it
all
ties
back
to
funding
at
the
end
of
the
day,
so
I'm
not
sure
I
can
confirm
or
deny
that
statement,
but
but
I
can
confirm
the
importance.
I
mean
right
now
we
don't
have
any
metrics
at
all
on
usage
of
our
container
network
policies.
We're
still
AM
feature
so
getting
something
in
place
is
highly
important
and
the
most
important
is
the
one
that
the
line
start
like
star,
which
sort
of
feeds
in
the
number
three
here,
which
is
blocked.
I
mean
that's.
A
B
C
I
had
a
quick
look
at
the
Emma's.
That
percent
I
think
I
think
you
chose
a
good,
a
good
breakdown
to
you
out
from
our
understand
you're
doing
the
database
first
Arthur
and
the
red
is
the
red
is
keys.
Were
you
gonna
store
that
given,
given
our
experience
with
mesh
request
for
for
database
changes?
That's
probably
a
good
idea,
but
then.
D
C
D
D
D
D
Each
case
is
like
markers,
nature,
again
crash,
and
there
is
a
chance
that
it
will
Conservation
Service
Workers
this
metrics,
but
unfortunately
we
found
already
solved
that
by
the
nature
of
the
processes,
so
yeah
I
took
all
the
measures
to
minimize
the
impact
yeah.
It's
a
bit
hard
to
project
all
the
context,
because
yeah.
E
C
D
D
C
D
Okay,
my
design
to
right
now
and
I
do
not
care
on
addresses
around
this
Barker
once
a
week
on
the
weekend
and
go
ask
all
questions.
What
did
you
get
missing
this
week
because
just
to
minimize
impact
on
the
cluster,
especially
on
people
at
home,
I'm
thinking
about
it
once
a
week?
So
we
will
be
incrementing
counter
by
a
week,
their
values.
If
it
makes
sense,
it
doesn't
have
to
be
bordered
on
the
graph
in
a
big
increment,
so
it
can
be
bought.
Different
lifting,
but
increment
will
be
weekly
just
to
minimize
yeah.
C
B
Awesome
so
that
covers
those,
so
you
just
make
sure
group
of
us
are
on
the
same
page,
which
it's
not
that
we
were
mostly
there,
maybe
not
completely
there.
On
those
three
items.
I
know
Arthur
as
well
is
the
thing
that
you
believed
we
should
be
working
on
with
a
higher
priority
was
the
ability
among
a
number
of
things,
including
first,
the
ability
for
the
user
to
set
policies
in
psyllium
and
Sam
has
started
a
high
level
issue
for
that
or
but
I
think
Sam.
B
A
A
little
bit
with
us,
okay,
we
do
want
to
have
our
policy
think
of
policy
management
in
a
technology
agnostic
way.
You
know
the
way
I
explained
it
to
to
Andi.
Was
you
know?
The
last
thing
we
would
want
to
do
is:
go
build
a
policy
editor
form
on
security
and
then
go
build
a
policy
editor
for
psyllium
and
then
go
build
a
policy
editor
for
you
know
the
other
two
or
three
technologies
that
we
may
end
up.
Embedding
down
the
road.
You
know
it's
not
natural
for
customers.
B
A
Different
things
not
know,
I
fully
understand
that
so
so,
just
to
clarify
the
idea
is
in
DUI
to
abstract
that
from
user
now,
obviously,
there's
going
to
need
to
be
a
translation
there,
where
you're
actually
applying
them
on
security
or
cilium
policy
at
the
end
of
the
day,
and
so
the
initial
phase
again
trying
to
keep
this
iterative.
The
first
phase
of
this
will
be
for
it
to
work
with
cilium
policies.
A
So
if
it
won't
work
with
modsecurity
policies
or
it
won't
work
with
other
policies
initially,
but
it's
really
more
of
a
design
challenge.
It's
on.
You
know
Andy
to
figure
out.
How
can
we
make
it
feel
like
I'm,
using
a
gitlab
policy
manager
rather
than
oh
I'm?
You
know,
writing
a
cilium
specific
policy.
A
If
that
makes
sense,
I
agree,
there
are
different
types
and
Andy
is
going
to
need
to
account
for
that
in
DUI,
but
starting
with
solium
and
starting
with
policy
packs
so
again,
keeping
the
management
a
little
bit
higher
level
just
so
that
we
can
get
something
out
the
door
and
iterate
from
there.
Where
you
know
it's
just
a
minimal.
You
know
initial
effort
to
put
out
some
kind
of
policy
management,
UI.
C
You
just
said
there
in
the
end
of
thing,
is
gonna,
be
crucial
because
of
that
risk
that
these
things
look
very
different
and
we
we
don't
know
a
lot
about
well
user
is
expecting.
You
know
how
they
they
plan
to
use
that
in
the
gitlab
context,
and
it's
really
important
to
put
something
out
there
soon
as
possible
and
that
feedback
and
adjust
the
course
if
there.
If
that's
the
plan,
that's
awesome.
It.
A
Is
it
is,
and-
and
Andy
is
also
going
to
be
doing,
a
solution,
validation
effort,
which
you
don't
look
close
problem,
validation
and
solution
validation?
These
are
rather
large
efforts.
They
keep
like
two
or
three
months
to
get
everything
through
the
process,
but
it
involves
you
know
interviewing
several
different
customers
and
non
customers.
Do
me
here,
target
profile
and
getting
feedback
from
them
and
collecting
all
together,
synthesizing
at
pulling
out
their
results
and
adjusted
based
on
feedback.
So
that's
going
to
happen
in
parallel,
but
I
don't
want
us
to
wait
until
you
know.
B
That
sounds
consistent
basis.
We
need
a
policy
management
UI.
It
needs
to
take
into
account
the
three
components,
at
least
the
two.
We
have
all
ready
to
start
cilium
and
mod
security
with
a
priority
first
on
cilium
is
without
the
ability
to
manage
the
policies
and
psyllium
psyllium
doesn't
provide
much
value,
you
know
just
accept
all
packets,
and
that
sounds
consistent.
Arthur
with
what
you
believe
should
be
a
priority.
Soon
is
an
ability
to
manage
the
policies
for
psyllium.
Is
that
that
I'm.
D
D
A
Is
now
so
if
I
can
just
speak
to
number
five
for
a
minute
there
I
know
we
kind
of
jumped
down
to
five
feet,
but
I
just
wanted
to
talk
for
a
minute
on
the
five
overall.
So
I
just
wanted
to
make
sure
you
know.
I've
got
full
transparency
here,
and
the
group
understands
where
we're
going,
probably
four
thirteen
one.
So
you
know
overall,
we
definitely
want
to
continue
our
work
and
contain
your
behavior
analytics.
A
I
do
not
have
issues
for
that,
because
I
want
to
guide
our
direction
there
based
off
of
the
outcome
of
the
research
but
and
prototyping
that's
going
on
right
now,
so
we'll
wait
for
some
more
results
to
come
in
there
before
we
decide
concretely
what
our
next
steps
will
be.
The
policy
management
UI
we
talked
about,
and
then
lastly,
there's
going
to
be
a
handful
of
issues
that
I'm
hoping
are
just
very,
very,
very
small.
Things
like
I've
created
one
issue
already,
but
correcting
the
wording
of
some
of
the
labels
in
our
UI.
B
B
Zamira,
Dallin,
anything
that
to
share
on
probably
good
since
I
think
we
spent
last
two
meetings
talking
about
those
two
items
as
well:
maybe
a
one
or
two
minute
overview
of
what
you
guys
have
done
recently
and
what
you're
planning
to
do
next,
just
for
the
group.
So
there
we
all
can
read
the
issues
of
course,
but
I
think
it'd
be
good
to
hear
it
occasionally
as
well.
F
So
no
updates
for
me,
since
our
last
meeting
I'm
still
trying
to
figure
out
a
way
to
stall
agent
as
a
part
of
container
tried
to
write
some
kind
of
automated
script
to
do
it,
but
I've
been
I've
been
working,
some
other
things
too.
I
I
just
waiting
this
one.
Probably
I'll
do
something
tomorrow
on
that
one.
The
web
statistics
work
was
completed
is
nearly
complete
in
terms
of
web
statistics.
B
F
On
target
for
13,
oh
yeah,
yeah
I,
believe
in
terms
of
West,
more
advanced
web
statistics.
I'll
have
similar
issues
of
us.
Arthur
has
because
of
the
we
need
to
get
some
statistic
from
elasticsearch.
We
cannot
do
that
in
one
query.
We
have
to
ask
every
single
elasticsearch
cluster
to
provide
us.
Some
statistics,
I
believe
I'll
rely
on
Arthur
work
in
terms
of
working
website
getting
old
of
that,
because
we
maybe
we
could
combine
those
together.
Both
thing
go
Samir.
E
From
my
side,
since
Friday
I
have
been
cleaning
up,
the
mrs
relate
to
the
sitting
log
on
the
flow
in
be
stuff.
So
there's
just
you
a
Mars
left
over
there,
all
there
Mars
were
merged,
so
we
are
on
track
for
the
team.
No
I
just
want
to
clean
up
this
and
get
a
marriage
as
soon
as
possible.
So
then
I
can
focus
on
the
the
wazzle
thing
for
the
wazzle,
as
you
need
more
genie
to
do
before
being
able
to
say
anything
else,
but
I
had
some
progress
over
there,
especially
I.