
在本课程中,您将学习在 Kubernetes 上设计和部署 Hyperledger Fabric 应用程序。本课程专为那些寻求在 Kubernetes 上学习超级账本结构部署的人设计。在课程结束时,您将能够在任何云上设计、开发和部署您的超级账本结构网络,因为我们使用了与云无关的方法。本课程完全是实践性的,我们将更多地关注实践方法而不是理论。
你将从本课程中学到什么
在课程结束时,您将能够在 Kubernetes 上设计、开发和部署您的超级账本结构应用程序。您将学习以下内容
创建 Kubernetes 集群
设置 NFS 服务器
启动 Fabric CA 服务器
为 peers 和 orderer 生成证书
创建诸如创世块、通道交易和锚点等工件
创建应用通道
加入申请渠道
配置节点以使用外部链码构建器
启动对等节点
根据外部链码构建器设置打包链码
在 Kubernetes 中启动链码作为服务
批准链码
提交链码
调用和查询事务。
设置 REST API 服务器
通过 Angular 设置前端应用程序构建
Hyperledger Explorer 集成
使用 Prometheus 和 Grafana 启用 Hyperledger Fabric 监控
设置入口控制器和域配置。
借助 cert-manager 和 Let’s encrypt 在 Kubernetes 上启用 SSL
Hyperledger Fabric 部署的多种方式
由于 Hyperledger Fabric 组件被部署为容器,因此在本地主机中运行时一切正常。当它们运行在不同的主机上时,我们需要找到一种方法让这些容器相互通信。
静态IP 通过指定运行容器的主机IP,容器之间可以相互通信。这些主机 IP 是使用 docker-compose 文件中的 extra_hosts 指定的,并且在容器运行后,可以在 etc/hosts 中看到这些条目。缺点是事物是静态配置的,当需要添加或更改配置时会遇到挑战。
Docker Swarm Docker Swarm 是 Docker 环境中原生的容器编排工具。简而言之,它为跨多个主机的容器提供了一个覆盖网络。这个覆盖网络上的那些容器可以相互通信,就像它们在一台大型主机上一样。显然,好的一面是可以使用原始配置,只需很少的修改,并且配置中没有编码IP等静态信息。
Kubernetes (k8s) K8s 是迄今为止最流行的容器编排工具。该机制类似于 Docker Swarm。这种方法的实现比前两种机制更具挑战性,但这种方法更具可扩展性,并且是 Hyperledger Fabric 团队推荐的。
Genre: eLearning | MP4 | Video: h264, 1280×720 | Audio: AAC, 48.0 KHz
Language: English | Size: 2.46 GB | Duration: 5h 59m
Deploy Hyperledger Fabric on Kubernetes
What you’ll learn
Design Hyperledger Fabric Network
Working with Kubernetes
Hyperledger Fabric on Kubernetes
Description
In this course, you will learn to design and deploy Hyperledger Fabric applications on Kubernetes. This course is specifically designed for those seeking to learn hyperledger fabric deployment on Kubernetes. By the end of the course, you will be able to design, develop and deploy your hyperledger fabric network on any cloud, since we have used the cloud-agnostic approach. This course is completely hands-on and we will be focusing more on the practical approach rather than the theoretical.
What you will learn from this course
By the end of the course, you will be able to design, develop and deploy your hyperledger fabric application on Kubernetes. You will learn the following things
Creating Kubernetes cluster
Setting up NFS Server
Starting up Fabric CA Server
Generating certificates for peers and orderers
Creating artifacts like genesis block, channel transaction, and anchor peers
Creating application channel
Joining application channel
Configuring peers to use external chaincode builder
Starting up peer nodes
Packaging chaincode as per external chaincode builder settings
Starting up chaincode as service in Kubernetes
Approving chaincode
Committing chaincode
Invoking and querying transactions.
Setting up REST API Server
Setting up Frontend Application build over Angular
Hyperledger Explorer Integration
Enabling Hyperledger Fabric Monitoring using Prometheus and Grafana
Setting up an ingress controller and domain configuration.
Enabling SSL on Kubernetes with the help of cert-manager and Let’s encrypt
Various Ways for Hyperledger Fabric Deployment
As Hyperledger Fabric components are deployed as containers, everything works fine when running in the localhost. When they are running in different hosts, we need to find a way to make these containers talk to one another.
Static IP By specifying the host IP where a container is running, containers can communicate with each other. Those host IPs are specified using extra_hosts in docker-compose files, and after a container is running, these entries are seen in, etc/hosts. The downside is that things are statically configured, and there are challenges when one needs to add or change the configuration.
Docker Swarm Docker Swarm is a container orchestration tool natively in the Docker environment. In a nutshell, It provides an overlay network for containers across multiple hosts. Those containers on this overlay network can communicate to one another as if they were on a large host. Obviously, the good side is that the original configuration can be used with minimal modification, and no static information such as IP is coded in the configuration.
Kubernetes (k8s) K8s by far is the most popular container orchestration tool. The mechanism is similar to Docker Swarm. The implementation of this approach is much more challenging than the previous two mechanisms but this approach is much more scalable and recommended by the Hyperledger Fabric team.
原创文章,作者:steven,如若转载,请注明出处:https://rr3d.cn/13838.html