►
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,
let's
start
wait
a
minute!
Let
me
share
the
ppt.
A
A
Okay,
first
is
this:
is
our
agenda?
First
review
will
introduce
some
hardware
1.9.
A
Third,
is,
I
will
demo?
Some
some
feature
is
about
the
tech
retention
and
the
kota
next
is
some
sharing
from
first
is
sung
from
xinhuang
will
share
their
experience
on
harper
hay
and
then
maximi
from
ovh
in
europe
will
share
some
business
experience
for
their
large
companies
and
the
last
is
the
free
talk.
A
Okay,
current
in
the
past
two
weeks,
hyper
1.1.9
coding
is
almost
done,
especially
the
quota
per
code,
hyper
project
and
attack
redemption.
The
coding
is
done
and
we
are
testing
webhook
pi
is
also
revealed,
and
the
code
is
done
now.
C
A
C
Yeah
I'd
like
to
leverage
our
meeting
to
talk
about
some
latest
updates
from
the
work
group.
I
think
I
have
mentioned
several
times
in
our
community
meeting.
Gopro
is
really
a
good
way
to
you
know
to
encourage
the
efforts
of
different.
You
know
the
members
from
different
organizations.
Yes,
no
matter
where
you
are,
if
you
are
have
the
same,
similar
interests.
C
So,
okay,
we
have
some
background
noise,
so
if
you
guys
have
some
similar
interests
on
some
topics,
you
can
work
together
under
this
work
group.
So
far
we
have
three
group.
I
think
the
first
one
is
replication.
This
is
a
very
it's
our
first
and
in
the
past
two
release.
The
relationship
group
has
delivered
several
key
features,
especially
you
know,
supporter
replication
from
harbor
to
other.
You
know
non-harvard
sheets.
This
is
it's
a
very
important
and
the
replicator
work.
C
Google
will
continue
to
deliver
more
features
in
the
future
and
we
have
two
new
ones.
What
is
the
scanning?
This
group
is
organized.
You
know,
by
a
engineer,
from
anchor
from.
D
C
And
from
vmware
this
work
group
is
a
fox,
is
working
on
to
deliver
a
plugable
scanner
framework
in
next
release
to
let
the
user
select
different
vulnerability,
availability
scanner
to
scan
their
artifacts
in
future,
we
may
introduce
more
other
scanners,
like
some
package
scanner
or
license
checking
or
some
other
complex
checking
scanner
into
harbor.
Based
on
this
new
framework.
C
C
C
So
here
I
want
to
you
know
to
aware
the
reason
why
I
talk
about
this
work
group
is,
if
you
have
some
other
ideas,
maybe
you
can
set
up
a
group
to
encourage
other
members
from
different
companies
to
work
together
with
you
to
deliver
features
to
harbour,
and
if
you,
if
you
have
some,
you
know,
if
you
are
interested
in
the
existing
group,
you
can
contact
the
coordinator
to
join
this
work
group
to
work
together
with
other
guides
to
deliver
the
features
okay.
C
So
this
is
the
work
group
on
the
hardware
community,
and
another
thing
I
think,
is:
maybe
it's
only
related
with
the
china
channel
members
a
way
of
launch
several
offline
events
in
different
cities
of
china.
The
first
one
will
be
heard
in
next
next
month
september.
C
10Th,
we'll
invite
other
end
users
to
share
their
user
kits
of
using
harbor
and
we'll
introduce
more
more
of
information
about
harvard
like
a
root
map
like
some
other
center
related,
and
we
and
all
the
audience
attendees
can
freely
communicate
with
maintainers
to
talk
about
any
topics.
A
Sorry
next
it
could
be.
My
should
be
my
demo,
but
my
but
my
demo
environment
is
not
start
up
yet.
A
A
On
canvas
with
ready
situation
very
easily
hardware,
called
player
photo
and
so
on
with
is
very
easy
because
they
are
better
less
and
you
can.
You
can
set
the
regulator
and
to
solve
the
and
to
solve
the
problem
now
that
radius
regeneration
actually
will
save
s3
very
easily,
but
we
found
a
few
problems
while
having
trying
to
connect
the
internal
and
internal
posterior
central
cluster
and
radius
cluster.
A
There
are.
There
are
two
main
problems:
first,
first
one
and
have
another
initial
hardware
database
yoga.
A
A
According
this,
this
way
harborough
harvard.
A
So
this
is
where
initial
hardware
database
will
be
first,
certainly
harbour
tongue
waterware
with
radius
cluster
with
the
sentinel
how
to
fix
the
problems.
We
made
a
couple
charts
at
the
region
between
harbor
and
the
radius
plaster.
A
Because
the
harbor
radius
cluster,
with
the
sentinel
counters
supporter,
where
with
the
greatest
client,
this
is
the
reason
we
made
a
carbocation
at
the
bridge
hub
haven't
this-
is
the
older
artificial
I
downloaded
from
the
hubble.
I
have
to
download
the
hardware
website.
A
B
A
A
A
A
A
A
A
C
Thank
you.
I
think
it's
it's
it's
it's
good,
so
I
have
a
question
about
the
solution.
So,
okay,
what
so?
The
change
you
did
is
only
about
the
you.
You
know
introduce
possibly
aj
and
the
red
is
h8
right.
You
do
not
do
any
other
change
to
the
original
harbor
herm.
C
Thermal
charger:
okay!
So
let,
let's
summarize
that
you
use
the
postgraduate
and
radius
aj
chart,
set
up
external
procedure
and
already
external
registration.
So
when
you
connect
to
harbor,
you
use
external
right
external
database,
external
already.
A
Yes,
okay,
wait.
I
can't
change
here,
I'm
insane
about
the
rest
of
the
actual
producer.
That's
all
open
source!
Oh
I
I
change
here.
I
I
change
the
default
walls
to
I'm
to
install.
C
A
D
So,
as
you
may
have
read
on
the
on
the
slack
actually,
ovh
is
a
large
global
cloud
provider.
We
are
based
in
europe
and
we've
been
focusing
on
offering
infrastructure,
public
and
property
for
years,
and
we've
been
offering
services
around
containers
for
a
few
months
now,
with
a
managed
kubernetes
service,
and
since
about
two
months,
we
launched
a
beta
product
which
is
well
basically
a
managed
arbor
solution.
D
We've
got
a
few
hundreds
of
of
beta
testers,
so
each
of
them
get
a
dedicated
arbor,
and
we
now
that
we've
got
like
this
few
androids
user
in
production,
we
are
eating
some
operational
and
under
mutualization
challenges.
So
we
wanted
to
to
share
that
with
you.
After
discussing
with
some
part
of
the
arbor
team,
as
this
morning,
I'm
actually
gonna
show
you
my
screen
that
you
can
see
up
a
little
sum
up
of
the
of
the
challenges.
Can
you
see
the
the
power
point
there.
A
D
Perfect,
so,
basically,
there
is
two
types
of
of
things
we
wanted
to
discuss
with
the
community.
The
first
one,
I
think,
will
apply
to
most
of
you.
It's
about
improvement
to
arbor
for
everyone,
essentially
about
making
airbar
more
operable.
D
For
example,
we
we
saw
that
we
have
some
bugs
in
production
bugs
happens,
and
it's
sometimes
very
difficult
to
dig
in
that
bugs,
because
the
way
that
our
bore
is
architected,
it
doesn't
come
with
a
integrated
pricing,
so
we
are
wondering
if
some
of
you
are
interested
in
in
implementing
trusting
in
arbor.
If
so,
we
would
be
really
interesting
to
to
have
your
feedback
and
and
to
discuss
that
together.
D
Another
challenge
that
we
see
is
that
building
arbor
locally
on
our
developer
laptops
will
will
take
a
few
dozens
of
minutes,
which
is
not
easy
again.
If
you
want
to
to
try
some
improvement
or
or
the
work,
so
we
think
there
is
some
efforts
in
to
do
to
to
rebuild
our
more
fastly
and
our
essential
problem
actually
having
arbor
at
scale
is
the
way
that
arbor
manages
connections
to
the
postgresql
server.
D
The
last
one
of
the
problems,
which
is
the
first
one
shown
on
on
this
slide,
it's
maybe
a
bit
more
specific
about
the
fact
that
we
use
openstack
swift
as
a
back
end.
We
do
that
because
all
our
public
cloud
offerings
are
based
on
openstack,
except
kubernetes,
one
and
potentially
a
registry
one.
If
we
continue
with
with
arbor,
and
we
see
that
some
of
the
features
of
arbor
such
as,
for
example,
code
management,
etc
were
not
integrated
with
a
swift
backend.
So
we
did
a
appear
for
that.
D
There
is
a
second
kind
of
subject
that
maybe
is
not
interesting
to
to
everyone,
and
these
subjects
become
really
important
when
you
use
a
arborite
scale
and
especially
if
you
use
dozens
or
drones
or
like
us,
thousands
of
arbor
in
a
given
project,
we
want
to
mutualize
the
the
components
behind
arbor
such
as
redis
database
or
also
maybe
have
the
ui
being
multi-tenant,
etc.
D
D
We
would
be
really
interesting
to
have
a
discussion
together
to
see
if
you
hit
these
challenges.
If
you
maybe
started
working
on
some
solution
to
to
address
that
or
if
not,
if
you
are
interested
to
work
on
that
with
us.
D
So
to
sum
up,
we've
been
working
with
with
arbor
for
a
bit
more
than
two
months
is
now.
We've
got
a
few
hundred
customers
and
we
are
at
the
point
where
we
see
that
we
can't
continue
with
with
the
technology
like
it
is
now,
and
we
are
wondering
if,
if
we
are
the
only
one
in
that
specific
use
case
or
if
we,
if
we
can
work
together
to
to
improve
our
bar
for
for
this
kind
of
use
case-
and
that's
that's
pretty
it
for
me,
in
fact,.
D
Yes,
actually,
we
are
using
kubernetes
as
a
as
a
backend,
so
each
arbor
component
is
deployed
as
a
pod
in
kubernetes.
D
B
D
Actually,
of
course,
we
we
started
thinking
about
just
providing
the
open
source
docker
registry
as
a
standalone
service
and
well
asking
our
customers.
We
discovered
that
there
was
a
lot
of
values
in
the
functionalities
that
arbor
integrates,
such
as
a
clear
integration,
such
as
many
more
features
that
use
entry,
integrate
notary,
etc.
D
So
now
we
discover
that
actually-
and
it's
okay-
I
mean
the
technology
has
not
been
built
to
be
a
multi-tenant
by
default,
but
we
think
we
may
not
be
the
only
one
in
that
use
case,
and
we
wanted
to
to
share
that
with
you.
D
D
So,
thank
you.
Is
this
a
pay
service
for
the
customer
or
dessert?
It
will
be
once
we
reach
commercial
stage,
a
general
availability
and
commercial
stage.
Currently
it's
a
free
beta.
You
can
test
it
by
connecting
to
labs.ovh.com
I'm
going
to
write
that
in
the
in
the
chat
window.
D
If
you
browse
this
website,
you
will
see
a
lot
of
beta
services
that
we
are
working
on
at
the
moment,
and
one
of
them
is
a
managed
private
registry.
You
can
test
it
for
free.
You
just
have
to
register
actually
an
account
in
europe,
because
currently,
our
beta
services
are
only
open
to
our
european
customers,
but
we
will
provide
an
enterprise,
managed
private
registry
within
2020
to
customers,
and
currently
our
first
strategy
would
be
to
do
it
offering
a
managed
arbor,
and
this
is
the
one
that
you
can
test.
D
B
A
Okay,
if
no
other
questions
I
will
to
the
next,
I
will
share
the
hover
1.9
feature:
demo
tag
retention
and
the
quota
project.
Let
me
share
my
screen.
A
Okay,
in
the
past
two
weeks,
we
have
had
a
small
but
important
new
feature
and
we
have
at
the
the
here
we
have
at
the
poorer
time
and
the
push
time
of
the
image
in
our
harbor.
So
based
on
this
new
feature,
we
also,
we
also
make
our
tech
retention
more
powerful
here.
We
here
you
can
see,
we
added,
we
add
more
text
retention
rules
based
on
product
time
and
push
the
time
such
as
you
can
retain
the
most
recently
push
the
image
or
pull
the
image
and
you
can
retain.
C
Swords,
but
do
you
were
you
sure
you
know
the
relationship
with
the
quarter.
A
Okay,
yes,
of
course
I
will.
I
will
also
show
the
quota
and
then
here.
C
A
A
Okay,
I
have
set,
and
the
quota
for
this
project
with
two
henry
the
megabits.
As
you
see,
kota,
also
has
a
new
feature.
If
you,
if
you,
if
you
input
such
as,
if
there
is
no,
it
will
show
red
if
there
is,
there
is
less
cauter
and
the
will
shows
ring
when
the
quota
is
enough.
A
A
A
A
As
you
can
see
business
you
can
see,
five
images
will
be
deleted
and,
let's
see
the
image
again,
only
two
image
that
I
have
to
prove
other
will
be
deleted.
A
A
Do
you
have
any
questions?
Okay,
okay,
if
no
more
questions
about
this
do
anyone
have
other
discussion
want
to
do
any
other
question.
I
want
to
discuss.