►
Description
Using ChainDigit Decentralised Management Console - Tsvetan Georgiev & Baiju Jacob, ChainDigit Inc
Setting up and operating a distributed and decentralised blockchain permissioned networks across different infrastructures is the biggest challenge facing blockchain adoption. ChainDigit decentralised management console simplifies those tasks in an efficient manner and enables them with a few clicks. We emphasise on simplicity, automation and breeze maintenance of complex Hyperledger Fabric networks and bring to the business the benefit of a secure and automated way of building complex consortium networks.
----
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 #Blockchain
A
Each
of
them
may
already
have
contracts
with
their
own
cloud
service
providers.
So
it
is
important
that
we
need
a
tool,
an
automation
layer
which
is
completely
agnostic
of
the
cloud
service
provider
underneath.
So
what
we
are
trying
we
are
demonstrating
today
is
that
tool
which
completely
abstracts
the
CSP
part
of
it
and
where
you
can
bring
up
networks
and
on
and
more
importantly,
it
has
a
decentralized
management
console
which
means
that
each
organisation
will
have
their
own
console.
A
It's
not
the
the
initiating
organisation
which
controls
the
network
and
each
of
them
can
bring
up
their
networks
and
then
join
the
consortium.
That
is
what
CD
pass
is
all
about,
and
why
why
we
are
doing
this.
So
it's
it's
mainly
because
in
the
last
18
months
we
have
been
working
on
multiple
projects
and
every
project
which
we
go
to.
Everyone
has
their
own
preference
for
a
CSP,
and
you
want
to
bring
up
or
bootstrap
the
networks
in
their
CSP
and
when
they
try
to
join
their
partners,
they
have
a
different
CSP.
A
So
this
is
becoming
a
big
operational
overhead
and
what
we
thought
is
that
an
a
simple
automation
tool.
It
is
not
simple,
it's
little
bit
complex,
but
a
automation
tool
would
help,
and
there
is
already
technology
is
existing
in
that
space.
So
that's
that's
what
we
do.
We
focus
only
on
a
hyper
ledger
and
specifically
high
but
larger
fabric.
We
are
one
of
the
training
providers
which
Brian
was
speaking
about
one
of
the
five
training
providers
across
the
globe
for
hybrid
larger
fabric,
so
our
expertise
is
all
about
hybrid
ledger
fabric.
A
So
what
what?
What
we
have
today
is
that
we
have
major
CSPs
providing
templates.
Obviously
some
of
them
are
trying
to
incorporate.
Other
clouds,
like
iBM,
has
an
initiative
to
bring
in
AWS
instances
also
into
their
network,
but
from
that
that
that's
what
the
CSPs
are
doing,
but
obviously
there
is
not
much
of
a
interest
of
bringing
other
CS
fees
because
that's
not
their
business
model
right
say
they
want
to
sell
most
of
their
computing
power
and
there
are
also
Smoot
expanders,
who
have
small
playgrounds,
which
is
which
is
not.
A
B
Bye
Joe
thanks
for
the
introduction,
yeah,
okay,
now
it's
better
so
as
wide.
You
mentioned,
the
basic
things
that
we
actually
faced
during
doing
the
projects
is
that
there
was
a
lot
of
repeat
in
terms
setting
up
fabric
project
project.
So
therefore
we
said
okay,
why?
You
know
repeating
those
steps
again
and
again,
so
let's
do
let's
how
to
make
them
so
essentially
that
also
actually
going
towards
adopting
you
know
in
terms
of
adoption
of
that
technology
in
the
on
the
business
side,
because
most
of
the
companies
they're
not
that
much
techie
right.
B
So
they
don't
know
about
infrastructure.
They
never
heard
about
docker
or
kubernetes,
for
example.
So
it
doesn't.
You
know
the
way
that
is
done
right
now
on
the
fabric
network.
If
you
go
there,
a
lot
of
people
get
confused
what
they're
doing
and
because
that
there
is
a
lot
of
things
they
just
don't
know
so
we're
putting
that
abstraction
layer
there
and,
of
course
we
wanted
to
have
everything
done
in
a
way
that
it
is
not
dependent
on
any
cloud
provider
api's.
B
Okay,
so
of
course
it
is
done
in
a
way
that
it
should
be
simple
enough
from
any
IT
guy
to
deal
with
it.
You
know
just
knowing
about
basic
things,
about
infrastructure
and
and
fabric
so
that
it
actually
leading
to
to
to
something
that
where
we
want
to
get
to
a
point
where
we
are
actually
more
focused
on
about
building
business
logic
and
coding
chain
code
instead
of
dealing
with
infrastructure
and
networking
concerns
and
issues.
B
Okay,
so
I
will
go
to
the
demo
right
away
and
essentially,
what
is
about
well,
I
won't
start
everything
from
scratch.
I
preset
couple
of
things
there,
but
what
I
improvise
in
here
is
that
we
have
two
financial
institutions.
I
named
them
maple
and
actually
funding
that
are
actually
creating
their
own
organizations
and
they
want
to
bring
their
own
peers
on
their
own
infrastructures.
B
Those
in
two
instances
by
the
way
are
actually
working
in
a
cluster
we
didn't
use,
for
that
particular
deploying
on
kubernetes
is
actually
orchestrated
by
docker
swarm.
That
is
actually
the
simplest
things
to
do
so
far.
Kubernetes,
unfortunately,
comes
with
a
bit
of
complexities,
complexity
on
top,
and
that
is
another
deployment
scenario.
B
So
what
I
have
to
do
essentially
is
and
by
the
way,
as
Baiju
said,
that
konso
is
not
meant
to
be
used
as
a
central
console
by
all
organizations.
So
we
are
provisioning
that
every
organization
will
actually
deploy
that
console
on
their
own
infra
or
maybe
somewhat
third-party,
like
our
like
chain.
Digit
will
host
it
for
them
if
they
want
to
don't
want
to
deal
with
that,
so
what
I
can
see
there
I
have
created.
Actually
it
is
the.
B
The
point
is
that
you
can
see
those
Mapple
and
funding
comm
organizations
both
of
them
are
actually
deployed,
but
bootstrapping
a
new
organization
is
actually
as
simple
as
you
capture
the
name.
You
put
you
know
the
MSP
ID
the
domain
name.
You
actually
decide
on
what
network
to
run
have
in
mind.
Those
networks
are
actually
obstructions
that
are
connected
to
the
different
clouds.
B
So,
for
example,
map
o-net
is
actually
connected
to
digital
ocean
and
I
have
two
more,
which
is
fund
net
and
order
net
that
are
connected
to
AWS,
but
you
could
have
as
many
as
you
like.
So
that
means
actually
that
even
you're
a
single
organization,
you
could
run
your
peers
across
clouds.
No
one
is
actually
forcing
you
to
post
all
of
your
peers
on
the
same
cloud
provider.
B
So
once
you
pick
actually,
the
network
I
will
just
add
the
the
the
organization,
and
then
you
can
actually
type
in
what
peers
you
guys
name
them
you,
the
external
endpoint,
so
have
in
mind.
Usually
those
will
be
your
domain
names
that
who
look
like
something
you
know
Walmart
fabric
calm
here,
I'll,
actually,
I
can
use
and
I've
been
using.
The
eyepiece
of
the
machines
on
the
cloud,
for
example,
I,
can
take
that
one
and
you
just
have
to
paste
it
here
and
then
to
decide
on
what
port,
of
course,
the
port.
B
That's
something
you
have
to
know
up
front,
so
it
can
be
shared
with
the
other
organizations,
so
they
can
connect
with
each
other.
And
of
course,
here
we
have
something
that
docker
actually
stuck.
We
are
using
that,
if
you
aware
of
that,
it's
it's
a
stock
file
that
actually
allows
us
to
deploy,
docker
container
or
yeah
run
docker
containers
on
a
cluster
of
machines-
and
here
are
those
labels-
are
actually
allowing
you
to
tell
docker
swarm
where
to
run
them
or
it's
like
load,
balancing
kind
of
a
thing.
B
So
you
can
dedicate
a
bunch
of
your
machines.
Name
them
properly,
and
then
you
can
say:
ok
run
those
peers
on
those
containers
wherever
they
are,
it
doesn't
really
matter
so.
I
want
bootstrap,
because
bootstrapping
alone
takes
around
three
two
to
three
minutes,
so
I'll
be
actually
just
reusing.
The
organizations
that
we
already
have
so,
as
you
see
the
one
that
I
just
created,
is
with
start
of
initial
and
what
I
would
do?
Actually
you
can
actually
as
well,
is
the
ordering
service.
B
B
Plug
and
plug
it's
the
same
thing:
it
might
be
the
projector.
So
if
I
do
docker
service
LS,
so
you
will
see
here
a
bunch
of
entries,
but
those
are
actually
the
Kafka
notes,
the
zookeeper
notes
and
all
of
that.
So
essentially,
as
you
see
here,
you
don't
really
need
to
think
about
all
of
those
CMO
files
that
you
need
to
generate
think
about
the
private
key,
the
PKI
and
all
of
that,
so
it
all
happens
behind
the
scene
and
by
the
way
we
have
different
options
to
deal
with
the
private
keys.
B
B
Right
right,
yeah,
so
there
are
different
options
here
you
can
go
with,
so
our
vision
is
again.
We
don't
want
to
control
or
or
see,
data
that
you
know
that
client
has
it's
the
offering
here
is
more
or
less
you
you
choose
where
you
want
to
host
your
peers
and
you
olden
right.
So
that
is
the
nature
of
block
chains
and
distributions
anyways.
So
if
that
client
and
the
UI
you
are
seeing
here,
it
disappears,
it
does
not
affect
at
all
the
network
itself.
B
Okay,
who
owns
the
machines.
This
is
the
one
who
owns
the
data
and
can
see
it
and
do
whatever
they
like,
but
you're.
Not,
actually
you
can
scrub
that
thing
completely
and
go
on
with
a
regular.
You
know
basis,
h2
and
comment
line,
and
all
of
that
that's
there
is
no
coupling.
There
is
no
nothing
specific
from
fabric
network
perspective
that
we
are
doing.
B
Ok,
so
it's
it's
the
standard
fabric
we
haven't
modified
it
or
something
to
make
it
work,
so
essentially
what
we
are
using
in
the
background.
We
essentially
always
look
at
the
ladies,
and
you
know
greatest
technologies
and
libraries
and
tools
available
out
there.
It
doesn't
make
sense
to
reinvent
the
wheel
right.
So
for
that
purpose
we
are
using
actually
pretty
handy.
It's
ansible
for
those
of
you
who
knows
it.
B
There
is
another
actually
open
source
project,
danceable
tower
which
allows
you
us
to
actually
manage
o
of
those
ANSI
blow
jobs
to
control
the
machines
you
know
of
that.
We
actually
have
also
a
provisioning
capability
that
is
actually
done
through
terraform
yeah
and,
of
course
the
API
is
that
you're,
seeing
here
it's
it's
all
hosted
on
on
a
spring
boot
application.
So
that's
how
we
get
you
know
the
REST
API
exposed.
B
Ok,
so
let's
now
do
the
following:
I
will
just
quickly
show
you
how
I
actually
can
you
can
see
by
the
way
the
channels
here
and
what
I
would
do
LCD
that
channel
actually
is
deployed,
so
what
I
can
do
I
can
go
to
actually
my
organization
I
can
select
one
of
my
peers.
Ok
and
as
you
see
that
peer
is
not
part
of
a
channel
yet
so
joining
a
channel
is
as
simple
as
clicking
on
join
Channel.
B
B
And
actually,
you
can
join
as
as
many
peers
of
your
blockchain
of
your
organization
as
you
want
one
by
one.
Ok.
So
when,
as
you
see
here
now,
my
peer
is
actually
part
for
channel
transfer
and
we
also
list
the
end
points
of
the
channel,
which
is
the
ordering
services
belongs
to
and
I
think
it's
we're
now
over
time.
B
Yeah
right
now,
the
crypto.
We
don't
really
need
to
deal
with
that,
because
those
organization
are
bootstrapped
by
the
same
client,
so
essentially
what
we
need
with
from
the
organizations
that
are
newly
joining
an
existing
consortium,
it's
the
private
certificates
of
their
TOS,
CA
or
or
you
know,
the
root
CA
of
their
organization.
So
this
this
is
a
functionality
that
you
can
actually
as
an
ordering
service.
B
If
you
want
to
include
a
new
organization
into
that
ordering
service
and
then
on
a
particular
channel
of
that
ordering
service,
all
you
have
to
do
is
actually
to
upload
those
certificates
to
the
management
console
where
you
run
the
ordering
service
and
just
update
through
a
configuration
update.
There
were
a
couple
of
steps
that
are
actually
being
performed
behind
the
scene
that
are
quite
different
compared
to
when
you
generate
the
genesis
log
by
the
way
of
of
the
ordering
series
yeah.
B
Yeah
I
will
explain
so
essentially
what
we,
when
you
bootstrap
an
organization.
What
you
you
start
with
is
actually
just
the
modeling
right.
So
at
that
point
of
time
you
just
have
the
model
set
up,
but
you
don't
have
the
organization
up
and
running
when
you
decide
where
you
wanna
run
it
you
hit
that
the
bootstrap
button
right
and
out
of
that
model,
then
the
Rio
peers
are
going
up
in
the
background.
So
what
happens?
B
Actually,
if
appear,
you
know
when
you
are
adding
a
new
organization,
and
all
of
that
there
is
this
service
discovery
functionality
that
we
are
using
actually
to
dynamically
show.
What
is
the
current
network,
because
a
peer
could
be
up
or
down
right
and
other
organizations
may
be
joining,
and
you
don't
know
upfront
what
their
peers
are,
because
you
have
no
control
over
them.
B
That
is
the
basic
idea
behind,
but
as
soon
as
actually
by
the
way,
there
is
a
setting
here
when
you
set
up
your
peers,
you
can
actually
mark
it
as
an
anchor
peer
which
actually
gives
the
other
organization
a
way
to
fetch
the
peers
of
your
organization.
So
you
actually
can
see
what
are
the
other
peers
in
the
network
through
the
discovery
service,
the
fabric.
B
B
Those
are
actually
stored
in
in
a
folder
on
the
system
on
where
we
run
the
network,
okay
and
then
actually
they're
brought
back
to
the
client.
So
the
client
you're,
seeing
here,
is
actually
running
on
a
different
machine
that
could
be
or
could
not
be
part
of
the
same
cluster
of
machines
doesn't
matter,
but
we
fetch
those
actually
certificates
on
the
client
so
from
their
own.