►
From YouTube: MSI Open Demo. August 18, 2017
Description
Magento 2 Multi Source (Stock) Inventory open demo
- Introduce Reservation API. Append only reservations
https://github.com/magento-engcom/magento2/wiki/Reservations
- New indexing of Inventory and creating Virtual Aggregated Stock Items based on linkage rules
https://github.com/magento-engcom/magento2/wiki/New-Indexer-for-StockItems
Validation of Domain entity - https://github.com/magento-engcom/magento2/wiki/Validation-of-Domain-Entities-in-Magento
B
And,
as
usual,
we
go
to
the
MSI
roadmap.
So
during
the
current
week
we
were
walking
on
the
two
stories
on
a
reservation
API
and
the
append-only
reservations,
and
another
story
was
new
indexing
of
inventory
and
creating
virtual
aggregation
stock
items
based
on
a
linkage
rules,
so
the
so
storing
for
the
reservation.
B
We
made
some
design
changes
in
this
cover.
This
story
also,
we
had
a
meeting
with
the
lead
architect
of
magenta,
with
anton
creo
and
I
made
a
demo
for
him,
and
he
proved
our
our
way
of
making
the
reservation
and
also
we
had
a
meeting
with
Alejandro
who
is
working
on
this.
This
story
and
we've
made
some
changes
to
how
the
reservation
interface
would
look
like.
Actually,
we
remove
the
status
from
the
reservation
and
introduce
the
metadata
and.
B
B
We
would
expose
reservation
API
via
Web
API,
so
we
will
consider
the
reservation
as
an
FBI
entity
which
will
happen.
I
decided
tag
of
some
particular
business
process
like
order
placement
of
the
original
handling
and
we
made
changes
for
the
reservation
services.
So
we
left
at
this
reservation
attend
service
and
we
change
service.
So
we
had
a
service
which
returns
the
open
reservation
for
the
product,
but
now
we
decided
to
remove
it
and
just
to
provide
two
services
which
will
provide
the
ability
to
get
the
precise
quantity
of
some
particular
product
in
some
particular
stock.
B
Ok,
so
let's
continue
so
for
now
we
decided
to
have
just
two
services.
We
shall
provide
the
precise
amount
of
time
particular
product
and
also
we
decided
so
Helena
a
conversation
with
Anton
Creole.
We
decided
not
to
put
stock
item
entity
inside
the
product
interface
and
it
is
implemented
actually
now
so
for
now,
in
magenta
2
we
have
the
product
interface
and
the
stock
item
now
added
to
this
interface
and
could
be
retrieved
as
an
extension
attributes
of
the
product.
B
B
D
B
B
Another
story
will
devoted
for
the
msi
stock
indexing
mechanism
and
where
we
would,
we
want
to
make
and
prepare
this
new
aggregation
for
the
stock
items,
and
here
we
because
we
are
going
to
introducing
new
index-
and
this
in
this
would
be
pretty
complex
because
it
should
be
splitted
by
the
dimension
and
in
our
case,
dimension
should
be,
should
be
stock
IDs.
So,
for
example,
if
there
are
like
three
different
stops
in
our
case,
our
indexation
will
end
up
with
creation
of
three
different
tables.
B
Each
of
the
tables
would
be
responsible
for
a
specific
stock
ID,
so
it's
pretty
similar
to
what
we
tell
in
the
catalog
search
index.
So
doing
so,
we
want
to
get
the
possibility
of
the
horizontal
scalability
when
we
will
create
as
many
stock
indexes
as
our
system
head
and
doing
so.
We
would
not
end
up
with
one
really
huge
overloaded
index
and
where
which
would
not
be
processed,
and
we
will
study
the
performance
problem
on
the
level
of
the
database,
for
example,
and
it's
pretty
so
we
start
with
some
problems.
We
have
on
a.
B
B
B
When
we
making
the
jewelry
indexation
and
after
that
process
of
real
indexation
is
finished,
we
need
to
switch
this
index
with
this
index
feature
to
the
substitute.
So
it
would
be.
It
would
be
useful
when,
as
Cooley
indexation
takes
quite
a
lot
of
time,
so,
for
example,
for
big
merchants,
it
could
take
minutes
or
even
sometimes
hours.
B
So
today
had
a
discussion
with
with
one
of
the
architect
who
designed
that
mechanism
and
also
I
raised
that
question
in
our
architectural
consumed
meeting
so
I
believe
we
will
get
some
response
in
the
shortest
in
a
shortest
time.
How
can
I
know
what
is
the
best
way?
How
can
we
arrange
the
problem,
but
for
now
we
will
I
believe
we
will
make
a
copy
paste
of
what
we
have
to
not
postpone
our
work
and
not
true
to
be
blocked
by
by
this
external
circumstances.
B
E
Yes,
on
Tuesday
I,
starting
with
the
implementation
and
the
testing
of
the
implementation,
I
use
the
creation
tab
first
time
we
have
but
work
in
ProQuest
I
already
copied
the
the
logic
for
switching
but
I
need
also
the
pictures
of
for
testing
the
switching,
because
the
process
is
really
complex
and
you
have
many
different
yeah
index
states
and
yeah.
It's
looking
progress.
B
B
B
B
So
we,
the
documentation
of
further
invalidation
next
needn't,
be
introduced
for
the
domain
entities,
and
so
here
you
see
this
article
I
just
shared
just
just
before
the
meeting
was
started
so
because
we
introduced
some
some
you,
it's
not
a
new
principle,
but
a
little
bit
new
approach,
comparing
to
what
we
already
have
in
magenta
to
regarding
the
entity
for
the
day,
SHINee's
I'm
eager
you're,
not
sharing
screen
anymore.
He
we're
trying
to
share
some
awkward.
Sorry.
B
You
yeah,
so
we
shared
the
article
like
what
it
is,
not
the
main
hand.
This
is
in
magenta
and
describe
why
the
entity
should
develop
methods
where
it
makes
sense
to
validate
this
entities
and
how
actually
entities
are
being
validated
in
the
magenta
MSI
project.
So
here
we
describe
the
validation
result,
for
there
is
an
exception
we
introduced
and,
for
example,
description
of
how
the
source
entity
which
use
the
save
command
under
the
hood
and
actually
have
the
validation
techniques
happens.
B
That's
already
nursed
all
develop
branch,
so
you
can
see
that
you
can
see
that
here
on
in
a
code
base
of
the
other
side
bridge
yeah
today
on
a
call
is
smart,
brilliant,
infuse,
product
owner
of
the
project
but
sorry
mark.
We
don't
have
anything
to
show
you
to
be
accepted,
because
two
stories
are
still
in
progress.
Sure
I
hope
that
next
next
weekly
demo
would
be
more
productive
and
we
will
close
one
of
the
story.
Great.
B
Yeah
and
Valerie
just
remind
me
to
just
to
say
you
pretty
pretty
important
status,
so
we
we
made
the
merge
of
the
develop
branch
of
the
current
current
deliver
branch
of
Magento
and
we
updated
the
ATP
unit
version
to
the
single
to,
and
actually
we
updated
a
the
unit
tests.
We
have
on
a
project
to
the
latest
version
so
for
now.
Actually
that
was
the
last
step
which
we
need
to
to
mate
on
the
way
for
using
HP
17
texts.
So
for
now
we
can,
we
can
use
PGP,
7
syntax.
B
E
D
B
B
F
B
B
D
If
it's
related
to
the
the
new,
the
tutorial
services
on
the
reservation
site
without
the
cap
rod,
quantity
in
stock
and
the
each
product
in
stock,
just
a
config
patient
that
executing
that
service
I
should
take
into
consideration
the
in
stock
status
and
yes
in
growth
of
the
method.
So
even
in
the
get
product
quantity
in
stock
or
only
in
the
East
product
in
stock,
because
the
get
product
quantity
to
me
can
be
unaware
of
the
status.
D
A
E
B
D
F
B
Okay,
so
let
me
rephrase
the
equation,
so
you
asking
so
we
have
the
service.
We
have
a
dedicated
service
which
returns
the
is
product
in
stock.
So
the
question
is
whether
we
need
to
take
into
consideration
all
the
open
reservation,
or
should
you
just
use
this
flag,
which
is
store
it
in
our
stock
item
and
because
we
already
have
this
top
item
flag,
which
represent
the
duration
stock
or
not?
But
for
example,
it
could
be
in
stock.
D
C
D
Okay,
but
please,
okay-
and
this
is
this-
is
clearing
the
is
product
in
stock
service,
but
in
the
get
product
quantity
in
stock
I'm,
not
sure
that
the
dislike
should
be
should
be
considered.
Yankel,
semantically,
speaking
I
am
asking
how
much
of
and
I
don't
know
if
this
is
intended
to
to
count
or
not
the
stock
flag.
If
this
can
be
use
to
determine
sale
ability
or
not,
if
it's
used
to
determine
saleability
I
have
to
consider
the
easy
stock
flag
for
sure.
If
not
I
I
can
I
can
ignore
the
flag.
So
yeah.
B
So
here
we
have
two
to
two
conditions,
so
the
first
one,
if
you
already
have
the
flag
turned
into
out
of
stock,
so
we
don't
need
to
consider
any
the
reservation
we
just
reach
on
this
out
of
stock.
Okay,
you
can
have
this
flag
as
in
stock.
We
need
to
get
the
identity
and
apply
all
the
reservation
and
check
whether
we
care
okay.