►
From YouTube: Jan 6, 2022 - 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).
C
All
right
so
to
say
again:
this
is
the
january
6th,
2022,
ortiz
architecture.
Meeting
I
put
the
link
to
the
doc
in
the
zoom
chat.
Please
sign
in
and
we'll
get
started
here,
so
just
kind
of
recap,
some
of
the
stuff
that
we
were
kind
of
wrapping
up
or
talking
about
last
year.
C
C
There
is
a
open
source
project
out
there.
I
think
we
can
incorporate
pretty
easy
into
our
google
cloud
build
at
that
level.
So
I
have
to
open
an
issue
on
that,
so
I
will
get
that
out
there.
C
One
of
the
other
things
is
aisha
was
going
to
look
at
how
he
can
incorporate
the
libya
into
our
components.
C
So,
for
those
that
don't
know
what
a
libyar
is,
it
basically
is
a
way
to
calculate
how
old
the
packages
that
you
are
consuming
are
so,
let's
say,
there's
been
like
log4j
if
you're
on
version,
one
two,
eight
of
log
for
j
and
the
current
versions,
217
your
the
diff,
the
time
difference
between
when
the
the
one
two
eight
was
released
and
the
current
217
release
is
what
they
call
the
beer.
C
So
it's
just
a
gauge
of
how
how
well
developers
are
staying
up
to
date
with
the
latest
version
of
their
dependencies
issues,
working
on
that
to
kind
of
design
out
and
lay
out
what
we
need
to
do
on
the
database
and
where,
where
we
can
kind
of
keep,
you
know
store
this
data
when
we
do
that,
we'll
probably
have
a
couple
more
microservices
to
load
that
data.
C
So
look
for
a
couple
if
anybody's
interested
in
some
python
microservices
that
will
probably
be
coming
out
of
that.
What
aisha
is
designing
there?
If
everyone
wants
to
help
her,
just
let
you
can
reach
her
on
the
discord
channel.
The
next
is
the
service.
Catalog
that
we've
been
working
on
seems
like
forever.
C
We
are
getting
very
close.
I
have
a
meeting,
we
have
our
another.
You
know
like
nine
hours
from
now,
we'll
have
the
australian
architecture
working
group
and
from
what
I
could
see
with
the
prs
that
they've
been
doing,
they've
been
figuring
out
this
whole
helm
process
in
artifact
hub
and
all
that
that
we
will
be
using
to
do
a
simple
one-line
install
of
ortelius.
That
was
kind
of
like
the
goal
that
we
had
was
to
do
a
single
online
install
if
anybody's
interested.
C
I
believe
we
still
need
a
a
a
helm
chart
that
includes
the
child
charts,
so
we
need
a
parent
hom
chart
that
includes
the
child
ones.
C
Okay,
cool:
it
should
be
pretty
easy,
it's
just
getting
the
format
down,
so
I
will
I'm
gonna
put
your
name
next
to
that
sasha,
yeah
and
I'll
make
sure.
There's
an
issue
out
there.
I
have
to
hunt
down
the
issue
number
for
you.
C
All
right
and
then
as
part
of
that,
once
we
get
that
kind
of
this
whole
install
process
wrapped
up,
then
we
just
need
to
make
the
final
changes
to
our
documentation.
So
we
know
what
the
you
know:
how
to
run
and
run
it
and
stuff
like
that.
C
If
you
jump
over
to
artifact
hub,
so
artifact
hub
used
to
be
called
helmhub
and
they
replaced
it,
the
helm
folks
did
over
to
this
to
be
a
little
more
generic.
So
we
can
actually
here's
our
what
they've
been
working
on.
These
are
our
microservices
that
are
that
are
currently
in
place
to
run
our
application.
C
So
this
is
where
we
need
the
one
more
parent
chart
to
kind
of
like
include
all
these
in
a
single
go,
and
these
look
like
yeah,
like
validate
user,
got
updated
nine
days
ago.
So
it
looks
like
the
automation
on
the
back
end
through
some
github
actions
and
a
couple
other
things
is
working,
so
that
will
simplify
things.
So
that's
like
what
ben
and
ahmet
and
brad
from
down
under
are
pulling
together
for
us
on
that
front.
C
We
got
some
bad
security
ratings,
an
f
yeah.
I
want
to
look
at
that.
I
have
not
seen.
I
knew
we
had
one
coming
out
of
that.
I
see
in
the
docker
image,
but
I
have
not
seen
any
in
big
detail
on
this
level.
So
I
want
to
take
a
look
at
that
as
well
I'll
open
an
issue
about
checking
the
the
security
vulnerabilities
in
what
these
are
popping
up.
C
I
can't
tell
I
think
so:
it
may
be
not
only
in
the
in
the
docker
image,
but
also
in
the
the
packages
that
we're
consuming.
Okay,
they're
python
has
a
couple.
C
I
saw
with
the
requests
python
module
that
you
had
to
upgrade
to
a
newer
version
to
get
around
some
of
the
cves
at
that
level,
and
one
of
the
things
I'm
working
on
kind
of
in
general
is
to
get
better
data
for
us
to
play
with,
and
part
of,
that
is
to
add
in
the
vulnerability
scan
against
our
own
microservices
and
when
we
push
them
out
there,
because
the
the
other
thing
that
we
have,
if
you
actually
log
into
deploy
hub
there,
it
is-
and
if
we
log
into
the
artillious
project
in
there
we'll
see
where
we're
keeping
track
of
ortelius
itself
and
deploying
it.
C
So
here
you
can
see
that
the
the
ortulius
devops
is
what
we're
currently
building.
So
that
is
the
the
package
that
we
are
consuming
and
it
has
all
of
our
our
microservices
as
part
of
that,
the
other
ones
that
you're
seeing
are
like
the
website
documentation.
C
Those
types
of
things
are
being
run
through
as
well.
So
these
are
all
the
website
updates
that
we've
had
and
change
the
filter.
We
shared
the
documentation,
so
here's
the
documentation
that's
being
published
as
well,
so
for
those
of
you
that
are
new,
our
documentation
and
our
website
are
hugo
markdowns.
C
We
run
it
through
the
hugo
engine
and
that
creates
a
static
sight
for
us
and
then
that's
all
part
of
our
our
docker
build
and
we
end
up
with
a
basically
it's
an
engine
x
website
with
a
bunch
of
static
files
underneath
it
that
came
from
the
markdown
files
and
then
we
use
the
nginx
page
speed
module
to
optimize
it.
So
we
get
nice
page
speed
loads
with
the
application,
and
that's
all
done
you
know.
So
we
have
this.
C
This
handoff
between
the
the
google
cloud
build,
deploy
hub
and
artelias,
so
deploy
up
is
based
on
artillery.
So
it's
like
we're
the
downstream
project
from
or
to
this.
So
that's
where
we're
we're
picking
this
information
up
and
and
going
with
it.
C
How
do
we
view
changes
over
time
so
as
an
application
gets
released?
What
are
the
the
changes
that
are
happening
with
it?
You
know:
do
we
can
we
identify
which
components
are
changing
the
most
frequently
you
know
so?
Is
there?
Is
there
like
a
specific
microservice
that
is
constantly
changing
and
then
there's
gonna
be
a
set
that
are
pretty
static
because
one
of
the
things
that
you'll
see
in
general?
C
Programs
openmake,
I
have
code
in
there
from
the
90s
that
I
haven't
touched
it
since
then,
since
we
originally
wrote
it.
So
that's
where
we're
talking
about
visualization
is
looking
at
some
sort
of
time.
Scale
was
one
of
the
ideas.
Maybe
a
3d
bar
chart
expanding
the
the
hierarchical
edge
bundling.
C
C
Well,
proverage,
can
you
talk
about
what
you've
done
with
the
testing.
E
Yes,
actually
I
initially,
I
started
a
testing
using
open
source
tool
actually
so
for
that,
I'm
using
java
and
a
certainty
framework.
So
it's
like
a
bdd
approach,
so
normally
in
software
development
we'll
follow
the
agile
technology.
So
the
for
that
vdd
approach
is
there
so
for
that
open
source
framework.
Already
it's
available.
So
I'm
using
that
framework
and
I
developed
some
poc,
like
just
I've,
opened
a
publication
tab.
E
C
Nice
and
then
also
on
the
on
the
testing
front,
I
think
we're
going
to
have
to
have
you
kind
of
share
with
us
how
to
kind
of
word
or
phrase
the
test
cases,
because
you
said
there's
like
a
certain
format
that
helps
you
be
able
to
build
out
the
actual
test
case
for
more
of
a
english
or
a
paragraph
style.
E
C
It
so
we'll
need
to
work
and
creating
those
those
test
cases,
and
you
know
everybody
learn
how
to
do
testing,
because
it's
one
thing
I
do
awful.
E
C
Right
so,
let's
go
so
that's
moving
along.
Oh,
I
did
merge
your
pull
requests
just
a
little
while
ago,
so
you'll
you'll
see
that
your
action
has
been
merged.
So
one
of
the
things
that
now
that
we
have
the
the
poc
kind
of
we're
kind
of
over
the
hump,
where
the
next
step
is
integrating
it
into
our
as
a
github
action
to
be
able
to
render
the
results
off
of
our
our
github
repo.
C
C
We
make
sure
that
you
get
a
well-rounded
experience
with
us.
So
if
you
want
to
learn
something
new,
just
just
reach
out
on
discord,
and
we
can
make
sure
that
you
get
the
help
that
you
need,
if
you
want
to
try
something
new
with
that
lakshmi,
why
you
go
ahead
and
introduce
yourself.
F
Hi
I'm
lakshmi
and
I
have
experience
working
as
an
infrastructure,
automation,
engineer
I've
I
primarily
code
in
python
and
powershell,
and
for
the
past
year
I've
been
working
with
azure.
Prior
to
that
I,
for
a
couple
of
years
I
had
my
hands
started
with
aws
as
well,
so
I
have
experience
on
devops
related
activities
and
no
development
experience.
C
Okay,
well
through
your
python,
we
can.
We
can
definitely
transition
you
and
give
you
an
opportunity
to
work
with
some
microservices
new
ones
that
we'll
have
coming
down
the
road
if
you're
interested
one
of
the
nice
things
with
with
microservices
and
the
approach
that
we're
kind
of
taking
with
or
to
this
or
to
this
is
a
monolith.
C
And
it's
just
like
the
data
access
routines.
The
30
000
line
java
program
java
class
and
instead
of
keep
on
doing
new,
updates
that
anything
new
new
transactions
and
stuff
we're
moving
into
the
python
fast
api
world
for
the
microservices
and
one
of
the
goals
that
we
kind
of
laid
out
was
trying
to
keep
the
program
under
250
lines.
Long,
so
we'll
be
able
to
get
you
that
developer
experience
with
those
types
of
programs
without
getting
making
a
weed
through
a
30
000
line
program.
C
And
then
the
just
to
give
you
some
background
around
the
devops
world,
we
kind
of
span
all
the
different
providers.
So
our
you
know
we
use
github
as
our
our
main
repository.
C
We
have
github
actions
that
will
execute
up
there.
We
have
google
cloud
build
to
do
the
build
and
that
will
publish
over
to
the
quay,
which
is
the
red
hat
registry
and
then
through
deploy
hub.
We
actually
deploy
out
to
an
azure
cluster.
C
So
we
have
a
little
bit
of
everything
happening
and
we
kind
of
kept
it
that
way
to
make
sure
that
if
somebody
had
a
bunch
of
aws
experience
and
they
wanted
an
azure
that
they
can
get,
that
feel
for
it
same
with
gcp
and
stuff
like
that.
So
we'll
make
sure
that
you're
you're,
not
bored.
H
C
Backwards
in
the
and
get
you
know,
your
favorite
thing:
sasha
merge
conflicts
in
github.
B
F
F
I
D
And
sergio
on
that
note,
I
think
you
need
to
we
need
to
the
three
of
us
need
to
get
together.
So
you
can
understand
your
your
role.
D
One
of
the
one
of
the
kind
of
roles
or
jobs
that
we've
been
missing
is
what
marky
jackson
was
really
really
good
at
doing
and
what
he
would
do
is
he
would
watch
for
the
pull
request
and
he
would
reach
out
to
people
and
say:
hey
here's
a
really
good,
first
time,
kind
of
pull
request
that
you
might
want
to
work
on
and
help
people
identify
with
what
they
should
be
doing,
and
that
is
the
role
we
we
really
really
need,
and
I
think
you'll
be-
I
think,
with
your
background-
and
you
know
pretty
much
most
of
everybody
on
the
team
that
you'll
be
able
to
start
doing
that.
D
So
I
think
that
will
be
your
primary
kind
of
role
in
being
that
care
person
is
to
help
help
push
the
pull
request.
C
And,
and
you
know,
kind
of
navigate
issues
to
people.
I
Yeah,
I
will
yes,
I
will
think
about
that.
I
will
love
to
do
that
because
the
the
moment,
the
few
times
I
try
to
take
like
like
okay,
let
me
try
something
it's
like
a
pool
of
stuff
and
you,
like
you,
don't
know
what
is
the
priority?
What
is
important,
what
is
what
is
going
to
go
about
so,
okay
yeah?
I
will
look
to
to
take
on
that
and.
D
Yeah,
I
think,
if
you
and
steve
start
watching
them
and
initially
start
doing
it
together
and
saying,
let's,
let's
give
this
to
laxmi.
This
was
something
that
you
probably
could
get
started
on.
You
know:
let's
push
this
over
to
arvind
he's
not
coded
anything.
Yet,
let's
give
them
that
to
work
on.
D
I
I
think
that
the
we'll
get
more
contribution
that
way,
because
then
everybody
knows
that
they've
been
given
something
and
they're
going
to
get
supported
on
it
as
well,
instead
of
just
taking
on
something,
I
don't
think
we
have
enough
experience
in
our
open
source
community
yet
to
just
start
taking
things
out
on
their
own.
C
Yeah
and
we
may
need
to
just
do
a
another
meeting
to
kind
of
weed
through
and
and
re-categorize
all
the
issues
just
to
help
and
clarify
some
of
this
stuff
to
make
it
because
when
you
go
out
there,
there's,
like
you,
know,
80
issues
and
it's
a
little
overwhelming.
D
Exactly
exactly-
and
you
know,
I
think,
the
more
that
you
and
steve
work
on
it
together
to
start
assigning
issues
it'll
be
easier
to
figure
out
how
you
need
to
organize
them,
or
at
least
tag
them
like
best
good,
first
issue,
you
know
high
coding
requirements,
low.
C
So
here's
a
question
for
you
that
is
for
as
being
part
of
an
open
source
community.
Do
you
think
it's
okay
to
have
deadlines
for
like
an
issue?
So
let's
say
we
needed
you
to
write
a
new
microservice
and
or
like
for
sasha
we're
going
to
do
the
helm
chart.
Do
you
think
it's
appropriate
to
assign
like
a
a
deadline
like
a
week
out
or
something
like
that,
or
do
you
think
that's
a
little
tacky.
C
C
Okay,
because
in
the
past
year
I
kind
of
left
it
open-ended
yeah,
and
I
think
that's
why
we
had
a
slip
on
this-
the
service
catalog
stuff,
because
we
it
was
basically
we
never
put
a
date
to
it.
You
know
we
never
had
a
release
date
or
anything
like
that.
That's
why
I
was
kind
of
curious
what
people
thought
about
that.
I
just
don't
want
to
step
on
anybody's
toes.
I.
D
C
Back
end
is
set
up
to
do
the
releases
so
anytime,
you
do
a
pull
request.
It
actually
will
do
a
release
at
that
level.
So
the
back
end
part
from
the
devops
perspective.
Is
there
it's
just
us
getting
all
the
other
pieces
pulled
together.
D
And
the
other
thing
that
we're
we
should
open
a
ticket
for
there's
two
two
things
that
we
show
tickets
for,
but
one
of
them
is
now
that
we
have
an
assass
version
of
ortillius
out
there
that
everybody
can
use.
We
need
to
have
a
ortillius
project
that
can
deploy
artilleus
out
to
people
who
want
to
have
a
local
version.
D
C
D
So
or
we
should
have
an
ortillius
project
so
if
they
want
to
have
they
want
to
install
a
local
version
out
in
their
environment,
they
can
go
to
ortillius
to
deploy
or
out
that
version
of
ortilius,
because
now
we're
going
to
have
different
component
a
lot
more
components.
So
we
need
to
define
an
artillious
deploy
project
so
that
people
can
use
artillius
to
to
push
out
a
local
version
of
ortillius.
D
And
then
I've
been
working
on.
Let
me
share
my
screen
really
quick
just
so.
This
team
knows
where
we
stand.
I've
been
working
on
a
comparison,
steve
and
I
I
should
say,
have
been
working
on
a
comparison:
dock
of
other
micros
microservice
catalogs
and
here's
kind
of
where
we
stand,
and
I
will
I'm
going
to
do
a
white
paper
and
I'll
publish
this
as
part
of
my
deploy
hip
content,
but
the
one
thing
that
we
saw
that
we
probably
could
do
fairly
easily.
D
Is
this
project
templating
and
what
that
is
is
creating.
You
know
once
you
set
up
your
mic,
if
you
have
a
microservice,
you
want
to
create
it's
going
to
go
out
and
create
your
github
repository.
It's
going
to
create
a
shell
version
of
the
microservice
is
going
to
create
a
sale
version
of
your
test
scripts,
those
kinds
of
things
and
there's
an
open
source
project
called.
D
Cookie
cookie
cutter,
which
we
could
integrate
with
pretty
easily,
and
so
we
should
probably
add
that
to
our
our.
I
think
this
is
a
it's
probably
a
fairly
low
hanging
fruit
since
cookie
cutter's
already
out
there,
because
that
was
that's.
What
that's
going
to
do.
It's
going
to
give
developers
an
even
stronger
reason
to
go
ahead
and
register
their
microservice,
because
when
they
register
their
microservice
they'll
be
at
the
same
time,
be
able
to
choose
what
template
that
they
want
to
use
and
it'll
set
up
some
stuff
for
them.
C
So
you
can
think
of
it
as
a
cookie
cutter
as
a
way
to
onboard
a
new
microservice
very
quickly,
and
if
you
look
at
the
the
premise
behind
it
is
instead
of
a
developer,
cutting
and
pasting
between
one
existing
repo
and
a
new
one
that
you
use
cookie
cutter
and
its
project
templates
to
do
all
that
work
for
you
and
it's
everything
from
saying
up
to
git
repo,
making
sure
there's
a
license
file.
There
read
me
some
basic
test
cases.
C
You
know
like
a
jenkins
file,
so
you
have
your
the
consistent
pipeline.
You
know
everything
like
that
is
what
the
the
cookie
cutter
templates
kind
of
are
working
towards,
and
it
looks
like
they
have
a
bunch
of
packages
out
there
or
temp
or
parts
of
templates
that
you
can
kind
of
string
together.
All
the
different
pieces.
Very
creatively
put
it
that
way.
D
So
I
think
this
looks
like
a
an
easy
feature
that
will
bring
a
big
impact,
so
this
would
be
what
backstage
does
backstage
doesn't
use
cookie
cutter.
They
have
their
own,
but
we
don't
need
to
write
our
own
since
cookie
cutters
out
there
and
it's
open
source.
I'm.
I
Going
to
check,
I
want
to
compare
it
because
today
there
is
something
similar
that
is
taking
a
lot
of
strongness
inside
on
the
on
the
on
the
web
developer.
I
In
some
way,
I
see
a
lot
of
that
file
putting
in
place
they
are
like
super.
There
are
valid
for,
for
example,
for
for
a
visual
studio
for
eclipse
and
you
can
instantiate
it
with
a
text
on
too.
I
Not
really,
I
don't
know
I
want
to
check
like
what
is
the
similarities,
because
I
haven't
hear
about
cookie
cutters,
but
I
feel
is
kind
of
close,
but
at
these
file
lines
I
I
look
in
that
and
everywhere
I
see
in
a
lot
of
projects,
and
I
can
see
it
is
integrated
with
a
lot
of
frameworks.
So
I
will
do
that
check.
C
Gonna,
go
ahead
and
open
an
issue
and
just
add
what
you
find
from
like
the.
I
D
Yeah-
and
we
do
have
three
kinds
of
objects-
that
we
create-
that
we
would
want
to
have
the
option
to
select
what
template
we
have
the
container,
which
is
what
we
focus
on
for
the
most
part.
And
then
we
have
just
application
files,
let's
say
somebody's
doing
salesforce
and
they
have
a
salesforce
apex
file
and
then
we
have
database
objects.
So
those
are
our
three
types
that
we
would
we'd
want
to
be
able
to
give
them
a
template
for,
but
initially
if
we
could
just
get
it
for
the
containers.
D
I
Yes,
yeah,
I
will
love
to
like
take
they.
I
would
like
to
well,
we
are
doing
a
devops,
so
I
think
at
some
point
we
are
going
to
test
a
techno
culture.
So
it's
going
to
be
nice
like
taking
a
template
from
update
file
with
text
on
into
kubernetes
yeah,
and
this
is
totally
integrated
with
the
argo
cd2.
So
yeah,
it's
a
nice
match
so
yeah
just
going
to
at
least
read
about
a
cookie
cutter.
Okay,.
C
J
C
All
right,
everybody
look
for
some
issues
to
pop
up
so
lakshmi
and
proof
just
all
the
issues
that
we
create.
We
all
put
them
in
the
ortulius
repo,
because
we
have
some
like
52
repos
or
something
like
that.
So
everything's
centralized
in
one
place
to
make
it
easy
for
you
to
to
find
things
we'll
do
pull
requests
across
repos
so
but
if
you're
looking
for
something
just
go
to
the
ortelius,
artelius
repo
and
you'll
see
what's
going
on
there
it
like.
C
I
said
we
have
to
do
some
cleanup
on
that
front,
but
that's
where
you
can
start
browsing
and
get
an
idea
of
where
to
what
you
may
be
interested
in
and
also
just
we're,
actually
pretty
good
on
our
discord
channel
so
just
drop
in
and
just
post
anything
out
there
we
get
a
lot
of,
I
would
say
it
could
be
a
random,
a
random
thought
generator.
C
Our
discord
channel
so
it'll
be
anything
from
a
new
development
that
we're
working
on
to
new
tools
that
we
found
or,
like
tracy,
said,
new
open
source
projects
that
we
need
to
look
at.
So
just
keep
an
eye
on
the
discord
and
welcome
aboard
and
happy
new
year.
Everybody.