►
From YouTube: Nov 10, 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).
A
B
Welcome
everybody
to
November
10th,
artillius
architecture
meeting
the
main
thing
that
I
want
to
go
over
is
where
we
stand
on
some
of
the
issues
for
the
blockchain
and
then
also
on
the
CLI
tutorial
portion
as
well.
Actually,
let
me
start
with
the
CLI
tutorial.
Let
me
try
to
share
my
screen.
B
B
B
So
with
this
information
we'll
be
able
to
gather
everything
that
we
need
to
take
the
information
from
the
CI
proportion
and
the
CD
portion
and
push
it
into
artillius
so
that
documentation
is
going
to
be
out
there.
What
we'll
need
to
do
is
to
have
folks
test
it
and
then
make
sure
that
we
clean
up
anything
that
isn't
clear
and
then
also
we
will
once
we're
happy
with
it
at
that.
That
point,
then
we'll
go
ahead
and
do
a
video
tutorial
around
it.
B
B
So
the
goal
on
that
front
is
to
kind
of
help
ease
the
onboarding
portion,
so
Sasha
I
know
you
wanted
to
kind
of
look
at
that
for
one
year
talks
at
your
company
coming
up
so
that
documentation
will
be
out
there
for
you
to
kind
of
follow
along
with
and
we
did
not
put
into
the
documentation.
Anything
specific
to
say
like
this
is
how
you
do
it
Jenkins.
This
is
how
you
do
it
with
GitHub
actions.
B
On
that
front,
we
try
to
leave
it
a
little
more
generic
if
it.
If
we
do
need
to
add
you
know,
tool
specific
pieces
if
it
makes
more
sense
to
make
it
easier
to
follow
just
creating
the
issue
and
we'll
go
ahead
and
address
it.
So
just
create
an
issue,
so
we
don't
forget
about
it.
B
The
other
portion
that
we
have
is,
let's
take
a
look
where
we're
at
with
our
blockchain
pieces.
Any
questions
on
that
front.
B
C
A
I
was
just
thinking
so
like
for
the
view
of
the
organization
there.
They
have
like
cd
part
separate
between
CA,
but
they
are
great
so,
but
you
said
like
this
will
require,
like
all
the
CDN
CI
information
for
onboarding,
your
application
or
tedious
right.
B
Right,
so
what
we
want
to
do
so
it's
basically
two
steps.
The
first
step
is
the
CI
integration
which
we
are
able
to
derive
a
bunch
of
metrics
and
information
from
the
git
repo
at
that
level.
B
So
that's
like
one
of,
and
that's
also
where
you
kind
of
like
register
your
your
new
component
version
at
that
point
at
the
when
it's
created.
Also
in
the
example,
we
associate
the
component
version
with
an
application
version,
so
those
dependency
relationships
created.
So
that's
like
the
first
step
is
the
the
information
gathering
phase.
B
Also,
we
included
sift
for
the
fs
bomb
at
that
level.
So
you
get
a
nice.
You
know
full
picture
of
every
all
your
dependencies
for
your
Docker
image,
for
example.
At
that
level,
the
second
portion
is
when
you
do
a
deployment,
we
want
to
record
what
was
deployed
where
so-
and
this
is
a
little
bit
harder
to
do
in
without
a
a
pipeline
tool,
so
we
need
to
to
kind
of
figure
out
how
we
want
to
take
people
down
that
Journey.
B
But
basically
what
happens
is
you
just
say
all
right,
I
just
deployed
this
service
over
to
this
cluster.
One
and
completed
I'm
going
to
record
that
it
went
to
this
environment
inside
of
ortelius.
So
it's
more
of
a
logging
step
that
we
put
in
as
part
of
that
and
the
stuff
that
Brad's
been
working
on.
I.
Think
of
course,
you're
doing
some
of
it
around
the
the
I
think
it
was
the
Argo
Notifier.
B
That
we
may
need
to
expand
an
end
point
on
our
on
the
artillery
side
to
capture
that
notification.
Coming
from
like
an
Argo
CD
that
a
deployment
was
completed,
but
that's
kind
of
like
secondary.
B
The
main
thing
we
need
to
look
at
is
just
testing
out
the
primary
piece,
which
is
the
the
CI
integration
right
now.
Does
that
help
put
it
into.
B
So
on
the
blockchain
piece,
I've
been
traveling
the
last
two
weeks,
so
I
haven't
been
able
to
to
really
keep
things
moving
along.
But
let
me.
B
Filter
by
that
I
did
meet
with
just
before
this
meeting
a
I
think
his
name
is
Nikita,
he
is
from
Ukraine
and
he
is
his.
B
He
works
with
doing
ux
UI
design,
so
I
talked
to
him
about
how
we
can
leverage
his
talents
for
Designing
out
how
he
can
visualize
the
blockchain
at
that
level.
So
I
have
on
my.
My
to-do
list
is
to
create
a
couple
more
issues
around
possibilities
of
some
thoughts
on
creating
a
ux
extending
our
ux
to
make
it
more
easier
to
navigate
because
I
think
with
the
blockchain
piece
and
The
Ledger
we're
going
to
have
more
information.
That's
going
to
be
persisted
over
time.
B
So
we'll
need
to
do
like
a
time
scale
of
a
component
and
some
things
like
that
around
the
the
visualization
of
the
data
and
the
on
the
back
end
side.
B
Some
of
the
things
that
we
need
to
kind
of
look
at
is
looks
like
everybody,
for
hacktoberfest
got
their
pieces
in
place
around
the
nft
storage
of
the
the
data
from
the
s-bomb.
So
the
next
thing
we
need
to
do
is
to
kind
of
normalize
the
data.
B
So
this
is
the
one
where
we
need
to
kind
of
take
a
look
at
the
the
this,
the
s-bomb
and
transform
it
so
like
we
were
talking
about
the
the
licenses,
for
example,
that
license
is
piece
of
the
of
the
blockchain
needs
to
be
transformed.
So
we
then,
instead
of
pointing
to
the
license
itself.
B
It
points
to
the
nft
I
mean
the
Sid,
that's
out
on
the
out
on
the
nft
storage,
so
that
was
one
of
those
things
that
we
need
to
to
follow
up
with
and
I.
Think
that's
going
to
be.
The
one
of
the
next
steps
that
we
need
to
accomplish
is
to
get
this
transformation
in
place
and
I
can't
remember
who
who's
perfect
believer.
B
B
So
we'll
have
to
follow
up
with
him
to
see
where
he's
where
he's
at
on
this,
what
we'll
need
to
do
is
now
that
we
have
the
the
nft
storage
kind
of
figured
out.
What
we
should
be
able
to
do
is
take
an
s-bomb
transform
it.
B
So
we
can
have
it
kind
of
you
know,
minimized
or
compacted
around
the
the
data
and
then
be
able
to
take
that
put
it
into
put
and
pull
push
it
into
the
nft
storage,
and
then
the
the
test
result
will
be
able
to
pull
it
back
out
and
compare
that
we
got
the
same
results
at
that
level.
So
those
will
be
the
the
like.
The
next
steps
that
we
have
now
the
same
thing
we'll
need
to
do
for
component
versions
and
application
version
start
building
out
the
nft
pieces.
B
For
that
I
will
add
those
issues,
so
we
can
start
working
on
what
we
need
to
how
we
need
to
transform
those
pieces
as
well
and
then
from
there
I
think
that's
going
to
be
once
we
get
those
three
pieces
like
in
place.
B
We
should
be
pretty
good
to
go
to
start
adding
into
the
the
blockchain
our
transactions,
because
what
we
want
to
make
sure
is
that
we
have
a
clean
data
going
into
nft
storage.
Before
we
start
adding.
You
know
garbage
into
the
blockchain
on
that
front.
Does
that
sound
like
a
reasonable
approach,
foreign.
B
I'm
still
I'm
going
to
be
in
California
through
the
end
of
the
week
and
I
will
start
working
on
those
issues.
I'll
create
issues
around
the
ux
UI
front.
B
Also,
extending
the
Json
transformation
include
component
versions,
application
versions
and
then
I'll
try
to
get
her
get
a
hold
of
debit
on
and
see
where
he's
at
on
the
the
transformation
piece
that
he
was
working
on.
The
other
piece
is
another
person's
working
on
loading
in
the
I
think
it
was
the
licenses.
B
And
then
we
had
another
one
to
load
in
here.
It
is,
let
me
tag
it
with
the.
It
is
496
that
we
need
to
also
do
the
load
into
the
orango
DB
portion,
the
cve
database.
B
And
I
think
there
was
a
you
did
some
work
on
the
arango
DB
right.
A
A
C
A
I
think
Joseph
also
ordered
some
milk.
B
B
Okay,
perfect,
so
it's
tagged
correctly,
all
right
yeah,
so
that
the
that
one
we
may
want
to
it
kind
of
goes
with
530
as
well
on
how
we
can
start
indexing
the
issues,
so
5
30
is
kind
of
flipping
the
the
data
upside
down.
B
So
what
my
thought
process
was
we'd
add
in
some
some
of
the
key
basically
create
like
a
key
an
index
based
on
portions
of
the
s-bomb
that
we
want
to
search
as
well
as
some
of
the
data
from
the
component
version
application
version
that
we
want
to
search.
Add
that
into
a
rainbow.
That
would
then
allow
us
to
go
ahead
and
point
over
to
the
blockchain
and
nfts.
It's
going
to
be.
That's
gonna
be
a
one
that
we
gotta
really
think
through
to
make
sure
we
can
navigate
the
data
correctly.
B
B
All
right
cool,
so
those
are
the
kind
of
like
the
next
steps,
I
kind
of
see
a
week
or
two
around
what
we
need
to
do
for
the
blockchain
piece.
Is
there
anything
that
I
that
I'm
missing
that
we
may
need
to
include
on
that.
B
Okay,
so
in
the
next
two
weeks
you
know
it'd
be
great.
If
we
can,
we
can
Target
a
lot
of
this
for
next
week
to
keep
things
moving,
but
we
have
the
theratilia
CLI
CI
CD
testing
to
do
the
wrap
up
the
nft
storage
and
then
expand
into
the
Rango
DB
realm.
B
B
So
that's
kind
of
what
I'm
thinking
in
the
next
week
that
we
need
to
tackle
two
weeks,
Max.
B
Cool,
oh
and
then
Sasha
just
a
side.
Note
I've
I've
been
working
on
the
the
helm
charts
in
the
the
GitHub
actions
for
creating
the
home
cards.
Oh.
C
B
So
one
of
the
things
I
did
was
just
to
simplify
our
whole
lives.
I,
remove
the
Google
Cloud
build
and
moved
over
just
GitHub
actions
for
our
microservices
and.
B
Just
to
kind
of
consolidate
what
we
have
going
on,
we
have
too
many
pieces
floating
around
and
I'm
working
on
the
the
main
home
chart
that
has
the
sub
charts
in
it.
Oh.
A
B
I'm,
taking
what
Ben
did
down
in
Australia,
he
wrote
a
simple
node.js
program
to
grab
all
the
charts
from
all
the
repos
and
smash
them
into
one
big
one:
yeah
that
wasn't
I
I'm
I.
It
wasn't
working
a
hundred
percent
on
the
way
we
need
to
to
have
the
repository
do
create
the
charts
in
the
right
format.
So
that's
why
you're
running
issues
I.
C
B
Because
there,
because
what
was
happening
is
the
that
program
was
re
reading
in
every
single
chart
in
every
single
version
of
every
single
chart
into
one
big
massive
chart,
yeah.
C
B
Makes
sense
so
what
we
need
to
do
is
what
I'm
making
the
change
to
do.
Is
we
create
a
a
parent
child
chart
at
at
that
level
and
then
once
we
have
that
version
of
that
chart
the
way
we
want
it
to
look.
So
basically,
you
can
think
of
it
as
a
a
snapshot
of
the
application
version.
At
that
point
in
time
that
chart
then
gets
saved,
and
then
we
run
the
helm
indexer
to
create
the
the
crate
correct
index.yaml
from
that
guy.
B
B
C
B
Is
going
to
work
a
lot
better
on
that
front,
and
then
we
can
add
in
automation
to
say
if
a
if
a
microservices
updated,
go
and
notify.
C
C
C
B
And
then
yeah,
because
I
think
your.
Let
me
know
when
you're
at
a
point
that
we
need
to
create
the
artillius
in
the
Box
repo
on
our
side.
C
Yeah
I
can't
wait
to
push
it
into
Atelier
side.
The
only
thing
I'm
working
on
now
is
istia
and
then
I've
got
auger
and
Captain
running.
They
run
I
want
to
get
istio
running
so
that
we
can.
You
can
just
hit
the
cluster
from
your
browser
without
having
to
do
port,
forwarding
and
stuff
right,
so
I
had
to
go
and
learn
about
istio,
which
I
learned
about
istia
and
Anna.
Now
I
know
what
this
deal
works
on
a
I'm,
not
an
expert
but
I
know
how
it
works
right.
A
B
Yeah
right
now,
the-
and
this
is
something
that
will
I'll
need
to
work
with
you
on
the
terraform
side
is
how
we
pass
in.
You
know
like
when
you
run
a
Helm
deploy,
you
can
give
it
a
long
string
of
parameters
at
the
command
line
or
Helm
upgrade.
B
You
can
give
it
a
parameters.
I'm,
assuming
those
parameters
are
pushed
into
terraform,
correct.
A
C
Into
anything,
if,
if
terraform
doesn't
support
it,
it
supports
batch
scripts,
you
just
use
a
bash
script
right
or
you
don't
even
have
to
use
a
bash
script.
You
can
actually
put
your
scripting
in
your
terraform.
It's
called
a
local
exec
provider,
okay,
like
I'm,
just
doing
cool
stuff.
For
that,
and
it's
amazing
man.
We
can
definitely
terraform.
B
Okay
cool
because
there's
things
like
we
have
to
generate
some:
the
JWT
public,
private,
Keys
and
there's
a
couple
other
settings
that
we
need
to
do
to
make
sure,
depending
on
what
cluster
you're
running
on.
If
you're
running
on
client
kind
like
a
local
Dev
environment
versus
gke
or
AWS.
And
if
you
have
load
balancers
and
things
like
that.
So.
C
C
B
I
think
that'll
be
the
a
perfect
next
step
to
getting
people
up
and
going
really
easy.
C
Yeah
and
we
can
use
if
we
want
to
go
to
the
cloud,
what
we
use
as
modules
and
we
just
consume.
Instead
of
repeating
the
code,
we
use
modules
that
can
different
environments
can
consume
that
same
module.
So
that's
how
you
can
do
that
yeah
you
can.
We
can
do
red
stuff
there.
We
can
make
it
so
easy
for
people.
B
And
running
yeah,
all
right
well
I
will
try
to
get
those
concerts
that
the
the
mean
Helm
charts
sorted
out
this
week,
I'm
getting
close,
but.
B
C
B
Cool
because
I
may
need
to
clean
up
the
GitHub
Pages
branch
of
all
this
all
the
repos
yeah.
C
B
A
B
All
right
well,
thank
you.
Everybody
I
will
update
the
if
nobody's
been
taking
notes.
I
will
go
back
and
update
the
the
document,
our
architecture
document
I
just
can't
do
it
on
this
little
screen
and
talk
to
you
guys
at
the
same
time.
So
all
right.