►
From YouTube: June 10, 2021 - Ortelius Architecture 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
Okay,
welcome
everybody
to
the
artilleries
working
group
for
architecture
june
10th.
Let
me
put
the
doc
if
you
just
jumped
in
in
the
chat
those
weird
things
again
with
zoom.
A
So
please
go
ahead
and
sign
in,
and
the
thing
I
want
to
cover
today
is-
and
I
don't
know
if
jesse's
on
does
not
look
like
he's
on
yet
last
week
we
covered
swagger
and
how
we
can
utilize
bring
in
swagger
into
the
ui,
and
so
I
want
to
kind
of
to
use
that
that
discussion,
because
we
have
a
couple
other
items
that
are
kind
of
popping
up
around
the
service
catalog
that
I
just
want
to
make
sure
that
we
are
going
to
handle
them
correctly.
A
What
we're
going
to
see
is
we
have
our
our
detail
here.
Some
of
the
other
boxes
is,
we
have
our
dependency
map.
A
We
go
scroll
down.
We
have
where,
where
we've
deployed
to
this
component,
our
key
value
pairs
as
part
of
that
process,
a
graphical
view
of
where
this
deployment
has
this
component
has
been
deployed
to
and
then
a
list
of
consuming
applications
or
audit
trail
or
access
control,
and
in
this
case,
because
I'm
running
deploy
hub,
I
have
change
requests
associated
with
it.
Change
requests,
just
don't
exist
in
or
to
this.
A
So
the
question
is
we're
going
to
be
adding
in
items
like
the
swagger
endpoint
documentation,
so
we'll
have
that
some
of
the
other
things
that
came
up
since
our
last
meeting
was
somebody
wanted
us
to
add
in
the
like
the
readme
file
from
the
github
repo,
the
license
from
the
repo
bring
that
and
associate
all
that
into
the
component.
A
Also
on
our
service
catalog
list,
we
have
the
cves
that
the
container
for
the
component
is
using
or
is
exposed
to.
So
let's
say
we
have
a
python
flask
container
that
python
flask
image
may
have
some
cbes,
so
we'll
have
a
list
of
cves
as
well
as
a
list
of
the
licenses
for
those
python
modules,
for
example.
A
A
You
know
single
page
with
like
bookmarks,
that
you
will
jump
you
to
the
a
certain.
If
I
want
to
go
see,
you
know
the
end
points.
I'd
have
something
up
here
that
I
could
jump
in
and
scroll
me
automatically
to
the
endpoint
section.
Just
give
you
an
idea
what
the
tabs
look
like
if
we
go
into
one
of
these.
A
Here's
a
here's,
one
that
has
at
the
application
level
we
do
use
the
tabs.
So
if
the
general,
then
we
have
the
package
components
which
brings
us
to
a
whole
new
screen
at
that
level.
So
I
just
kind
of
want
to
open
it
up
for
discussion,
get
some
ideas.
What
people
think
what
would
be
the
best
way
to
pull
this
together,
because
I'm
actually
at
the
point
of
pulling
in
the
microservices-
and
you
know,
hooking
the
front
end
to
the
back
end
now.
A
A
Neil,
what
do
you
think
what
what
have
you
ever
experienced
when
you
got
a
website
with
a
lot
of
a
lot
of
data
on
it.
A
C
Yeah,
like
I
was
one,
was
asked
for
that
collapse
and
blocks
in
that
window,
and
first,
we
need
to
group
like
which
we
can
has
as
a
tab.
So
I
think
we
don't.
We
can't
have
everything
as
a
tab,
then
it
will
also
be
a
like
run
time.
We
can't
load
all
the
tabs
into
the
data
into
the
tab,
so
you
have
to
look
into
that
as
well.
A
Yeah,
once
we
figure
out
the
layout,
I
can
figure
out
how
we
can
load
the
stuff
efficiently
from
the
back
end,
because
one
of
the
things
we
used
to
have
in
an
old
version
of
ortelius
was
a
bunch
of
taps,
and
then
we
went
and
got
rid
of
the
tabs
and
brought
it
all.
So
it's
on
a
single
kind
of
like
a
single
pane
of
glass
that
we're
looking
at
so.
A
I'm
I'm
hesitant
of
the
the
tab
idea.
I
think
some
big
tabs,
like
you
said
maybe
group
some
things
together
that
fit
well
together
and
we
make
that
a
tab
and
then
other
things
we
can
group
together
as
part
of
another
tab.
A
What
what
do
people
think
about
the
the
collapsing
of
rose?
You
know
where
we
could
say
you
know,
take
a
row
in
let's
say.
C
So
see
I
was
thinking
like
we
can
have
like
pictorial
representation
representation
of
these
into
one
tab
and,
like
we
have
like
a
data
text.
This
is
like
endpoints
and
then
general
information
in
one
tab
and
the
maps
and
component
connections.
These
pictorial
representations
in
another
tab.
A
B
Okay,
okay,
can
I
ask
a
question
to
you
yeah,
so
I
understand
you're
worried
about
data
exploding
but
like
are,
is
the
it
the
key
value
pairs
and
the
details
that
you're
worried
about
exploding,
or
is
it
just
all
of
these
things
becoming
more
detailed?
Is
there
some
specific
aspect
of
this
that
you're
worried
about
becoming
less
manageable.
A
It
is
because
we
are
adding
so,
for
example,
the
swagger
ui
endpoints.
A
That
would
take
up
a
pretty
good
size
box,
because
if
you
ever
look
at
the
swagger
interface,
it
has
all
your
endpoints
listed
and
then
you
could
like
try
them
and
things
like
that
and
gives
the
documentation
that
would
go
in
one
of
these
boxes
and
we
would
go
ahead
and
you
know
scroll
the
box.
You
know
to
allow
the
navigation
within
like
the
swagger
documentation
and
same
thing
like
with
the
readme.
You
know
the
readme
from
the
git
repo
we'd
bring
that
in
and
we'd
probably
show,
maybe
a
third
of
it.
A
You
know
maybe
a
couple
inches
and
let
people
scroll
on
that
point.
The
other
thing
I
just
thought
of
is
maybe
we
need
to
do
something
like
a
small
snippet.
A
You
know
kind
of
show
a
part
of
it
where
it's
scrollable,
then
we
can
jump
out
into
a
bigger
another
tab
on
the
browser
or
something.
But
that's
the
that's
where
we're
going
christopher
is
we're
getting
more
data.
Different
data
sets.
I
just
talked
to
somebody
tracy.
I
just
talked
to
somebody
a
couple
days
ago.
A
Other
things
that
they
would
like
to
see
is
like
the
sli
and
the
slo
who's,
the
the
primary
top
three
developers
for
the
service
that
type
of
page
the
playbooks
pagerduty
incident
management.
Those
type
of
things
is
what
we're
gonna
be
adding
on
here.
B
Cool,
so
you
know
like
from
a
paneled
ux
experience
sort
of
thing.
You
know
one
of
the
common
things
I've
seen
is
that
you
can
collapse
the
boxes
you
know,
so
we
could
like
minimize
the
dependency
map
and
it
wouldn't
be
taking
up
so
much
space
right
and
the
other
thing
is
that,
like
I
really
feel
like,
given
the
expanding
number
of
boxes,
you
you
need
some
like
intra
page
navigation
like
a
table
of
contents.
B
You
know
maybe,
instead
of
using
the
tabs
as
distinct
sets
of
information,
you
could
have
the
tabs,
be
you
know
thing
that
takes
you
to
that
part
of
the
page,
instead
of
taking
you
to
a
different
page,
but
you
know
that
they're.
If
somebody's
looking
for
the
readme,
you
know
how
are
they
gonna
know
that
it's
at
the
bottom
of
this
page.
A
Exactly
so,
that's
why
I
was
thinking
up
here,
like
you
said,
instead
of
doing
the
the
tabs
going
across,
that
we
would
have
like
the
readme,
like
you
said,
would
be
interrupt
intra
page
navigation
to
the
readme
to
the
cves,
those
type
of
things
I
like
that
idea.
I
think
the
more
we
keep
on
a
single
page.
I
feel
the
better.
A
It
seems
to
be
easier
for
people
to
follow
or
find
people
aren't
are
getting
used
to
scrolling
a
lot.
You
know,
especially
on
your
phone
so
and
jumping
to
the
different
sections,
could
be
pretty
cool.
C
A
Yeah,
I
can
help
you
on
that.
The
this
front
end
code
is
pretty
ugly.
It's
yeah
there's
no
framework
to
it,
so
it's
just
pure
jquery
and
javascript.
So
it's
it's,
not
the
prettiest
piece
of
code,
so
that
aside
I'll
help
you
get
started
on
that.
A
Okay,
we'll
get
you
set
up
there,
we'll
we'll
schedule
a
time
to
get
your
your
eclipse
environment
all
up
and
running,
so
you
can
run
run
locally.
The
front
end
so
part
of
it
was
what
we're
running
into
is
the
front
end
is
a
monolith
based
on
top
of
a
java
application
and
so
the
new
stuff
that
we've
been
doing
like
around
the
new
certain
all
the
new
stuff,
we're
adding
for
the
service
catalog.
It's
all
new
microservices
that
people
have
been
working
on.
A
So
that's
going
to
be
easier
and
we're
breaking
that
away
from
the
monolith
side
of
things.
It's
all
in
the
java
world,
our
our
main.
Well,
I
would
call
our
our
middle
tier
for
lack
of
a
better
word
where
all
of
our
our
database
transactions
exist.
It's
a
java
class.
So
that's
like
35
000
lines
long.
So
it's
not
it's
not
the
best
layout,
but
that's
what
we
have
to
work
with
down
the
road.
A
A
Okay,
so
we
got
a
couple
ideas
there
now,
what
this
is
going
to
have
a
lot
much
harder
to
implement,
but
it
may
be
worthwhile
taking
a
look
at
would
be
to
well
somebody
a
person
from
german
from
belgium
suggested.
A
He
said
he
would
like
to
be
able
to
click
click,
these
three
services
and
then
say
open
and
would
open
up
three
separate
tabs,
so
you
can
then
cut
and
paste
data
from
the
three
different
components,
and
so
that
was
one
thing
that
may
allow
us
to.
A
If
we
do
something
like
that,
we
could
then
break
out
this
screen
into
a
whole
new
framework
as
part
of
that
level.
So
that's
something
that
we
can
consider
as
well.
We
would
lose
this
part
over
here,
but
we'd
have
more
real
estate
for
just
editing
that
component
as
part
of
that
level.
So
that
was
an
interesting
idea
that
he
came
up
with
the
other
question
I
have
is:
do
we
need
to
allow
people
to
pick
and
choose
which
boxes
that
they
want
to
see
kind
of
like
a.
A
Like
a
portal
type
of
thing,
where
you
get
to
go
and
configure
what
you
want,
which
boxes
you
want
where
you
want
them
located
that
type
of
thing,
or
should
we
just
let
it
you
know
kind
of
work
with
what
we
have
does
anybody
does?
Does
that
make
sense
when
I'm
talking
about
those
those
portal
things.
B
A
B
Yeah,
you
know
I
mean
it
is
you
know
that
that's
probably
nicer
for
the
beginning
user,
but
like
for
a
more
advanced
user,
you
know
I
would
want
to
have
something
that
locked
it
in.
You
know
it's
like
I.
I
know
that
I
never
want
to
see
the
cves,
because
you
know
I'm
just
burned
out
on
security,
so
you
know,
even
if
I
accidentally
look
at
it
one
day,
I
don't
want
it
to
pop
up
on
the
next
thing,
but
you
know
having
it
at
least
be
what
the
last
thing
was.
A
Right,
okay,
we'll
put
that
out,
we'll
see
what
we
can
do
in
that
front,
because
we
do
one
of
the
things
that
we
do
do
is
we
persist
the
filters
to
your
user
id.
So
if
I
want
to
next
time
I
come
back,
this
filter
is
persisted
at
the
table
level,
so
we
do
do
some
of
that
persistence
of
like
search
criteria
at
the
u
on
a
per
user
basis,
so
we
have
that
table
there.
So
it
may
be
worthwhile
to
expand
that
as
per
that
process,.
B
Wondering
you
know
like
for
the
details
you
know
like
you.
You've
got
this
really
long
box,
that
has
information
and,
like
somebody
might
only
care
about
50
of
the
details.
So,
like
you
know,
maybe
having
that
stuff
only
show
up
if
it's
populated
or
if
it's
a
non-default
value,
you
know
there's
different
ways
but
like
maybe
making
that
searchable
in
the
same
way.
That
other
thing
is.
A
Okay,
yeah
on
on
the
the
new
front
end
that
I've
been
working
on.
I
cut
it
off
and
like
this
data
here
is
in
the
left-hand
side
box
and
I
moved
the
dependency
map
down
to
the
bottom,
and
then
I
started
taking
this
other
data
and
moving
it
over
here.
So
I've
already
started
the
split
on
the
the
ui
work.
I've
been
doing
so
it
definitely
works
better
to
have
it
in
not
such
a
long
list
as
part
of
that
process.
It
makes
it
definitely
easier
to
to
read.
A
A
I
think
that
was
the
main
stuff.
What
I'd
like
you
everybody
to
do
is
on.
A
I
want
to
make
sure
that
we're
not
missing
anything
as
far
as
what
we
need
from
a
service
catalog
perspective,
so
I
will
put
out
on
our
discord
channel
the
list
of
everything
that
we
are
gathering
and
if
we
could,
everybody
could
just
review
it.
I'll
put
it
on
a
dev
channel,
just
review
it
and
see
if
we
need
to
add
anything
like
like,
I
said,
sli
and
slo
came
up.
Also,
there's
been
some
things
popping
up
around.
A
A
D
D
I
think
that
probably
is
just
another
another
effort,
because
we'd
really,
I
think
at
this
point
adding
that
information
might
require
us
determining
which
apm
tool
we're
going
to
integrate
with,
or
we
have
to
do
them
all
at
once,
at
least
the
main
ones
yeah.
I
would
leave
that
off
the
table
for
now,
but
I
would
suggest
that
everybody
take
a
look
at
two
two
websites
backstage
one's
called
backstage,
and
this
is
they
consider
this
a
portal
for
for
developing.
D
Developer
platforms
because
you
can
go
in
and
say
I
want
to
develop
this
kind
of
a
solution
and
I
click
on
this
option
and
it
builds
my
ci
cd
pipeline
in
the
back,
but
it
does
have
a
nice
registry
of
nice
catalog,
and
this
is
a
cncf
project.
That's
gaining
some
traction,
so
I
would
say
it's
the
catalog,
the
registry
part
of
it.
We
should
be
looking
at
closely
and
how
they
do
things
there
and
the
other
one.
Is
this
company
called
ops
level?
D
Now
ops
level
is
a
it's
a
commercial
product
and
they
are
super
focused
around
nothing
but
doing
support
at
the
production
level
clusters.
But
I
think
that
it
would
do
us
all
good
to
know
what's
in
these
products
and
make
sure
that
our
catalog,
our
service
catalog,
is
going
to
compete.
Well
with
these
two
products.
B
So,
on
the
observability
front,
you
know,
apm
is
really
key
from
like
in
integrating
information
across
your
component
standpoint
and
it
helps
you
know,
isolate
where
stuff
is
going
on,
but
like
on
a
component
by
component
level,
you
would
tend
to
have
either
a
inaugural
style
check,
which
is
like
either
upwards
down.
Basically
or
you
would
have
metrics.
You
know
so.
B
You'd
have
time
series
history,
data
graphs
to
show
the
health
of
something-
and
you
know
grafana-
is
pretty
best
of
breeding
in
you
know
in
this
graph
presentation
sort
of
stuff,
and
so
I'm
guessing,
we
could
probably
take
a
grafana
component
and
put
it
in
a
box
and
not
have
to
build.
A
A
B
The
only
real
problem
I
see
with
that
is
that
you
might
have
50
grafts
associated
with
something,
so
you
might
like
want
a
drop
down
box
or
something
to
let
people
choose
which
graph
they're
looking
at
now.
But
you
know
that
I
I
that
that
seems
like
relatively
low
hanging
fruit.
Instead
of
trying
to
integrate
apm
with
artilleries.
A
Right
right:
well,
that
was
the
other
thing
when
we
do
these
integrations,
because
a
lot
of
the
the
starting
point
will
be
gathering
basically
where's
the
url.
What's
the
url
for
pagerduty,
you
know,
for
example,
and
then
or
what's
what's
the
url
for
the
cve
and
from
there
when
we
go
to
display
that
we
either
just
jump
them
to
another
tab
to
let
them
view
that
data
or
we
do
an
iframe
and
bring
that
in
as
another
box
as
part
of
that
process.
A
A
A
A
Okay,
excellent
anybody
have
anything
else.
I
think
so
what
I'll
do
is
it
kind
of
sounds
like
the
consensus
would
be
to
have
the
collapsible
boxes
like
we
were
talking
about
reorder
them
kind
of
group
them
together
a
little
bit
better
and
then
do
the
book,
the
navigation
tabs,
to
get
to
get
you
to
the
right
place
on
the
page.
A
If
I
want
to
go
see,
dependencies
will
get
me
to
the
to
that
section
of
that
pr
area.
So
I
think
that
am
I
missing
anything,
or
is
that
basically
the
plan
that
kind
of
seemed
like
we're?
Gonna
start
with.
A
Okay
and
I'll
put
some
and
then
the
other
thing
is
I'm
going
to
put
out
on
our
dev
discord
channel
all
the
service
catalog
information
that
I
can
think
of
and
I'd
like
everybody
just
to
review
it
and
add
to
it.
If
I'm
missing
anything
you
know
like
tracy,
says
one
of
the
things
that
we're
we've
we're
moving
into
the
world
where
artelias
is
becoming
a
data
hoarder,
where
we
want
to
go
and
grab
as
much
information,
we
can
around
components
and
applications,
environments
and
those
type
of
things.
A
A
Okay,
perfect
devon.
Try
to
I
will
touch
base
with
you
to
figure
out
a
time
to
get
your
dev
environment
set
up.
A
We
are
definitely
getting
a
plan
in
place
here
and
we'll
be
able
to
get
by
I'm
hoping
by
definitely
by
our
next
architecture
meeting,
but
hopefully
by
our
next
just
general
meeting
I'll,
be
able
to
show
some
of
the
layout
changes
that
we
got
going
on.
So
people
get
a
feel
for
where
we're
headed.