►
From YouTube: Oct 28, 2021 - Ortelius Architecture Meeting AUS TZ
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
C
A
Oh
no
worries
welcome
aboard
and
glad
you
could
make
it.
Where
are
you
located
where
I'm
in
istanbul,
turkey,
okay,
a
very
nice
place.
C
So
hopefully,
this
time
works
for
you
yeah.
It's
just
perfect
timing
for
me,
so
I
have
just
finished.
My
work
finished
all
the
meetings
there
and
we
have
spent
time
to
spend
for
this
all
right.
Excellent.
It's
five
five
o'clock
here
in
istanbul.
A
D
A
Yeah
we'll
go
over
what's
happening
on
that
front
here
in
a
second,
so
just
some
updates
that
have
been
happening
over
the
last
week,
the
service
catalog
utkarsh
has
been
fixing
the
database
connection
issue
that
we're
having
when
we
get
a
database
when
there's
like
a
timeout
that
happens
in
the
background.
A
So
thank
you
very
much
for
for
figuring
that
out
it.
I
could
tell,
as
we've
been
rolling
out
the
the
changes
to
those
microservices
that
that
it's
working,
because
some
of
the
the
ones
we
haven't
changed,
throw
errors
and
the
ones
that
we
fix
are
recovering
just
fine.
So
I
it
looks
like
that
is
working.
Well,
the
the
fix
that
you
came
up
with.
A
So
many
other
things
that
have
been
we've
been
talking
about
is
around
the
packaging
and
the
installation
process
of
ortelius.
So
right
now
the
current
version
that
we
have
artelias
is
basically
a
monolith.
A
It's
a
a
monolith
container
that
has
all
the
java
code
in
it
and
it
also
has
runs
postgres
if
it
needs
to
as
part
of
that
and
uses
a
volume
mount
to
persist
everything.
So
we
it's
it
was
it's
been
very
convenient
to
get
up
and
going
because
you
could
just
you
you
don't
have
to
install
kubernetes.
You
could
just
run
it
with
docker
to
kind
of
kick
to
tires
with
artelius.
A
A
So
as
part
of
that
process,
I
opened
a
couple
issues
and
I
believe
no
it's
karam
and
usual
are
going
to
be
looking
at
how
to
interact
with
artifact
hub,
and
it
looks
like
what
we
need
to
do
is
stand
up.
Our
own
basically
chart
museum
or
a
way
to
host
our
charts
and
based
on
the
documentation.
I
read
really
quickly.
A
It
looks
like
we
can
just
basically
they're
just
static
files
that
have
to
be
in
a
certain
directory
structure
for
helm
to
go
ahead
and
pick
that
up
as
a
repo.
A
So
the
way
it
looks
like
artifact
hub
is
no
longer
a
place
that
you
would
upload
your
charts
to,
but
basically
it's
a
consolidation
or
federation
of
existing
chart,
museum
repos
that
are
out
there.
So
I
it's
gonna,
be
I
think
it's
gonna
work
out
easier
in
the
long
run
that
we'll
be
able
to
control
our
own
repro,
but
also
have
artifact
hub
as
like
a
shopping
or
marketplace
for
people
to
find
ortelius.
A
As
part
of
that
process.
I've,
the
helm,
charts
are
already
all
set
to
go.
There's
values,
files,
one
of
the
things-
is
that
our
charts
are
spread
across
our
polyrepos.
A
So
as
part
of
the
build
process-
and
it
looks
like
it
would
be
the
build
process
for
our
website,
we
would
bring
in
those
charts
and
get
them
in
the
right
directory
structure
and
things
like
that,
and
then
we
would
just
go
ahead
and
publish
our
website
as
normal.
That's
kind
of
the
feel
I
get
for
it,
but
we
need
to
do
some
more
digging
on
that
to
make
sure
I'm
understanding
the
process
correctly.
A
Just
so
you
know,
if
you
go
out
to
the
ortilia.io
homepage,
you
can
sign
up
for
the
be
able
to
test
out
the
new
version
and
basically
to
sign
up.
You
can
put
in
any
project
name
and
company
name
just
make
it
up,
and
what
will
happen
is
we
will
go
ahead
and
load
the
sample
data
for
the
hipster
store,
plus
sample
data
for
the
cves
licenses,
swagger
files
and
things
like
that.
A
So
go
ahead
and
please
sign
up
and
go
ahead
and
start
testing.
You
know
play
around
with
with
that.
I
did
notice
that
there
may
be
an
issue
when
you
switch
between
what
was
it.
You
go
from
a
component
version
over
to
an
application
version
and
then
there's
a
tab
called
like
a
package
tab,
and
we
got
this
overlay
problem.
I
thought
it
was
fixed,
but
it
looks
like
it
came
back
for
some
reason.
A
It
may
be
just
a
caching
problem
on
my
browser,
but
I
got
to
double
check
that,
but
play
around
with
that
open
issues
in
the
ortilius
ortilla,
slash,
artelias,
repo
and
just
assign
them
to
the
service
catalog
location.
Also
out.
There
is
part
of
hacktoberfest.
A
A
So
it's
part
of
the
the
the
service
catalog.
What
we
have
is
we've
added
new
boxes
and
the
new
boxes
are
pertained
to
different
objects
in
the
service
catalog.
So
you
tell
I'm
up
to
my
20
second
user
id
that
I
did
to
try
to
get
the
data
to
load.
In
correctly,
22
tries.
A
So,
in
the
as
part
of
that,
so
we'll
need
to
document
what's
happening
with
each
one
of
these
boxes,
so
in
the
oktoberfest
you'll
see
an
issue
that's
available
for
doing
the
readme
doing
swagger.
If
that's,
please
pick
those
up.
They're
gonna
be
like
a
15
minute
to
a
half
hour,
update
to
the
documentation,
explain
what
this
box
is.
What
this
box
is
the
license
issue
the
license
consumption.
A
So
please
pick
those
up
easy
way
to
get
your
your
hacktoberfest
and
then
the
license
down
here
or
the
other
ones.
If
you
can't
figure
out
what
they,
what
they're
about
just
go
ahead
and
ping
the
discord
channel
and
we'll
chime
in
and
help
you
get
the
details
on
that.
A
So
the
website,
if
you
want
to
or
and
the
documentation,
if
you
go
to
the
docs.
A
Oops
once
wrong
contributor
guide
and
then
how
to
tips
so
all
of
our
documentation,
whether
it's
and
and
the
website
use
hugo
as
our
server.
So
it's
really
easy.
Just
follow
the
steps
the
download
hugo
get
it
installed
locally
from
there.
You
just
fork
either
the
ortelia
stocks
or
the
or
to
this
week
website
and
you'll,
be
able
to
bring
it
down
and
make
the
the
changes
on
markdown
you'll
be
able
to
test
all
your
changes
locally
before
you
create
your
pr.
A
So
please,
if
you're
looking
for
somewhere
to
start
grab
one
of
those
and
let's
get
those
taken
off
of
the
our
list
for
hacktoberfest,
and
they,
though
you
know,
there's
an
easy
way
to
get
a
couple.
Pull
request
account
also
just
make
sure
before
you
do
that.
If
you're
interested
in
hacktoberfest
you
go
to
the
digitalocean
site
and
register
over
there,
we
do
have
captain,
I
mean
get
ops,
that's
gonna,
be
this
evening.
A
My
time
it's
gonna
be
8.
30
sydney,
time
in
australia
am
brad,
is
going
to
run
it
tonight
because
I'm
out
of
the
office
I'm
going
on
a
holiday
for
a
couple
days.
So
brad's
going
to
run
it
there's
there's
going
to
be
talk
about
the
captain.
Argo
sasha's,
writing
up
the
the
poc
diagram
and
that's
kind
of
what's
happening
on
that
front.
Who
cares
you
want
to
kind
of
give
a
little
highlight
of
what
you're
doing
with
the
the
captain
side.
E
Yep
so
we
have
like,
we
have
a
captain
environment
for
artelias
that
is
up
and
running
and
in
locally
I
tried
to
deploy
multi
staging
environments
and
we
were
doing
the
same
in
in
our
in
our
art,
alias
environment.
E
So
there
are
like
couple
of
configuration
that
needs
to
be
done,
so
brad
is
taking
care
of
those
things.
Apparently,
what
I'm
trying
to
do,
I'm
trying
on
multiple
reports
so
that
we
can
identify
any
changes
to
any
repos
and
after
that
we
can
do
the
health,
checkups
and
deployment
recording.
A
And
are
you
going
to
have
to
write
any?
I
think
they
call
them
in
kept
in
microservices.
As
like
event,
listeners.
E
Yes,
correct
correct,
so
currently
I'm
using
cli
commands
okay,
but
going
forward.
We
have
to
write
a
solution
for
that
because
we'll
be
using
the
apis
for
that.
A
Perfect
and
what
languages
are,
do
you
think
we'll
use
for
that?
Is
it
go
or
python
or
node.
E
Yeah
so
like
that
totally
depends
on
us,
so
there
are
just
because
there
are
flexibility.
There
are
samples
available,
so
we
can
use
go
or
python
anything.
A
Nice
excellent
and,
if
you're
interested
in
what
so
sash-
and
I
did
earl
on,
I
think
it
was
monday-
I
did
a
working
session
and
I
recorded
it
and
you'll
see
it
up
on
youtube.
A
So
it's
kind
of
the
the
high
a
walk
through
or
talk
about
the
the
flow
of
how
you
know
when
you
check
something
in
what
happens
to
kept
in
what
happens
to
artillius
and
argo
who
gets
who's
doing
what
updates
where
so,
if
you're
interested
in
kind
of
how
the
the
poc
is
going
to
fall
out
our
initial
pass,
you
can
look
at
that
video
and
sasha's,
putting
together
like
the
the
documentation
and
the
diagram
around
that
front,
so
that
is
out
there
for
you
to
take
a
look
at.
A
Those
are
the
two
big
things
that
we
have
going
on
right
now,
if
you're,
I
know,
there's
a
couple
issues
out
there
that
people
want
to
work
on
like
around
the
installation
process.
You
know
how
to
document
the
the
installation
process,
those
types
of
things:
how
to
set
up
a
local
environment.
Some
of
that
we're
waiting
for
like
the
it's
kind
of
like
a
prerequisite
to
figure
out
the
artifact
hub
before
we
can
go
out
and
figure
out
the
next
step.
A
So
there
we
are
backed
up
a
little
bit
on
that.
So
if
it
looks
like
you're
stalled
on
that,
please
grab
another
issue
to
work
on
and
get
your
prs
going
on
on
that
front,
any
questions
or
comments
or
if
I
missed
anything.
A
Oh,
I
know
that
the
you'll
see
on
the
discord
channel
for
the
builds
that
we're
getting
some
failures
showing
up
on
some
of
the
bills.
For
some
reason,
our
credentials
got
messed
up
again
with
azure,
so
I
have
to
look
to
see
what's
going
on
on
that
front,
one
of
the
things
I
I
kind
of
posted
over
to
utkarsh.
A
A
Is
if
we
go
into
there's
a
login
that
you
can
use
just
log
in
with
ortillius
as
the
username
and
artelius
as
the
password,
and
you
can
get
into
the
project
that
we're
using
for
ortelius.
So
this
is
where
you
can
see
all
the
websites
being
deployed.
The
versions
of
the
website
that
documentation,
those
are
the
in
artelias
itself.
A
So
you'll
see
like
the
devops
is
what
we're
the
application
that
we're
using
to
deploy
all
the
the
microservices
that
we
have.
So
in
this
case
we
have
our
six
microservices
that
are
being
deployed
at
that
level.
So
there
is
some
work
that
needs
to
be
done
on
this
front.
If
you're
interested
like
one
of
the
things
is
this
application
version
only
has
our
six
microservices
and
it
should
have
nine
what's
happening
is
in
like
in
the
cloud
build
piece.
A
It
is
getting
split
between
two
different
application
versions,
so
it's
just
a
little
tweak
that
we
need
to
do
so.
This
one
looks
better.
A
A
So
if
you
see
on
the
like
the
the
cloud
build
side
that
there's
something
happening
where
it
failed
and
it
like
gets
a
time
out
or
something
you
could
come
over
to
log
into
the
deploy
hub
console
here
and
we'll
see
what
we're
having
right
here
is
a
a
credentials
problem.
A
So
just
if
you're,
if
you're
interested,
if
you
want
to
get
more
into
understand
how
we're
using
deploy
hub
to
deploy
artelias,
which
is
basically
our
ortelius,
deploying
itself.
A
And
there's
some,
like,
I
said,
there's
some
cleanup
that
we
need
to
do
like
the
versions
are
coming
across
correctly:
the
application
versions
that
needs
to
be
cleaned
up
a
little
bit.
So
there's
there's
things
that
we
just
have
to
do
on
that
front
and
all
of
that
happens
at
the
the
cloud
build
stage.
A
So
what
ends
up
happening
in
our
our
build
process?
We
set
up
a
set
of
variables,
basically
to
say
this
is
the
the
the
the
application
name,
the
version,
the
component
that
we're
building
the
repo
the
chart
that
we're
gonna
use,
and
then
we
do
our
docker
build
here
and
tag
it.
This
also
push
it.
Let
me
turn
on
word
rep,
for
you.
A
So
that
does
the
the
the
build
and
the
push
over
to
quay
and
then
from
there
we
actually
call
our
deploy
hub
command
line
to
record
everything
on
the
deploy
hub
site,
and
then
this
will
also
down.
This
will,
in
turn,
do
the
deployment
of
everything
that
was
just
built
so
deal
with
the
whole
incremental
build
process.
A
So
if
we
just
change,
one
microservice,
like
ukrs
has
been
doing
like
validate
user
gets
updated,
we'll
just
go
ahead
and
deploy
just
validate
user
will
get
deployed
out
as
a
new
new
version
of
the
application.
So
this
is
like
one
of
the
things
that
we
need
to
add
to
all
the
charts.
A
Is
the
application
version
here
I'll
I'll
make
sure
to
open
an
issue
around
that,
but
there's
just
some
little
cleanup
that
we
need
to
do
on
that
front.
A
And
this
this
same
command
line
that
we're
using
here,
you
can
use
it
a
jenkins
pipeline
as
well,
so
this
this
basically,
this
dh
is
a
update.
Comp
is
a
python
program.
That's
in
the
ortus
repo
that
we
can
you
utilize.
It
makes
a
bunch
of
restful
api
calls
to
the
articles
and
a
server
side,
so
just
a
bunch
of
restful
stuff,
and
then
it
has
a
bunch
of
logic
on
how
to
deal
with
versions
and
iterating
things
and
figuring
out
what
to
do
next.
A
So
just
to
give
you
a
highlight
there
what's
happening
on
the
build
level,
but
that's
what's
happening
when
the
build
happens.
You'll
see
this
step
will
sometimes
time
out
or
it'll
get
in
air,
and
that's
where
you
can
go
over,
like
I
said
over
on
the
artelia
side,
the
deploy
up
side
and
look
at
the
login
with
artelias
and
you'll
be
good
to
go
any
questions
on
that.
I
hope
that
helps.
E
Just
one
question
here:
yeah
yeah,
so
we're
like.
Are
we
using
argo
cd
here?
Because
the
battery
is
showing
us
like
the
deploy,
have
used
the
cd
right.
A
Not
yet
so
what
this
is
doing
is
artelias
and
the
playhouse
both
have
a
deployment
engine
and
that
deployment
engine
understands
how
to
interact
with
helm
to
do
the
deployments.
A
So
one
of
the
things
that
we
do
is
there's
a
first
step
where
we
create
that
this
toml
file
and
basically
toml's
just
just
like
yaml,
it's
just
a
little
bit
easier
to
read-
and
this
is
your
values
file
and
that
values
file
is
the
basically
you
think
of
it
as
overrides
file
for
a
helm,
and
what
this
is
doing
is
it's
bringing
in
all
the
key
value
pairs
from
the
component,
application,
environment
and
endpoint.
A
A
So
when
we
go
to
deploy
to
the
dev
environment,
we
can
go
and
pull
down
the
cluster
name,
that's
associated
with
with
dev
versus
production
and
that
gets
dropped
into
this
values
file.
So
when
we
get
to
the
helm
part
which
is
down
here,
we
can
see
all
the
the
values
that
are
coming
across,
like
the
chart
name,
the
the
sha.
All
these
variables
are
going
to
be
exposed
to
helm
at
that
level.
A
Now
our
helm
templates
are
gonna
pick
up
things
like
the
docker
repo
will
be
a
variable
name,
that
our
helm
templates,
look
for
and
we'll
go
ahead
and
substitute
in
that
as
part
of
that
process.
A
So
it
makes
it
easy
for
us
to
do
a
helm
upgrade
basically,
which
is
happening
right
here
against
our
our
kubernetes
cluster,
and
that's
one
of
the
steps
that's
happening
up
here.
A
Is
it's
logging
in
to
kubernetes
and
that's
where
I
have
to
figure
out
why
our
credential
is
messed
up,
so
it's
logging
into
kubernetes
as
one
of
the
first
steps-
and
this
is
a
another
set
of
variables
that
come
from
the
environment
or
endpoint,
so
you
can
switch
cloud
providers
throughout
the
process,
so
you
can
mix
and
match
so
dev
could
be
on
azure
production
could
be
on
google.
It
doesn't
matter
to
us
now
in
the
get
ops
world.
A
This
values
file
information
instead
of
being
just
kept
locally
and
we
tell
helm
to
use
this
local
overrides
file.
This
overrides
data
will
be
checked
into
back
into
the
the
repo
and
then
argo
will
look
at.
Oh,
I
just
got
a
new
values
file
update.
Let
me
go
ahead
and
deploy
to
the
cluster
I
need
to
deploy
to
so
one
of
the
things
we
have
coming
down
the
road
for
other
updates.
A
Besides,
like
the
events
that
your
ukarsh
is
working
on
for
from
kept
inside
the
captain
side
on
the
github
side
and
we're
gonna
have
to
take
and
do
some
additional
like
github
commands
and
things
like
that,
and
maybe
interact
with
like
the
github
api
to
create
prs
and
things
like
that
and
automatically
approve
them.
But
basically
we
need
to
get
this
values
file
into
the
appropriate
repo.
So
argo
can
then
pick
it
up
and
start
running
with
it.
A
So
it
the
nice
thing
will
be
we
can
swap
and
what
ends
up
happening
is.
Instead
of
this
helm
upgrade
we'll
have
like
a
a
git
upgrade,
or
something
like
that.
You
know
our
git
ops
upgrade
and
we'll
basically
have
to
write
some
sort
of
command
line
to
do
that,
interaction
with
git
and
whether
we're
going
to
be
dealing
with
prs
or
for
directly
and
go
on
to
a
certain
branch.
That
type
of
thing
will
be
where
some
new
coding
that
we'll
need
to
do
down
the
road.
A
E
Yep
yep
so
like
I've,
got
an
idea
now
so
yeah.
This
helps.
A
Yeah
and
then
when
we
bring
in
the
the
whole
kept
in
events
process,
so
captain
events
allows
us
to
do
you
can
think
of
like
a
it's
another,
it's
event
driven
jenkins.
A
So,
instead
of
having
a
a
like
kind
of
like
a
hard-coded
pipeline,
you
can
create
more
of
a
dynamic
pipeline
using
the
the
kept
it
events
and
we
can
chain
things
together
and
have
things
go
in
parallel
at
that
level,
and
one
of
the
cool
things
that
they
have
in
kept
in
is
what
they
call
quality
gates.
A
So
what
we
can
and
part
of
this
is
what
karsh
is
working
on
is
we
can
deploy
into
into
qa,
for
example,
and
then
we
can
run
a
quality
gate
check
to
see
if
everything
tests
out
okay
and
if
it
doesn't,
then
we
can
go
ahead
and
roll
that
back
or
take
the
next
step.
If
it's
successful
the
quality
gate's
good,
then
we
can
move
up
to
production
at
that
level.
So
it
allows
us
to
really
automate
some
stuff,
pretty
slick.
A
All
right
well,
like
I
said,
please
pick
up
some
of
those
issues.
Some
of
them
are
pretty
low
hanging.
Fruit
grab
those
and
help
us
wrap
up
the
the
service
catalog
we're
we're
at
the
the
tail
end
here,
and
I
would
really
like
to
get
it
out
the
door
here
soon.
A
Yeah
well,
and
when
you
go
when
you
go
into
an
issue,
please
assign
yourself
just
so
that
we
don't
have
multiple
people
working
on
the
same
thing:
okay
and
then,
when
we
do
the
when
the
pull
request
comes
across,
we'll
add
the
labels
on
and
at
the
polar
cross
level.
So
you
get
your
you're
counted
for
hacktoberfest.
A
Alrighty
well,
thank
you,
everybody
and
reach
out.
If
you
need
anything,
even
though
I'll
be
taking
some
time
off,
I'll
still
keep
an
eye
on.
What's
happened
on
on
discord,
so
thanks
everybody
and
have
a
good
day.