►
From YouTube: Nov 11, 2001 - 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
A
So,
just
to
get
started
on
the
service
catalog,
just
we
are
trying
to
wrap
that
up.
It's
looking
pretty
good.
I
we
did
find
one
bad.
I
won't
say
bad
query,
but
a
a
slow
query
that
we
need
to
rework.
A
It
makes
it
appear
like
the
service
catalog
screen
kind
of
like
hangs,
but
it's
actually
doing
work
on
the
back
end.
So
I'm
gonna
take
a
look
at
that
and
rework
that
query
a
little
bit
to
improve
their
performance
and
then
it
looks
like
if
anybody's
looking
for
some
smaller
pull
requests
and
changes
to
do.
A
There's
a
couple
around
the
cloud
bill,
app
updates
that
need
to
be
done
for
the
microservices
and
we
may
have
some
additional
changes
for
the
helm,
charts
coming
up
and
maybe
some
github
actions
I'll
know
more
tonight
when
I
meet
with
the
get
ops
folks
and
what
they're
doing
down
in
australia,
they're
trying
to
figure
out
the
how
we
need
to
manage
the
charts
because
we're
a
polyrepo
and
the
charts
are
spread
out
across
multiple
repositories
that
consolidating
them
and
getting
them
in
a
position.
A
Update
site
has
been
a
little
bit
of
a
challenge,
some
of
the
tools
out
there
don't
quite
do
what
we
do,
but
I
think,
looking
at
the
prs
that
have
been
coming
through,
I
think
they've
figured
something
out,
or
at
least
they're
trying
something
so
that
will
so
the
the
cloud
built
app
version
updates.
There's
an
issue
out
there.
If
you
look
in
the
bertillous
arterios
repo
you'll
see
something
about
the
app
version.
It's
a
couple
lines
of
code
that
need
to
be
inserted
into
the
cloud
build
dml
files.
A
So,
if
you're
looking
for
some
easy
prs
to
get
started,
that's
where
I
would
look
with
that
being
said.
One
of
the
things
that
this
is
going
to
allow
us
to
do
is
to
have
a
single
command,
so
it
will
be
a
basically
it'll
be
like
I
can't
remember.
It's
called.
I
think
it's
called
a
a
a
parent
and
subcharts.
A
So
if
we
could
spell
helm
will
have
a
parent
chart
for
what
we
would
call
like
the
the
distributable
application
for
the
ortilius
itself.
A
And
what
this
is
gonna,
this
will
be
nice
once
we
get
it
sorted
out,
so
we'll
be
able
to
have
a
single
command
line
script.
Usually
I
know
you
brought
this
up
about.
Having
like
a
single
script
to
do
the
install
the
the
commands
that
we're
gonna
need
to
execute
are
gonna,
be
like,
like
a
home
repo
ad,
a
helm,
repo
update
and
then
the
helm
install
with
the
chard.
A
Do
you
think
we
still
need
a
shell
script
to
wrap
those
three
commands
or
just
documenting
him
would
be
easy
enough.
C
So
I
think
if
we
want
to
install
all
the
helm
charts
at
once,
then
a
script
would
help,
because
you
don't
have
to
do
individual
updates
for
each
application.
But
if
you're
just
updating
a
service
of
an
already
installed
environment,
then
that's
a
different
story
right.
You
don't
need
a
script
for
that.
A
Okay,
and
do
you
think
I
know,
there's
a
big
debate
where
you
kind
of
like
do
a
a
curl
and
then
or
w
get,
and
I
think
it's
mostly
curl,
then
you
pipe
it
through
shell.
Do
you
think
something
like
that?
Would
curl
the
shell
script.
C
Yeah,
if
we
have
a
shell
script
and
if
it
is
in
github,
then
doing
a
w
get
on
on
the
and
piping.
The
shell
script
will
make
a
single
line.
Installation.
A
C
A
Okay
and
I
believe,
since
we're
using
helm
that
will
be
able
to
install
into
a
local
environment
like
kind
or
like
mini
cube.
Does
anybody
know
that
answer
if
you
can
use
helm
against
kind,
a
kind
cluster.
A
A
Are
there
any
other
local
development
environments
that
I'm
I'm
missing,
that
we
need
to
focus
on.
B
A
A
What
about
is
the.
A
On
windows,
I
don't
run
windows
so
but
on
windows.
Is
there
like
a
docker
desktop
and
does
that
have
kubernetes
kind
of
built
into
it?.
A
All
right
we'll
take
a
look
at
those
those
three
to
make
sure
that
we
have,
because
I
know
like
with
kind
that
need
to
open
up
certain
ports.
Mini
cube,
uses
a
different
port
forwarding,
and
I
I
have
no
idea
about
the
the
docker
desktop
for
windows,
how
you
get
it
you
know
into
it
on
a
totally
separate.
A
Oh,
it's
kind
of
related.
We
will
need
to
figure
out
a
developer
environment
to
be
able
to
run.
You
know
a
set
of
since
we
have
we're
not
that
big
yet,
but
we're
gonna
get
we're
gonna.
You
know
keep
on
adding
to
this
and
we're
gonna
grow,
pretty
quick
to
be
able
to
have,
let's
say
our
10
micro
services
running
in
the
cluster
and
then
being
able
to
debug
one
of
them
outside
of
the
cluster
and
have
all
the
traffic
kind
of
routed
correctly.
So
you're
still
using
the
the
correct
database.
A
You
know
it's
all
shared
data,
but
you're
able
to
be
like
stepping
through
python
code
in
visual
studio.
So
I
think
that's
going
to
be
one
thing:
we're
going
to
have
to
look
at
how
to
set
that
up.
I
have
a
couple
ideas.
A
So
the
get
ops,
it's
kind
of
overlapping
a
little
bit,
because
the
get
ops
part
needs
the
the
helm,
charts
kind
of
organized,
and
so
we
have
or
basically
we
have
overlap
between
how
we,
how
we're
going
to
distribute
along
with
the
get
ops
piece.
So
I
think,
once
we
kind
of
flush
that
out
things
will
start
picking
up
pretty
quick.
A
I
believe
food
course
is
working
on
some
captain
events
along
with
brad,
amit
and
ben
around
the
argo
cd,
and
I
think
carson
might
be
working
on
the
argo
piece
as
well.
Sasha
did
put
together
his
diagram,
we're
in
the
process
of
getting
that
placed
into
the
documentation,
so
we
can
kind
of
show
people
the
the
steps
that
we're
going
through
we're
going
to
market
this
for
proposed.
A
So
we've
gone:
I've
gone
through
a
couple
iterations
with
sasha
on
this,
and
we
finally
got
it
close
enough,
so
we
could
start
breaking
out
and
taking
a
look
at
the
different
steps.
So
you'll
see
a
bunch
of
tabs
out
here
this
the
draw.io
is
out
in
the
google
shared
drive.
A
A
And
we've
added
on
our
our
developers,
so
we
have
our
cat
with
our
fish
and
our
dog
with
our
sausages
and
some
beer,
typical
developer,
being
able
to
check
in
and
kick
off
the
whole
process.
It's
this.
This
whole
get
ops
process
is
surprisingly
over
complicated
just
to
just
the
the
whole
git
flow,
and
things
like
that.
I
I
I
get.
A
I
understand
why
people
are
are
interested
in
it
because
they
think
it's
going
to
solve
the
a
lot
of
problems,
but
there's
a
lot
of
moving
parts
that
end
up
happening
in
this
process
so,
but
I
think
we
can
make
it
work
with
ortulius
and
argo
and
captain
to
be
able
to
get
the
a
good
story
out
there.
A
I
know
that
it's
a
big
interest
to
people
and
what
we're
looking
at
here
is
this:
the
flow
for
the
ci
environment
when
we
get
up
to
qa
and
production,
the
diagram
slightly
changes,
because
of
where
you
do
your
last
image
build.
Basically,
you
have
to
decide
and
your
git
flow.
You
know
how
you're
going
to
get
out
of
get
out
of
the
development
world
and
into
the
higher
level
pipeline
process,
but
this
this
this
diagram.
A
We
figured
out
how
to
create
it
as
html
and
we'll
be
incorporating
in
into
the
dock
without
losing
any
of
the
animation,
which
would
be
nice.
Some
new
stuff,
the
the
supply
chain
management,
is
picking
up.
Speed.
A
So
part
of
the
supply
chain
has
to
do
with
dependency
management,
tracking
dependencies
and
those
pieces
now
they're
looking
at
the
supply
chain
from
like
a
single
mpm
package
or
python
module,
but
they
have
not
looked
at
how
to
roll
it
up,
like
ortelius,
does
going
from
the
lower
level
components
rolling
up
into
an
application
view,
so
we'll
be
getting
some
more
information
about
that.
It's,
like
I
said
it's
a
new
organization.
A
So
it's
going
to
be
another
one
of
those
where
we're
going
to
have
overlap
like
where
we
have
overlap
with
kept
in,
which
is
part
of
the
cncf
argo,
which
is
kind
of
cncf
cdf
part
of
the
world.
So
just
to
give
you
a
heads
up,
that
will
be
something
that
we'll
need
to
take
a
look
at
down
the
road
anybody
else
anything
I
miss.
A
A
No
because
this
is
the
architecture,
but
I
can
talk
about
the.
A
Yep,
so
if
you're
part
of
the
google
groups,
you
would
have
received
an
email
to
join
up
another
like
open
source
platform
for
doing
the
voting
and
it'll
give
you
this
authentication
like
key.
You
can,
because
we
have,
I
think,
three
different
votes
out
there
that
need
to
happen.
What
will
happen,
at
least
for
me.
I
had
to
go
in
and
use
the
same
authentication
key
three
separate
times
to
get
to
the
polls,
but
just
keep
a
eye
out
at
that
level.
E
A
Okay,
just
curious,
so
go
ahead
and
vote
and
we'll
get
that
wrapped
up.
I
think
it
it's
gonna
run
through
the
24th.
It
closes
two
weeks.
B
A
Okay
and
a
reminder
for
those
of
the
you
doing,
presentations
for
the
visionary
summit
december,
8th
reach
out
to
tracy
to
get
a
time
to
record,
and
if
you
need
help
on
getting
the
presentation
pulled
together,
we
can.
We
can
do
that
as
well.
C
Yep
tracy
I'll
reach
out
to
you
next
week.
This
is
usual
this
week,
I'm
a
bit.
E
Yeah
no
problem
and
I'll
get
your.
The
press
release
is
on
my
list.
C
Other
thing
is,
we
are
getting
a
new
project
started
on
our
end.
It's
a
it's
in
a
very
beginning,
phase
we're
getting
people
on
board
and
stuff,
but
this
is
a
new
monolith
to
microservices
transformation.
C
So
I
want
to
kind
of
introduce
cortelius
like
in
a
couple
of
months
there,
so
we
were
able
to
internally
set
up
ortilius
and
get
the
url
working
and
everything,
but
I
need
little
help
in
kind
of
loading,
the
data
in
our
environment
and
to
learn
more
about
the
functionality
and
the
api.
So
I
need
a
bit
of
help
from
you
to
get
going
on
the
autilia
side.
From
our
end,.
A
Okay,
what
is
for
this
new
project?
What
are
you
using
for
the
ci
cd
orchestration?
It's
gonna
be
like
jenkins
or
captain.
Yes,.
C
No,
they
already
have
a
lot
of
customers
have
a
mature
ci
process
because
they
are
going
into
kubernetes.
I
need
to
increa
integrate
their
cei
into
a
into
a
githubs
process,
so
our
poc
would
be
primarily
using
using
captain
and
argo
for
the
just
the
deployment
of
microservices
into
kubernetes
environment,
where
we
will
not
be
doing
the
ci
through
kept
in,
because
that
complicates
things
a
lot.
Usually
most
of
the
companies
have
have
a
mature
ci
where
they
have
security
and
build
process
and
integrated.
C
We
just
need
to
add
a
docker
registry
into
their
ci
environment
to
push
the
docker
images,
but
gitops
is
something
that
we
want
to
implement
from
the
deployment
side.
Only.
A
Okay,
yeah
so
we'll
have
to
when
you
introduce
the
the
docker
registry
piece
on
the
jenkins
side,
there
will
be
you'll
need
to
add
in
the
artillious
cli
call
to
create
in
the
ortus
world
of
components
so
and
then
on
the
deployment
side.
A
That's
where
we
would
be
working
with
captain
to
trigger
the
get
ops
process.
Yeah.
C
Yes,
so
I
I'll
connect
with
utkarsh
also
next
week,
just
to
kind
of
get
an
update
on
on
the
developments
of
kept
inside,
but
primarily
what
our
poc
is
to
enable
ortelius.
With
with
like
a
couple
of
three
or
four
dummy
services,
and
we
are
using
github
gitlab
ci
to
to
build
those
services
and
push
to
aka
ak
acr,
which
is
which
will
be
our
registry
and
from
there
we'll
be
pulling
in
using
captain
and
argo
cd.
C
But
primarily,
I
need
some
help
with
ortelius
data
loading
and
and
additional
things.
Additional
features
that
we
might
not
be
familiar
with.
Yet.
A
Okay,
no
problem,
and
I
was
going
to
ask
you
one
more
question
now:
it
slips
in
my
mind.
A
On
the
repository
side,
are
you
going
to
have
move
to
poly
repos,
or
are
you
going
to
have
a
mono
repo
still.
C
A
Okay,
all
right,
it's
just
how
the
a
lot
of
the
triggers
happen
on
what
you're
gonna
scan
and
things
like
that.
So
both
argo
and
captain
can
deal
with
that.
It's
just
how
you
do
this
setup.
C
A
Yeah
because
that's
like
what
we
have
with
artelias
is
we
have
our
we're
in
the
hybrid
world
right
now,
so
we
have
our
mono
repository
and
then
we
have
our
new
microservices
that
are
in
in
their
own
repositories.
So.
C
Yeah
yeah,
when,
when
we
are
going
through
the
digital
transformation
developers
will
be
peeling
off
services
and
putting
into
poly
repos
and
and
then
there
will
be
a
big
mono
report
that
has
an
existing
stack.
That
is
already
in
production
right.
A
All
right,
it
looks
like
we
have
a
couple
new
guests:
alper.
Can
you
just
introduce
yourself.
G
Hello,
I
sorry
I'm
in
a
stairwell
right
now,
hello,
I'm
from
turkey
and
I'm
a
university
student
working
on
computer
engineering
and
I'm
interested
in
data
science.
So
I
was
just
joining
and
see
what
was
going
on
with
these
kinds
of
meetings.
E
Yes
and
alper
is
interested.
You
know
I
recruited
him
through
his
brother.
He
is
studying
data
science
and
I
am
encouraging
him
to
sort
of
take
the
at
least
take
an
interest
and
a
focus
on
our
graphs,
our
existing
reports
and
then
start
learning
our
data
to
see
what
kind
of
predictive
reporting
we
can
do.
A
Perfect
welcome
aboard
once
once
we
wrap
up
our
service
catalog
here,
hopefully
the
next
week
or
two
that
we'll
be
able
to
get
focused
on
some
new
topics
like
we're
talking
about
like
the
supply
chain
management,
get
ops
and
when
we
do
start
doing
that,
we're
going
to
be
bringing
in
a
lot
more
data.
A
The
interesting
thing
with
what
we
are
focusing
on
right
now
is
our
data
sets
aren't
huge,
but
we
do
have
very
complex
relationships
that
end
up
being
tracked,
so
you're
not
going
to
be
like
chugging
through
a
terabyte
of
data,
but
you
may
end
up
having
to
deal
with
a
million
relationships
and
how
how
those
are
associated
together.
A
So
we're
going
to
give
you
a
different
slant
on
data
from
our
our
side
of
things
and
some
of
the
things
that
long
term
that
we've
always
talked
about
with
ortillius
is
being
able
to
manage
and
track
the
relationships
at
the
open
source
or
like
the
real
high
level
world
of
of
things.
So
let's
say
we
we
we
recognize
through
our
like
at
the
component
level.
We
know
this
is
this:
docker
image
is
based
on
python
and
it
includes
a
let's
say,
the
the
curl
pearl.
A
I'm
sorry
python
library
now,
if
somebody
goes
out
and
updates,
makes
a
fix
to
the
to
the
curl
library
for
python
that
we
should
be
able
to
broadcast
out
across
the
whole
world
to
everybody,
that's
consuming
it
and
tell
them
that
they
have
to
go
in
and
update
a
new
version
or
you
know,
rebuild
their
their
docker
images.
A
So
this
whole
concept
of
being
able
to
understand
who's
using
what
across
the
whole
world
is.
It
is
like
kind
of
a
vision,
I'd
like
to
kind
of
keep
in
the
back
of
her
mind
to
be
able
to
provide
that
in
visibility
for
everybody.
So
everyone
knows
what's
what's
happening
because
that's
part
of
the
supply
chain
concept
is
you
know
where
something
where
the
the
the
source
of
truth
is
for
the
actual
source
code
that
has
been
certified
and
then
who's
consuming
it
and
how
much
drift
there
is.
A
Has
anybody
heard
of
we?
I'm
gonna
run
over
like
by
two
minutes
here.
If
everybody's
okay
drop
off,
if
you
need
to
there
when
I
was
at
the
linux
foundation
member
summit
last
week,
there
was
an
interesting
concept
that
came
up
around
packages
and
package
dependencies.
It's
called
libyars.
A
A
So,
like
I
said
in
my
example,
I
I'm
relying
on
the
python
curl
module
and
that's
going
to
be
version
5.1,
let's
say,
and
that
was
created
six
months
ago
and
now
the
current
version
is
5.5,
so
my
container
has
drifted
by
five
releases
and
there's
a
time
period
between
the
current
release
and
my
the
release
that
I'm
using
that's
called
libyars,
and
what
it's
trying
to
do
is
to
point
out
and
find
libraries
that
you
are
aren't
updating
and
that
it
could
have
potential
drift
as
part
of
that
process.
A
So
it's
the
interesting
way
to
look
at
drift
by
seeing
how
old
you
are
compared
to
the
current
version.
So
just
think
about
that
as
a
another
way
of
viewing
dependencies.
D
Yeah
so
last
week
aisha
shared
the
document
like
the
architecture
document
for
the
macro,
my
migration
to
microservices.
So
I
guess
I
mentioned
some
comments
and
also
also
there
were
some
comments,
some
other
guys,
so
we're
going
to
have
a
meeting
to
discuss
this
out.
A
Yes,
what
we'll
need
to
do
is,
do
you
wanted
to
schedule?
I
think
we
should
just
schedule
a
one-off
or
a
couple
off
meetings
on
that.
A
I
I
would
say
next
week
crumb
this
same
time:
let's
go
ahead
and
schedule
something
for
that.
A
Next
thursday,
are
you
is
your
week
freeing
up
better
at
the
end
of
the
week.
C
Yes
depends
on
the
time
they
have
couple
of
I'll.
Send
you
my
schedule,
steve
okay,.
A
Yeah,
let's
so
chrome,
let's
shoot
for
next
thursday.
D
A
We'll
figure
out
calendars
and
get
that
out
there,
because
I
think,
having
a
couple
people
take
an
eye
look
at.
It
will
help.
D
Yeah
better,
like
more
of
the
minds
more,
is
the
problem
to
solve.
A
Exactly
alrighty
I'll
touch
base
with
you
over
discord
and
we'll
figure
out
a
time.
A
All
right,
I
did
just
a
side
note.
I
did
create
a
discord
channel
for
call
for
papers
for
cdcon
in
spain
coming
up
in
the
springtime,
and
I
have
to
I'm
gonna,
throw
out
there
a
couple
more
ideas.