Hyperledger Fabric Network Controller Automation in Kubernetes

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing methods for creating a Hyperledger Fabric network are either inconvenient due to the need for script writing or require high development costs and resource allocation for backend service development.

Innovation Solution

A method utilizing a configuration file and a preset state machine to automate the deployment of a Hyperledger Fabric network in a Kubernetes cluster, eliminating the need for manual script writing and backend service development.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Extent of automation

If manual script writing is used to deploy Fabric network components, then automation is achieved, but user convenience deteriorates due to the need to learn script writing

Engineering Contradiction:

Improveautomation of network deploymentVSAvoiduser convenience

Core Design Contradiction:

Extent of automationVSEase of operation

Solution Approach 1:

The patent introduces a controller as an intermediary between the user and the complex deployment process. The controller receives high-level commands from the user and automatically translates them into the necessary deployment actions, eliminating the need for users to learn scripting while maintaining automation.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The system enables self-service deployment where the controller automatically manages the entire deployment process without requiring user intervention in the technical details. The controller autonomously creates components, manages dependencies, and handles the deployment sequence based on user-defined configuration.

Inventive Principle:

Principle #25Self-service

2Ease of manufacture

If a backend service is developed to create Fabric network in Kubernetes, then deployment capability is achieved, but development cost and resource occupation increase

Engineering Contradiction:

Improvedeployment capabilityVSAvoidbackend service development

Core Design Contradiction:

Ease of manufactureVSDevice complexity

Solution Approach 1:

The controller is designed as a universal deployment tool that can create various Fabric network components (orderers, peers, CAs, MySQL databases) through a unified interface. This multi-functional approach eliminates the need for separate backend services for each component type, reducing overall system complexity.

Inventive Principle:

Principle #6Universality (Multi-functionality)

Solution Approach 2:

Instead of developing a complete backend service from scratch, the patent uses Kubernetes operators and existing cluster resources to replicate the deployment functionality. The controller leverages Kubernetes' native capabilities (Pods, Services, ConfigMaps) to achieve deployment without requiring custom backend service development.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS11307849B2Method for creating hyperledger fabric network, controller and storage medium

Publication Date: 2022.04.19 BEIJING BAIDU NETCOM SCI & TECH CO LTD

AI summary

Embodiments of the present disclosure relates to the field of block chain technology, and provides a method for creating a Hyperledger Fabric network, a controller and a storage medium. The method may include: acquiring a configuration file required to create a Hyperledger Fabric network in a Kubernetes cluster; and creating the Hyperledger Fabric network in the Kubernetes cluster according to the configuration file and a preset state machine. Embodiments of the present disclosure are applicable to the procedure of creating the Hyperledger Fabric network.