►
From YouTube: Nov 15, 2022 - Ortelius General Community 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
the
artillius
General
community
meeting
on
November
15th
I.
Don't
have
the
doc
right
in
front
of
me,
but
I'll
get
to
it.
So
just
some
updates.
So
last
week
was
the
the
Linux
Foundation
membership
Summit
and
some
of
the
things
that
came
out
of
it.
B
Tracy
and
I
were
able
to
meet
with
the
the
lead
developer
from
the
kepton
project
and
so
there's
two
of
them,
but
both
of
them
were
from
from
Captain,
and
that
was
interesting.
They
have
a
new
release
of
Captain
that
they
put
out
on
as
a
demo
for
kubecon
and
what
they've
done
is
they've
restructured
kept
into
only
live
inside
of
kubernetes.
So
it's
a
total
crd
based
solution
and
what
it
does
is
it's
going
to
trap
all
of
the
the
messages
that
are
happening
inside
of
kubernetes.
B
So,
for
example,
if
you
go
and
do
a
deployment,
kubernetes
sends
out
a
message
saying
I'm
doing
a
deployment
and
Captain
will
go
and
capture
that
and
allow
you
to
run
a
pre-action
to
the
deployment.
B
So,
like
one
of
the
things
you
could
do
is
check
to
make
sure
you
get
enough
resources
scaled
before
the
deployment
happens,
and
if
it
doesn't
happen,
you
can
stop
it
or
you
can
continue
on
one
of
the
nice
things
that
they
were
telling
us
that
we'll
be
able
to
do
is
have
a
a
global
listener
for
post
deployments
and
that's
where
we'll
hook,
ortelius
into
so
we'll
be
able
to
capture
any
deployment
without
anybody
having
to
update
their
pipeline
or
anything
like
that.
B
So
and
what
they'll
do
is
when
that
post
deployment
happens,
we'll
get
notified
of
the
containers
that
were
updated
so
which
pods
were
updated
as
well
as
what
they
call
an
application,
so
they're
introducing
an
application
concept
as
well
to
kind
of
associate
all
the
services
to
an
application.
So
that
was
a
good
news
that
we'll
be
able
to
to
drop
that
in
in
place
and
be
able
to
capture
that
stuff
without
having
anybody
to
update
any
anything
on
their
pipeline
side.
B
So
we
don't
have
to
worry
about
updating,
Jenkins
files
to
capture
deployments
or
anything
like
that,
we'll
be
able
to
do
it
all
from
the
cluster
side.
Now
this
is
on
a
cluster
by
cluster
basis.
So
if
you
have
like
uber,
where
they
have
you
know,
250
production
clusters
just
to
run
their
stuff,
it's
gonna
be
in
every
single
cluster,
we'll
be
getting
information
back
from
we
wouldn't
we
will
need
to
do
some.
B
Some
changes
on
our
rest,
API
side,
I,
think
to
handle
the
the
payload
that
we're
going
to
get
from
Captain
at
that
level.
So
we
will
have
some
coding
changes,
but
it
it
looks
good.
It
is
not
in
production
yet,
but
we
can
actually
go
and
try
it.
If
you
want,
they
said
the
the
repos
public
for
us
to
start
playing
with
it
is.
B
Yeah,
so
the
way
they're
doing
is
by
a
bunch
of
yeah.
This
is
exactly
it
so
dude
they're
doing
a
bunch
of
annotations
in
the
Manifest
files
to
be
able
to
capture
this
stuff.
B
So
the
way
we
may
need
to
do
some
stuff
around
open,
Telemetry
I,
don't
know
yet,
but
they
were
talking
that
they
they
basically
are
getting
rid
of
their
seat,
their
gooey
and
using
grafana
and
open
Telemetry
to
kind
of
visualize
what's
happening
at
that
level.
B
So
we
may
need
to
do
some
investigation
on
open
Telemetry
just
for
us
to
grab
some
more
information
from,
but
that
is
the
one
and
from
what
I
understand,
we
can
go
ahead
and
install
that
and
it
should
get
up
and
going
on
that
note.
I
have
been
reworking
the
the
helm,
charts
and
some
of
the
the
GitHub
actions.
B
So
basically
what
I've
been
doing
the
last
week
or
so
is
pulling
out
the
Google
Cloud
build
and
replacing
it
with
GitHub
actions
and
going
through
and
making
sure
the
GitHub
actions
are
actually
creating
the
right
Helm
index.yaml.
This
is
what
you
ran
into
Sasha
I,
think
I.
Have
it
all
pretty
much
plugged
together,
so
things
should
be
being
pushed
to
artifact
Hub
clean
now,
so
your
Ortiz
in
the
Box
should
be
able
to
pull
everything
from
artifact
Hub,
pretty
clean.
B
D
B
Need
to
figure
out
how
to
pass
a
couple
parameters
to
your
terraform
there's
some
things
that
we
need
to
pass
like
a
JWT
key
and
some
of
the
secrets
you
know
like
you,
ran
into
the
secrets.
B
Database
connection,
those
type
of
things.
C
B
C
E
C
B
Yeah,
there's
a
openssl
command
that
you
run
and
I
would
imagine
in
your
terraform.
You'd
have
access
to
open
SSL.
B
B
All
right,
that's
why
we're
having
a
delay?
Okay,
hopefully
I'm
still
here,
so
on
that
front,
the
cleanup's
coming
along
pretty
well
on
the
repos
and
stuff
I
did
take
Ben
pose
node.js
script
and
I
updated
it
to
make
it
so
what
happens?
Is
we
go
out
and
grab
all
the
the
charts
from
all
the
microservices,
bring
them
together
and
create
a
a
a
main
with
a
sub
chart,
update
and
then
from
there
that
goes
off
and
and
creates
the
index.eml
and
stuff?
B
So
let's
pull
them
together
and
working?
Well,
any
questions
on
like
the
the
the
captain
or
the
the
chart
cleanup.
B
Yeah,
it
looks
like
so
the
way
they're
describing
the
communication
on
the
captain's
side
is.
We
would
do
a
like
a
post
deployment
hook
and
that
would
run
a
container.
It
sounds
like
or
typescript
I.
B
It
was
hard
to
figure
out,
but
it
basically
it
runs
a
command
line
program
or
a
container,
and
that's
where
we
would
go
ahead
and
probably
use
our
CLI,
our
python
CLI,
to
be
able
to
post
details
back
over
to
through
our
rest
apis
or
we
may
just
instead
of
doing
the
CLI,
we
may
just
extend
create
a
microservice
that
will
understand
how
to
accept
the
captain,
payload
and
just
just
handle
it
on
the
server
side.
Then
that
may
be
the
easier
way
to
go.
B
B
My
my
guess
is,
we
would
probably
lean
towards,
is
creating
another
microservice
to
listen
to
that.
So
we
make
the
configuration
side.
You
know
really
simple.
Basically,
here's
our
our
URL
that
you
need
to
kind
of
forward
on
the
payload
to
I'm,
just
basically
a
little
forwarding
program,
so
that
will
simplify
what
people
need
to
do
on
the
con
skept
in
configuration
side.
B
Alrighty,
so
let's
go
on
to
the
blockchain
side.
So
on
that
front,
I
don't
see
him
here.
There's
you
know
we
had
our
architecture
meeting.
We
need
to
work
on
some
of
the
more
more
of
the
issues
around
the
nft
storage
I'm
gonna
have
to
reach
out
to,
and
I
might
ask
some
other
folks
to
reach
out
to
a
couple
people
that
are
working
on
issues
that
we
haven't
seen
updates
in
the
last
week
or
two
to
see
if
they're
able
to
complete
them.
B
If
not
we'll,
have
to
hijack
those
issues,
so
we
can
keep
things
moving
along.
The
two
main
ones
are
there's
three
main
ones:
one
is
a
cve
database,
another
one
is
the
license
database
and
the
third
one
is
the
transposing
of
the
s-bomb
Json.
So
we
can
do
get
that
part
sorted
out.
B
B
Also,
on
the
blockchain
side,
Tracy
brought
in
found
a
new
contributor,
he
is
from
Kiev,
Ukraine
and
I
believe
his
you
saw
us
get.
He
came
through
Discord
last
week.
I
think
he
goes
by
Nick
and
I
came
maybe
or
Nick
I
I'm,
not
100
sure
on
how
he
pronounces
his
name.
But
I
did
go
through
and
work
with
him
to
add
him
to
the
ortilius
repo.
B
What
he
is
specializes
in
is
ux
and
UI
design
and
I
think,
based
on
what
we
need
to
do
on
the
blockchain
side.
There's
two
aspects
of
it:
one
is
taking
like
component
version
because
we
have
all
these
versions
of
components
that
we're
creating
being
able
to
navigate
those
and
the
relationships
to
the
application
versions
and
just
getting
all
that
data.
So
it's
easy
to
kind
of
search
and
display
I
think
the
component
version
with
all
the
boxes
that
we
have
is
laid
out.
B
Well,
it's
just
the
the
list
view
that
we
need
some
work
on.
So
that's
one
aspect
of
it
that
he's
going
to
take
a
look
at
and
then
also
a
Time
series
type
of
look.
If
you
look
at
a
component
or
an
application,
how
it's
changed
over
time
and
the
blockchain
is
going
to
have
that
in
The
Ledger
our
time
series.
So
it's
just
a
matter
of
how
we're
going
to
want
to
navigate
that
through
the
UI,
so
he
does
a
UI
design,
but
not
the
coding.
B
So
we'll
still
have
issues
to
do
the
the
actual
coding
piece.
Once
we
figure
out
what
it
looks
like
then
we'll
figure
out
you
know
how
we
want
to
implement
that
going
forward.
You
know
in
in
bringing
it
into
the
the
existing
UI,
so
I
have
to
create
a
couple
issues
on
that
front
around
the
ux
design
to
make
sure
that
things
are
moving
along
on
that
front.
B
So
we
we
stay
busy
because
we're
going
to
kind
of
attack
from
both
ends,
so
I
have
the
the
back
end
piece,
the
nft,
storage
and
The
Ledger,
and
that
piece
coming
together,
but
also
we'll
need
to
address
the
front
end
side
to
make
sure
that
we're
able
to
visual
visualize
the
data
that
we're
capturing
at
that
level.
We'll
probably
have
to
have
a
couple
design
discussions
around
that
on
what
what
we
want
to
kind
of
put
in
for
requirements.
B
I'll
I'll
get
a
a
starting
point,
but
we'll
need
definitely
need
to
kind
of
evolve
that
to
make
sure
we
got
the
right
requirements
in
in
place
before
we
get
too
far
along
on
that
front,
also,
I
still
have
to
figure
out
the
payment
process
for
the
blockchain
piece
right
now.
I
may
just
use
wise
and
just
pay
everybody
from
to
play
hub
directly.
B
Instead
of
going
through
the
crowdfunding
part
of
Linux,
the
Linux
Foundation
I
was
hoping
to
meet
with
the
people
last
week
from
the
Linux
Foundation
around
that,
but
there's
nobody
from
the
CDF
that
came
to
that
in-person
meeting,
so
things
are
kind
of
a
little
I
gotta
track
that
down,
but
the
short
term.
What
I
may
do
is
just
go
ahead
and
use
wise.com
and
pay
everybody
directly
from
that
I'll.
B
B
B
Cool
try
and
think
what
else
was
on
the
list.
Tracy
was
there
anything
else?
Anybody
have
know
anything
I'm
missing.
E
You
are
good
yes,
but
let
me
just
give
a
quick
update
of
what
we
happened
at
the
open
ssf
we
did
meet
with
VMware.
They
are
still
looking
at
potentially
becoming
a
a
user
as
well
as
red
hat.
So
we
have.
We
have
continued
those
conversations,
so
that's
exciting.
E
We
also
had
some
interest
from
Dell,
so
I'm
going
to
reach
out
with
Dale
I
met
their
CTO
and
we're
going
to
have
a
chat
with
him
as
well
aloe
from
the
captain
group.
They
he
does
want
to
meet
with
our
team
and
kind
of
go
over.
What
we're
doing
so.
We
need
to
do
a
follow-up
with
that
probably
do
that
in
the
early
part
of
the
beginning
of
next
year.
E
So
all
those
were
good
things
we
had
I
think
it
was
a
really
good
conference
for
us
to
be
at
because
we
did
get
to
meet
and
face
to
face
a
lot
of
folks.
We've
been
working
with
for
some
time.
E
The
other
thing
that
I
did
is
I
reached
out
to
the
folks
from
Roadie
who
are
managing
backstage
and
I
sent
an
email.
We
scheduled
a
follow-up
call
with
their
CTO
she's,
going
to
just
kind
of
take
a
look
at
what
we're
doing
and
give
us
some
ideas
of
facts
if
we
could
potentially
have
a
plug-in
from
backstage.
So
there's
a
handful
of
you
that
are
that
that
are
show
up
to
the
architecture
meetings
that
I
invited
to
that.
E
That
call
we
may
you
know,
I,
don't
know
if
we
want
to
pursue
that.
We
have
a
lot
on
our
plate,
but
we
may
want
to
go
ahead
if
it's
something
we
can
do
create
a
project
out
there
in
case
somebody
wants
to
take
it
on
that.
E
C
E
It
would
fit
right
in
it
would
yeah
it
would
and
now
that
we
also
it
when
he
was
going
over
how
kept
in
the
some
of
the
changes
they
do
have
information
that
we
could
pull
from
kept
in
to
populate
components
and
applications.
What
Steve
likes
to
call
version
zero
or
version
one.
So
we
need
to
continue
working
on
making
it
easier
to
adopt
ortilious
and
integrating
to
Backstage,
as
well
as
integrating
to
the
underlying
pieces
that
Captain's
doing
those
are
really
good
ways
for
us
to
help
with
the
adoption
I.
E
On
the
on
the
December
14th
our
holiday
gathering,
we
have
two
talks,
we're
still
short,
we
still
so
anybody
who's
interested
in
presenting,
please
let
me
know,
and
the
elections
for
the
board
went
out.
So
please
get
that
off
your
plate.
It's
open
until
December
7th,
giving
us
enough
time
to
announce
who
the
new
board
is
for
the
December
14th
event,
s.
E
Yeah,
it
was
better
than
the
other
one
we
used
it
cost
a
little
bit.
It
was
like
30
bucks,
but
it
didn't
seem.
It
seemed
like
it
was
a
much
cleaner
and
easier
way
to
manage.
C
It
no,
it
worked
really
well,
it
was
so.
E
C
E
Then
there
was
one
other
thing:
I
can't
remember:
we
did.
I
did
send
a
finalized
blog
on
hacktoberfest
to
the
CD
Foundation.
Hopefully
they
will
be
sharing
that
and
I
continue
I'll
be
updating
some
social
media
cards.
Utkar
has
signed
up
to
take
on
the
talk
on
xrp
ledger
to
give
us
an
update
of
where
we're
at
so
we
just
have
two
more
presentations.
We
need
to
find
presenters
for.
So
if
anybody
here
wants
to
present,
please
do.
B
Oh,
and
that
reminds
me
on
the
xrpl
I,
did
submit
our
report
to
the
Ripple
folks
our
status
update.
Basically,
it
wasn't
a
big
deal.
C
Oh
cool
I
also
try
to.
B
C
10
free
jet
Brands
licenses
for
developers
in
otilius
yeah.
You
can
get
free
licenses,
but
they
said
I
didn't
do
enough
commits
I.
C
F
C
C
They
said
I
didn't
do
enough,
they
say
we
can
only
provide
freelance
licenses
to
active
committers.
A
requester
has
to
consistently
contribute
to
the
project.
For
the
past
few
months
will
be
in
the
top
three
contributors
for
the
past
year.
That
was
the
criteria
yeah,
which
sounds
like
fair
enough.
You
know,
sometimes
your
stuff
you're
working
on
is
not
always
in
the
artillius.
You
know
in
the
toilet,
but
it's
like
fair
enough.
They
have
to
have
some
sort
of
process
right.
E
E
D
C
A
Hey
guys
I
want
to
ask
a
question.
It
might
be
a
repeat
question.
What
topics
are
allowed
for?
The
the
talks
like
what
are
the
topics
say
topic
areas.
F
F
B
E
Basically,
okay,
so
and
understanding
the
data
that
artillius
gathers
I
thought
would
be
an
interesting
one,
we're
starting
to
gather
in
more
and
more
data,
especially
around
like
at
a
component
level
level,
the
Swagger
information,
the
readme
information,
the
s-bomb,
how
we
gather
the
cve
information,
how
I
implemented
ortilius
common
use,
cases
for
using
a
central
service
catalog.
E
What's
a
logical
application
and
a
decoupled
cloud
native
environment
or
any
topic
that
makes
you
happy
here.
I'll
put
these
in
the
chat,
real,
quick.
A
A
E
Because
I
I
send,
when
I
send
out
I,
send
it
out
to
the
ortelius
Google
group.
Okay,
so
make
sure
that
you're
getting
emails
from
the
artillius
Google
group.
Because
that's
where
the
vote
went
out
to
as
well.
E
Previous
okay
and
when
you
got
the
email
for
the
vote,
when
I
I
told
everybody
we
were
going
to
do
the
vote.
I
sent
it
out.
So
when
the
vote
went
out,
you
gotta
everybody
got
a
specific
invite
so
make
sure
you're
getting
emails
from
me.
E
Yeah
look
to
see
if
you
got
something
from
Tracy
at
deploy
hub
and
it
should
be
coming.
You
should
be
getting
it
through.
The
Google
group,
okay
and
you
are
definitely
in
there
because
I
checked
to
make
sure
I
did
because
I
was
you're
in
both
groups,
you're
in
the
xrp
group
and
the
artillius
group,
and
so
that's
why
I
know
that
your
name
was
in
the
yeah.
A
E
A
Yes,
okay,
and
what
are
the
talks?
Do.
E
December
14th
is
our:
is
the
we
have
a
month
basically
to
get
it
recorded?
We
try
to
get
them
done,
I
would
say
we
want
to
get
them
all
uploaded
and
ready
to
be
staged
by
the
12th
of
December,
which
is
at
Monday.
E
All
right-
and
if
you
you
know
as
soon
as
you
decide
which
one
you
want
to
do,
I
will
update
the
the
blog
so
that
your
information's
on
there
and
I'll
get
you
a
social
card.
E
Just
yesterday
signed
up
to
do
the
xrpl
update,
so
that
just
leaves
us
two
more
and
if
we
only
have
one
more,
that's
fine
too,
but
it'd
be
good
to
have
at
least
one
more.
F
E
And
I
sent
out
an
email
to
the
board
too
and
said:
hey
board
members,
if
you
have,
if
you're
not
presenting
you
might
be
good
to
do
so
and
I
believe
that
Siddharth
wants
to
get
somebody
from
NatWest
to
do
a
presentation.
So
that
would
be
our
so
Joseph.
If
you
take
one
and
Siddharth
takes
one
we'll
be
good.
A
Okay,
okay,
I'll,
take
a
look
at
the
the
topics
and
find
the
one
that
I
really
I'm,
really
interested
in
or.