►
From YouTube: CNCF Harbor's Community Zoom Meeting - July 28, 2021
Description
CNCF Harbor's Community Zoom Meeting
A
A
A
C
A
C
But
those
are
the
epics
or
the
themes
hey
no
longer.
I
wonder
if
you
can
talk
about
the
stuff
that
we're
doing
for
arm,
and
you
know
the
work
that
we've
been
doing
with
a
lot
of,
because
I
think
I've
mentioned
a
couple
times,
but
ultimately
we
weren't
able
to
get
anything
released
right.
There
was
nothing.
C
There
was
nothing
released
in
the
2.3
slipped
into
2.4
and
maybe
for
the
folks
that
were
interested
because
I
have
seen
some
tickets
in
the
past
on
you
know.
When
are
you
going
to
have
an
arm
build
of
harbor?
What
is
their
thinking
here
and
is
it
going
to
be
released
under
the
harper
repo,
the
harper
project,
or
is
it
going
to
be
under
some
other
project?
And
how
are
we
thinking
about
this.
D
Actually,
we
do
not
have
any
a
lot
of
update
about
the
arm
because
of
the
the
contributors
are
busy
on
their
company's
business
strategy.
So
we
just
escaped
the
recent
several
weeks:
okay,
but
the
the
basically
we
we
wanna
to
shape
her
arm
align
with
the
2.4
release
and
the
contributors
will
prioritize
their
their
tasks
in
the
last
months.
A
C
All
right,
yeah
sounds
good.
Thanks
for
the
update.
I
haven't
been
involved
in
this,
so
much
so.
For
those
that
don't
know
it's
there's
a
company
called
aladda,
which
is
a
cloud
cloud
company
in
china.
That's
been
driving
this
with
us
previously,
but
like
going
inside,
you
know
they've
been
busy
with
their
own
work
for
some
time.
C
Yeah,
so
I
mean
this
is
much
more
of
a
status
update
for
now
join
us
and
orlan,
there's
nothing
to
demo
for
this
one,
but
I
think
for
next
one
we'll
have
something
planned.
I
think
I
think
we'll
go
with
the
proposal
at
the
very
least
for
how
we're
thinking
about
adding
tracing
right.
So
you
can
look
at
a
request,
as
it
makes
its
way
through
the
various
components
of
harper
and.
D
C
C
You
know
through
a
headless
service
through
hardware
applications,
and
so
when
you,
where
we're
really
there's
a
lot
of
performance,
performance-related
work,
that's
going
on
right
now
and
we're
thinking
about
how
to
make
our
replication
much.
You
know
more
resilient,
much
more
scalable
right
we've.
Never
we
know
we
can
configure
two
replications
between
a
heart,
for
instance,
and
and
another
registry,
but
we've
never
really
tested
the
use
case
where
you
have
a
hubspot
deployment
of
a
a
central
harbor
right,
a
central
harbor.
C
That
is
the
harvard
that
exists
today
and
then
rotating
out
to
a
series
of
series
of
harvard
lights
on
different
edge
sites.
Right
and,
if
you
think
about
this,
for
you
know,
for
retail
right
when
we
talk
about
edge,
we're
talking
about
retail,
something
like
ups
or
starbucks
or
potentially
looking
at
you
know,
anywhere
between
100,
harvard
instances
on
edge
notes
to
possibly
a
thousand
or
ten
thousand,
and
so
that's
kind
of
the
scale
that
we're
dealing
with
that's
kind
of
the
forward-looking.
C
They've
set
it
up
just
like
I've
like
I've
talked
about,
we
have
worked
with.
This
is
a
customer
of
vmware,
and
I
think
you
know
through
that
customer
we
we've
really
been
shaping
and
driving
some
of
these
requirements
around
harvard
light,
but
that's
something
we're
going
to
be
releasing
for
the
oss
community.
Like
I
said,
but
yeah
I
mean
the
basically
the
the
use
case
that
the
use
case
with
edge
right
now
is
that
the
hardware
instance
on
the
edge
site
is
not
does
not
have
to
be
full
featured
right.
C
You
know
thing
that
we
have
to
be
careful
about
right.
Now
is
really
the
replication
right
because
with
edge
sites
they're,
not
24
7,
you
know
highly
available
right,
they
might
go
down
if
what
happens
if
you're
doing
replication
and
the
site
goes
down,
sometimes
these
retail
sites
don't
get
powered
back
up
until
maybe
you
know
hours
or
24
hours
later
and
ideally,
the
hard
replication
should
be
resilient.
D
C
That
it
just
picks
up
where
left,
where
you
left
off
right,
which
you
can't
do
right.
You
can't
do
that
right
now,
so
yeah,
the
replication
is,
is
like
the
biggest
the
biggest
improvements
that
we
need
right
now.
I
think,
and
then
you
know
we
have
to
make
harvard
smaller
for
it
to
run
on
the
edge
site
right.
Harbor
right
now
is
too
big.
It
takes
too
much
memory.
It
takes
too
much
cpu
and
we've
heard
typically
on
the
next
site.
You
know
we're
working
with
anywhere
between
a
one.
C
You
two,
you
know,
maybe
likely
a
two
you
right,
possibly
a
for
you
server
right,
just
a
single
server
or
two
servers
on
in
half
a
rack
of
hardware
space,
and
you
know
that
has
to
run
the
entire,
the
entire
kubernetes,
this
drill
right,
plus
the
hardware
registry.
So
it's
shared
with
the
rest
of
your
your
stack
right.
If
it's,
you
know,
obviously,
if
it's
a
vmware
stack,
vmware
customers,
there's
the
vmware
software
data
center.
C
But
if
you,
if
you
are
another,
if
you're
using
another,
you
know
kubernetes
distribution,
possibly
rancher
or
or
anthos
or
openshift
or
some
other
diy
cloud,
then
it's
the
same
problem
right.
You
can't
it's
not
just
running
a
harbor,
it's
running,
harbor,
plus
the
rest
of
your
kubernetes
stack
and
so
harper
as
it
exists
today
is,
is
way
too
big
for
that
and
there's
no
need
for
it
to
be.
You
know
to
take
that
much
resources,
because
a
lot
of
these
features,
I
think,
won't
won't
get
leveraged
very
heavily.
C
I
I
don't
think
customers
will
be
pushing
you
know
from
the
edge
side
to
the
central
harbor.
It's
going
to
be
one
way
for
a
lot
of
these
applications
for
a
lot
of
these
actions,
and
you
know
they
have
to
be
centrally
gated
scanned
signed
and
then
they're
pushed
out
to
the
edge
sites
so
that
that's
kind
of
the
assumptions
that
we're
working
with
so
does
that
sort
of
answer.
Your
question
yep.
A
A
I
really
want
to
to
do
more
often
notifications,
so
even
for
the
minor
releases
so
can
we
can
we
work
on
some
some
kind
of
process
how
we
can
get
like
notification
internally
through
the
hardware
team
and
and
and
then
I
can
work
on
the
notification
through
the
my
necklace,
feeder
or
whatever,
because
that's
that
those
minor
releases
are
not
scheduled
really
right.
They're
on
on
demand
pretty
much.
A
C
Yep,
so
there
is
a
harvard
channel
within
our
company
slack
that
gets
notified
from
from
different
ci
runs,
but
I
don't
think
it's
limited
to
just.
I
don't
think
it's
the
action
of
uploading
it
to
github.
It's
really.
We
produce
a
successful
build,
but
that
kind
of
you
know
it's
a
precursor
to
what's
about
to
happen
right.
You
can
use
that
as
to
kind
of
know
that
hey
we're
getting
ready
to
release
a
build
and
then
hey
lion,
is
there
a
way
to
send
notification
to
slack
every
time
or
to
email?
C
Well,
yeah
I
mean
orlan
is
thinking
about.
How
does
how
can
he
get
alerted
right
because
he's
not
in
our
internal
engineering
channel
he's
in
project,
maybe
or
maybe
we
can
announce
it
in
the
project
harvard
channel
as
soon
as
as
soon
as
as
you
upload
the
container
images
or
you,
you
know
you
are
releasing
it
up.
D
C
C
D
C
A
C
C
C
A
Yeah
all
right
and
yeah
by
getting
the
the
data
out
of
github
and
calculating
the
the
elephant
factor.
So
it's
very
simple
calculation.
But
for
now
it's
so
it's
a
ratio
between
total
commits
and
and
commits
made
by
the
the
first
one
or
two
company
organizations
and
vmware
is
far
more
exceeding
a
number
than
anyone
else.
Combined.
A
A
C
You
know,
they're
not
consistent
enough
right,
and
this
is
not
to
blame
anyone,
but
you
know.
I
think
this
has
really
been
something
that
we've
struggled
with.
We
try
to
be
mindful
of
everyone's
responsibilities
within
their
own
companies.
Right,
not
everyone
is
getting
compensated
to
to
actually
work
on
harper
but
yeah.
I
feel
like
you
know
it
comes
and
goes
there
were.
There
were
releases
over
the
last
two
years
that
you
know
they
were
filled
with
external
contributions.
C
At
times,
then
there
were
other
releases
where
it
was
very
hard
to
get
something
going
right
and
we,
you
know,
I
think
we
we
have
certain
dates,
that
we've
committed
to
right
and-
and
you
know
that
forces
us
to
sort
of
you
know,
draw
a
cutoff
date
for
when
features
can
get
kick
and
get
merged
because
it
impacts
our
it
impacts
our
ability
to
release
on
time
right.
We
always
try
to
release.
C
C
You
know
work
that
we
wanted
to
to
release
in
the
harbor
and
in
the
harbor
in
a
particular
harbor
release
right
and
they
get
pushed
out
and
sometimes
they
never
get
completed.
And
I
just
wonder
you
know
how
do
we,
like?
You
said:
how
do
we
get
first
of
all
get
more
contributors
to
come
to
the
table
and
then
also?
How
do
we
work
with
them?
C
D
C
C
D
C
Get
something
when
they
get
something
else
within
their
own
company,
then.
Obviously,
that's
the
utmost
importance
in
in
the
harbor.
The
os
stuff,
unfortunately
suffers.
I
think
you
know
it's
it
all.
It
obviously
works
best
if
they're
working
on
something
that
depends
on
their
work
on
harbor
or
is
tied
to
their
work
in
harvard
in
a
big
way
right,
the
stuff
that
they
work
on
for
their
own,
their
employers,
and
so
I
think
you
know
this
isn't.
C
And
just
be
very
clear
on,
you
know
what
they
need
and
why
they
need
it
ultimately,
and
how
does
that
impact
their
product?
You
know
some
of
their
integrations
and
things
like
that
I
found
you
know.
I
found
those
kind
of
partnerships
to
be
the
most
fruitful
is
is
when
you
know
exactly
what
everyone
is
coming
to
you.
B
B
Yes,
it's
really
out
of
date
right
now,
so
it's
it's
our
commitment
to
the
community
when
we
publish
the
roadmap,
so
everyone
knows
what
we're
working
on
and
that
makes
it
easier
for
people
to
contribute
as
well,
because
otherwise,
if
they
don't
know
what
we're
working
on,
they
don't
know
if
they
can
contribute
so
having
the
roadmap,
updated,
linking
out
to
proper
tracking
issues
for
new
features
and
or
milestones
or
epics.
Or
what
have
you?
It's
super
important.
C
C
C
C
I
need
to
write
like
a
goals
and
or
philosophy
document,
that
kind
of
highlights
where
the
project
is
going,
because
the
project
I
feel
like
has
taken
off
pretty
well,
but
yeah
there
are
other
there
there.
You
know
some
major
themes
in
the
future,
as
we
think
about
expanding
into
you
know
harvard
as
a
service
harbor
for
edge.
You
know
other
just
other
distributions
of
hardware
like
like
like
harbor
arm,
and
things
like
that.
C
C
C
A
C
The
sprint
is
just
two
weeks:
it's
not
possible
to
see,
I
I
don't
think
it's
possible
to
see
which
sprints
are
in
a
particular
release,
but
you
know
those
are
roughly
the
dates
for
the
sprints,
so
you
can
see
what's
being
worked
on.
You
know
in
the
next
two
weeks
or
next
four
weeks.
Basically,
and
the
project
board
is
really
for
you
know,
issues
it's
it's
for
you
know.
D
D
A
C
C
D
C
C
So
I'm
talking
about
vmware
in
this
case
they
have
a
real
need
around
a
hybrid
light
for
edge
deployments
and
that's
kind
of
where
we've
taken
our
cues
and
been
you
know,
hashing
out
the
requirements
but
yeah.
I'm
I'm
happy
to
chat
about
this
on
the
community
call
as
well.
I
have
thought
about
this
before,
but
not
you
know,
do
it
to
a
really
with
a
really
detailed
proposal,
because
it's
in
flux
in
her
for
downstream
as
well.
It's
just
you
know.
I.
D
A
A
I'm
asking
because,
as
far
as
I
know,
for
example,
companies
like
ericsson,
they
deploy
a
lot
of
stuff
in
in
their
edge,
and
I
know
that
we
have
people
from
eriksen
engaged
with.
If
I'm,
if
I'm
not
mistaken.
So
maybe
we
can
just
an
idea.
We
can
approach
them
to
collaborate
on
this
one
because
inevitably
they'll
need
that
functionality
as
well,
if
they're
aiming
towards
harvard
to
be
in
production
use
for
their
batch
solution.
For
example,.
C
E
E
A
E
E
A
E
But
we
need
to
know
the
the
requirement
and
the
scope
currently
because
I
asked
for
a
yeah.
We
need
to
know
what
is
the
status
like
the
proposal
where
we
can
contribute
on
first
on
the
document
basis
and
then
see:
okay,
what
what
other
customers
have
and
how
can
this
be
adapted,
what
they
have
and
what
they're
working
on,
because
it's
not
yet
ready,
and
basically
they
mostly
is
one-
is
using
multiple
hardware
instances
full-blown
one
and
the
other
one
has
a
more
customized
version
yeah.
C
D
C
A
C
Yeah,
it's
a
cap
or
it's
a
series
of
caps
but
yeah.
We
we
pushed
a
proposal
to
the
community
repo
and
we
don't
have
a
process
to
really.
You
know
for
people
to
vote
on
it.
I
think
we
just
internally,
you
know,
get
consensus,
and
then
you
know
what
we're
fairly
good,
with
making
sure
everyone's
comfortable
and
aligned
right
and
then
we
just
start
working
on
it.