►
Description
This workshop provides an in-depth hands on discussion and demonstration of using Bevel and the new Bevel-Operator-Fabric to deploy Hyperledger Fabric on Kubernetes.
Hyperledger Bevel is an automation tool for deploying consistent, production worthy DLT platforms on cloud. It provides three key aspects – security, scalability and acceleration for DLT deployments. Hyperledger Bevel currently supports deployment of R3 Corda open source and enterprise, Hyperledger Fabric, Hyperledger Indy, GoQuorum and Hyperledger Besu. It uses ansible scripts and helm charts responsible to achieve the desired DLT network state on Kubernetes and uses Flux GitOps for automation.
The Hyperledger Bevel developers have recently integrated hlf-operator, a Hyperledger lab, into Hyperledger Bevel and have renamed it to Bevel-Operator-Fabric. Adding Bevel-Operator-Fabric is an important milestone for Hyperledger Bevel and a step towards the redesign of Bevel with support for Kubernetes operators to achieve DLT (distributed ledger technology) network deployments and automation.
Bevel-Operator-Fabric is the first of the different sets of Kubernetes operators that Hyperledger Bevel will ultimately support. As the name suggests, it is a Kubernetes operator for managing Hyperledger Fabric networks. Bevel-operator-fabric enables developers to define Hyperledger Fabric components in the form of custom resources and associated controllers to manage the lifecycle of those components.
Presenters
* Sownak Roy, Accenture
* Suvajit Sarkar, Accenture
* David Viejo, Kung Fu Software
For more information about Bevel, check out: https://github.com/hyperledger/bevel
For more information about Bevel-Operator-Fabric, check out: https://github.com/hyperledger/bevel-operator-fabric
----
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)
B
So
throughout
the
Workshop
you
can,
as
David
already
pointed
you,
can
feel
free
to
ask
questions
and
also
use
our
Discord
Channel
and
then
just
have
have
that
open,
so
we'll
be
posting
out
links
and
code
Snippets
to
help
you
with
the
workshop
with
that.
Let
me
let's
have
some
introduction
from
the
speakers
for
the
session.
C
B
Around
decade
of
experience
in
software,
engineering
and
technology
management,
I
work
with
accenture's
metaverse
and
Continuum
business
group
I'm
also
the
maintainer
of
hyperledger
bevel
previous
work.
Experience
was
with
Oracle
and
safe
in
global
markets.
You
can
find
me
on
LinkedIn
my
IDs
as
circar1604.
B
B
Right,
okay,
yep,
so
hyperledger
bevel
is
an
automation
framework
for
rapidly
and
consistently
deploying
production
ready,
DLT
platform.
It
is
not
a
dld
platform
it.
It
is
a
tool
which
does
the
automation,
so
there's
always
some
confusion
when
when
people
usually
start
with,
but
the
important
point
to
understand
it
is
that
it's
a
deployment
tool.
B
So,
in
a
nutshell,
if
you
see
the
diagram
here,
it
it
kind
of
starts
with
a
developer
or
an
operator
configuring.
A
single
configuration
file,
we
kind
of
prefer
it
as
a
network
yaml
file
and
the
that
single
configuration
file
holds
the
information
of
the
DLT
platform
on
network
that
the
user
wants
to
deploy.
B
Now
there
are
some
guiding
principles
based
on
which
bevel
has
the
bevel
solution
has
been
created
and,
and
it
majorly
kind
of
confronts
to
the
reference
architecture.
We'll
talk
about
the
reference
architecture
a
bit
in
the
later
slides.
The
other
guiding
principles
are
the
infrastructure
independent
part
of
it,
which
is
done
through
the
abstraction
on
kubernetes,
allowing
it
to
be
deployed
on
any
cloud
provider
or
choice
or
on-prem
infrastructure
as
well.
B
Most
of
the
components
that
are
in
bevel
are
modular
in
design,
so
you
are
free
to
kind
of
plug
and
play
with
them
and
have
your
own
desired
components.
Basically,
the
bevel
solution
is
designed
for
security,
so
with
uses
best
key
management
practices,
none
of
the
keys
or
credentials
are
stored
in
the
source
or
configuration
file.
We'll
also
talk
about
these
in
more
details
when
we
actually
go
through
the
Workshop
demonstration
and
yeah.
Of
course,
it
is
open
sourced
under
Apache
2.0
license.
Then
it's
contributed
to
hyperledger.
B
Moving
to
the
next
slide,
so
key
benefits
of
using
bevel
I
would
say
bevel.
The
key
benefits
of
bevel
are
tree
aspects
of
it,
which
is,
firstly,
it
provides
a
secure
environment
for
your
deployments
by
utilizing,
as
I
was
talking
about
the
best
key
practices
of
Key
Management,
which
is
available
by
default
in
the
solution.
Secondly,
it
is
a
truly
scalable
solution,
allowing
the
platforms
to
be
used
for
early
pocs
and
pilots
and
then
can
be
scaled
up
to
run
in
a
true
production
environment.
B
B
B
E
B
Containerized
assets
and
bevel
itself
can
also
be
run
out.
The
source
code
can
be
run
from
a
containerized
environment
and
you'll
also
see,
while
you
do
the
workshop
that
most
of
the
configurations,
as
as
initially
we
talked
about
the
network,
yaml
file
and
also
the
other
different
DLT
Network
related
configurations,
you'll
see
that
all
of
them
are
created
as
code.
So
all
the
policies
and
configurations
can
be
can
be
configured
through
the
3D
code
itself.
D
D
D
Dlt
Networks,
then,
on
top
of
that
we
have
the
distributed
data
platforms.
So
at
some
point
we
had
the
distributed.
Databases
I
think
no
one
has
actually
worked
on
this
yet,
but
it's
still
there,
but
on
the
Ledger
side
we
we
support
all
these,
so
that
means
hyperledger
Fabric
in
the
Quorum
Basu
and
Corda
Enterprise
and
open
source.
We
support
all
of
them,
then,
on
the
next
layer
where
we
integrate,
which
is
includes
the
application
integration
as
well
as
dld
education
and
DLT
integration.
D
We
mainly
use
Ambassador
for
most
of
the
these
two
dlts,
but
specifically
for
fabric.
We
use
proxy
the
other
application
Integrations
and
are
will
be
dependent
on
whatever
application
you
are
developing
on
the
DLT
and
then,
of
course
you
have
the
presentation
Services,
which
is
mainly
the
front
end,
so
that
will
of
course,
definitely
be
according
to
your
application.
D
So
whatever
is
is
basically,
as
a
picture
here
is
provided
by
by
bevel
and
the
one
those
you
can
see
in
the
green
boxes
are,
are
the
prerequisites
I
mean
it?
Bevel
does
not
do
them.
You
have
to
have
them
before
you.
You
are
trying
to
use
level
on
the
security
services.
Of
course,
the
main
main
is
is
the
vault
which
is
Services
your
screen
yeah.
So
it
is
Bolt,
which
is
the
key
management
where
all
the
keys
and
certificates
and
even
secrets
are
stored.
D
There,
then,
of
all
the
policies
are
done
by
in
git.
The
policies
means
like
who
has
access
and
all
that
because
we
use
githubs.
So
all
the
policy
management
is
happening
is
taken
care
of
by
kit,
the
other
ones
like
IAM
and
certificate
authorities,
and
all
the
other
things
they
are
determined
by
the
project
or
or
kind
of
or
again
will
depend
on
the
application,
because
you
will,
your
application
will
have
a
different
way
to
access
the
front
end,
for
example,
then
subbing
to
the
devops
services.
D
If
we
again
do
bottom
up,
we
have
the
application
lifecycle
management,
which
is
the
delivery
management.
We,
inter
ourselves,
use
GitHub
and
read
the
docs.
So
all
the
documentation
is
on
read
the
docs
and
GitHub
is
our
main,
where
we
do
all
the
all
the
spirit,
management,
speed,
planning
and
and
release
management.
Then,
on
the
build
and
test
artifact
management,
we
we
have
Jenkins
as
well,
which
we
are
we.
We
have
not
used
for
a
long
time,
but
it's
there,
but
we
have
now
mainly
moved
on
to
GitHub
action.
D
So
all
the
build
management
release
management
releases
actual
releases
happen
via
GitHub
actions.
All
the
sample
codes
are
there
on
on
GitHub
under
the
dot
dot,
GitHub
folder,
you
have
the
infrastructure
as
code,
which
is
not
part
here,
because,
as
I
said,
that
the
infrastructure,
the
cloud
infrastructure
is,
is
a
prerequisite.
D
Then
you
we
have
the
kubernetes
deploy.
We
used.
We
of
course
use
Helm
hell,
mainly
the
helm
operator
and
the
flux
operator
to
do
that
which
again
uses
hell,
then
Prometheus
and
graphene
is
kind
of
it's
still
in
the
backlog.
We
have
not
with
the
we
need
some
help
on
there.
So
if
you
hear
anyone
is,
is
able
to
help
on
the
issues
which
are
related
to
deployment
of
Prometheus
and
grafana
for
any
of
the
DLT
networks.
It
would
be
great,
then
configuration
management
is
via
ansible.
D
Again
we
as
we
discuss
our
main
configuration
file
is
just
one
network
ml.
We
don't
do
the
whole
management
of
servers
via
ansible,
because
it's
this
anyway
on
on
separately
done
by
the
cloud
provider
and
we
are
using
manage
kubernetes
Solutions.
So
we
don't
need
to
configure
kubernetes
via
ansible
or
anything,
but
we
are
mainly
using
it
for
the
template
for
creating
the
helm
releases,
Helm
files
which,
which
is
gets
deployed
via
the
gitops,
and
that's
where
we
have
the
version
management
via
Gates
and
githubs.
D
B
E
F
E
Yeah
I
have
a
quick
question
with
respect
to
the
previous
slide
on
the
architecture.
So,
instead
of
using
you
know,
managed
kubernetes.
If
we
could
I
mean
if
the
self-managed
kubernetes
could
provide
the
more
you
know,
powerful
options
to
go
ahead,
I
mean
implement
the
solution,
so
how
different
so
will
it
be?
Will
it
be
more
advantage
to
use
self-managed
kubernetes
instead
of
the
managed
kubernetes?
So
could
you
please
put
more
light
on
that.
D
Yeah,
so
if
you
go
back
on
that
yeah,
so
I'll
I'll
answer
that
so
self-managed
I
I
mean
I,
don't
think
from
a
barrel
point
of
view
or
from
a
DLT
pan
point
of
view.
It
it
doesn't
matter
if
you're
using
a
self-managed
equipment
is
or
a
managed,
kubernetes
I
don't
see,
there
is
a
positive
or
negative.
It
will
depend
on
your.
You
know:
companies,
policies
or
your
clients
policies
if
they
want
to
use
self-managed
kubernetes
and
they
have
people
to
manage
their
kubernetes.
D
Then
then
fine,
yeah
I,
don't
think
there
is
any
advantage
or
disadvantage
in
using
a
self-managed
kubernetes.
The
only
difference
that
you
would
notice
when
and
that's
with
any
kubernetes,
even
if
you
move
from
AWS
to
Google
that
the
change
that
you
need
to
do
on
bevel
side
is
at
the
correct
storage
class
so
that
the
PVCs
or
you
know,
persistent
volumes-
are
getting
created.
E
D
Yeah,
okay,
we
have
another
question
about
alternative
tools
like
Argo
CT
Etc.
Yes,
why
not
I
mean
Jenkins
and
GitHub
actions
is
not
a
part
of
bevel
it's
it's
an
example
that
we
provide
that
that
is
there
for
someone
who
wants
to
automate.
The
whole
solution
is
the
release
management
and
all.
If
those
are
examples,
I
mean
GitHub
actions
we
use
for
ourselves
like
for
bevel
as
an
open
source
project.
Not
it
is
not.
D
If
you
are,
someone
is
using
bevel,
they
don't
have
to
use
GitHub
action,
they
can
just
run
it
manually,
so
there
is
yeah
you
can
always
use
Argo,
CD
or
anything
any
other
or
even
git
lab
or
something
to
automate.
We
have
also
you
know
from
our
experience.
We
have
even
used
AWS
devops
tools
and
Azure
devops
tools
to
as
automate
the
whole
process,
because
at
bevel
from
bevel
side,
it's
it's
more
mainly
running
ansible
commands
foreign.
D
D
Because
if
the
question
is
that
then
fabric
operator,
bevel
fabric
operator
fabric
is
part
of
bevel?
Is
it's
just
that
we
are
not
have
integrated
yet
but
in
general
I
think
if
superjit
you
can
post
the
blog
post
about
the
differences,
but
in
somebody
bevel,
the
one
that
originally
was
was
created
or
for
more
Production
Solutions,
because
it
is
production
worthy
and
and
you
you
just
run
it
using
the
configuration
management
and
gitops
it
all
comes
with
it.
D
Even
the
magical
Vault
you
need
hashikov
Vault
to
use
bevel,
so
the
security
and
all
is
integrated
in
it.
But
when
you're
using
bevel
operator
fabric,
you
have
to
run
it
yourself
and
think.
That's
that's
part
of
the
second
part
of
this
demonstration
or
or
Workshop
which,
where
David
Behavior
will
will
explain
what
is
bevel
operator
fabric.
D
Then
I
think
I'll
close
the
questions
with
another
two
second
ones.
So
external
chain
code
is
there
currently
on
hlfb
use
it
yeah
external
chain.
Code
example.
Is
there
now,
which
is
released
last
Sprint
right
that
it
is
available
on
the
develop
Branch?
It
has
not
been
yet
merged
and
released
to
the
main,
but
it
is
there
available
on
the
develop
branch,
a
documentation
for
hosting
on
Google
Cloud.
D
B
D
D
G
D
D
D
From
the
demo
point
of
view
right,
so
we
are
not
from
from
demo.
We
are
not
creating
a
separate
Network
or
sorry
a
kubernetes
now.
So,
if
whoever
is
working
on,
if
your
guys
are
working
on,
you
want
to
do
it
along
with
me,
then
you
will
have
to
you
know.
Have
your
own
kubernetes
is.
Is
anyone
here
who
is
actually
ready
for
the
workshop
which
we
have
kubernetes
installed.
F
D
F
D
So
as
we
had
talked
about
I
can
I
can
give
you
a
brief
overview
of
how
how
this
works
on
the
bevel,
so
I
have
the
the
bevel
as
I
have
cloned
it
like
git
clone
bevel
like
it's
just
that
it's
named
as
bab
demo,
my
older
it's
from
old
project
or
for
the
demos
so
I
have
cloned
it
and
I
am
here
as
well,
so
git
remote,
sorry,
yeah,
git,
Branch
I
am
on
fabric
Branch.
So
this
is
the
latest
that
I
have
cloned
from
from
develop.
D
All
right,
I'll,
give
you
an
exam.
The
the
structure
is
folder
structure
is
I
mean
can
be
a
little
bit
confusing
because
we
have
so
many
platforms,
so
we
actually
have
substrate
now,
as
well
as
an
example
substrate,
but
yeah.
So
the
make
all
the
code
are
are
under
platform
for
each
of
these
different
platforms.
But
shared
is
a
common
platform,
so
this
this
part,
is,
is
used
by
all
the
platforms.
D
D
Then
configuration
contains
all
the
playbooks
and
roles
because
we
are
using
ansible
images
is
kind
of
empty,
but
in
general,
wherever
there
would
be
custom,
Docker
images
containers
required.
Then
the
docker
files
will
be
in
these
images.
Folder
releases
is
where
the
releases
will
go
because
it's
we
are
using
githubs
and
then
scripts
here
are
some
sample
scripts
for
for
all
the
crypto
generation
and
all
that.
But
then
we
have
the
for
the
external
chain
code.
D
We
have
the
chain
code,
server
and
peers
chain
code,
certificate
generation,
scripts
here,
so
basically
any
script.
Shell
scripts
that
you
will
need
for
for
that
particular
platform
platform
will
be
in
here.
I'll
explain
the
proxy
the
network
camel,
which
is
the
configuration
file
which
we
are
talking
about.
So
if
we
go
to
configuration,
then
all
the
playbooks
are
here.
So
the
operation
operators
will
be
using
just
the
Playbook
at
this
when
they
are
specifically
working
upon
hyperledger
fabric,
but
in
general
for
the
shared,
which
is
the
common
playbooks.
D
We
go
to
shared
and
these
playbooks.
So
these
are
the
common
playbooks,
like
you,
have
all
the
requirements
or
all
the
setuping
of
the
environments
or
validating
the
schema,
and
our
will
be.
We
generally
all
our
documentation
refer
to
the
site.yaml
Playbook,
which
which
is
kind
of
like,
like
the
main
Playbook,
but
within
fabric.
Also,
you
have
additional
sub
playbooks,
like
you
want
to
add
a
new
peer.
You
want
to
add
CLI
specific
CLI.
You
want
to
deploy
just
the
fabric
console
you
you
have.
As
I
said,
you
have
the
external
chain
Port.
D
So
these
are
the
separate
playbooks
that
you
provided,
but
will
be
mainly
using
that
now,
playbooks
need
an
input
which
is
the
network
file,
which
is
we
call
Network
ml
or
the
configuration
file.
So
we
have
the
network
for
this
demo
or
Workshop.
We
are
using
this
and
I
think
so.
Widget
has
provided
I
want
a
better
one,
but
I'll
explain
it
in
anyways
regardless.
D
So
we
have
all
all
networks
in
hyperledger
bevel
has
a
similar
looking
network
yaml
and
they
are
all
in
these
configuration
samples,
and
you
can
see
there
are
so
many
different
samples
for
fabric,
because
fabric
is
the
most
used
platform
for
for
bevel,
and
we
have
a
lot
of
different
examples
like
how
to
do
this
and
how
to
do
that
kind
of
examples
here.
So
we've
moved
on
from
Kafka
and
we're
only
supporting
raft
nowadays.
A
A
D
All
right
yeah,
so
yeah
I
didn't
so
this.
You
can
actually
minimize
this
here
to
see
so
yeah
under
samples.
You
have
all
these
examples
as
I
was
talking
about
you,
you,
because
fabric
supports
most
or
more
operations
than
any
other
platform
right
now,
because
fabric
is
the
most
used
platform
for
bevel,
so
you
have
different
samples
for
others.
Also,
there
are
minimum
samples,
but
generally
everyone
will
have
a
made
Network
ammo,
so
I'll
explain
the
network
gamble
now.
D
D
Then
we
have
an
environment
section,
which
is
mainly
like
a
common
environment,
a
common
section
for
all
the
environments.
Then
we
have
a
Docker
section
where
which
is
mainly
used
when
you
have
a
private
Docker
images,
I
mean
if
you're
not
using
private
Docker.
You
can
actually
comment
this
out
and
or
not
use
the
username
password.
D
D
So
you
have
ordered,
and
then
it
has
the
order
name
and
then
the
organization
name,
and
what
is
the
URI
and
all
so
in
this
example,
I
will
be
using
a
local
or
a
proxy
as
none
that's
why
the
organization
name
has
a
local
name,
and
then
environment
type
is
basically
it
just
creates
a
tag
for
the
flux
deployment.
If
you
have
multiple
deployments,
you
must
generally
encouraged
it's
not
entirely.
You
must
use
the
different
tag
for
each
of
the
environments.
D
These
are.
This
is
the
retry
count
which
which
basically
within
x
within
ansible,
we
check.
If
the
network
is
up,
you
know
has
reached
a
certain
state,
so
it
retries
for
this
much.
So
if
you
basically
have
a
slower
network,
it
is
higher
number,
if
you,
if
you
require,
if
your
network
is
fast
enough,
you
I
think
20
also
is
fine.
We
are
not
using
proxy.
That
is
why
we
don't
need
to
have
external
DNS.
If
we
had
external
DNS,
it
will
automatically
update
the
external
DNS
paths
Etc.
D
D
Okay,
so
you
have
yeah,
so
only
the
the
only
thing
is
that
I
have
the
V2
here,
the
old
one,
so
the
original
one
which
we
generally
use
for
for
or
NM
for
cross-cluster
deployments.
So
that's
when
the
proxy
is
proxy
h
a
proxy.
We
don't
actually
have
Ambassador.
We
I
had
problems
with
Ambassador
for
fabric.
That
is
why
we
never
used
Amber
Center.
So
you
can
use
each
proxy,
but
in
this
case
we
are
using
none
because
it
will
be
local.
D
We
are
deploying
it
only
in
one
cluster.
We
are
not
using
multiple
clusters
right
so
yeah.
So
that
is
why,
because
we
are
doing
local,
the
URI
is
local
order,
one
Whatever
supply
chain
and
the
port
number
for
for
public
or
user
using
h
a
proxy.
You
use
your
fully
fqdn
with
then
say:
443
or
https
or
8443.
D
Then
we
have
the
channel
configuration,
so
you
can
provide
multiple
channels
here.
In
this
example,
there
is
only
one
channel
called
all
Channel,
then
any
chain
code
for
the
channel
you
can
provide
here
whatever
orderers
are
part
of
this
channel
is
here,
which
is
basically
the
organization
name
of
the
order,
and
then
all
the
participants
of
the
Channel.
Then
you
will
also
have
the
endorsers
for
the
channel,
and
this
is
all
details.
D
D
You
will
provide
a
Genesis
name
again,
which
is
a
unique
name
for
a
different
group
for,
for
that
particular
Channel
then
comes
the
section
of
the
organizations
now
bevel
is
designed
so
that
one
originally
designed
its
production
worthy
and
all
so
originally
designed
that
only
one
organization
is
part
of
one
kubernetes
cluster
for
another
kubernetes
cluster.
You
will
use
another
organization
right
or
you
will
use
another
another
kubernetes
cluster
for
a
new
organization,
but
in
all
the
occurs,
when
we
do
deployments
or
examples,
you
cannot
have
multiple
organizations.
D
Sorry
kubernetes
clusters
for
different
for
a
small
example,
so
we
are
using
a
single
I
mean
in
the
same
cluster
itself.
All
the
organizations
but
in
general
organizations,
are
like
how
fabric
does
the
members
right?
So
those
are
the
members
so
in.
In
this
example,
we
have
the
first
organization,
which
is
an
order
or
organization.
That
is
why
the
type
is
ordered
and
then
all
the
details
of
the
ca
server
and
the
you
know
your
AWS
Keys
Etc
will
provide.
D
Then
the
kubernetes
section
you
have
to
provide
the
kubernetes
config
file,
which
the
you
use
to
connect
to
the
cube
CTL.
Then
you
provide
the
Vault
where
all
the
secrets
will
be
stored,
and
then
we
have
the
GitHub
section
where
all
the
git
details,
all
the
details
are
there
I
think
most
of
us
is
quite
we
have
you
have
used,
we
are
using
it,
it's
create.
You
can
update
it.
It's
already
provided
all
the
examples.
Then
you
under
that
under
after
the
githubs,
so
this
is
again
per
organization.
D
Each
organization
has
a
similar
concept
or
or
same
keys
after
that,
then
you
have
the
services
where
you
have
this
CA
and
and
then
the
orders,
so
this
is
for
the
regular
order
organization.
Now,
if
we
go
to
the
manufacturer,
which
is
a
member
organization
or
a
peer
organization,
then
of
course
a
CA,
and
these
details
are
common,
then
only
difference
you
can
see
is
that
you
have
the
users,
you
can
add.
Bevel
will
generate
a
user
One
automatically.
D
So
if
this
section
is
missing
even
then
you
will,
you
will
generate
a
user
one.
But
if
you
want
to
add
more
new
users,
you
can
add
here
and
then
you
can
give
to
all
the
revoker
and
what
else
and
dots
are
those
kind
of
attributes
via
this
attributes
channel
sorry
attributes
key,
so
you
can
add
more
more
users
for
your
application.
D
Then
you
can
you
have
the
ca
service,
because
each
organization
has
a
fabric
CA
and
then,
after
that
you
have
the
peers.
In
this
example,
we
have
only
one
peer,
but
you
can
add
multiple
peers
with
just
adding
here.
So
in
each
peer.
You
have,
of
course,
the
peer
type
as
anchor
or
non-anchor
the
gossip
peer
address.
In
this
case
they
are
the
same,
but
if
it
were,
there
were
two
Piers.
D
D
Here
is
public
key.
Basically,
then
we
have
the
CLI
part
which
is
enabled
or
disabled.
It
will
create
a
CLI.
Then
we
recently
released
the
cactus
connector,
so
you
can
do
enabled
the
main
main
Playbook
will
not
deploy
that
access.
Connector.
There
is
a
separate
playbook
for
deploying
the
cactus
connector.
D
Then
all
the
ports,
you
will
find
all
the
ports.
So
mainly,
these
are
the
used
this
rest
server
and
express
API.
These
are
part
of
the
application
deployment,
so
it
is
here
just
as
an
example,
after
that
you
can
pass
the
chain
codes,
so
you
can
pass
now.
You
can
pass
multiple
chain
codes
earlier.
We
used
to
support
only
one
chain
code,
but
now
you
can
pass
multiple
chain
codes
as
an
array
like
this.
D
So
in
this
example,
we
are
passing
this
chain
code
and
all
the
details
are
here
like
how
to
how
to
do
the
change
course.
Then
I
think
the
metrics
were
enabled
recently,
so
this
will
enable
The
Matrix
server
same
for
the
final
third
organization.
Yeah,
just
you
know
different
names
and
the
certificate
parts
and
all
are
different,
but
otherwise
is
generally
the
same
kind
of
configuration.
B
So
just
to
clear
the
confusion,
you
can
configure
the
organizations
to
be
on
different
clusters,
that's
what
should
be
suggested
and
is
suggested
for
production
architecture
where
each
organization
kind
of
has
its
own
cluster.
But
as
shanak
was
mentioning
for
test
environments
or
for
a
quick
development,
you
can
have
all
the
organizations
kind
of
be
deployed
on
on
a
single
cluster
yeah.
D
So
yeah
to
to
you,
know
zoom
in
on
that
how
we
will
do
that
is
via
this
section.
Each
organization
has
a
case
section
and
of
course,
each
other.
If
you
are
using
AWS,
each
organization
has
a
different
AWS
section.
So
if
you're
using
AWS
keys
and
values,
then
you
can
give
the
AWS
details
for
the
different
organization
to
be
different
for
each
and
then
under
the
kts
section.
D
D
D
You
should
be
you,
you
will
not
beep
you
if
you
use
these
kind
of
Uris,
it
is
not
going
to
work
because
it
is
on
different
clusters,
and
these
are
local
cluster
Uris
right.
So
you
will.
You
will
use
these
kind
of
method
where
you
you
own,
the
domain
called
blockchaincloud
poc.com,
and
then
you
have
created
proper
paths
or
DNS
Roots,
so
that
your
order,
one
dot
or
one
Ambassador,
is
correctly
pointing.
D
Okay,
I
see
some
few
questions
is
I.
Don't
know
why
the
chat
window
is
so
small
for
me.
Okay,
I
can
increase
it
now,
yeah
can
people.
So
there
was
a
question
about.
Can
we
have
only
organization
with
both?
Yes,
we
can,
and
that
is
where
you
have
this
Branch,
where
you
should
be
I
mean
that
branch
is
actually
not
kept
updated
because
we
don't
I,
think
we.
It
adds
unnecessary
confusion,
but
you
can
use
the
code
from
this
mixed
organization
Branch.
D
D
D
Ports
on
the
grpc
defaults
yeah,
you
can
modify
I
mean
if
I
go
back
on
this
I
mean
that's.
The
whole
point
of
this
file
is
is,
if
you
want
to
change
all
these
ports
to
seven
zero,
whatever
or
nine
five
nine,
two
or
yeah,
so
that
that
you
can
modify
and
bevel
will
work,
just
ensure
that
it
is.
You
have
changed
everywhere,
because
this
is
a
local
example
right.
So
you
can
you
have
to
modify
all
the
paths
correctly
for
for
a
different
port.
D
Yeah
I'll
I'll
show
how
the
secrets
are
managed.
I
will
show
that
anything
so
yeah
so
generally
secrets
are
managed.
I
would
say
is
is
via
Vault.
So
all
the
secrets,
you
will
need
the
Vault
URL
and
the
Vault
root
token.
It
will
be
passed
here
just
another
important
thing,
because
you
will
have
different
a
lot
of
secrets
in
this
file.
D
D
It
should
be
in
yeah
as
it
should
be
inside
a
build
folder,
which
you
just
create
like
mktir,
build
and
and
put
that
there
and
then
once
you
run
it
or
if
you
want
to
change
it
yeah,
you
can
have
a
separate,
for
example,
a
private
repository.
If
you
want
to
store
your
network
configurations
and
share
it
with
with
your
team
members,
but
it
should
not
never
be
a
public
Repository.
D
A
D
I
answered
the
questions,
can
other
hyperledger
tools
like
caliper
or
Explorer,
be
connected
and
launched
by
bevel
I
mean
it's
I'm,
not
sure
what?
What
is
the
goal
here?
But
if,
if
you
want
to
it
can
be,
it
is
not
there
supported.
Now,
as
as
we
kind
of
trying
to
mention
bevel
is
a
deployment
tool
it
deploys.
D
What
is
the
max
cluster
organization?
It
can
support,
I
would
say
10
we
have
not
tested
Beyond
because
it
will
take
long
time
or
or
I,
don't
think
it
will
be
suitable
for
for
test
cases
as
well.
So
it
is,
it
I
would
say
10
for
now
and
because
it
takes,
of
course
it
will
take
a
long
time
to
run
and
all
that
any
other
question
that
I
have
missed.
D
Oh,
there
was
a
question:
where
is
the
fabric
branch?
In
this
repository?
There
is
no
fabric
branch
in
the
repository.
You
have
to
create
the
branch
so
because
you
want
to
keep
your
deployment
separate
from
the
develop
branch.
That
is
why
you
just
create
the
branch
like
git
checkout,
minus
B
fabric.
That's
all
you
have
to
do.
D
Can
you
just
work
with
an
external
DNS
and
connect
with
a
Gateway
for
an
end
user
application?
I
have
yes,
so
you,
if
you
have
a
separate
way
to
connect
or
ex
expose
your
applications?
That's
fine
yeah!
So
you
don't
have
to
make
the
whole
fabric
Network,
as
as
a
public
network
right
if
you're
running
the
whole
fabric
Network
only
in
a
single
kubernetes
cluster,
then
it's
where
you
you
can
just
expose
the
application.
D
You
know
either
the
API
or
the
rest,
server
or
or
the
front
end,
for
example,
or
via
any
other
method
that
you
want
to
expose
it
to
through,
but
yeah
within.
If
you,
if,
if
you
are
not
deploying
anything
separately
like
in
a
different
environment,
then
cluster,
then
it
is
no
no
need
to
use
an
external
DNS
or
or
h
a
proxy.
D
D
So
you
you
can't
bevel
cannot
guarantee
if
the
cluster
is
connected
or
not,
it
will
try
to
and
if
it
is
not
working
now,
if
it
takes
longer
time
yeah,
you
can
I
think
there
are
some
parameters
in
the
fabric.
Rest
server
that
you
can
modify
for
for
that
connection
parameters,
but
otherwise
you
know
bevel
is
deploying
the
DLT
Network.
E
D
D
Yeah
Edward
your
question
that
external
DNS,
if
you
are
planning
to
have
various
organizations
in
different
clusters-
yes,
that
is
right,
so
you
will
need
to
have
external
DNS
and
and
domain
DNS.
You
know
configured
so
that
to,
for
example,
peer
one
in
cluster,
one
can
talk
to
peer
one
in
cluster
two
from
a
different
organization.
Yes,
so
you
will
need
the
external
DNS.
D
Can
we
distribute
orderers
between
clusters
using
bevel,
going
back
again
to
the
new,
the
other
branch
that
we
showed
you
yeah?
If
you're
using
the
mixed
organization
Branch,
then
you
can
have
you
can
have
each
each
of
each
organization
can
have
orders,
it's
ordered
and
peers,
not
just
order
and
peers
so
or
peers,
so
you
can
have
both.
In
that
case,
you
can
have
distribute
the
orders
between
different
clusters
using
bevel,
or
you
have
multiple
order
scenario.
Bevel
also
supports
multiple
orders.
You
know
multiple
order
organizations
as
well.
D
Yeah
going
back
to
the
question
about
how
many
minimum
order,
so
this
is
an
example.
That
is
why
we
use
only
one
raft
orderer,
but
ideally,
as
always
all
draft
examples,
it
says
for
for
cons,
consistency
or
I,
don't
know
what
it's
called,
but
forget
the
term,
but
you
need
two
n
plus
one.
So,
basically,
if
you
want
to
work
with
one
failure,
I
think
you
need
three
cluster
three
orders
in
the
raft.
So
if
you,
if
you
need
more,
you
cannot,
or
it
should
ideally
be
odd
number
of
orders.
D
D
B
B
B
D
Yeah,
so
for
anyone
who
is
a
bit
confused,
so
you
can
just
create
a
file
called
override
yaml
inside
build
directory.
In
this
case,
we
just
done
it
is
build
infra.
Then
over
ID
amount,
so
you
can
just
write
I,
create
it
in
under
build
directory
so
that
it
doesn't
get
checked
in
because
there's
no
point
yeah
yep.
B
So
once
you're
ready
with
the
file,
we
are
ready
to
install
the
helm
so
Helm
chart
before
that.
You
can
create
a
separate
namespace
for
your
Vault
to
run.
So
you
do
it
simply.
By
creating
running
this
Cube
CTL
command,
which
is
Cube
CTL,
create
NS,
stands
for
namespace
and
the
name
of
the
namespace.
We
we
wanted
to
have
the
name
space
name
as
vault.
D
B
Yes
and
then
finally,
the
installation
command,
which
is
Helm,
install
the
installation
name,
would
be
Vault,
and
this
is
the
Helm
chart
that
we
have
added.
So
that's
the
mention
of
that
and
then
the
namespace
on
which
we
want
to
have
the
installation,
the
namespace
that
we
created
is
Vault.
The
version
is
the
choice
of
version
that
we
picked
from
here
when
we
did
the
search
and
then
finally,
we
have
to
add
the
override
file
to
overwrite
the
default
values
of
the
Vault
Helm
chart.
B
D
Production
steps
for
security,
you
you
can
use
the
use
a
console
model
where
you
will
have
multiple
faults.
You
can
have
vault
in
high
availability
mode.
You
can
have
Vault
in
a
private
Cloud.
You
know
not
in
the
cluster
itself.
You
can
have
vault
as
as
a
separate
running
as
a
separate
VM
in
your
private
name,
namespace,
not
private,
subnets
and
and
then
you
can
use
it.
You
know
within
from
within
the
kubernetes
cluster.
So
those
are
a
few
ways
of
deploying
more
production,
oriented
world.
D
F
B
B
B
B
B
So
one
sign
in
you
can
now
start
using
the
The
Vault.
One
of
the
prerequisite
of
of
having
Vault
and
running
bevel
is
to
have
a
unsealed
Vault
and
have
a
secret
engine
created,
so
we'll
use
a
KV
secret
engine
to
to
kind
of
store
our
secrets
for
for
the
network.
So
you
can
create
a
secret
engine
using
the
the
button
here
so
enable
secret
engine.
It
would
be
a
type
of
key
value
and
then
you
can
just
name
it.
B
D
F
F
D
But
if
you
have
created
something
different,
you
can
that
use.
That
then
comes
I'll.
Just
explain
what
is
the
GitHub
section,
which
will
be
same
for
you
mostly,
so
you
will
can
use
https
or
or
good
protocol
as
SSH.
So
let's
use
https.
In
that
case
your
git
URL
will
be
https
github.com.
Then
your
username,
basically
your
fourth
bevel
name.
Then
this
Branch
yeah
actually
I'm
using
fabric.
So
you
can
change
it
to
fabric.
D
Then
the
release
directory
I
explained
earlier
so
that
you
can
use
this
as
the
releases
directory.
So
this
is
platform
cyber
Ledger
fabric
releases
Dev.
You
can
use
any
other
name
here
as
well.
Chart
Source
will
be
you
can
keep
it
same,
no
need
to
change
this
git
triple
is
basically
the
shorter
version
of
this
I
I
think
we
can
figure
out
how
to
make
the
same.
D
But
yes
is
still
like
this,
so
you
can
use
github.com
that
then
this
is
your
GitHub
username
and
then
replace
all
of
this
git
access
token
with
the
password
or
don't
use
password
use
an
access
token
so
that
you
can
deactivate
after
the
deployment
is
complete
or
or
in
case
it.
You
can
change
it
later.
Email
is
your
git
email
and
because
you're
using
https,
this
private
key
doesn't
matter.
D
D
Then
in
my
case
I'm
passing
build
Network
local.
You
have
to
put
add
that
in
because
it
should
read
it
as
a
file,
so
add
that
it
build
Network
local.japan.
So
that's
the
single
command
that
we
use.
It
does
a
lot
of
things
so
once
the
people
are
here,
I
think
it's
time
we
can
move
on
to
David.
We
have
about
showing
how
the
fabric
operator
works,
but
this
is
the
command
that
you
will
use
and
once
I
click
press
enter,
it
will
do
all
the
steps.
D
It
will
kind
of
check
all
the
prerequisites
and
it
will
check
all
the
it
will
install
the
deployments
of
anything
all
CLI,
for
example,
and
then
it
will
deploy.
It
will
start
doing
all
the
different
stages,
we'll
come
back
to
it
later
towards
the
end
of
the
of
this.
But
this
is
the
command
that
you
should
be
using.
D
D
C
F
C
You
can
see
it,
but
this
basically,
this
model
is
what
the
the
base,
the
presentation
that
we
did
on
January
this
year,
which
was
a
full
version
of
dollars
and
a
half,
and
that
you
know
in
order
to
understand
what
is
level
operator
fabric,
we
need
to
understand
what
is
a
kubernetes
operator.
What
is
the
goal,
so
the
role
of
opportunities
operator
is
to
make
the
deployment
of
an
application.
C
So
if
you,
if
we
look
into
the
fabric
samples,
for
example
here
there
is
an
example
on
how
to
different
coordinates,
but
this
it
would
check
the
configuration
and
the
the
German.
This
is
too
aesthetic
and
the,
and
there
is
a
large
term
about
this,
so
it
it
is
hard
to
run
Dynamic
networks
using
this
approach.
C
So
this
is
word
operator
automates
of
these
parts,
all
of
this
creation
of
of
these
resources
governed
as
a
certificates,
the
conflict
maps
the
deployment,
so
it
it
will
abstract
you
from
the
actual
deployment
of
the
of
the
Republic
Network.
So,
let's
think
the
developerative
fabric
is
a
declarative
way
of
creating
a
perfect
components.
This
includes
a
PR.
The
order
chain
called
channel
channel
is
more
logical,
but
it's
also
supported
in
the
in
the
in
the
operator.
C
Also
in
the
version
1.9,
there
is
a
possibility
to
create
identities,
which
is
a
way
to
enroll
the
user
and
get
the
certificate
in
order
to
use
it
in
applications
that
connect
to
the
cenko.
This
is
this
quantity
operator,
obviously
based
on
kubernetes
or
on
cloud
in
all
of
the
places
that
we
have
done.
We
have
work
on
cloud
because
managing
kubernetes
clusters
company-
it's
not
really
something
that
brings
much
value
and
this
customizable
for
specific
use
cases
for
some
positive
renewal,
which
is
already
supported.
C
There
is
a
an
alpha
feature,
which
is
a
automatic,
scientifically
renewal
with
one
month
or
15
days
before
it
can
remove
your
data
certificates
for
your
peers
and
your
rotators.
So
this
is
also
something
some
feature
that
was
asked
a
lot
before
and
what
is
supported
apart
from
the
happy
leveling
components.
So
I
saw
a
question
before
in
the
chat
about
the
investment
code,
is
supported
in
developerative
fabric
educational
components
and
also
the
channel
configuration
as
a
code.
C
This
is
a
really
useful
feature,
because
one
of
the
hardest
is
to
manage
the
governance
and
the
and
the
governance
and
the
population
of
the
channel,
for
example,
how
many
transactions
you
want
in
a
blog,
whatever
organizations
that
will
belong
to
the
network.
What
are
the
consensus?
So
we
have
a
resource
that
we
will
see
in
the
next
screen,
which
is
Channel
configuration
which
there
are
two
parts.
C
There
is
the
founder
of
the
channel,
which
is
the
organization
that
manage
and
runs
the
channel
and
around
the
there
are
the
followers
which
are
the
organization
that
join
the
channel
and
the
versions
2.3
2.5
and
2.5
are
supported
right
now.
In
fact,
this
this
demo
will
be
based
on
hyperlade
on
the
latest
version,
I
believe
2.5.3,
which
I
think
it
was
released
like
or
something
like
that.
G
C
It's
a
personal
10
codes,
but
the
department
of
the
chain
code
is
not
if
the
task
is
not
just
to
deploy
the
kubernetes,
so
there
needs
to
be
a
thing
called
approvals
you
could
commit.
So
there
are
operations
involved
in
the
regulatory
network,
but
yeah.
This
is
supported,
and
this
is
something
that
we
will
see
in
the
demo,
because
we
will
deploy
a
organization,
it's
with
two
beers
and
then
another
organization,
with
three
orders.
C
C
C
D
Okay,
so
I
think
there
is
a
question.
Let
me
go
back
yeah,
so
the
bevel
operator,
when
do
you
use
bevel,
and
what
uses
developer
fabric
yeah
versus
operations
console
that
that
is
a
good
question.
That's
right!
So,
as
we
I
kind
of
explained,
bevel,
the
pure
bevel
it
was
was
designed
for
more
production
systems.
So
we'll
use
that
at
some
point
one
of
the
we'll
be
using
bevel
will
also
be
using
bevel
operator
fabric
to
deploy.
D
So
until
that
comes
there
is.
These
are
two
separate
kind
of
deployment
method
methodologies,
but
we
we
are
working
on
to
so
that
you
know
you
run
the
same.
Ansible
command
and
internally
bevel
will
use
the
bevel
operator
Fabric,
and
that
will
happen
for
all
the
other
platforms
as
well.
So
we
will
create
a
again
here.
Anyone
who
is
interested
to
lead
the
way
to
bevel
operator
Coda
or
a
bevel
operator
Quorum,
please
feel
free
to
get
in
touch.
D
So
basically,
at
that
point,
bevel
will
use
the
gitops
operator
for
production,
oriented
workloads
and
we'll
use
the
Fab
bevel
fabric
operator
or
bevel
operator,
Fabric
or
more
say,
POC
or
even
production
operator.
You
can
choose
what
you
want
to
use,
you
want
to
use
the
gitops
operator
or
you
want
to
use
the
bevel
operator
Fabric
and
that's
that's
the
main
difference.
So
it's
basically
not
not
a
great
difference.
D
You
can
use
bevel
right
now
to
deploy
the
operations
console
as
well
and
and
also
get
all
the
change
channel
assets
that
you
need
to
basically
manage
add
the
keys
to
the
wallet
and
all
that
so
that's
possible
via
bevel.
You
use
the
same
UI,
which
is
the
operations
console.
There
was
a
question
about
fabric
bever
supports
2.2,
but
bevel
yeah.
C
D
You
can
you
can
do
both
Channel
management,
separate
edition
of
a
new
channel
and
additional
members
yeah.
It
does
the
approval
and
all
that
as
well,
so
that
the
channel
configuration,
as
is
same
in
your
case,
yeah
you're,
using
as
a
code.
In
our
case,
it
will
be
in
the
network
yaml
as
a
configuration
yeah.
That's.
C
C
Sources
that
are
supported,
so
there
are
two
parts:
the
physical
and
the
logical
part,
the
physical,
the
order,
certificate,
Authority,
saying
code
operator
UI
and
the
public
operations
console,
which
was
a
project
which
was
donated
by
IBM.
In
order
to
manage
the
network
and
The
Logical
resources,
the
favorite
main
channel,
the
follower
Channel,
which
is
used
for
organization
to
join
a
channel
that
has
already
been
created,
but
by
by
summarization
and
more
radical
resources,
would
were
added
in
the
latest
version.
C
1.9
are
the
public
identity
and
the
fabric
Network
config,
the
federal
identity,
enrolls
the
user
and
also
manage
the
certificate
renewal,
which
is
something
that
is
a
is
also,
is
most
likely
a
problem
in
the
process
after
one
year,
then
certificates,
buyer.
So
with
this,
you
ensure
that
the
identity
that
you
will
use
in
order
to
run
the
application
that's
inspire
and
the
first
Network
config,
which
automates
the
creation
of
a
network
of
configuration
for
your
application
in
taking
into
consideration
on
the
PS
and
all
the
orders
that
are
in
your
cluster.
C
C
You
can
use
whatever
we're
going
to
discuss
that
you
want
so
in
this
in
this
demo,
we're
going
to
use
kind
which
we
will
have
locally,
but
you
plan
your
CWS
are
sure,
whatever
cloud
provider
that
you
want
and
this
cubic
CTL
will
create
the
crds
that
will
be
created
you
installing
the
headset
of
the
HLF
operator,
and
then
this
year.
This
will
be
then
taken
be
taken
from
the
agilef
operator
and
then
the
turf
operator
will
create
the
peers.
C
The
orders
for
xcas,
we'll
update
the
channel
will
manage
the
channel
configuration
for
the
channel
that
we
will
create,
update
the
channel
for
the
periodization,
including
the
computers
and
sorry,
and
also
deploy
the
visualization
crds,
which
are
the
operator
API
operator
UI
and
the
fabric
operations
control.
So
this
is
the
role
of
the
parade
at
the
end,
it
abstracts.
The
creation
of
these
entities
that
we
see
here
and
the
main
difference
between
bevel
and
developerative
fabric
is
that
we
will
focuses
on
more
networks
such
as
Corda,
the
one
that.
C
We
will
need
the
to
know
what
basic
cryptography,
what
is
a
certificate?
What
is
a
public
key,
a
private
key
basic
knowledge
about
kubernetes
and
broker
when
I,
say
Docker,
I,
say
container
deep,
so
a
container
technology
to
know
what
is
a
container
in
order
to
run
the
API,
you
will
need
node.js
with
typescript
and
then
basically
know
it's
about
cell
commands.
In
that
case,
I
would
use
Mark
M1.
So
if
you
have
back
and
one
it
will
run
more
than
fine
and
basically
networking
Concepts,
because
we
will
use
a
a
local
DNS.
C
Good
of
two
organizations
to
create
organizations-
HP
organization
will
have
its
two
peers
and
achenko,
and
then
there
will
be
another
organization
which
will
have
three
orders
and
then
the
them
organization.
The
demo
challenge
will
be
created
between
these
three
organization.
The
ordering
organization
will
manage
the
consensus
and
the
pl
will
manage
the
and
those
endorsement
of
the
transactions
and
then
the
API,
the
secret
client,
will
send
the
transactions
to
the
on
to
the
ordinary
service.
D
C
It's
probably
my
channel
is
different
from
no
what's
up
with
my
channel,
and
this
is
globally
tied
to
the
governance
and
you
may
want
to
use
another
way
for
your
use
case.
But
the
idea
of
the
public
main
channel
is
that
usually
the
interior
projects,
there
is
one
organization
that
has
the
knowledge
about
hyper
life.
African
organization
ends
up
managing
the
channel
managing
the
channel
means
who
joins
an
organization
who
lives?
C
What
is
a
configuration
of
the
channel
Etc,
so
the
government
Channel
usually
has
the
list
of
consenters,
which
are
the
one
that
manage
the
consensus
and
the
the
value
follower
channel
for
the
organization
that
they
know
another
organization
that
manages
a
channel
and
they
just
want
to
be
part
as
a
peer
organization
of
the
channel.
That
is
the
whole,
but
at
the
end
everything
is
a
piece
so.
C
C
C
C
C
So
first
thing
that
we
will
need-
and
this
is
something
that
I
already
created
in
order
to
speed
up
the
demo-
it's
the
kubernetes
cluster,
so
we
have
already
according
to
this
cluster,
which
I
can
show
here
that
this
is
the
coventus
cluster.
I
did
the
test
just
before.
So
what
we
have
to
hear
some
follower
definitions
in
the
left,
the
result
or
remain
Channel,
which
I
will
delete
in
order
to
start
from
scratch.
And
you
know
they
don't
have
any
problem,
so
we
don't
have
any
more
resources.
C
C
C
C
C
This.
We
have
done
already
uninstalled
the
telephone
operator.
The
version
1.9.0
in
this
case
I
have
already
installed
it
and
I'm
not
going
to
restore
it.
So
I
can.
But
if
you
go
through
this
step,
then
different
methods
will
appear
and
the
operator
will
be
stored
and
then
manager
will
be
created
here
and
then.
C
C
Yeah,
so
this
has
been
installed,
so
this
is
the
right
now
we
have
qcpl
HLF,
but
we
can
get
the
help
of
the
usual
plan,
which
has
all
of
these
commands
we're
not
going
to
use
all
of
them,
but
it
may
be
good
for
you
too,
to
revisit
this
so
after
installing
the
game
still
playing
with
this
is
a
acoustical
plugin
that
is
installed
in
the
development
machine.
It's
not
stored
in
the
cluster.
We
need
to
install
istio
and
you
can
just
download
istio
with
this
command,
which
will
create
a
folder.
It's
still
1.16.1.
C
In
this
folder,
and
then
you
just
export
the
path
in
order
to
plot
the
istio
binaries
in
order
to
to
be
able
to
install
Eastern
to
govern
this
cluster
and
then
step
after
this,
we
should
have
CTL
with
all
of
the
comments,
the
ones
that
we
will
use
is
operator
init,
which
will
be
the
operator.
This
I
have
already
run
so
make
sure
that
you
run
it
I
also
created
a
Mr
system.
C
These
are
the
resources.
This
is
the
service,
so
this
is
basically
the
properties
for
the
separator
and
then
after
this
is
installed,
which
we
have
already
installed.
If
we
see
in
the
in
the
coordinates,
cluster,
which
is
crd,
is
the
Redway.
This
is
healthy
already
and
what
this
will
deploy
is.
If
we
go
to
the
Post
foreign.
C
Which
will
be
the
one
that
will
serve
the
request
after
this
is
installed.
We
can
start
to
create
the
organizations,
so
actually
this
this
difference
is
for
the
words
of
the
version
in
January,
but
we
can
just
remove
that
because
the
images
are
the
same,
because
now
fabric
supports
layer
and
irm.
So
we
don't
need
to
have
different
images.
Then
we
can
just
support
them
here,
and
this
is
an
important,
also
configure
internal
DNS.
C
And
the
current
container
it
will
go
to
the
istio
English
Railway,
so
that
will
be
there.
That
would
be
the
difference.
That
is
why
we
need
to
configure
the
internal
DNS.
If
you
don't
do
this
step,
then
nothing
will
work
basically,
because
the
operator
will
not
be
able
to
contact
the
therefore
excel
in
order
to
enroll
the
users.
C
C
C
So
for
the
DNS,
we
need
to
configure
this.
This
HP
is
the
one
from
the
network.
This
is
the
English
Headway,
which
has
the
10
96
24
71
is
equal
to
a
bit,
and
so
what
will
happen
is
that
for
any
localhost.c
it
will
be
regulated
related
to
host
internal
Ingress,
and
this
will
be
related
to
the
cluster
IP
of
the
istia
investment.
So
that
is
why
we
need
this
damage.
C
So
we
just
configure
it
in
my
cases
and
change
because
I
configured
it
early
so
right
now
what
we
need
to
do
is
deploy
the
organizations,
so
we
have
here.
The
first
step
is
the
president
Authority
for
organization
one.
The
second
step
is
to
play
the
two
beers
for
organization
one
and
the
third
and
fourth
step
is
just
to
do
the
same
for
the
organization.
Two
then
the
five.
The
fifth
step
is
to
the
organization,
and
then
we
will
create
the
channel.
Then
the
organization
one
will
join
the
beer
that
appears
to
the
channel.
C
Better
then,
we
will
install
the
think
of
which
we
will
need
to
prepare
the
connection,
a
string
for
the
beer.
Okay,
the
metadata
file
prepare
the
connection
file.
This
is
for
the
external
tenko
then
build
the
chain
of
documents.
This
is
optional
because
there
is
one
provided
out
of
the
box,
but
if
you
want
to
configure
in
order
to
run
your
own
Cinco,
then
this
is,
and
we
have
two
options-
one
for
a
a
m
and
the
other
for
regular
AMD
64..
C
Then,
if
you
build
the
locally,
you
need
to
push
it
for
the
to
our
Montana
registry
that
is
accessible
by
the
importance
of
this
cluster.
It
doesn't
necessarily
need
to
be
a
a
public
container
registry.
Then
we
will
deploy
the
chain
core
here
using
this
command.
This
is
the
external
sync
code,
cluster.
C
Then
some
texts,
approval
of
the
chain
code
committing
and
then
we'll
do
doing
in
this
case
two
instructions,
and
then
we
will
not
display
them
in
order
to
see
the
peers
and
the
orders
and
the
channels
that
have
been
deployed
as
well
as
some
blocks.
So
this
is
the
a
quick
work
through
through
what
we
will
do
and
everything
is
in
common
self-definition
cells
inside
script.
C
D
C
Then
we
will
run
this
command
in
order
to
be
faster.
I
will
create
depreciation
at
the
same
time,
because
I
think
we
will
be
very,
very
tight
on
time,
so
we
will
get
a
series
for
the
second
organization
during
this
command.
The
commands
are
very,
very
similar
for
the
three
organization
we
will
in
the
in
the
meantime,
while
there
are
going
to
be
deployed,
we
will
review,
but
basically
we
are
specifying
the
claimats
which
will
have
supported
before
this
is
a
version
of
the
stress
class.
But
this
is
a.
C
This
is
the
one
that
can
support
the
capacity
for
the
for
the
storage
of
fabric
CA,
the
name
natural
ID,
which
you
can
change
the
general
password.
You
can
also
change
the
host.
This
is
for
which
we
have
confused.
The
support
is
the
same,
is
the
external
one.
So,
since
right
now
we
have
configure
the
external
portal
443,
then
we
will
stick
to
that
and
this
command.
If
you
are
running
it
running
this
in
a
Cell
script,
then
you
want
to
wait
all
of
the
fabric.
C
C
C
This
is
this
registered
the
name
of
the
of
the
certificate
Authority
that
will
be
used,
the
user
and
the
secret.
This
is
the
user
and
the
password
that
will
be
created,
the
type
of
the
user.
This
is
very
important.
What
creating
a
user
for
the
peer
is
used
for
the
beer
will
not
use
in
order
to
submit
and
sometimes
from
an
API.
This
is
really
really
important
and
then
the
credentials
in
order
to
be
able
to
register
this
issue,
this
user,
which
are
the
ones
that
we
specified
while
creating
the
fabric
certificate,
Authority
foreign.
C
So
this
is
something
that,
if
this
is
your
first
time
it
will
not
repeat
this
error
and
then
we
will
create
the
peers,
so
we
will
create
two
peers
same
time
and
then,
in
order
to
go
faster,
we
will
deploy
also
the
two
beers
for
the
organization
too,
which
is
the
same
command.
We
will
try
to
register
organization
to
use
it
for
the
peers.
This
will.
This
currency
has
been
registered
register.
Okay,.
C
We'll
wait
for
all
of
the
PS
to
be
in
the
condition
running
and
in
the
meantime,
you
can
also
see
it
on
the
on
the
lens
in
order
to
visualize
the
piercing
create
before
your
connectivity
is
good.
Then
this
will
take
one
minutes,
two
minutes
maximum.
It
would
also
depend
in
the
resources
that
you
have
in
in
your
PC.
In
this
case,
I'm
running
in
a
Mac
Studio
of
128,
there
was
developers
of
Rama
many
CPU
Corso
is
very
very
fast
and
you
saw
in
20
30
seconds.
C
We
have
a
appear
running,
so
this
players
have
already
been
created.
We
can't
verify
using
care
randomly
one.
This
will
give
this
server.
This
means
that
the
pr
is
responding.
We
do
this
for
the
pr1,
it
will
be
the
same
error,
but
this
means
that
there
is
connectivity,
PSL
or
one
same
level,
br02
singer.
If
you
want
to
go,
if
we
check
this
against
appear
that
doesn't
exist,
then
this
will
give
this
error,
which
means
that
is
going
over,
so
it
still
has
enough
away.
C
C
This
is
the
same
as
we
did
with
the
beer,
but
the
typing
instead
of
the
disorder,
and
we
have
the
role
ID.
Everything
is
the
same
and
the
MSP
ID
is
different
and
we
will
create
three
further
nodes,
which
this
is
the
closest
that
we
can
get
to
a
production
Network,
although
in
a
production,
Network
I
highly
recommend
to
run
five
ordered
notes,
because
you
will
have
more
more
room
in
case
toward
their
nodes.
C
Left,
which
will
be
more
than
enough
in
order
to
run
the
consensus
and
to
be
able
to
restore
logs
in
the
case
of
three
or
levelers,
if
two
of
them
go
down,
then
the
network
will
not
be
useful,
so
we
will
create
the
three
orders.
We
will
wait
until
these
are
created
and
then
we
will
go
to
lens
in
order
to
visualize.
F
C
C
C
If
there
is
any
question
in
the
meantime
feel
free
to
to
to
ask
it,
there
is
still
a
lot
of
I
mean
you
do
need
to
to
do
this
a
lot
of
times
if
you
are
new
to
fabric
in
order
to
understand
all
the
pieces
and
all
of
the
all
of
the
components
to
be
able
to
deploy
this
step.
A
network
in
another
plot
provider.
C
D
Okay,
there
is
a
question:
is
bevel
being
used
in
any
production,
environment,
I'm
sure,
yes
and
I'm
sure
there
are.
There
are
members
from
those
organizations
which
are
who
are
in
this
call,
so
yeah
bevel
has
been
used
and
being
used
in
production
environments.
The
question
second
question:
I
guess
is
for
operator
fabric
right.
Is
there
a
plan
to
integrate
with
Vault
for
certificates
and
other
secrets?
So
that's
for
you,
David.
C
C
D
Yes,
yeah
so
I'll
just
summarize
on
on
that
one
yeah,
so
Corey
I
mean,
if
you
want
it
to
be
supported.
Maybe
you
can
create
an
issue
on
the
channel
on
the
thing
but
as
as
David
said
they're,
the
main
problem
that
operator
fabric
is
solving
is
how
fast
you
can
do
it
rather
than
adding
more
complexity
but
yeah.
D
If
you
want
that,
you
can
always
use
use,
and
you
know
bevel,
which
has
support
for
faults,
but
as
I
was
saying
earlier
at
some
point,
we'll
integrate
bevel
and
bevel
operator
tablet.
So
bevel
will
use
developerative
fabric,
but
you
will
have
the
options
to
use.
You
know
the
original
bevel
or
the
operator
Fabric,
in
which
case
the
original
bevel
will
give
you
a
more
production
worthy
where
you
have
boiled,
and
all
that
secrets
you
know
or
secrets
are
managed
by
Vault
where
odd.
D
C
D
C
So
if
we
see
the
Inland,
then
we
have
here
all
of
the
components
employed.
There
is
one
both
per
component,
so
we
have
four
peers.
These
are
the
four
peers.
We
have
three
CS.
These
are
test
three
Cas
and
at
the
top
we
have
this
three
ordered
nodes.
So
this
is
the
status
so
now
we're
going
to
create
the
channel
line
for
this
and
for
the
following
main
Channel
and
for
the
follower
Channel.
We
need
to
create
the
identities,
so
we
need
to
create
first,
the
identity
for
the
order
of
MSP.
C
In
this
case,
there
is
a
small
difference
in
the
identity
related
because,
instead
of
being
the
plsca
and
the
instead
of
the
industry,
which
is
the
one
that
is
used
in
order
to
submit
transaction
in
case
of
using
the
channel
participation
API,
which
is
the
only
way
that
we
can
create
channels
in
hyper
life
audit
and
we
need
to
enroll,
it
is
in
the
tlsca
ca.
So
this
is
the
only
difference.
C
C
F
C
If
we
want
to
sit
in
depth,
you
have
the
meter
from
January
which
will
much
much
in
depth
into
Fabric
and
why
there
are
to
explain
the
commands
line.
Press
line
so
feel
free
to
do
that,
but
we
will
basically
get
the
organization
sign
certificate.
There
is
the
root
certificate
for
for
signing
and
other
certificates
for
the
for
the
notes,
which
is
a
dealer
certificate,
and
we
will
also
get
the
certificates
for
the
specific
orders.
This
is
for
the
consensus
for
the
consensus,
so
we
will
export
these
variables
and
then
we
will
keep
CTL
apply.
C
This
example
which
this
the
type
of
of
this
of
this
resource
is
found
main
Channel,
then
name
of
the
channel
is
demo.
These
are
the
admin
order,
organizations
that
means
their
organization,
so
basically
the
channel
will
be
created
so
that
only
decision
apples
from
this
organization
are
needed
in
order
to
change
the
configuration
or
add
another
member
to
this
organization
to
this
channel,
and
then
the
channel
form
field
which
has
a
you,
can
control
the
policies,
the
ecls.
This
is
not
usually
the
case,
but
you
can
look
into
modifying
this.
C
C
If
we
have
five,
then
we
can
just
create
all
the
rest
more
and
then
add
them
here.
So
let's
create
this.
If
there
is
any
expected
question
before
you
go
to
the
to
the
repository
and
then
raise
a
question
in
the
chat-
and
we
can
we
can
answer
it
later,
but
basically
we
create
the
crd
and
we
can
check
if
the
channel
has
been
created
using
this
command.
C
C
C
C
Then
we
will
see
that
there
are
blocks
here
and
belonging
to
the
demo
channel.
So
this
looks
good
so
right
now
we
will.
We
need
to
prepare
the
connection
stream
for
the
beer
and
we,
as
we
have
already
the
identities
we
can
create
Authority
level,
config
that
the
operator
will
use
this
aspect
in
order
to
create
a
valid
level
conference
to
be
used
by
the
qctl
Plugin
or
by
any
application
that
you
want
to
develop.
For
example,
node.js
go
Java,
Etc.
C
This
is
for
the
endpoints
in
this
case.
This
is
not
internal,
then
any
space
that
we
want
to
to
filter
in
this
place.
We
want
all
of
the
enemy
spaces
to
be
set
to
to
set
in
all
of
the
enemy
spaces
for
the
PSN
orders,
since
we
only
have
one
network
and
the
organization
that
we
want
to
be
added,
and
the
separate
name
will
be
the
second
name
that
will
create
the
predictor
and
we
can
apply
the
file
creating
this
we
can
see.
C
C
Okay,
let
me
delete
this
because
this
was
something
from
before
I
don't
know
if
there
will
be
any
problem
turning
this
now
for
the
test
cluster
that
was
used
before
for
a
network,
but
right
now
this
is
running
and
then
the
secrets
will
be
here.
So
this
is
the
number
one
thing
that
we
will
use
if
I
copied
well,
I
I
can
copy
the
best
whenever
I
want
and
also
I
can
use.
C
This
command,
which
is
here,
uctl,
gets
secrets,
and
then
we
will
pull
it
into
the
resources
Network
folder
and
then
we
can
go
to
the
network
jam
and
we
can
see
your
Quantum
XP
with
the
users
that
were
added
certificate,
private
key
and
the
pairs
of
the
organization.
So
this
is
a
level
config
that
you
can
use
in
your
application
in
order
to
connect
to
the
to
the
channel
and
execute
transactions.
C
So
right
now
the
status
is.
We
have
created
the
peers,
the
orders
CIS.
We
have
created
the
channel,
we
have
joined
the
peers,
the
channel
configured
and
configures
for
each
organization.
So
right
now,
what
we
want
to
do
is
deploy
the
chain
code
in
the
coordinates.
Cluster
install
the
chain
coding
in
each
of
the
peers,
approve
the
chain
code
for
its
organization
and
committed
income,
and
when
this
is
done,
one
of
these
steps
are
finished.
C
Then
we
will
need
to
test
the
chain
code
so
in
submit
a
transaction
and
query
the
the
network
in
order
to
refresh
to
interact
basically
with
the
with
the
chamber.
So
This
is
highly
technical,
but
this
is
this
step
is
to
create
a
metadata
file.
This
is
for
the
type
of
external
builder.
In
this
case,
we
will
use
the
thing
called
as
a
as
a
service
and
the
label
can
be
whatever
you
want.
C
We
will
execute
this,
so
they
will.
This
will
create
the
metadatization
and
prepared
the
population
files.
We
will
create
a
connection
Json.
This
thing
called
name-
and
this
this
address
will
be
the
one
that
the
PS
will
use
in
order
to
connect
to
the
chain
code,
and
it
will
not
use
TLS
in
this
case,
and
we
will
let's
execute
this
so
based
on
the
optimization.
We
will
create
the
code
that
they
said.
This
is.
C
Which
will
contain
the
connection
Json?
So
this
is
a
structure
the
fabric
needs
in
order
to
install
the
chain,
and
then
we
can
calculate
the
package
ID
using
a
helper
Fountain
from
from
the
cube
cctl
plugin,
and
this
it
will
be
the
package
ID
and
then,
after
this
we
can
install
the
chains
in
needs
of
appears.
We
will
need
to
secure
the
chain
code
for
four
times
one
fourth
spear,
and
we
can
run
this
copy
and
paste
in
everything.
C
And
then,
if
there
is
no
error,
then
this
means
that
everything
went
well.
There
is
a
question
that
the
Eduardo
Vasquez
is
asking
in
the
previous
Workshop.
You
created
the
network
config
file
a
different
way
with
the
CLI,
which
will
will
be
better
I
recommend.
Now
this
is
a
resource
that
was
other
than
1.9
I,
recommend
that
you
use
this
TRD,
because
you
can
automate
the
creation
of
the
Network
Conference
using
the
coin
filter
the
availability
which
previously
you
need
to
have
more
tools
locally.
So
this
is
right
now
in
the
place
that
we're
running.
C
This
is
how
we
are
managing
the
network
marketers
and
discuss
the
the
Improvement
that
this
is
refreshed
every
minute,
every
two
minutes
so
as
the
identities
are
also
refreshed,
so
this
ensure
that
you
have
a
network
config
with
with
valid
identities,
so
the
certificates
one
despite
so.
This
also
has
the
Improvement
about
the
the
certificate
automatic
certificate
renewable
or
after
this
answer
to
this
question,
we
have
installed
the
same
code
in
all
of
the
beers.
Then
we
need
to
build
the
image
in
this
case,
since
we
are
an
insulted
in
of
time.
C
The
image
is
already
built.
This
instructions
are
in
case
that
you
want
to
build
your
own
chain
code
and
then
use
the
same
code
in
order
to
deploy
it
and
run
your
own
use
case.
So
these
are
just
for
reference.
This
is
what
I
had
to
run
in
order
to
push
this
image,
but
this
is
already
in
the
in
the
docker
half,
so
nothing
to
Docker
build
to
run
the
soccer,
build
and
also
no
need
to
run
this
local
push
command.
C
Now
we
need
to
deploy
this
the
chain
code
in
the
quantities
cluster
and
the
reason
why
we
have
to
compute
the
product.
Id
is
because
the
single
needs
to
have
the
package
ID
for
the
organization,
so
we
will
need
to
deploy
it
with
the
package.
Id
the
replicas
and
the
name
will
be
the
thing
called
name
will
be
asset
in
this
case
and
then
space
will
be
default.
The
image
will
be
the
one
that
will
do
need
to
change.
C
If
you
want
to
deploy
a
custom
Tango,
so
we
can
go
back
to
lens
to
the
ports
and
we
see
that
the
asset
is
already
running.
Then
we
can
see
in
one
BR
they
think
of
that
are
installed.
You
can
run
this
for
any
beer
or
one
pr0
or
or
one
period,
one
so
feel
free
to
adjust
these
Scripts
you
as
you
need,
then
we
will
need
to
upload
the
think
of
for
the
organization
one.
Since
we
have
two
organization
and
the
majority
of
organizations
need
to
approve,
then
we
need
to
approve
for
both
organization.
C
C
Network
and
the
query
will
only
go
to
the
chain
code
and
gather
the
information
without
leaving
any
any
Trace.
So
when
you
want
to
store
an
information
that
you
need
to
use
in
bulk
in
this
case,
where
in
which
is
in
the
laser
The
Ledger.
So
since
we
want
this
data
to
be
persisted,
we
need
to
use
invoke.
So,
let's
delete
both.
C
All
of
the
assets
that
were
created,
so
these
are
the
Assets
in
this
case,
and
in
order
to
see
the
network
we
can
deploy
the
explorers
in
the
in
the
kubernetes
cluster.
The
API
cost
will
be
this
one
operator,
API
localhost.st.
This
will
be
the
Network
Conference
that
will
be
used.
This
will
be
the
visualization
mode
for
the
Explorer.
The
spirit
will
be
visualized,
based
on
the
policies
that
the
organization
one
has
foreign.
C
In
the
because,
if
we
want
to
then
and
see
network
config
in
the
current
cluster,
then
we
will
find
that
the
key
is
completely
damage.
You
can
create
your
own
secret
with
your
own
network
config
and
adjust
it
as
you
want,
and
then
the
HLF
user
of
this
network
conference
for
this
organization
for
organization
1
MSP
is
the
old
one
admin
default.
So
we
can
just
export
these
variables
and
we
can
create
the
operator
API.
C
This
is
needed
because,
in
order
to
reduce
the
deployment
components
because
before
the
the
operator,
API
and
operator,
UI
were
needed
so
right
now
there
is
only
well
one
one
company
which
is
operator
API.
That
has
a
website
embedded
in
that
in
the
in
the
image.
So
there
is
no
need
to
deploy
the
operator
UI,
because
this
is
already
in
place.
So.
C
C
C
C
and
you
can
in
the
best
screen
and
the
screen
that
gives
you.
The
status
of
the
network
is
these
channels
which
will
have
the
demo,
which
is
the
one
that
we
have
created
and
then
here
we
can
see
the
channel
demo
with
the
height
with
the
organization
with
the
other
organization,
with
the
channel
peers.
C
Also,
we
can
see
the
pairs
of
it,
the
height
of
each
of
the
pairs,
which
this
is
really
useful
in
order
to
receive
the
disappear
that
doesn't
have
connectivity
or
or
has
problems
in
order
to
patch
up
with
the
rest
of
the
peers,
and
we
can
see
the
tips
of
the
organization
have
two
beers,
Concord
beers
and
the
other
chemistry
has
further
and
much.
If
we
we
can
go
to
the
detail
of
the
organization
one
and
we
can
see
the
sign
certificates,
which
is
by
in
10
years,
on
The
Daily
certificates.
C
C
If
we
go
to
the
latest
one,
then
we
will
be
able
to
see
that
this
block
the
block
number
11.
We
need
to
understand
that
the
block
starts
with
zero.
So
even
though
we
have
a
height
of
12,
then
the
red
test
block
is
11,
but
because
it
will
start
with
zero.
This
is
the
has
of
the
block.
This
is
the
date
where
the
block
was
created,
and
these
are.
These
are
all
of
the
keys
and
values
that
were
created
with
this
transaction.
C
C
F
C
D
D
D
D
C
Basic,
the
basic
answer
will
be
so
what
you
want
to
do
is
recreate
the
physical
components
in
the
new,
the
new
cluster
or,
if
you're
on
a
Docker
then
create
according
to
this
cluster
and
create
the
physical
components,
the
pr
are
the
easiest
ones.
So
you
will
need
to
join
the
peers
to
the
previous
channel
in
order
for
them
to
catch
up.
This
will
be
the
first
part,
but
the
the
hardest
part
is.
C
D
D
F
D
H
C
C
D
C
D
I
think
it's
common,
and
the
answer
to
that
is
no
bevel
is
mainly
aimed
at
operators
who
would
or
mainly
also
aim
that
automation.
So
as
soon
as
you
keep
adding
console
and
UI
to
it,
you
cannot
you,
you
may
add
more
complexity
to
the
automation
tools,
so
so
to
be
asked
you.
The
short
answer
to
that
is
no.
We
we
have
supported
the
fabric
operations
console
to
some
because
fabric
already
did
it.
The
fabric
operations
console
adds
those
parameters
of
creating
fear
Etc.
D
D
Even
my
commands
are
from
bevel
you
use
batchel,
which
is
basically
what
operators
would
use
like
to
use,
and
it
is
also
much
easier
to
automate
them,
because
you
can
just
write
a
script
which
will
run
at
whatever
time
good
yeah
rather
than
sitting
on.
You
know
teaching
someone
how
to
browse
this
console:
yeah,
okay,
so
I'll
I'll
get
back
the
screen
share,
so
just
to
show
you
what
happened
on
my
side.
D
B
D
D
D
So
Flex
again,
as
you,
we
heard
about
an
operator
so
yeah
flux,
flux,
installs,
a
lot
of
different
operators,
so
same
thing
has
happened
here,
so
we
have
different
operators
which
are
running
and
then
gradually
the
the
bevel
system
start
running.
So
we
first
have
the
Vault
kubernetes
job
so
that
the
main
purpose
of
this
job
is
to
create
the
connection
between
kubernetes
and
Vault,
so
that
you
can
talk
to
kubernetes
talk
from
kubernetes
to
Vault
and
vice
versa.
D
Okay,
because
quality
is
supposed
to
be
secure
and
and
you
you
not,
everyone
should
have
access
to
Vault
right
after
that.
You
have
the
ca
certificates,
because
we
are
deploying
the
assertive
CA
CS.
So
you
we
create
a
job
which
will
create
the
ca
certificates
so
that
job
then
stores
the
certificates
into
the
vault.
Then
the
ca
servers
are
running.
So
these
are
the
servers,
as
you
see,
they're
green.
So
that
means
they're
running
and
then
we
have
the
ca
tools.
D
So
basically,
this
is
the
like
the
Pod
we
are,
we
are
providing,
which
does
all
the
crypto
generation
using
all
the
commands
that
you
would
use.
So
all
the
certificates,
the
user
registration,
similar
to
what
what
David
showed
with
with
the
cube
CTL
HLF
commands.
So
you
do
the
user,
registration
and
all
and
and
then
all
the
the
only
difference
in
this
case
is
that
all
the
ca
tool
is
once
there
the
subject
is
get
generated.
They
get
taught
again,
they
get
stored
into
vault.
D
So
if
you
delete
them,
that's
also
fine
and
this
point
I
just
added
another
AWS
node
but
yeah
again.
Yeah
then,
after
that,
it's
just
the
peers
that
have
started
running
so
peer
manufacturer
supply
chain
which
is
ordered
and
and
the
carriers
here
and
then
once
that
is
once
the
PA
started
running.
Then
we
we
have
the
channel
creation
and,
as
David
kind
of
said,
like
we
have
the
main
person
main
organization
which
creates
the
channel.
D
So,
for
example,
in
this
this
scenario
carrier
net
created
the
channel
and
then
they
both
joined
the
channel
through
these
jobs.
So
these
are
jobs
or
which
which
run,
and
then
we
also
had
PR
CLI
for
manufacturer
as
true
enable,
so
the
pr
CLI
was
installed
and
then
we
have
the
anchor
peer
set
up.
So
basically
that
means
the
anchor
Pier
was
added.
D
So
if
you
see
the
logs
from
the
orderer
and
all
that
so
yeah,
you
can
see
that
the
all
channel
was
added
here,
I
mean,
and
this
this
edit
is
because
the
joiners
were
not
added
but
yeah.
You
can
see
that's
the
whole
Channel
added
this
and
then
on
the
pier
0.
So
first,
so
this
is
for
Carrier.
So
after
the
anchor
peers
were
added,
then
the
membership
view
on
the
all
channel
was
changed
and
it
was.
D
Yeah,
so
if
you
see
the
same
thing
and
then
manufacturer
can
see
the
other
peer
which
is
pr0,
so
that's
the
summary
and
then
if
I
was
trying
to
see,
if
there's
any
answer,
no
question
here,
no
going
back
to
what
all
things
other
things
you
can
do
via
bevel
with
fabric
is
this
is
here
so
you
can
upgrade
the
fabric
question.
You
can
upgrade
a
running
fabric
from
1.4
X
to
2.2
x.
You
can
add
a
new
organization,
you
can
add
a
new
order
or
organization.
D
If
you
want
to
you,
know,
add
separate
kubernetes
cluster
with
the
order
organization,
you
can
create
new
channel.
Definitely
you
can
remove
an
organization,
but
removing
an
organization
of
course
means
you
should
have
agreement
with
all
the
other
organizations,
but
Max
I.
Think
it's
a
it's
a
vote
kind
of
thing.
Then
you
have
a
you
can
add
a
new
peer
to
an
existing
organization.
You
can
add
just
another
raft
order
to
an
existing
organization
order.
D
Just
adding
the
CLI.
You
can
add,
install
chain
code,
basically
both
1.4
and
2.2
versions.
You
can
upgrade
a
chain
code
and-
and
you
can,
as
I
said
you
can
deploy
in
a
fabric
operations
console
you
can
refresh
certificates
separately
by
one
Playbook,
and
this
I
already
said
you
can
deploy
fabric
the
cactus
connector,
though
the
cactus
connector
itself
has
that
effect.
So
we
are
not
able
to
successfully
test
it,
but
you
can
still
deploy
the
version
of
cactus
connector
and
then
you
can
also
deploy
the
external
chain
code
using
beverage
right.
D
C
D
Yeah
right
yeah,
so
I'm
going
back.
Okay,
it's
going
to
the
second
question,
always
about
the
ca
server.
Yes,
the
fabric,
CA
server
is
not
supposed
to
be
used
for
production
workloads,
so
we
have
not
tried
ourselves
with
a
generic
guess
server,
which
is
like
provided
by
AWS,
or
you
know,
deploying
your
own
CS
server.
So
basically,
the
idea
is
that
you
should
deploy
with
your
own
CA
server
and
it
should
have
the
MSP
kind
of
configuration.
D
So
not
aware
of
this
thing
right
so
yeah.
So
if
you
go
to
the
if
I
opening
Vault
once
the
vault
is
deployed
all
the
ones,
everything
is
completed
in
the
secrets,
V2
and
when
sewage
is
created,
this
was
empty.
Now
you
have
all
the
secrets
in
order
organizations
and
supply
chain.
So
this
is,
for
example,
this
is
the
Genesis
block
and
then
under
this,
these
are
the
certificate.
The
ca
servers
public.
You
know
certificate
and
key,
and
then
you
have
the
users
MSP
details.
You
know
all
the
admin
search.
D
All
things
are
here.
So
if
you
want
to
copy
or
download
for
an
application,
for
example,
especially
the
admin
user,
you
can
you
can
use
Vault,
CLI
or
even
Vault
tape.
You
all
provides
API
access
as
well
to
download
these
certificates
in
your
application
yeah.
So
that's
the
question
in
the
rest
server.
D
You
can
use
I'm
sure
there
would
be
packages
where
you
can
use
Vault
server
and
pass
the
details
of
this
Vault
and,
and
the
you
know
token,
as
some
kind
of
secret,
so
that
it
can
download
these
using
the
apis
and
that's
what
bevel
also
does
anyway.
So
bevel
for
all
these
all
these
boards,
which
which
are
running
if
you,
if
I,
do
this,
so
this
is
the
certificates
init
part,
as
you
can
see
it,
it
runs.
It
gets
this
using
the
apis.
D
F
D
It's
there
there
is
a
step.
Basically,
there
is
a
separate
Playbook
which
will
reference
the
certificates
and
backing
to
back
to
this.
Using
you
know,
your
question
I
think
David
answered
it,
that
you
can
do
that.
But,
as
we
already
discussed,
the
UI
is
not,
you
know
100
and
we
don't
test
it
as
well.
So
it
may
may
work
and
may
not
work
as
well.
So
we
we
don't
and
we
are
more
focused
on
providing
the
CLI
versions
or
working
on
the
CLI
versions
of
both.
C
D
So
on
fabric
2.5,
yeah,
I,
think
will
be
supported
in
we
have
started
a
spike
if
anyone
wants
to
help
here
they
can,
but
we
just
started
a
spike
where
we
want
to
explore
what
is
fabric,
what
are
the
differences
between
fabric
2.2
and
2.5
and
how
it
will
impact
bevel
and
then
we'll
create
the
stories
for
those
differences.
If
there
are
not
major
differences,
it
will
be
a
smaller.
It
will
be
earlier
available.
Sooner
than
later,.
D
D
Oh,
going
back
to
the
fabric
person
support
for
bevel
to
we
as
I
keep
on
saying
that
if
you
are
not
using
if
there
is
no
major
changes,
if
the
generic
I
think
fabric
is
generally
backwards
compatible,
so
if
you're
not
using
specific
features
of
fabric
2.4,
if
you
just
update
that
2.2.2
to
2.4
point
x,
I,
don't
use
x,
Gap
some
real
versions,
it
should
work
yeah,
the
recording
will.
Is
there
already
there
on
YouTube,
so
you
don't
have
to
wait
for
the
recording.
D
D
No
raft
leader
I'm
not
exactly
sure
what
you
mean
by
that
like
you
can
create
you
I
mean
you
can
definitely
create
three
orders
with
raft.
Consensus,
I
think
David
showed
how
to
create
on
on
that
and
an
Endeavor.
You
just
add
in
the
network
ml.
Add
multiple
orders
in
the
orders
under
the
auditor
organization.
C
D
C
This
was
meant
to
be
support
that
the
reason
why
we
have
the
customer
exploited
for
fabric
is
because
this
flooded
project-
and
this
is
my
opinion-
is
a
which
is
great
because
it's
for
multiple
blockchain
networks,
but
it's
not
tailored
for
firing.
For
example,
you
don't
have
the
option
to
see
the
private
data
in
the
in
the
transaction
in
the
Explorer,
which
is
which
many
use
cases
rely
on
private
data.
So
this
is
something
that
is
not
in
the
Block.
It's
in
each
of
the
beers
and
the.
D
All
right,
I
think
that's
all
thanks
everyone.
We
love
the
participation
and
and
the
questions.
Definitely
some
great
questions
but
yeah
I
know
people
didn't
put
on
this
card,
but
you
can
always
come
back
on
Discord.
We
have
those
two
separate
channels
and
also
the
workshop
Channel.
If
you
need
to
need
some
help
again
on
the
workshops,
Shop
Channel,
please
come
back
there
and
ask
your
questions.
D
It's
not
a
video
answer
or
you
know
you
don't
have
to
wait
for
the
whole
video
to
complete
to
get
an
answer,
but
yeah,
please
feel
free
and
please
use
both
of
them
and
as
if
you,
as
we
already
said
for
some
of
the
issues,
if
you
think
that
that
any
feature
would
be
great
for
that,
you
can
add
them
as
an
issue.
Of
course
we
can
do
the
triage
when
if
we
need
more
details
or
more,
you
know
how
to
do
it.
D
We
can
realize
that
issue,
but
if,
if
that's
also
one
way
of
participating
in
an
open
source
that
you
can
submit
a
issue,
it
doesn't
have
to
be
always
good,
of
course,
go
if
you,
if
you
already,
are
working
on
something
and
you
think
that
is
a
good
fit
you
can.
You
can
create
the
issue
and
then
submit
the
pr
as
well.
So
that's
that's
the
best
way,
anyways
and
yep.
That's
all
thanks.