►
From YouTube: April 1, 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
Okay,
it
looks
like
it's
recording
so
that
april
1st
or
to
this
architecture
meeting
I
don't
have
the
doc
up
yet
I'll.
B
A
Okay,
we're
getting
there
so
just
a
couple
updates
that
we
have
going
on
today
is
the
first
day
of
chico's
africa.
We
have
two
mentees.
A
I
thought
we're
getting
one
but
we're
getting
two
this
time,
so
I'm
gonna
reach
out
or
sasha
if
you
can
reach
out
to
aisha
and
see
if
she
can
help
out
on
that.
I
know
she
mentioned
some
interest
on
that.
A
All
right,
so
that's
gonna
start
today.
It's
gonna
be
between
20
and
30
hours
a
week
for
about
a
month
we're
going
to
have
them
focus
on
on
our
new
project.
A
The
part
around
dependency
information
so
going
into
containers
grabbing
information
out
of
the
containers
like
what
are
all
the
python
modules
that
are
installed
on
the
container
and
what
are
the
what's,
the
license
associated
with
it
and
the
cves
there's
a
another
open
source
project
that
we're
going
to
be
levering
leveraging
around
that.
Actually,
two
of
them
one
is
going
to
be
a
cyclone
dx.
A
Is
a
ui
that
has
some
rendering
in
it?
I'm
not
sure
at
this
point,
if
we're
going
to
how
we're
going
to
relate
the
ui
data
and
display
it
if
we're
going
to
literally
bring
in
dependency
track
into
ortilius
or
if
we're
just
going
to
make,
do
our
own
ui,
because
the
information
that
we're
going
to
gather
the
key
information
that
we're
looking
for
is
what
are
the
licenses
being
con
in
the
containers
and
then
what
are
the
the
cves
in
the
containers
that
information
that
dependency?
A
I
I
need
to
come
up
with
a
better
term.
If
somebody
has
it
at
the
package
level
or
the
module
level,
the
hard
part
is
every
language
has
a
different
term
for
it,
so
we'll
call
dependency
packaging
for
now.
A
The
the
package
information
we'll
roll
that
up
to
a
version
of
the
component
and
then
from
there
we'll
roll
the
component
from
the
component
version
up
into
the
application
version
and
then
also
at
the
environment
level.
So
one
of
the
goals
on
this
part
of
the
project
is
to
you
always
get
these
questions
from
lawyers.
What
are
all
the
open
source
licenses
that
you're
using
in
your
project
or
what
are
all
the
open
source
licenses
that
are
out
in
production
or
what
are
the
cves
in
production?
A
So
that's
where
we'll
have
this
information
to
answer
those
questions
as
we
roll
things
up
through
the
process,
so
that's
what
they're
going
to
be
working
on
aisha
and
sasha
are
going
to
be
helping
out
as
the
mentors.
If
anybody
else
is
interested,
let
me
know
I'm
going
to
push
for
them
to
be
asked
questions
on
the
discord
channel,
so
in
the
dit
in
the
dev
discord
channel.
That's
where
we'll
be
doing
some
focus,
I
don't
have
their
user
ids
set
up.
A
Yet
we
have
an
onboarding
call
and
a
couple
hours
that
will
get
all
that
sorted
out
so
we'll
introduce
them
to
the
group
and
if
something
comes
up
they
need
help.
Please
give
them
a
hand.
A
Also,
on
the
our
service
catalog
project,
I
did
put
out
a
a
database
dump
for
some
sample
data.
Let
me
drop
that
in
the
drive.
I
dropped
it
in
the
discord,
but
if
anybody
needs
it,
we
run
postgres,
like.
I
think
nine
six
or
something
like
that
there
are
some
bugs
with
the
database
drivers
in
10.,
so
we
stuck
with
the
version
nine
for
now:
hey.
B
Steve
on
that
topic,
would
it
be
useful
if
we
created
a
test
repository
and
added
it
to
there.
A
I
was
thinking
of
that.
I
have
to
double
check
the
the
data
it
looked
like
there
was
no
user
id,
you
know
passwords
or
user
ids
in
there.
Oh,
I
see,
but
there's
there's
like
the
basic
ones.
A
Like
admin
admin,
you
know
test
user
one,
two,
three,
those
type
of
things
that
are
are
in
in
the
data,
but
I
think
after
we
have
people
play
with
it
and
we
look
at
take
a
second
pass
at
it
and
if
people
are
finding
that
it's
good
data
to
start
with
from
debugging,
you
know
writing
your
code
and
debugging
that
they
we
can
move
it
over
to
a
repo.
E
A
So
I
think
it's
pretty
clean
from
what
I
been
working
with.
It
came
from
one
of
my
test-
databases
that
is
basically
built
up
from
scratch
versus
a
database
that
I
do
a
dump
of
like
somebody
else.
That's
I
need
a
debug
or
anything
like
that,
so
I'm
I'm
pretty
confident
that
we're
going
to
be
clean
on
that
front,
but
I
just
want
to
wait
and
leave
it
out
in
a
google
drive
for
now.
E
A
If
you
are
using
windows,
there's
a
if
you
go
to
the
postgres
website,
you
get
redirected
to
another
company,
it's
like
enterprise
db,
or
something
like
that.
That
will
give
you
the
installer
for
installing
postgres
locally.
A
I
usually
use
the
something
in
the
version:
9
version
10
area
for
postgres
you'll
end
up
with
a
135
or
140
tables.
A
If
you
need
help
navigating
the
tables
and
working
on
queries
I'll,
let
me
know
because
I'm
in
there
all
the
time,
so
I'm
familiar
with
the
relationships,
I
can
at
least
point
into
the
right
tables
to
get
the
data
that
you
want
for
the
service
catalog
we're
going
to
be
creating
a
couple
new
tables,
especially
specifically,
to
deal
with
the
the
dependency
packaging
that
we're
just
talking
about
with
the
the
the
sheet
codes
africa
mentees.
A
So
that
will
be
part
of
their
project
as
well
as
doing
some
database
table
creation.
Manipulation,
not
not
a
big
deal.
A
couple
tables,
like
I
said
most
of
this
stuff,
is
already
pretty
well
laid
out
for
everybody
to
move
forward
with.
A
I
did
change
the
or
I'm
in
the
process
of
changing
the
login
for
ortelius
to
use
jwt
tokens,
instead
of
so
basically
you
log
in
with
the
user
id
password
and
you
get
return
a
jwt
token.
I
did
an
implementation
where
we
can
revoke
the
tokens
from
the
server
side.
The
tokens
live,
I
think,
for
an
hour.
A
So
basically
that's
how
long
you
get
to
be
in
the
in
the
ui
until
if,
while
if
for
any
activity,
if
you're
inactive
for
over
an
hour,
then
you
have
to
be
you
have
to
log
back
in
basically,
so
that's
that's
going
to
be
hopefully
early
next
week,
I'll
get
that
merged
into
everything.
I
just
have
to
do
some
more
testing
on
it.
It's
a
little
interesting
change.
A
Put
it
that
way.
So
that's
where
everybody
will
be
able
to
start
using
that
that
token
to
on
the
restful
api
and
their
microservices,
to
be
able
to
connect
up
to
the
database
and
as
a
particular
user
and
be
able
to
to
basically
get
your
data
without
having
to
go
through
a
fancy
login
process
at
that
level.
A
Yeah,
so
on
the
issue
side,
I
want
to
thank
owen
for
doing
some
more
work
on
the
the
website.
Fine-Tuning
that
oh
and
I
saw
a
pull
request
for
a
git
ignore,
I
think
it
was.
Can
you
can
just
give
us
update
what
you
did
on
that.
F
Yeah
sure
so
the
way
hugo
works
is
takes
the
defined
hugo
content
and
then
renders
it
out
to
content
which
then
gets
loaded
into
the
nginx
container.
We
use
that's
the
eventual
static
content
that
writes
out
to
slash
public
in
the
repo
and
slash
resources.
F
Additionally,
because
we're
using
the
hugo
post
css
version,
we
also
have
node
modules
we
need
to
extort
install.
So
I
was
finding
myself
when
I
was
doing
local
dev
that
I
was
doing
hugo
serve
minus
d
and
then
I
opened
up
git
status.
I
was
like
holy
hell,
there's
17
000
files,
which
need
to
be
committed.
I'm
sure
I
only
made
a
single
line
change
and
it
was
because
the
the
rendered
output
hadn't
been
added
into
the
get
ignore.
F
So
that's
now,
when
we
get
ignore,
if
we
were
running
it,
the
website
directly
from
a
git
repo,
which
is
one
of
the
ways
of
running
hugo,
we
would
want
that
stuff
to
be
committed,
but
because
we're
then
rendering
it
to
we're
creating
a
docker
container
as
the
artifact,
and
we
have
a
multi-stage
docker
build.
So
we
build
it
into
one
stage
and
then
copy
that
across
into
the
final
image,
we
don't
need
it
in
the
reaper.
F
A
Now
does
the
you
know
when
you
can
go
to
like
a
black
page,
and
you
can
say
I
want
to
edit
this
page
is:
is
that
still
working.
F
Yeah
that
should
still
work,
so
it
will
still
take
you
to
the
get
repo
and
take
you
through
that
process,
because
that's
handled
as
a
direct
link
to
the
git
repository
which
really
just
changing
it.
So
we're
not
storing
that
rendered
artifact
content
in
git,
as
we
only
need
it
in
the
eventual
container.
A
A
And
just
to
let
people
know
the
bill
did
go
down
yesterday
for
the
website.
That
was
on
our
side.
We
run
the
reverse
proxy
on
our
network
here,
because
I
have
the
keys
locally
on
our
network
for
connecting
tours
or
google,
and
things
like
that.
So
we
have
a
set
of
ssh
keys
that
we
use,
depending
on
who
we're
authenticating,
with
basically
public
private
keys
for
the
different
cloud
providers.
So
I
run
that
internally
on
a
network
and
that
docker
container
just
went
down.
A
We've
been
moving
things
around
here
at
our
office.
So
that's
part
of
the
reason.
Eventually
I
want
to
move
that
to
the
kubernetes
cluster
somewhere
and
you
know
lock
down
those
keys
over
on
the
cloud
provider
side.
A
One
of
the
things
that
we
need
to
start
looking
at
from
our
architecture
perspective,
is
a
who
we
can
get
as
a
cloud
provider
for
running
our
kubernetes
cluster
right
now,
we're
running
under
deploy
hub
was
able
to
get
a
startup
program
through
microsoft,
so
we
got
one
year
worth
of
basically
azure
resources
or
up
to
25
grand
of
azure
resources.
That's
going
to
expire.
I
think
in
june.
A
A
Okay,
I'll
make
sure
that
gets
on
the
agenda.
Yeah.
A
Because
the
other
thing
we
could
do
is,
I
believe
there
may
be
a
an
open
source
program
in
microsoft
that
we
may
be
able
to
leverage,
since
they
have
the
startup
program.
B
A
Okay,
cool.
I
wasn't
sure
that
was
the
main
stuff
that
I
had
issues.
A
Okay,
let
me
jump
over
there.
A
Oh,
I
did
open
a
a
new
issue
yesterday
around
creating
versions
of
environments,
something
that
we
need
to
start
thinking
about
at
that
level.
A
A
So
if
anybody
is
interested
in
the
dependency
packaging
around
cyclone,
you
know
dealing
with
security
scans
cves
licenses.
The
cyclone
dx
is
a
good
one
to
look
at,
and
this
is
where
we're
gonna
we're
gonna
need
to
throw
a
couple
people
at
this.
It's
I
don't
know
if
the
mentees
from
chico's
africa
are
going
to
have
enough
knowledge
about
what
were
the
underlying
covers
and
why
we're
trying
to
scan
for
things.
A
A
Microservices-
and
I
know
who
is
it
zach,
I
think
it
was
zach-
was
doing
some
updates
around
the
helm
charts.
So
there's
a
lot
of
little
cleanup
that
we
need
to
do
with
our
existing
microservices
that
we
had
in
place
from
the
hackathon.
B
B
And
I
think
what
you're
going
to
do
is
break
it
out
for
updating
the
what
service,
data
and
break
it
out
into
small
chunks.
So.
A
A
B
A
Here's
one
of
them
so
some
of
the
base
data
that
we
need
to
gather
we
have
most
of
it,
but
we're
going
to
need
to
do
some
queries
just
to
persist.
Slack
channel
hip
chat,
discord,
pager
duty,
those
type
of
of
of
information,
put
some
information.
Basically,
what
we're
looking
for
as
far
as
a
rough
query
as
part
of
that
process
I'll
make
sure
the
other
ones
are
created,
because
I'm
not
seeing
them
here
I
mean.
B
Yes,
since
we
only
have
eight
minutes
left
on
this
call,
I
what
I
suggest
that
we
do
is
schedule
a
day
for
anybody
who
wants
to
start
working
on
this
project.
The
service
catalog
project
make
sure
we
have
the
issues
clearly
defined
and
then
kind
of
do
a
kickoff
meeting.
B
I
think
maybe
right
now,
because
I
think
we
have
some
folks
that
are
new
to
programming
as
well,
that
it
would
be
helpful
to
do
some
kind
of
a
regular
call
just
to
make
sure
we
for
the
just
for
the
service
catalog
folks
who
wants
to
pre
who
wants
to
participate
in
that.
A
B
B
A
All
right,
there's
82
issues,
so
you'll
get
80
of
them.
D
C
B
And
powell-
and
I
don't
know
if
a
dtf
does
she
dropped,
are
you
guys
up
for
doing
some
work
in
this
area?
E
G
B
Okay
and
dt,
what
about
you?
What
time
is
it
right
now.
B
So
can
we
do
this
time,
then,
possibly
starting
next
week.
C
Not
the
same
as
pablo,
I
think
pebbles
in
poland
same
at
the
moment.
At
the
same
time,.
B
Yeah,
okay,
so
let's
do
it
at
this
time,
which
would
be
8
30
for
us
and
we'll
do
it,
but
maybe
just
do
a
standing
meeting
that
you
can
jump
on
a
call
with
steve
steve.
What's
your
calendar
starting
to
look
like
for
next
week.
A
We
can
do
monday
monday.
I
don't
know
it's
easter
monday.
I
don't
know
if
that
this
group
doesn't
seem
to
care
about
holidays.
So
I'm
just
a
bunch.
B
A
B
A
Yeah,
the
only
thing
I
run
into
these
other
c
cdf
meetings
that
get
in
the
way.
B
Yeah,
there's
nothing,
there's
nothing
for
you,
there's
no
toc
meetings
or
sig
meetings.
H
B
The
event's
exit
9,
so
that
gives
you
30
minutes
just
to
do
a
touch
base,
but
I
think
you
kick
it
off.
On
monday.
A
A
So
I'm
trying
to
think
the
best
way
to
I
said
hate
to
put
this
out
to
everybody
in
the
in
the
google
groups,
because
a
lot
of
people-
this
is
more
of
like
a
smaller
working
group.
What
I'm
going
to
do
is
I'm
going
to
put
the
calendar,
invite
in
the
announcements
in
slack
and
discord
for
monday,
so
we
can
at
least
start
there.
F
B
A
group
out
of
australia
who
want
to
start
working
on
the
architecture
team
so,
but
there
it's
like
one
in
the
morning
right
now
for
them,
so
we're
gonna
do
a
kind
of
a
shadow
or
a
second
architecture
meeting,
and
that
is
happening
today
at
four
o'clock.
You
know
if
it's
we're
going
to
start
on
the
15th.
B
So
two
weeks
from
today
we'll
be
doing
two
meetings.
One
will
be
at
the
this
time
at
eight
o'clock
our
time
and
then
the
follow-up
one
will
be
at.
I
think
it's
4
30
our
time.
I'm
sorry.
B
If
that,
if
that
second
shadow
of
time
works
better
for
you,
you're
totally
welcome
to
to
attend
it,
it's
really
going
to
just
depend.
I
think,
for
most
of
you,
it'll
be
a
weird
time.
It'll
probably
be
1am
for
the
rest
of
us,
but
so
we'll
be
doing
two
of
them
like
six
hours.
Apart.
B
B
C
B
You'll
join
that's
happening
and
they're
going
to
try
to
get
a
you
know
a
small
team
together.
I
apparently
there's
a
lot
of
people
in
australia
who
want
to
participate
in
open
source
projects,
but
because
of
the
time
zone,
they've
been
limited,
so
we're
going
to
accommodate
them.
It's
not
a
problem
for
us
to
to
do
this
call
twice
and
we're
not
going
to
have
it
we're
not
going
to
do
that
with
the
regular
community
meeting
or
the
outreach
we're
just
going
to
do
right
now.
A
A
So
I
will
make
sure
that
those
issues
are
all
out
there
and
ready
to
go
before
monday
and
put
some
more
detail
behind
them.
Some
more
meat
behind
the
what
we
have
going
on
and
then
we'll
get
running
on
monday.
B
And
we
need
to
make
sure
that
everybody
has
what
they
need
to
do
to
do
the
coding,
if
there's
stuff
that
they
need
to
download.
You
know,
I
think
we
should
focus
on
making
sure
everybody.
A
I
think
that's
all.
I
had
really
we're
gonna
start
moving
here,
pretty
quick,
so.
B
Forward
to
today,
yeah
it'll
be
a
good
learning
experience
for
us
all.
I
think
the
I
think
the
blog-a-thon
was
useful
because
it
started
requiring
it,
and
it
was
great,
oh
and
thank
you
so
much
for
getting
the
website
where
it's
at.
F
B
We
could
have
that
as
our
sort
of
our
first
big
project,
but
I'm
looking
forward
to
seeing
everybody
starting
to
get
their
head
into
coding
and
watch
people's
skills,
increase
and
it'll
be
it'll,
be
fun,
be
hard.
C
E
E
B
A
A
So
what
will
the
the
approach,
just
so
everybody
kind
of
knows
in
general?
The
approach
I
like
to
use
around
the
programming
is,
they
may
seem.
A
A
little
slow
or
but
what
I
do
is
we'll
we'll
take
this
in
small
steps,
because
I
don't
know
everybody's
programming
skills
and,
if
you're,
a
rock
star
I'll
I'll,
have
you
jump
in
and
help
other
people?
But
what
we'll
do
is
we'll
set
things
up,
so
we
do
a
small
change
like
sasha
put
together
a
bubble
sort
for
a
python
flask.
It
has
nothing
really
to
do
with
the
data
that
we're
dealing
with,
but
it's
going
to
be
something
a
good.
A
It's
a
good
starting
point
for
the
mentees
to
get
them
going
on
that
and
then
we'll
build
on
to
that,
putting
it
into
a
docker
container
and
then
doing
a
cloud
build
around
that.
So
we'll
do
this
process
where
we're
going
to
iteratively
add
on
more
complexity
to
the
the
coding.
So
once
we
get
to
the
certain
level
we'll
start
bringing
in
sql
queries-
and
you
know
multi
transactions
and
things
like
that
that
we'll
be
dealing
with
so
everything's
going
to
be
built
upon
at
that
level.
A
A
B
That's
not
till
june
anyway,
so
that
gives
us
some
time.
So
that's
why
this
she
code,
africa
and
getting
this
project
started,
will
be
good
practice
for
us.
Yeah.
C
A
Yeah
yeah
definitely
all
right,
everybody
well,
thank
you
so
much
and
I
will
send
out
that
invite
for
monday
and
we'll
talk,
then.
G
Can
I
make
a
quick
question:
yeah?
Yes,
because
I'm
wondering
about
the
this
micro
service
management
platform?
G
B
And
there,
but
there's
also
a
have
you
signed
up
yet.
B
There's
a
deploy
hub
team
that
we
host
the
ortillius,
the
full
artillious
version,
and
it
has
something
called
the
hipster
store.
B
My
suggestion
is
steve:
can
you
send
him
a
calendar
link
and
steve
can
help
you
get
signed
up
and
started
on
playing
with
the
test
data
in
the
hipster
store.
C
A
And
what
it,
what
it
is,
what
the
what
microservices
are
in
general
are
little
functions
that
go
and
get
like
data,
so
example,
microservice
would
be
get
the
user
profile,
and
that's
the
only
thing
that
the
microservice
does
is
is
go
retrieve
a
user's
profile
based
on
like
a
user
id
as
an
input.
A
So
that's
all
that
that
microservice
does
and
what
we
do
is
we
have
in
ortelius,
because
we
have
about
130
140
tables,
we'll
have
around
140
microservices,
roughly
probably
a
little
more
to
do
what
we
need
to
do
to
make
the
transactions
occur.
Now
what
that
allows
us
to
do
is
we
can
have
each
person
working
on
a
specific
microservice
and
they're
isolated
from
everybody
else
for
the
most
part.
A
So
what
that
allows
us
to
do
is
to
have
different
speeds
on
which
microservices
are
being
developed
and
maintained,
and
what
we
do
from
the
front
end
side
of
things
and
also
on
the
kubernetes
cluster
side.
We
kind
of
plumb
it
all
together
at
runtime,
so
we
pick
which
versions
of
which
microservices
that
we
want.
We
plumb
it
all
and
hook
them
all
together
at
runtime.
A
We'll
probably
rarely
have
to
go
back
and
revisit
it
unless
we
have
like
a
business
reason
to
go
our
business
reason
or
bug
that
we
need
to
go
change
it,
but
we
end
up
with
80
percent
of
our
micro
services
will
be
pretty
static
and
that'll
be
15
to
20
percent
that
are
going
to
be
changing
a
lot
because
of
enhancements
new
business
requirements
bugs
those
type
of
things
is
where
we'll
have
that
those
updated
those
micro
servers
updated
more
frequently.
A
So
it's
a
really
it's
a
really
nice
way
to
architect
an
application
as
part
of
that
process.
A
A
And
docker
just
popped
up
saying
I
wanna
install
so
like
a
mongodb
one
of
these
no
sql
databases.
You
can
just
go
ahead
and
and
write
your
code
and
your
code
will
basically
the
way
you
write.
It
allows
it
to
persist
the
data
basically
kind
of
automatically
in
the
background
for
you,
but
because
we're
using
a
relational
database,
we
have
to
go,
create
the
tables
and
the
columns
and
things
like
that.
A
B
Go
ahead
and
I
sent
you
a
in
the
chat.
You
should
see:
steve's
calendar,
yes,
just
click
on
that
and
and
grab
a
slot.
B
And
anybody,
if
you're,
if
there's
any
questions
you
have
don't
ever
hesitate
to
grab
time
on
our
calendars,
you
can
find
our
calendars
at
deploy
hub.
There's
a
on
the
front
page
steve
show
you
just
go
to
the
website.
B
Here
I'll
share
I'll
do
it.
So
if
you
go
over
to
the
website,
there
is
a
on
the
front
page.
It
says
this
is
on
our
corporate
website.
It
says
chat
with
the
team.
If
you
click
on
schedule,
there's
a
link
to
put
a
time
on
my
calendar
and
then
there's
two
links
to
put
time
on
steve's
calendar
one's
a
like
a
30
minute
and
one's
an
hour.
I
would
schedule
the
deep
dive.
C
Now,
can
I
ask
a
question
quick:
is
there
a
cicd
tool
that
we
still
need
to
test
just
asking
from
us,
so
so
that
I
can
I
want
to
try
and
do
two
versions,
one
stone,
because
I've
got
some
stuff
from
my
own
private
network,
my
home
network
that
I'd
like
to
I
could
you
know
I
could
use
a
tool
that
we
need
to
test
and
use
that.
As
part
of
my
you
know,
part
of
the
testing.
A
I
think
the
the
get
lab
yeah
we
really
have
not
built
in
a
any
pipeline
pieces
around
git
lab.
C
B
If
you're
looking
at
an
open
source,
one
though
I
would
suggest
taking
a
look
at
captain,
I
think
we
should
have
better
integrations
with
captain.
E
B
A
commercial
perspective,
I
think
that
we
do
need
to
do
more
work
with
git
lab,
because
I
know
there's.
B
Building
out
a
in
captain
an
event
for
for
ortillius,
that
would
be
a
really
great
idea.
A
The
hard
part
was
like,
like
even
like
techton
captain,
you
know,
there's
a
couple
others
out
there
like
puppets
nebula,
you
have
to
actually
stand
up
a
full
kubernetes
cluster
and
you
know
if
you're
gonna
be
doing
that
on.
You
know
one
of
the
cloud
providers
that
running
that
every
day
it
gets
pretty
pricey
yeah.
F
I
was
gonna
say
on
the
puppet
nebula,
which
I
think
is
now
called
relay.
It's
their
kind
of
sas
version,
so
intelligent
growth
solutions
is
on
their
early
access
program.
Oh
nice,
you
essentially
have
a
10
year,
30
user
license
free
for
a
year,
they're
going
to
be
working
with
us
to
create
integrations.
F
A
Because
I
did,
we
were
involved
in
the
when
it
was
called
nebula.
So
it's
like
the
beta
of
relay,
so
we
did
create
a.
I
can't
remember
what
they're
calling,
but
basically
we
we
created
our
module
for
nebula,
which
should
translate
over
to
relay
pretty
easily.
F
But
yeah,
essentially,
if
there's
anything,
we're
using
igs
where
we're
finding
they
don't
have
great
native
support
for
it.
Part
of
the
eap
program
we've
got
with
them
is
to
basically
say
hey:
could
you
help
flush
this
out
or
polish
it
up
or
bring
it
into
the
core
relay
modules?
So
we
can
utilize
that
link
if
we
need
to
look
into
that.
A
Perfect,
if
you
could
do
me
a
favor
and
open
an
issue
around
that
just
so
because
I
will
totally
forget
about
it.
A
Guaranteed
because
I
know
like
I
said
I
did
work
around
nebula
so
that
should
translate
over
to
to
relay
and
I
believe
it
should
translate
over
to
tecton
as
well,
because,
like
you
said
under
the
covers,
is
basically
techcon
stuff.
That's
happening.
B
And
I
I
think
that
the
an
integration
with
with
relay
I
mean
if
we
were
to
say
if
we
have
to
choose
between
get
lab
and
relay
right
now
I
would
say:
let's
do
relay.
B
A
C
B
Well,
it
sounds
like,
then
it
would
be,
maybe
get
lab
relay
and
then
captain
sasha
would
be
the
order.
A
And
then
the
other
one
obviously
is
spinnaker
but,
like
I
said,
the
some
of
these
other
ci
cd
tools
are
so
they're
they're
a
lift
to
just
get
installed
and
get
going
so.
C
A
A
Yeah,
that's
that's!
Why,
like
you
said
something
like
get
lab
the
the
nebula
I
mean
relay
now.
If
they
had
the
sas
version
with
the
early
access
that
one
would
fit
in,
you
know
like
tekton
does
not
really
have
a
a
sas
version
have
to
install
everything
locally
as
part
of
that.
So
that's
one
of
the
the
things
you
get
tripped
up
on.
F
If
we,
so,
if
we
talk
about
local
dev
environments-
and
I
was
mentioning
the
dm.sql
stuff,
potentially
as
a
container
potentially
the
the
microservices
which
we're
looking
at
spinning
out
as
well
as
far
as
that,
it
might
be
worth
looking
into
something
like
scaffold
and
having
a
local
scaffold
template,
which
is
google's
spin
up
a
stack
of
microservices
against
a
kubernetes
cluster
which
you
can
automate
locally
and
it
will
install
the
helm
charts
and
do
the
whole
deployment.
F
I
found
it's
quite
useful
for
validating
the
whole
end-to-end
deployment
locally,
so
it
might
be
that
we
could
look
at
creating
an
ortelius
scaffold
template
which
we
can
just
add
in
new
helm,
charts
to
and
then,
if
sasha
wants,
to
look
into
a
specific
seduce
solution.
It's
quite
often
easy
just
to
slot
that
in
for
your
local
desktop
I'll,
make
a
note
to
try
and
write
up
a
little
bit
of
notes
on
scaffold
and
log,
an
issue
against
something
to
look
at
for
that.
Local
dev
ecosystem
and.
A
A
F
A
Yeah,
because
the
does
that
run
in
a
it's
been
a
while,
since
I've
run
kubernetes
locally,
I
usually
just
run
the
docker
containers
locally
and
interact
with
them
at
that
level.
You
know
that's
one
of
the
nice
things
with
the
microservice,
because
you
can
put
you
know
you
don't
need
this
whole
big
dev
environment
yeah
the
little
piece
that
you
get
to
work
with.
But
what
are
the
kubernetes
clusters?
Look
like
these
days
for,
like
a
windows,
is.
F
F
So
it's
not
being
shipped
natively
per
se,
but
you've
got
a
couple
of
good
options.
Mini
cube
is
a
you
know
the
traditional
one
which
runs
in
a
vm
but
you've
never.
F
Like
kind
which
I
use
quite
heavily,
it's
what
we're
using
at
igs
for
the
devs
local
dev
stacks
and
kind,
is
what
the
kubernetes
sig
their
dev
and
it
essentially
brings
up
the
full
stack
inside
docker.
So
as
long
as
you've
got
docker,
it
will
then
bring
up
a
control
plane
and
the
number
of
nodes
you
specify
within
docker,
which
is
one
of
the
nice
things
about
it.
Is
you
can
figure
the
whole
thing
through
yaml
files
you
provide
as
part
of
the
input,
so
it's
really
easy
to
automate
in
a
programmatic
way.
F
F
Up
and
tear
down
event,
we
use
it
we're
using
it
now
at
igs,
because
we
have
certain
cloud
components,
part
of
the
deploy
which
we
sometimes
want
to
validate
locally
before
it
goes
through
the
cd
process.
So
it
allows
for
devs
to
say
I
want
to
bring
up
these
services
with
debug
hooks
into
it,
and
the
emulator
for
azure
blob
storage
within
my
local
environment,
and
we
found
it's
a
little
bit
easier
doing
it.
F
That
way
than
trying
to
do
it
with
just
pure
docker
containers,
because
it
lets
them
validate
the
helm
files
as
well
right.
Nice
I'll
make
a
note
to
write
up
something
just
as
a
kind
of
let's
some
notes
on
local
dev
and
maybe
an
issue
to
look
into
options
around
how
we
support
local
dev.
A
A
Exactly
because
we
will
end
up
with
some
tightly
coupled
I
want
to
say
tightly
coupled,
I
would
say
we're
going
to
end
up
with
dependencies
between
services.
I
can
already
envision
that
so
like
a
the
login
service
and
your
microservice,
so
you
log
into
one
service,
get
your
token
and
then
that
token
will
be
used
for
your
service
to
access
the
data
database.
So
I
have
some.
A
Multi-Dependency
or
multi-transactions
that
will
need
to
have
to
deal
with,
so
we
will
be
bringing
up
a
subset
of
services
locally
for
dev,
but
I
don't
think
we'll
need
the
full
stack
initially.
B
So
I'm
gonna
so
on
this
topic,
I'm
going
to
ask
owen
and
steve
if
you
guys
could
kind
of
make
a
work
to
make
a
decision
on
how
this
can
move
forward
and
also
if
we
need
to
do
anything
with
git
lab
on
git
lab
or
puppet
relay,
I'm
I
can
also
reach
out
to
I
can
I
can
reach
out
to
abby
kearns
and
I
can
reach
out
to
brandon
o'leary,
I'm
sure
that
they
would
give
us
environments
to
work
in
from
an
open
source
project
standpoint.
A
F
So
yeah
definitely
with
them
they're
going
to
a
general
release
in
the
next
week
and
a
half.
I
think
it
is
so
they're
really
ramping
up
the
pr
and
also
looking
to
get
more
integrations
and
people
on
board
with
it,
as
they
move
from
this
kind
of
eap
to
general
release
so
they're
in
a
really
good
position.
Right
now
to
do
that.
Eric
sean
sorenson
is
the
product
owner
technical
product
owner
on
that
side
and
he's
pushing
pretty
heavily
to
try
and
get
people
using
it
and
integrated.
So
I
think
it'd
be
pretty
cool.
B
Yeah,
yvonne,
I
I
know
yvonne,
would,
if
I
sent
her
an
email,
she
would
tell
me
who
I
should
evon
and
abby
would
take
care
of
us,
I'm
pretty
confident
about
that.
So,
if
we
want
to
pursue-
and
you
know
that's
something
that
we
always
looked
at
doing
that's-
why
we
did
it,
we
we
worked
with
them
early
on
with
relay.
B
So
maybe
we
should
just
pick
up
the
pick
up
the
discussion
again,
steve
and
yeah.
Okay,.
B
And
reach
out
to
my
contacts
and
if
I
have
any
issue
I'll
I'll
ping,
you.
F
Yeah,
absolutely
I've
already
mentioned
or
tellius
to
eric
in
some
of
the
chats
who
are
having
early
on
so
if
it
ends
up
being
rooted
to
him,
he's
got
some
familiarity
with
that
space.
E
A
There
but
we'll
find
out
so
let's
knock
out
the
get
lab
because
it
sounds
like
sasha's
pretty
far
along
and
then
we'll
the
next
one
trailing
on
that
from
a
cicd
perspective
will
be
relay.
C
A
So
you
docker
is
the
original
way
to
create
a
an
image.
Now,
there's
been
other
tools
out
there
to
create
the
images,
so
you
could
do.
A
Yeah,
so
the
kubernetes
is
going
to
run
a
an
an
image
and
docker
just
happens
to
be
the
the
first
and
one
of
the
easier
ones
to
build
and
run
locally.
Okay,
what's
the
other
one,
it
came
out
of
google.
No,
I
start
with
a
k.
A
Everything
starts
with
a
cave
with
google,
the
docker
build
tool
that
allows
you
to
build
without
having
to
connect
to
the
docker
host.
A
F
Require
a
kubernetes
cluster
like
nico,
does
or
can
eco
technically
built
it
in
docker?
It
doesn't
need
a
cluster,
you
can
do
it
against
docker,
but
yeah
doc
is
still
the
kind
of
baseline
for
all
platforms.
A
And-
and
you
could
run
kineco
from
the
command
line
without
and
not
have
to
do
it
in
the
cluster
one
of
the
nice
things
with
konico
is
it
doesn't
require
a
connection
to
the
docker
socket,
that's
how
it
can
be
used
inside
of
a
kubernetes
cluster.
That's
pretty
cool.
C
A
Yeah,
if
you
were
to
go,
let's
say
you
had
a
kubernetes
environment,
let's
say
just
like
mini
cube.
If
you're
running
mini
cube-
and
you
wanted
to
do
all
your
testing
inside
a
mini
cube,
you
could
use
konico
or
podman
and
build
your
images
and
not
have
docker
running
at
all.
You'd
just
be
you'd,
be
just
interacting
with
kubernetes,
which
would
be
running.
The
images
and
you'd
have
some
other
tool
to
create
the
layers
for
you
at
the
build
level.
A
A
B
Send
you
an
email
right
now.
F
A
All
right,
thank
you,
everybody
and
keep
a
heads
up
for
the
invite
for
monday
8
30
mountain
time.