►
Description
Test tags for specific kinds of cloud provider tests.
- Continue with gce-pd tag
- Disable tests with these in K/K Prow
- Introduce StorageProvider tag
A
Welcome
to
the
october
7th
2021
cloud
provider,
extraction,
working
group,
meeting
of
sig
cloud
provider,
these
meetings
are
being
hosted
by
the
kubernetes
group
and
the
cncf
and
as
such,
we're
adhering
to
all
of
their
practices,
most
of
which
amounts
to
please
be
considerate,
polite
and
inclusive
of
all
your
fellow
participants.
So
please
be
polite.
Considerate
and
inclusive
of
all
your
fellow
participants,
I'm
gonna
go
ahead
and
share
my
screen.
A
B
B
So
this
is
the
result
of
talking
to
some
people
from
sig
storage
and
the
part
of
part
of
storage
has
stuff
that
needs
to
be
extracted
as
part
of
the
cloud
provider
extraction,
and
they
also
have
some
special
considerations,
which
is
they
have
tests
that
not
always
implicitly
require
a
cloud
provider.
B
B
B
B
They
consider
an
alternative
of
having
feature
colon
storage
provider,
which
would,
I
think,
have
been
a
little
more
consistent
with
some
of
the
other
feature
type
tests.
But
the
problem
is
we're
kind
of
overloading
this
flag
and
a
lot
of
people
already
have
like
skipped
futurecoins.star
and
so
then,
trying
to
like
in
a
cloud
provider
then
trying
to
like
then
enable
this
with
the
way
that
drag
x's
and
tags
work
would
be
really
messy.
B
So
that's
why
they
were
thinking
of
just
calling
it
storage
provider
there's
another
one
called
like
driver
colon,
and
then
you
say
the
name
of
your
your
specific
storage
drivers
that
you
need,
and
the
last
thing
that
so,
if
anybody
has
feedback
on
those
tag,
names
we'd
love
to
hear
it,
and
this
is
just
people
seeing
the
problem
and
they're
just
trying
to
brainstorm
on
some
tags.
Nobody
has
really
strong
opinions
about
them.
B
If
somebody
could
suggest
one,
that's
better
or
has
experience
in
dealing
with
this
stuff
and
test
we'd
love
to
hear
your
thoughts.
The
last
thing
we
want
to
do
is
make
sure
that
we
get
these
tags
right
and
you
know
the
only
way
we're
going
to
feasibly
do.
That
is,
if
we're
running
tests
that
fail.
If
the
tags
are
not
where
they
should
be
right,
otherwise
we're
just
relying
on
humans
to
somehow
keep
these
in
sync
and
that's
probably
a
little
like
a
losing
battle.
B
B
C
I
think
I
think
I
think
that
all
makes
sense
just
to
make
sure
I'm
on
the
same
page.
So
we're
saying
that
we're
gonna
introduce
when
you
say
tags.
Are
you
saying
like
go
com,
go
tags
or
like
the
feature
tags
in
the
test
framework.
C
C
Yeah,
that
makes
sense,
I
mean
that's
like
a
low-cost
way
to
do
it
and
yeah
that
that
seems
like
a
no-brainer
to
me
to
add
the
ginkgo
filters
in
there
so
that
we
can
either
exclude
or
skip
the
specific
driver
tests.
Awesome.
A
I
will
also
say
if
we
keep
the
list
relatively
short
and
we
have
a
list
or
sorry
if
we
keep
those
yeah,
we
keep
the
list
of
such
tags
short
and
we
have
an
actual
list.
What
that
also
allows
us
to
do
is
then
basically
be
building
up
a
way
of
querying
which
tests
need
to
be
need
to
find
homes
in
like
cloud
provider,
repo
test,
suites.
B
Yeah,
that's
right,
I
mean
that's
why
I
kind
of
preface
at
the
beginning
like
this
is
a
step
forward,
but
doesn't
necessarily
do
everything
we
want
to
do.
Hopefully
that
information
is
useful
for
those
subsequent
steps.
D
I
guess
my
only
question
joe
is
like
I'm,
assuming
that
part
of
this
would
be
updating
the
doc
in
the.
I
think
it's
in
the
testing
repo,
where
we
lay
out
all
the
different
ways
that
you
could
tag
your
tests
and
the
ginkgo
labels,
or
whatever
like
we
would
update
that
to
include
what's
what's
changing
here,.
B
B
B
Are
you
know
what
I
don't
think
we
do?
I
think
sig
storage
is
going
to
cover
more
of
the
details
on
this.
I
know
michelle
ow
and
do
you
know
what
michael's
last
name
is
walter
anyways?
I
think
matt
matt
carrie?
Oh
sorry!
Yes,
it's
matthew.
Sorry,
I
think
the
other,
the
other
sorry
about
that
yeah.
So
the
I
think
they
know
more
details
about
specifically
who's
going
to
be
breaking
down
and
doing
what
in
sick
storage.
B
So
I
think
maybe
I
don't
know
how
we
want
to
organize
that
between
the
two
sigs.
I
don't
know
if
we
want
to
have
six
storage
managing
the
the
execution
of
this
or,
if
you'd
like
to
have
this
sig
weeded
and
open
issues.
A
E
No,
I
just
you
know
related
to
my
previous
question.
I
just
want
to
make
sure
like
you
know.
I
know
what
I
need
to
do
so,
if
there's
a
tracking
issue
or
anything
that
I
guess
it's
just
related
to
enabling
the
the
tests
on
on
our
repo,
so
knowing
which
tests
exactly
to
enable
and
stuff
like
that.
B
B
D
Minutes
back,
I
guess
like
not
about
this
topic,
but
just
a
heads
up
walter.
I
talked
with
dennis
moyesif
a
little
more
and
he's
been
looking
into
the
web
hook
stuff
and
he's
been
setting
up
like
a
debug
test,
stand
and
everything
I
think
he
may
have
sent
you
an
email
or
may
be
going
to
send
you
an
email
because
he's
got
a
few
questions
and
I
think
he'd
like
to
take
you
up
on
that
offer
of
having
a
meeting
or
something
awesome.
A
I
haven't
seen
anything,
but
maybe
I
missed
it
tomorrow
would
be
a
great
day
for
me.
So
if
you
could
ping
him
and
sort
of
suggest
tomorrow,
next
week's
not
going
to
be
so
great
because
I'll
be
at
cubecon.
D
It
would
be
a
great
time
but
yeah,
unfortunately
not
so
he
I
mean
he's
in
you
know,
like
I
said
he's
in
europe,
so
I
can
leave
a
message
in
slack
and
he'll.
Get
it
like
in
the
morning
like.
Would
it
be
best
to
like
send
him,
send
you
an
email
or
ping
you
on
slack
or
what's
the
best
way
to
get
in
touch,
I
guess
any
and
all
of
the
above
okay
cool
I'll
leave
them
a
message.
Then
all
right
sounds
good
thanks.
Everyone
later.