►
From YouTube: Harbor Community Meeting 20190227 - Americas Time Zone
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
Hello,
everybody
and
welcome
to
the
harvard
community
meeting
for
the
u.s
time
zones.
I
am
michael,
michael
and
I'll
introduce
myself
in
a
second,
but
essentially
we
started
the
cadence
of
having
the
hardboard
community
call
every
two
weeks
and
we're
going
to
have
two
of
them,
one
in
beijing
time
which
is
utc
class
8.
I
believe,
and
the
second
call
will
be
or
based
on
a
u.s
space
time
zone
at
8
am
pacific.
A
Hopefully
this
time
is
convenient
for
everybody
and
we'll
start
seeing
a
lot
more
participation
from
european
as
well
as
u.s
based
members
of
the
harvard
community,
so
I'm
fairly
new
to
the
project.
So
if
you
guys
don't
mind
I'll,
introduce
myself
and
we'll
do
a
quick
round
and
get
everybody
else
to
introduce
themselves
as
well,
and
that
will
help
us
start
creating
a
more
vibrant
and
engaging
community.
A
So,
like
I
mentioned
earlier,
I
am
michael
I'm
a
director
of
product
management
of
vmware
and
I
just
started
working
on
hardware
for
the
last
a
month
or
so,
and
I'm
the
program
manager
lead
for
for
hardware.
So
I'll
work
very
closely
with
stephen
stephen,
as
well
as
danielle
and
dao
jun
and
others
from
the
vmware
team.
Helping
define
features
and
functionality
of
hardware
help
us
with
the
future
direction,
as
well
as
run
a
lot
of
the
community
calls
and
meetings
and
and
help
us
create
the
roadmap
for
hardware.
A
So
if
you
guys
don't
mind,
let's
allow
for
everybody
to
introduce
themselves
and
tell
us
a
little
bit
about
how
they're
using
hardware
or
what
their
affiliation
in
the
communities
and
I'll
start
in
alphabetical
order.
If
you
guys
don't
mind
so
al
you're
you're.
First.
B
Hey
michael
thanks,
my
name
is
brad
mizellis.
I
work
for
vmware
and
I
am
a
engineering
manager.
A
A
Nope,
okay,
daniel
you
wanna,
go
next
daniel.
C
A
Thank
you,
daniel
keith.
You
wanna
go
next
hi.
D
Everyone,
I'm
keith,
I'm
a
software
developer
for
rackspace,
I'm
not
a
contributor
yet,
but
I'm
interested
in
working
on
some
of
the
the
auth
related
stuff
for
harper.
I've
been
working
with
daniel
on
his
oadc
proposal.
So
I'm
mostly
here
to
listen.
A
Very
cool
keith
welcome
to
the
community
that
that's
excellent.
The
ydc
proposal
is
something
that's
definitely
a
front
end
center
for
our
for
some
of
the
next
features
of
hardware,
I
will
open
up
the
integration
of
hardware
into
other
tools
and
products,
so
I
look
forward
to
seeing
that
come
along
the.
E
A
I
neil
you
wanna,
go.
A
A
No
there's
a
person
called,
I
neil,
I
I
guess
the
kind
of
bmw,
okay,
yeah
timon
go
ahead.
You
go
next.
E
Sure
I'm
actually
thomas
thomas
munn
and
I'm
a
security
practitioner
and
I'm
using
harbor
as
a
secure
development
delivery.
Private
registry,
I'm
working
on
an
open
work
project
called
go
cloud
and
I'm,
I
think,
I'm
not
a
programmer,
but
I'm
like
a
really
good
security
architecture
person
and
I
can
also
do
documentation.
So
I
think
I
could
help
with
some
of
the
documentation
and
maybe
video
guides
on
how
to
set
up
harbor.
If
people
were
willing
to
teach
me-
and
I
I
don't
mind-
learning
so
anyways
great.
A
Welcome
thomas
thank
you,
jan
at
vmware,
introduce
yourself.
F
Hi,
I'm
yang
I'm
from
the
same
team
with
daniel,
so
I'm
on
the
one
harbor
team,
so
currently
I'm
a
the
core
maintenance
harbor.
So
for
me
I
have
worked
for
harbor,
maybe
more
than
two
years
from
init
team,
maybe
zero
version,
so
I'm
still
working
on
harvard
and
right
now
and
okay.
That's
all
for
me!.
A
Excellent,
thank
you,
jan,
and
both
you
and
daniel.
Thank
you
for
joining
us
this,
this
late
in
in
your
time
zone.
We
really
appreciate
it.
Is
there
anybody
else
that
would
like
to
introduce
themselves.
A
All
right,
let's,
let's
kick
it
off,
like
I
mentioned
you
know
we'll
start
a
a
a
regular
cadence
for
the
hardware
meetings
from
now
on,
you'll
be
able
to
predictably
know
when
we're
gonna
have
a
meeting
and
for
today's
agenda
we'll
talk
a
little
bit
about
the
one-to-date
development
updates
and
talk
a
little
bit
about
some
next
steps
in
open
source
events.
We
are,
we
do
have
an
agenda
on
the
community
repo.
A
So
if
there
is
a
topic
that
you
want
to
introduce
to
a
future
agenda,
something
that
you
want
to
talk
about
something
that's
near
and
dear
to
your
heart,
whether
that's
a
new
feature
or
you
want
to
talk
about
a
specific
pr,
please
feel
free
to
add
it
to
the
agenda.
I
will
start
adding
things
as
I
get
more
comfortable
with
hardware,
so
we'll
we'll
start
having
some
more
engaging
conversations
on
the
one
to
date.
A
Updates
from
a
p0
perspective,
the
hardware
health
check
api
is
done,
the
robot
account
work
is
done.
The
developer
center,
the
configuration
refactor
and
the
press
script
refactor
are
in
very
good
shape
for
the
one
to
date.
Release
one
of
the
things
that
I
wanted
to
mention
is
that
1.8
will
not
ship
until
mid
may.
So.
The
goal
here
is
from
a
development
standpoint
is
that
all
of
the
prs
are
are
tested
and
ready
before
the
end
of
april.
A
So
if
we
want
to
have
a
good
chance
of
releasing
in
time
by
mid-may,
we
want
to
make
sure
that
we
have
all
our
coding.
So
you
can
start
doing
the
ci
testing,
making
sure
that
end-to-end
testing
is
is
complete
and
and
all
our
features
are,
are
validated
and
working
well
in
conjunction
with
everything
else.
That's
coming
in.
So
please
try
to
finish
your
work
by
end
of
april.
A
Some
of
the
p1
work
that
already
underway
on
the
hardware
cli
the
work
is
complete
and
right
now,
faison
and
others
are-
are
working
on
testing,
setting
up
all
the
pipelines
and
making
sure
that
they
they
get
that
work
through
to
the
completed
stage.
A
The
web
work
essentially
what
with
the
web
hook,
is
going
to
enable
is
third
parties
to
be
able
to
integrate
better
with
hardware.
I
think
of
this,
as
you
want
to
get
a
notification
when
scanning
is
complete
or
anytime
a
certain
action.
Harbor
happens
and
you
want
to
get
their
web
hook
notification,
so
you
can
initiate
any
pipeline
or
any
other
action
that
work
is
most
of
the
code
is
complete,
but
there
are
some
open
issues
that
any
further
discussion.
A
We
can
have
a
discussion
on
on
the
on
that
ticket,
but
if
you're
interested,
whether
you
want
to
try
it
out
or
you
want
to
contribute,
feel
free
to
contact
mingming
and-
and
you
can
be-
he
can
loop
you
into
the
discussion-
the
replication
work
that
there's
a
virtual
team,
that's
working
on
that
they
are
meeting
independently
from
the
hardware
community
meetings
and
that's
the
work
that
will
allow
us
to
replicate
hardware
images
and
hum
charts
between
hardboard
and
non-hardware
registries
and
the
way
that
that
work
is
done.
A
It's
basically
split
into
two
main
efforts.
The
first
effort
is
that
there's
a
base
framework
around
the
replication
engine
that
work
is
about
70
done
from
what
I'm
hearing
from
the
team,
so
really
good
progress
there,
maybe
in
a
week
or
so
that
work
will
be
complete.
The
second
part
of
this
of
this
work
is
around
an
adapter
framework.
Think
of
this
as
a
plug-in
framework,
where,
if
you
want
the
replication
target
to
be
another
hardware
instance,
then
you
need
a
hardware
adapter.
A
If
you
want
the
replication
target
to
be
docker,
you
need
a
docker
adapter.
That
work
is
just
getting
started,
so
we
still
have
a
lot
of
work
ahead
of
us
in
terms
of
getting
all
of
that
completed.
So,
if
you're,
really
interested
in
contributing
in
that
effort,
feel
free
to
contact
us
and
and
start
participating
in
the
replication
work
group
as
well.
A
This
is
our
the
these.
Are
the
high
level
updates
on
on
on
version
one
to
date.
Does
anybody
have
any
questions
or
concerns
with
our
work.
B
Hey
michael,
are
there?
Are
there
any
other
features
that
might
make
it
in
that
aren't
on
this
list?.
A
I
believe
there
are,
there
are
a
few
more
minor
features.
We
can
cover
the
full
list
of
capabilities
for
one
to
date,
next,
three
next
meeting
time,
if
that
will
be
helpful
to
everybody.
B
C
Yeah,
absolutely
yes,
I'm
drafting
the
proposal
and
engaging
keys
who's.
Also
in
the
call
for
the
proposal
and
the
plan
is,
the
dropout
proposal
will
be
submit,
hopefully
this
week
or
early
next
week,
and
we
will
start
working
with
implementation.
E
This
is
thomas
that
I
the
security
person.
I
would
recommend
if
it's
just
for
end
users
and
not
applications
to
use
fido
2,
it's
a
lot
more
relevant
and
a
lot
simpler
to
set
up
open
id
and
oauth
2.
Are
there
they're
great
but
they're
very
complex?
So
just
a
suggestion.
A
Thomas
definitely
will
will
steal
some
of
your
expertise
in
this
area.
So
thank
you.
You're
welcome.
C
Yeah,
I
think
I
will.
I
think
I
can
submit
the
pr
for
the
idc
and
you
can
feel
free
to
add
comments.
But
currently
we
are
trying
to
squeeze
that
into
the
one
that
I
release,
but
we'll
see
how
it
goes.
A
Excellent.
Thank
you
another
feature.
That's
not
here
is
the
window
support
that
brad
you
and
a
few
others
who
have
talked
about,
and
we
have
a
pr
open.
We
will
support
windows
images
in
1.7.5,
so
that
means
you'll
be
able
to
push
and
pull
windows.
Images
scanning
for
vulnerabilities
will
not
work
on
windows
images.
That's
just
because
claire
doesn't
support
it
and
may
never
support
it
and
we're
looking
into
what
it
would
take
for
us
to
enable
the
replication
capabilities
for
windows
images
as
well.
So
hopefully
that
will
make
it
for
1.8
as
well.
A
A
We
already
discussed
it
on
the
earlier
harbor
meeting
that
was
catering
more
to
the
folks
in
asia.
So
I
won't
talk
more
than
that
in
this
call.
A
A
We
will
have
both
an
introductory
section
on
introductory
section
on
harbor
to
educate
the
conference
attendees
or
hardware,
but
you
will
also
have
a
deep
dive
and
I
will
encourage
everybody
from
the
community
to
attend
the
deep
dive.
We
can
have
a
discussion
on
the
future
roadmap
of
hardboard.
We
can
deep
dive
into
specific
features,
and
after
that
session
we
can
also
sit
down
and
talk
more
as
a
community
if
there
is
a
need,
an
interest
for
an
ad
hoc
session.
I
think
of
this
as
a
community
meeting
of
harvard.
A
We
can
certainly
arrange
and
schedule
something
like
that
as
well
for
kubicon
in
barcelona,.
A
All
right-
and
I
only
have
one
more
topic
that
that
I
want
to
cover
and
then
we'll
open
it
up
for
for
folks
to
bring
anything
that
that's
of
interest
to
them.
If
you
guys
remember,
there
was
a
pr
that
was
submitted
to
update
the
governance
model
for
for
harbor.
I
wanted
to
make
sure
that
everybody
is
aware
that
the
pr
has
been
retracted.
A
We
will
continue
maintaining
the
current
governance
model
for
harbor,
but
if
anyone
from
the
community
has
any
suggestions
on
how
we
can
better
improve
our
governance
model,
whether
that's
around
voting
membership,
maintainers
or
anything
that
you
feel
can
make
our
community
run
smoother
and
as
a
weld
oiled
machine
feel
free
to
make
the
suggestions
open.
Pr's
talk
to
maintainers
talk
to
me
and
we
can
certainly
collaborate
on
on
any
proposals
and
suggestions
to
find
a
better
way
for
our
community
to
run.
A
E
This
is
my
name
is
thomas
and
one
of
the
things
that
I
really
liked
about
it.
You
know
the
clear
the
clear
scanning
is
great,
but
I
can't
really
use
it
in
my
pipeline
because
if
there
is
a
high
with
no
solution,
the
gate
still
gets
stopped.
E
C
Thomas,
we
actually,
we
had
internal
discussion
about
this
problem,
but
we
currently
are
thinking
that
it's
not
the
right
way
to
solve
the
problem,
because
a
vulnerability
without
a
solution
is
not
less
vulnerable.
So
if,
if
you
enable
the
policy
you
want
to
prevent
a
running
vulnerable
image,
you
you
should
not
ignore
any.
You
know
certain
level
of
vulnerabilities.
E
B
Hi
this
is
brad
one.
Let
me
just
make
a
suggestion
and
see
how
this
sounds
to
you:
what
if
what
if
there
were
a
way
to
white
list
specific
vulnerabilities,
where
you
know
yeah,
because
you
know
from
you
know,
if
you
think
about
daniel's
comment,
I
think
he's
he's
right.
B
But
if
you
review
a
particular
vulnerability
and
make
an
assessment
that
you're
willing
to
tolerate
that
risk,
yeah
and
any
future
occurrence
of
that
one,
you
can
slide,
you
can
let
slide
and
and
then
eventually,
you'd
probably
get
most
of
the
ones
that
are.
That
would.
E
A
So,
thomas,
first
of
all,
great
suggestion,
brad
thomas,
would
you
like
to
open
up
an
issue
in
our
you
know,
repo
with
the
recommendation
and
put
both
the
business
case
the?
Why
behind
it,
like
you
explained
as
well
as
the
this
proposal.
C
Thomas
actually,
there
is
a
issue
opened
by
other
users
asking
for
a
very
similar
change.
So
I
I
will
send
you
the
link
to
your
of
the
the
link
to
the
issue
and
you
can,
you
know,
add
your
comment
and
we
can
continue
the
discussion.
Okay
and
see
maybe
put
that
in
the
roadmap.
Yeah.
A
Is
that
issue
699
daniel
I'm
putting
it
in
chat
right
now
to
see,
if
that's
the
one
that
we're
talking
about.
B
Oh
yeah,
I
was
just
you
know,
was
gonna
answer,
thomas's
general
question,
which
is
that
yeah
we
use
issues
in
github
for
a
whole
range
of
of
you
know
things
that
we
need
to
track.
It
could
be
bugs
and
feature
requests.
B
So
yeah,
if
you
just
create
new
issue-
and
you
know,
as
michael
was
saying
you
know
type
in
you
know
whatever
description
you
have
about
about
an
enhancement,
then
you
know
we
go
ahead
and
tag
them
so
that
we
can
differentiate
bugs
from
from
feature
requests,
but
but
either
way,
that's
the
way
to
do
it.
A
So
the
the
issue
that
I
posted
is
the
right
one,
so
you
can
go
ahead
and
add
your
comments
into
that
ticket,
including
updating
the
justification
the
why
behind
it,
let's
talk
a
little
bit
around.
It's
actually
me
who
did
the
the
request
in
the
first
place.
So
oh.
E
B
Hey
michael,
I
had
a
question
about.
You
know
whether
I
don't
know
if
now's,
if
today's
the
right
day,
but
you
know,
should
we
be
you
know,
thinking
about
coming
up
with
a
mechanism
for
adding
sub-projects.
A
Yes,
so
that's
definitely
something
that
that
we
need
to
evaluate
and
and
meet
and
agree
as
a
community
as
well
as
have,
if
there's
any
proposed
sub
projects
that
are
in
the
pipeline.
I
know
of
one.
We
can
definitely
do
our
diligence
around
that
and
see
how
we
can
do
that.
A
lot
that
in
the
agenda
for
a
future
meeting
grad
thank.
A
A
All
right,
I
will
talk
about
that.
Maybe
next
meeting,
as
always,
all
our
meetings
are
recorded,
there
will
they'll
be
uploaded
to
the
to
the
meeting
schedule
on
github,
as
well
as
the
slides
and
always
go
back,
and
obviously
you
know
we
don't
want
this
meetings
to
be
the
only
forum
for
everybody
to
ask
questions
and
collaborate
with
the
team
feel
free
to
find
us
on
on
slack.
A
E
Question
do:
do
you
have
any
questions
about
my
user
experience?
I'm
asking
you
sure
you
you
want
to
elaborate
on
that
a
little
bit,
oh
sure.
So
one
of
the
reasons
why
I
came
is
because
I
think
that
a
lot
of
the
projects
I
have
the
advantage
of
being
a
complete
newcomer
to
it.
E
So
I'm
a
great
person
to
write
documentation
and
one
of
the
things
like
I
was
trying
to
do,
because
I
I
do
a
lot
of
ipv6
and
it
worked
great
in
some
areas
and
didn't
work
in
others
and-
and
I
know
ipv6
and
docker
are
not
always
friendly
and
it's
probably
not
number
one
on
anyone's
list,
but
I
I
just
found
it
diff.
You
know
I
found
the
I
found
the
documentation
difficult
to
navigate
as
a
new
person.
E
I
mean
I've
started,
studying
docker
content,
trust
and
I've
studied
a
lot
of
the
other
stuff.
But
there's
just
not
a
you
know
from
soup
to
nuts
here
step
one
step,
two
step
three
step
four,
and
that
was
something
that
I'm
definitely
willing
to
write
in
markdown
and
and
have
it
be
part
of
the
documentation.
E
So
I
I
think
that
you
know
like
the
harbor,
you
know
the
docker
installation
goes
very
well,
but
there's
like
all
these
things
that
you
have
to
kind
of
know
like
I
was
thinking
of
maybe
having
like
I
could
write
an
ansible
script
that
would
automatically
http
make
https
work,
have
another
script
that
would
sort
of
be
on
the
client
side
to
set
up
the
docker
content,
trust
in
a
registry
just
those
kinds
of
little
things
that
I
can
do,
but
I
don't
know
how
to
do
them,
because
I
don't
know
how
to
do
them.
E
I've
never
done
them
before.
So,
if,
if
someone
is
willing,
I
would
be
very
happy
to
work
with
them
to
document
these
non-developery
things
and
and
put
them
as
a
my
contribution
is
to
the
community
would
be
to
help
you
know
sort
of
develop.
Some
of
these.
C
It
would
be
extremely
appreciated
tom.
I
agree
our
documentation
on
the
github
ripple
needs.
You
know
heavy
refinement.
I
I
think
we
can
continue
the
discussion,
maybe
on
the
cncf
slack
yeah.
D
E
Yeah
and
I
think
using
more
than
just
writing-
you
know
everything
from
videos
to
screencasts
and
ascii
cinemas
that
you
could
just
go
through
a
complete
setup
of
it,
and
that
way
they
can
just
watch
that
I
find
those
almost
better
than
documentation
and
they're
very
easy
to
update
you
just
go
through
a
new
install.
A
Absolutely
first
of
all,
thank
you
for
for
for
offering
to
help
in
this
area.
It
will
be
much
appreciated
with
one
today.
You're
definitely
gonna
need
a
lot
of
help
documenting
the
new
features.
Some
how-to
guides.
Videos.
Definitely
that's
something.
That's
that's
gonna
be
in
in
our
mind
and
we're
very
likely
gonna
have
a
cncf
webinar
as
well
on
hardware.
So
we'll
I'll
wrote
a
note
here,
we'll
see
how
we
can
leverage
your
expertise
and
help
in
that
area,
and
thank
you
everyone
for
listening
to
me.
I.