►
From YouTube: Keptn Community Meeting - Sep 28, 2022
Description
Meeting notes: https://docs.google.com/document/d/1y7a6uaN8fwFJ7IRnvtxSfgz-OGFq6u7bKN6F7NDxKPg/edit
Learn more: https://keptn.sh
Get started with tutorials: https://tutorials.keptn.sh
Join us in Slack: https://slack.keptn.sh
Star us on Github: https://github.com/keptn/keptn
Follow us on Twitter: https://twitter.com/keptnProject
Sign up to our newsletter: https://bit.ly/KeptnNews
B
There
is
a
discussion
in
the
chat
from
Brett
asking.
Why
do
we
have
so
many
meetings
so
this
week?
And
actually
it's
a
totally
legit
question
because
we
had
presentation
by
Rajiv
one
hour
ago
next
hour
we
will
have
a
presentation
by
Janam
about
k6
integration,
service
and
yeah
I
highly
recommend
everyone
to
join
this
presentation.
B
C
Yeah
I
think
maybe
I
can
share
my
experiences
at
the
moment
and
then
I'd
like
to
bring
a
couple
maintainers
into
have
a
discussion,
because,
in
my
opinion,
it
needs
to
be.
It
needs
to
be
reworked.
It
needs
quite
a
lot
of
work,
especially
if
it's
going
to
be
in
the
LTS
that
we're
talking
about.
B
So
do
you
want
to
do
it
now,
because
so
some
insight
information,
for
example,
from
Diamond
trees,
so
our
team
in
plugin
for
has
a
fire
drill.
B
So
what
I
suggest
so
next
week
on
Thursday,
we
have
a
developer
meeting.
At
the
same
time,
yeah.
C
B
C
C
A
C
Not
so
much
issues,
but
just
right,
so
I'll
give
you
like
a
high
level
thing
of
what
I'm
talking
about
so
at
the
moment,
the
Primitive
service
has
been
made
to
use
the
the
Prometheus
Community
chart,
whereas
it
doesn't
work
with
the
Prometheus
operator.
C
So
this
is.
This
is
bad
for
adoption,
because
these
days
people
want
to
use
a
chart
called
Cube,
Prometheus
stack,
which
has
out
of
the
box
grafana
default
Prometheus
rules
of
Arts
Etc,
so
it
doesn't
work
with
the
operator.
So
this
is
saying
especially
it's
more
the
configuration
of
it.
C
So
when
you
go
Captain
configure
monitoring,
that's
what
we
need
to
look
at
about
the
the
challenges
that
we'll
have
going
forward,
especially
when
people
start
adopting
get
UPS
first,
where
the
Primitive
service
will
update
the
config
maps
and
things
like
that,
so
it's
just
a
just
calling
out
some
of
their
architecture
and
what
we
can
do
in
the
future.
B
C
Just
yeah
it
it
doesn't
really
break,
but
it
won't
work
because
the
for
example,
the
alert
manager.
So
when
you,
when
you
use
the
so
there's
I,
can
should
I,
show
you
for
five
minutes
or
or
do
I
not
want
to
waste
time
here,
I'm
kind
of
curious.
If
we
can
spare
the
time
yeah,
we.
C
C
Right,
correct
correct!
So
if
you
look
at
essentially
the
captain
CLI
when
you
go
to
configure
monitoring,
we'll
call
the
configure
event
handler
and
that
will
do
a
series
of
things.
So
you
don't
need
to
use
this
so
so
I
don't
actually
use
the
configure.
I
drop
myself
because
it's
quite
a
ID
like
naming
conventions
as
well,
which
makes
sense,
but
not
for
everyone.
Starting
out.
C
Sorry
I've
done
lots
of
analysis
around
compared
both
the
charts
for
Prometheus
community
and
the
operator
and
the
the
operator
won't
contain
the
the
config
Maps
that
the
Prometheus
chapter
as
well.
So
the
configuration
doesn't
work
but
I
have
the
the
SLI
part
working
with
the
operator
which
works
good.
So
I
just
wanted
to
share
my
experience
with
how
I've
done
that
and
implemented
that
for
the
quality
that
it
was
Prometheus
operated,
I.
Think
it's
because
there's
actually
a
couple
of
issues
on
well.
C
There's
one
issue
of
a
few
people
raising
it
before,
but
I
think
they're
a
little
bit
scared
to
keep
talking
about
it.
They
might
not
have
understand
it
and
Doug
is
deep
resided
on
it,
but
I
I
think
it's
good.
Like
I
have
a
solid
understanding
of
how
it
works
now,
so
it
will
be
good
to
present
that
to
the
developmenting
I
think.
Oh,
that's
good!.
C
Not
yet
I
I
talked
to
Andy
about
other
services,
but
not
Prometheus
yet,
but
all.
A
C
A
I,
don't
know
any
details,
but
a
couple
weeks
ago
we
were
talking
about
something
and
he'd
run
it.
He
just
made
a
passing
comment
that
he
was
seeing
that
the
Prometheus
integration
it
wasn't
as
high
quality
as
it
should
be,
or
something
to
that
effect-
and
this
may
be
the
this-
may
be
his
issue
or
he
may
have
others.
Yeah
I
know.
C
I
know
the
work
involved
to
to
make
this
better,
but
yeah
I,
I'd,
like
to
talk
to
like
Andy
and
Thomas,
would
be
good
if
he
can
come
as
well,
because
it's
going
to
relate
to
to
get
up
stuff
in
the
future
as
well.
Okay,
Prometheus
service,
captain
I'll
just
show
you
an
issue
on
it.
C
Raised
about
a
year
ago,
which
I
found
this
one,
so
it's
a
type
feature
so
support
Prometheus
deployed
via
premises
operator.
C
So
that's
exactly
what
what
I
came
into
and
I
reached
out
to
my
friends
as
well
and
said
in
terms
of
Prometheus
grafana
Etc?
How
do
you
do
it
and
they
do
it
the
same
way
as
me,
because
it's
in
my
opinion,
that's
why
it's
sort
of
it's
good
but
I,
think
we
should,
if
we're
saying
that
for
LTS
that
we're
going
to
support
Prometheus,
we
should
definitely
support
the
operator
as
well.
C
It's
a
big
task
but
I'm
happy
to
change
the
work,
but
it
would
need
a
yeah
I
actually
said.
I
said
last
night
that
I
was
analysis,
but
a
lot
of
my
analysis
has
done.
It's
been
a
couple
days
doing
it
so
I
can
present
it
at
the
meeting.
B
Yeah,
definitely
it's
required
for
longer
term
yeah
and
yeah.
You
made
a
note
about
decision.
C
Yeah
so
I'll
present
back
what
I
said
today,
like
technical
analysis
like
more
evidence
and
Etc.
C
C
C
Yeah,
so
that's
an
update
for
me
anyway.
Yep
about
what
I
mean.
B
So
it's
still
a
feature
request,
of
course,
but
yeah
I
think
that
it's
quite
important
to
edit
so
I
will
add
it
to
my
scope
and
yeah.
So
one
of
the
topics
to
keep
in
mind
that
the
Christian
he's
moving
on
from
the
Primitive
service.
So
he
still
helps
us.
We
support
the
maintenance,
but
yeah.
We
will
need
to
identify
identify
another
maintainer,
and
this
is
why
it's
important
topic,
because
it
could
be
firstly,
quite
useful,
involving
task
for
knowledge
transfers.
So
I
will
put
it
on
the
list.
C
Yeah,
that's
right,
I'm
happy
to
do
the
work
as
well.
B
Yeah,
thank
you
so
yeah.
Maybe
since
we
are
talking
about
integration
Services
anyway,
I
could
just
show
you
a
very
very
draft
proposal
about
a
couple
of
Lighthouse
as
a
sub
project.
B
So
it's
something
that
I'm
still
yet
to
discuss
widely
in
the
community.
I'm
just
evaluating
feasibility
but
yeah.
If
you're
interested
I
can
show
it
to
you
right
now.
Yeah.
C
B
It
would
be
quite
interesting,
too
I
wanted
to
discuss
zombies
tomorrow.
That's
our
call,
but
yeah
I
can
show
it
now.
B
So
have
you
already
heard
about
the
project
called
openness
alone?
Yes,
so,
basically
open
a
slow
is
a
standard
suggested
by
number
nine
or
two
before
SLO
evaluations.
B
So
that
is
a
standard
and
a
few
tools,
including
one
so
that
allow
to
show
some
dashboards
Etc
based
on
the
standard
and
the
specification
itself
for
variations
Etc.
B
The
problem
with
the
standards
is
that,
even
if
it
exists,
it's
not
widely
adopted
at
the
moment
uh-huh,
and
actually
we
had
a
number
of
discussions
about
whether
we
should
adopt
it
in
Captain,
Etc
and
yeah.
A
few
weeks
ago,
I
started
looking
whether
it
would
be
technically
feasible
for
us
and
what
would
be
the
cost
for
that
actually
just
to
show
some
context.
B
For
me,
the
biggest
problem
was,
but
in
Captain
we
basically
have
our
own
engine
for
affiliating
casillos
our
standard
for
sending
events,
and
currently
it
looks
like
that.
So
basically,
we
have
Captain
Lighthouse
service.
We
have
a
slide
provider
services,
including
parameters.
B
We
just
got
a
data
dog
and
small
logic
and
Dyna
trees
and
basically
their
adapters
that
provide
slis
that
can
be
relatively
heated
by
Captain's
Lighthouse,
which
has
its
own
Logic
for
its
laws.
So
that
is
the
definition
which
be
follow.
B
Look
at
this
one,
so
it's
basically
like
that
and
it's
Universal.
This
definition
to
some
extent,
is
closer
to
what
the
openness
law
has
to
offer
so
forth
and
slow.
They
have
Generations
like
that
with
some
targets,
with
some
comparisons
with
Target
values
and
actually
one
important
thing:
they
have
budgeting
support
and
Captain.
We
don't
have
a
slow,
Budget,
supplemented
on
the
the
captain
level.
B
So
my
idea
was
so
that
actually,
this
part
is
quite
generic.
So
what
if
we
standardize
it
by
actually
putting
open
a
slow
support
in
the
service
itself?
Explosion
has
low
compatible
web
interface
and
probably
adopting
more
standards
like,
for
example,
open
Telemetry
for
traceability,
also
providing
some
rest
apis
for
querying
evaluations
and
sending
components
load
detail
over
a
cloud
advanced.
B
So
in
this
case
we
could
keep
our
slide
Provider
Services
our
yaml
format,
and
for
slos
we
could
probably
support
two
formats.
One
is
Captain,
another
one
is
open,
slow,
so
I
spent
some
time
discussing
it
with
developers
and
it
seems
feasible
on
the
captain
side,
so
it's
possible
to
detach
the
services
like
that.
Obviously,
you
need
to
disconnect
them
from
control
plane,
maybe
create
new
charts
wire
them
together,
but
in
principle
it's
possible
and
actually
it's
also
possible
from
the
open
SLO
standpoint.
B
So
last
week
we
had
a
first
conversation
with
a
few
people
from
open,
SLO
student
committee,
and
my
conclusion
is
that
we
actually
can
do
that
so
the
biggest
differentiation
for
us
from
opening
solution
standpoint.
It
doesn't
support
comparisons
against
the
Baseline
which
could
be
added
to
the
standard
and
from
Captain
site.
We
have
a
few
limitations
like
we
support
only
one
SLI
source
for
SLO
in
open
and
slow.
It
is
abstract.
So
for
me
it's
limitation
and
another
one
is
of
course
a
slow
budget.
B
So
basically
what
we
discussed.
If
the
openness
low
standard
could
be
slightly
adapted,
we
can
make
Captain
compatible
with
it
and
we
could
formally
adopt
it
and
provide
open
source
implementation
for
open
SLO,
which
is
missing
at
the
moment.
So
for
that
yeah
we
wouldn't
have
some
specification
for
a
slow
event.
So
when
we
have
Captain
Advanced
specification,
the
specification
could
be
somehow
Upstream
to
open
the
slow
and
adapt
it
to
the
standard.
B
Also,
we
could
add
some
capability
flux
to
remove
budgets,
so
you
have
kind
of
could
have
actions
for
sending
events
like
in
Captain
and
at
some
comparison,
but
all
of
that
seems
technically
feasible
and
if
you
could
do
that,
we
could
formally
adopt
open
a
slow
in
Captain
as
one
edit
failure
and
secondly,
we
could
detach
Captain
like
house
as
a
kind
of
Standalone
opponent,
maybe
some
project
like
life
cycle
controller
that
can
be
actually
used,
not
just
by
Captain
but
by
any
other
system.
So
we
have
such
submission.
Cloud
events.
B
So
yeah,
so
this
is
this
idea
is
just
cooking
I
mean
there
is
no
time
commitment,
resource
commitment,
Etc
I,
wanted
to
work
with
a
few
other
projects
to
see
what
it
would
be
fusible.
B
There
is
another
project
on
my
readers,
which
is
called
era,
so
I'm,
not
sure
about
the
U
breath
of
Suresh
I
heard
about
it.
No,
so
it's
actually
a
project
that
integrates
with
parameters
only
and
allows
exposing
slos,
mostly
some
dashboarding
Etc.
So
it's
created
by
polar
signals.
B
But
yeah
it's
probably
another
project
to
talk
to
because
it
feels
that
there
might
be
some
overlap
or
opportunities
for
Integrations,
because
if
you
work
on
this
project
right
now,
we
are
definitely
not
creating
UI
or
other
components.
But
if
you
provide
property
addressed
API,
maybe
it
could
be
connected
to
tools
like
period
as
well.
A
So
there's
a
there's
an
outward
pointing
out
on
open
SLO
right.
So
IV
is
the
idea
that
we
are
going
to
ex
export
convert
the
SLO
that
we
have
and
Export
it
as
open,
SLR,
yeah.
B
So
they
think
that
openness
low,
has
no
expert
format
at
the
moment,
so
what
it
has
actually
it's
just
this
book
and
I
didn't
crack
away.
Oh,
it
has
a
definition
for
it.
B
But
this
definition
format
could
be
also
to
somehow
extracted.
So
if
you
had
a
standard
for
SLO
events
and
data
like
Json,
we
could
easily
export
it
outside.
So
for
me,
it
would
be
rather
like
that,
so
it
would
be
Cloud
event
sending
data
in
a
standard
test
of
openness,
level
format
and
pretty
much
the
same
for
open
Telemetry.
So
it
would
be
also
standardized
in
openness
alone.
A
B
B
It
sent
us
Cloud
event,
so
you
can
subscribe
any
tool
within
the
cloud
events
like
a
system
to
handle
this
event.
So
just
to
show
you
examples.
So
if
you
take
Cloud
events,
so
the
list
of
adopters
is
actually
quite
impressive,
including
Captain
by
the
way.
So
it
means
that
if
you
have
a
standard
event
that
we
should
send
through
Cloud
events,
you
can
subscribe
any
of
these
tools
to
do
something.
So,
for
example,
Captain
can
react
to
this
events
and
three
from
Auto
remediation.
The
same
could
be
done
with
directive
with
key
native
events.
A
It's
just
like
giving
a
plug
that
anybody
can
exactly.
C
A
Makes
sense,
so
is
the
idea
that-
and
this
is
I
know
this-
is
this-
might
be
in
the
future,
and
we
might
not
do
it
immediately,
but
is
the
idea
that
we
might
light
our
service
might
become
the
implementation
for
open
SLO
like
one
of
the
implementation
for
open,
SLO
or
yeah?
Okay,
cool
yeah.
B
A
A
B
Yeah
so
just
wanted
to
say
that
yeah
it
could
become
a
reference
implementation
for
openness
alone,
I
think,
but
we
can
contribute
things
that
we
need
in
openness
alone,
for
example.
The
choke
point
for
me
right
now
is
slow
budgets,
because
if
you
wanted
to
implement
the
slow
budgets
and
Captain,
we
would
have
helped
to
implement
three
algorithms,
which
are
currently
supported
by
openness
law.
B
So
the
occurrences
stem
slices
ratio,
10
slices
and
we
just
have
no
infrastructure,
no
tooling-
to
implement
that
in
Captain
right
now.
So
if
you
wanted
to
fully
implement
the
standard
right
away,
it
would
be
quite
a
massive
endeavor.
So
the
idea
is
that
we
contribute
some
bits
of
the
specification.
Some
capability
plugs
right
into
the
spec.
B
B
Yeah
so
bonus
points
for
us
so
that
basically
all
the
slide
providers
that
we
use
in
captain
in
Theory
without
any
modification
the
could
remain
in
this
system,
the
keyboarding
Theory
in
practice,
yeah.
It
might
require
some
changes.
But
if
you
do
that,
then
basically
we
can
have
these
companies
basically
helping
quite
the
icon
system,
not
just
captain.
B
So
yeah
again
disclaimer
it's
just
initial
discussion,
so
we
need
to
talk
to
stakeholders.
We
had
a
conversation
with
snowball
line
and
we
open
the
slow
maintenance
risk
here.
But
it's
just
a
discussion
without
any
commitment
at
the
moment
and
yeah
we'll
be
definitely
looking
for
some
more
feedback
Etc
before
we
go
public,
because
I
think
that
we
need
more
contributors
from
outside
Captain
America
system
to
pull
this
project
off.
B
I
think
it's
a
good
opportunity
to
grow
the
community
and
actually
to
grow
adoption
of
Captain.
A
B
This
is
why
the
question
Brett
brought
up
about
parameters
and
Integrations
is
for
me
it's
more
than
relevant,
so
we
still
have
Captain
and
CSM,
maybe
in
one
month
or
so,
and
basically
the
same
for
a
data
dock
integration
service
by
user.
If
you
you
could
promote
it
to
Country
to
LCS,
it
could
build
a
good
addition
to
the
ecosystem,
because
many
people
use
datadog
May.
B
Well,
parameters
is
our
first
class
citizen
implementation,
at
least
it
should
be,
and
if
we
make
it
a
kind
of
Public
Service,
then
I
think
that
there
would
be
some
extra
value
advocacy.
B
Yes
or
speak
and
event
advice.
Yes,
if
you
have
standard
slow
definition,
you
can
basically
change
observability
providers
quite
freely
that.
C
That's
a
good
sell,
a
good
salary
people
to
adopt
it,
because
if
you
think
about
all
these
people
that
get
tools
like
Donatos
New
Relic,
they
they
buy
it,
they
spend.
You
know
200
000
a
year
and
it
takes
them
a
year
to
implement
it
because
they
realize
that
they
don't
have
tracing
and
they
don't
have
structured
logging.
B
So
yeah
this
basically
what
what's
cooking
at
the
moment,
but
yeah
I
think
it
would
be
another
to
discuss
at
the
captain
coming
today.
A
B
Yeah
so
for
coming
to
the
yeah
I
hope
that
you
finally
published
a
program
this
week,
so
the
problem
that
the
cncf
decided
not
to
publish
our
initial
program
because
we
related
diversity
requirements
over
the
Linux
Foundation.
So
we
need
to
add
basically
speakers
with
diverse
background
to
the
agenda.
It
took
some
time
to
reach
out,
but
we
have
a
solution
so
hopefully,
today
it
will
be
published
and
so
I'm
not
sure
whether
you
have
seen
the
agenda.
B
Okay,
so
here
we
have
the
initial
agenda,
so
we'll
have
a
short
State
of
the
Union
in
the
morning,
while
it's
on
the
morning
because
than
many
people
had
to
be
tops
event,
if
I
recall
correctly,.
B
Thomas
suggested
that
we
do
it
on
the
morning,
then
we
will
have
workshop
for
whatever
for
whomever
interested
in
Captain.
So
and
you
will
drive
it.
Then
there
is
a
lunch
break
and
then
we
basically
start
sessions.
So
we
will
have
session
with
this
bread
and
Etc
about
Captain
and
enter
ability.
B
So
this
was
the
original
submitted
schedule.
I
will
add
two
more
talks
there,
but
more
or
less
it's
what
we
have
on
on
the
phone.
C
B
B
So
if
somebody
is
not
available,
we
will
just
adjust
the
speaker
to
line
up
accordingly,
but
the
idea
is
to
have
basically
a
many
community
members.
There.
A
B
And
so
I
will
submit
it
and
yeah
once
I
have
a
slot.
I
will
send
the
information
to
everyone.
C
Yeah,
if
we
should
get
the
the
captain
t-shirts
for
swag
this
year,.
B
We
should
so
for
watch
work
David
here
she
is
driving
Logistics,
so
there
should
be
t-shirts
for
the
coming
today.
Also
there
would
be
stickers,
Etc
I,
don't
think
there
will
be
anything
specific,
because
yeah
budgeting
this
year
is
more
complicated
than
it
should
be.
Let's
say
so,
but
yeah
I
hope
that
we
will
have
basic
swag
at
least.
A
A
B
Okay,
so,
basically,
last
week
we
had
a
quick
conversation
and
the
developer
meeting,
but
the
LF
second
controller
is
basically
an
experimental
project.
So
Giovanni
and
the
team
are
looking
into
that
and.
B
A
I
I
went
through
the
issues,
I
went
through
the
readme
and
all
of
that
my
question
is:
do
you
have
any
idea
around
the
current
state
of
the
system
because
I
see
this
so
many
things
happening
right
now
and
I'm
not
sure
what
is
the
current
state
of
the
system?
I
was
going
to
ask
the
same
question
in
the
slack,
but
since
yeah.
B
Yeah,
so
the
current
state
of
the
system,
with
that
first
proof
of
concept,
use
work
and
progress.
So
there
is
a
kind
of
hackathon
going
on
and
yeah.
Hopefully,
within
the
next
few
weeks
we
will
have
something
to
present
so
right
now,
they're,
just
looking
they're
implementing
things
here
and
there
there
is
a
very
recruited
implementation
at
the
moment,
but
not
something
ready
to
show
so
the
target
so
Thomas
already
asked
for
a
slot
at
the
Kaplan
Community
D
to
do
the
full
demo.
B
So,
basically,
that's
all
at
least
from
my
side
and
again,
if
you
have
missed
the
previous
developer
thinking,
we
agreed
that
the
next
Captain
release
0.20
would
be
actually
Captain
one
to
zero
LCS.
B
So
for
that
we
had
0.19
release
two
weeks
ago
and
for
the
for
0.20
they
don't
plan
on
any
incompatible
changes
at
the
moment,
so
we
could
safely
assume
it
would
be
LCS
unless
something
changes
drastically
over
the
common
Greeks.
So
for
Captain
quarter
the
party
solved
for
integration
Services.
We
still
need
to
work
on
that.
C
Yeah
because,
if
you're
taking
the
distributor
out
for
the
zero
downtime,
that's
quite
a
massive
change,
yeah,
because
I
think,
for
example,
the
the
job
executor
service
might
not
work
at
the
moment
in
0.19.
B
Cool
I
was
going
to
change
that
yeah
I
know
that
some
beats
do
not
work.
For
example,
dynatories
integration,
service
parameters,
I
believe
it
was
updated
for
0.19
already.
A
C
Have
you
considered
the
concept
of
like
a
sub
main
terminal
that
looks
after
a
specific
specific
domain
or
service.
B
Well,
in
practice,
we
have
it:
I
can
practice
primitive
Services,
maintain
water
maintained
by
Christian
data
services.
Vice
versa,
for
example,
job
executor
service
was
maintained
by
a
Christian
at
the
team
too.
So
if
anyone
wants
to
step
up
as
a
sub-maintainer,
basically
we
have
for
this
framework
and
practice.
It's
not
critified
and
I.
Don't
see
much
reason
to
clarify
it
at
the
moment,
but
yeah
well,
I
approached
Jenkins
Way,
where
basically,
maintenance
of
partitional
particular
service
have
almost
full
Freedom
when
working
on
it
yeah.
B
B
Or
same
for
other
services
sure
but
defaults.
Yes,
we
clearly
have
an
issue
with
some
services
that
are
actively
used
and
some
services
that
are
not
maintained
at
all
yeah.
Sadly,
for
example,
article
rollouts
service
is
not
maintained
or
there's
a
bunch
of
other
services,
especially
in
sandbox,
which
are
not
actively
maintained
and
for
them,
of
course,
we
cannot
include
them
into
the
LCS
yeah
and
but
even
for
Country
yeah.
There
is
this
Argo
service.
B
Just
doesn't
make
much
sense,
they
can
that
we
have
web
hook
service
at
the
moment.
B
Service
which
we
just
detached
from
the
core,
and
we
still
need
somebody
to
step
up
and
take
maintenance
of
them
if
you
want
to
have
them
sustainable
in
the
longer
term.
So
not
all
services
would
go
into
LTS
at
the
moment,
but
obviously
extent
over
time.
B
It's
just
the
drastically
painful
to
start
from
a
very
small
set.
C
A
C
B
So
I'm,
just
just
taking
it
easy,
so
your
contributions
are
welcome
everywhere,
at
the
same
time
committing
to
the
maintenance
yeah.
It's
a
major
commitment.
So
at
the
moment,
if
you
want
to
contribute
to
a
service
you're
more
than
welcome
maintenance,
yeah.
B
B
B
And
I
didn't
sleep
at
all
and
I
stepped
down
from
basically
everything
over
time,
but
yeah,
so
I'm
not
going
to
try
it
again
here.
B
So,
listen
in,
in
any
case,
the
number
of
services
in
the
captain
in
the
big
there
was
some
unified
students,
so
we
should
referred
but
yeah
for
now.
My
suggestion
is
to
just
focus
on
the
companies
that
I'm
a
mission
critical
to
the
system.
B
B
Okay,
so
anything
else
for
today,
no
I'm
good,
so
Mike.
What
if
we
make
a,
are
you
still
available
in
one
hour
after
genomes,
presentation.
B
Okay,
so
maybe
we
just
do
some
Cup
on
the
community.
They
talk
a
bit
later
and
so
foreign.