►
From YouTube: 12 6 Kickoff: Package
Description
In which we talk about optimizing the container registry garbage collection algorithm, NuGet and Tag expiration policies.
A
We
have
a
few
issues
that
I'm
really
excited
to
talk
to
you
about.
All
three
of
these
have
been
highly
requested
by
users
and
customers
and
I
look
forward
to
launching
these
and
getting
feedback.
The
first
one
is
to
optimize
the
container
registry
garbage
collection
algorithm.
Currently,
the
garbage
collection
algorithm
requires
the
container
registry
being
set
to
read
only
or
downtime.
A
The
problem
is
that
for
organizations
that
have
over
1
terabyte
of
storage
being
used,
the
downtime
could
be
several
hours
to
several
days,
depending
on
how
much
storage
they're
utilizing.
So
in
this
issue,
what
we
plan
on
doing
is
optimizing
the
algorithm
to
make
sure
that
the
process,
while
still
requiring
downtime,
doesn't
run
for
an
entire
weekend.
A
Our
goal
is
to
say
that
if
you
have
one
terabyte
of
storage,
that
it
will
run
in
less
than
4
hours,
which
should
enable
some
of
our
larger
customers
to
run
the
process
lower
their
cost
of
storage
on
them
and
within
a
single
day
with
and
within
less
than
four
hours.
It's
also
important
to
note
optimization,
you
know:
do
we
tackle
optimization,
or
do
we
enable
online
garbage
collection?
A
Talking
about
the
next
issue.
It's
an
MVC
of
a
net
new
package
manager,
format
called
nuga,
which
will
support
net
developers
in
building
publishing
and
sharing
net
packages
right
alongside
their
source
code
and
their
pipelines.
So
this
is
an
MVC,
so
this
will
be
a
not
the
full
scope
of
what
we
may
see
in
our
NPM
or
maven
repositories,
but
for
the
for
the
scope,
I
just
wanted
to
review
this
quickly.
We
will
provide
documentation
for
configuring,
the
new
get
client.
A
So
how
do
you
add
get
lab
to
the
remote
list
we'll
make
sure
that
users
are
able
to
add
a
project
to
the
new
yet
registry
in
an
authenticated
manner,
using
their
get
lab,
username
and
personal
access?
Token
users
will
be
able
to
push
and
pull
and
delete
packages.
The
limitation
of
the
MVC
here
is
that
this
will
not
include
any
front-end
work.
A
There's
a
quick
screenshot
here
of
what
it
will
look
like
it's
very
similar
to
our
other
package
registries,
but
we've
learned
from
other
integrations
with
other
package
managers
that
this
work
often
takes
more
than
one
milestone,
and
we
really
want
to
hit
our
commitment
of
getting
something
done.
So
as
an
MVC,
it
will
only
include
the
backend
functionality
to
allow
for
pushing
installing
and
deleting
packages,
and
subsequently
we
have
future
work
planned
for
adding
in
a
front-end
support
and
adding
in
support
for
groups
and
subgroups,
as
well
as
at
the
instance
level.
A
The
next
one
is
an
MVC
for
a
contained
docker
container
registry
tag,
expiration
policies,
so
we
currently
have
a
bulk
delete.
Api
that
allows
users
to
delete
to
remove
tags
from
their
docker
can
from
their
get
lab
container
registry.
Our
goal
is
to
use
utilize
that
API
to
create
UI
based
container
registry
tag,
expiration
policies-
and
we
do
have
a
you
hot
UI
here
that
might
be
worth
clicking
in
so
for
the
MVC.
A
What
we're
gonna
do
is
focus
on
setting
a
default
tag,
expiration
policy,
which
will
pretty
conservatively
remove
any
tags
that
meet
this
criteria,
which
is
basically
saying
that
if
it
is
30
more
than
30
days
old,
keep
at
least
10,
but
remove
any
that
match
the
commit
sha.
So
our
goal
is
to
start
to
help
users
to
programmatically,
remove
images
that
are
tied
to
a
specific
branch
that
don't
serve
any
long-term
purpose.
A
A
So
that's
it
for
the
twelve
point.
Six
is
six
issues.
I
think
it's
important
to
note
that
there
are
two
issues
that
look
like
they
may
slip
out
of
twelve
point:
five
into
twelve
point:
six
and
I'd
like
to
just
spend
a
few
seconds
talking
about
each
of
those.
The
first
is
a
bug
with
our
NPM
repository,
where
they
Black's
package
dependency
data,
and
the
workaround
is
that
you
have
to
run
NPM
install
two
times.
This
issue
is
currently
in
maintainer
review.
A
We're
hopeful
that
it's
going
to
make
it
into
twelve
five,
but
if
it
doesn't,
it
will
slip
into
twelve
point
six
and
then
finally,
the
Konan
repository
I've
talked
about
this
over
the
past
several
milestones.
This
is
currently
in
maintainer
review.
There
is
a
chance
that
this
slips
until
twelve
six
as
well,
but
this
would
be
another
package
manager
format
similar
to
what
we
talked
about
for
nougat.
That
would
allow
C
and
C++
developers
to
build,
publish
and
share
their
their
packages
and
dependencies.
A
Okay.
So
that's
a
brief
summary
of
what
we're
working
on.
If
you
have
any
questions
or
comments,
please
feel
free
to
always
reach
out
to
me
and
T
rysiek
at
lab
comm
or
comment
in
the
issues.
We
love
feedback
and
we
love
when
our
users
contribute.
Thank
you
and
look
forward
to
launching
these
features.