►
Description
A virtual meetup hosted by Hyperledger Seattle on September 15, 2021 focused on using Fabric Operations Console to manage your Hyperledger Fabric Network. This session would include a high-level architectural overview, the new console's key features, and a live demo of it working with "test network" from Fabric Samples. We will also cover additional console integration options currently available using MiniFabric.
More about Fabric Operations Console is at: https://github.com/hyperledger-labs/fabric-operations-console
More about MiniFabric is at: https://github.com/hyperledger-labs/minifabric/
Speakers:
Varad Ramamoorthy is currently one of the Lead Architects for IBM Blockchain Platform (IBP). He leads the User Interface team that builds IBP Console that won one of the prestigious Red Dot Design Awards. Varad has been part of IBM for over 20 years, working on several products as UI architect. He is passionate about user experience, making product consumption easier for end-users.
Tong Li is a senior software engineer at IBM. He has been a software architect, developer, deployer, operator, advocator and a consultant through his professional career. His main focuses in recent days have been cloud computing, social software and Blockchain technologies. He is very passionate about large software system integration and automation. He created Minifabric and continued his contributions to the product in last two years.
----
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 #HyperledgerMeetup #Blockchain
A
B
Right,
wonderful
thanks!
Everybody
for
the
interest
in
the
fabric
operations
console.
Let
me
start
sharing
my
screen
all
right.
So
so
today
we're
going
to
talk
about
you
know
again
the
fabric
operations
on
console
right.
So
I
think
you
know
people
know
from
the
recent
announcement
from
ibm
right.
You
know
the
the
donation
per
se
of
the
console
to
the
open
source
community
right.
So
the
console
has
been
you
know
again.
We
have
been
using
console
within
ibm
for
managing
fabric
networks
as
part
of
ibm
blockchain
platform.
B
B
You
know
how
to
use
the
test
network
to
again
against
the
console,
and
then
we
will
demo
like
how
you
can
easily
create
channels
on
the
ui
and
then
you
will
also
show
you
know
how
to
use
the
lifecycle
flow
right.
You
know
the
typical
proposal
through
commit
process,
and
then
we
will
touch
on
some
future
topics
and
we
would
love
to
hear
from
the
community
on.
In
terms
of
you
know
what
other
future
topics
you
guys
might
be
interested
in,
but
you
know
we
have
some
topics
planned
right.
B
You
know
I
can
share
with
you
guys
with
that
right.
So,
let's
start
with
the
architect.
So
what
is
the
console
right
so
console
again
is
the
tool
that
you
can
use
to
manage
your
existing
fabric
network
right.
So,
let's
assume
you
have
tiers
orders
cas
and
sucks
right.
Currently,
most
people
would
use
cli
or
sdk
or
some
sort
right
to
manage
it.
B
A
B
The
console
does
right,
so
here
is
the
picture
that
shows
the
different
components
that's
involved,
so
console
under
the
covers
has
multiple
packages
right.
You
know
there
is
three
parts
to
the
package.
We
won't
cover
the
details
of
it.
Yet
you
know
that
may
be
one
of
the
following
topics
right,
but
it
has
the
ui
component,
which
is
an
which
is
a
react
application,
and
then
it
has
a
node
component
to
it.
B
That
is
responsible
for
doing
all
the
api
stuff,
and
then
it
also
has
a
component
for
grpc
communication.
It's
a
set
of
libraries
that
javascript
libraries
to
be
more
specific,
that
do
jrtc
stuff
right
so
and
then
the
underlying
database
is
in
a
couchdb
right
for
managing
and
maintaining
some
of
the
configuration
information
and
such
right
so
and
then
the
peers
and
orders
already
have
again
grpc.
They
talk
to
your
pc.
B
However,
we
have
grpc
web
proxy,
that's
sitting
in
between
again
the
console
and
the
peers
and
orders
that's
the
product,
seeing
the
calls
right
so
that
and
then
we
also
have
to
have
config
translator.
Basically,
that's
responsible
for
translating
the
request
between
a
json
and
protocol
and
vice
versa.
That's
another!
You
know
component
that
sits,
you
know
in
in
the
mix
right.
So
let
me
move
on
to
the
next
one,
which
is
a
demo
right.
B
So
so,
if
I
go
back
to
the,
let
me
make
it
bigger
right,
so
the
I'm
on
the
again
the
the
git
github
page.
You
know
for
the
console
right,
it's
under
the
hyperledger
labs.
Right
again
it
talks
about
all
the
capabilities
right.
You
know
viewing
modifying
channels
install
instantiate.
We
have
support
for
the
1.4
flow,
which
is
the
traditional
cds
format.
You
know
for
packaging
and
then
also
the
top
gc
format.
B
So
again,
I'm
just
going
to
give
you
guys
a
high
level
world
view
today,
and
then
we
will
have
drill
down
on
individual
topics
right
as
and
when
we
need
right.
So
again
we
talked
about
the
architecture
and
what
we
are
going
to
show
today
right
in
terms
of
demo,
how
you
can
use
console
against
the
test
network
that
is
set
up
with
again
in
fabric
right,
so
we
do
currently
only
support
up
to
2.2.3.
B
In
the
sense
you
know
there
is
the
channelless
system.
Channelless
configuration
feature,
that's
in
2.3.
The
console
does
not
support
it
right.
So
you
know
we
do
rely
on
system
channels
for
some
of
the
information.
So
that's
just
something
to
keep
in
mind
and
again
the
script.
We
have
a
simple
script
right.
You
know
you
can
look
at
the
script,
but
all
it
does
is
it
pulls
down
2.2.3.
B
A
B
Represent
the
peers,
orders
and
cas
and
msb
definitions
and
all
the
rest
right,
so
the
create
asset
step
basically
takes
the
test
network
right
and
then
it
has
a
template,
json
files
for
each
of
the
assets,
and
then
it
basically
pulls
stuff
the
latest
certificates
and
all
that
from
the
test
network
and
then
generates
a
zip
file.
That's
essentially,
you
know
fit
for
the
test
network
that
can
be
imported
into
the
console.
B
Right
again
feel
free
to
ask
questions.
I
mean
I,
I
don't
you
know,
I
want
to
keep
it
more
again,
informal
right,
so
there's
no
like
formal
stuff
right.
So
if
you
have
questions
you
know
feel
free
to
ask,
and
so
that's
basically,
once
you
generate
the
zip
file,
you
can
import
it,
and
then
there
is
a
set
of
steps.
We
will
go
through
to
again
create
the
certificates
from
the
ca,
attach
it
to
the
peers
and
orders
and
create
channels
right
again,
the
steps.
A
B
B
B
So
there
are
the
grpc
with
proxy
yeah
yeah.
That
is
the
one
that's
going
to
proxy
the
request
because
way
back
when
we
started
right.
If
we
directly
try
to
talk
to
the
peer
using
grpc,
we
kept
having
crash
issues
so
back.
Then
we
added
jrpc
proxy.
It's
simple
again
web
proxy
that
just
processes
that
it
goes
from
http
back
to
the
pier
to
the
grpc.
A
B
B
Yeah,
so
the
main
requirement
is
to
be
able
to
add
the
grpc
with
proxy
in
front
of
your
peers
and
orders.
If
you're
able
to
do
that,
you
know
have
the
right
port
configuration,
then
it
should
work.
So
since
we
are
on
it,
I
can
quickly
show
you
guys
right
again.
I
want
to
keep
it
more
informal,
so
I
want
to
make
sure
people
know
the
information
to
make
it
work
right.
B
So
if
you
go
into
the
scripts,
I
think
so
it
builds
the
images
right,
but
then,
if
you
go
into
docker
and
if
you
go
into
grp
see
where
so,
this
builds
the
grpc.
But
then,
if
you
see
the
grpc
web
docker
compose
file,
you
can
see
you
know
again
how
the
proxy
is
used
to
configure
talking
to
an
existing
network.
So
in
this
particular
case
the
certificates
and
the
ports
and
the
backend
address,
and
all
that
is
running
in
docker.
B
A
A
B
Yeah,
it
should
work
because
again
we
proxy
that
request
also
right.
So
if
you
see
again,
this
picture
right,
the
proxy,
not
just
the
grpc,
and
maybe
there
is
additional
lines
going
from
the
console
to
the
directly
to
the
peer
and
order.
We
didn't
call
that,
but
there
is
a
connection
from
console
console
basically
proxy
still,
as
it
goes
back
to
the
orders
and
tiers
on
the
operations
board,
so
that
should
be
fine
as
well.
Okay,
so
that
sounds
like
you're,
interacting
with
the
user
interface
side
right
right
right.
B
B
A
B
Yep
yeah,
that's
how
again
the
the
console
currently
is
the
one
you
know
that
works
in
ibm,
blockchain
platform,
which
runs
in
openshift
and
kubernetes,
and
you
know
what
not
right,
so
you
should
be
able
to
deploy
it
onto
any
kubernetes.
There
is
no
restriction
in
terms
of
running
it.
Only
in
docker
you
should
be
able
to
work
with
it
in
kubernetes.
B
B
Okay,
all
right,
so,
let's
move
on
to
the
demo
part
right
and
then
you
can
come
back
with
additional
questions.
So
what
I
did
to
save
some
time
is.
I
ran
the
first
command
the
setup
network.
All
it
does,
is
it
pulls
down
fabric
two
two
three
as
you
can
see,
and
then
it
it.
It
basically
starts
at
the
network
right
this
step
took,
I
don't
know,
maybe,
depending
on
your
connection,
speed.
It
needs
to
download
all
the
binaries
right,
the
images
and
then
start
up
with.
B
Maybe,
like
I
don't
know,
five
six
minutes,
I
didn't
want
people
to
sit
on
the
call
for
five
minutes
just
staring
at
these.
So
just
so
you
know,
you
know
again
you
the
first
step.
Is
you
clone
the
repo
right?
I
cloned
it
the
console
and
then
once
you
go
into
console,
you
just
do
setup
network
up
again
just
command
this.
B
On
the
you
know
again
the
git
github
page
right
and
then
you
again
it
does
all
it
does,
is
again
check
out
and
then
download
all
these
images
and
then
it's
again
it
starts
up
again
peers
order,
cas
it's
all
done
by
the
test
network
script
and
at
the
end,
you
are
left
with
a
channel
called
my
channel,
and
then
it
has
the
fab
card.
Smart
contract
installed
on
it
right.
That's
basically
the
current
state
right.
So
I
do
now
have
a
test
network
with
that.
B
B
B
B
This
is
going
to
basically,
you
know,
get
the
certificates
and
such
you
know
and
then
use
that
use
it
against
the
template
to
generate
a
zip
file
right.
So
you
would
be
you
know.
So
this
is
the
zip
file.
It'll
generate
right.
So
let's
go
on
to
the
console
right.
So
the
next
step
is
to
go
into
the
ui.
B
One
thing
I
would
point
out
is
so
we
use
you
know
the
subtle
crypto.
You
know
the
libraries
right,
you
know
that
are
browser-based
and
they
expect
you
to
run
either
on
localhost
or,
if
you're
running
on
non-local
boost
it
should
be
https
right.
If
it's
not,
then
you're
gonna
get
you
know
now.
If
you
see
the
browser
locks,
you
will
see
messages
saying
like
you
cannot
run
this
on
non-tls
right
so
ensure
like
if
you're
accessing
the
console
or
anything
other
than
localhost.
B
You
know
it's
tls
enabled
right
so
we'll
have
some
documentation
instruction
and
follow
on
topic
on,
like
you
know
how
to
run
it
in
a
production
kind
of
setup
with
tls
and
all
that.
But
you
know
for
now
just
be
aware:
localhost,
you
know
should
be
fine,
but
if
you
change
the
port
I
mean
not
work,
but
the
host
name.
B
B
And
immediately
your
presented
will
change
your
password
right.
I
know
there
is
issues
open
asking
like
you
know.
Can
you
like
disable
this?
You
know
the
password
change
prompts
or
you
know,
from
doing
local
development
testing.
I
can
just
directly
jump
into
the
screen,
so
we
do
know
that
that's
coming
up
later,
but
let's
do
that
change
it
to
some
other
password
and
then
now
I'm
asked
to
log
in
right.
B
B
B
Yeah,
so
now
you
have
a
clean
console
with
nothing
right,
so
the
next
step
is
to
import
your
configuration.
One
thing
I
do
want
to
mention
is
wallet
is
a
concept
right.
You
know
again
we'll
actually,
let's
finish
the
import
and
then
I
can
walk
through
that
concept,
so
import
right,
that's
the
next
step,
and
so,
if
you
go
into
again
github
console
work
area,
you
should
see
the
new
console
asset
zip
file,
import.
That.
B
You
know
two
different
cas
for
each
of
the
organizations
and
then
you
got
the
order
and
you
got
the
two
peers
right.
So
the
first
step
you
would
want
to
do
is
to
be
able
to
generate
again.
You
know
you
know
the
the
certificates
for
your.
You
know
talking
to
the
pearson
orders
right.
So
let's
go
into
the
order.
First,
then
it
says
associate
identity
and
the
default
password
for
all
of
the
cas.
I
think
for
the
test
network.
This
is
coming
from
test
network
right
admin,
admin,
pw.
B
So
now
as
simple
as
that
right
so
now
it
generated
a
certificate
for
the
ca
to
talk
to
you,
and
then
we
are
talking
to
the
ca
with
the
certificate
and
you
can
list
the
again.
The
all
the
enrolled,
ids
and
secrets
that
are
registered
on
that
ca,
and
the
next
step
you
will
do
is
to
generate
a
certificate
for
the
admin
identity
right,
so
enroll
an
identity.
B
Or
to
two
all
right
so
now
we
have
certificates
for
all
the
peers
and
orders
to
talk
to
right.
So
all
the
registered
certificate
go
into
the
wallet
right.
That's
where
you
see
the
certificates
right.
So
if
you
click
on
one
of
them,
you
can
see
the
certificate
right
again
and
the
private
key
right.
So
those
are
available.
You
can
export
the
identity
which
will
give
you
the
you
know
again
a
json
file
that
you
can
carry
along
between
different
consoles.
That's
something
you
can
do
so
just
for
information.
B
These
certificates
are
only
stored
in
the
context
of
the
browser.
It's
not
stored
anywhere
else,
so
they
are
in
local
storage
right,
so
meaning
the
tricky
thing
is
right.
Let's
say
you
set
up
something
you
worked
with
the
console
and
then
you're
like
you,
deleted
everything
and
you
recreated
the
environment
right
you're
still
going
to
have
the
console
under
this.
You
know
the
the
local
storage,
you
can
go
delete
individually
or
you
can
just
delete
these
two.
You
know
keys
right
from
the
local
storage
to
basically
clear.
B
You
know
the
the
all
the
wallet
items
right,
just
just
okay,
but
okay,
so
now
that
we
have
the
identities,
let's
just
go,
associate
it
with
the
orders
and
peers
right.
So
now
I'm
going
to
connect
the
order
and
then
it
knows
you
know,
based
on
the
orders
certificate.
What
are
the
valid
certificates
to
be
associated?
As
you
can
see,
it
did
not
show
the
rf1
stuff.
B
B
So
as
simple
as
that
right,
so
you
got
the
order.
Now
we
pulled
the
system
channel
and
you
can
see
the
you
know
the
organic.
You
know
the
orders
of
this
administrator.
You
can
see
who
the
consortium
members
are,
and
you
know
again,
you
can
even
delete
the
consortium.
Member,
essentially
updating
the
system,
channel
answers
right
so
and
then
you
can
also
see
who
the
consenters
are
on
the
system
channel,
which
is
again
the
single
order
right.
B
So
for
that
peer
organ
admin
and
then
now
you
can
see
the
actual
channel
right.
So
that
is
my
channel
that
has
seven
blogs.
You
can
drill
down
into
that
right
into
the
channel
and
then
you
can
see
that
it
has
half
car
installed
using
the
new
tool
lifecycle
flow
and
then
you
can
see
the
transactions
on
it
right
blocks
and
then
transactions
within
it.
B
So
this
has
some
again
sample
data
right,
so
you
can
see
the
read
write
set
like
in
some
form
and
then
you
can
also
see
the
channel
details
right
again.
What
nodes
are
part
of
the
channel
participation
in
terms
of
like
order?
This
order
is
part
of
the
channel.
The
sphere
is
joined
with
the
channel
and
then
you
can
see
that
one
msp
and
r2
msp
are
the
members
of
the
channel
and
so
on
and
so
forth.
B
Right
now,
if
you
have
access
control
list,
then
you
see
that
and
then
you
can
manage
the
anchor
peers
right.
So
if
you
want
to
delete
that
appears
or
add
additional
anchor
peers,
you
can
do
that
right
so
fairly
easily.
So
these
all
would
result
in
channel
update
transaction
right.
So,
depending
on
what
you're
doing
you
might
need
to
get
signatures
from
other
consoles
or
participants,
but
for
this
network
everything
is
local
test
network.
So
you
know
so
you
should
be
able
to
perform
all
the
operations
without
relying
on
anybody
right.
B
And
we
got
the
again
from
the
second
year:
we
can
get
the
channels
and
then
you
know
you
can
see
channel
information
right.
So
that's
that's
up
to
the
channel
part
right.
So
next
I
would
show
you
guys
how
to
use
the
console
to
do
the
life
cycle
flow.
So
before
I
do
that
right.
Are
there
any
additional
questions.
A
B
That's
a
good
question
right,
so
you
so
there
is
two
parts
right,
so
you
can
go
to
the
ordering
service,
for
example,
and
then
say
like
I
want
to
add
another
consortium
member.
So
if
you
already
have
a
speed
definition,
you
can
fairly
easily
add
it.
But
in
this
case
I
don't
have
anything,
that's
not
added,
so
you
don't
see
it.
B
B
Right
next,
so
now
that
I
have
a
new
organization,
I
should
be
able
to
go
down
to
the
the
again
the
ordering
service
and
then
update
the
system.
Channel
and
say
like
oh
now,
for
3d
is
also
a
member
right
and
then,
if
you
have
peers
from
that
organization,
obviously
you
can
add
it
right
now
import
it
like
if
it's
running
somewhere.
So
that's
basically
the
process
right.
That's
that
answer
the
question.
A
B
That's
right,
so
that's
a
good
segue
into
what
I
wanted
to
mention
right.
So
so
the
ibp
console
that
offering
has
options
to
add
peers
and
orders
and
cas
right
into
an
existing
kubernetes
cluster.
But
the
open
source
console
does
not
have
that
capability
right.
So
it's
purely
managing
an
existing
fabric
component
right,
not
like
provisioning
and
creating
a
new
component.
That's
not
something!
That's
that's
possible
from
the
console
right
now.
A
B
B
B
B
A
A
A
A
C
B
So
so,
basically,
I
think
you
know
the
console
knows
the
context
of
the
channel
and
what
operation
it
performs
and
then
takes
away
some
of
the
complexities
with.
Like
you
know,
how
do
I
sign?
What
do
I
use
to
assign
right?
If
it
has
the
information
to
you
know
it
it'll
try
to
update
right
so
so
I
can
delete
it
just
so
we
don't
have
it
so
this
will
remove
it
from
the
system
channel.
B
Let's
learn
from
system
all
right,
so
next
step.
So
the
last
piece
of
information
I
want
to
show
before
I
give
it
to
tong
right
to
show
the
mini
fabric.
You
know
how
mini
fabric
works
against
the
console
I'll
show
the
the
finishing
part
of
it,
which
is
using
the
tool
lifecycle
right.
So
let's
go
into
the
channel,
so
I
have
already
my
channel
and,
as
you
can
see,
the
capability
is
already
2.0,
so
you
can
see
the
three
different
capabilities
on
the
channel
right
application
ordering
and
then
the
channel
capability.
B
B
So
you
know,
then
you
get
a
question.
Do
you
want
to
install
it
on
all
peers
that
for
the
given
organization?
So
I
so
if
you
remember,
the
first
step
I
chose
is
I'm
operating
in
the
context
of
part
one.
So
it
will.
If
you
have
multiple
peers
for
that
organization,
it's
going
to
install
it
on
all
peers
for
that
organization,
but,
as
you
can
see,
it's
like
1x,
which
is,
I
just
have
one
here
for
that
organization.
B
It's
gonna
install
it
on
just
that
one
and
as
part
of
the
definition
of
the
proposal,
what
you
want
to
call
the
name
and
the
version
for
the
proposal,
and
then
you
can
use
the
default
endorsement
policy
or
you
can
update
it
right
into
advanced
mode
if
you
choose
to,
since
there
are
two
members
on
the
channel
by
default.
We
say
like
one
of
these
two
members
stand
in
doors,
but
you
can
say,
like
you
know
you
can
say
I
want
both
of
them
to
invoice
right.
B
If
you
want
to
do
that,
so
it's
from
the
ui,
you
know
you
can
you
can
control
the
endorsements?
If
you
don't
want
to
use
the
default
right,
which
is
majority,
then
next
and
then,
if
you
have
private
data
collection
right,
you
can,
you
know,
use
the
json
to
export.
You
know
upload
the
json
so
part
of
the
definition.
You
will
get
the
pdc
and
then
again
you
get
a
summary
at
the
very
end.
Right
use.
B
B
B
A
B
Let
me
proceed
still
so
what
it
is
doing
right
now
is
it's
installing
the
the
smart
contract
on
the
pr
tools
and
then
it's
doing
creating
a
definition
for
the
given
organization,
and
so
that's
the
second
step
right
it's
proposed
and
then
the
next
step
is
to
commit.
That's
the
next
step
right.
If
there
are
multiple
organizations
you,
since
there
are
multiple
organizations
I
can
approve
as
the
other
organization,
because
I
own
everything
I
have
all
the
certificates
for
both
of
the
organizations,
I
can
do
it
on
the
same
console.
A
B
Yep
exactly
so,
okay,
so
now
the
status
changed
as
you
can
see
before
it
was
proposed
and
since
both
of
them
approved
now
it's
ready
to
commit
right.
So
we
do
a
check
to
see
you
know.
Both
our
organizations
are
true
because
you,
the
default
policy,
was
majority
need
to
approve.
So
now
you
can
commit
the
process,
because
you
know
you
have
the
you
know
the
the
necessary
approvals
and
the
commit
can
be
as
any
one
of
the
two
organizations
right.
So
I'm
going
to
just
use
one.
B
A
B
So
now,
as
you
can
see,
this
particular
chain
code
is
committed
onto
the
channel
and
then
again
you
can
generate
transactions
on
it.
So
that's
the
life
cycle
flow
again,
like
sonic
said
right.
You
know
if
it
is
on
multi
console,
you
would
do
the
approval
on
multi
console
different
consoles
and
then
eventually
commit
to
the
console
facilitates
all
that.
So
again,
that's
one
of
the
future
topics
how
you
can
set
up
that
kind
of
scenario:
multi-console
production
setup.
You
know
that
would
be
one
of
the
follow-on
sessions.
B
So
before
I
give
control
to
tom.
One
quick
thing
I
want
to
show
is:
you
can
obviously
create
a
channel
and
join
channel
from
the
console.
So
when
you
create
a
channel
you
know
you
can
say
I
want
so
so
then
I
pick
which
order
I
want
to
do
it
on
and
I
can
choose
them
as
three
definitions
that
I
want
to
use
right.
You
know,
I
can
say
all
one
is
the
operator
and
who
is
just
a
writer.
B
You
can
do
some
of
those
access
control,
stuff
and
then
one
and
then
I
can
say
I'm
creating
as
a
one
and
then
you
get
to
pick
the
application
and
order
capabilities
on
the
channel.
So
I'm
going
to
say
two
of
capabilities
then
use
the
default
for
order,
and
this
is
the
life
cycle
policy
since
I
chose
to
owe
as
the
type
now
I
get
additional
options
to
do
life
cycle
endorsements.
B
So
how
many
need
to
endorse
before
you
can
change
the
definition
of
the
again
the
smart
contract,
instantiation
definition
right,
so
you
can
specify,
or
you
can
choose
majority,
I'm
just
going
to
leave
with
the
false
but
know
that
you
can
customize
some
of
those
options.
You
can
again
change
the
block,
cutting
parameters
right.
You
know
how
many
message
counts
and
the
size,
and
all
that
this
is
specifically
application,
channel
kind
of
capability
right.
B
B
Okay
and
then
I
can
click
on
it,
and
then
I
see
that
there
are
two
gears
because
again
it
knows
the
channel
members
are
those
two
and
then
it
gives
me
option
to
join
both
of
those
peers,
and
I
can
choose
to
make
the
mantra
peers
again.
This
is
going
to
submit
a
channel
change
and
then
add
whichever
the
prc
chooses
anchor
fields
right
so
join.
B
That's
it
right.
So
now
I
have
created
the
second
channel.
I
joined
both
of
my
peers
and
I
made
the
macro
piece
all
in
that.
You
know
as
part
of
that
step.
Right
and
one
last
thing
is,
you
know,
obviously
you
can
drill
down
into
a
channel
and
then
you
can
click
on
the
gear
to
make
a
change
to
the
channel
right.
If
you
want
to
add
new
members
delete,
you
know
ad
consenters,
you
know
it's
it's
it's.
B
B
A
B
All
right
thanks
chris
thanks
for
the
feedback
again,
if
you
based
on
what
you've
seen
if
you
need
any
follow-on
topics,
folks,
you
know
feel
free
to
add
it
to
the
chat.
So
we'll
come
back
with
additional.
You
know
this
is
the
first
of
many
to
come
right.
So
we'll
have
more
of
these
sorts
of
deep
dives
right.
You
know
we'll
have,
and
then
you
know,
if
you
have
comments,
add
it
to
the
comments
and
we'll
get
back
to
you
guys.
Thank
you.
C
So
to
get
started
you
you
just
need
darker
and
nothing
else,
no
darker
compose
whatsoever,
just
darker
will
be
good,
and
then
you
copy
paste
this
one
line
if
you're
on
linux
or
mac,
if
you're
on
windows
copy
this
line
execute
the
next
step
is
to
minify
up.
So
that's
all
you
have
to
do
to
set
up
a
fabric
network
which
used
a
default
spec.
If
you
don't
like
that
default,
spec
create
your
own
spec.
C
C
I
have
done
this
while
verado
was
talking
so,
as
I
said,
you
just
need
to
do
this.
One
thing
I
did.
I
did
that
extra
flag.
That's
e!
True!
This
basically
says
when
I
set
up
fabric
network.
I
want
the
endpoints
of
these
nodes,
holder,
peter
and
even
ce
node,
to
be
able
to
accessible
from
outside
this
little
machine.
C
This
machine
actually
is
a
virtualbox,
1204
virtual
machine
and
only
has
four
gigabit
memory,
so
I
just
did
this
one
command
if
you
want
to
try
it
on
yourself,
it's
fine
just
follow
the
instruction
here.
I
just
showed
you,
which
will
actually
set
up
the
fabric
network
and
include
the
download
the
images
of
the
peer
and
folder
and
start
a
network
and
then
create
a
channel,
simple
channel
and
install
a
sample
chain
code.
C
All
that
kind
of
stuff
set
up
your
anchor
appear
and
we
can
save
from
jenkins
install
proof
commit
initialize
all
that
kind
of
stuff
right.
So
at
this
point,
the
fabric
network
actually
is
up
running
right,
but
for
this
talk
I
just
want
to
show
you
how
you
can
quickly
set
up
a
console
which
works
with
the
fabric
network.
You
set
up
use
mini
fabric,
all
right,
so
to
do
that,
it's
really
really
easy.
Just
like
everything
mini
fabric
does,
okay,
you
almost
don't
have
to
do
with
your
demo
files
or
or
very
complex.
C
C
C
Okay,
now
I'm
in
so
I
have
absolutely
nothing
right,
because
this
is
just
set
it
up
right.
So
what
do
I
do?
Next?
As
rada
has
showed
you
earlier,
you
can
import
the
asset.
The
good
news
is
that
when
you
run
this
minifab
console
up,
the
asset
file
has
been
created
for
you,
so
the
file
actually
will
be
in
this
directory.
C
C
C
C
Now
you
can
see
that
I
have
wallets
from
different
from
different
organizations
right.
I
remember
talking
about
when
I
set
up
fabric
network,
I
use
the
default
spec
file,
which
contains
basically
org
zero
or
one
two
different
organizations,
and
always
the
example.
That's
for
the
older
org
right
now
I
import
the
asset
I'll
see
this
node
happily
show
the
green.
That
actually
means
the
console
is
working
with
the
node.
Otherwise
this
will
be
white,
okay,
so
channel,
because
I
have
not
associate
my
wallets
with
those
notes.
C
C
C
Okay,
so
actually
I
I
just
want
to
show
you
how
easy
to
start
up,
console
and
pick
up
the
asset
which
generated
by
the
command
then
import.
The
console
from
this
point
on
you
can
follow
what
rod
have
showed
you
associate
those
wallets
to
different
nodes,
or
you
know,
deal
with
the
this
certificate
say
a
note
like
here
right,
you
can
associate.
The
identity
which
you
know
should
be
by
default,
is
admin
at
the
mean
pw
right.
C
A
A
A
So
tom,
to
clarify,
I
think,
faisal's
question
is
like,
at
least
in
the
ibm
bs
code
app.
You
have
the
option
to
export
the
connection
profile
so
that,
if
you're
writing
an
app
through
the
sdk,
you
can
utilize
that-
and
I
think,
oh
question,
because
I
had
the
same
one
right:
how
do
you?
How
do
you
access
the
connection.json
or,
if
it's
in
yaml
and
then
the
crypto
material,
for
the
wallet,
if
you're,
writing
an
app
on
top
of
that
faisal?
I
hope
I
captured
what
you're
getting
at.
C
C
A
A
B
C
All
right,
so
so
so
the
connection
profile,
actually
the
connection
profile
will
be
created
when
you
actually
set
up
the
you
set
up
fabric
network.
So
here
I
just
want
to
show
this.
So
in
this
vert
first
directory
there
is
directory
subject
called
the
profile
called
profiles
in
this
profile
directory.
You
will
see
cost
of
json
and
yaml
files
for
different
sdks
and
many
fabrics
really
really.
You
know
tried
very
hard
to
support
developers,
regardless
of
using
go,
sdk
or
or
java
or
node,
and
they
create
those
connection
files
for
you.