►
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
Okay,
so
let's
start
can
everyone
hear
me.
B
A
So
welcome
to
the
call
the
community
call
half
an
hour
on
the
pm.
My
name
is
alex
and
still
today,
we're
gonna
take
a
quick
look
at
the
1.10
release
first
and
then
we're
going
to
be
doing
two
demos,
one
for
limited
guest
rule,
another
one
for
tag
immutability
and
then
we're
going
to
have
a
quick
update
from
daniel
on
the
progress
we're
making
on
oci
image
support.
A
So,
first
of
all
on
the
1.10
release,
we're
still
on
schedule
to
release
a
release
candidate
around
the
second
or
third
week
of
november.
B
A
A
A
So
this
is
to
prevent
accidental
overrides-
and
this
is
effective
for
not
just
pushing
but
as
well
as
replication
for
re-tagging,
and
so
we
had
released
a
feature
called
tag
retention
which
which
allows
users
to
set
policies
to
manage
life
cycle
of
container
images,
so
images
that
are
tagged
as
immutable
or
also
not
cannot
be
deleted
via
attack
attention.
So
next
I
will
let
log
into
the
demo
so
I'll
stop
sharing
my
screen.
C
Oh
yeah,
okay,
let
me
share
my.
D
B
C
Okay,
let's
start
the
demo
before
I
go
into
the
details,
I
want
to
give
you
some
background
about
the
remember
immediate
attack.
The
the
original
requirement
is
from
the
community.
So
someone
some
guy,
found
an
issue
about
a
removable
repository.
C
Okay,
some
guy
filed
an
issue
in
a
great
harm
about
the
immigrant
repository
from
the
original
requirement.
Is
that
the
other
administrator
I
like
to
make
a
specific
repository
immutable
so
that
the
image
that
cannot
be
re
overrided
on
or
cannot
be
deleted?
C
So
it
seems
to
be
one
of
the
most
popular
requirements
from
the
community
so
far,
so
we
can
see
the
requirement
a
lot
of
people
jump
up
about
the
requirement,
so
we
decided
to
put
it
into
the
1.10
releases.
So
if
you
want
to
know
some
details
about
the
immutable
pack,
I
have
already
of
open
tech
retention.
I'm
sorry
immutable
tag
proposal
in
the
community
report,
so
you
can
go
to
the
details
to
see.
F
Hey
jan,
we
can't
really
hear
anything.
I
don't
know
if
if
your
microphone
went
dead
or
something
it
shows
that
you're
talking,
but
you
can't
hear
anything.
F
F
Hey
alex
and
jan
is
having
some
trouble
with
the
internet.
Connection
stephen
is
asking
if
we
can
switch
to
away
and
then
we're
all
in
the
office.
A
A
It
yeah
he's
next
to
me,
but
some
reason
is
this:
mic
isn't
coming
through
so
yeah:
let's
can
you
stop
sharing
yeah.
A
A
A
So
we've
gotten
requests
to
create
a
limited
guest.
So
this
is
basically
for
certain
deployments
or
specific
tendency
models
where
you
might
have.
You
know
different
customers
in
the
same
project,
where
you
don't
want
any
user
to
have
visibility
into
the
projects,
all
the
other
members
in
the
project
and
have
to
have
limited
access
to
the
logs.
A
So
we've
created
a
new
role
in
harvard
called
them
in
the
guest
and
in
the
future.
We're
gonna,
you
know,
allow
user
and
allow
the
project
admin
to
create
his
own
role.
Basically,
his
custom
role.
We
can
specify
the
permission
set
for
push-pull
replication
scanning
et
cetera,
but
for
now
we've
created
this
idea
of
a
limited
guest,
which
is
has
a
set
of
permissions
slightly
more
restrictive
than
the
guest.
B
G
Okay,
the
limited
caster
was
introduced
in
harbor
version
1.10.
It
has
the
same
permissions
of
the
customer,
except
except
that
it
don't
have
the
have
the
permission
to
save
the
members
and
the
logs
of
the
project.
G
Here,
when
create
a
new
project
member,
we
can
select
the
limit
guest
rule
and,
let's
first
create
a
new
user.
G
G
At
a
pickle
as
as
the
beginning,
the
particular
number
infer
here
here
is
the
particular
membrane
for,
but
the
limit
against
the
word
don't
have
the
permission
to
view
the
particular
number
in
first
of
all.
At
this
page
the
particular
member
is
load
shoe.
G
B
B
G
G
G
B
G
G
B
G
F
I
think
thank
you,
that
was
great,
that's
a
very
powerful
stuff
and
it
will
certainly
enable
some
of
our
hardware
users
to
host
hardware
in
a
multi-tenant
environment
where
different
tenants
may
come
from
different
organizations
and
shouldn't
see
each
other
and
have
this
limited
permission.
So
this
is
great.
A
Yeah
so
yeah
I
mean
just
one
thing,
but
the
current
guest
role
also
does
not
have
push
access
only
4x,
so
I
listed
that,
but
that
hasn't
changed.
It's
mainly
the
the
restriction
of.
A
C
C
Download
the
background
is
that
some
guy
found
the
issue
in
the
github
about
the
report
in
mobile
repository,
and
it
seems
that
it
was
one
of
the
most
popular
issues
in
the
github.
Usually
so
we
decided
to
put
the
immune
attack
in
1.10
and
so
far
as
you
know,
harbor
do
not
have
a
way
to
protect
your
reporter
and
text.
So
anyone
who
has
the
right
permission
can
overwrite
any
text
in
the
project
so
for
the
immune
attack.
C
C
You
will
see
that
there
is
one
more
type
name
immunotype
in
project
detail
view.
C
So
if
I
go
to
the
immunotag
we
can
set
up
if
you
are
familiar
with
the
attack
retention,
it's
very
easy
for
you
to
get
started
to
use
the
enable
dac
before
that.
The
ui
is
quite
similar
with
the
tech
retention.
C
C
That
way,
you
can
see
that
I
I've
just
pushed
the
hello
world
latest
into
my
environment,
and
I
I
want
to
set
a
rule
to
protect
the
hello
latest.
C
So
this
rule
means
that
any
repository
with
the
attack
latest
will
be
cannot
be
its
immune
protect.
C
C
C
C
Removable
rules
in
per
project
each
one
contains
a
matching
repository
or
matching
text
or
including
reports
or
including
text.
It's
very
similar
with
the
text
retention
use.
As
that's
more
that's
all
my
demo.
Do
you
have
any
questions
about
that?
What
is
the
rules
conflict
with
each
other?
What
do
you
mean
complete.
E
So
yeah
yeah.
I
think
that
we
also
have
some
demo
about
when
we
run
doing
the
dry
run
from
tech
detention.
If
this
tell
is
immutable
and
we
will
exclude
that
from
tech
retention,
are
we
going
to
damage
day
or
time
until
next
time.
C
It's
under
review,
let
them
know.
A
Okay
thanks
william
yeah,
so
basically
those
are
the
two
features
we
wanted
to
demo.
Also
just
one
quick
thing:
if
you
know
because
immutability
overrides
tag
retention
right,
so
any
tag,
that's
configured
immutable
will
not
get
picked
up
by
attack
retention,
but
we
will
send
a
web
hook
to
let
the
user
know
that
you
know
images
that
were
marked
for
deletion
by
attack
retention
are
not
deleted
due
to
mutability,
so
the
user
can
go
into
system,
settings
or
project
settings
to
turn
off
immutability.
A
Like
long
and
demo,
you
have
to
turn
off.
You
have
to
turn
off
immutability
before
you
can
do
anything.
It's
of
the
highest
presence
over
all
other
lifecycle
management
capability
features
in
harbor,
so
we
had
some
other
infra
other.
A
We
had
another
thing
we
want
to
share
on
oci,
but
we
ran
out
of
time
so
we're
going
to
share
that
next
time,
daniel's
going
to
share
that
next
time.
So
I
hope
you
guys
enjoy
this
presentation
and
I
will
share
the
meeting
on
the
harper
repo
all
right.
There's
any
questions.
F
Any
questions
or
concerns
from
anybody
in
the
community
on
or
either
of
those
presentations
or
anything
related
to
hardware.
I
Hi,
I'm
moshe
I'm
a
little
bit
new
here,
but
I
have
a
couple
of
concerns
regarding
the
upgrade
from
previous
versions
of
harvard
to
1.9
and
1.91.
I
So
there
have
been
a
good
couple
of
issues
reported
regarding
failures,
migrating
issues
encountered
with
oci
images,
zero,
byte
images
and
it
I'm
I'm
not
seeing
much
attention
being
placed
on
it.
I
might
be
missing
something
but,
like
I've
been
trying
to
upgrade
harbor
for
a
while
now,
and
it
fails
on
my
repository
for
the
types
of
issues
which
are
not
unique
to
me.
F
Hey
so
so,
basically,
what
you're
saying
is
you're
trying
to
upgrade
hardware
to
1.9,
to
mention
from
1.5.
I
No
from
like
1.85
1.83,
it's
1.8
to
1.9,
so
it's
just
a
step
release,
but
it's
the
the
resilience
of
the
migration
tool
for
the
quota
tax
and
that
there's
there
are
about
five
or
six
issues
logged
and
ready
for
it.
So
this
is
not
something
unique
to
me,
but
all
of
the
areas
that
I've
encountered
have
already
been
locked
and
I
I
think
it
needs
to
receive
a
little
bit
more
attention.
F
Absolutely
can
you
send
me
a
slight
message,
my
alias
is
then,
I
left
m
and
the
number
two
with
a
link
to
those
issues,
you're
mentioning
and
it's
more
specific
about
your
environment,
like
how
many
images
do
you
have
or
what
the
size
for
that
conversion
and
the
actual
releases
that
you're
upgrading
from
to
two
and
the
errors
and
and
the
errors
you're
getting
at
the
same
as
the
links
and
I'll
have
we'll
have
someone
look
at
it?
H
I
Okay,
great
thank
you,
but
other
than
that
great
job,
guys
hub
is
really
awesome.
F
Are
there
any
other
questions?
There's
a
question
on
chat
by,
I
believe,
is
miming.
H
Yeah
yeah,
in
fact,
I
believe
it
did
it's
implemented
via
a
rule
calculation,
so
it
does
have
some
impact
on
performance
but,
as
cn
pointed
out,
it's
just
acquiring
db.
So
that's
a
pretty
trivial
downgrade
of
performance.
I
believe.
B
F
Alex
we
should
make
sure
we
document
that
in
the
documentation
for
immutable
tags,
so
that
folks
are
aware
that
if
they
do
want
to
turn
on
the
ability
on
a
project,
it
will
have
some
performance
hit
when
they
do
push
and
pull
operations,
because
this
api
needs
to
be
reconciled.
So,
let's
make
sure
we
capture
that
in
the
docs
as
well.
A
A
All
right
any
other
questions.
F
Someone
chinese
feel
free
to
alex
can
do
the
translation,
so
I
no
need
to
ask
in
english
if
you
know
as
comfortable
about
it.
H
A
You
are
you're
muted,
by
the
way,
I'm
speaking
you
will
type
in
chinese.
Oh.
B
H
A
G
A
No,
nobody
has
any
other
questions,
then
that's
it
for
us,
and
so
next
week
we
will
share
some
progress
on
oci
image,
image
support
and
I
think,
by
this
time
from
now
we'll
have
a
better
look
at
the
all
the
features
we're
releasing
for
1.10.