►
From YouTube: Ortelius Kick-off Meeting - July 21, 2020
Description
This is a recording of the initial kick-off meeting for the Ortelius open source project. It introduces the Ortelius solution, reviews goals, focuses on creating an inclusive community and introduces Marky Jackson (@MarkyJackson5) Community Manager, Tracy Ragan (@TracyRagan) Exec. Director and Steve Taylor (@SBTaylor15) Chief Architect.
A
All
right,
everybody
huge
thanks
to
all
of
you
for
showing
up
today,
I
have
been
on
a
mission
to
speak
to
as
many
people
as
possible
about
microservices,
where
their
heads
are
at,
if
they're,
using
them.
What
challenges
they're
having
I
have
probably
spoken
to
on
average
five
people
a
day
in
the
course
of
the
last
six
weeks
and
I
have
spoken
to
some
really
amazing
people-
and
many
of
you
are
here
today.
A
A
My
most
of
you
have
met
me.
I'm,
Tracy,
Reagan
I
am
the
CEO
of
deploy
hub
and
the
executive
director
of
our
project.
Here
our
Tilly
is
open-source
project.
I
have
not
new
to
governance.
Around
open-source
I've
been
on
the
Eclipse,
Foundation
and
I
have
been
I
am
now
on
the
CD
Foundation
Steve
Taylor
is
our
chief
architect.
He
was
the
creator
deploy
hub.
He
and
another
individual
by
the
name
of
Phil
Gibbs,
who
is
now
on
our
Technology
Oversight
Committee.
They
created
it
as
initially
as
a
release,
automation
solution.
A
Since
that
time
we
have
could
have
split
the
code
and
and
really
focused
some
of
its
really
cool
features
that
we
thought
were
really
cool.
Around
monolithic
release,
automation
when
it
came
to
what
we
were
calling
incremental
releases.
We
realized
that
we
were
actually
building
a
tool
for
micro
service
and
we
just
didn't
know
it.
Yet.
A
He
is
also
word:
does
some
contribution
and
and
sits
on
the
Tecton
meetings?
As
a
you
know,
it's
kind
of
a
CD
focus
and
on
a
spare
time
he
is
a
volunteer
he's
a
chief
of
the
local
volunteer
fire
department,
so
he
is
our
local
hero.
We
also
have
Marquis
accident.
I
am
so
excited
to
be
introducing
Marky
Jackson
as
our
community
manager,
even
though
I
have
experience
from
a
governance
level
from
open
source
I
have
absolutely
no
idea
how
to
run
an
open
source.
A
community
itself
I
have
never
worked
or
contributed
to
projects.
A
I've
only
worked
at
the
board
level
for
these.
For
these.
For
these
open
source
projects,
so
we're
having
marki
volunteer
for
this
project
has
been
a
it's
been
an
amazing
lucky
turn
of
events.
For
us
he
really
is
I
would
call
an
open
source
guru.
He
is
also
the
director
of
open
source
software,
a
table
some
X,
and
he
has
been
a
contributor
for
many
tools,
including
jenkins,
falco,
kubernetes,
Jenkins,
x
and
screwdriver,
and
he's
going
to
talk
a
little
later
and
introduce
himself.
A
So
this
is
why
we
started
getting
into
micro
services.
You
know
it's,
it's
not
just
the
numbers
of
what
this
market
looks
like,
but
the
market
reflects
where
people's
heads
are
at
you
know.
Monolithic
has
been
with
us
for
quite
some
time
and
everything
we
do
is
baked
in
it.
But
now,
when
we
shift
to
micro
services,
it
means
that
we
have
some
disruption
that
we
have
to
address
and
where
we
see
most
of
the
money
going
is
not
in
how
to
make
how
to
make
it
easy
to
build
applications
of
micro
services.
A
The
money
isn't
how
to
build
out
kubernetes
clusters,
that's
where
everybody's
focused
it
is
currently
at
which
means
there's
a
lot
of
challenges
for
at
the
application
level,
and
this
project
is
to
make
those
challenges
and
go
away
and
make
it
easy
to
implement
micro
services
just
to
kind
of
reframe
the
problem
that
we
want
to
solve
with
this
open
source
project.
This
is
what
a
monolithic
CD
pipeline
looks
like
everything
you
do
in
terms
of
software.
Configuration
management
is
done
at
the
devastate
when
you
do
traditional
CI
or
even,
if
you're
not
doing
CI.
A
If
you're
just
compiling
your
code,
the
process
of
compiling
and
linking
code
and
creating
a
package
is
indeed
a
monolithic
that
is
being
completely
disrupted
in
a
micro
service
environment.
We
no
longer
will
have
this
smart
person
sitting
in
the
corner,
worrying
about
what
what
file
is
to
pull
out,
what
files
to
compile
what
libraries
to
link
creating
our
package
so
that
we
can
carefully
push
it
across
the
lifecycle
that
is
going
away
and,
in
some
respect,
we're
going
to
see
even
the
wat.
A
This
waterfall
approach,
this
dev
test,
prod
approach,
go
away
in
the
coming
years
as
things
like
service
measures
become
more
prevalent,
so,
instead
of
having
a
static
software
application
package,
we're
going
to
take
it
and
we're
going
to
blast
it
into
many
little
pieces.
So
the
static
application
pack
is
just
being
broken
into
these
smaller
pieces
and
that's
what
micro
services
are.
So
we
still
have
to
have
a
way
of
understanding
what
the
application
is,
even
though
somebody's
pointing
to
it
and
saying
hey
that
pile
of
glass.
A
That's
your
wine
glass
and,
if
you
think
about
what
that
means,
it
means
that
there
are
micro
services
in
different
states
of
the
lifecycle
all
being
pushed
out
to
be
seen
as
a
complete
package.
But
we
don't
do
that
package
anymore.
It
goes
away,
so
we
lose
the
the
logical
view
of
an
application
and
there's
no
software
configuration
management
done.
A
So
we're
here
to
reimagine
software
delivery
and
when
I
say
software
delivery,
it's
not
just
deployments.
It
is
the
process
of
progressing
a
change
from
a
from
inception
to
an
end
user
consumption
and
returning
to
these
some
of
these
critical
concepts
and
applying
those
critical
concepts
to
modern
architecture
is
what
we
want
to
achieve.
A
So
some
of
you
have
seen
deploy
hub.
We
are
in
the
process
of
rebranding
the
deploy
hub
team
to
an
appropriate
art
ileus,
but
what
we're
doing
with
with
ortelius
is
recreating
a
centralized
hub
for
putting
the
application
back
into
them
into
a
micro
service
architecture.
We
want
to
create
a
central
marketplace
for
sharing
and
versioning
service
to
their
applications,
which
means
that
we
could
potentially
grow
this
so
that
the
way
the
SAS
environment
works.
It
has
something
called
a
global
domain.
A
We
could
start
allowing
everybody
to
publish
micro
services
to
that
to
a
high
level
global
domain
that
can
be
shared
across
organizations,
think
about
github
and
the
way
that
they
have
pushed
the
open-source
community
to
centralize
their
source
code.
We
would
like
to
follow
suit
and
understand
that
that
was
an
important
feature
of
github
and
it
can
be
an
important
feature
of
ortelius
as
well.
A
If
we
open
it
up
and
allow
people
to
share
micro
services
and,
in
the
end
of
the
day,
our
real
goal
is
to
create
a
simplified
process
for
achieving
business
agility
through
a
Microsoft
architecture.
And
what
we're
finding
is
that,
while
some
people
are
really
good
at
managing
eat,
even
up
to
100
micro
services,
there's
some
core
problems
that
they're
running
into
that
we
want
to
understand
and
that
we
want
to.
We
want
to
address.
A
So
how
did
we
get
the
name?
Abraham
ortelius
created
the
first
world
atlas.
We
thought
it
was
a
very
appropriate
name.
We
also
wanted
to
stick
with
some
kind
of
a
nautical
theme,
because
cloud
native
because
of
kubernetes
the
stayed
there
and
you
know
what
do
we
want
to
build?
We
really
really
I
am
pretty
passionate
about
creating
an
inclusive
open-source
project
when
I
about
a
year
ago,
I
was
at
devops
world.
Then
I
went
to
a
of
diversity.
A
Lunch
and
I
sat
with
mainly
a
group
of
women
and
two
black
men
and
I
asked
the
question
how
many
of
you
have
ever
contributed
to
an
open-source
project.
Nobody
raised
their
hand,
except
for
one
woman,
and
she
said:
I
tried
to
do
to
participate
in
an
open-source
project,
but
nobody
ever
responded
to
any
of
my
pull
requests
and
so
I
stopped
trying,
and
it
me
sad.
A
It
made
me
sad
that
someone
sat
on
a
governing
board
for
open-source
projects,
but
never
really
asked
the
question
from
a
low-level
who's
participating
in
them,
and
we
will
see
that
if
we
looked
at
the
demographics
are
not
a
lot
of
women
in
or
minorities
in
in
open-source,
and
we
really
really
want
to
change
that.
That's
why
I'm
so
excited
we
have
so
many
people
from
so
many
different
continents
on
this
call.
Today
we
really
want
to
create
a
common
ground,
as
well
with
experts
from
security
testing,
infrastructure,
project
management
and
development.
A
We
have
some
interesting
people
watching
what
we're
doing
so.
We
do
have
a
technology
Oversight
Committee
that
we
started
even
before
or
chilliest
had
its
name.
When
we
just
started
thinking
about
building
out
this
project,
we
have
Tim.
Kelton
was
one
of
our
first.
A
bet.
I
would
call
them
board
members
who
really
started
giving
us
some
clear
direction
on
where
to
how
this
tool
should
look.
He
co-founded
a
company
called
decart
labs,
decart
labs.
As
recently
it's
the
santa
fe
company,
recently
became
famous
during
the
Cova
pandemic
because
they
have
a
way
to
track.
A
They
do
a
lot
of
AI
and
machine
learning
around
mapping
and
they
were
the
first
ones
to
start
tracking
cell
phone,
where
you
travel
in
it
with
a
cell
phone
to
show
how
the
Kovac
can
spread
Doug
or
is
also
a
local
as
a
he
used
to
be
in
Santa.
Fe
he's
now
moved
back
to
Santa
Santa
Cruz,
but
he
was
one
of
the
original
kubernetes
architects
he's
now
retired.
He
is
a
rockstar
in
this
industry
and
as
and
I
hope
that
you
we
all
get
a
had
to
have
a
meeting
with
him.
A
He
doesn't
say
much,
but
when
he
talks,
everybody
listens,
he's
brilliant
and
has
given
us
a
lot
of
insights
and
how
to
move
forward
since
that
day,
it's
he
he
works
for
Bibby
financial.
He
also
is
a
you
know,
is
on
the
board
of
our
open,
makes
software
company,
and
he
was
one
of
the
he
built
what
we
now
know
as
our
domain
structure.
So
his
it
was
his
ideas
to
create
a
domain
structure
and
to
have
things
that
could
be
independently
deployed.
A
Hank
Hendrickson
I
met
as
well
in
the
process
of
doing
phone
calls
he's
the
infrastructure
lead
architect
at
BP,
and
he
has
a
amazing
background
and
just
how
companies
have
to
or
the
struggles
companies
are,
having
moving
to
a
digital
transformation
in
a
modern
architecture.
And
then
we
have
a
Tara
Hernandez
who
I'm
a
huge
fan
of.
A
She
is
a
senior
engineering
manager
at
Google
she's,
also
on
the
TOC
for
the
CDF
and
Michael
Galloway
who's,
also
an
engineering
manager
at
Netflix,
and
he
is
on
the
board
of
the
of
the
CD
foundation
and
that's
how
I
sort
of
recruited
him.
So
those
are
the
folks
who
have
been
part
of
the
oh
and
then
there's
Chris
Palmer,
who
I
he
does
not
have
any
pictures
and
he's
one
of
our
end
users,
and
he
is
the
in
charge,
he's
what
they
call
a
dev
ops
program
owner
for
unisys.
A
They
were
one
of
our
our
first
customers
who
really
understood
and
started
leveraging
the
use
of
a
domain
structure
and
on
that
I
am
going
to
pass
it
off
to
Marky.
Who
will
be
your
fearless
leader
in
the
future?
I'll
be
talking
a
lot,
but
Marky
and
Steve
will
be
really
taking
over
this
project
from
here.
B
Welcome
everybody
I
am
super
excited
to
have
everybody
as
well
to
get
this
kicked
off
for
those
that
don't
know
me.
Thank
you
for
the
introduction.
Tara
I
am
super,
humble
and
a
collaborative
person.
If
you've
seen
me
online,
you
know
I
like
to
have
fun
and
usually
at
my
own
expense
and
I
believe
in
having
it
truly
inviting
environment,
making
it
very
collaborative.
So
this
is
going
to
be
something
that
we're
all
on
a
journey
and
we're
all
learning.
There's
no
such
thing
as
mistakes.
B
There's
no
such
thing
as
asking
dumb
questions
and
trust
me
I've
already
asked
most
of
them.
So
that's
what
getting
started.
We
have
two
things
that
will
be
of
interest
to.
You,
first
will
be
the
github
repository
and
that
is
at
github.com,
slash,
affiliates
and
then
the
ortelius
main
repo,
myself
and
Steve
are
going
through
and
Steve's
creating
a
lot
of
the
work.
That's
gonna
start
off
I'm,
adding
some
of
the
good
first
issues.
So
if
you
go
look
there,
we
can
definitely
get
started
that
way.
B
A
B
Have
a
discord
channel
and,
if
you'd
like
to
join
that
disparate
Channel,
please
do
that's
where
we'll
be
doing
a
lot
of
our
async
communications.
So
definitely
join
that,
and
the
next
slide
will
talk
about
some
of
the
work
that
we're
doing
so.
We've
got
a
lot
on
the
roadmap
full
test
for
the
hipster
store
example:
we've
got
documentation,
scrub,
there's
the
spinnaker
integration,
the
or
filius
home
chart
for
kubernetes
clusters.
B
It's
the
oh
I
won't
read
through
all
of
these,
but
you
can
kind
of
get
an
idea
of
all
of
the
work
that
we're
doing
now.
One
of
the
things
I'd
like
to
point
out
about
a
lot
of
this
work
is
if
any
of
these
areas
are
of
interest
to
you,
and
you
have
absolutely
no
idea
how
to
do
it
or
you
have
a
little
bit
of
idea
or
you
are
like
an
architect
level
person
doesn't
matter.
Please
do
not
be
afraid
to
ask
to
take
on
something
that
you
don't
know.
B
B
So,
if
there's
something
that's
interest
of
interest
to
you
on
here,
please
do
not
hesitate
to
reach
out
and
say:
I
would
love
to
learn
how
to
do
Python
or
I
would
love
to
learn
to
do
data
science
for
data
visualization,
kubernetes
or
I'd
love
to
figure
out
how
to
write
a
helmet
chart.
This
is
the
time
where
you
can
get
to
learn
and
it's
going
to
be
in
a
sort
of
welcoming
environment
for
you
to
learn.
So
don't
don't
feel
like.
Oh
I,
don't
know
how
to
do
that.
C
Let
me
jump
in
real,
quick
one
thing
that
we're
gonna
focus
on
as
well
as
starting
from
the
real
basics
as
well.
You
know
what
is
a
pull
request.
You
know,
how
do
you
squash
and
merge?
You
know
what's
a
good
commit
message,
you
know
some
of
those
basics.
If
we
get
everybody
on
the
same
page
will
help
us
down
the
road
tremendously
yeah.
This.
B
B
They
spent
time
to
show
me
how
to
do
it
correctly,
and
that
was
so
amazing
to
me,
because,
even
though
I've
been
doing
this
for
a
long
time,
some
of
the
basic
things
were,
you
know
hard
to
grasp
and
so
I
want
to
make
sure
that
we're
showing
you
that
exact
same
thing,
some
of
the
true
fundamentals
of
computer
science
or
or
even
just
how
to
do
you
get
things.
This
is
that
this
will
be
the
time
to
learn.
B
So
for
those
that
don't,
if
you
need
to
get
a
hold
of
me
or-
and
you
feel
like
you,
don't
want
to
ask
in
a
public
channel,
my
direct
messages
are
open
on
Twitter
at
marki,
Jackson,
5,
there's
five
in
my
family,
so
I
think
we
just
stick
with
the
Jackson
5
you're
you're.
More
than
welcome
to
reach
out
to
me
and
welcome
aboard
everyone.
I
will
from
here
turn
it
over
to
Steve
the
awesome
person
and
take
it
away.
Steve.
A
Steve
gets
ready
doing
for
that,
I
want
to
add
it.
You
know
we
showed
a
list
of
things
we
want
to
work
on.
If
any
of
you
have
something
that
we
should
be
working
on
like
we
just
we
just
added
to
we're
going
to
add
to
deploy,
have
ant
ortelius,
probably
a
connection
to
console
for
storing
key
value
pairs,
because
we
have
a
we're
storing
them,
but
we
can
push
them
over
to
there.
So
if
somebody
has
an
idea
about
that,
bring
it
up,
please
we
want.
You
know
we
want
your
input.
C
One
of
the
things
that
we
have
here
is
a
list
of
applications
that
have
been
created.
These
applications
are
actually
based
on
a
micro
service
application.
The
hipsters
store,
so
the
soup
stir
store
is
the
one
that
we
ship
as
part
of
the
sample
when
you
sign
up
on
for
the
SAS
version
and
I
somebody
hit
us
up
on
the
discord
channel
saying
there
was
a
problem
with
the
signup
page.
I
should
have
that
sorted
out.
C
I
think
WordPress
got
a
wordpress
module,
got
updated
on
us
on
the
back
end
and
I
kind
of
threw
a
wrench
in
that
process,
but
that
will
get
sorted
out
in
the
next
couple
hours,
but
the
hipster
store
is
as
a
true
micro
service
architecture,
application.
It
came
out
of
Google
as
one
of
their
samples
each
one
of
the
containers
like
the
payment
service
load
generator.
The
cart
service
are
written
in
different
languages.
C
We'll
actually
see
where
the
store
is
referenced,
so
anything
that
starts
with
store
is
going
to
be
where
the
sample
code
is
now.
If
we
just
pick,
one
of
these
I've
been
working
with
Circle
CI
lately.
So
this
is
where
the
circle
CI
llamo
code
is
for
us
to
go
ahead
and
and
do
a
automated
build
when
we
check
in
a
change
into
this
repository,
that's
gonna
go
ahead
and
kick
off
and
hook
back
into
the
deploy
hub
version
here.
So
that's
where
we're
gonna
get
things
automatically.
C
C
Some
of
the
integrations
that
we
have
in
place
are
like
the
circle.
Ci
cloud
build.
There's
other
other
examples
out
here
that
hook
into
Jenkins,
like
Marky,
said
some
of
the
one
of
the
issues.
One
of
the
github
issues
is
to
hook
into
spinnaker
as
part
of
those
processes.
We
have
another
one
for
Team
City,
so
those
are
some
of
the
integration
pieces
that
were
working
on
on
that
front
as
part
of
that
process.
C
You
see
that
jenkins
file
here
for
the
the
Jenkins
cloud,
the
Jenkins
build,
so
that's
kind
of
pulling
together
what
we
have
on
that
front.
Let
me
get
back
to
the
right
repository
other
things
that
you'll
see
out
here
are
going
to
be
there
Lea
stocks.
This
is
the
repository
for
all
of
the
doxy
documentation.
C
C
So
there's
some
basic
some
good
first
issues
that
marquees
tagged
out
here
for
us
just
things
like
a
simple
documentation,
cleanup
or
if
you
want
to
be
more
evolved
in
dealing
with
standing
up,
kubernetes
and
learning
how
to
deploy
with
ortelius
out
to
the
cluster
as
per
that
process,
all
that
is
is
available
for
you.
We
are
going
to
start
on
the
one
of
the
things
on
the
roadmap
is
to
take.
C
If
we
actually
look
at
the
code
base,
we're
actually
going
to
take
a
lot
of
the
code,
it's
pretty
monolithic
right
now,
a
bunch
of
java
code
here
in
this
in
the
DM
admin
web.
This
is
like
the
front
end,
so
you
have
your
java
code
and
your
javascript
code.
At
this
level,
we
do
have
C
code
and
one
of
the
things
that
we
have
on
that
level
is
to
remove
the
C
code
and
replace
with
either
like
Python
or
go.
This
is
the
deployment
engine.
C
C
A
micro-services
approach
to
our
TAS
itself
also
we'll
be
setting
up
once
we
just
had
some
money
from
Microsoft,
so
we'll
be
able
to
stand
up
a
testing
area
place
out
in
a
sewer
that
we
can
actually
work
and
do
a
lot
of
our
productivity
work
with,
as
part
of
that,
we'll
be
splitting
things
out
into
a
smaller
will
have
more
repositories
that
are
going
to
be
working
with
at
that
level.
Just
besides
the
examples
that
we
have
going
on.
C
So
if
we
jump
back
to
the
point
hub,
if
we
look
at
what's
happening
on
the
components
every
time
we
we
check
in
one
of
those
samples,
we
actually
go
off
and
capture
the
information
about
it,
and
so
we
can
see
that
this
is
a
circle
CI,
depending
on
how
we
have
the
sample
set
upon
what
we
have
turned
on
and
turned
off.
If
we
have
like
this
case
circle,
CIA
was
turned
on
where
the
github
cloud
build
was
turned
off.
C
We
can
toggle
those
things
by
just
playing
with
the
switches
behind
the
scenes
as
part
of
that
process,
but
we'll
be
able
to
really
have
a
good
working
demo
to
get
us
started
with
and
then
we'll
be
using
deploy,
ortelius
itself
to
deploy
our
key
leus
to
the
kubernetes
cluster
as
well
as
once
we
get
that
stood
up.
So
it's
going
to
be
a
fun
process
here
and
there's
a
little
bit
of
everything
if
you're
at
the
level
of
being
an
architect
or
if
you're,
an
SRE
or
if
you're
developer,
for
you
do
documentation.
C
D
Yeah,
this
is
Christopher
heads
with
blueshift
and
I'm.
You
know,
and
relatively
new
to
deploy,
hub
and
I
guess
we're
all
new
George
Eliot's
at
this
point.
But
can
you
help
me
understand
like
what
the
current
differences
are
between
the
two
and
I'm
guessing
there's
not
very
many,
and
what
the
direction
of
that
is
intended
to
be
yeah.
C
So
in
the
in
the
deploy
up
world,
we
have
a
concept
of
releases.
So
that's
one
of
the
add-ons
that
we
have
at
that
level
and
then
also
user
groups
in
art,
Ilyas.
You
have
administrators
everyone,
users
and
in
our
pro
version
and
deploy
a
version,
that's
where
we
let
you
create
any
any
number
of
user
groups
at
that
level.
Also
it
gets
into
the
domain
structure
and
how
the
domain
driven
design
is
actually
laid
out.
A
number
of
levels,
deep
that
you
can
go
between
art,
Ilyas
and
the
deploy
a
pro.
C
Some
of
you
may
die
on
seeing
us
because
we
don't
typically
dive
into
a
calendaring,
but
when
we
can
when
we
want
to
schedule
out
events
and
things
like
that,
that
is
in
in
deploy
hub
and
not
in
art
Ilyas.
So
in
there
chilliest
code
base
you'll
see
you
know,
the
calendaring
code
is
actually
not
there.
C
The
release
codes,
not
there,
the
user
group
code
is
is,
is
not
there
and
then
there'll
be
more
additional
things
that
the
poi
hub
will
add
around
visualization
and
along
those
lines
like
DIF
reports,
additional
value
stream
type
of
data
gathering
that
that
we're
gonna
gather
from
interfacing,
like
with
Al
like
an
APM
side
of
the
house
as
well.
Our.
C
Tickets
I
forgot
about
that
change,
requests
those
links,
so
it's
gets
into
more
of
the
value
stream
from
a
change
all
the
way
out.
So
the
core
piece
with
art
Ilyas.
We
have
the
applications,
components,
environments
and
points
actions,
functions
procedures
and
then
just
some
of
the
bait.
You
know
the
basics
that
are
the
underlying
pieces
so
like,
and
this
gets
into
like
notifiers
and
templates,
our
current
notifiers
that
we
can
use
our
emails
slack
HipChat.
We
got
a
request
for
Microsoft
teams
as
a
another
notifier
to
work
with.
We.
C
This
board
itself,
so
that's
the
high
level
difference
between
the
the
two
products,
so
I
would
say
about.
85
percent
of
the
code
base
is
open.
Source
of
what
deploy
hub
is
based
on
it's.
Basically,
it's
a
hundred
percent
of
the
code
base
that
deploys
Mesa
and
then
we
add
another
20
percent.
On
top
of
that,
that
help
does
anyone
see
you
a
question.
Oh
yeah.
D
C
And
right
now,
we've
I'm
in
the
process
of
merging
a
lot
of
the
UI
code
back
down
insular
or
Tullius
project.
They
got
they
branched
pretty
far,
because
we
did
a
major
rewrite
of
the
the
GUI
from
the
deploy
website
and
now
or
from
the
deploy
apps
contributing
back
to
RT
leus,
and
I
should
have
that
done
by
the
end
of
the
week.
All
the
code
merge
all
the
the
C
code
is
good
to
go.
It's
just
some
of
the
UI
stuff
they're.
E
B
Our
pattern
is
on
the
roadmap,
hello.
We
just
chased
home
because
a
lot
of
times
you'll
find
from
a
kubernetes
abstract
people
will
choose
to
do
the
helm,
easy
deployment.
However,
it
becomes
down
to
you,
know
kind
of:
what's
your
flavor
I
do
think
operator
patterns
or
the
CR.
D
is
definitely
favored,
but
sometimes
people
want
a
very
stripped-down
version
of
a
deployment
and
they'll
choose
a
home
chart
because
it's
from
a
security
perspective,
it's
a
little
bit
easier
than
an
operator
which
takes
a
lot
of
more
from
a
cluster
role.
You're
on
tour.
E
B
C
C
No
not
yet
you
know,
we've
been
just
focusing
on
mainly
the
the
homeworld
right
now
and
we're
open
to
expanding
that
into
other
other
solutions.
You
know
that's
one
of
the
things
here:
we're
not
we're
not
going
to
be
locked
into
a
particular
language,
or
you
know
we're
gonna
try
to
pick
the
best
for
the
the
problem
that
we're
solving.
G
B
Definitely
again,
it
goes
back
down
to
like
kind
of
what
the
flavor
is.
I
agree
with
you,
I
think
ailment
and
customize
together
is
super
awesome,
because
you're
able
to
use
a
lot
of
the
underlying
sprig
templates
from
go
to
go.
Templating
I
think
it's
called
a
sprig
template,
so
yeah
there
will
be
every
flavors
because,
just
like
Steve
said
we
want
to
make
sure
everybody
has
sort
of
an
option
to
choose
from
so
you'll
see
as
as
time
progresses.
B
C
C
We
just
want
to
try
to
be
somewhat
consistent
just
so,
we
are
able
to
not
have
to
have
a
steep
learning
curve
as
per
that
process,
and
then,
when
we
get
into
that,
I
can
foresee
that
it's
going
to
evolve
on
how
we're
going
to
be
deploying
art,
Ilyas
with
or
Pelias
out
to
the
kubernetes
cluster,
whether
we're
gonna
be
using
customizing
home
or
if
we're
going
to
be
using
operator
or
something
new
comes
along
that
we
want
to
try.
We
can
do
that.
You
know
this
is
this.
C
A
H
H
You
are
trying
to
like
rewritten
it
rewrite
it
in
Python
or
go
in
a
modern
language
so,
but
for
any
applications
who
want
to
use
this
tool
do
they
need
to
rewrite
their
code
bases
to
more
modern
language,
to
kind
of
get
full
functionality
of
of
this
product
or
it
would
there
be
any
role
map
for
monolithic
applications
to
kind
of
break
down
and
use
what
the
tool
what
we
are
providing
here?
You.
C
Know
let
me
share
my
screen
again.
I'll
show
you
how
that
comes
into
play.
So
one
of
the
things
that
is
the
beauty
of
deploy
hub
is
we
abstract
everything
into
a
component.
So
these
are
all
my
components.
You
see
like
hard
servers
here.
These
are
different
versions
of
the
same
component.
So
as
the
the
circle
CI
build
process
was
coming
along,
we
actually
were
creating
new,
so
checking
happen.
We
created
a
new
version
of
the
of
the
component.
Now
a
component
can
be
anything,
it
could
be.
C
Our
test
case
component,
so
components
loss
to
have
that
level
abstraction
and
then
we
bring
together.
The
components
are
packaged
together
into
an
application
version,
and
so
we
have
our
domain
hierarchy
over
here
of
where,
where
our
components
are
stored,
which
domain
that
they're
they're
coming
from
and.
F
C
F
C
Or
two
components
instead
of
many
components,
so
the
more
tedious
will
go
ahead
and
support
a
monolith
world,
it's
just
in
the
the
number
of
components
that
we
have
associated
to
that
application.
Now
this
is
where
one
of
the
challenges
is.
You
know,
if
you
look
at
this
simple
example,
the
screen
is
pretty
busy.
This
is
where
data
visualization
and
comes
into
play
is
when
you
have
200
micro
services
that
are
rolling
up
into
a
version
of
an
application.
How
do
you
navigate
that
at
that
level?
C
A
That
is
actually
one
of
those
good
discussion
we've
been
having
with
some
of
you,
I'll
go
back
to
that
Steve.
What
you
were
looking
at
was
an
application
version,
but
if
you
could
go
to
a
base
version
for
me
Steve,
so
what
we
need
to
be
able
to
do
is
we
need
to
be
able
to,
and
Steve
has
already
done,
some
work
in
this
area
we
just
haven't
made
it.
A
We
haven't,
published
existent,
hasn't,
really
been
thoroughly
tested
by
really
large
systems,
but
we
need
to
be
able
to
create
the
base
version
based
on
interrogating
a
cluster,
so
I
mean
there's
other
ways
that
we
can
provide
this.
You
could
give
us
this
data.
A
user
could
provide
this
data,
the
package
component
data
by
providing
us
a
list.
We
might
be
able
to
grab
it
out
of
the
kubernetes
deployment
file,
but
more
likely
it's
going
to
be
in
a
cluster
based
on
namespaces.
So
that
is
an
area
that
we
really
need
to
be
get
start.
A
C
What
will
happen
is
once
we
have
our
base
version
and
we
know
the
the
relationships
we
can
then
start
maintaining.
You
know.
So,
if
recommendation
service
keeps
on
getting
updated,
we
know
that
we
have
to
create
a
new
version
of
the
of
the
hipster
store.
So
once
we
have
our
starting
point,
then
it's
pretty
much
behind
the
scenes.
Self-Audit
made
self
updating
when
we
get
commits
coming
in
and
through
the
hooks
from
the
CIS
CD
pipeline
tool.
C
So
that's
where
that
that
kind
of
comes
into
play
and
we
grab
information
from
that's
at
that
point.
But
this,
the
starting
point
like
Traci
is
saying
is
what
is
our
starting
point
and
we
have
some
prototypes
that
we've
done
around
trying
to
reverse
engineer
cluster,
to
figure
out
what
isn't
what
is
in
the
application
these
days,
especially
when
you
have
a
couple
hundred
services
in
a
cluster
and
how
are
the
namespaces
related
to
each
other
and
which
versions
of
of
the
appli
components
the
micro
services
are
rolling
up
into
which
version
of
the
application.
C
A
F
A
Fork
is
too
late.
I
want
to
just
do
some
basic.
You
know
how
we
want
what
the
cadence
of
these
meetings
look
like
and
maybe
Marquis
you
can
give
us
some
ideas
of
how
often
we
should
meet,
and
you
know
you
know
what
that
needs
to
look
like
and
I
get
some
feedback
from
the
crowd
in
terms
of
what
they
would
like
to
see.
A
B
I
so
I
was
giving
some
thought
over
this.
The
last
few
days
and
I
was
thinking.
We
should
have
a
general
weekly
meeting
I'm
at
cover
sort
of
the
project
as
a
whole.
We
can
maybe
start
by
doing
a
fifteen
minute
demo
of
a
various
particular
portion
of
the
project.
Everybody
can
become
familiar
with
that
and
then
we
can
start
in
remainder
part
of
the
meeting
we
can
start
to
cover.
B
You
know
what
we're
going
to
be
working
on
and
sort
of
do
it
very
stand-up
style
if
anybody's
joined
goodie
of
the
other
open
source
project
meetings,
you'll
see,
there's
like
a
general
larger
meeting.
I
mean
we'll
see
over
time
as
we
start
to
break
into
work
verbs.
Those
will
have
their
own
meeting
cadence,
but
they'll
be
sort
of
meeting
back
into
the
original
figure.
B
A
B
Think,
generally,
what
will
we
can
do
is
I
think
this
is
a
good
time.
It
does
cover
a
wide
range
of
that
world
time
zones.
I
do
think
that
it
may
split
into
two
meetings,
someone
that
covers
North
America
and
one
is
more
a
path
friendly,
but
I
will
say
that
will
probably
send
out
a
doodle
to
everybody,
so
people
can
sort
of
vote
on
the
time
and
we
can
make
it
a
very
transparent
sort
of
everybody.
Selecting
from
something
we
know,
I'll
know
what
we're
we're
all
looking
at
I
find.
A
And
then
it
is,
we
are
about
10
minutes
before
you
know
the
full
hour
and
I
want
to
respect
everybody's
time.
So
if
there
is
anything
that
we
haven't
covered,
that
somebody
has
a
question
about
just
logistically,
you
know
how
to
get
to
github
I
think
that
will
be
Steve
pointed
out.
We'll
try
to
do
some
of
that
training
stuff
will
probably
create
videos
of
that.
F
A
At
a
ortelius
youtube
channel
created
and
get
this
first
video
uploaded
to
it,
and
then
this
there
is
a
the
presentation.
I.
Everybody
should
have
received
a
link
to
the
presentation
and
will
have
also
on
Google
Docs,
the
ortelius
meeting
notes.
And
so,
if
you,
if,
once
those
I'll
get
those
up,
there
I'll
shoot
everybody
an
email
and
if
you
could
go
ahead
and
add
your
name
as
a
initial
attendee
since
there's
no
way
I
can
do
it
from
here.
C
B
D
C
C
So
if
you
go
grab
one
of
the
containers
from
the
ortelius
project,
you'll
get
the
old
old
UI
version,
like
I
said
by
the
end
of
the
week,
I'm
hoping
to
have
the
new
UI
from
the
play
up,
pushed
down
and
merge
back
into
the
art.
Ilyas
piece
the
seco
has
been
merged,
the
documentation
has
been
merged,
is
still
I.
Have
a
couple
conflicts
on
some
JavaScript
I
got
to
deal
with
to
push
back
down
and
then
then
will
be.
B
D
I
may
have
asked
my
question
ambiguous
way.
I
should
know
better
than
using
the
word
release
and
a
group
of
geeks
like
this
foolish
me
again.
So
really
what
I
was
talking
about
was
the
release
in
terms
of
github,
because
people
that
are
watching
the
repo
can
choose
to
watch
it
on
a
release
only
basis,
and
if
people
are
trying
to
minimize
the
note
noise
I'm
expecting
they're
going
to
do
that
and
so
I
understand.
D
C
So
the
concept
of
a
big
release
is
going
to
go
way.
You
know
be
more
of
like
we've
gotten
to
a
point:
we're
going
to
start
a
whole
new
like
feature
that
will
go
ahead
and
tag,
something
create
a
release
and
branch
off
of
that
to
allow
that
to
happen,
I
mean
one
of
the
things
I'd
like
to
do
is
to
be
able
to
you
really
get
into
a
model
where
we're
actually
using
like
a
service
mesh
and
pushing
new
features
like
a
beta
feature
out.
B
And
well
well,
that's
happening.
What
I
would
like
to
say
is
that
you
know
one
of
the
things
that
you'll
find
is
that
this
is
this
is
where
we're
getting
started
with
this
project,
and
this
is
sort
of
a
really
awesome
thing,
because
you
have
the
ability,
as
a
contributor
to
this
project
to
influence
how
that
can
happen.
How
certain
things
happen,
so
part
of
collaboration
and
open
source
is
taking
everybody's
feedback
and
we
all
decide
on
something
as
a
as
a
team
as
it's
sort
of
open
family.
A
C
A
I
C
A
Yes,
a
Death
Star
with
a
modern
architecture,
you
will
have
a
kubernetes
cluster
with
nodes
and
pods
running
individual
containers
that
execute
a
micro
service
talking
via
api's.
Take
a
look
at
these
Death
Star's
running
four
hundred
plus
services.
The
complexity
is
epic.
So
how
do
we
navigate
the
Deathstar?
We
should
ask:
where
are
our
applications,
which
version
of
a
service?
Is
the
application
consuming
and
the
best
question?
Who
is
using
my
micro
service
with
micro
services?
All
the
parts
are
loosely
coupled.
In
addition,
all
the
linking
is
done
via
api's
at
runtime.
A
In
other
words,
micro
service
configuration
management,
just
became
critical
deploy,
have
is
a
micro
service
configuration
management
solution
that
catalogs
versions
tracks
and
deploys
independently
deployable
microservices
to
the
applications
that
consume
them.
Deploy
a
hub
becomes
a
central
location
or
single
source
of
truth,
exposing
service
to
application
dependencies
and
allowing
you
to
fully
navigate
your
Deathstar
deploy
web,
makes
it
easier
to
migrate
to
micro
services
and
provide
you
the
platform
needed
to
manage
them
over
time
for
more
information
reach
out
to
us
at
request
info
at
deploy
web
comm.
Thank
you
for
watching.