►
From YouTube: 2023-01-24 meeting
Description
cncf-opentelemetry@cncf.io's Personal Meeting Room
A
A
C
C
Yeah,
it's
actually
on
a
a
Howie
ski
trip
in
Eastern,
British
Columbia,
so
I'm
gonna
get
there
via
Alberta
those
cool,
pretty
amazing
just
out
in
backcountry
yeah
yeah.
My
favorite
thing
to
do
so.
I've.
A
A
Okay,
there's
nothing
in
the
agenda.
I,
don't
know
if
you
guys
have
anything
that
you
want
to
discuss.
C
A
A
There's
this
PR,
that
is
open,
which
defines
how
we
understand
stability
I
also
wanted
to
advertise
it
outside
these
work
group,
so
that
others
know
as
well
that
we're
deviating
a
bit
from
the
definition
that
otlp,
for
example,
will
adopt
or
or
the
idea
that
throttle
Buffs
should
not
be
exposed
in
the
API
as
well.
A
A
What
I
would
like
to
do
is
to
give
it
a
bit
of
a
cool
down
cool
down
period
for
the
spec
in
particular,
and
now
is
a
very
good
time
to
do
that,
also
because
there
are
two
essential
implementations
in
progress,
one
that
Evan
is
doing
for
the
collector
and
the
other
is
the
operator
is
also
open.
Planetary
operator
is
doing
the
opamp
implementation.
A
That's
that's
great
I
hope
to
see
some
feedback,
maybe
or
no
feedback.
I
guess,
that's
that's
good
as
well.
I
didn't
think
it
works,
so
maybe,
let's,
let's
give
it
a
couple
weeks,
maybe
a
bit
more
and
once
these
implementations
are
complete
or
close
to
being
complete,
we
will
be
more
confident
that
what
we
have
Works,
essentially
right
and
then
I
think
we
should
be
ready
to
to
go
ahead
and
declare
1.0
I
I.
Don't
there
is
no
open
issues,
I,
don't
I'm,
not
aware
of
anything
that
prevents
us
from
declaring
1.0.
A
C
Okay:
okay,
thank
you
for
the
feedback
by
the
way
I
missed
I,
somehow
missed
that
I
I
just
looked
to
see
if
you
had
a
chance
to
review
that
code.
Apparently
that
was
three
weeks
ago.
So
the.
C
On
the
connection,
yes,.
A
Yeah
yeah
yeah,
okay,
yeah
no
worries
so
yeah.
That's
that's
what
I'm
thinking
okay
is
that
is
that
reasonable,
from
your
perspective
as
well,
are
you
actively
working
on
the
extension,
the
op
amp
extension
now.
A
B
Yeah,
so
the
interface
is
waiting
on
another
review.
It
should
be
I
think
in
good
shape,
I
mean
if
we're,
if
we're
good,
with
kind
of
the
approach
of
just
adding
that
data
to
the
the
settings
given
to
the
hosts
once
on
creation.
B
C
B
B
Yeah,
so,
basically,
right
now
we
have
yeah
so
basically
within
the
collector,
the
the
actual.
What
do
you
want
to
call
it?
The
collector
component
inside
of
the
open
Telemetry
collector,
just
since
they
have
the
same
name.
B
I
think
there
are
some
ongoing
discussions
on
having
more
sophisticated
handling
of
that,
so
that
maybe
you
wouldn't
need
to
restart
that
service,
and
you
could
I
mean
you
could
probably
even
go
through
the
actual
pipelines
and
determine
you
know
which
components
have
had
configuration
changes
and
which
pipelines
need
to
be
restarted
as
a
result,
but
right
now
everything's
reset.
So
everything
will
get
reset
the
extension
you
have
to
reconnect
to
the
supervisor.
All
that
so
I
mean
that's.
That's
fine
for
I!
Think
an
initial
implementation,
I
think
long
term.
B
It's
non-ideal
I,
don't
know
if
it's
going
to
cause
any
issues
necessarily
but
I
I
think
that's
kind
of
where
we're
at
right.
Now.
A
Okay,
just
just
just
to
clarify
for
the
initial
implementation,
we're
only
doing
the
the
read-only
part
essentially
of
open
protocol
inside
the
opamp
extension
in
The
Collector,
so
the
extension
reports
the
status-
yes,
the
effective,
effective
configuration,
but
it
doesn't
accept
configuration
remotely
okay
and
in
the
initial
implementation,
we're
going
to
to
use
supervisor
to
do
that
right.
So
there
is
no
restarts
in
process,
essentially
got
it.
What
you,
what
what
you
were
talking
about
is
a
problem.
A
C
A
On
that
is
that
I
don't
think
anybody
is
working
on
the
supervisor
right
now,
so
Sean
is
working,
I
believe
on
the
extension,
so
that
would
be
the
the
beginning,
I
guess
right,
just
the
regarding
mode
and
then
we'll
see.
Who
who
does
the
supervisor
I
think
we
know
roughly
what
we
want
to
do,
but
I
don't
think
anybody
is
committed
to
doing
it
to
actually
writing
the
code.
Yeah.