►
From YouTube: 2021-08-05 meeting
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
B
It
is
viable,
but
that's
even
more
specific
topic.
The
stuff
that
I
presented
in
the
slides
is
just
it's
something.
That's
one
of
the
possible
solutions
that
we
have
for
problem
2
here.
B
B
A
Okay,
okay
and
then
my
my
other
comment
was
going
to
be.
We
have
like
a
few
distros.
Google
does
not
have
one
right
now
for
what
it's
worth
and
I
was
wondering
like.
Should
we
collect
all
of
the
requirements
from
the
vendors
to
make
sure
that
the
distros
are
doing
what
we
need
or
have
we
already.
C
A
C
A
Yeah,
like
I
know,
from
nathaniel's
aws
standpoint,
there's
the
id
generator
and
then
I
guess
otlp
exporter
would
be
like
the
standard
setup
and
then
maybe
like
splunk
and
light
stuff
have
something
different.
So
if
we
know
like
all
the
configuration
points
that
we
need,
it
would
be
really
good.
Yeah
and
propagators
like.
C
A
Has
a
propagator
and
exporter
too
so
yeah.
A
Yeah
and
then
one
more
thing
was
for
number
three.
I
do
think
that
there
should
be
like
a
larger
hotel
discussion
for
this.
Specifically,
I
I'm
sure
at
some
point.
Somebody's
gonna
want
to
have
a
standard
configuration
file
format
that
can
be
used
across
sdks
there's
going
to
be
some
some
specifics
in
there
that
are
going
to
be
really
tricky
like
if,
if
there's
a
regex
field,
and
they
want
to
use
the
same
config
across
multiple
languages
and
the
regexes,
don't
they're
not
consistent.
A
I've
seen
this
come
up
in
like
the
metrics
metric
view.
Discussion
so
like
I'm
sure
that
this
is
happening
at
a
larger
scale
too.
So
I
don't
know
if
it'll
be
possible
to
defer
that
I
don't
know.
B
B
So
we
may
end
up
putting
effort
into
a
solution
that
has
a
a
very
valid
goal.
I
understand
it,
but
it
may
end
up
being
something
completely
outside
of
the
spec,
which
can
definitely
happen.
I'm
not
saying
it
can't
be
implemented
like
that,
but
this
project
sounds
big
and
it
may
take
resources
away
from
completing
the
specification.
A
Maybe
we
can
tackle
the
sdk
configuration
later
like
this
could
all
be
done
with
with
python
code
so
that
we
can
use
whatever
hooks.
And
then
maybe
we
can
come
back
to
like
a
larger
configuration
thing
later.
C
Cool
diego,
if
you
could
go
back
to
the.
A
Yeah,
so
I
I'd
be
like
happy
to
contribute
more
to
this
too.
I
just
sort
of
need
like
action
items
to
get
up
to
speed
and.
C
Yeah,
I
think
I
think,
in
my
opinion,
the
first
thing
we
should
address
is
diego's
pr
for
number
one,
the
the
the
entry
points
for
the
pre
and
post
and
whether
or
not
that
is
something
that
we
should
use
as
a
generic
way.
C
It
has
no
other
goal.
Wait
is
this
the
pr
that
adds
the
pre
and
post
entry
points
number
one
yeah
so
like
it
does
the
separation
and
it
introduces
those
entry
points
and
we
want
to
see
if
that's
the
mechanism,
we're
going
to
use
right.
B
Sure
what
happens
is
that
this
mechanism
of
having
these
entry
points
doesn't
force
us
to
follow
a
specific
path.
I
mean
these
entry
points
are
just
there
and
if,
in
the
future
we
decide
that
we
want
to
do
something
else,
they
will
do
no
harm
we're
just
sitting.
B
A
D
B
D
Does
I
mean
I
mean,
for
example,
for
existing
distros
when
they
upgrade
to?
Let's
say
if
you
release
it,
if
you
have
a
new
release
on
tuesday
1.5
and
existing
distros
upgrade
1.5,
then
they
won't
work,
as
is
if
we
merge
that
pr,
unless
they
have
the
because
now
they
need
to
install
another,
the
the
configuration
package
which
hosts
the
hotel
distro
entry
point
now.
D
B
If
we
keep
the
entry
point
in
the
instrumentation
package,
then
we
are
not
decoding,
so
we
we're
pretty
much
gaining
nothing.
D
C
D
And
yeah
until
the
full
transition
is
complete
and
then
we
get
rid
of
all
the
old
stuff,
because
the
pr
it
in
itself
is
only
solves
problem
number
one
right:
it
doesn't
solve
the
whole
the
entire
problem
set.
So
until
we
have
solution
for
the
entire
problem
set,
I
would
like
not
to
break
existing
stuff.
B
I
mean
we
can
do
that.
I
just
feel
like
it
defeats
the
complete
purpose
of
the
rpr,
because
it's
we
have
two
distros
and
instrumentation
coupled
by
two
ways,
one
of
them
by.
D
B
D
Yes,
we
are
not
decoupling
right
now,
but
like
it's,
it's
very
normal
to
have
like
a
gradual
transition
from
one
system
to
another.
So
if
we
are
not
decoupling
it,
but
we
are
like
laying
the
groundwork-
and
we
are
allowing
you
to
build
on
top
of
this-
this
decoupling
mechanism.
So
then
we
can
release
on
tuesday
or
next
week
and
you
can
still
work
on
it
and
we
can
like
have
five
more
prs
that
built
on
top
of
this
and
come
up
with
the
new
system
for
disk
drives.
So
it's
not.
D
B
We
only
need
to
put
three
distro
as
a
dependencies
of
the
districts
that
that's
the
only
thing
we
need.
We.
B
No,
no,
I
don't
think
those
two
things
are
related
because
we
can
add
the
dependency
of
this
row
to
the
of
the
open
elementaries
package
to
the
distros
and
that
won't
solve
the
problem
of
which
this
three
is
being
selected.
But
that's
fine
because
it
was
never
its
intention.
All.
C
Right
guys,
it
seems
like
we're.
Oh
sorry,
for
interrupting
you
we're
kind
of
out
of
time
now,
please
we
do
need
to
close
on
that,
but
aaron.
If
you
could
review
that
pr
as
well
or
anyone
yeah
sure
who
wants
to
move
this
ahead,
please
remove
you
diego's
pr
and
away
yo.
You
guys
can
maybe
continue.
Yeah
awesome
cool.
All
right.
I
will
see
you
guys
next
week,
then
thanks
for
joining
all
right.
Thank
you.
All
later,
all.