►
From YouTube: June 9, 2022 - Ortelius Architecture
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
B
B
C
E
C
C
D
C
So
the
only
thing
that
I
really
that
I
just
want
to
kind
of
look
back
around
on
the
the
blockchain
stuff.
So
what
was
it?
Last
friday
we
ended
up
doing
an
interview
with
the
ripple
folks
utkarsh.
We
would
have
invited
you,
but
it
was
like
four
o'clock,
our
time,
which
had
been
like
some
ridiculous
early
morning
time
for
you,
but
what
I
did
was.
C
I
took
your
code
base
and
your
example
that
you
showed
us
and
just
ran
that
and
kind
of
walked
through
and
answered
some
questions,
some
basic
questions
that
they
had.
We
only
had
10
minutes,
so
it
wasn't
anything
elaborate
that
we
did
for
that
review.
C
So
I
think
they
I
think
they
had
something
like
40
project
supply
or
something
or
40,
I
wouldn't
say
open
source
projects,
but
40
folks
that
applied
for
it
and
were
narrowing
in
at
the.
I
think
we
got
a
pretty
good
chance
from
what
brian
has
told
us
and
helped
us
out
with
one
of
the
the
only
like
real
question
that
came
up
on
the
the
discussion
was.
C
So
because
I
I
showed
him
an
s-bomb
and
you
know,
s-bombs
are
going
to
get
pretty
big
here,
especially
when
folks
start
figuring
when
the
detail
starts
getting
discovered
and
recorded,
because
right
now
the
the
high
level
s-bomb
requirements
are
just
like
package
dependencies,
but
I
can
foresee
that
once
that
gets
kind
of
solved,
the
next
level
of
s-bombs
will
be
file
dependencies
that
make
up
the
package
and
those
in
all
the
commits
for
the
files
and
stuff
like
that.
C
So
s-bombs,
I
think
over
time
are
going
to
grow,
to
be
pretty
big
and
pretty
in
depth.
So
that's
one
thing:
we
just
got
to
keep
an
eye
on.
C
And
then
I
told,
and
then
I
just
brought
up
that
the
the
we
have
to
do
a
quick
budget
this
week
or
early
next
week
on
what
we'd
use
the
75k
for
and
we'll
lay
that
out.
We,
we
had
three
high
level
points,
but
they
want
a
little
more
detail
for
what
we're
going
to
do
the
development
with,
and
I
kind
of
threw
it
back
on
on
some
of
this
stuff
I
put
back
on
to
the
ripple
community
to
tell
us
you
know
this
is
our
problem.
C
What's
the
best
way
for
us
to
implement
what
we're
trying
to
do,
you
know
searching
ipfs
for
our
json.
You
know
value
in
our
json
file.
How
what
what's
going
to
be
the
best
way
to
do
that?
Those
type
of
things
so
we're
moving
along
on
that
front.
So
it
looks
pretty
good
excellent
work
on
all
that.
Utkarsh.
C
The
the
next
thing
I
had
on
my
list
was:
we
got
our
the
linux
foundation
to
pay
for
our
azure
cluster,
so
today,
at
4
p.m.
Mountain
time
we're
going
to,
I
was
able
to
get
the
the
linux
foundation.
C
It
support
to
be
able
to
join
the
meeting
and
we're
going
to
figure
out
what
permissions
we
need
to
be
able
to
stand
up.
The
new
cluster
under
the
new
subscription
in
azure,
so
brad
mccoy
is
gonna,
be
there.
I
think
adam's
gonna,
be
there
from,
I
think,
he's
from
captain
or
argo.
I
can't
remember
where
adam's
from,
but
that's
gonna
be
happening
at
4
p.m.
C
Mountain
time
today,
so
that's
nice
that
we'll
be
able
to
get
get
everything
stood
up
in
one
place
and
have
the
linux
foundation
pay
for
it
instead
of
deploy
hub.
Our
subscription
is
just
ran
out
a
couple
days
ago.
It
expired
june
3rd.
So
now
we're
at
a
pay.
As
you
go
program
with
azure,
when
we
do
that
we're
actually
gonna,
we
have
two
clusters
right
now
we
have
one
for
the
the
docs
and
the
website
and
then
one
for
the
dev
ortilla
site
and
all
the
get
op
stuff.
C
We're
gonna
combine
all
that
into
one
cluster,
just
to
save
money
on
that
front,
so
that
that
should
help
instead
of
running
multiple
clusters,
we'll
just
let
the
clusters
expand
when
they
need
to.
So
that's
kind
of
the
plan
happening
on
that
front,
and
then
I
know
brad.
When
I
talked
to
him
last
is
he
was
able
to
wrangle
up
some
more
folks
from
I
think
a
university.
C
So
we
may
have
some
more
folks
joining
from
the
university
level
that
are
interested
in
the
devops
piece
around
get
ops
and
stuff
like
that
with
ortelius
captain
argo
on
that
front,
we
just
have
one
little
brad
has
most
of
the
events
figured
out
and
with
artelias,
and
then
we
have
just
to
do
some
plumbing
pull
together
the
final
helm,
charts
pull
together
the
final
events
and
kind
of
plumb
everything
together,
so
that's
going
to
be
kind
of
like
the
the
one
of
the
focus
in
the
next
month,
or
so
that's
like
the
main
highlights.
C
I
have
anybody
else,
have
anything.
F
Yeah
steve,
so
I
was
working
on
consolidating
the
apis
that
we
talked
about
earlier
for
writing.
Artillery's
captain
services
cool
yeah.
So
there
is
this
component
com
comp
update.
So
I
see
like
a
lot
of
apis
that
I
was
not
aware,
is
used.
That
is
where
it's
taking
you
some
time.
C
Yeah,
so
what
what
we
have
is
most
of
the
apis
are
exposed
through
the
api
endpoint
or
the
ms
api
endpoints
there's
a
couple
that
the
comp
update
uses
that
are
basically
the
endpoints
that
the
front
end
hits
that
what
we
should
probably
do
is
kind
of
move
those
around
down
the
road
to
do
some
to
clean
it
up,
because
some
of
them
are
a
little
weird.
The
way
you
have
to
pass
the
data.
C
C
To
take
a
look
at
to
clean
up
and
or
extend
and
have
new
a
new
microservice
to
do
that
down
the
road.
C
Yeah,
let
me
know
which
apis
that
you
you've
run
into
that
don't
make
sense,
and
we
can
figure
out
a
plan
on
our
approach
to
either
get
them
well
documented
or
go
ahead
and
move
or
replicate
that
api
into
a
better.
You
know
basically
refactor
it.
So
it's
a
little
bit
easier
to
understand.
C
Cool
and
on
the
the
comp
update
I
do
I
on
my
to-do
list,
is
to
complete,
like
some
example,
documentation
on
how
to
use
it.
You
know
example
config
files
and
things
like
that
to
make
it
easier
for
people
to
just
go
ahead
and
drop
drop
in
a
config
file
and
start
working
with
that.
G
C
And
from
over
them
over
to
him
today,
but
yeah,
I'm
on
that
he
he
he
reached
out
to
me
and
I
said
sure
I'll
do
it
it's
at
some
bizarre
hour
like
five
in
the
morning,
I've.
B
H
H
H
Yeah
for
the
requester
movie,
we
are
using
sdo
right.
Html
service
mess
correct,
so
I
did.
I
did
the
course,
but
I
didn't
understand
a
little
bit
about
it.
Anything.
Okay,.
C
Yeah
so
there's
a
couple
ways
that
ortelius
can
run
the
current
installation
of
ortulius
into
a
kubernetes
cluster
with
all
the
microservices
is
using.
We
have
an
nginx.
C
Now,
what
we've
done
in
the
kubernetes
cluster
and
what
we
will
do
is
we'll
actually
use
a
combination
of
those
two
to
start
with,
so
we'll
use
istio
to
route
the
transactions
over
to
the
documentation
and
the
website
someone.
C
So
when
somebody
hits
the
like
docs.ortulius.io
that'll
get
routed
to
the
right
documentation
pod
through
istio,
and
then,
if
it's
like
the
the
dev
dot
ortelius.io,
then
it'll
get
routed
over
to
the
engine
x
entry
point
and
then
then
from
there
it'll
actually
go
ahead
and
still
do
the
reverse
proxy
from
from
the
engine
x
into
the
other
containers.
C
Eventually,
what
we'll
want
to
do
is
a
full
istio
implementation
around
ortilius
in
all
the
the
paths
on
that
front.
So
istio
is
a
lot
more.
Let
me
put
this
more
friendly
than
nginx
and
how
you
can
set
up
the
routing
the
internet
stuff
with
the
reverse
proxy,
can
get
pretty
bizarre.
C
I
ran
into
one
just
just
a
couple
days
ago
in
one
of
our
micro
services,
there's
a
microservice
for
retrieving
the
like
the
license
file
or
the
readme
file
in
the
python
code.
The
api
endpoint
had
a
trailing
slash
on
it
and
if
you
didn't
pass
in
from
the
front
end
the
trailing
slash,
it
would
then
go
ahead
and
reroute
the
python
code.
It
would
reroute
and
add
the
trailing
slash,
and
then
that
would
cause
this
weird
rewrite
that
was
happening
somewhere
in
one
of
the.
C
I
don't
know
if
it
was
nginx
or
if
it
was
the
front-end
load
balancer.
But
actually
what
ended
up
happening
was,
it
would
just
say
I
have
a
https
front-end,
that's
trying
to
talk
to
an
http
back-end
and
I'm
not
going
to
allow
you
to
do
that
and
the
transactions
would
fail
and
the
fix
ended
up
being
just
removing
the
slash
and
the
trailing
slash
and
the
python
code.
And
everything
worked.
C
So
yeah
the
istio
will
allow
us
to
do
better
filtering
and
you
can
have
like
a
cascading
filter.
So
if,
if
it
does,
if
you
don't
match
these,
if
you
don't
have
a
match
on
the
url
on
these
couple
or
or
the
like
the
dns
name,
then
you
can
go
to
a
default.
That's
like
kind
of
the
catch-all
which
makes
it
easier.
So
the
amount
of
coding
that
you
have
to
do
for
istio
is
so
much
smaller
than
with
with
nginx
reverse
proxy
routing.
D
D
C
C
F
Okay,
so
header-based
decisions
are
only
possible
issue.
That
is
what
you
use.
F
I'm
saying
some:
if
you,
if
you
want
to
make
any
decisions
based
on
the
headers,
then
asia
is
our
choice.
Right.
C
No,
not
not
really,
I
don't
believe
nginx
has
a
way
to
look
at
headers.
You
can
set
headers
and
you
can
rewrite
headers,
but
you
can't
interrogate
them.
F
C
So
we'll
see
what
happens
when
we
get
this
new
cluster
up
and
going
what
we
need
to
do,
and
we
may
start
looking
at
how
to
to
really
leverage
istio
at
that
level.
C
Yeah,
the
meeting
today
is
literally
just
with
the
the
I.t
folks,
so
we're
not
going
to
get
into
any
of
the
details
of
istio.
It's
going
to
be
more
like
active
directory
permissions,
and
things
like
that.
So,
if
you
can't
make
it
tonight
which
will
be
early
your
morning,
we'll
figure
out
another
time,
that's
more
convenient
for
you.
Irvine.
C
F
Yeah,
just
one
suggestion
yeah,
if
possible,
just
make
a
recording
for
that.
C
C
Right
we're
we're
pulling
for
you
to
be
a
a
speaker
at
argo
khan.
D
Be
there,
but
I'm
I'm
going
to
do
my
best.
I
will
tell
you
later
sounds
good.