►
From YouTube: Hyperledger Fabric (HLF) - Creating a Consortium
Description
A recording of the Study Circle session hosted by Hyperledger Sweden on August 15, 2020 featuring a discussion led by by Roland Bole about using Hyperledger Fabric to create a consortium.
Github Link: https://samlinux.at/blog/fabric-05/
More about the Study Circles hosted by Hyperledger Sweden are at: https://www.meetup.com/Hyperledger-Sweden/
----
Hyperledger – Open Source Blockchain Technologies
Hyperledger is an open source community focused on developing a suite of stable frameworks, tools and libraries for enterprise-grade blockchain deployments.
It serves as a neutral home for various distributed ledger frameworks including Hyperledger Besu, Fabric, Sawtooth, Indy, as well as tools like Hyperledger Avalon, Cactus and libraries like Hyperledger Aries, Ursa. Learn more about Hyperledger projects: https://www.hyperledger.org/use
Case Studies: https://www.hyperledger.org/learn/case-studies
Training & Certification: https://www.hyperledger.org/learn/training
Tutorials: https://www.hyperledger.org/use/tutorials
Webinars: https://www.hyperledger.org/learn/webinars
Events: https://www.hyperledger.org/events
Vendor Directory: https://www.hyperledger.org/use/vendor-directory
Subscribe to the Hyperledger Newsletter: https://www.hyperledger.org/newsletter
Follow-us on Twitter @Hyperledger
Learn about Hyperledger Membership: https://www.hyperledger.org/about/join
#Hyperledger #HyperledgerMeetups #Blockchain
A
Okay,
so
I
think
we
can
start
hello
and
welcome
to
this
hyperledger
sweden
meetup
this
saturday
and
today
my
name
is
roland.
I'm
your
host
for
today
and
in
this
session
and
in
the
upcoming
sessions,
we're
going
to
build
a
new
consortium
with
you
and
I've
called
this,
the
sunshine
company
sunshine.com
and
in
this
session
and
in
the
next
sessions
we
will
start
a
new
consortium
step
by
step
and
you
will
find
that
to
this
consortium,
all
configuration
files
in
the
github
label.
A
A
A
A
You
will
see
what
this,
what
you
can,
what
you
have
to
change
when
you
you're
going
to
try
when
you're
going
to
build
your
own
consortium
and
in
this
first
step
we
will
do
it
with
crypto
crypto
again
and
because,
when
we
start,
it's
a
little
bit
easier
to
start
with
the
cryptogram
tool,
because
as
a
replacement
for
the
fabric
ca.
Because
this
fabric
ca,
we
have
to
copy
a
lot
of
certificates
and
we
need
a
structure
and
a
crypto.
A
Con
gives
us
this
structure
in
the
first
way,
so
that
we
can
study
these
examples.
And
then
we
can
in
the
later
sessions
we
can
use
favorite
ca,
also
to
create
the
crypto
materials
for
the
appeals
for
the
orderers
and
so
on.
But
that
will
come
to
a
later
to
a
later
time,
because
it's
a
very
heavy
task
so
because
we
have
to
copy
a
lot
of
things.
A
A
This
is
a
a
config
file
and
also
an
and
folder
which
are
the
structure
we
need.
Then
we
need
this
config
tx
yammer
file.
It's
also
configuration
file.
We
will
see
for
what
is
this
needed
and
what
we?
What
we
have
to
edit
to
create
our
example.
Then
we
have
to
look
into
the
docker
compose
file.
So
all
these
elements
are
created
with
docker
in
docker
containers
and
to
organize
this
docker
containers.
A
A
We
are
going
to
try
to
add
that
we
have.
We
are
going
to
try
to
add
a
third
pier
we
can
enable
tls
in
this.
In
this
example,
we
can
also
change
the
order
system
from
solo
to
weft
so
rough.
This
is
really
good
because
in
the
current
version
of
2.2
solo,
adam
system
and
kafka
ordering
system
are
duplicated.
A
So,
in
the
end,
I
think
raft
will
be
the
default
consonants
algorithms
for
favic,
and
that's
a
good
start
that
we
didn't
see
how
we
can
con
configure
raft
for
the
system
and
this
week.
I
have
also
tried
the
example
where
we
can
add
another
pier
but
and
not
appear
on
a
different
host.
So
that's
a
pretty
exciting
example,
which
I
provide
so,
but
that's
one
for
for
next
session.
A
A
A
We
have
to
look
into,
then
we
have
to
configure
the
config.hxml
file
and
then
we
have
to
configure
the
docker
compose
yaml
file.
So
these
three
configuration
files
we
need
and
to
edit
that
we
can
have
and
consortium
like
this.
We
we
have
seen
in
the
in
the
picture,
so
that's
the
first
part
we
have
to
do
after.
A
We
have
a
good
idea
from
what
we
are
going
to
do,
and
the
second
part
is
that
we
generate
all
the
crypto
materials,
so
we
have
to
generate
the
certificates,
the
private
keys,
the
public
keys
and
so
on,
and
for
this
we
will
use
a
crypto
again.
This
is
the
tool
for
development
for
prototyping
and
it's
a
replacement
for
a
favorite
ca
or
any
other
system
where
we
can
generate
x509
certificates.
A
A
So
these
are
the
the
steps
you
know
from
a
high
level
which
we
are
going
to
do,
though,
to
create
a
new
network
and
as
a
begin
for
the
beginning,
we
have
to
to
know
what
the
terms
are
for
so
this
cryptoconfigurable
file.
This
is
the
definition
of
organization
managing
other
nodes
for
the
cryptoconfig
folder.
So
this
we
will
look
later
in
detail
for
this,
but
this
file
is
needed
to
define
the
organization
and
this
file
creates
a
crypto
material,
and
this
is
stored
in
this
cryptoconfig
folder
here
and
this
cryptoconfig
folder.
A
Is
at
the
place
where
all
the
crypto
material
is
generated
when
we
use
the
cryptoconfig
tool
for
us
and
it's,
I
think,
a
replacement
for
the
frederic
cite.
So
these
both
elements
belongs
together,
and
the
third
thing
is
the
config
tx
yummy
file,
which
contains
information
related
to
the
configuration
of
the
network
structure.
A
So
this
is
also
a
file
we
are
looking
into
and
have
to
make
some
changes
which,
which
is
which
fits
our
needs
and
the
docker
compose
file
is
the
definition
for
the
network
structure
and
we
have
seen
we
can
in
this.
When
we
look
into
the
fair
examples,
we
have
also
saw
base
docker,
compose
files
and
or
sub
docker
compose
files,
which
we
can
include
in
a
main
docker
compose
file,
and
but
we
can
do
this,
I
have
in
my
example,
I
have
the
docker
base
file
where
the
beer
base
file
extracted.
A
So
that's,
but
we
can
do
this,
but
we
have.
We
don't
have
to
do
this
when
we
don't
when,
if
we
don't
want
so,
but
it's
a
little
bit
easier
to
do
is
because
when
we
have
more
appears,
then
we
have
to
put
all
the
config
variables
or
tls
configuration
variables
only
in
a
single
file
and
not
we
have
to
copy
this
all
in
every
section.
So,
but
this
these
files
are
needed
and
this
folder
is
also
needed.
A
So
that's
also
for
only
for
testing
and
for
prototyping
and
as
I
have
mentioned,
that
you
can
see,
there's
a
replacement
for
a
certified
authority
and
something
like
favorite
ca.
This
is
the
the
way
we
are.
You
should
do
it
in
the
etheric
world,
and
here
we
have
two
important
commands
and,
as
you
can
see,
crypto
can
generate.
This
is
the
main
command
to
generate
the
crypto
material
and
cryptogram.
Extend
is
also
interesting
but
not
needed
for
today,
but
this
is
for
the
next
time
when
we
extend
the
network.
A
So
when
we
will
have
today,
we
have
two
peers.
When
we
have
three
or
four
peers,
then
we
can
use
the
extent
command
here
and
then
we
will
have
the
cryptogram
will
not
override
and
delete
and
write
new
crypto
material.
So
he
will
extend
the
existing
crypto
materials
and
extended
only
with
the
second
beer,
the
referred
beer
and
so
on
so
and
for
this
we
have
to
we
have
the
config
parameter.
A
This
is
a
config
file
and
the
input
option
here
or
parameter
is
where
the
crypto
material
slips
for
so
these
both
commands
are
needed.
So
this
we
will
use
today-
and
this
is
maybe
a
command
for
the
next
for
the
next
session,
but
keep
in
mind.
Cryptogram
is
only
for
the
testing
and
not
for
production
so
and
config
text.
Gen
is
the
next
command
line
tool
which
we
have
to
be
look
a
little
bit
and
we
have
to
use
it
so,
and
this
command
line
tool
works
with
the
config
tx
yam
file
together.
A
So
and
we
we
need
this
tool
today
for
three
different
commands,
so
the
first
thing
is
for
the
generation
of
the
genesis
block.
So
this
is
the
first
block
in
the
network
and
we
can
create
also
the
channel
configuration
transaction
and
these
anchor
b
update
transactions.
So
these
are
the
commands
here
so
this,
but
all
all
information
from
this
for
this
command
comes
from
the
config
txjump
file.
So
that's
important.
These
both
elements
belongs
together.
A
A
A
So
the
best
thing
is,
we
make
a
copy
from
the
favorite
samples
we
can
copy
this
file
and
then
we
can
make
our
adjustments
to
this
file
and
in
this
file,
as
you
can
see,
we
have
to
define
some
information
about
our
organization
about
our
network.
So
this
is
the
the
other
organization.
That's
we
have
to
change
here
in
the
sunshine.com
and
it's
the
ottawa
element.
A
The
host
name
is
order
and
this
will
create
barwab.sunshine.com
configuration
and
the
same
is
for
our
peer
organizations,
so
we
have
to
set
up
here
our
peer
organization,
so
that's
organization,
one
and
we
have
to
configure
here
our
domain
producer.sanction.com-
and
we
can
hear
this
this
in
this
template.
There
is
a
count
key
and
we
say
this
is
set
to
two.
So
that
means
that
we,
we
will
have
two
peers
in
this
organization.
A
When
we
want
to
have
three
or
four,
then
we
can
change
this
number
and
then
crypto
again
will
create
this
crypto
materials.
For
this,
when
we
extend
our
network,
then
we
have
also
changed
this
value
here.
So
we
can
make
then
three
or
four
and
with
the
cryptogram
extend
command
the
the
tool
will
generate
the
crypto
material
for
two
more
appears
here
in
this
yeah
and
the
same
is
for
the
users.
So
by
default,
every
organization
will
have
here
one
one:
admin,
user
and
one
normal
user.
A
So
and
when
you
can
share
this
to
two
or
three,
then
you
will
have
two
users:
three
users
and
the
admin
user
is
always
included.
So
users
are
also
users
and
not
admin.
So
we
have
by
default
one
admin
and
one
user,
and
when
we
increase
this
number,
then
we
will
have
we'll
have
two
or
three
users
and
so
on,
but
for
the
users
is
not
so
important,
so
we
can
use
also
with
with
cryptogram
favorite
ca,
because
that's
also
a
advantage
when
we
use
cryptogram.
A
So
our
crypt
I
needed
crypto
my
tutorial
for
the
favorite
c
to
the
usage
of
favorite
three
is
also
generated,
so
we
can
create
a
single
favorite
ca
container
and
to
make
some
and
and
make
some
adjustments
to
the
docker
compose
file,
and
then
we
can
create
third
hair
users
through
the
favorites
a
command.
So
that's,
maybe
a
good
part
for
for
the
next
time
to
extend
the
network.
A
A
We
will
have
one
organic
peer
organization
with
two
peers
and
one
user
and
the
user
is
called
user
one
and
by
default
a
user.
An
admin
user
is
also
generated
through
this.
So
I
think
that's
that's
very
easy
to
do,
and
the
second
step
is
a
little
bit
complex,
it's
more
complex,
so
the
config
tx
yaml
file.
So
these
are
informations
about
our
network
itself,
about
the
membership
service
provider
and
so
on.
A
A
This
is
the
path
here
and
that
is
very
important
to
know
that
the
crypto
config,
when
you
change
the
paths,
you
have
to
be
carefully
that
you
know
what
is
on
the
proper
organ
on
the
proper
position
and
so
because
otherwise,
you
will
have
a
lot
of
a
lot
of
errors
and
the
the
system
cannot
find
any
any
path.
So,
but
when
we,
when
we
be
carefully,
we
can
change
this
and
we
can
say
okay,
this
is
our
sunshine.com
organization
order
organization
and
we
can
have
different
orders.
A
A
So
and
here
under
orders
you
will
have
ottawa,
01,
error,
02
and
so
on.
So
and
that's
the
part
for
this,
but
that's
everything
the
same-
you
have
only
to
change
the
names
here
when
you
come
away
from
the
example.com
and
the
name
and
the
the
name
and
the
id
we
have
to
be
aware.
So
for
the
all
better
organization.
A
That's
the
only
organization
we
have
in
this
this.
This
is
original
named
or
organization
one
and
we
call
it
producer
and
then
we
have
to
adjust
to
the
name
producer,
msp
and
the
id
also
producer.
So
and
then
here's
the
same
thing.
We
have
to
change
here
in
the
crypto
config,
there's
the
the
folder
to
producer
samsung.com
and
in
this
peer
organization
folder
we
will
have
when
we
have
two
or
more
organizations.
We
will
have
here
the
base
structure
for
organization,
two
three
and
so
on.
A
So
that's
the
same
like
here,
so
you
have
the
orderers
and
then
you
will
have
different
others,
and
here
you
have
peer
organizations
and
then
you
will
have
different
peer
organizations.
How
many
you
want
and
the
speaker
depart
is
a
membership
service
provider,
and
here
I
have
changed
this
like
one
msp
and
id
org,
one
msp
to
a
more
understandable
name
for
for
me.
I
call
this
producer
msp
because
of
our
business
requirements
from
the
picture,
and
then
we
have
to
adjust
this
path
as
well.
A
A
A
This
is
for
the
development
and
here's
the
address
order,
sanction.com,
and
this
is
also
the
name
of
the
service
and
also
the
name
of
then
of
the
docker
container,
so
that
they
found
this,
and
here
you
can
see
some
information.
So
sometimes
the
question
is:
when
is
a
new
block
generated,
and
that-
and
here
are
the
settings
for
this,
so
this
patch
time
is
two
seconds.
So
that
means
in
in
this
case
here
every
two
seconds.
A
new
block
is
created
from
the
order
system
and
yeah.
A
Maybe
that
means
that
every
transaction
will
have
its
own
block
because
of
the
two
seconds
limits,
but
there's
also
a
batch
size.
So
we
have
here
the
max
message
count.
This
is
two
two
transact
as
a
ten
transactions
and
we
have
also
a
maximum
number
of
heights,
and
so-
but
I
think
that's
when,
when
when
the
batch
time
and
two
seconds
or
the
patch
size
is,
is
matches
first
and
then
we
then
will
create
a
new
block.
A
You
can
inspect
this
when
the
network
is
running,
so
you
can
look
into
the
blocks,
you
can
fetch
a
block
and
they
can
look
what
is
introduced.
What
is
into
this
block?
Okay?
So
these
are
some
information
but
also
defaults.
There's
there's
nothing
to
change
from
so
okay,
there
are
also
defaults
and
the
channels
are
also
defaults
so
and
the
only
thing
what
we
have
to
look
now
is
are
in
this
proof
in
this
profile
section.
A
So
this
profile
section
is
a
part
where
you
can
define
different
profiles
and
when
you
call
the
conflict
x
context
tx
then
tool.
You
can
say
what
do
you
want
from
this
from
this
from
this
config
takes
yaml
file
so,
and
we
can
have
here
different
configurations,
so
we
can
have
here
different
audio
configurations
and
then
we
can
say:
okay,
config,
tx,
again
tool
create
the
genesis
block
for
this
profile.
That's
in
my
one
words
order
again
assist,
so
that's
a
that's
only
a
name.
A
A
So
we
have
also
one
orgs
channel
channel
profile
here
and
we
have
a
consortium-
and
these
are
the
points
here,
so
we
defined
here
in
the
order
organization.
This
is
the
sunshine
consortium
and
in
the
sunshine
consortium
we
will
have
one
organization,
and
this
is
the
producer
organization.
So
this
is
the
value
which
we
have
created
here
on
top
on
this
file.
So
this
is
the
producer.
So
this
is
our
organization.
A
Elements
belongs
together
so
and
when
we
have
a
second
organization
and
then
we
will
have
here
another
line
at
the
third
line
and
so
on
and
yeah
and
for
the
for
the
channel
configuration
we,
it
belongs
to
this
consortium.
So
the
channel
belongs
to
the
consortium
sunshine
and
this
id
defaults.
We
have
which
we
have
seen.
A
In
this
in
this
in
this
file
a
little
bit
earlier,
and
here
we
also
define
the
or
we
have
to
set
which
organizations
belong
to
this
channel.
So
but
you
can
say
in
favorite,
okay,
we
have
a
channel
yeah.
We
have
different
organizations,
but
not
all
organizations
belongs
to
our
channels,
so
we
can
have
a
chat.
We
can.
We
can
have
free
organizations,
and
one
channel
belongs
to
organization
one
and
organization
two
and
we
can
have
another
channel
which
belongs
to
our
organization,
one
and
three
and
so
on.
A
So
and
that's
the
reason,
I
think
why
we
can
hear
say:
okay,
this
channel
belongs
to
producer
or
seller
or
accounting
or
marketing
or
whatever.
So-
and
I
think
that's
it
for
this
now
so
and
with
this
settings
you
have
a
customized
general
configuration
and
but
with
default
settings
from
the
solo
order,
but
also
with
default
settings,
if
you,
if
you
use
raft
or
kafka,
but
I
have
I've
deleted
these
profiles
here.
A
When
you
look
in
the
original
file
config
the
external
file,
you
will
have
here
more
profiles
and
examples
how
you
configure
this
in
the
kafka
case
or
in
the
graph,
and
for
this.
For
now
we
have
only
this
three
ordering
systems,
solo,
kafka
and
zookeeper
and
graphs,
and,
as
I
have
mentioned
in
the
2.2
version,
I
have
I
read
in
the
documentation
that
the
solo
on
the
kafka
is
duplicated.
A
A
A
Controls
the
network
services
files-
and
one
thing
to
know
here,
is
that
here
I
have
set
volumes
and,
and
with
this
volumes
I
have
persistent
data.
When
you
don't
do
this,
you
will
have
not
persistent
data
on
techniques
that
when
your
network
is
stopped,
then
you
will
lose
your
blockchain
and
all
other
informations.
A
Sometimes
the
volumes
are
still
there
and
then
you
have
to
delete
these
volumes
and
that's
and
that's
a
good
part.
I
have
here
in
the
in
the
last
section
here:
some
that's
the
command
delete
all
persistent
volumes
with
docker
volume
prune
so
and
with
this
step
you
can
be
sure
that
all
incorrect
volumes
and
so
on
are
deleted
from
your
system
that
you
can
make
a
clean
start
again.
A
A
A
With
the
cli
container.
We
can
interact
with
the
network
from
the
command
line,
so
we
don't
need
node.js,
sdk
or
golang
sdk
to
interact
with
this
network.
So
as
a
system
administrator
or
as
a
favorite
administrator
from
the
point
of
view
of
the
administrator,
you
can
use
the
cli
container
to
interact
with
this
system
with
your
system.
So
that's
the
reason
why
the
cli
container
is
important
and
it's
also
a
specific
container.
A
So
it's
called
fabric
tools
for
this,
and
this
fabric
tools
container
have
everything
installed,
which
you
will
need
to
interact
with
the
containers
so
and
that's
the
service
which
we
need
here
so
okay,
and
so
this
is
always
in
one
file.
But
we
have
another
file
here.
The
spear
base
yaml
file.
So
when
we
look
here
into
the
first
service,
so
this
is
simply
yaml
file.
The
yummy
file
is
you
see?
This
is
so.
A
I
don't
know
it's
structured
in
this
way
that
you
can
have
here
two
spaces
or
one
tab,
to
structure
this
file,
and
here
you
have
the
service
name,
and
this
is
the
service
name,
and
this
is
the
container
name.
So
when
we,
when
the
system
is
running,
then
we
have
to
know
which
is
the
container
which,
which
is
the
container
the
other
container,
and
we
can
look
at
this
names
here
and
when
we
have
some
informations
which
we
need
in
different
services.
A
Docker
gives
us
the
possibility
to
extend
this,
and
we
can
include
this
from
from
another
file,
and
this
is
done
with
this.
This
is
extend
command
and
then
you
have
to
specify
a
path
to
another
yaml
file.
So,
and
this
is
the
be
a
base
yummy
file
and
in
this
beer-based
yummy
file,
we
have
two
services,
so
we
have
one
the
base
configuration
for
the
beers
so
and
one
for
the
ottawa.
So
in
our
case
for
the
order,
this
is
not
necessary
because
we
have
only
one
other.
A
But
when
you
have
a
when
you
use
rust
raft,
for
example,
then
you
have
at
least
three
or
three
or
more
other
container,
and
then
you
you
need
all
this
the
same
configurations.
Maybe
then
you
can
have
here
the
order
of
base
configuration,
and
this
is
included
in
the
in
the
in
the
docker
compose
file
here.
A
So
that's
that's
the
reason
why
this
is
splitted
so
now
and
in
our
case
now,
it's
not
so
much
information
here,
but
when
we
next
time
when
we
enable
tls,
for
example,
then
then
we
will
have
more
environment
variables
which
we
have
which
we
can
define
here
and
then
it
makes
sense
to
do
it
in
this
in
such
a
base
file
and
we
don't
have
to
copy
and
paste
all
the
information
in
to
the
docker
compose
file.
So
it's
large
enough.
A
A
We
can
import
something
into
the
container
and
what
the
auto
I
need
is
the
channel
conf,
the
guinness
block
from
their
channel
artifact
folder,
which
is
generated
to
the
from
the
generate
process.
We
will
see
a
little
bit
better
a
little
bit
later
and
here
these
are
the
paths,
these
paths.
This
is
the
path
where
the
other
the
genesis
block
from
the
order
should
be
so
I
think
this
path
is
fixed,
I
think
so,
that's
maybe
in
the
core
file.
A
Maybe
you
can
change
this,
but
I
don't
know
so,
but
I
think
this
the
the
the
right
side
from
from
the
volumes
definition.
So
these
are
default
parts
and
on
the
left
side
we
can
make
our
adjustments
how,
where
our
genesis
block
is
stored.
So-
and
in
my
case
I
have
called
this
channel
artifact.
So
this
is
a
method
which
is
very
common
in
the
examples
you
find
this
on
different
places
and
here
the
genesis
block.
Of
course
this
is
the
the
order
and
access
to
the
genesis
block
they
have
to
know.
A
Where
is
the
again
and
the
second
thing
what
we
need
here
is
the
membership
service
provider.
So
the
membership
service
provider
is
one
of
the
important
spots
from
from
fabric.
This
is
the
the
part
where
we
can,
where
we
can,
where
we
will
have
oil
crypto
materials
for
this
particular
member
of
a
network,
and
the
order
is,
is
a
member
of
the
network,
like
a
user
like
admin
like
beer
and
so
on.
So
every
member
of
the
network
need
the
membership
service
provider
and
the
informations.
A
The
information
from
the
membership
service
provider
comes
in
our
case
from
the
cryptogram
tool
or
from
the
favorite
ca
container
from
the
favorites
ca
service,
and
the
right
part
is
also
the
default.
I
think
the
default
path
configuration
for
this,
whatever
membership
service
provider
so
and
so,
and
in
this
way
you
map
the
localhost
so
a
file
from
the
localhost
in
the
container-
and
in
this
this
last
point
here,
this
hyperliteral
production
order
folder,
as
the
name
mentioned
here.
This
is
the
this
is
production.
A
So
then
you
have
here
volume
and
in
this
here
lives
the
the
blockchain,
the
blockchain
data
lives
in
this
folder
and
since
we
have
a
volume
here
that
leads
us
to
be
to
have
persistent
data.
So
when
we,
when
we
comment
this
out,
I
think
then
the
system
will
also
work,
but
we
don't
have
the
data
anymore
when
you
restart
the
network
and
that's
the
part
definition.
So
this
is
the
default
part
for
your
one
and
for
the
peers.
A
I
think
it's
basically
the
same
structure
we
have
seen
here.
We
have
a
con
vms
service
here
and
we
have
the
container
name
so
over
the
service
name.
We
can
interact
with
this
and
the
container
name
is
the
name
of
the
container
and
also
the
base
yaml
file,
which
you
see
here,
and
here
we
see
a
little
bit
more
environment,
important
part
environment
variables.
A
So
these
are
some
important
information.
So,
with
this
environment
variables,
we
can
define
the
pid
bp
address,
dpr,
listen
address,
so
the
chain
code
address
and
chain
code,
listen
address,
and
here
also
these
these
bootstrap
gossip
variables,
both
of
them
and
very
important
here,
the
last
one,
the
corp,
your
local
msp,
wherever
this
is
the
part
where
the
system,
the
cle
container,
for
example,
will
know
which
organization
is
used
and
then
which
crypto
material
is
used
to
interact.
A
So
and
with
this
environment
variables
we
can
change
their
the
configuration,
but
in
the
case
of
the
beer,
it's
not
important
to
change
this
here.
So
this.
This
is
the
configuration
for
this
and
for
the
pier
1
as
well,
and
when
you
compare
this
with
the
cli
container,
we
have
here
this
one,
this
three
lines
here
and
you
see
when
you
start
the
cli
container.
A
We
you
have
to
the
cli
container,
have
to
know.
Okay,
I
will
connect
two
beer,
but
to
hp
and
in
which
name
I
will
work
now
you
can
say-
and
this
is
done
with
this
free
environment
variables
and
when
we
are
into
the
cli
container,
and
we
would
like
to
change
to
another
deal
or
to
another
organization.
A
A
For
the
container,
we
need
also
some
mount
point,
some
mapping
to
the
local
host
and
yeah.
You
can
see.
Okay.
Of
course,
we
need
the
chain
code.
So
when
we
install
chain
code,
we
do
this
with
the
cli
container,
so
we
need
access
to
the
cli
container.
We
can
copy
with
docker
the
chain
code
into
the
cli
container,
that
you
can
do
this,
but
it's,
I
think,
more
efficient
when
you
map
this
here
and
also
you
need
the
md
path
to
the
cryptoconfig
folder
into
the
channel.
A
Artifact
artifacts
folder
here
and,
as
you
can
see
here,
docker
has
some
you
can
control
the
the
boot
process,
the
starting
process
from
the
docker
system-
and
you
can
see
here
this
cli
container-
will
be
ready
when
the
order
are
the
pl1.
The
b2
rdp,
one
0
and
p1
is
ready
to
work
so,
and
this,
I
think,
is
what
you
have
to
adjust
when
you
try
to
build
a
network
like
we
have.
A
We
have
it
in
the
big
picture,
and
one
thing
here
in
the
base
is
only
that
we
have
here:
that's
so
docker
core
host
config.
So
this
is
something
I've
mentioned
in
the
in
the
developer
developer
course
several
times
so
don't
store
user
names,
passwords
and
so
on
into
the
in
the
docker
compose
file.
So
you
can
use
the
environment
variables
from
from
the
dot
m
file.
A
So
when
you
have
a
dot
n
file,
docker
compose
will
look
for
this
file
and
use
this
variables
in
the
docker
compose
file,
and
then
you
can
check
in
in
a
git
repository
all
your
configuration
files,
but
you
don't
have
to
check
in
the
dot
m
file.
Yeah
dot
is
in
the
linux
way,
a
hidden
file,
so
you
have
to
you:
don't
have
to
do
this
into
git
repo,
and
you
can
copy
this
later
in
this
in
this
folder.
A
A
A
In
the
same
network,
when
we'll
have
when
you
will
have
here
the
same
network
name
and
that's
the
interesting
part
when
it
comes
to
multi-host
configurations,
then
you
can
use
the
functionality
from
the
docker
overlay
network,
so
that
comes
from
docker
swamp,
but
you
don't
have
to
use
docker
swamp
as
the
dockers
form
services.
You
can
only
use
a
docker
swarm
overlay
network
and
then
with
the
same
network
within
the
same
swarm
network
name.
A
Both
hosts
could
could
connect
together
and
then
you
will
have
two
docker
compose
files
and
two
different
hosts
with
different
public
id
addresses
and
through
the
docker
swarm
environment.
You
will
have
an
overlay
network
and
these
both
docker
compose
files,
work
in
the
same
network
and
that's
a
really
cool
thing
and
yeah.
And
that's
that's
the
part
here.
A
That's
that's
the
reason
why
the
network
is
important
for
this
okay,
so
I
think
these
are
all
to
the
configuration
and
then
we
have
to
the
first
step
is
I
have
here
a
list,
and
this
is
also
in
the
vapor
in
the
github.
Repo-
is
all
the
single
steps
here.
So
please
try
it
at
home
and
try
to
create
this
network
and
the
first
step
what
we
are
going
to
do
now.
A
A
For
this,
and
so
so,
we
need
two
terminals
for
this
example.
So
and
then
in
this
example.
This
is
the
project
folder,
which
is
also
in
the
github
repo
and
the
github
variable
has
everything
involved,
but
not
the
crypto
artifacts
folder
and
not
the
cryptoconfig
folder,
because
this
is
generated
to
the
init
init
script
here,
and
the
first
step
is
that
we
have
to
create
the
crypto
material,
and
this
is
done
here
in
different
steps.
So
but
but
the
steps
are
really
simple.
A
So
we
have
seen
this
in
the
in
the
in
the
presentation.
So
we
have
an
export
variable
for
channel
name
and
important.
We
have
to
set
the
system
channel
name.
So
that's
that's.
Maybe
an
important
part
that
we
have
to
know
that
when
we
create
here
the
general
artifact,
the
the
the
genesis
block,
we
have
to
set
the
system
channel
name
so,
but
we
need
here.
First,
we
need
some
environment
variables,
so
the
path
to
the
config
directory
so
has
to
be
set,
and
here
the
channel
name
and
the
system
general
name.
A
A
A
So
when
we
drive-
and
we
change
this
to
another
configuration,
we
can
use
the
same
config
config
tx
file,
but
we
have
access
here
to
different
profile
names,
and
so
we
can
test
different
configurations
and
the
same
here
for
the
create
the
channel,
config,
config
transaction
part
and
yeah.
It's
basically
the
same
so
but
here
you
have
the
channel
name.
So,
of
course
we
have
to
say
which
channel
we
are
going
to
create
and
we
need
also
a
file
where
this
channel
configuration
is
stored.
A
A
We
will
have
one
pr
research,
so
that's
the
output
from
this
command
here
and
then
in
the
channel
artifact
artifacts.
We
have
the
against
this
block
here
and
we
have
the
channel
configuration
and
here
is
the
anchor
be
updated
configuration
so
also
all
three
files
are
here
so
and
that's
the
first
step.
So
now
we
have
everything
generated.
A
A
So
with
the
power-
and
you
see
here
this
organization's
structure,
so
you
can
see
here
information
for
the
certified
authority.
You
see
here
the
membership
service
provider
folder
with
the
with
the
artificial
materials
you
see,
these
orders,
tls
and
users,
and
so
on
and
the
same
you
can
see
here
in
the
peer
organization
too.
So
and
you
when
we
look
into
this
and
more
and
more
important.
This
is
the
producer
msp.
A
So
we
will
have
here
tls
certificates,
but
we
don't
need
tls
for
a
moment.
We
have
here
sign
up
certificate.
We
have
the
the
private
key
from
this.
You
have
also
the
certified
authority
certificate,
but
we
don't
have
any
favorite
ca
at
the
moment,
but
when
we
create
a
docker
container
with
certified
authority,
then
we
can
use
these
folder.
A
So
when
we
do
this
in
this
way,
so
it's
the
docker
composer
starts
not
in
a
detached
motors.
So
when
we
stop
this,
our
network
is
finished.
This
stops
for
the
moment,
and
but
we
have
the
second
terminal,
so
it
doesn't
matter
for
now
and
now
the
network
is
running
well,
we
can
check
this
with
docker
compose
ps.
So
and
you
see
all
your
containers
are
up
and
running.
A
You
see
a
light
container
the
ottawa
and
pier
0
and
tier
1..
So-
and
you
see
here
these
commands
and
from
now
on,
we
can.
The
next
step
is.
We
have
to
use
the
cli
container
and
we
have,
and
in
the
cli
container
we
have
to
create
a
channel.
We
have
to
join
the
channel
and-
and
then
we
have
to
do
this
for
both
peers
here,
zero
and
v1,
and
then
we
can
install
and
instantiate
some
train
code
and
then
we
can
query-
and
this
is
done
in
very
this-
we
can.
A
So
you
can
go
into
a
container
with
the
command
docker
exec
and
this
it
here
it
means
interactive.
So
you
are
in
this
container
in
the
container
cli,
and
the
last
current
here
bash
is
the
command
which
you
are
going
to
use
in
the
container,
and
when
you
look
here,
these
are
the
the
folders
we
have.
You
have
mapped
to
from
the
host
to
the
container
in
the
docker
compose
file.
We
have
seen
before
okay,
so
we
need
the
channel
name.
A
So
the
first
thing
is,
we
can
create
the
channel
so,
and
this
is
done
with
the
beer
channel,
create
command
so
and
when
we
don't
need
in
this
example,
we
don't
use
tls.
So
the
only
thing
what
we
have
to
say
is
okay,
which
order
this
is
the
order
of
service
and
the
board
and
the
channel
name
and
where
we
can
find
the
channel
configuration
and
this
we
have
seen
in
general
artifacts
folder.
A
A
And
then
you
really
have
this
message
successfully
submitted
proposal
to
join
channel
and
you
control
this
with
a
pl
channel
channel
list.
So
and
you
see
okay,
my
channel
channels
channel
spss
join
this.
Is
this
p?
These
peer
did
this
particular
beer
has
joined
this
channel
called
my
channel
and
we
should
look
fast
in
the
print
environment.
A
And
we
can
grab
the
core
variables,
and
here
we
have
this
free
environment
variables
which
the
the
cli
container
uses
to
connect
to
a
particular
beer.
So
the
cli
container
knows
now
that
we
have
in
the
producer
organization,
and
we
need
this
msp
config
path,
and
this
is
the
accounting
part
to
the
admin
msp
so
because
the
admin
is
allowed
to
create
a
channel,
create
and
install
chain
code
and
so
on
so
and
okay.
We
can
do
this
also
for
the
anchor
here.
A
A
A
Then
we
switch
back
to
b0
and
then
now
we
are
ready
to
install
the
chain
code
so
install
the
chamber.
This
is
is
simple,
so
we
can
use
the
peer
chain
code
install
command
in
that's
the
process
for
one
favorite
one
for
one
for
in
the
in
the
two
point,
two
point
versions:
there's
there
are
another
commands:
the
there
is
another
life
cycle
for
the
chain
code,
installation,
but
in
1.4.
A
We
can
do
this
in
this
way
and
we
have
to
set
the
name
for
the
chain
code,
a
version
from
your
chain
code
and
where
the
chain
code
lives
and
by
default
go
is
used.
So
we
don't
have
to
say
that
no
chairs
or
a
java
chain
code.
So
when
we
don't
have
a
parameter
for
the
for
the
language
of
the
of
the
chain,
code
then
is
go
is
used
so,
and
we
have
also
in
the
cli
container
on
this
part.
You
can
see
here.
A
A
We
have
again
as
this
block
so
and
now
we
have
also
a
channel
and
on
this
channel
we
can
have
different
chain
codes
and
this
chain
code,
and
when
you
install
the
chain
code,
you
have
to
install
it
and
and
here
and
then,
but
when
you
want
to
use
it,
you
have
to
instantiate
it
and
that's
the
second
command
which
we
need
so
on
ps0.
On
the
first
tier,
we
have
to
instantiate
the
chain
code
and
that's
depends
on
the
chain
code.
A
So
what
is
what
is
the
initial
command
for
the
change,
then,
in
this
in
the
standard
chain
code?
It's
also
a
a
message,
a
key
and
the
value
of
nicer.
This
is
message,
one
is
the
key
and
hello
is
the
value
and
with
this
parameter
p
we
can
set.
Let's
call
it
endorsement
policy,
that's
another
interesting
topic,
but
for
and
for
our
scenario,
we
have
only
the
producer
organization
and
we
have
only
to
say
okay
one,
but
this
means
only
when
the
producer
msp,
the
producer
organization,
said
this
transaction
is
valid.
A
Then
this
this
transaction
is
also
valid.
But
when
you
have
two
organizations,
then
you
can
say
okay
to
do
some
organization.
One
and
organization,
producer
and
organization
producer
must
have
the
same
state
of
lecture
and
must
say:
okay,
this
organization
is
valid
and
then
the
transaction
is
finally
valid
again.
A
So
this
also
one
so
and
now
we
have
the
chain
got
installed
and
we
have
in
this
density.
Then
we
can
switch
back
to
the
tier
one
and
we
have
to
install
and
that's
an
important
part
for
your
understanding.
So
in
favorite
there
are
several
several
terms
for
peer.
We
have
learned
the
anchor
beer,
that's
between
the
communication
tuition
organizations.
A
This
is
responsible,
then
we
have
an
endorsement
here
and
then
we
have
committing
bills
and
committing
bills,
and
endorsement
tiers
are
the
same.
But
the
difference
is
when
you
install
chain
code
on
a
beer,
then
it
comes
to
the
endorsement
field,
and
that
means
that
only
peers
with
only
endorsement
peers,
can
invoke
chain
code
and
query
chain
code.
A
A
A
Installed
and
with
the
command
be
a
chain
code
list
installed,
you
can
see
on
the
beer
which
chain
codes
are
installed
here,
so
this
command
is
not
in
the
list,
but
you
can
find
it
very
easily.
So
now
we
are
so
we
are
ready
so
and
then
we
can
query
so
now
we
have
an
initial
value
from
the
message
one
and
when
we
do
this.
A
A
So-
and
you
can
see
here
all
there
tranquil
all
the
all
the
docker
container
running-
and
you
see
here
this
for
this-
both
dev
tier
one
and
dev
piano
container,
and
these
are
the
chain
code
containers.
So
every
chain
code
runs
in
an
in
a
controlled
environment
and
in
a
single
container
and
every
deer
has
its
own
train
code
container
and
these
chain
code
containers
are
started
automatically
when
you
install
and
instantiate
a
chain
code.
So.
A
But
you
don't
see
this
chain
code
container
when
you
say
doc
appears,
and
you
see
only
so.
The
reason
for
this,
for
that
is
that
docker
composer
looks
on
to
the
services
on
the
docker
composed
yaml
file
and,
and
we
don't
have
a
setup
for
these-
both
jengkol
containers
and
and
that's
the
reason
why
you
have
to
look
with
docker,
compose
and
also
docker
network.
Ls
is
a
good
thing.
So,
and
you
say
here
here
is
our
sunshine
network.
A
So-
and
you
see
here
when
you
say
this
is
our:
this
is
our
network-
the
network
was
called
sunshine
and
then
the
environment
variable
here
in
this
one
we
have
set
the
the
net
the
net
prefix
here-
and
this
is
the
unknown
right,
and
what
you
can
see
here
also
for
troubleshooting
is
rd
containers
are
all
your
containers
inside
of
the
network
and
with
this
command.
You
can
control
this,
and
you
see
here
the
containers,
that's
a
json
file,
and
you
see
here.
Okay,
this
is
p1.
A
A
And
with
this
command,
you
can
that's
good
for
dru
bible
shooting.
So
when
your
water
is
not
in
this
network,
then
you
cannot
connect
to
the
other
idea
is
not
in
your
network.
You
cannot
connect
to
the
other.
So
that's
a
a
good
point
to
see
when
something
not
not
this
working,
then
you
can
look,
are
all
containers
in
the
same
network
and
that's,
I
think,
a
common
mistake
which
can
happen
okay.
A
A
One
so
and
message
two
is
sunshine.com,
and
this
is
one
method
to
query
to
check
if
the
network
is
ready
so
from
there
admin
administrator
perspective.
So,
but
you
don't
have
to
go
inside
this
container,
you
can
do
it
also
from
outside.
So
the
only
thing
you
can
for
this,
you
can
use
the
docker
exec
command
and
it's
pretty
much
the
same,
so
you
can
say
docker,
exec,
cli
and
then
your
command.
This
command
is
the
same
as
you
have
to
set
inside
the
container
and
when
you
have
this
as
a
prefix,
so
you
can.
A
The
blockchain
are
also
from
outside
when
we
use
the
docker
exec
command
with
the
same
arguments
and
more
important
is
when
you
want,
as
we
have
seen,
the
default
configuration
is
for
the
pier
0.
So,
but
when
it
when
we
want
to
query
the
peer
1
from
outside,
then
we
have
to
change
the
environment
variables
and
we
can
do
this
with
the
e
option
here.
A
A
A
So
we
have
the
crypto
material
ready
for
the
network
for
a
single
organization
for
order
system
for
tls,
for
example,
but
then
what
we
need
for
this
example
different
users
and
the
chain
code
should
have
different,
should
control
different
roles
so
that
we
that
we
know
that
when
the
chain
code
is
called
from
user
from
identity,
a
that
this
is
identity
a
and
from
bob.
In
the
change
of
this
code
from
another
position,
then
it's
identity,
b
and
so
on.
A
So,
but
and
for
this
we
d,
we
need
specific
users
and
we
don't
want
to
have
user
one,
two,
three,
four
and
so
on
and
for
this
we
can
create
a
favorite.
J
container
include
this
in
the
docker
compose
file,
and
then
we
can
create
this
specific
users
for
the
string
code
and
how
you
can
do
this.
This
will
be
maybe
part
for
the
for
the
next
session
and
yeah.
A
A
Start
the
network
in
a
detached
mode
and
to
start
a
network
in
a
detached
mode.
That
means
in
the
background,
so
then
you
have
to
here
put
the
parameter
d,
yeah
minus
d
and
then
the
docker
compose
network
runs
in
the
background
and
then
you
can
call
the
locks
command.
Docker
locks
command
here,
but
we
can
do
it
here
in
the
in
the
terminal.
So-
and
you
see
here,
this
is
the
docker
locks
command.
A
So
important
is
the
f
parameter
here.
So
that
means
that
that
the
the
the
lock
is
is
con
con
continually.
When
you
don't
use
the
f
parameter,
then
you
have
a
lock
until
now.
So
it's
finished,
so
that's
the
last
lock
entry
so
and
then
you
use
this
f
parameter
yeah.
You
can
monitor
the
the
blockchain
yeah
the
peer
in
this
case,
to
be
a
serum
so
and
and
that's
also
useful
for
troubleshooting.
A
So
when
you
have
problems
to
connect
to
the
spear
or
when
you
want
to
see
what
happens
exactly
on
this
spear
and
then
you
can
have
here
this,
you
can
lock
this
only
on
the
spear.
So
that's
also
helpful
for
the
train
code
containers
when
you
debug
the
train
code,
some
chain
code
values
from
from
your
chain
code,
and
this
we
have
seen
network
inspect
so
so
it
is
also
important
to
know,
are
all
my
containers
in
the
same
network
and
then
here
the
cleanup
process.
A
A
Rm
key
is
only
containers
and
not
images
and
rni
clears
images,
and
you
can
also
use
some
specific
commands
here.
So
if
you
only
want
to
clear
the
chain
code
container,
then
this
is
a
commonly
used
command
to
clear
only
the
chain
code
containers.
So
but
this
is
more
for
the
for
the
development.
So
as
an
administrator,
you
should
have
a
working
train
code
and
you
don't
have
to
think
so
much
about
the
chain
code
configuration
okay,.
A
So
I
think
I
have
tried
to
be
to
give
my
best
to
be
under
one
hour
so
that
we
have
time
a
little
bit
to
discuss
and
have
some.
And
if
you
have
some
questions
so,
but
you
see
it
takes
every
every
time
it
takes
a
little
bit
more.
But
I
think
here
you
have
a
good
starting
point
to
see
how
you
can
create
a
network,
and
I
think
it's
important
to
try
this
and
go
a
little
bit
away
from
the
example.com
from
the
build.
A
Your
first
network
example
is
a
very
good
example.
It
is
it's
very
good
for
chaincode
development.
So
as
a
chaincore
developer,
you
can
use
this
build
your
first
network
example
and
then
you
have
a
can
test
different
configurations,
couchdb
favxca,
different
ordering
system
and
so
on.
So
you
have
by
default
two
organizations
and
you
can
test
the
endorsement
policies
and
so
on.
A
So,
if
not
so,
but
take
take
this
opportunity,
you
can
ask
questions.
Don't
be
shy,
ask
something
you
can
also
say
when
you
for
the
next
session,
when
you
want
a
particular
thing
and
and
when
it
is
okay
for
the
for
the
learning
process,
we
will
try
to
include
this
in
the
learning
process.
But
what
we
don't
offer
here
is
that
we
don't
give
a
solutions
for
business
problems
or
something
like
this.
So
this
is
a
learning
channel,
so
we
are
trying.
A
So
because
that's
there,
that's
the
aim
of
this
of
this
of
this
study
circle
that
you
are
get
help
for
their
certification,
but
you
don't
have
to
do
the
certification,
so
that's
only
for
learning,
so
you
can
learn
as
much
as
you
want
great
job
ronald.
It's
really.
I
think
it's
helpful
for
everyone
to
create
their
own
channel
and
create
their
own
network.
Well
done
great
job.
Thank
you
so
much.