►
From YouTube: Hyperledger In-depth: An hour with KrypC: Best practices for upgrading to Hyperledger Fabric 2.2
Description
The first Hyperledger Fabric major release since v1.0, Fabric v2.0 delivers important new features and changes for users and operators alike, including support for new application and privacy patterns, enhanced governance around smart contracts, and new options for operating nodes.
Hyperledger Fabric v2.0 introduces decentralized governance for smart contracts, with a new process for installing a chaincode on your peers and starting it on a channel. The new Fabric chaincode lifecycle allows multiple organizations to come to agreement on the parameters of a chaincode, such as the chaincode endorsement policy, before it can be used to interact with the ledger.
In this webinar, Hyperledger Member KrypC will discuss their experience updating their customer’s Hyperledger Fabric infrastructure to version 2.2, share some of the obstacles their customers faced, and how KrypC navigated these obstacles to ensure a successful update.
In the “Hyperledger In-depth: An hour with… .” series, Hyperledger members share learnings from their projects and try to answer all the hard questions about the pains of working with DLTs. It is not yet another webinar: participants will be encouraged to take part, come with prepared questions and voice opinions. Expect live demos and tutorials, stories from the battle field and hopefully some heated discussions. Let’s get out of the zoom fatigue and engage to share experiences and build a stronger community.
----
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 #HyperledgerMemberWebinars #Blockchain
B
A
A
A
A
A
All
right
so
welcome
everyone
to
this
week's
hyperledger
in
depth,
an
hour
with
cripsy
best
practices
and
major
obstacles
for
upgrading
to
hyperledger
fabric
2.2.
My
name
is
karen
o'tone
and
I'm
the
director
of
ecosystem,
hyperledger
and
I'll
be
facilitating
our
session.
Today
we
have
chris
smith
joining
us,
mohit,
sathi
and
kartik
nair,
but
before
that
I'll
get
into
a
little
housekeeping
before
we
get
started
as
with
all
sessions
and
meetings
here
at
hyperledger,
we
follow
an
anti-trust
policy
that
you
can
find
on
our
website
and
our
wiki
page.
A
This
is
being
recorded.
So
don't
worry,
it
will
be
available
both
on
our
youtube
page.
We
are
currently
live
on
youtube
and
also
on
the
same
events
page
that
you
registered
for
this
session.
Slides
will
be
available
on
the
event
page
on
our
website
as
well,
where
you
registered.
So
don't
worry
about
that.
You'll
get
all
the
information
you
need.
A
We
like
to
make
these
webinars
a
little
bit
more
interactive
than
your
typical
webinar,
so
we
encourage
you
to
ask
questions
to
get
involved,
raise
your
hand
early
and
often
I
will
be
monitoring
the
chat,
the
q,
a
box
and
the
hand
raising
so
anytime.
You
want
to
jump
in.
Please
feel
free
to
do
so,
and
our
speakers
will
also
be
inviting
you
to
speak
at
certain
points
as
well.
A
C
C
My
name
is
christopher
smith
and
I
am
the
vice
president
of
sales
for
cripsy
technologies,
also
presenting
today
our
our
vp
of
technology,
mohit
sethi
and
our
research
engineer,
karthik
nyer.
To
start
out.
I
just
want
to
oops.
I
should
have
showed
you
that
there,
so
these
are
the
wonderful
faces.
So
to
start
out,
I
just
want
to
tell
you
a
little
bit
about
cripsy.
C
C
C
These
recommendations
are
based
on
our
experience,
upgrading
our
systems
and
upgrading
the
system
so
settle
over
several
of
our
clients,
all
right.
So
the
question
is
you
know
what
is
the
need
for
all
this?
So
so,
why
are
we
talking
about
this
today?
So
there
have
been
two
major
announcements
in
the
last
few
months
that
are
relevant
to
this
topic.
First
hyperledger
fabric
announced
the
end
of
support
for
version
1.4
as
of
april
2021,
and
then
second
microsoft
announced
that
they
were
deprecating
their
azure
blockchain
services
as
of
september
2021..
C
So
so,
if
you
want
to
take
advantage
of
the
additional
features
of
hyperledger,
2.2
you'll
need
to
go
through
the
upgrade
process,
and
if
you
are
using
abs,
you
may
need
a
new
technology
partner
to
guide
you
through
the
process.
So,
given
the
maturity
curve
of
blockchain,
most
of
the
programs
in
the
past
were
not
in
production,
so
the
upgrades
were
offline
and
it
was
not
a
business
critical
issue.
C
So,
in
this
session,
my
colleagues
will
share
their
real
life,
upgrade
experiences
and
we're
not
going
to
reference
any
client
names
just
to
respect
confidentiality,
and
I
will
also
tell
you
about
our
upgrade
arm
template
that
is
available
at
no
cost
on
the
microsoft
marketplace.
It's
a
great
resource
for
getting
started
in
the
process
and,
of
course,
if
you
have
any
questions
about
how
to
use
it
or
if
you
need
extra
help,
we
are
available
to
help
so
I'll
turn
it
over
to
mohit
now
to
discuss
the
best
practices
for
getting
started.
D
Yeah
thanks
chris,
am
I
audible?
Yes,
I
can
hear
you
yeah.
Thank
you,
everyone,
so,
as
chris
mentioned
so
before
I
get
into
some
of
the
details
and
experience
which
we
have
gone
through
at
krc
handling,
multiple
upgrades
just
to
touch
on
like
what's
currently
happening,
so
that
there
are
a
lot
of
projects
which
are
on
production
on
hyperledger
fabric
iet
and
implementation
teams
are
busy
with
new
projects
on
fabric
hyperledger
fabric.
D
Now
why
it
is
why
upgrade
have
become
so
important
in
the
hyperledger
fabric
journey
is
because
most
of
the
production
projects
were
on
basically
hyper
ledger
fabric
1.4,
lts
version,
which
was
a
very
long
supported
and
very
stable
version,
and
it
was
like
widely
adopted
now.
When
we
talk
about
upgrades
in
a
normal
ecosystem,
it
is
basically
how
do
we
write
scripts
and
how
do
we
do?
Database
upgrades
application
upgrades,
but
when
it
comes
to
blockchain
and
specifically
hyperledger
fabric,
there
are
multiple
members
and
we
would
have
projects
might
have
multiple
channels
multiple
chain
code.
D
So
basically
I
would
be
sharing
the
experience
which
we
have
gone
through
and
what
we
should
be
following
and
what
we
should
be
avoiding
and
definitely
during
the
the
presentation
the
webinar
like
we
would
like
to
make
it
more
interactive.
If
you
have
anything,
you
can
send
a
message
for
a
particular
point.
So
let
me
start.
D
So
the
first
thing
is
basically:
we
have
to
create
a
plan
and
create
simulated
instances.
For
example,
if
our
application
is
running
on
a
cluster
or
a
virtual
machine
model,
and
if
there
are,
let's
say
three
members,
three
pr
organization,
one
order
organization,
you
should
basically
be
doing
the
same
thing
in
our
test
instances
and
run
the
upgrades.
D
D
Once
we
basically
have
done
the
test
on
various
instances
by
repeating
the
let's
say,
taking
the
backup
of
the
data
recreating
the
instances
we
could
perform
certain,
let's
say
a
better
plan.
So
in
what
sequence
of
operation
we
should
be
performing
the
upgrades,
shall
we
upgrade
the
pr
first?
Shall
we
upgrade
the
order
first
or
among
a
large
consortium
who
should
be
doing
this
first,
so
this
practice
would
basically
remove
any
challenges
which
you
get
into
the
maybe
let's
say
the
uat
systems
or
the
production
systems.
D
C
D
Okay,
yeah,
maybe
you
have
to
go
into
yeah
now,
when
we,
when
we
say
testing
creating
an
instance,
it
is
also
equally
important
that
we
are
testing
end-to-end
functionality,
for
example,
in
your
current
application.
The
channel
chain
for
endorsement
policy
is
something
so
we
should
also
test
whether
such
endorsement
policies
are
working.
For
example,
we
have
two
out
of
five.
D
D
D
This
is
a
significant
upgrade
in
the
way
chain.
Code
management
was
managed,
so
it
would
help
people
to
basically
plan
that
are
all
of
the
members.
Their
id
teams,
their
software,
their
life
cycle
flow
are
have
adapted
basically
to
this
no
new
flow,
and
that,
if
you
are
upgrading
from
1.4
to
2.2,
then
there
would
be
some
channel
policies
which
are
also
needed
to
be
maybe
validated
upgraded.
A
D
Primarily,
is
I
I
want
to
know
like
how
do
you
add
an
order
which
does
not
have
the
certificates
like
the
crypto
material?
So
let's
say
I'm
having
an
order
of
a
specific
organization
and
I
want
to
add
another
order
from
a
different
organization
not
having
the
same
crypto
material
to
the
application
channel.
Not
the
system
channel
in
hyperlink
fabric
2.2.
D
Yeah,
that's
a
good
question.
However.
Basically
I
would
like
to
focus
on
the
upgrade,
so
I
will
give
you
a
brief
and
maybe
separately
we
can
have
a
discussion
so
hyperledger
fabric
2.4,
which
is
expected
to
come
that
reduces
the
dependency
of
the
tie
up
between
the
system
channel
and
the
application
channel
which
exists
today
right
so
till
hyperledger
fabric
2.0,
it's
it
makes
it
makes
it
compulsory.
Basically,
first
you
have
to
add
the
order
into
the
system
channel
right
then
only
you
can
make
it
to
the
like
application
channel.
B
D
What
is
happening
today
is,
if
you,
even
if
you
design
multiple
orders
for
different
channels
right
within
the
organization,
each
order
would
be
aware
of
all
the
channels
which
are
available
across
any
of
the
members.
So,
but
going
with
this
new
logic,
which
is
supposed
to
come
in
2.4,
that
privacy
would
be
enhanced,
plus
it
would
make
order
management
much
simpler.
D
Yeah,
so
one
more
thing
important
is
basically
taking
the
backup
and
creating
the
rollback
procedures.
Now
why
this
is
important
is,
and
your
existing
channel
could
comprise,
of
multiple
members
and
different
member
would
be
running,
are
managed
by
different
id
teams.
They
might
be
running
on
different
platforms.
For
example,
a
few
of
the
members
could
be
running
in,
let's
say
the
gripsy
provided
platform.
Some
could
be
running
in
their
own
and
similarly
azure,
aws
or
like
there
are
multiples
right
due
to
various
ways
in
which
the
platforms
are
basically
designed.
D
D
So
it's
important
to
factor
that
everyone,
not
only
one.
Let's
say
if
you
have
five
member
organization
and
if
you
are
doing
an
upgrade,
everyone
should
basically
create
a
plan
in
case
of
a
failure.
How
do
we
go
back
to
our
previous
version
and
if
we
don't
do
so,
we
can
get
into
a
situation
where
the
network
is
partially
upgraded
partially
not
and
we
might
not
be
able
to
do
any
transactions.
D
D
So,
for
example,
in
a
simple
docker
docker
compose
model,
you
just
need
to
ensure
that
the
volumes
which
are
basically
tied
to
your
the
docker
instances
for
the
pr
and
the
order.
So
we
should
basically
stop
the
processes,
take
their
backup
and
and
then
do
the
upgrade
process.
So
in
case
of
any
issues,
then
we
figure
out
that
okay,
this
is
not
going
to
work.
We
have
to
try
it
again,
but
let's
bring
the
network
back
again.
D
That's
how
it
was
so
it
would
be
easy
if
we
can
bring
back
that
folder
use
that
same
config
file
and
bring
the
network
back.
So
this
was
a
simple
example.
However,
if
if
we
have
a
custom
deployment
model,
your
own
kubernetes
model,
where
you
are
having
disk
mounted,
so
we
should
be
knowing
how
the
data
have
to
be
backed
up
and
basically
how
the
how
to
use
the
backup
data
again.
D
It
would
definitely
take
time.
So
how
does
the
business
take
this?
Certain
applications
could
be
critical
that
the
reports
or
the
chain
code
queries
should
be
made
available
to
them
at
any
point
of
time.
So
do
we
handle
it
in
such
a
way
that
not
all
the
peers,
for
example
in
my
organization,
I
have
three
peers
or
lesser
four
peers,
so
I
will
have
I'll
upgrade
the
three
pairs
bring
the
network
upgrade
the
network,
but
one
of
my
peer
would
still
remain
in
1.4.
D
So
this
is
how
we
could
handle,
let's
say
an
example
of
handling
the
queries
and
the
downtime.
But
this
is
also
an
important
aspect
that
when
we
are
upgrading,
we
should
consider
what's
the
impact
of
the
downtime
on
the
application
which
relies
on
the
blockchain
network.
And
do
we
need
to
provide
query
or
not.
D
Yes,
I
think
we
can
go
into
the
next
one,
so
I
have
actually
covered
it
previously.
So,
as
I
said,
a
hyperledger
fabric
network,
let's
say
five
member
organizations
could
be
sparing
across
a
different
geographies.
People
would
be
in
different
time
zones,
so
coordination
and
the
plan,
which
also
included
the
rollback
and
sorry
backup
and
recovery
plan.
D
Yeah,
please
go
ahead.
We
we
are
doing
architecture
for
entirely
different
projects
for
that
coronavirus,
control,
program,
okay,
that
is
upgradeable
for
the
regular
real-time
healthcare
application.
So
the
thing
is
yeah
here
there
will
be
lot
of
interoperability
when
the
blockchain
in
this
project
is
there,
so
in
that
we
plan
to
use
that
the
hyperledger
framework
as
that
base
for
the
the
total
security
of
this
data
security.
D
So
what
is
your
recommendation
when
we
upgrade
from
one
version
to
another
version?
Any
any
thing
you
you
advise
for
that
the
structural
designing,
let's
see
what
what
have
to
be?
Yes?
Yes,
yes,
so
we
have
a
similar
experience,
not
exactly
critical
on
the
same
aspect,
but
it
was
critical
from
the
business
requirement.
D
D
And
similarly,
what
happens
is
if
you,
if
you
have
multiple
team
members
for
the
same
cluster,
and
if
you
are
going
with
the
sequence,
so
we
ended
up
basically
creating
scripts,
so
that
reduced
a
lot
of
manual
intervention.
Obviously
everything
cannot
be
automated,
but
we
basically
created
scripts
to
the
extent
that,
let's
say
the
pr
upgrade
process
and
whatever
could
could
have
been
done.
D
They
got
executed
in
a
script
flow
and
all
the
validations
were
done,
whether
each
and
every
process
of
happened,
and
then
it
went.
So
I
would
say
that
we
have
to
do
an
automation
to
the
extent
possible,
reduce
the
manual
error,
the
scope
of
manual
errors
that
could
happen,
practice
it
and
then
execute
it
on
the
production,
and
I
think
specifically
in
the
case
which
you
are
referring.
D
D
Registry
that
also
in
a
blockchain
whether
it
will
be
helpful
application
registry-
yes,
because
that
when
we
work
out
for
the
same
interoperability,
that
is
the
different
project
developers,
maybe
from
the
future
also
they
will
learn,
they
can
access
their
blockchain
data.
That
is
that
way
that
I
think
that
that
registry,
that
app
registry,
that
also
in
a
blockchain,
I
think
it
will
work
out
that
I
think
so.
D
A
D
D
Yeah,
so
this
is
one
of
a
very
important
point,
sometimes
as
part
of
a
downtime
strategy.
We
tend
to
do
multiple
things,
because
the
iit
team
and
the
business
think
that
we
are
getting
into
an
upgrade.
So
let's
do
multiple
tasks
at
the
same
time,
so
that
on
a
single
downtime,
we
could
complete
the
pendant
task.
One
of
those
could
be
upgrading,
I
won't
say,
upgrading
the
consensus,
changing
the
consensus
or
migrating
the
consensus,
for
example,
kafka
to
wrap.
D
D
Yeah,
so
it's
common
that
when
we
have
basically
set
up
the
idea
systems,
for
example,
in
a
dockerized
environment,
we
could
have
scheduled
backups
of
the
virtual
machines
or
the
docker
data,
or
in
kubernetes
managed
kubernetes
services.
We
could
have.
I
use
certain
tools,
basically
to
take
the
backup
of
all
the
containers.
D
However,
before
going
for
an
upgrade,
it's
very
important
that
don't
rely
that
we
have
the
backups
already
taken
as
a
good
good
starting
point.
It's
always
good
to
either
use
this
backup
to
create
your
test
system,
where
you
want
to
first
validate
the
upgrade
process
or
basically
validate
them,
that
the
network
is
coming
up
and
all
your
application
functionality
is
working
with
the
with
the
existing
network,
which
is
basically
created
using
by
restoring
this
spec.
D
How
do
we
handle
that?
They
don't
interfere
with
the
live
system
is
another
challenge,
but
it's
important
that
we
validate
this
data
by
restoring
them
and
also
performing
certain
transactions
on
it.
So
we
are
very
sure
that
the
backups
are
going
to
work
in
case
of
any
failures
in
our
upgrade
process.
D
An
upgrade
failure,
but
this
happens
when
part
of
your
network,
for
example,
out
of
six
members,
four
of
the
members
have
successfully
upgraded,
whereas
two
of
them
have
got
certain
issues
and
the
policies
for
your
channel
and
the
chain
code
were
such
that
four
members
could
basically
endorse
a
transaction
or
the
endorsement
policy
allowed
them
now.
In
such
case,
what
could
happen
is
you
would
have
gone
ahead
with
your
blockchain?
New
blocks
have
got
added,
and
two
of
the
members
have
basically
not
upgraded.
D
Now
we
have
no
choice
right.
We
have
to
just
figure
out
how
to
upgrade
the
two
organizations
which
fail
to
upgrade.
We
will
not
be
able
to
basically
roll
back
this,
for
because
you
would
have
done
some
real
logical
transactions
and
it
would
not
be
possible
to
in
general.
We
cannot
delete
it.
We
should
not
be
deleting
any
blocks,
because
there
are
live
transactions.
D
It
could
be
connected
with
your
live
systems,
so
once
the
upgrade
have
happened.
Ideally
we
should
be
validating
transactions
from
all
the
members
that
all
of
the
members
are
able
to
perform
transactions
so
best
way
is
to
basically
ensure
that
all
of
them
approve
a
new
chain
code.
So
you
will
know
that
the
life
cycle,
the
new
life
cycle,
is
basically
working
and
each
member
have
got
adapted
to
the
new
life
cycle
flow
and
after
that
you
could
perform
transactions
perform
some
transactions
in
such
a
way
that
all
the
party
perform
certain
transactions.
D
Yeah,
so
this
is,
this
issue
is
very
specific
to
deployments
which
are
executed
on
managed
kubernetes
service
for
non-managed
kubernetes
service,
as
well.
So
from
I,
if
I
remember
from
1.20
kubernetes
is
basically
not
going
to
support
the
docker
in
docker
support
where
docker
is
able
to
create
new
docker
images,
and
this
have
a.
D
References,
we
are
executing
chain
code
by
themselves.
They
are
when
we
deploy
a
chain
code.
Peer
is
able
to
create
a
new
docker
image
and
start
the
it's
not
going
to
once.
We
move
to
this
kubernetes
version,
so
the
only
way
is
to
basically
create
external
chain
support
and
we
need
to
test
them
as
well,
and
once
we
get
into.
D
D
D
D
And
maybe
one
more
point
I
would
like
to
highlight
here:
the
upgrade
of
hyperledger
fabric.
2.2
is
not
just
on
the
the
binaries
it
now.
We
also
have
needs
to
upgrade
the
channel.
So
there
is
something
called
the
channel
capability
which
needs
to
be
upgraded
from
1.42.2,
and
the
the
important
thing
to
consider
is
if
we
have
multiple
channels,
this
have
to
be
done
multiple
times.
So,
if
you
have,
let's
say
four
channels,
this
upgrade
of
the
channel
capability
have
to
be
done
four
times.
D
If
we
have,
let's
say
n
number
of
chain
codes
in
n
number
of
channels,
then
the
life
cycle
of
each
chain
code
have
to
be
planned.
All
of
them
have
to
be
deployed
and
confirmed
using
the
new
life
cycle.
So
that's
also
an
important,
so
it
might
be
relevant
for
projects
which
have
a
lot
of
chain
codes
lot
of
channel,
and
it
would
be
good
if
we
basically
define
a
strategy,
certain
automation,
so
that
those
things
are
minimized.
C
B
B
So
what
we
have
identified
is
there
is
a
inflection
point.
At
this
point
time
I
mean
the
on
on
one
side:
the
orchestration
technology
and
the
containerization
technology
is
improving,
rapidly
you're
having
kubernetes
evolution
happening
and
you're.
Getting
new
new
releases
coming
in
with
extra
powerful
features.
Similarly,
you're
getting
hyperledger
features
which
are
getting
improved
day
by
day,
so
for
us
developers
who
started
working
on
hyperledger,
either
0.4.6
or
maybe
1.4.
B
We
have
seen
a
lot
of
features
and
we
have
worked
with
them,
but
at
this
point
of
time,
what
has
happened
when
it
switched
off
to
2.0
and
then
2.2
to
0.4
is
that
the
life
cycle
of
the
entire
process
has
been
improved.
It
has
been
democratized
further,
so
anytime,
you
make
a
change
to
something
everybody.
Who's
participating
in
the
network
should
come
into
consensus.
B
So
the
existing
production
systems,
which
are
relying
on
the
docker
runtime
and
the
production
systems
which
are
running,
are
running
on
1.4,
based
on
mammoth
task
of
upgrading
the
cluster
infrastructure,
as
well
as
the
hyperledger
fabric
protocol,
due
to
their
up
closing
dates.
So,
since
the
new
release
dates
are
been
announced
for
newer
versions,
we
had
to
find
a
way
where
we
can
accomplish
both
the
tasks.
So
that
was
the
whole
agenda
behind
the
presentation,
so
we
identified
few
problems.
B
We
identified
the
consequences
we
have
just
given
you
a
few
steps
to
think
to
remember
that
you
should
be
addressing
these,
for
example,
the
five
things
to
remember
when
you're
trying
to
upgrade
more
than
explained
all
the
five
points
very
clearly
to
you.
The
main
thing
is
the
data
backup
most
of
the
time
you
may
you
take
the
data
back
up,
but
you
really
never
focus
on
the
channel
capabilities
or
any
other
artifact
related
information.
B
B
So
we
decided
there
are
many
people
who
would
like
to
play
around
with
hyperledger
2.2
before
they
move
on
to
2.2,
because
there
are
consequential
changes
with
the
life
cycle,
maybe
with
the
consensus
mechanism,
maybe
with
the
private
data
collection,
with
many
things
so
to
have
a
test
drive,
be
created
by
infrastructure
as
code
offering
on
azure
marketplace,
with
the
name
cripsy
arm
template
for
azure
or
deployer
of
hyperledger
fabric
version
2.2
and
above
so
you
can
try
this
out
anytime,
you
can
go
into
azure.
You
can
try
the
template,
it's
free.
B
You
can
have
the
template
installed
in
your
tenant
id
in
your
client
and
then
you
can
have
a
test
drive
of
hyperledger.
Try
your
application
out
there.
If
the
application
is
exceeding
all
the
parameters
which
you
have
identified
for
your
application,
then
go
ahead.
Please
upgrade
your
application,
so
the
process
of
upgradation
is
very
well
documented
by
hyperledger
foundation
and
you
can
take
off
your
advices,
which
you
might
have
learned
today
now.
What
is
there
in
the
template?
B
So
I'll
explain
what
you
get
from
the
template,
so
the
concept
or
the
design
behind
the
template
is
to
create
two
separate
clusters
for
the
order
organization
and
the
pr
organization,
so
the
template
by
default.
It
comes
with
a
peer
cluster
of
two
or
two
peers
and
an
order
organization
of
I
think
three
orders
or
five.
It
depends
on
the
the
draft,
the
formula
which
you're
adopting.
B
So
how
do
you
use
the
template?
That's
the
next
question
you
move
on
to
azure
marketplace.
You
select
the
template,
you
click
on,
try
it
now,
then
you
have
to
feed
in
some
information
you
feed
in
information
regarding
your
fabrics
or
the
admin
name,
the
admin
password
you
feed
in
information
regarding
the
cluster,
the
type
of
clusters
which
are
allowed,
or
this
type
of
vms,
which
are
allowed
to
constitute
your
cluster,
is
already
given
in
a
dropdown.
You
can
easily
select
it.
You
can
provide
the
cluster
information.
You
can
draw
the
ci
information.
B
You
can
provide
the
organization
information.
So
in
this
part,
you
have
to
select
if
you
want
to
create
a
peer
or
an
order
organization,
so
you
can
start
with
creating
a
pr
organization.
Then
you
complete
the
cluster
creation,
follow
through
the
process.
Once
a
cluster
is
available
with
peer
running
in
it,
you
can
come
back
to
the
same
offer
again
and
then
create
another
where
our
order
organization
will
be
created
with
the
number
of
orders
which
are
specified
and
the
order
organization
details
which
are
fair
fed
into
the
user
interface.
B
So
at
this
point
of
time
you
are
left
with
two
clusters
which
can
together
constitute
your
original
hyperledger
network.
So
you
have
the
peer.
You
have
the
order,
then,
how
do
you
use
it?
So
we
have
a
data
profile.
We
have
given
step
by
step
guidance
on
how
to
use
a
template,
how
to
use
the
clusters,
how
to
interact
with
them,
how
to
create
a
channel
how
to
join
a
channel.
B
So
there's
much
of
these
many
operations
can
be
done
by
following
the
instructions
which
we
have
provided
on
the
github
page
plus.
There
are
two
major
things
which
are
coming
in
this
arm.
I
mean
the
arm
template,
which
we
have
provided.
First
thing
is
the
peer
image.
The
peer
image
is
coming
customized
to
support
the
external
change
feature.
B
So
in
general,
if
you
are
using
hyperledger
original
for
2.2
images,
you
are
downloading
and
then
you
are
running
it
in
your
docker
container
or
maybe
you're
getting
some
other
way,
you're
getting
it
by
having
charge
you're
installing
it
in
your
cluster.
However,
it
is
it's
coming
in
factory
made
as
in
it
doesn't
support
external
chain
code
as
it
is,
the
peer
binary
has
to
be
rebuilt.
The
pr
binary
has
to
be
reinstalled.
B
The
pa
binary
has
to
be
fed
into
a
net
plugin,
so
this
process
we
have
taken
care
of
for
you.
You
can
just
try
out
the
external
change
code
feature.
Only
few
details
need
to
change.
You
just
have
to
mention
the
connection
profile,
the
metadata
profile
inside
in
your
chain
code,
and
then
you
can
test
your
external
chain
code
out
in
the
network.
B
So
the
second
feature
I
wanted
to
refer
to
is
the
fabric
go
play
image.
So
in
general,
you
use
peer
commands
to
execute
and
then
test
out
your
network.
That's
how
hyperledger
fabric
admin
really
operates.
We
have
created
a
custom
version
of
fabric,
go
clay
which
is
again
provided
by
the
hyperledger
foundation,
thanks
viewers,
so
we
have
used
the
fabric.
Okay,
we
built
an
image.
B
So
this
is
what
we
have
in
stock
in
the
arm
template.
So
anybody
can
try
it
out
if
you
have
an
azure
account
of
course,
so
these
step-by-step
guidance,
like
I've,
explained
it's
available
in
the
github
profile.
If
you
guys
want,
we
will
share
the
link
here
in
the
chat
window,
or
can
somebody
get
them
the
github
link?
B
B
Try
your
application
in
this
see
if
it
is
working,
see
if
you
are
finding
some
struggle
understand
where
all
the
changes
have
to
be
made
in
your
application
in
order
to
support
2.2
version,
then
you
start
planning
your
movement
from
1.4
to
2.2,
so
just
consider
it
as
a
step-by-step
upgradation
plan.
So
you
can
formalize
your
strategy
around
this.
You
can
try
this
out
and
I
think
the
references
are
here
for
the
things
which
I
was
making
a
discussion
on.
So
you
can
find
render
support
for
fabulous
fabric
is
available
here.
B
The
template
link
is
available
here
and
then
yeah.
So
that's
where
you
can
find
the
template,
and
I
think
we
will
give
you
the
github
page
link
too,
because
it
will
help
you
further
your
understanding
of
my
pleasure
fabric,
so
yeah,
that's
where
you
can
start.
If
you
have
any
queries,
any
problems
you
can
reach
out
to
us.
We
are
always
there
technology.
I
think
chris
can't
take
over
now.
C
A
C
B
A
B
So
yeah
we
have
done
few
projects
in
public
sector,
so
we
can
only
relate
to
the
ones
which
we
have
done
here,
so
it
may
not
be
uniform
across
the
globe.
So
first
thing
is
the
timing,
of
course,
so
it
takes
a
very
long
time
for
the
project
to
kick
off,
even
though
it's
not
relevant
to
the
technology
itself,
I
mean
that's
one
big
challenge
which
we
have
to
go
through
all
the
time.
B
Second
thing:
it's
all
about
data
localization
rules
which
are
coming
in
so
anytime.
You
have
to
address
something
like
this.
You
need
to
go
through
a
plethora
of
security
concerns
and
then
the
data
localization
rules
of
which
our
government
or
which
our
country
are
addressing
to
we
had,
I
mean
we
did
manage
to
do
this.
B
I
mean
thanks
to
the
cloud
ecosystem,
which
is
like
working
around
the
clock
to
make
sure
that
you
have
regions
available
wherever
you
can
so
that
has
helped
us
a
lot,
and
there
is
this,
intrinsic
feel
of
blockchain
may
be
providing
a
problem
towards
the
privacy
of
data
that's
coming
in.
So
we
had
to
like
talk
people
into
understanding
how
the
enterprise
and
the
permission
ledgers
work.
B
D
Yes,
so
just
to
add
to
karthik's
thing
what
karthik
said,
the
few
other
challenges
could
be
specifically
related
to
security.
How
is
the
data
secured
and
how
are
basically
the
the
keys
right
when
we
do
a
transaction?
There
are
private
keys
and
certificates
where
they
are
stored,
how
they
are
secured.
D
So
what
happens
if
an
identity
is
revoked?
So
how
do
we
ensure
that
you
are
not
able
to
perform
the
transactions,
so
those
things
have
to
be
well
documented.
Well,
articulated
well
explained,
because
it's
not
just
the
transactions,
because
generally
in
sectors
which
are
not
from
the
above
to
the
the
the
queries
would
be
more
related
to
what
is
the
scalability?
What
is
the
performance
here?
D
Also,
those
things
are
valid,
but
security
is
equal,
equally
important,
not
just
the
data
localization,
which
karthik
means,
and
that
is
obviously
an
important
factor,
but
how
the
transactions
are
secured.
How
do
we
ensure
that
somebody
else
is
not
able
to
do
the
transaction
on
my
behalf
or
if
a
person
leaves
a
company,
he
is
not
able
to
perform
the
transaction.
Can
we
integrate
with,
let's
say,
identity
provider
and
use
a
proxy
id
to
perform
all
the
transactions
right
in
certain
blockchain
applications?
D
It's
hyperledger
fabric
ecosystem
is
definitely
the
most
important
part
of
the
deployment,
but
how
all
the
systems
integrate
with
the
blockchain
network
becomes
much
more
important
in
this
scenarios
and
there
could
be
times
like.
Are
we
using
elective
cup
cryptography,
which
is
the
signature
algorithm?
What
is
the
hashing
algorithm
and
what
are
the
options
we
have?
Such
are
the
challenges
specifically
when
it
is
related
to
defense
as
well.
A
Thank
you
so
much
mohit.
I
will
just
take
the
screen
now
just
to
wrap
it
up.
Thank
you
so
much
chris
kartik
and
mohit
for
a
really
informative
session.
As
I
said,
they're
available
for
any
other
questions
that
you
have
for
them,
you'll
find
the
slides
on
the
page.
For
this
event,
we
do
this
twice
a
month
our
member
webinars,
coming
up.
We
have
pravichi
talking
about
verifiable
credentials
and
oracle
on
august
18th
and
oracle.
A
Talking
about
tokenization
a
hyperledger
fabric
on
september,
8th,
so,
please
be
sure
to
sign
up
for
those.
We
also
have
so
much
more
content.
If
you're
looking
to
learn
more
about
use
cases
or
dive
into
more
technical
sessions,
we
have
a
webinar
page
on
our
website
and
then
also
we
had
our
global
forum
in
june
and
you
can
find
all
the
sessions
from
the
global
forum
on
our
youtube
page
as
well.
There's
a
playlist
there
that
you
can
browse.
A
So
I
encourage
you
to
go
there
and
I
encourage
you
to
get
involved.
We
have
a
number
of
channels
at
hyperledger
we
have
a
number
of
working
groups,
special
interest
groups.
If
you're
looking
to
ask
questions
when
you're
struggling
with
implementation,
I
invite
you
to
go
to
the
chat.hyperledger.org,
where
you
can
jump
right
into
the
open
source
community
of
each
of
our
technologies
and
help
with
getting
some
of
your
questions
answered,
and
we
look
forward
to
seeing
you
here
with
us
next
time.
Thank
you.
So
much
for
joining
us
have
a
great
day.