►
From YouTube: May 27, 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
artillious
may
27th
architecture,
meeting
the
8
30
a.m.
Mountain
time
looks
like
we
have
a
couple
new
people.
If
you
could
introduce.
A
Give
a
quick
background
of
what
you
are
are
up
to
and
what
you're
interested
in.
C
D
D
C
Okay,
actually
we
got
both
the
things
also,
so
we
normally
work
on
vms
only
and
but
we
are
also
open,
kubernetes
and
comment
says
also,
so
I
think
I
have
some
I'm
actually
a
newbie
only
so
I'm
just
learning
around
okay.
A
No
problem
and
are
you
interested
in
doing
any
coding
or
what's
the
interest
with
the
artelias
group,
so
we
can
make
sure
we
can
help
you
out.
C
A
E
I
have
java
experience
as
well,
I'm
right
now
working
with
wells,
fargo
and
so
it's
kind
of
a
close
door
kind
of
projects
we
do,
and
I
I
used
to
make
open
with
open
source
contributions
three
years
ago
and
then
I
just
left
out
from
the
open
source
community.
Now
I
wanted
to
join
back
and
I
had
met
jesse
reagan
and
then
through
through
her
like
I
joined
julius,
and
I
want
to
contribute.
E
A
The
new
microservice
work
that
we've
been
doing
is
around
python
flask,
so
you'll
fit
right
into
that
really
quick.
A
And
it
looks
like
we
have
jesse
yeah,
okay.
B
Hey
hey
guys,
long
time
no
see
so.
Yes,
I've
been
here
a
few
times,
but
a
new
role
in
life
is
kept
me
super
busy
and
then
some
pretty
famous
breeches.
I
think
that
you
guys
have
heard
of
recently
has
also
taken
up
quite
a
bit
of
my
time.
So,
okay,
well.
A
Yep,
I
threw
the
link
in
there
if
you
could
sign
in
and
so
where
we
left
off
with
this
tracy.
Can
you
move
yours
because
I'm
getting
a
crazy
echo.
A
A
metadata
or
like
tracy
likes
to
call
it
data
hoarding
that
artelias
is
going
to
be
doing
or
does,
and
the
for
swagger
it
kind
of
came
to
the
decision
that
we
were
going
to
pull
in
the
swagger
yaml
files
and
store
them
somewhere
inside
of
ortelius's
database
or
more
likely
in
the
database,
because
they're
not
that
big
and
be
able
to
version
that,
along
with
the
com,
the
microservice
that's
getting
created.
A
So
what
we're
going
to
need
to
do-
and
I
believe,
there's
also
something
called
open
api.
I
have
to
double
check
on
that.
That's
comparable
to
swagger,
so
we'll
have
to
bring
in
either
swagger
yamo
or
open
api
yaml
file.
I
don't
know
if
they're
interchangeable,
let's
do
some
research
on
that
front,
so
I'm
going
to
need
if
somebody
would
like
to
do
some
research
on
how
we
can,
if
there's
any
like
javascript
libraries
or
if
there's
like
a
mini
swagger
server
that
we
need
to
embed
in
ortelius.
A
B
Yeah
you
can
put
my
name
on
that
spend
some
time.
I
want
to
say
that
open
api
and
swagger
are
interchangeable,
and
maybe
that
swagger
implements
the
open
api
spec.
But
I
don't
recall
right
now,
but.
A
A
The
let
me
show
you
what,
where
it's
going
to
fit
in,
so
it
gives
you
a
better
context.
Let
me
find
my
screen.
A
Okay,
so
if
we
look
at
a
a
microservice,
the
data
that
we've
been
gathering
is
information
like
the
build
engine.
A
Well,
this
one
was
done
by
circle,
ci
the
build
number
where
it
was
pushed
to
the
the
container
registry,
the
container
digest
the
git
commit,
and
what
we're
in
the
process
of
doing
is
this
big
area
from
probably
from
last
build
number
down
we're
going
to
split
that
out
into
a
new
box
here
and
things
that
are
going
to
be
added
into
that
that
area
or
it
may
get
split
into
multiple
boxes,
are
going
to
be
things
like
the
service
owner.
A
A
Documentation
as
part
of
that,
and
if
it
gets
too
big,
we
may
just
we
have
room
to
put
it
on
another
page
as
well.
B
Okay,
so
should
be
a
way
just
to
expose
the
underlying
microsoft,
the
underlying
essential
services.
Swagger,
your
open
api,
spec,
okay,
okay,
makes
sense.
A
Yeah
so
like
here,
here's
the
yaml
file
yeah
and
then
you
have
like
these
pieces
over
here.
So
in
a
microservice
you're
not
gonna
have
a
hundreds
of
different
endpoints.
You
know
it's
gonna
be
confined
to
a
smaller
subset
of
endpoints,
but
this
is
this
area
over.
Here
is
what
we're
looking
like
to
embed
over
in
this
area
as
under
a
component.
B
A
Yeah,
so
this
is
like,
in
this
case
there's
a
pet
endpoint
which
would
be
equivalent
to
the
microservice,
so
we're
looking
at,
maybe
a
dozen
possible.
You
know
calls
that
we'll
have
to
render
up
in
that
air
in
that
box
area,
so
see
what
you
can
find.
F
And
there
there
is
backstage
has
a
good
example
of
how
they've
integrated
with
it.
So
that
may
be
something
you
want
to
take.
A
look
at
as
well
doesn't
doesn't
backstage,
have
a
link
to
it
or.
F
Oh,
I
thought
they
were
tracking
like
api,
like
endpoints
and
documentation
on
a
microservice.
A
I
don't
remember,
I
had
to
double
check
again,
but
I
didn't
think
so
they
were.
That
was
another
thing
that
we
need
to
bring
in
that
to
add
to
the
service
catalog
is,
we
know
where
the
get
repo
is,
and
one
of
the
things
we
need
to
bring
in
is
the
readme
file
and
the
license
that's
actually
associated
with
that
get
repo
for
this
service
and
bring
that
in
as
a
couple
other
boxes.
A
I
have
a
feeling
we're
going
to
have
to
expand
onto
multiple
tabs
here,
just
because
we're
it's
going
to
get
pretty
long
real
estate
wise.
A
I
don't
know
that
will
be
something
that
we'll
have
to
play
around
with
and
see
because
I
know
sometimes
people
hate
going
to
different
tabs,
but
at
the
same
time
I
don't
know
which
was
which
is
what
better
to
scroll
or
to
tab
over,
so
we'll
have
to
kind
of
play
around
to
get
we'll
have
to
get
some
ideas
around
that
once
we
start
getting
data
in
here
and
seeing
what
it
looks
like-
and
I
know,
there's
chrome
was
talking
about
moving
the
dependency
map
lower
in
the
the
list.
A
So
we
can
move
the
catalog
data
up
in
this
upper
right
hand
corner
so
all
right
perfect.
So
that's
thank
you,
jesse
for
taking
that.
What's
your
github
handle.
A
A
B
And
that
that
your
reference
tracy
was-
or
maybe
you
can
answer
this
too
steve
was
backtraced
that
I
sorry
backstage
dot,
io
right,
yeah.
A
Let
me
see
if
I
see
it
in
yep
there
you
are
so
for
the
new
folks.
If
you
could
do
me
a
favor,
and
let
me
share
my
screen
again:
real
quick
come
on
zoom.
Where
did
you
go.
A
A
A
So
if
you
need
help
doing
a
pull
request,
if
you've
never
done
one
before
just
reach
out
and
we'll
help
you
out
of
that
front,.
E
Okay,
yeah,
just
on
the
swagger
topic
like
have
some
experience
with
this
packer
like
if
I
can
contribute
something
with
jesse.
I
would
like
to
do
that
actually.
A
Okay,
what
is
your
github
handle,
so
I
can
keep
an
eye
out
for
it
when
I
pop.
A
Okay,
perfect,
if
you
do
that,
pull
request
against
the
main
repo
for
the
readme
I'll,
be
able
to
add
you
to
the
issue
with
jesse,
so
the
two
of
you
can
be
on
that
same
issue
and
get
notified.
When
we
have
a
discussion
going
on
there.
A
A
So
I
know
from
a
front-end
perspective
what
we
need
to
do
as
far
as
integrating
with
that
just
so
I
have
a
a
game
plan
on
that
front,
so
that's
kind
of
what
I'm
looking
for
there
try
and
think
what
else
was
on
my
list
or
go
back
to
the
doc.
A
Oh
so
the
just
to
let
you
know
the
I,
I
was
able
to
get
additional
credits
from
microsoft,
azure
for
running
ortillius
in
a
kubernetes
cluster
that
I
had
to
do.
The
switchover
between
the
subscriptions
on
the
third
of
june,
so
after
the
third
of
june
I'll,
be
able
to
go
ahead
and
add
new
own
new
new
people
to
have
permissions
to
our
kubernetes
cluster
in
azure.
A
So
we
got
another
year
which
is
good
as
part
of
that
the
get
ops
the
australian
group
is
going
to
be
installing.
A
I
don't
remember
if
it's
gonna
be
argo
or
flux
which
one
they're
gonna
go
with
first
into
the
cluster,
so
they
can
understand
how
that's
going
to
work
with
the
whole
get
ops
picture
that
we're
working
around.
So
just
a
heads
up
on
that
if
you
need
to
have
access
to
azure.
For
any
reason,
just
let
me
know
and
we'll
get
that
sorted
out.
The
azure
active
directory
security
model
can
be
very
complicated.
It's
not
the
easiest
thing
to
get
get
security
set
up
like
you
think
it
would
be.
A
I
looked
at
I'd,
ran
a
report
and
I
ended
up
with
like
8
000
security
objects
that
I
had
access
to
a
little
bit
too
much
over
my
head.
So
that's
just
a
heads
up
the
coding
we
have
additional
I'm
waiting
on.
I
was
hoping
sergior
sergio
was
here.
A
There
is
a
python
circuit,
breaker
module
that
we're
going
to
be
using.
He
was
working
on
the
implementation
of
that
and
what
that's
doing
is
handling
database
connections
and
retries,
and
things
like
that.
I
will
reach
out
to
him
to
catch
up,
to
see
where
he's
at.
On
that
front.
Also
on
discord,
I
did
put
a
new
channel
out.
There
called
stand
up,
and
basically
that
is
for
us
to
work
with.
You
know,
notify
each
other
that
you're
waiting
on
somebody
for
something.
A
A
Trying
to
think
what
else
we
had
on
the
list,
I
think
that
was
the
main
thing
I
know
a
dt.
Is
there
anything
that
you're
waiting
on
from
your
side?
I
can't
remember
regarding
what
that's
why
I
wasn't
sure
if
it
was
you
or
aisha,
that
was
waiting
on
some
stuff
for
for
the
micro
services.
A
So
if
we
we,
let
me
share
my
screen
one
more
time.
A
So
the
issues
that
we
have
we'll
go
ahead
and
go
to
projects.
A
Are
the
the
microservices
and
for
a
bala
there's
another
person
that
is
like
brand
new
to
programming
and
stuff
knows
some
basics
and
we
start
out
with
a
a
simple
python:
flask
bubble
sword
to
kind
of
get
your
feet
wet.
If
you're
interested
in
that,
let
me
know-
and
I
will
set
up
the
issue
and
what
ends
up
happening
is
those
evolve
into
full
on
microservices?
A
So
we
take
you
step
by
step
through
the
coding
process
to
get
you
to
a
point
where
you're,
actually
coding,
sql
queries
and
doing
things
like
that
against
the
database.
If
you're
interested,
let
me
know
and
I'll
set
that
up
for
you.
A
A
Yeah,
it's
not
hard
to
find
it,
but
if
anybody's
interested
in
doing
a
little
bit
of
golang
programming,
let
me
know
there
is
an
issue.
A
I
can't
find
it
right
now,
but
basically,
what
we
need
to
do
is
to
bring
in
or
run
cyclone
dx
and
like
safety
and
a
couple
other
scanning
tools
against
a
cluster
or
against
a
container
gather
the
information
and
then
be
able
to
hit
the
end
point
here
this
one
here
for
doing
dependency
management,
so
that's
kind
of
where
we'll,
if
somebody's
interested,
it's
not
a
very
big
golang
program.
A
B
I
don't
want
to
commit
to
too
much,
but
I've
done
some
golang
development.
So
I
can.
I
can
help
if
anybody's
interested
as
well
on
the
golang
front,
but
maybe
like
I
don't
want
to
volunteer
for
too
much
all
at
once
and
kind
of
slow
things
down,
but.
A
Yeah,
we'll
we'll
let
go
ahead
and
just
focus
on
the
swagger
stuff,
because
that's
a
pretty
big.
A
Task
there
and
then
we'll
focus
on
the
golang
piece.
The
golem
piece
isn't
isn't
it
is
it's
down
the
road?
So
it's
not
something
that
we
need
to
do
right
right
off
the
bat
today.
So
a
couple
weeks
down
the
road
we'll
be
able
to
bring
that
in
so
we'll
keep
in
that.
For
some
reason,
I'm
not
seeing
your
user
id,
but
that's
something
I
have
to
do
on
the
the
github
side
to
get
you
assigned
to
this.
But
this
will
be
the
issue
306.
A
And
I
believe,
is
devendran
you're
you're,
also
interested
in
the
swagger
piece.
A
I
believe
he
said:
okay
I'll,
add
you
to
the
same
issue
so
be
306
is
what
you'll
get
us
assigned
to
as
part
of
that
so
awesome
tracy.
Am
I
missing
anything
else.
F
A
Well,
I
was
thinking
of
for
the
service
catalog
we
would
be
middle
of,
I
would
say
by
july,
middle
of
july
would
be
where
I'd
like
to
target
it.
Well,.
F
That's
six
weeks
from
now,
so
if
that
thing,
if
you
guys
think
you
can
get
that
done
in
that
period
of
time,
but
we
do
need
to
put
a
stake
in
the
ground
for
when
we're
going
to
get
that
delivered.
So
we
can
start
talking
about
it.
A
Well,
let
me
let
me
look
through
what
we
have
and
where
we're
at
and
on.
Is
it
monday's
call
the
general
meetings
on
monday
or
is
it
on
tuesday?
I
can
never.
F
Remember
I
think
the
general
meeting
is
on
tuesdays
at
8
30.
yep.
A
So
I
will
look
at
it
and
see
where
we're
at
and
try
to
figure
out
a
date
for
that
and
we'll
bring
it
up
to
the
general
meeting.
So
everybody
knows
what's
happening.
F
A
Because
I
know
a
lot
of
the
stuff,
a
lot
of
the
microservices
have
been
are
pretty
far
along,
so
I
think
it's
just
a
matter
of
pulling
pieces
together,
we're
getting
closer
to
that
point
and
I
think,
from
an
architecture
standpoint
we've
narrowed
in
as
where
we
want
to
focus.
You
know
we
have
the
swagger.
A
We
know
we
need
to
bring
in,
like
the
the
scanning
tools
licenses,
those
type
of
things,
the
readme
file.
I
think
we
have
a
pretty
good
idea
of
what
we
need
to
collect,
and
now
it's
just
hit
the
ground
running
and
get
all
those
pieces
pulled
together.
E
A
I
haven't,
I
don't
have
my
email
I'll
get
that
in
the
next
few
minutes
here
and
then
what
I'll
do
is
I'll
also
set
up
everybody
into
the
right
group,
cf
permissions
to
all
the
the
repos
and
and
we'll
be
able
to
get
a.
You
know,
assign
issues
comment
on
issues,
those
type
of
things,
so
I
will
take
care
of
that
as
soon
as
we're
done
here.
A
E
Yeah,
just
from
like
one.
E
A
Yeah
from
the
the
layout
perspective,
that's
a
a
great
idea.
Let
me
see
how
we
could
implement
that
and,
if
that's
going
to
make
it.
A
Do
you
think
we
should
yeah?
We
could
probably
do
it
by
row
I'll
have
to
see
because
the
boxes
are
like
on
a
row.
A
Let
me
share
real
quick,
so
like
this,
this
endpoint
and
key
value
configuration
I
I
get.
What
you're
saying
is.
If
we
can
do
like
a
a
a
hide
expand
button,
where
we
can
highly
expand
that
that
row
could
work
to
help
us
with
the
real
estate.
A
A
The
the
hard
part
is,
this:
ui
is
written
all
in
javascript
with
jquery
and
there's
no
framework
behind
it.
So
it's
just
random
javascript
code.
So
there's
like
really
no,
it's
not
like
you're
using
view
or
react,
so
you
know
changing
some
things
can
be
interesting.
Put
that
way,
but
I
like
the
idea.
A
Well,
thank
you,
everybody
and
on
tuesday
8
30
to
a
half
hour.
Basically,
this
time
we'll
have
our
general
meeting
and
I
will
get
everybody
between
in
the
next
few
minutes,
I'll
get
everybody's
access
and
github
straightened
out.
Bollock
and
devin
welcome
aboard
and
good
to
see
you
back
jesse.