►
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,
so
it's
being
recorded
now,
so
the
need
to
nito
and
tracy
started
working
on
the
persona
piece.
I
think
we
need
to
break
that
out
as
a
new
document,
so
we
can
right
now
it's
in
a
github
issue.
I
think
we
need
to
break
out
as
a
document.
B
A
I'd
to
do
is,
like
you
said,
the
collaboration's
a
lot
easier
on
the
google
doc
and
then
we'll
once
it
gets
solidified
move
it
to
markdown.
So
I
think
this
the
personas
are
really
going
to
start
driving.
Some
of
these.
A
You
know
it's
going
to
drive
the
sign
up
process
and
basically
the
getting
started
process
is
going
to
be
driven
by
the
personas.
You
know.
So,
if
we
have
somebody,
that's
a
developer
they're
going
to
have
you
know
a
different
view
of
the
world
versus
something
that's
jenkins:
admin
versus
somebody.
That's
looking
at
sre
doing
log
file,
analysis
and
those
types
of
things.
A
So
I
think
the
next
step
is
to
really
look
at
the
personas
get
those
broken
out
and
how
we,
how
it's
going
to
affect
the
sign
up
process
and
how
we
get
people
going
at
the
start
and
what
they
want
us
what
they
need
to
see.
You
know
the
data
is
there?
What
we
need
to
make
sure
is
that
we're
getting
to
the
data
to
the
right
person,
so
they
they,
they
can
see
the
value
and
and
artelias.
C
A
So
the
big
things
that
we
want
to
focus
on
is
adoption
tracy
your
column,
your
your
big
rocks.
C
Yep,
so
I'm
writing
down
the
stuff
that
you
guys
have
just
been
talking
about,
because,
obviously
that's
what
you
guys
want
to
focus
on
so
goals,
I
would
say
for
q1
and
q2
goals
for
q1
and
q2.
C
I
would
say
that
the
website
redesign
that's
gotten
a
lot
of
attention.
We're
meeting
with
mark
waite
on
friday
tomorrow
morning,
he's
going
to
go
through
how
they
did
jenkins,
which
is
awesome
that
they're
doing
that
for
us
and
then
one
of
my
areas
I
feel
like
we
need
to
work
on
is
the
the
data,
how
we're
displaying
the
data.
I
think
that
our
maps
look
great,
but
I
don't
know
if
they're
going
to
be
able
to
handle
as
much
data
as
they
need
to
so
we
did
it.
C
There
was
a
argo
presentation
and
I
thought
some
of
the
argo
visualizations
were
pretty
interesting,
that
they
were,
they
were
doing
it
and
then
the
third
one
for
q1
and
q2
would
be
to
to
you
know,
increase
adoption
by
using
some
kind
of
scraping
of
aws
gke.
A
C
For
q3
and
four
right
now
is
to
get
a
our
first
marketplace
published.
That
may
happen
sooner
if
we
could
do
something
with
sandia,
but
I
think
that
one
before
we
run
down
that
too
fast,
we
really
need
to
get
the
visualizations
clean,
and
then
we
need
to
work
on
start
working
on
converting
all
that
dm
script
over
to
python.
C
So
I
broke
them
down
into
two.
You
know
six
month
period,
six
months.
I
think
that
those
three
are
pretty
doable
for
the
first
first
half
of
the
year.
C
C
And
if
anybody
else
has
any
other
ideas.
C
C
Well,
we
have,
you
know,
I'm
working
on
them
now,
because
I
think
that
by
december
1st
we're
all
going
to
go
mushy.
C
So
if
we
can,
you
know
sort
this
sort
them
out
for
the
team
to
understand
what
needs
what
we
know.
I
know
for
sure
that
ortillius
cat
we
have
to
get
out
of
dm
script.
That's
a
big
one!
It's
you
know
that
if
we
can,
if
we
can
get
a
few
of
the
python
convert
a
few
of
those
dm
script,
dm
script
is,
let
me
show
steve:
would
you
bring
up
the
documentation
and
show
the
dm
script
documentation
yeah.
D
C
The
person
his
name
was
phil
gibbs.
He
worked
for
openmake
software,
we
acquired
his
agentless
engine
several
years
back
and
he
wrote
it
and
we've
never
liked
it.
He
was
pretty
attached
to
it
because
he
wrote
it
and
you
know
that's
good
we're
weird.
C
You
know
he
wrote
quite
a
bit.
It
was
really
before
you
know
he
was
trying
to
write
a
language
specific
to
doing
deployments
and
the
problem
with
it
is
that
you
have
to
learn
it
and
if
we
can
convert
it
into
some
of
these
calls
into
python,
even
if
they're,
some
of
the
core,
the
the
ones
that
are
more
frequently
used,
it'll,
be
a
lot
easier
for
people
to
to
use
the
product
and
customize
around
it.
C
A
And
it's
a
funky
language.
Basically,
what
it's
the
the
goal
of
it
is
is
when
we
do
a
deployment,
there's
a
stack
of
objects
that
are
available
so
at
the
highest
level
you
have
an
environment
which
is
which
contains
a
set
of
endpoints
and
you
deploy
a
version
of
an
application
to
an
environment,
and
when
you,
when
you
do
that
process,
any
of
the
key
value
pairs
at
the
environment
level
are
put
on
the
on
the
stack
and
then
the
application
versions
are
put.
A
Those
variables
are
put
in
the
stack
and
then
a
component
version
is
contained
in
application
version.
So
now
we
loop
through
all
the
components
for
this
application
version,
and
each
component
is
actually
tied
to
an
endpoint
in
the
environment
and
the
endpoint
has
attributes.
So
it
brings
builds
up
this
stack
of
all
these
values
that
we
get
to
use
and
allows
us
to
really
do
some
nice
logical
deployments.
A
You
know
through
the
process,
and
this
allows
us
to
really
separate
the
data
from
the
definition.
So,
for
example,
you
can
have
your
dev
cluster
could
be
in
mini
cube.
Your
qa
cluster
could
be
in
aks
and
your
production
one
is
going
to
be
in
eks.
A
The
only
difference
between
those
those
environments
is
literally
how
you
connect
to
the
cluster,
so
you
can
actually
set
those
those
variables
up
those
key
value
pairs
at
the
environment
level,
then
the
application
and
all
the
underlying
deployment
scripts
just
get
passed
in.
Oh
I'm,
on
aks.
Now
I
need
to
go
grab
these
variables
set
up.
Do
my
call
to
aks
to
authenticate
and
from
there
on
out
once
I've
authenticated
and
converted
my
cube
cuddle
config,
I'm
ready
to
go
with
the
regular
process.
A
So
that's
the
thought
process
of
where
it
came
from.
You
know,
there's.
If
you
get
into
the
c
code,
there's
there's
yak
compilers
that
and
lex
the
deal
with
this,
the
scripting
language
that
they
created.
A
It's
a
nightmare
to
debug,
believe
me
going
through
and
trying
to
figure
out
when
something
breaks
and
the
goal
would
be
to
trans.
Probably,
it
looks
like
moving
this
over
to
python
as
the
language
and
the
reason
being
is
python.
Has
the
ability
to
do
an
evaluation
on
the
fly
of
some
some
strings
of
code,
so
we
can
actually
do
inject
things
and
still
follow
those
stack,
but
inject
user
defined
procedures
and
functions
and
stuff
like
that
into
the
deployment
process.
D
No,
no,
no,
no,
I'm
really
glad
we're
having
this
conversation
now.
This
is
great,
so
there's
a
couple
things
that
I
wanted
to
bring
up
in
this.
So
one
is
that
I
found
two
other
examples
of
dm
script
on
the
web:
there's
one
that's
being
used
for
crypto
stuff
and
the
w3
used
it
for
this
dialog
manager
script,
and
so
I
thought
that
was
just
hilarious,
that
the
name
has
has
been
reused
at
least
three
times
that
we
can
find
in
five
minutes.
So
that's
awesome.
A
Yeah
and
the
reason
why
it's
called
dm
script,
the
so
the
original
product
that
open
make
software
bought
from
phil
gibbs
was
called
deployment
manager
and
it
was
tied
very
tightly
into
the
ca
harvest
scm
product.
A
So
they
did
a
bunch
of
allowing
the
the
ca
product
to
do
deployments
from
when
you
do
a
check
in
or
promote.
You
know
they
have
a
whole
life
cycle
model
in
harvest,
so
it
was
actually
called
deployment
manager.
Then
you'll
see
that
we
renamed
it
somewhere
along
the
way
to
release
engineer
and
then
finally
got
renamed
one
last
time
to
deploy
hub
and
then
torotelius
as
we
split
it
out.
It's
the
marketing
people
tracy.
C
C
Is
what
we
were
interested
in
because
it
the
way
it
stacks
things?
It's
able
to
also
incrementally
deploy
things
and
for
microservices.
That's
really
what
was
needed
to
be
able
to
not
take
a
whole
monolith
and
say
I
have
to
redeploy
everything
in
this
and
just
redeploy
environment
variables,
even
in
a
monolithic
environment
where
you
just
want
to
change
environment
variables.
C
So
that's
what
we
were
attracted
to
and
that
it
turns
out.
It
was
it's.
It
actually
is
a
very
perfect
solution
for
microservices
platform.
A
And
you'll
see
you'll
see
some
some
things
that
are
really
nice
like
a
restful
get
is
literally
a
one-liner
and
it
returns
a
json
string
for
you.
So
there's
some
power
in
the
language,
but
this
can
be
replaced
with
a
few
lines
of
python
code.
D
A
No,
we
would
want
to
replace
all
the
c
code
with
another
language
I
just
been
going
to
python
as
a
default.
It
doesn't,
you
know,
go
may
be
better
suited
for
it.
We'll
have
to
see
when
we
go
to
tackle
this.
D
D
A
Yeah
and
that's
one
of
the
things
it
doesn't
have
to
be
super
fast
and
the
other
part
is
when
we
do
a
deployment
under
the
covers.
When
we're
talking
kubernetes
we're
interacting
with
helm.
We
have,
we
can't
interact
with
the
operator,
but
we
haven't
gone
there
yet
and
then
also
on,
like
regular
file
deployments,
we
need
to
move
like
a
jar
file
out
or
do
like
a
iis
website.
Then
we're
just
actually
interacting
with
ansible
and
ansible's
all
based
on
python.
D
C
It
is
a
big
project,
but
if
go
is
going
to
be
more
appropriate,
I
I
say
we,
and
sometimes
you
know
it's
what
we.
What
do
we
want
to
learn
as
a
community,
because
we're
trying
to
do
this
as
a
learning
effort
as
well.
So
if
go
is
a
good
place
to
if
that's
a
good
solute,
a
good
alternative,
and
we
all
think
yeah
we'd
like
to
learn
go.
I
think
we
should
do
go.
A
Well,
I
think,
realistically,
we
had
to
look
at
adoption.
That's
what
it's
going
to
come
back
to
if
they're,
if,
if
somebody
having
to
learn,
go
to
go
ahead
and
customize
artelias
is
a
barrier
we
need
to
consider
that
that's
like
like
russ
could
be
really
cool,
but
you
know
it's
one
of
those.
You
know
I
could
learn
in
a
couple
hours,
but
it's
one
of
those.
What
can
other
people
do
with
it?.
D
A
A
Well,
need
to
just
said:
go
is
becoming
more
popular
and
good
for
people's
resumes.
G
A
Cool
need
to
really
quick,
I
don't
know
if
you
jumped
on,
but
we
are
going
to
break
out
the
personas
into
a
separate
google
doc,
so
we
can
get
a
bunch
of
people
contributing
on
it.
C
I
I
responded
to
you
so
if
you
want
to
just
cut
and
paste
that
big
paragraph,
that
I
wrote
that
broke
out
the
initial
ones
and
put
it
in
a
google
doc
and
then
we
can
start
collaborating
from
there.
G
Sounds
good
yeah
I
just
was
thinking
that
I
can
start
interviewing
some
people
and
you
know,
try
to
flush
it
out
and
then
leave
it
out.
I
I
don't
know,
let
me
see
what
you
have
posted.
I'm.
C
Just
shooting
glasses,
I
wrote
I
wrote
a
bunch
about
that.
You
know
just
all
of
my
thoughts.
You
know
on
the
different
people
that
we
have
worked
with,
so
I
think
that
can
be
a
good
starting
point
for
a
shared
doc.
C
Just
put
it
under
oh,
create
a
brand
new
one
under
under
the
ortillius
group,
google
group,
okay,
and
that
way
everybody
will
get
it
automatically.
If
you
create,
you
should
have
access
to
be
able
to
create,
create
it
under
a
google
group.
A
So
anything
else,
we've
gone
over
a
little
bit
today.
C
C
It's
great:
it's
awesome,
the
work
that
you've
been
doing
good
job.
What
do
you
think
about?
What
are
you
thinking
about
different
languages
that
we
might
want
to
use
to
convert
all
of
this
scripted
code
in?
Do
you
think
you
would
would
be
what
what?
What
are
the
people
in
your
ar
you're
in
school
right
now,
right.
C
F
So
if,
if
you
ask
my
preference,
so
I
have
been
doing
node.js
for
quite
a
while,
I
haven't
done
development
lately,
but
if
I
have
to
pick
based
on
my
personal
preference,
then
I
I
would
say
I
would
rather
go
rather
go
with
go
because
yeah,
it's.
I
think
it's
it's
more
popular
these
days
and
yes,
I
think
it
would
be
python
is
like
I
think
it's
I
don't
know
it's
like
too
mainstream.
Maybe
we
it's
been
used
a
lot,
so
I
think
we
should
we
should.
C
C
A
So
helm
is
written
in,
go
as
well
as
tekton
are
both
written
same
with
kubernetes.
C
All
of
microsoft,
that's
right
all
right!
Well,
I
have
I'm
going
to
update
the
the
goals
on
the
front
page
to
the
ones
that
we
discussed.
If
anybody
has
any
changes
that
they
want
to
make,
this
is
always
a
living
document,
but
we'll
get
them
at
least
to
find
those
five
top
goals.
Three
in
the
first
two
quarters
and
two
in
the
last
and
being
that
the
two
in
the
last
has
this
this
conversion
to
go
in
it,
and
certainly
we
can
you
know
we
can
have.
C
We
can
get
somebody
started
on
it,
so
we
can
figure
out
how
it's
going
to
get
done
and
then
we'll
be
able
to
create
issues
and
have
each
of
those
those
call
those
dm
functions
as
issues
to
work
on.
C
It's
gonna
take
us
a
year
to
do
it.
Let's
just
put
it
that
way:
it's
not
it's
not
an
easy
project.
Now,
one
last
thing:
I
know
you
guys.
I
I
want
to
first
thank
all
of
you
for
being
on
this
call.
We've
had
way
too
many
ortillius
calls
this
week.
So
thank
you
very
much
for
attending
them
and
if
you
attended
the
cdf
one,
thank
you.
It
made
a
big
difference
to
have
so
many.
C
You
know,
as
I
called
you
guys,
the
mappers
on
the
call
it
was
noted
to
tracy
miranda,
sent
me
a
email
and
said
wow
you
have
you
have
a
you:
have
a
devoted
community
there!
That's
awesome!
C
There
is
another
one
happening
in
40
minutes:
it's
the
interoperability.
They
want
to
see
ortillius
there,
I'm
going
to
put
the
oops.
That's
not
what
I
wanted
to
do.
I'll
put
the
I'm
going
to
put
the
link
in
the
chat,
and
I
will
also
put
it
in
discourse.
So
if
you're
interested
you're
welcome
to
come
great,
but
I
know
everybody
has
work
to
do.
A
And
just
let
everybody
know
this
doing
some
coding,
I
will
have
some
stuff
for
you
to
bring
in
around
database
queries
for
our
microservices,
so
keep
a
heads
up
on
that.
I'm
gonna
try
to
get
that
out
either
today
or
tomorrow.
So
we'll
be
good
to
go.
C
D
The
guy
that
came
after
you
that
had
this
beautiful
long,
white
hair,
yes
had
the
the
these
four
monitors
behind
him
that
were
running
the
the
matrix
screen
saved
like
wow,
and
we
all
need
that
office
background.
I
mean
you
look
like
you
know
what
the
hell
you're
doing
when
you've
got
that
stuff
behind
you.
That's
like
really
sharp
yeah
dan
was.
D
C
C
A
All
right,
no
problem
all
right.
Well,
thank
you,
everybody
and
if
you
have
any
I'll
for
the
people
who
are
doing
the
microservice
coding,
I'll
sort
things
out
on
discord
here
shortly,
thank
you.
Everybody
have
a
good
weekend.
All.