►
From YouTube: Environments Design Pair Session - 07/09/2023
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
B
Yeah
all
right
thanks!
So
let's
talk
about
service
blueprint,
I'm
gonna
share
my
screen.
B
So
where
are
we
right
now?
We
talked
about
motivation
and
then
we
talked
about
goals
and
it's
harvest
properties
last
week
and
then
I'd
like
to
discuss
diagram
today.
I
already
showed
this
to
Victor.
That
seems
like
it's
a
bit
off,
so
I
would
like
to
fix
it
and
then
the
goal
is
that
we
have
the
you
know
same
Mentor
model
around
the
service
models.
B
So
we
just
said:
let's
dive
into
the
this
diagram,
so
I
already
puts
a
couple
of
the
nodes,
but
let's
clean
up:
first,
yes
and
probably
seeing
this
off
so.
B
Oh
by
the
way
feel
free
to
edit
it
so
I
just
want
to
make
it
brief
rule
that
this
blue
note
is
the
entry
of
I
think
from
the
from
the
closely.
B
Yeah,
so
this
these
ones
displayed
right,
so
service
is
the
one
of
them
and
if
it's
a
really
satisfact
deployment
environment
blob,
we
only
use
this
terminology.
We
only
use
this
keyword
inside
this
blue
box
and
then
this
is
one
of
the
entry
entries.
B
C
D
B
So
yeah
big
dates
back
so
I'm
gonna
continue.
So
this
I
should
say
balloon
thing
is
that
represent
properties,
so
if
service,
this
problem
is
stick
to
this
service.
That
means
like
this
service.
Has
these
properties
like
this
is
something
similar
to
what
we
discussed
in
the
last
session.
That
like
service,
has
a
name
service.
Has
a
metadata
service
has
a
description,
blah
blah
blah.
So
in
this
case,
like
service,
has
a
name
something
metadata,
something
right.
Yes,
so
let's
get
started
I.
B
So
let's
say
like
these
are
project
inside
the
organization
inside
the
git
love
instance
and
then,
let's
say,
users
want
to
modeling
Service.
That
is
already
exists
in
their
infrastructure.
B
So
here's
a
very
simple
one.
This
CDN
is
a
like
a
cloud
of
layer,
so
this
is
a
load
bouncer.
This
is
where
the
records
come
from
and
then
this
request
is
spread
to,
let's
say
U.S
region
and
the
Europe
region.
And
then
this
region
has
a
the
simple
web
server
and
maybe
like
a
cytical
service
and.
C
Then,
in
this
case,
sorry,
just
because
you
said
that
each
blue
box
is
one
instance
of
that
specific
type,
you
would.
B
C
A
B
So
is
it,
does
it
make
sense
like
it's
very
simple,
maybe
like
it's
not
even
like
realistic,
but
probably
it's
good
to
start
to.
You
know
very
perfect.
I
think
therefore,
I'm
simple.
B
C
B
C
B
Then
then,
so
the
first
thing
is
like,
since
we
are
saying
that
Services
entry
point,
probably
at
first,
we
put
service
first
right,
User
make
its
service
inside
the
project
and
then
what
name
of
this?
First,
let's
say
that
Jesus
yeah
users
want
to
track
this
web
instance.
C
Or
basically,
in
this
case
so
I
yeah,
I.
B
Would
say:
yeah,
okay,
so
this
project
has
a
web
service
metadata.
It's
like
could
be.
It
could
be
customer
X,
customer
X.
It's
a
label,
the
key,
the
keyword.
B
The
label
is
the
value:
okay,
X
yeah.
Maybe
this
is
enough.
So
the
only
one
service
in
this
project
right
and
then.
B
C
C
A
D
D
B
Okay,
so
I
think
then
for
now
this
would.
B
Not
like
then,
environment
has
a
name
right:
name,
production,
yep
and
staging
and
staging.
D
A
B
Okay
yeah
so
then,
like
on
the
environment,
there
deployments
I.
A
C
A
B
C
C
B
B
B
C
C
I
don't
know
where
should
we
place
it
because,
in
a
sense
that
release
an
Enviro
that
reads
artifact
packages,
part
of
a
service
I,
don't
know
how
to
best
say
it
like.
D
B
I
or
not
yet
about
which
tiger
yeah.
A
C
C
Okay,
then,
let
me,
where
is
that
screen
here
very
Zoom.
C
So
I
I
will
make
a
demo
of
all
of
these
things,
but
right
now
we
should
only
focus
on
this
project,
primarily
where
I
have
I'm
I'm,
deploying
this
Potato
Head
project.
It's
a
cncf
demo,
application
specifically
for
demos
and
I
deployed
to
a
Dev
environment
and
the
production
environment
and
I,
deploy
it
with
a
ham
chart.
Okay,
but
I,
don't
deploy
it
directly
with
flux
using
a
git
repository
but
I
deploy
it
with
flux
using
an
oci
image.
C
C
I
would
say
that
in
this
case,
the
release
artifact
is
this
Potato
Head
delivery,
Potato
Head
for
product
here
I
have
separated
these
artifacts
for
production
and
for
Dev,
because
that's
what
gitlab
supports,
but
if
that's,
why
we
don't
have
these
artifact
actions,
but
so
anyway,
we
have
this
Potato
Head
container,
which
actually
packages.
C
This
chart
here
and
a
related
ham
release
that
configures
provides
configurations
for
that
provides
the
values
for
that
ham
chart
actually,
okay
and
I
would
say
that
basically,
the
container
packaging.
This
single
file
is
the
closest
that
we
have
today
for
to
release
artifact,
but
this
release.
Artifact
reference
is
another
container,
and
this
container.
C
C
B
So
so
question:
can
you
go
back
to
previous
page?
C
I
think
it
should
have
I
mean
I,
create
an
environment
for
entry
points
as
well,
but
what
I'm
really
interested
in
I
didn't
even
set
up
kubernetes
for
this
one,
because
it's
really
it's
it's
a
it's
an
auxiliary
environment
just
to
provide
some
common
things.
Actually,
in
my
case,
it
just
provides
a
secret
and
the
the
main
environment
artifacts.
C
C
C
B
C
C
C
That
this
is
the
artifact
that
got
deployed
okay
and
here,
if
I
show
you
a
bit
of
the
synapse
back
bundle
Json
what
bundle?
What
cnap
does
is
that
they
basically
just
say
that
let's
have
an
oci
image
with
a
defined
schema
that
always
includes
this
bundle.
Json
and,
for
example,
the
banda
Json
lists
all
the
images
that
are
needed
in
the
end,
to
run
this
application
and
other
images
that
are
needed
to
set
up
this
image
in
the
environment.
C
So
it's
it's
and
then
you
can
have
a
I
know.
It's
just.
It
always
just
have
a
single
image
here,
but
you
could
have
multiple
images.
You
can
see
that
these
references
are
actually
can
be
signed.
So
it's
it's,
not
it's
lightweight,
as
here
where
you
have
to
track
down
that.
Okay,
this
is
my
release.
Artifact,
but
I
have
no
idea.
What's
included,
it's
more
that
it's!
C
A
C
B
B
D
B
B
C
A
secret
that
it's
it's
not
in
the
cluster
but
is
in
I,
don't
know
Google
key
manager
or
something.
B
It
sounds
like
there's
a
lot
of
work
around
the
artifact
I,
especially
like
it.
That's.
B
Yeah
a
lot
of
this
yeah,
but
that's
the
idea
yeah,
that's
the
idea.
Okay,
okay
got.
It
sounds
like
yeah
I,
don't
know
better
to
documents
in
glossary,
but
yeah.
Thank
you
for
sharing,
so
wait,
I
it
just
assuming
that
this
is
not
in
the
scope
of
this,
like
maybe
like
in
the
in
the
future,
but
maybe
yeah.
No,
no
okay
got.
C
It
yeah
but
I
think
for
the
visualization.
We
should
understand
what
it
means
so
that
that
we
know
what
we
don't
want
to
deal
with.
B
B
Got
it
yeah
that
makes
sense.
B
So
yeah
look
actually
I
have
a
a
few
questions.
For
example,
you
said
deployment
is,
doesn't
belong
to
project
in
this
case
like
we
don't
need
to
show
deployments
around
the
service.
A
C
B
C
B
B
So
it
sounds
like
we
don't
need
to
Define
deployments
in
the
blueprint,
but.
C
You
are
right
in
the
sense
that
likely
we
have
a
status
of
every
these
artifacts
in
a
in
a
given
environment
and
that
status
might
be
that
it's
deployed,
and
then
it's
rolled
out
and
that's
where
the
deployment
relationship
comes
in,
but
the
Diplomat
is
not
there.
In
the
gitlab
side,
it's
just
a
simple
record
still.
B
B
Then,
okay
cool.
Does
anyone
have
a
question
otherwise
I'm
gonna
ask
the
second
question.
So:
okay,
I.
B
Right
yeah,
this
one
is
actually
a
bit
more
interesting
one
that
let's
say
there
are
two
two
projects.
Well,
these
are
the
same
set
exists
to
the
right.
Well,
I.
Don't
have
the
time
to
do
that
did
in
this
case
we
have
four
environments
right,
let's
say
imagine.
C
A
C
C
D
B
D
I
think
we've
had
a
number
of
customer
complaints
in
the
past.
That
convention
doesn't
seem
to
really
work
once
you've
scaled
Beyond,
like
thousand
environments
up
yeah
I.
Think
specifically,
it
was
eMobile
that
complained
about
having
like
I,
don't
know
lots
of
strange
environments
with
weird
names,
because
we,
but
no
we
had
nothing
in
the
product
that
would
enforce
particular
naming
schemes
we
have
to
I.
Don't
know
now
is
a
good
chance
to
try
and
figure
out
how
to
solve
that
problem.
Instead
of
just
relying
on
convention.
D
But
don't
we
want
to
like?
Don't
we
don't?
We
want
to
group
all
these
Services
together,
anyways
on
on
the
unlike
the
project
page
like
when
we,
when
we
go
to
the
project
page
and
we
look
at
services
or
environments,
are
we
looking
at
environments
or
are
we
looking
at
services.
D
C
D
No,
you
well
even
at
a
project
level
right
like
like
why
wouldn't
this
staging
environment
in
this
service
be
the
same
as
the
staging
environment
in
the
other
service
here,
because
we're
all
still
under
one
project
right.
C
But
I
think
it's
because
it's
partial
because
showed
this
as
a
tree,
but
you
could
visualize
the
same
thing.
Let
me
try
to
do
it
quickly.
C
I
hope
it
will
work.
Then
I
really
have
to
drop.
C
B
Let's
continue
in
next
week.
B
A
A
That
are
we
good
for
this
week
or
move
on
to
next
week
for
the
rest
of
this.
A
A
D
You
have
any
I,
don't
have
any
fun
design
questions
for
you
this
week.
A
No
worries
well
thanks
again
shinya
for
keeping
our
agenda
occupied
with
things
for
this.
The
last
few
weeks
appreciate
it.
B
I
think,
thank
you
all.
It's
really
helpful
to
you
know,
review
the
things
with
a
bunch
of
eyes.
Yeah.