►
From YouTube: MSI Open Demo. August 4, 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
- Cover with WEB API all existing scenarios for SourceItem and Source to Stock linkage
A
Okay,
yes
looks
like
everybody
who
wanted
to
join
join
and
we
can
start
our
weekly
meeting
so
I
see
that
there
is
one
you
participant
on
a
medium
sassette
I
said.
Would
you
like
to
introduce
yourself
and
tell
us
a
little
bit
about
your
our
interest?
Why
you
can
about
the
msi
and
maybe
have
some
experience
you
want
to
share.
A
B
I
guess
I
does
not
finish
a
story
about
MPI
because
of
the
seek
I
focus
at
corner.
You
I
component
update
it
was.
It
was
our
tag
that
we
have
read:
internal
Butte
now
I
finishes
a
great
PR,
and
now
we
have
green
internal
deals
for
Web
API
test
and
to
API
functionality.
I
need
several
days,
I
think
I
over
finish
it
to
to
where
whether
they
may
be
to
choose
it.
B
A
Did
you
or
I
going
are
going
to
create
it
DK
page
for
any
component
description,
because
I
believe
we
have
something
to
share
with
the
community,
because
we
start
with
some
pretty
interesting
stuff
in
magenta
to
regarding
Zi
components
and
also
we
wanted
to
show
what's
the
best
way
to
work
with
Zi
component
cities
have
many
to
many
relationship.
If
we
potentially
have
quite
a
lot
of
items
to
be
rendered
and.
B
A
This
pool
request
was
prepared
by
Lars
with
FNS
connections
on
today's
meeting
and
actually
I
created
a
code
review
for
this
pool.
Request
and
I
prepared
I
prepared,
dedicated
technical
tech,
technical
design
document
describing
the
indexation
process,
because
the
indexation
process
for
stock
items
is
pretty
interesting
because,
for
example,
if
they're
talking
about
the
big
merchant,
if
you're
talking
about
the
big
merchant,
we
could
end
up
with
a
lot
of
data
stored
in
this
index.
Because
here
we
can,
we
we
have
multiplication
of
data.
A
So
we
have
a
multiplication
of
product
quantity
as
a
quantity
of
SQL
results
for
some
particular
merchant
multiplication
by
amount
of
sales
channel.
A
merchant
has
configured
on
his
particular
installation,
so
in
our
case
sales
channel
are
could
be
like
websites.
So
if
we
are
talking
about
the
notes
and
to
have
quite
a
lot
of
websites
and
to
help
quite
a
lot
of
excuse,
we
end
up
with
with
the
multiplication
of
amount
of
s
queues
on
a
number
of
sales.
A
This.
Why
is
proposed
here
to
introduce
and
dimension
mechanism
and
will
reduce
the
dimension
mechanism
to
the
full
text
index
by
they
mentioned?
We?
Actually,
we
understand
a
school
by
which
we
make
a
split
of
index.
So,
for
example,
if
I
talking
about
full
text
index,
we
use
as
dimension
at
store
view,
because
we
usually
use
a
store
view
as
a
as
a
scope
for
work
I.
So,
for
example,
we
have
a
color
for
the
English
local
dedicated
for
German
language
and
each
stove.
A
You
have
own
scope,
that's
why,
for
example,
for
the
full
text
index
we
create
tools
in
dependent
to
independent
indexes
for
each
record.
So
actually
pretty
sensitization
happens
here,
but
here
we
have
a
scope
which
is
represented
by
this
talk
so,
for
example,
seven
five
websites,
each
of
which
represent
particular
sales
channel.
We
actually
end
up
with
five
different
indexes,
like
here
inventory
stock
item
for
the
first
up,
one
inventory
stock
item
for
the
stock
to
for
the
stock,
three
four
and
five,
and
also
we
already
have
in
our
index
or
framework.
A
We
have
the
SPI
interface
and
this
este
interface
used
actually
ever
about
the
dimension.
So
you
can
see
that
all
of
this
methods
of
that
interface
are
aware
about
the
dimension
and
they
can
accept
reversible
interface.
So
you
can,
for
example,
save
data
for
some
particular
indexes,
so
actually,
in
our
case
dimension
would
be
the
stock
IDs.
A
Also,
another
really
interesting
point
here
that
for
all
magenta
two
indexes
we
have
a
requirement
of
zero
downtime
during
the
full
pre
indexation
happen
and
actually
what
we
understand
here
by
the
zero
downtime.
So,
let's
imagine
that
we
have
the
full
realization
happen
and
we
create
a
new
table
and
while
we
are
creating
table
actually
the
front
end
is
unreachable,
because
we
actually
at
the
beginning
of
the
realization
process,
we
just
drop
the
old
table
and
start
to
recreate
one.
A
A
A
We
clean
data
and
we
create
the
data
for
the
new
index
and
that
actually
apply
the
changes
for
the
temporary
index
beyond
used
and
how
the
index
is
prepared.
We
using
the
index,
feature
interface.
Actually,
we
make
a
switch,
so
we
replace
we
substitute
actually
that
old
index
within
u1
and
make
a
can
connected,
calling
the
use
regular
index
so
the
same
behavior
we
would
like
to
achieve
with
within
you
stock
item
indexes
to
provide
zero
downtime
for
the
front-end.
A
A
C
A
Reservations
so
in
the
reservation
18
so
for
the
reservation
I
edit,
a
technical
design
for
how
the
reservation
should
look
like.
We
already
had
the
reservation
page
and
I
added
here
some
more
description
based
on
our
previous
discussion.
How
reservation
should
should
be
down
for
the
order,
cancellation
and,
as
the
agree
to
the
previous
meeting,
we
no
need
to
make
any
kind
of
bingham
between
the
reservation
and
the
order.
A
So
as
we
see
for
now,
the
reservation
should
be
just
an
append-only
operation
and
we
need
to
create
just
another
reservation
with
the
concert
status
and
here,
I
also
added
the
API
for
reservation.
So
I
introduced
the
example
of
the
data
interface
for
the
reservation
entity,
which
holds
now
there.
The
raishin
ID
stock,
ID,
SQ
quantity
and
the
status
into
possible
status
is
created
and
cancelled
and.
A
To
service,
maybe
we'll
need
more,
but
now
I
see
it.
Probably.
We
need
to
services
the
first
one,
the
append
service,
which
append
an
area
of
reservation
into
the
table.
So
this
service
is
actually
pretty
similar
to
what
we
serve
with
the
multiple
save
column,
because
actually-
because
this
is
an
so
risk,
it
will
insert
new
reservations
to
some
to
some
reservation
storage,
I
believe
in
out
of
the
bottle
fermentation.
That
would
be.
A
A
That's
why
we
have
a
service
which
is
called
get
reservation
product
and
we
will
use
this
service
in
inside
the
stock
item
implementation.
So
how
the
stock
item
get
quantity
will
work,
so
we
will
retrieve
the
stock
item,
quantity
data
and
we
need
to
minus
the
number
of
all
the
visitors.
Duration
for
the
this
particular
school
are
on
in
the
scope
of
particular
sales
of
channel.
So
in
the
scope
of
stock
we
are
working.
A
So
here
you
can
see
the
description
of
how
this
happen
and
to
make
actually
tree
to
make
it
possible
to
retrieve
all
the
open
reservation.
We
need
to
use
this
service
get
reservation
for
product,
so
this
service
going
to
be
used
in
the
scope
or
inside
the
implementation
of
the
stock
item,
and
so
for
now
this
is
how's
their
reservation
service,
a
suit
like
and.
A
D
A
D
A
D
A
D
There's
something
to
think
about
in
because
I
I
think
that
it's
early
to
think
about
it,
but
I
think
that
as
soon
as
an
order
is
placed
or
cancelled
or
updated
in
some
way
and
reservation
has
to
be
affected
by
this
change,
we
will
have
to
to
establish
how
this
will
happen.
I
did
it
and
on
Magento
one,
but
on
magenta
one
I
used
the
event
event.
Roblin
was
yes
and
it,
but
it
was
a
separate
module
and.
D
It
was
a
third
party
modules,
so
it's
a
the
only
way
to
do
that.
But
since
we
are
here
developing
a
core
module,
I
don't
know
if
in
this
case
we
can
interact
more
deeply
with
the
framework
or
we
have
to
stay
on
high
level,
and
in
that
case,
if
you
prefer
to
use
a
plug-in
or
other
methods
it
a
suggestion.
Let's
talk
about.
Is
that
think
and
talk
about
this
not
now
not
mandatory,
to
talk
about
this
now,
just
a
hint
mm-hmm,
so.
A
It's
actually
a
good
question
so
for
now
our
strategy
is
next,
so
we
are
building
actually
new
inventory
system
and
for
now
we
are
trying
to
be
they
trying
to
be
separately
from
the
core
so
to
prevent.
Actually
integration
with
occur
because
integration
with
the
core
for
now
will
actually
imply
that
introducing
some
changes
to
support
and
it
will
introduce
some
changes
to
the
core
now,
actually,
we
will
introduce
some
backwards,
incompatible
changes
to
the
core
generally
at
this
stage.
A
We
want
to
prevent
this,
or
at
least
responses
as
far
as
possible,
and
we
are
trying
to
make
all
the
implementation
separately
in
our
inventory
module
and
covers
that
functionality.
This
end-to-end
testing
scenarios
to
make
it
sure
that
actually
we
could
you
could
just
see
that
all
our
interfaces
and
all
our
business
scenarios
work
as
expected
and
just
after
that
start
to
integrate
it
to
the
core.
So
now,
actually
the
deduction
which
is
the
stock
deduction
which
happens
during
the
order
placement.
A
We
don't
have
a
particular
nice
extension
point
in
magenta
to
core
FL,
so
it's
pretty
similar
how
it
was
done
in
magenta
one.
So
we
have
the
event
which
is
thrown,
and
after
that
we
have
the
observer,
which
actually
makes
deduction
using
the
stock
item
model.
I
believe
that
when
we
will,
when
we
actually,
our
system
would
be
ready
for
the
integration
score.
A
So
for
now
we
want
us
to
make
sure
that
it
will
work
and
cover
that
with
Web
API
and
integration
test
that
actually
the
functionality
work
and
the
after
they
try
to
recreate
like
step
by
step
that
we
can.
We
can
manage
our
sources.
We
can
build
the
stops
based
on
the
source
source.
Inventories
gave
that
aggregated
quantity
after
that.
Try
to
try
to
make
a
reservation
for
that.
Stop
after
that,
make
a
deduction
and
see
how
it
like
making
step
by
step
and
make
sure
that
we
are
covering
all
the
business
case.
A
A
Okay,
so
if
you
guys
don't
have
any
other
question,
probably
we
can
we
can
finish
today's
meeting
so
looks
like
we
are
clear:
what's
the
commitment
take
for
the
next
week,
so
we
will
continue.
Work
on
a
will
actually
start
work
on
a
reservation
and
we
will
continue
work
for
the
test
coverage
of
UI
compiled
of
our
basic
scenario
and
we
need
to
process
a
pull
request
created
by
Valera
and
fix
the
eye,
components
and
I
believe
we
will
provide
an
article.