►
From YouTube: Oct 28, 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
All
right,
hi
everybody-
this
is
the
october
28th
artelia's
architecture
meeting.
Let
me
drop
the
meeting
link
into
the
chat.
So
just
a
few
highlights
we
are
making
some
pretty
good
progress
with
the
service
catalog.
A
So
there's
the
the
meeting
this
evening,
my
time
with
brad
and
ahmet
and
a
few
folks
down
in
the
australian
area,
australia
area.
So
I
think,
there's
an
issue
with
some
of
the
consolidation
of
the
charts.
Hopefully
we'll
get
that
sorted
out.
A
One
of
the
things
that
we
did
add
for
working
with
artifact
hub
is
the
we
added
a
new
tag
on
the
ortelius
repo
and
one
of
the
things
that
we
found
out
for
artifact
hub
is:
you
can
use
github
pages
to
kind
of
host
the
the
all
the
the
yaml
and
the
art
of
the
artifacts
themselves?
A
So
this
is
where
we'll
be
able
to
have
basically
we're
creating
our
own
chart
museum
using
github
pages,
one
of
the
things
you'll
see.
If
we
look
at
this
code,
the
code
tree,
the
github
pages,
is
like
a
totally
separate
branch,
and
it
only
has
a
few
commits.
So
what
I
did
was,
I
had
actually
went
back
in
time
to
the
initial
commit
in
the
repo
branch
from
there.
A
So
we
had
a
minimal
number
of
files
and
that
will
allow
us
to
do
the
github
pages,
and
the
reason
for
this
is
the
way
that
the
the
get
actions
work
and
also
the
artifact,
the
artifactory.I
setup.
A
So
this
this
branch
will
never
merge
to
the
trunk
and
it
only
be
used
for
the
maintaining
the
like
this
index
at
yaml.
So
just
to
let
you
know
that
that's
out
there.
I
think
one
of
the
things
we're
running
into
an
issue
with
is
getting
this
to
be
consolidated
from
multiple
github
actions,
I'll
double
check
with
brad
and
his
his
folks
later
today,
but
that's
happening.
A
What
that's
gonna
allow
us
to
do
is
do
a
single
helm,
chart
install
so
helm,
upgrade
and
give
it
like
ortelius
and
it
will
go
through
and
do
all
of
the
you
know
find
out
where
all
the
charts
are
and
bring
them
down
and
do
all
the
work.
One
of
the
things
that
we
still
do
need
is
a
parent
helm
chart,
and
that
includes
the
the
child
home
charts.
So
if
somebody's
interested
in
taking
a
look
at
that,
I
know
it
can
be
done.
A
I
just
haven't
done
it
myself
on
how
to
do
a
parent
and
children
charts.
But
there
is
an
issue
out
here.
I
think
it's
kind
of
buried
in
one
of
the
other
ones
as
part
of
the
the
process.
A
So
that's
going
on
with
the
artifactory
and
that's
also
going
to
kind
of
play
into
how
we
set
up
like
a
shell
script,
to
go
ahead
and
curl
the
shell
strip
or
do
a
w,
get
pass
it
through
the
command
line
sh
and
go
ahead
and
download
and
install
everything
trying
to
minimize
the
number
of
commands
that
we're
going
to
utilize
at
that
level.
A
So,
if
you're
interested
in
working
with
some
helm
stuff,
there
are
issues
out
there
pertaining
to
this
there's
simple
stuff
and,
like
I
said,
there's
going
to
be,
I
would
say
it
wouldn't
be
overly
complicated,
but
some
extra
stuff
around
the
parent-child
helm,
charts
that
need
to
be
created.
Also.
I
believe
that
this
methodology
will
fit
into
our
local
development
environment.
A
So,
if
you
have
like,
if
you're
running,
like
kind
locally
or
mini
cube,
being
able
to
pull
from
artifact
hub
and
all
that
information
or
our
our
site,
the
helm
charts
will
make
it
easy
to
get
up
and
going
so
that's
one
of
the
the
speed
bumps
that
we
have
right
now
is
getting
getting
everything
streamlined.
So
it's
easy
to
get
going.
A
A
So
there's
a
flag
that
we
need
to
add
to
that.
There's
a
on
our
google
cloud
build.
We
have
to
add
the
application
version
so
deploy
hub
knows
right
now,
it's
not
consistent,
so
we
are
creating
weird
application
names
and
deploying
doing
some
extra
deployments
just
because
of
that.
So
there's
this
couple
lines
that
we
need
to
put
into
the
google
cloud
build
files.
A
Some
other
things
we
have
argo
stood
up,
kept
and
stood
up
and
sasha
has
a
pretty
good
some
good
movement
on
the
the
diagram
for
our
ci.
I
get
ops
process.
Let
me
see
if
I
have
it
here
locally.
I
was
downloading
it
yesterday.
A
So
this
is
a
work
in
progress
and
we
are
including
this
into
the
the
dock.
This
is
like
the
dev
stage
of
the
process
laying
out
the
steps
who's
doing
what
as
part
of
that
process.
So
it's
it's
coming
together,
really
nice.
This,
like
I
said
this-
is
the
dev
level
and
then
there'll
be
another
page.
That's
pretty
close
to
this.
That
will
be
for
like
a
qa
environment
and
then
for
production.
A
So
look
for
this.
I
saw
sasha
had
some
questions
about
updating
the
doc
he's
having
some
problems
with
this
hugo
server.
So
but
this
will
be
part
of
the
the
documentation,
this
diagram,
which
would
be
nice
to
give
a
visual
representation
of
of
our
the
proposed
git
ops
process
with
ortilius
as
part
of
it.
A
A
So
that's
kind
of
hap,
that's
kind
of
exciting
to
have
that
happening
there
and
then
lukas.
You
want
to
give
an
update
on
how
captain's
going.
B
Yes,
steve,
so
basically
I
was
looking
into
like
what
we
can.
You
know
develop
using
captain
apis.
So
basically
I
was
looking
at
control
plane
api,
so,
like
captain
says
all
the
apis,
that
is,
you
know,
required
for
getting
every
meta
meta
information
from
the
captain
context.
B
So
there
are
like
quite
a
lot
of
aps
that
we
can
leverage
to
get
every
minute
information,
so
currently,
I'm
playing
around
with
all
those
you
know
apis
and
also
I
tried
with
the
multi-repository
application
so
like
I
tried
with
the
application
that
has
three
repositories
so
yeah,
I'm
like
playing
around
with
with
these
applications.
A
Nice
in
it
are
those
when
you
they're,
called
captain
calls
them
microservices
right
that
you
write
as
as
their
plugin.
B
B
C
B
B
Yeah
so
like
once,
our
poc
document
is
finished,
so
we
can,
you
know,
start
like
start
on
particular
use
cases,
so
that
would
be
much
easier
to
work
on.
A
A
Yeah
cuz
we'll
be
because
one
of
the
things
that
we
added
to
the
diagram
was
for
each
step,
what
it's
gonna
kind
of
like
what
what
event
it's
going
to,
listen
for
once
it
gets
once
that
event
triggers
it.
What
it's
going
to
do
and
then
it's
going
to
send
a
complete
that
it
you
know
completed
it
from
that
was
my
understanding.
A
It
kind
of
captain
kind
of
has
this
what
you're
going
to
listen
for
and
then
I
I
believe
you
could
also
add
in
additional
events,
saying
that,
like
you,
started
you're
in
the
process
of
doing
this
and
then
finish
it.
So
you
like
from
my
understanding,
has
some
pretty
fine
grain
event
statuses.
So
you
can
kind
of
really
track
where
things
are
are
moving
along.
B
A
Right
and
the
other
question
that
came
up,
I
think
it
was
yesterday
or
day
before
when
sasha
and
myself
in
usual,
were
talking
was,
if
you
have
a
let's
say,
you're
going
through
this
process
for
a
a
shared
component
and
you
deploy
argo.
You
know
you
go
out
and
deploy
that
shared
component
to
your
dev
cluster,
that
all
the
applications
that
consume
that
should
start
their
quality
gate
off
to
you
know,
check
and
run
their
quality
gate
against
that
new
version
of
the
the
shared
component.
A
So
there
was
a
question
that
came
up
around
being
able
to
broadcast
a
deployment
across
multiple,
basically
slo
files
for
kept
in,
and
so
that
was
one
thing
that
we
may
need
to
look
at
down.
The
road
is
is
being
able
to
tell
you
know:
we've
we've
done,
you
know,
captains
monitoring,
you
know
or
are
looking
at
five
applications,
and
we
want
to
tell
those
five
applications
from
a
single
point
of
of
the
deployment
process.
A
A
So
that's
moving
along
I'm
trying
to
think
some
other
things
that
we
will
be.
I
haven't
really
come
up
with
a
term
for
it
yet
tracy.
What
are
we
going
to
call
the
the
the
services
like
the
restful
api
relationships?
Did
we
come
up
with
a
name
for
that?
I
can't
remember.
A
Yeah,
so
one
of
the
things
that
you
could
call
it
supply
chain.
A
So
one
of
the
things
that
I
have
started
working
on
on
the
deploy
hub
side
was
to
bring
in
in
this.
This
is
where
we'll
need
plugins
for
lack
of
a
better
word.
A
So
what
we
have
is,
you
know
like
in
a
swagger
file.
The
swagger
file
is
going
to
give
you
all
the
restful
api
endpoints
for
a
service,
so
that
will
allow
us
to
look
at
a
swagger
file
and
say
these
are
all
the
restful
apis
that
this
service
produces.
So
basically,
we
know
the
verb.
If
it's
a
post
or
get,
we
know
the
url
and
we
know
which
component
version
is
producing
those.
So
that's
one
side
of
the
the
the
equation.
So
that's
like
the
the
producing
of
the
restful
apis.
A
A
A
So
we
can
figure
out
what
that
that
service
is
consuming
so
and
then
that
just
gets
spit
out
into
a
json
file.
Now
what
this
allows
us
to
do
is
map
producers
to
consumers,
and
then,
if
you
have,
you
know,
microservice
a
calls
b,
which
calls
c,
which
calls
z.
We
can
follow
that
path
all
the
way
across
through
and
map
it
all
out
at
that
level.
So
that's
something
once
we
get
the
service
catalog
out
that
we'll
need
to
take
a
look
at.
A
And
I
think
it
may
not
be
too
bad.
You
know,
there's
a
limited
number
of
methods
that
can
be
used
to
go
in
and
make
the
restful
api
calls.
You
know,
there's
there's
gonna
be
a
handful
for
python
and
java.
There's
gonna
be
a
couple
especially
like
if
you're
in
a
swing
boot
world
you're
going
to
have
certain
standard
methods
to
make
the
the
wrestle
api
calls.
So
that's
something
that
we'll
need
to
look
at
down
the
road
to
bring
in
this.
The
producers
and
consumers
world.
A
So
that's
one
thing
that
is
going
to
be
very
exciting:
we've
had
a
several
companies
start
talking
about
how
they
want
to
map
out
their
restful
api
calls
now.
The
other
thing
that
we'll
need
to
look
at
as
well
is
not
only
restful.
Api
calls,
but
also
like
a
pub
sub
methods.
Grcp.
A
Those
type
of
things
down
the
road,
but
we'll
start
with
rest
since
swagger
is
easy
to
parse
and
the
reason
why
we're
doing
this
up
front
versus
looking
at
open
telemetry
is
we
want
to
gather
this
information
ahead
of
time.
So
we
can
tell
you
like
an
sre.
Here.
Is
a
change
coming
down
the
pipeline?
A
A
I
think
that
was
basically
what
I
had
on
my
list
for
today.
Anybody
else
have
anything.
Did
I
miss
anything.
A
We
kind
of
did
with
hacktoberfest.
We
have
a
couple
low,
frank
and
low
hanging
fruit
issues
out
there
that
we
just
need
to
take
off
get
those
wrapped
up.
A
And
if
you're
looking
for
any
issues
that
you
want
to
get
some
credit
for
hacktoberfest,
just
ping
me
on
discord,
and
I
can
point
you
into
the
issue
and
help
you
through
it.
A
Alrighty
well,
thank
you
everybody
for
joining
today
and
we
will,
if
you're
interested
and
if
you're
awake,
we
will
have
the
get
ops
meeting
with
myself
and
the
folks
in
australia,
4
30
p.m.
My
time
8
30
a.m,
sydney
time
and
also,
I
believe,
brad-
is
doing
some
off
a
different
schedule
to
as
well
to
help
accommodate
everybody.