►
Description
A virtual meetup hosted by Hyperledger Denver on September 1, 2022 featuring Varad Ramamoorthy, one of the Lead Architects for IBM Blockchain Platform (IBP) speaking about the Fabric Operations Console.
Interested in learning how to manage a Fabric network using Channel Participation API? In this session we will discuss and demonstrate how you can use Fabric Operations Console lab to easily move a network that has System Channel to a network with Channel Participation API (without system channel). We will also demonstrate how you can create and update the channel with multiple orderers as consenters and followers.
More about the Fabric Operations Console lab is at:
https://github.com/hyperledger-labs/fabric-operations-console
----
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
Discord: https://discord.gg/rVCn4j7UFd
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 #Blockchain
License
Creative Commons Attribution license (reuse allowed)
A
So
at
this
point,
I'm
going
to
go
turn
it
over
to
varad
and
let
him
go
through
his
presentation.
But
I
do
want
to
let
everyone
know
that
if
you
have
any
questions,
while
we're
moving
through
the
presentation
feel
free
to
post
them
in
the
chat
on
Zoom
here
and
we'll
address
them
and
then
we'll
also
be
posting.
You
know
relevant
links
as
we
move
through
the
presentation,
so
you
can
go
in
and
engage
with
the
community
and
one
thing
that
I
always
like
to
really
promote.
A
Is
you
know
this
is
a
great
way
to
learn
about
projects,
but
we're
always
looking
for
additional
contributors
and
maintainers,
and
if
you're
interested
in
really
contributing
to
you
know,
hyperledger
Fabric
or
the
operations
console,
definitely
feel
free
to
follow
up
and
engage
with
us
and
we'll
be
glad
to
get
you
engaged.
So
at
this
point,
broad
I'm
going
to
turn
it
over
to
you
and
let's
go
through
your
presentation,
perfect.
B
B
B
B
So
the
first
thing
is
again:
what
is
the
channel
participation
API
and
what
is
the
benefit
right?
So
so,
if
you
look
at
the
picture
on
the
left
side
right
with
system
Channel,
this
is
the
Legacy
approach
of
managing
orders.
So
we
had
the
again
fabric
had
the
concept
of
system
channel,
where
it
needed
to
know
all
the
ordering
service.
You
know
organizations
and
nodes
that
are
part
of
the
quote-unquote
soda
cluster
right.
B
B
Say
you
know
I,
you
know
I'm
an
organization
that
just
needs
to
as
one
one
two
and
three.
However,
if
since
say
organization,
five
is
in
the
system
Channel,
if
organization,
five
with
node
five
is
querying
the
system
Channel,
they
know
that
that
is
app.
Channel
One,
you
know
in
the
system
right.
So
that's
one
of
the
you
know
the
gaps
that
fabric
tries
to
address
with
the
with
removing
system
channel.
B
So
on
the
right
you
see
that
without
system
Channel
again
in
this
picture,
that
is
of
course,
no
system
Channel
and
with
the
same
set
of
five
different
nodes
you
in
the
system,
if
I'm
creating
app
Channel
One.
Nobody,
but
the
note
you
know,
organizations
from
nodes.
You
know
one
two
and
three
are
the
only
ones
that
know
about
this
particular
channel
right.
B
B
B
B
B
A
B
B
Just
like
any
other,
like
you
know
peer,
you
create
an
order
with
its
own
identity,
and
then
you
can
join
a
channel
to
that
particular
order
right
so
again
that
simplifies
quite
a
bit
and
then
increased
privacy
I
briefly
touched
on
it
right
so
again,
since
there
is
no
system
Channel,
then
that
is
nobody,
not
everybody
in
the
quote.
Unquote,
Consortium
knows
about
all
the
channels
that
are
being
created
again.
That
is,
you
know.
That's
that's
one
of
the
big
benefits.
B
Scalability
is
the
other
thing
that
you
know
the
fabric
talks
about
right
as
a
benefit
again,
if
you
have
a
lot
of
different
nodes
that
are
in
the
system
Channel,
when
the
orderer
comes
up,
it
needs
to
check
all
the
other
orders
so
that
if
it
sends
you
know
heartbeat
checks,
you
know
that
are
like
going
across
the
board,
like
you
know,
multiple
times,
so
that
kind
of
slows
things
down.
So
you
know
the
the
new
architecture
helps
with
again
scalability
right.
B
So
actually
let
me
quickly
show
the
page
where
fabric
talks
about
the
benefits
so
I
added.
You
know
the
the
link
is
in
the
presentation,
but
but
again
you
know
you
can
see
that
fabric
list
again
knows
system
Channel
and
then
no
Consortium
simplified
creation
process.
Again
you
know
you
can
read
through
more
of
it.
You
know
from
the
fabric
page,
you
know
there
are
some
additional
benefits
that
are
being
described
right.
B
So
again,
let
me
go
back
and
then
there
are
new
apis
right.
So
the
new
you
know
approach
right
to
the
the
channel
participation
API
has
you
know
they
added
new
three
new
apis
right
again,
that
is
one
that
joins
the
channel
to
the
orderer,
and
now
you
can
list
all
the
channels
on
a
particular
order,
and
then
you
can
also
remove
a
channel
from
the
order.
B
So
all
these
apis
use
TLS
certificate
on
the
order
right.
So
again,
you
need
to
remember
that
this
is
slightly.
It
is
different
than
the
general
ordering
service
the
admin
certificates.
These
are
TLS
certificates
that
come
from
the
ca
right,
any
you
know,
tlsr
that
comes
from
the
ca
and
again
just
to
reference
right.
You
know
the
OS
and
admin
apis
are
listed
here
in
the
fabric
page
join
list
and
remove
are
the
three
different
operations
and
what
console
does
this
is
the
main
part
we
want
to
cover
so
fabric.
B
Has
these
features?
This
has
nothing
to
do
with
the
operations
console.
What
operations
console
did
is
to
support
this
architecture
where
there
is
no
system
Channel
and
we
leverage
these
apis,
so
the
voice
and
admin
apis
are
basically
rest
apis
right
that
are
protected
governed
by
again
these
TLS
certificates.
So
we
will
see
how
console
is
able
to
simplify
this
process
without
having
to
build
a
command
line
to
do
these
operations?
How
can
you
do
that
from
the
console?
That's
the
thing
we
are
going
to
see
and
talk
about
any
questions.
A
B
So
that's
a
good
question
right,
so
you
can
go
to
2
4
and
still
continue
to
operate
with
the
system
channel
right.
That's
not
like
a
required
thing
as
part
of
two
four.
So
again
you
know.
If
you
don't
make
any
changes,
everything
will
continue.
You
can
start
2.4
in
the
system
channel
list
mode
that
are
flags
that
you
pass.
You
know
it's
documented
in
you
know
the
in
the
fabric
pages
and
IBM.
B
You
know
has
operators
right
when
you
integrate
Operator
by
the
way,
that's
a
plug
for
future
talk,
so
IBM
also
open
source
operator
right.
That
is
fabric
operator.
If
you
look
up
that
allows
you
to
create
nodes
with
again
2.2
2.4,
it
allows
you
to
migrate
from
2.2
to
2.4
with
the
right
images
right.
It
runs
on
kubernetes,
you
know
and
all
that
right
so
IBM
does
support.
You
know
having
a
flow
where
you
start
with
2.2.
You
have
system
Channel
and.
B
B
Right
I
would
think
so
at
some
point
like
3.0
or
something
I
wouldn't
expect
them
to
drop
support
that
drastically
in
a
DOT
release.
I.
Think
it's
more
like
you
know,
a
big
release
would
drop
support.
I
would
think,
but
there
is
no
plan.
I
don't
think
yet
on.
When
the
system
channel
will
be
dropped.
A
B
A
B
A
B
Zero
things
change
in
the
channel.
They
continue
to
operate
the
same
way.
The
peer
join,
nothing
changed
from
the
peer
join,
so
none
of
that
change,
which
is
great
right.
So
it's
only
the
fact
that
system
Channel
got
removed,
and
now
you
have
to
join
the
channel
to
individual
orders.
The
process
change.
A
B
A
A
good
question,
though
yep
and
the
other
one
I'm
gonna
have
Sunny
come
off
and
ask
his
question,
but
it
looks
like
he's:
got
a
question
about
privacy
so
sending
you
on
just
ask
your
questions.
Well,
yeah!
So
originally
blockchain
was
created
for
for
Prime
no
third-party
entities,
and
and
allegedly
it
was
considered
private,
where
no
one
could
control
it
or
get
into
it.
But
then
now
I'm
hearing
that
that
it's
on
a
public
Ledger
and
now
everybody
could
see
what
you're
doing.
B
B
B
Not
entirely
true
right
because
the
blocks
with
the
new
auto
right
they
go
to
you
know
again,
you
you
distribute
it
to
all
the
peers
that
are
members.
Only
the
people
in
the
channel
that
are
authorized
to
see
are
the
only
ones
that
can
query
the
blocks.
Nobody
else
right:
okay,
okay,
if
you
have
a
channel
and
say
the
channel,
has
three
members
right
in
our
organization,
one
two
and
three
you
define
like
when
you
create
a
channel
you
define
these
are
the
members
of
the
channel,
and
these
are
the
right.
B
They
are
admins
readers,
writers,
you
tell
it
and
only
those
operations
are
allowed
for
members
from
that.
You
know
role
if
you
will
right.
So,
if
you
say,
R1
is
only
a
reader
he's
not
even
allowed
to
write.
If
organization
2
is
using
its
certificates
to
query
the
blocks,
they
can
only
read,
they
can't
do
anything
else
right
and
if
you
don't
have
anything,
nobody
can
query.
A
A
B
A
B
A
B
That
are
consenters
on
the
Channel,
and
now
there
is
a
concept
of
followers
right.
So
within
the
channel
you
tell
it
right
organization,
one
and
two
are
the
admins
of
the
organizations
that
are
contributing
orders
to
this
particular
application
channel
right
one
and
two,
and
as
long
as
I
have
the
certificates
write
certificates.
I
can
use
any
of
my
orderers
to
just
follow.
They
are
not
consenters
right,
they
are
simply
following
meaning
they're
simply
pulling
blocks
replicating,
so
they
are
available.
B
B
Are
consenter
right
away
and
if
it
needs
to
replicate
all
the
blocks,
it
takes
a
large
amount
of
time
during
which
you
know
the
the
there
are
members
that
are
clients
that
keep
trying,
and
you
know
it
can
potentially
fail.
Like
you
know,
this
is
still
coming
up.
They
are
not
part
of
the
center.
What
the
new
approach
does.
Is
you
simply
again
start
as
a
follower?
B
You
simply
say,
like
you
know,
if
you
look
at
the
previous
picture,
like
I
showed
on
the
right
side
ordering
service
one
two
and
three
are
like
10
centers
like
that's.
How
the
application
channel
has
the
definition
and
you
simply
voice
and
underscore
f,
is
joining
the
channel,
but
they
are
not
consent
again.
What
that
does
is
once
the
synchronization
is
complete,
meaning
like
let's
say
you
have
20
million
blocks
or
whatever
right.
You
know
they
they
pulled.
They
are
up
to
date.
Now
you
can
simply
say
hey.
B
This
node
is
now
working
Center.
You
can
simply
add
it
and
it's
like
instantaneous
almost
right,
it's
you
know
they
become
consenters
without
having
to
wait.
You
know,
and
then
clients
are
able
to
like
just
use
them
and
all
that
right.
So
that's
the
benefit
of
having
a
consider.
You
know
and
follower
architecture.
B
You
can
read
a
little
bit
more
on
fabric
itself,
but
from
the
console
perspective
we
do
show
allow
people
to
be
fall,
allow
nodes,
they
should
say
to
be
followers,
and
we
should
we
show
like
which
notes
or
followers
which
are
consenters
from
the
channel
from
the
console
to
make
it
easier
to
manage
it.
That's
basically
the
point
I
want
to
make
for
the
console
side
of
things.
B
So
with
that
said,
let's
go
to
the
demo
so
that
so
I
have
set
up
locally
right.
So
I
just
have
my
local
setup
and
I
imported.
A
bunch
of
notes
from
you
know,
ibp.
So
on
the
IBM
blockchain
platform
I
created
some
notes
and
I
imported
them,
but
you
can
create
them
using
the
open
source
fabric
console
not
console
fabric
operator,
that's
available
like
again,
we
should
have
a
future
session
on
it,
but,
however,
you
create
it.
You
can
simply
import
them
into
the
console
again.
I
have
three
different
Cas.
A
B
B
B
We
will
see
a
migration
scenario
from
you
know
with
the
system
Channel.
How
do
you
go
into?
You
know
two
four
system
without
system
channel
that
covers
migration,
and
then
how
do
you
create
a
channel
with
the
new
approach?
How
do
you
join
remove
and
how
do
you
see
the
consent
or
follower
of?
What's
right?
That's
what
we
will
see
so
again,
I've
imported
two
different
or
created
and
imported
two
different
orders
so
order.
One
in
this
case
you
can
see
is
with
system
Channel
you
can.
B
B
Me
actually
do
this
so
that
way,
you
know
people
don't
get
tripped
up
when
they
set
this
up.
Let
me
remove
that
TLS
search
from
the
wallet
that
way
you
can
see
how
it
looks
like
without
so
I'll
start.
First
right.
So
now,
if
you
go
to
the
nodes
and
then
say
I
go
into
order,
one
you
can
see,
you
cannot
see
this
channel
listed
right
so
meaning
it
does
not
have
the
appropriate
TLS
certificate.
B
A
B
B
So
now
I
have
a
certificate
in
the
wallet
right.
If
you
see
it
order
one
kls
certificate
and
if
I
go
to
the
nodes
and
then
drill
down
into
order
one,
you
can
see
that
it,
it
is
able
to
list
the
system
Channel
or
any
other
channel.
On
that
note
right,
so
the
bottom
section,
the
ordering
admins
and
all
that
those
are
of
course
relevant
only
for.
B
So,
just
you
know,
I'll
add
or
one
just
to
show
everything
continues
to
work
again.
This
goes
back
to
the
question
of
migration,
so
in
this
case,
I
have
a
2
4
system
that
is
operating
with
system
Channel.
You
know,
and
it
has
like
application
channels.
You
know
everything
operates
normally.
The
only
thing
you
see
in
addition
now
is
that
we
are
listing
the
system
Channel
and
any
other
channels.
Using
the
you
know,
the
the
new
API
that
fabric
provides
right.
B
So
what
do
you
do
for
migration
perspective
is
again
two-step
processes.
What
fabric
recommends
so
the
first
step
is
you
need
to
get
the
system
channel
into
maintenance
mode
so
that
accidentally
nobody's
creating
channels
during
this
migration
process?
You
know,
if
you
have
multiple
nodes
within
the
cluster.
You
know
you
don't
want,
like
accidentally,
people
becoming
it's
just
confusion,
so
they
highly
recommend
that
you
flip
the
channel
into
maintenance,
more
system
channel,
so
no
new,
channel
creation
or
or
update,
is
happening
during
the
space.
B
A
B
Maintenance
mode,
you
flip
it
to
this,
and
then
you
see
a
message.
You
know
you
will
not
be
able
to
create
or
manage
new
channels
and
I
say
update
as
simple
as
that
right
so
now
the
channel
is
in
maintenance
mode
right.
So
again,
no
new
channels-
all
you
do
is
just
click
on
this
delete
button,
and
then
you
paste
the
channel
name
for
confirmation
in
this
case
system
channel.
Is
this
particular
one
this
system
chain
ID
and
join
boom?
That's
it
right!
B
A
A
B
Okay,
let
me
see
migration
is
on
this
same
version,
or
the
version
would
also
be
different.
So
so,
if
I'm
understanding
the
question
are
the
nodes
need
to
be
in
the
same
version.
If
you
have
multiple
ordering
nodes,
the
answer
is
as
long
as
it's
a
2.4
system.
It
should
work
the
new
channel
participation
API
can
only
work
in
2.4
system.
So
if
you
have
a
cluster,
you
know,
the
expectation
is
all
of
the
nodes
under
the
cluster
need
to
move
to
2.4.
That's
the
first
requirement.
B
B
Know
like
with
an
ibp
how
you
know
the
options
show
up.
So
this
is
ibp
on
cloud
and
if
I
create
a
new
ordering
service
right,
I
can
create
a
new
one
and
I
get
an
option
to
say:
do
I
want
to
pay
it
with
or
without
system
channel
right.
So
it's
an
option
so
so
again
did
I
answer
the
question.
You
need
to
have
the
same
version
or
a
two
four
and
a
higher
end.
Channel
participation
API
enabled
for
the
migration
to
work,
foreign.
B
And
generally,
the
orderers
are
the
ones
that
need
to
join
and
then
the
peers,
because
basically
you're
saying
hey
order,
you
know
join
these
channels.
I
could
have
like
three
different
notes
or
whatever
you
know,
all
those
three
notes
individually
you're
joining
it
and
then
you're
saying
peer
join
this
as
long
as
that
is
consensus,
the
peer
should
be
able
to
join
and
operate
as
normal,
but
you
need
to.
Let's
say
this
is
the
case.
You
need
to
consider
right.
Let's
say
you
have
three
nodes
in
the
consenter
and
you
are
you
need
to
join.
B
B
Right
so
you
could
have.
Let's
say
you
have
a
single
node
right
orderer,
you
joined
the
peer,
you
know
everything
is
happy
and
now
you
need
to
add
additional
orderers
as
consenters.
Then,
of
course
you
know
you
would
do
it
on
the
order
and
the
beer
would
automatically
know
the
channel
gets
replicated
and
know
the
that
information
sounds
good.
Yeah.
A
B
They
they
were
stored
in
system
Channel.
That's
why
it
was
a
problem
in
terms
of
organizations
within
that
able
to
see
the
changes
coming
in
so
that
configuration
option.
Those
are
like
not
like
you
know,
applicable
anymore,
because
now
you
are
working
with
the
block
that
is
stored
like
in
console
or,
like
you
know,
you
store
it
somewhere
and
then
you
just
you
know
when
you
join
the
order,
you
give
the
order
and
say
join
this
application
Channel.
B
So
you
need
to
have
all
of
one
of
the
notes
up
and
running
to
make
these
changes,
but
you're
not
you're,
changing
the
channel
within
the
scope
of
the
application
Channel
within
the
set
of
order
symptoms
and
that
so
there
is
no
system
channel
in
this
case
right,
so
everything
is
managed
with
it
by
these
orders
that
are
consenters
within
the
channel.
Those
configuration
changes.
A
B
B
A
A
B
You
John,
so
let
me
create
a
new
channel
right
with
the
new
you
know.
So
in
this
case
I
don't
have
any
so,
let's
say
the
channel,
so
I'm
creating
a
new
channel
choose
one
of
the
ordering
services.
This
is
the
one
we
just
removed
the
system
Channel
and
for
reference.
Actually
let
me
do
that
just
to
show
you
the
second
node
I
created
without
so
order.
One
MSP
is
part
of
this
guy
and
then
order
two
MSP.
B
So
again
you
see
a
message
that
this
is
the
order
without
system
Channel,
and
it
tells
me
that
TLS
identity
is
not
found.
I
need
to
create
one,
and
it
also
tells
me
that
you
know
I
need
to
associate
a
regular
admin
identity.
So
let
me
associate
identity.
Just
ordered
MST
now,
I
need
to
go
back
in
the
same
process
holds
true
before
right,
where
I
was
showing
I
need
to
create
a
new
TLS.
B
A
B
And
now,
if
I
go
back,
it
should
show
that
you
know
it's
the
no
channel
of
course.
So
it's
a
brand
new
note.
So
basically
I
have
two
nodes
right:
one
from
each
organization,
two
different
organizations
I'm
going
to
create
a
channel
with
both
of
the
organization
one
and
two
and
then
join
them
so
that
basically
mimics
the
scenario
where
you
have
multiple
organizations.
Each
organization
is
then
trying
to
contribute
different
Auditors
to
the
you
know,
consensus
process
right.
So
if
I
go
to
channels
create
a
new
channel
and.
B
Channel
two
that
I
just
want
to
say
it
started
one
and
first
it's
going
to
say
who's
the
organization
like
just
members
right
or
one
who
are
the
peer
organization.
Members
I'll
just
pick
one.
This
doesn't
matter
for
the
demo,
and
this
is
the
one
of
the
important
screens.
That's
new
screen
that
got
added,
who
are
the
orderer
admins
that
are
on
this
application
channel.
So
the
msps
that
you
choose
are
the
only
ones
that
can
join
the
order.
B
So
in
this
particular
case
you
can
only
join
orders
that
belong
to
Art,
one
MSP
or
R2
MSP
right,
that's
important
right,
because
if
you
have
or
just
or
you
know
just
our
one
MSP,
you
won't
be
able
to
join
because
they
don't
have
the
right
certificate.
So
this
tells
you
who
are
the
organizations
that
are
allowed
to
contribute
orders
and
then
create.
B
So
what
this
did
at
this
point,
nothing
happened
at
the
order
of
level
all
it
did
was
to
create
a
block
with
the
predefined
configuration.
You
said
like
again,
we
we
said
or
go.
You
know,
order
one
and
ordered
to
our
admins
and
org.
One
is
the
member
of
the
channel.
We
did
that
and
at
this
point
the
console
has
a
block
you.
B
You
hit
the
continue
step.
This
is
the
joint
flow
that
automatically
gets
initiated
right.
So
what
the
console
did
at
this
point
is
it
looked
at
who
the
members
are
in
the
block
again
in
this
case
order
one
MSP
in
order
to
Ms
MSP,
and
it
also
looked
at
the
local
config
to
say
hey,
which
of
the
orderers
or
from
those
msps.
So
in
this
particular
case
it
sees
that
one
and
two
like
these
are
the
two
you
know
they
are
already
defined
as
consenters
by
default.
I'll
show
you
the
process
by
default.
B
B
To
show
you
something
interesting
so
now,
if
I
go
into
the
node
and
then
go
down
to
order
one,
you
should
see
that
V
Channel
2
is
the
member.
However,
I
did
not
choose
the
other
node.
You
know
the
node
2
as
a
member.
So
obviously,
at
this
point
I
said
two
membership
and
Center
generally.
You
want
three,
of
course
right
just
for
the
demo,
so
two
are
consenters,
but
only
one
is
joined.
So
at
this
point
the
channel
does
not
have
a
quorum.
B
B
Back
to
the
Channel
with
the
console
block,
so
we
see
that
we
stored
the
Block
in
the
console.
Now
what
I
can
do
is
take
the
block
join
the
second
node
to
the
channel,
which
will
establish
consensus.
This
may
be
a
little
bit
confusing.
Let
me
know
if
it
is
I
can
try
to
explain
it
a
little
bit
more
but
again,
the
general
premises
right,
I
Define,
the
Channel,
with
two
nodes
as
consenters,
and
only
one
I
joined
the
other
one
hasn't
joined,
and
hence
there
is
no
Quorum
and
I.
B
B
If
I
go
back
to
the
nodes
and
then
drill
down
into
the
second
node,
I
should
see
that
you
know
I
joined
and
the
consensus
is
established.
So
I
can
like,
for
example,
if
I
did
this
right
well,
I
can't
join
any
other
nodes.
I
don't
have
one
so
I'll
I'll
show
the
adding
a
follower
part
next
right,
because
that's
another
important
distinction
I
want
people
to
see,
but
any
questions
so
far
in
what
you
guys
have
seen
in
terms
of
joining
ignored.
A
B
So
what
I'm
going
to
do
next
is
right
to
add
a
third
node
right,
I
already
pre-created
one
I'm
just
going
to
import
one
of
the
nodes,
I
already
created,
to
show
the
Apollo
crossing
right
so
I'm
going
to
add
the
third
node,
so
the
third
node
I
created
as
part
of
order,
2
MSP
right
there
you
go
so
the
that's
part
of
the
MSP.
So
if
You
observe.
B
B
And
two
or
the
consent,
you
know
notes
msps
that
can
contribute
majority,
whatever
the
policy,
nothing
change.
These
are,
like
you
know
things
we
used
to
have.
This
is
the
screen?
That's
interesting
right.
So
by
default,
it's
going
to
include
all
of
the
nodes
that
belong
to
those
two
order:
organizations
in
the
channel
so
right
now,
I
added
a
third
one.
B
B
I
can
say,
like
you
know,
through
these
two
guys
or
whatever
I
want
so
point
being
if
I
flipped
it
to
include
all
nodes.
It'll
include
all
the
nodes
at
that
point
in
time
that
are
in
the
console
that
belong
to
those
two
organizations
into
the
consenter
set,
and
you
have
an
option
to
flip
it
and
choose
the
specific
notes
that
you
want
to
choose
so
going
back
to
the
original
thing
right.
B
A
B
B
So
next
and
then
I
say
choose
the
order
three.
So
if
you
know
this
right,
we
did
not
get
the
consensus
error
this
time,
because
there
are
two
nodes
in
the
consentors
and
both
are
like
you
know
in
the
channel,
and
you
see
that
that
is
a
star
with
follower
right.
So
this
basically
says
I
have
two
notes.
You
know
this
goes
back
to
the
picture.
I
was
showing
in
this
screen
where
I
have
two
nodes
as
in
centers,
and
one
is
the
follower
right.
If
you
go
back,
not
this
guy
join.
A
A
B
B
Seems
to
be
some
sort
of
bug,
but
but
again
that
will
become
follower.
The
third
note
would
right
did
I
want.
Oh,
the
last
thing
I
want
to
show
is
that
deleting
the
node
from
the
channel
right?
So
if
I
go
into
the
again
the
details,
I
can
again
add
a
node
or,
like
you
know,
look
at
the
information.
In
this
case
again,
the
consenter
and
I
can
also
hit
the
delete
button
right
I
can
say,
delete
this
channel.
So
what
this
does
is
again.
B
It
only
deletes
the
node
from
the
order
right.
So
this
does
as
a
consenter
or
like
a
follower.
It
simply
deletes
it.
It
does
not
do
anything
with
the
peer
right.
The
peer
Channel
continues
to
remain.
The
fabric
has
I
think
they
already
have
a
feature
where
you
can.
You
know,
remove
a
channel
from
the
peer
console
hasn't
implemented
it
yet.
So
there
is
a
set
of
I.
Think
PRC
alike
commands
right
that
allow
you
to
you
know,
remove
a
channel
peer
Channel
just
to.
B
B
Yeah
enjoying
so
again,
it's
a
CLI,
that's
available
in
the
newer
fabric
that
console
hasn't
implemented
right,
but
it's
a
CLI.
That's
mostly
what
I
wanted
to
tell
more
did
I
miss
anything.
Let
me
just
quickly
check
what
I
wanted
to
show
migration
create,
join,
remove
consent
or
follower.
Taiwan
I
think
there
is
some
sort
of
bug
that
we'll
look
at,
but
any
questions
any
other
questions
we
should
say.
B
B
Approval
required,
like
you
know,
I'm
just
saying:
I
I
have
a
Consortium
of
three
members
and
it's
the
the
distinction
is
the
orderer
admin
is
the
only
one
that
can
join
the
channel
to
that
order.
So
unless
I
have
the
right,
credential
random
person
cannot
join
my
order.
You
know
my
Channel
interview
right,
so
there
is
implicit
approval.
I
should
say
that's
involved
here
right.
Let
me
know
if
that's
not.
A
B
In
without
system
Channel,
how
you
gotta
categorize,
which
peers
should
be
into
its
org,
and
how
do
you
know
which
peer
from
our
confirmed
consensus,
so
the
process
of
the
peer
and
Order
organization
did
not
change
right
with
the
new
thing.
So
when
you
created
a
channel
when
we
created
a
channel
right,
we
basically
said
right.
Let
me
go
back
to
the
channel
creation,
so
when
we
create
a
new
channel,
it's
still.
Let
me
just
type
something
we
still
have
the
same
like
organization
list.
B
B
B
B
B
Let
me
see
so
this
particular
one
the
fabric.
You
know
that
you
know
documentation,
doesn't
quite
talk
about
the
all
the
benefits
of
the
consent
or
follower
business.
But
if
it's
a
follower,
you
know
it's,
it's
quicker
to
join.
You
know,
so
this
the
particular
benefit
is
again
right.
Once
you
synced
up,
then
the
node
is
in
the
release
date.
You
know
you
can
simply
join.
B
However,
if
you
started
with
the
consenter,
then
joined,
then
during
the
time
it's
trying
to
catch
up
all
the
blocks,
that
node
is
unavailable
for
anything
right.
You
know
it's.
It's
still
thinking
of
blocks,
it's
not
able
to
consent,
so
I
think
that's
benefit
like
you
know
again.
If
you
synced
up
and
then
become
a
concentrate,
it's
a
quick
join
process
and
it's
right
away
available
for,
like
you
know,
consensus,
hopefully
that
helped.
A
B
So
just
wanted
to
give
you
this
plug.
So
there
is
fabric
operator,
it's
fairly
quick
to
set
up
and
get
it
running
and
what
the
operator
gives
you
is
it
also
kind
of
bundles.
If
you
go
to
the
console,
there
is
a
step
to
include
the
console
and
you
can
do
sample
Network
right
and
that
sample
network
will
have
2.4,
so
I
think
you
can
play
without
system
Channel
and
all
that
right.
It's
a
fairly
quick
and
easy
way
to
get
the
entire
ecosystem
lifecycle
working
right.
B
B
So
again,
I
think
we
need
to
have
a
session
for
the
operator
and
how
to
use
it
set
up,
but
should
be
fairly
straightforward
to
do
it.
You
know
they
also
support
kind,
find
it
as
an
option
right.
You
know,
you
know
kubernetes,
you
know
cluster
as
an
option.
So
this
is
what
I
use
for
development
locally
I
don't
rely
on
much
outside,
but
that
should
help.
B
A
B
B
That's
a
good
question.
Yes,
let
me
know
so
in
this
particular
screen
when
you're
creating
a
channel
you
are
telling,
which
are
the
organizations
that
are
able
to
contribute
notes
and
again,
if
you,
in
the
scenario
you're
describing
right,
there
are
three
organizations
to
begin
with
and
two
wants
to
join.
Then
you
need
to
make
a
channel
update
right
to
add
those
two
new
organizations
into
the
order
organization
and
the
way
this
approval
works
is
right.
B
There
is
another
policy
console
for,
like
you
know,
Simplicity,
if
you're
creating
from
the
fabric
operator,
the
policy
is
one
organization
need
to
approve
for
any
new
order
organization
to
join,
which
is
not
like
ideal,
but
that's
a
controllable
policy
where
you
can
say,
majority
need
to
approve,
in
which
case
you
need
to
go
through
the
whole,
like
you
know,
approval
to
add
the
new
guide
but
you're
right
that
the
policy
is
decided
by
you
know
again.
That
is
the
policy
for
you
decipher
the
block.
B
A
B
So
again,
there
are
two
different
things:
I
want
to
make
sure
people
got
it
right.
One
is
the
channel
member
policy
right
who
are
the
members
and
how
does
the
you
know,
peers
join
and,
like
you
know,
work
with
it?
That's
one
and
the
second
one
is
the
order
specific
list
right.
You
know,
organizations
that
are
part
of
the
you
know
to
do
any
modifications
to
the
order
level.
A
B
So
that's
not
something
you
can
do
at
the
moment
from
the
console
again
we
set
the
default
to
like
whatever,
like
single
node
single
order
need
to
approve,
but
if
you
need
to
extend
it
to
other
cases,
console
does
not
support
it.
Yet,
but
yes,
it
would
require
doing
the
whole
like
a
dance
right.
You
know,
download
ad,
you
know
get
fruit
above
get
it
sign,
get
it
you
know
submitted.
Yes,.
B
B
A
A
A
And
I
think
you
know
we're
at
the
top
of
the
hour
ride.
But
let's
just
tackle
one
more
question
and
then
we'll
call
it
good
for
today
and
I
agree
with
you.
I
would
like
to
have
a
follow-on
presentation
by
you,
because
I
think
that
there's
a
lot
to
cover
here
and
let's
just
get
on
email
and
cover
that.
B
So
as
long
as
you
can
run
kubernetes,
you
can
run
it
anywhere.
Basically,
that's
the
general
answer
right.
So
you
know
you
can
use
kind
or
kubernetes
the
open
source.
The
operator
that
runs
wherever
kubernetes
distance
and
you
know,
I
mean
I
use
for
my
local
setup,
Rancher
and
kindly
within
it
right
so
I
think
you
should
be
able
to
run
it.
There
is
no
reason
why
it
wouldn't
work,
because
again
it's
all
kubernetes.
A
Okay,
I
think
that
that
covers
everything.
I
really
appreciate
everyone
joining
the
call
today
and
please
feel
free
to
follow
up
with
farad
and
please
feel
free
to
interact
with
the
GitHub
Community
there
as
well,
and
we'll
look
forward
to
the
next
presentation
by
varad
and
I
hope.
Everyone
has
a
wonderful
rest
of
your
day.
All.