►
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
Yeah
and
then
I
even
thought
about
it
at
the
next
level,
where
you
could
really
get
granular
and
let's
say
like
in
our
our
reporting
service,
we
access
three
tables
on
the
database
side.
We
could
create
a
view.
A
The
dbas
could
create
a
view
and
then
we'd
have
access
to
the
view,
so
we'd
actually
only
be
creating
up
against
the
view.
I
know
some
dbas
don't
like
to
deal
with
a
lot
of
views
and
there
are
some
that
do
because
then
they
get
to
control
the
queries
and
the
indexing
and
all
that
stuff
at
that
level.
But
then
the
idea
expanding
it
out
from
like
a
user
id
per
per
service
is
also
limiting
the
access
to
which
tables
that
user
id
would
have
access
to
instead
of
having
access
to
the
full
schema.
A
You'd
have
access
to
just
your
four
tables
that
you're
going
to
be
interacting
with
at
that
level.
So
that
was
the
the
next
kind
of
logical
step.
I
thought,
but
I
wasn't
sure
if
it
was
overkill,
doing
this
fine-grained
type
of
permissions
on
the
back
end,
any
thoughts.
C
Yeah,
when
I've
seen
people
try
to
to
do
things
at
that
level
of
granularity,
it
ends
up
being
more
of
a
maintenance
difficulty,
and
since
each
of
these
things
is
sort
of
a
demo-
and
it's
not
like
we're
expecting
there
to
be
a
lot
of
feature
drift,
we
might
be
able
to
live
with
that
sort
of
maintenance.
C
But
you
know
I,
I
think,
from
demoing
the
product
perspective
having
the
user
id
for
microservice
and
seeing
you
know
how
much
we
can
make
that
all
trailable
to
people
would
be
more
more
useful
from
the
achilles
perspective.
Okay,.
A
A
Okay,
so
initially
we'll
set
up
a
read
only
and
what
will
what
we'll
recognize?
I
think
right
now,
we'll
do
it
at
basically,
you
know
the
monolith.
A
The
monolith,
piece
of
or
artelia's
obviously
has
full
access,
because
it
does
all
the
different
transactions,
but
the
the
microservices
like
for
these
reports
would
be
a
read
only
and
we
just
share
that
same.
I
same
database
user
id
across
all
the
reporting
services.
A
B
So,
basically,
everything
that
we're
doing
in
terms
of
the
issues
we've
opened
for
the
reports
and
whatnot
every
we're
writing
everything
as
a
microservice.
At
this
point,
yep.
B
B
A
Yeah
the
just
to
give
you
an
idea,
the
there's
a
hundred-
and
I
think
I
counted
130
tables
that
are
used
to
run
our
ortelius.
So
you
could
think
of
130
microservices
at
the
minimum.
A
Yep,
so
that
was
on
the
architecture,
so
that's
moving
along
we'll
get
the
the
database
connection
out
there
as
part
of
that
things,
like
the
the
cloud
build
pieces
are
coming
into
play.
I
believe,
like
aisha,
and
I
want
to
say,
segar
are
working
on
home
charts
for
these
services
they're
going
to
work
on
it
over
the
weekend
coming
up.
A
So
that's
moving
along
we're
doing
a
a
build
upon
approach,
so
we're
gonna,
take
our
dummy,
flask
and
we're
gonna
build
upon
it.
So
everybody
that's
been
interested
wants
to
learn
from
from
the
very
you
know,
check
in
and
start
coding
all
the
way
through
the
whole
process,
all
the
way
to
deployment
and
monitoring.
So
we're
going
to
take
everybody
through
that
that
process.
Everybody
learns
a
little
bit
of
of
the
whole
devops
world
out
here
on
to
the.
A
I
did
reach
out,
I'm
still
we're
trying
to
reach
out
to
open
source
communities
that
are
creating
microservices.
A
The
parts
I'm
thinking
of
right
now
that
we're
trying
to
reach
out
to
our
scientific
labs,
doe
dod
here
in
the
states,
universities
that
may
be
doing
some
sort
of
research,
scientific
research
based
on
kubernetes
at
that
level
and
then
also
on
the
what
I
was
calling
the
the
financial
side
of
things.
You
know
there's
some
economic
models
out
there
that
they're
running
through
kubernetes
as
well
from
the
universities.
A
You
know
those
those
types
of
of
groups
we
want
to
reach
out
to.
So,
if
you
have
any,
you
know
if
your
alumni
have
a
university
and
get
their
their,
you
know
monthly
newsletter
or
something
like
that
from
your
cs,
department
or
econ
department.
You
know
just
take
a
look
to
see
if
they
have
any
projects
that
we
can
maybe
hook
into
as
part
of
that
process.
A
A
I
want
to
figure
out
if
we
want
to
call
it
a
marketplace
or
a
catalog,
so
we
don't
have
to
do
it
today
because
we're
running
kind
of
late
here,
but
think
about
that
for
next
time
the
we
just
need
to
stand
up
to
standardize
on
it.
A
So
we
can
get
all
the
documentation,
all
the
positioning
and
the
outreach
and
all
that
stuff
in
place
marketplace.
For
example,
you
have
like
the
google
marketplace.
I
don't
know,
remember
christopher
what
does
aws
call
their
stuff?
C
I
think
like
for
the,
I
am
images
and
stuff:
it's
a
marketplace.
Okay,
you
know
and.
D
C
C
But
but
you
know
I
I
I
hate
to
throw
rocks
and
class
houses
against
old
people,
but.
B
Well,
tech
town's
using
the
term
catalog
for
their
sort
of
their
plugins
right,
but
when
you
think
about
apis
you,
you
really
think
of
an
api
marketplace.
B
A
A
I
mean
on
a
new
the
new
term
side.
You
know
the
domain
driven
design
is
based
on
patterns,
so
we
can
think
that
way
as
well,
because
that's
what
we're
really
talking
about
is
is
domain
driven
design.
B
Let's
talk
about
my
biggest
concern
for
ortillius
right
now,
which
I
think
it's
you
know
it's
going
to
be
our
biggest
thing
to
overcome,
and
that
is
adoption
like
I
said,
the
I've
asked
the
outreach
committee
to
each
for
each
of
them
to
kind
of
work
through
signing
on
to
orterius
through
the
deploy
hub
team
environment
and
go
through
the
tutorial.
B
But
what
I
feel
like
this
group
we
need
to
make
was
one
of
our
our
primary
goals
initially
is
to
make
sure
that
the
tool
is
easy
to
use
and
where
are
the
problems.
So
this
is
something
that
steve
and
I
have
struggled
with
because
we
are
too
close
to
it.
We
can't
see
what
we
we
already
know,
it's
hard
to
it's
hard
to
forget
how
the
tool
works.
So
you
already
know
the.
D
B
And
we
need
to
find
out
from
the
open
this
community
what
we
need
to
address
from
a
usability
standpoint
and
if
we
need
to
start
thinking
about
making
those
making
those
changes
a
priority.
B
So
we
we
really
need
your
input
on
this.
If
we
can
get
some
feedback
from
you
over
the
next
two
weeks
and
how
we
can
make
it
an
easier
tool
to
use
the
thing
is
we
we've
talked
to
people
who
you
know
are
pretty
sharp
and
they
catch
on
really
quickly
and
then
other
people
they
struggle
with
it.
We're
not
sure
why,
but
we
we
do
need
to
address
it,
and
any
conversation
in
this
group
would
be
great.
B
And
and
doing
things
like
christopher's
thinking
about
in
terms
of
onboarding,
making
it
doing
something
more
automated
to
go
out
and
look
at
it.
Look
in
a
cluster
and
try
to
figure
out
what
the
applications
are
and
bring
that
information
back
in
into
artelia,
so
that
when
people
first
start
using
it
they're
sort
of
a
automatic
integration
to
their
existing
cluster.
A
That
way,
they
can
actually
start
visualizing
what
they
have
as
a
starting
point.
You
know,
building
out
these
these
relationships
even.
A
Be
100
accurate,
you
know,
based
on
a
name
space
or
something
like
that.
We
can
re,
make
the
association
that
type
of
thing.
So
that
was
one
part
I
I
was
thinking
of.
Is
we
get
some
data
loaded
in
really
quickly
that
people
can
start
looking
at.
B
D
Sure
so,
back
about
the
user
accounts
and
stuff
figuring
out
how
some,
how
to
contain
groups
for
groups
of
microservices
application,
stacks
of
microservices,
grouped
together
or
user
communities
or
those
kinds
of
things
a
service
account
in
the
database
for
scoping.
D
A
group
of
microservices
for
a
specific
task
might
be
useful:
okay,
cool
also
about
the
documentation
and
how
we
bring
people
on
board.
D
Any
use
cases
we
can
think
of
might
be
a
good
idea
to
stick
in
a
tracker
of
some
sort,
things
that
we
could
do.
Our
video
tutorials
or
you
know
somebody
familiar
with
the
project-
could
do
video,
tutorials
or
suggest
tutorial
documents
with
screenshots
or
those
kinds
of
things
might
be
a
good
idea,
but
definitely
if
we
could
track
them
in
some
kind
of
ticket
or
tracker.
A
Cool
now
I
was
thinking
on
the
we
have
the
now
this
is,
I
don't
know
if
this
is
the
right
right
place
to
put
it,
but
on
the
let's
say,
you're
in
jenkins,
and
you
have
your
ci
build,
that's
creating
your
docker
container.
We
have
a
plug-in
that
we
can.
We
can
slim
down.
So
it's
maybe
like
two
or
three
lines
of
code
that
we
could
throw
in
your
jenkins
pipeline
and
we
can
start
recording
stuff
out
of
your
pipeline
and
populating
into
artelias
at
the
component
version
level.
A
Information.
That's
coming
out
of
your
ci
process.
A
I
don't
know
if
that
would
be
a
good
starting
point
for
understanding
how
what
the
benefit
of
what
artelias
is
or
if
we
should
start
from,
like
I
said,
the
the
cluster
side
and
work
backwards,
we'll
need
to
marry
the
two
together
eventually,
so
we
can
start
anything
coming
out
of
the
ci
process,
we'll
be
creating
new
versions
of
of
components
and
new
versions
of
applications
that
people
can
track
at
that
level.
A
C
I
mean,
I
think
each
route
works
for
different
sets
of
people.
You
know
for
the
people
that
are
spending
their
time
doing,
release
engineering,
throwing
the
thing
into
jenkins
is
a
no-brainer
and
easy,
but
you
know
if
you're,
not
in
the
group
of
people,
that's
doing
the
release
engineering
having
some
other
route
into
it
is
probably
better.
So
you
don't
have
to
mess
with
that
part
of
it.
A
A
A
B
Yeah
and
I
she's
not
on
this
call
today,
but
I
believe
that
nitu
is
also
working
on
trying
to
really
define
the
personas.
A
A
Yeah
she
has
a
conflict
for
this
meeting
cool.
That's
a
great
idea.
We
can
narrow
it
down
and,
like,
like
roy,
said
that
we
could
create
a
tutorial
for
each
persona
how
to
get
started.
B
A
I
like
to
keep
it
to
like
three
to
four
personas
instead
of
like
10.
You
know
that
just
saves
us
work,
even
though
there
would
be
overlap,
but
if
we
could
figure
out
three
to
four
personas
to
start
with
and
see
how
it
goes.
B
I
guess
the
question
is
of
for
those
of
you
who,
for
all
of
us
on
here
how
many
of
you
have
actually
signed
up
and
gone
through
like
the
first
hour
to
see.
A
Yeah
one
of
the
things
I
know
that
there
is
we'll
run
into
problems
with
the
bridge
between
wordpress
and
ortelius,
or
deploy
help
on
the
back
end
with
the
sign
up
process,
and
that
definitely
has
to
be
changed
up.
B
We
were
trying
not
to
do
too
much
at
this
point
because
we
did
have
our
meeting
with
the
cd
foundation
went
really
well
they're,
pretty
excited
about
the
prospects
of
bringing
artillius
in
they're.
Gonna
have
a
do
another
call
on
it
with
that,
probably
without
a
song
on
the
phone,
because
if
it
then
we
could
build
that
we
could
get
funding
from
the
cd
foundation
to
build
it
out
on
the
on
their
in
their
environment
in
their
google
environment.
B
I
think
they
have
jenkins
running
in
a
google
environment
there,
so
we
could
add
ourselves
up
there
and
then
we
need
to
build
out
the
sign
ups
around
artillius
through
that.
B
But
right
now
we're
we're
hosting
it
ourselves,
and
I
don't
think
that
the
bridge
is
you
know
was
the
only
concern
that
people
had,
though.
So
if
you
go
through
it,
if
you
have,
you
can
give
us
a
list
of
things
that
we
need
to
take
a
look
at.
This
would
be
a
good
time
to
do
it.
A
And
if
and
if
something
breaks,
let's
get
an
issue
open
and
we'll
we
can
see
if
that's
a
common
thread
that
people
are
tripping
over.
So
even
if,
if,
if
you
run
into
a
problem,
the
issues
are
out
there
just
go
ahead
and
either
update
that
issue.
Saying
you
had
the
same
thing
or
you
know
create
another
one.
B
And
then
has
anybody
finished
a
pull
request
for
hacktoberfest.
E
E
B
E
A
A
B
And
just
one
more
question:
if
anybody
needs
to
help
on
getting
those
getting
those
pull
requests
in
do
reach
out.
I
know
that
some
of
you
are
working
on
some
of
the
stuff.
So
let's
make
sure
that,
as
many
of
you
can
can
get
your
your
four
pull
requests
in
and
if
we
need
to
create
more
pull
requests
for
hacktoberfest
just
go
ahead
and
create
an
issue
and
and
put
hacktoberfest
on
it,
and
then
you
do
the
pull
request.
B
Well,
they
said
that
they
were
going
to
try
to
do
it
faster
because
they
I
I
know
that
they
said
there
were
so
many
people
participating
this
year,
we're
all
bored
we're
all
having
fun
talking
to
people
virtually.