►
From YouTube: Aug 18, 2022 - Ortelius Keptn Events Sequence Diagram WG
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
Okay,
welcome
everybody
to
artelia's
architecture,
meeting
for
august
18th,
just
kind
of
picking
up
where
we
left
off
with
the
state
diagram
and
let
me
share
my
screen.
A
Okay,
so
I
did
figure
out
how
to
get
the
numbers
in
place.
You
actually
do
a
little
markdown
magic
and
you
just
add
in
the
initialization
to
show
the
sequence
numbers.
So
what
we
need
to
do
is
kind
of
break
down.
A
Who
wants
to
focus
on
which
item
numbers
to
kind
of
lay
out
the
details?
You
know
what
happens
during
that
process,
so
that'll
be.
The
first
thing
is
what
what's
actually
occurring
during
that
step
and
then
we'll
evolve,
that
into
what
the
cloud
event
is
going
to
look
like
and
we'll
basically
kind
of.
I
don't
know
if
something
like
swagger
would
be
worthwhile
to
lay
out
the
payloads
or,
if
we
just
do
it
in
just
json
in
the
mermaid
dock,
just
as
inline
json
code
either
way.
A
So
what
I
think
we
should
do
is
if
anybody
has
any
specific
areas
that
they're
more
familiar
with.
Maybe
you
can
pair
up
with
another
person
and
kind
of
knock
out
what's
happening
during
that
that
step,
so
kind
of
the
areas
would
be
around
git,
what's
happening
between
git
and
captain,
and
then
the
next
step
is
what's
happening
around
the
build
and
then
the
component
updates
pieces.
A
And
then,
finally,
this
is
going
to
be
the
argo
cd
piece
and
then
back
to
kept
in
for
quality
gates.
So
it's
like
four
to
five
areas
and
if
you
don't
know
like,
if
you're
not
familiar
with
something,
that's
okay,
if
you
just
want
to
kind
of
take
the
lead
on
it
and
pull
in
the
resources
that
you
need
to
get
that
area
kind
of
laid
out.
Does
that
make
sense.
A
B
A
All
right
cool
so
who
wants
to
take
a
look
at
stuff
around
github
and
captain.
A
B
C
C
A
And,
like
I
said
this,
is
you
don't
have
to
be
an
expert?
It's
basically
you're
gonna
go
go
off
and
do
some
research
and
pull
in
the
the
folks.
You
know
reach
out
to
the
community
and
and
get
some
people
to
help
you.
So
the
next
part
is
is
docker.
B
A
And
then
this
is
artelias.
C
A
A
And
I
can,
since
I'm
the
most
familiar
with
this
part,
I
will
be
that
and
who
would
like
to
come
on
and
work
with
me
on
that.
A
Else
on
artillery's
captain
piece
all
right.
A
A
Yeah,
so
that's
that
is
getting
into
our
in
that
step.
We
actually
use
our
python
program
component
update
to
do
a
bunch
of
that
stuff
so
that
that
piece
is
actually
pretty
far
along.
I
think
we'll
have
to
tweak
it
for
dealing
with
the
events
and
then
the
next
section
is
argo.
Cd.
A
Integration,
that's
an
integration
too,
and
I
believe
this
is
part
of
it.
I
know
is
going
to
be
a
kept.
I'm
sorry,
an
argo.
A
Notification
yep
exactly
okay,
so.
A
Okay,
we'll
we'll
we
should
just
assign
brad
to
all
these
and
who
does
anybody
remember
the
new
person
that
joined
this
team?
I
don't
know
if
they're
on
today.
B
A
Yeah,
so
if
anybody
else-
and
this
isn't
like
I
said
this
does
not
mean
that
you're
going
to
be
responsible
for
doing
the
whole
thing,
you
know
you'll
be
able
to
do
some
research
kind
of
present
back
what
you
found
to
the
group
and
then
you
know
other
folks
can
chime
in
as
well.
So
it
is
not
like
we're
hanging
out
to
dry
on
these.
B
A
You're
interested
in
learning
something
what
else
do
we
have
on
here?
I
closed
my
list.
Arvin
you've
been
quiet,
come.
A
So
which
part
of
the
process
would
you
be
interested
in
arvin
something
early
on
in
the
process,
so
the
ci
cd,
ci
part
or
more
on
the
cd
part,
the
delivery
part
you're
getting
added
to
this
list
somewhere,
so
you're
not
getting
out
of
it.
B
This
is
kind
of
not
really
what
I
do.
I'm
happy
to
be
a
reviewer
bounce
ideas
off
me
that
kind
of
thing,
but
all
right,
we'll
give
you
way
way
behind
me.
A
Yeah
and
and
speaking
of
that,
if
we're
missing
stuff,
I
will
get
this
checked
in
it
will
go
into
the
docs
repo.
So
right
now
ice.
A
I
don't
know
why
it's
not
showing
it
maybe
online.
No,
oh,
I
didn't
open
the
folder,
that's
why,
but
it
is
in
the
docs
location,
so
yeah
definitely
a
reviewer
and
somebody
to
just
ask
the
the
questions
everybody
wants
to
avoid.
You
know.
Developers
are
famous
for
making
things
easy
on
themselves
and
ignoring
the
problems.
A
A
And
I
think
what
we
could
do
is
just
to
make
it
make
it
easy
for
reviews
and
stuff
like
and
prs
just
do
a
separate
document
on
your
section
so
and
put
my
name
on
this.
A
Just
as
a
placeholder
for
now
so
just
make
a
new
document
with
for
your
section,
just
like
number
one
get
github
kept
in
a
new
markdown
document
and
then
you
can
get
in
and
format
it.
However,
you
want,
and
what
we'll
do
is
we'll
do
the
prs
against
the
the
docs
repo
and
we
can
do
the
discussions
off
of
that
ask
questions
and
things
like
that,
and
then
we
can
merge
those
files
in
and
then
we're
all
happy
we'll
consolidate
into
one
bigger
file.
A
Probably
or
we
can
just
do
links.
You
know
we
can
just
do
a
link
from
here
to
the
the
sub,
the
supporting
document
at
that
level,
so
that
is
kind
of
where
we're
at
for
this.
Does
anybody
have
any
questions
based
on
our
last
conversation
when
we
walk
through
this?
If
there's
anything
that
we
missed?
If
we
need
to
add
or
if
we're
looking
good
so
far,.
B
Do
we
have
like
some
discussion
with
brad
about
this
architecture.
A
No,
I
haven't
had
a
chance
to
get
in
touch
with
brad,
I
think
he's
back
in
australia.
I
was
waiting
to
because
I
know
you
left.
I
think
this
past
weekend
to
go
from
columbia
to
back
home.
Science
is
giving
him
a
little
bit
of
time,
but
we
should
start
pinging
him
on
discord
and
get
let
them
know
where
all
this
stuff
is.
I
did
publish
the
last
two
architecture
meetings.
A
B
A
A
B
Also
think,
yeah
speaking,
they
should
not
be
captain,
but
captain
executive
service
in
case
of
captain,
because
captain
executive
service
would
internally
call
captain.
A
Kind
of
rework
in
our
our
wording
because-
and
this
is
kind
of
like
how
I'm
not
100
sure
how
things
are
configured
because
I
know
you
have
the
shipyard
file
and
kept
in
and
stuff
like
that.
But
I
don't
know
how
you
tell
it
to
listen,
for
you
know
certain
events
and
things
like
that,
if
that's
in
the
shipyard
file
or
what
we
need
to
do
on
that
front,
so
I
think
there's
there's
there's
multi,
and
this
is
where
this
captain
piece
may
need
to
get
split
out.
A
So
we
have
kind
of
like
the
kept
in
control
plane,
that's
handling
all
the
event
routing,
and
then
we
may
have,
like
you
said.
The
captain
service,
which
will
split
out
to
be
the
you
know,
throw
the
events
for
to
or
from
ortelius
at
that
level,
and
that's
the
same
thing
on
the
artelia
side.
We
may
need
to
do
they
split
this
out
into
the
listening
side,
where
it's
listening
for
events
and
another
side.
This
can
be
publishing
events.
B
A
Right
but
one
of
the
things
with
our
rest
apis
is
they
don't
talk
cloud
events
and
that's
the
thing
that
we'd
want
to
we
would
need
to
implement.
Is
it
would
probably
be
just
a
wrapper
to
one
of
our
existing
rest
apis
to
consume
the
cloud
event,
parse
the
json
of
the
event
and
then
go
in
and
re-route
that
information
to
another
restful
api
inside
of
artillios.
A
And
that's
that's
one
thing
when
you're,
when
you're
working
through
this
just
keep
it
in
mind
cloud
events
that
we're
going
to
need
to
work
through
now,
one
of
the
things
like
that
that
this
is
going
to
flush
out
when
we
start
working
on
this.
A
So
the
folks
that
are
on
this
first
part
where
you
get
the
commit-
and
you
start
the
captain
recognizes
that
there's
a
a
new
event
that
git
commit
the
repo
as
much
information
that
we
can
grab
from
from
the
github
side
is,
will
need
to
be
passed
along
to
all
these
other
events
down
the
way.
So,
in
this
case
like
in
step
eight,
we
need
to
know
information
from
step
one
and
step
seven,
so
we
actually.
A
This
is
where
the
events
are.
Gonna
have
to
be
cumulative
that
we're
gonna
go
ahead
and
grab
everything
from
from
that
level.
All
the
way
through
now
with
that's
being
said,
if,
if
one
event
is
not
passing
on
the
payload
to
another
event,
and
we
keep
on
like
pushing
the
payload
forward,
then
we
may
have
to
in
our
design,
come
up
with
a
a
global
event.
Listener
that
listens
on
all
events
and
that
will
kind
of
keep
a
database
of
all
the
events.
A
So
if
you
want
to
go
ahead
and
follow
the
chain
backwards.
So
if
I'm
here
on
step
eight-
and
I
need
to
get
information
from
step,
one
that
I
can
work
my
way
backwards
through
the
database
to
get
that
information.
C
A
B
A
We
may
need
to
do
that.
I
don't
know
yet.
If
we'll
have
to
find
out,
that'll
be
some
of
what
we
need
to
dig
through.
Would
that.
A
C
A
It'll
in
it'll
in
the
size,
the
json
and
we'll
store
regular
json,
and
it
it's
pretty
quick
and
it
deals
with
these
relationships.
So
the
the
graph
databases
are
really
good
for
managing
large
numbers
of
relationships,
okay,
so
being
able
to
traverse
multiple
relationships
in
a
single
go.
It
does
that
really
well
through
the
graph
graph
database.
Queries.
A
Yep
yeah,
it's
a
new
world
for
me
as
well.
I've
played
with
it
a
little
bit.
She
played
with
it
as
well
right.
B
A
A
You
run
in
a
docker
image,
especially
for
development.
When
you
go
to
production,
you
can
stand
it
up
slightly
different,
so
you
can
have
different
nodes
in
the
cluster
to
be
able
to
do
more
distributed.
You
know.
C
A
That's
what
I'm
not
sure
about
on
the
production
side
on
the
on
the
like,
when
you
run
it
run
it
locally
on
docker,
you
give
it
a
volume
amount.
A
I'm
not
sure,
that's
the
part,
I'm
not
sure
about
on
a
production
raw
of
what
you
need
for
the
backing.
If
this
can
be
like
a
elastic
block,
storage
or
if
it's
gonna
be
like
google
is
called
a
firestore.
I
think.
A
A
That
that
is
already
kind
of
like
pre-defined
is
that
the
entry
is.
B
A
Yeah,
so
there's
a
another
way
around
it
for
like
short-term
ways
in
google
to
get
around
that
that
file
store
issue.
You
can
stand
up
your
own
nfs
server
and
that
could
be
blocked
by
persistent
storage
like
a
google
cloud,
storage
can
be
used
for
that
and
then
there's
another.
C
A
And
then
there's
another
one,
it
is,
and
I've
used
this
for
another
project.
It
is
gcs
fuse
which
will
allow
you
to
mount
an
s.
A
bucket
into
a
container
and
it'll
be
read,
write
at
that
level.
It's
actually
a
special
like
volume.
Mount
driver,
yeah
gcs,
fuse
it's
an
interesting.
A
And
gcs
fuse
has
a
slight
lag
on
the
right
side,
but
if
you're
doing
a
bunch
of
read
stuff
off
of
a
bucket
yeah,
it
works
pretty
good.
A
So
that's
where
we're
at!
I
will
get
this
committed
in
and
we'll
start
working
on
it
and
we'll
we'll
touch
base
early
next
week
on
discord
to
just
to
get
a
let's
say
tuesday.
Next
week,
we'll
just
kind
of
do
a
a
quick
discord
status
check
to
see
where
everybody's
at.
B
C
So
sorry,
just
to
sir,
because
it's
been
a
long
day
and
you
guys
are
just
starting
probably
had
coffee.
C
Already
so
these
documents
we're
making
that
I'm
going
to
be
working
with?
Is
it
like
a?
Is
that,
like
a
working
architectural
kind
of
document
around
the
portion
that
we've
got
under
our
responsibility?
Okay,.
A
Let
me
just
write
this
down
forever,
so
some
of
the
things
that
we'll
want
is,
you
know
basically
the
how
the
how
y'all
cool
and
then
the
next
one
is
gonna,
be
the
what
you
know.
So
how
does
the
event
work?
B
C
A
Yeah,
I've
had
that
and
then
just
like
a
overall.
C
A
Yeah,
because,
if
you
need
to,
if
you
need
to
inline,
json
and
stuff
like
that,.
B
A
Ahead
and
inline
that
if
you
need
to
do
some
more
more
mermaid
stuff,
maybe
like
you
do
like
on
the
github
action
part
it
may
you
may
not
have
many
more
events
but
like
on
the
docker
one.
Here
we
have
like
kind
of
like
six
events,
so
you
may
want
to
take
this
this
part
of
the
diagram
and
put
it
into
your
document,
so
you
can
kind
of
like.
C
A
A
So
that's
kind
of
what
we're
looking
for.
A
Is
what
I'm
thinking
right
now?
Unless
does
anybody
have
any
other
ideas?
What
else
we
would
need
in
in
the
event,
like
kind
of
description.
A
A
And
that
one
being,
for
example,
in
this
first
event,
what
what
happens
if
this
is
in
a
private
repo.
A
You
know
so
we
have
something
happening
in
a
private
repo
and
then
maybe
something
else
on
the
argo
side
is
happening
in
the
public
repo.
You
know
what
what
does
that
mean
when
we
have
to
look
in
and
inspect
data,
and
things
like
that.
A
A
And
the
whole
git
ops
process
is
is
pretty
what
should
I
say,
confusing
or
vague,
especially
when
you
get
into
a
multi
a
multi
poly
repo
for
the
services?
Okay,
because
that's
what
you're
dealing
with
mostly
poly
repos
now
right,
sasha.
C
A
C
C
Yeah,
that's
what
I
do:
angular
node.js
springboot
java
framework
and
all
the
middleware
like
all
the
services,
and
then
we
migrate
the
databases
too.
So
I've
migrated
oracle
to
postgres
absolute
torture,
it'll
torture,
you
that
is
absolutely
torture
and
then
or
or
or
so
we
can
only
use
postgresql
mysql.
That's
it
yeah.
A
C
A
A
All
right,
we
ran
over
a
little
bit.
Anybody
else
have
any
questions.
A
All
right,
I'm
going
to
jump
off.
I
have
another
meeting
to
get
to
so
we'll
talk
to
you
guys
soon,
cool.