CN114172804A - Alliance chain separation deployment method, system, medium and electronic device - Google Patents
Alliance chain separation deployment method, system, medium and electronic device Download PDFInfo
- Publication number
- CN114172804A CN114172804A CN202111461192.2A CN202111461192A CN114172804A CN 114172804 A CN114172804 A CN 114172804A CN 202111461192 A CN202111461192 A CN 202111461192A CN 114172804 A CN114172804 A CN 114172804A
- Authority
- CN
- China
- Prior art keywords
- network
- configuration file
- chain
- baas
- network configuration
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 37
- 238000000926 separation method Methods 0.000 title claims abstract description 30
- 230000008520 organization Effects 0.000 claims description 30
- 230000006870 function Effects 0.000 claims description 21
- 230000006835 compression Effects 0.000 claims description 6
- 238000007906 compression Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012544 monitoring process Methods 0.000 claims description 3
- 238000012795 verification Methods 0.000 claims description 3
- 230000000873 masking effect Effects 0.000 claims 1
- 230000008569 process Effects 0.000 description 5
- 230000004044 response Effects 0.000 description 5
- 238000010586 diagram Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 2
- 241000109539 Conchita Species 0.000 description 1
- 241000212333 Perideridia Species 0.000 description 1
- 230000006978 adaptation Effects 0.000 description 1
- 230000002708 enhancing effect Effects 0.000 description 1
- 239000004744 fabric Substances 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44505—Configuring for program initiating, e.g. using registry, configuration files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
- H04L41/084—Configuration by using pre-existing information, e.g. using templates or copying from other elements
- H04L41/0843—Configuration by using pre-existing information, e.g. using templates or copying from other elements based on generic templates
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
- H04L67/1059—Inter-group management mechanisms, e.g. splitting, merging or interconnection of groups
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45562—Creating, deleting, cloning virtual machine instances
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/4557—Distribution of virtual machine instances; Migration and load balancing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer And Data Communications (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a method, a system, a medium and electronic equipment for alliance chain separation deployment, which specifically comprise the following steps: when the container cloud platform does not obtain the k8s right, the network cannot be created directly through k8s, and a federation chain network is created by adopting a separated deployment mode, wherein the federation chain network comprises the following steps: uploading the network configuration file to BaaS, calling an interface for generating a k8s resource configuration file, and finishing the creation of the k8s resource configuration file by the server according to the network configuration file; taking the returned network ID and the k8s instance IP as parameters, and calling an interface for starting a chain code; and the BaaS starts the chain code and creates a alliance chain network. So far, deployment of the alliance chain network is completed under the scene that the container cloud platform is separated from the k8 s; meanwhile, in order to ensure information security, in the separated deployment mode, the access right of the user is adjusted, and the related request depending on the k8s is limited.
Description
Technical Field
The invention relates to the technical field of block chains, in particular to a federation chain separation deployment method, a federation chain separation deployment system, a federation chain separation deployment medium and electronic equipment.
Background
Kubernetes (hereinafter referred to as k8s) is an open source platform for automatic container operation, and block chain nodes can be better managed and the availability of the nodes can be improved by deploying a block chain network through k8 s. The k8s provides the functions of flexible resource scheduling, strong operation and maintenance management, easily-expanded micro-service architecture, convenient cloud platform integration and the like for the blockchain. In addition, for the federation chain, the k8s also has the capability of multi-tenancy, namely, a plurality of Fabric instances isolated from each other can be run, and the management of the federation chain is facilitated.
When a technician deploys a alliance chain network, the container cloud platform is used for acquiring the k8s authority and the network is directly created through k8s, but if the container cloud platform does not acquire the k8s authority, the network cannot be directly created through k8s, so that a solution for creating the alliance chain network is urgently needed when the container cloud platform does not acquire the k8s authority.
Disclosure of Invention
The invention aims to solve the problem that in the prior art, when a container cloud platform does not obtain the authority of k8s, a network cannot be created directly through k8s, and provides a federation chain separation deployment method, a federation chain separation deployment system, a federation chain separation deployment medium and electronic equipment.
In order to achieve the above object, the present invention provides a federation chain separation deployment method, which specifically includes:
initializing BaaS;
responding to a request for organizing a split deployment alliance link network, acquiring a network configuration file, and reading network configuration information, wherein the network configuration file is stored in a readable directory of the BaaS;
checking an organization CA, checking port conflict, and acquiring organization information of the organization;
creating a k8s client based on the network configuration information, initializing, and constructing a creating block;
acquiring a path of the network configuration file in the BaaS and a k8s instance IP of the k8s client, calling an interface for generating a k8s resource configuration file in a separated deployment mode by using the path of the network configuration file in the BaaS and the k8s instance IP as parameters, creating a k8s resource configuration file, and returning a network ID;
calling an interface for starting a chain code by taking the network ID and the k8s instance IP as parameters;
and the BaaS starts the chain code and creates a alliance chain network.
Further, the step of initializing BaaS includes: defining a deployment mode in the application configuration file of the BaaS, defining the deployment mode as a separated deployment mode in an initialization function of the application main file of the BaaS, and starting the BaaS;
the deployment mode comprises a separated deployment mode and a non-separated deployment mode.
Further, the step of creating a k8s resource configuration file and returning a network ID specifically includes: and creating a resource object, generating and compressing the k8s resource configuration file based on the resource object to obtain a k8s resource configuration file compression package, returning the compression package, and returning the network ID.
Further, the step of BaaS starting the chain code and creating the alliance chain network specifically includes: inquiring the network configuration information based on the network ID, initializing a chain code and an initialization channel based on the network configuration information, acquiring organization information of the organization and node information of a node where the organization is located, uploading the organization information and the node information to the channel, adding the organization and the node into the channel, synchronizing cross-network configuration, starting chain code monitoring, and completing creation of a alliance chain network.
Further, after the creation of the federation chain network is completed, the method further includes: in the separate deployment mode, shielding access rights to a part of functions in the alliance chain network specifically includes: and setting the identifier of the deployment mode in the function authority table as a separate deployment mode, wherein the access authority of the part of functions is the shielded authority and is not returned.
Further, the partial functions include: the method comprises the steps of managing network instance configuration information, adding network configuration information, editing network configuration information, deleting network configuration information, checking network configuration information, joining a network, creating a network, uploading configuration information, editing cross-network configuration, stopping nodes and starting nodes.
Further, after the step of shielding the access right to part of the functions in the alliance-link network, the method further comprises the following steps:
for the operation of acquiring the k8s used port, set to return error;
for the operation of obtaining the node state, setting to return running;
for the operation of checking the details of the network configuration information, the method is set to return an empty character string.
Further, logically, the partially overlapping of the detached deployment mode and the original un-detached deployment mode includes:
under the non-separated deployment mode, uploading a network configuration file, creating the first half part of the alliance chain network and creating the second half part of the alliance chain network;
in the separated deployment mode, the process of generating the k8s resource configuration file corresponds to the uploading of the network configuration file in the non-separated deployment mode and the creation of the first half of the alliance link network; in the separation deployment mode, after the k8s resource configuration file is successfully created, the returned network ID and the k8s instance IP are used as interfaces for parameter call of a startup chain code, and the latter half of the alliance chain network is created in the non-separation mode correspondingly.
Correspondingly, the invention also provides a federation chain separation deployment system based on k8s, which comprises: the system comprises an application initialization module, an acquisition module, a verification module, a client creation module, a resource configuration file creation module and a chain code starting module;
the application initialization module initializes the BaaS;
the acquisition module is used for responding to a request for organizing and separately deploying a alliance link network, acquiring a network configuration file and reading network configuration information, wherein the network configuration file is stored in a readable directory of the BaaS;
the checking module is used for checking CA configuration, checking port conflict and acquiring organization information of the organization;
a client creating module, which creates a k8s client based on the network configuration information and initializes the client to construct a creating block;
a create resource profile module: acquiring a path of the network configuration file in the BaaS and a k8s instance IP, calling an interface for generating a k8s resource configuration file in a separate deployment mode by using the path of the network configuration file in the BaaS and the k8s instance IP as parameters, creating a k8s resource configuration file, and returning a network ID;
a starting chain code module, which takes the network ID and the k8s instance IP as parameters and calls an interface for starting chain codes; and the BaaS starts the chain code and creates a alliance chain network.
Accordingly, the invention also provides a computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method steps of any of the above.
Accordingly, the invention also provides an electronic device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, which computer program, when executed by the processor, performs the method steps of any of the above.
Compared with the prior art, the container cloud platform adopts a k8s separated deployment mode, and technical personnel independently write a network configuration file, create a k8s resource configuration file and call a related interface of the container cloud platform to create the alliance chain network, so that the problem that the alliance chain network cannot be deployed in a scene where the container cloud platform is separated from k8s due to the fact that the container cloud platform does not have k8s permission is solved. Meanwhile, under a k8s separated deployment mode, the access authority of users in the network is adjusted, the related requests depending on k8s are limited, and the information safety during separated deployment is ensured.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings without creative efforts.
Fig. 1 is a schematic diagram of a separation deployment process in a specific embodiment of a federation chain separation deployment method of the present invention.
Fig. 2 is a schematic flow chart of generating a k8s resource configuration file in the embodiment of the federation chain separation deployment method of the present invention.
Fig. 3 is a schematic diagram of a chain code starting process in an embodiment of a federation chain separation deployment method of the present invention.
Detailed Description
To make the objects, technical solutions and advantages of the embodiments of the present invention clearer, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings, and it is apparent that the described embodiments are some, but not all embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
In the description herein, references to the description of "an embodiment," "a particular embodiment," "an embodiment," "for example," mean that a particular feature, structure, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the application. In this specification, the schematic representations of the terms used above do not necessarily refer to the same embodiment or example. Furthermore, the particular features, structures, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples. The sequence of steps involved in the embodiments is for illustrative purposes to illustrate the implementation of the present application, and the sequence of steps is not limited and can be adjusted as needed.
In order to better understand the technical content of the present invention, some words in the industry mentioned in the specification are explained as follows, including: BaaS (Block chain as a service) is a block chain, namely a service platform, provides a convenient and high-performance block chain ecological environment and ecological matching service for developers, and supports the business expansion and operation of the developers; k8s (kubernets) is an open source platform for automated container operation that can be used to deploy blockchain networks; the ca (verification authority) is used for providing a digital certificate (i.e. a server certificate, which is composed of a domain name, a serial number, signature information, and the like) and digital certificate operation and maintenance related services, and enhancing the security of information interaction between a server and a client; the created block is the earliest constructed block in the blockchain network, i.e., the first block.
In a specific embodiment, when a federation chain network is deployed through a container cloud platform, the federation chain network includes two modes of separated deployment and non-separated deployment, and in the non-separated deployment mode, the container cloud platform already obtains a k8s right and is directly connected to a k8s service through a k8s client to create the federation chain network; in the separate deployment mode, the container cloud platform does not acquire the k8s right, and when the k8s client is created, the container cloud platform cannot be connected to the k8s service.
In this embodiment, when an organization deploys a federation chain network, the container cloud platform does not obtain the k8s authority, so that a k8s separate deployment mode is selected; the organization sending out the request for deploying the alliance chain network is the initiative organization of the alliance chain network.
Fig. 1 shows a schematic diagram of a separation deployment process based on k8s in the present invention, and this embodiment implements a federation chain separation deployment method based on k8s as shown in fig. 1, and the specific implementation steps include:
s1, initializing BaaS: specifically, a deployment mode is defined as a separate deployment mode in the application configuration file of the BaaS, and the BaaS is started; wherein, defining a deployment mode as a separate deployment mode in the application configuration file of the BaaS specifically includes: defining a deployment mode as a separate deployment mode in an initialization function of an application master file of the BaaS, and starting the BaaS;
s2, generating a k8S resource configuration file: responding to a request for organizing a split deployment alliance link network, acquiring a network configuration file, and reading network configuration information, wherein the network configuration file is stored in a readable directory of the BaaS;
checking CA configuration, checking port conflict, and acquiring organization information of the organization;
creating a k8s client based on the network configuration information, initializing, and constructing a creating block;
acquiring a path of the network configuration file in the BaaS and a k8s instance IP, calling an interface for generating a k8s resource configuration file in a separate deployment mode by using the path of the network configuration file in the BaaS and the k8s instance IP as parameters, creating a k8s resource configuration file, and returning a network ID;
s3, start chain code: calling an interface for starting a chain code by taking the network ID and the k8s instance IP as parameters;
and the BaaS starts the chain code and creates a alliance chain network.
In this embodiment, the network configuration file is written autonomously by a technician.
On the one hand, the deployment modes described in S1 are divided into two modes, i.e., a separated deployment mode and a non-separated deployment mode, and the present embodiment is performed in a case where the deployment mode is set to the separated deployment mode.
On one hand, the specific implementation flow of generating the k8S resource configuration file is shown in fig. 2, where the step of creating the k8S resource configuration file and returning the network ID in S2 specifically includes: and creating a resource object, generating and compressing the k8s resource configuration file based on the resource object to obtain a k8s resource configuration file compression packet, returning the k8s resource file compression packet, and returning the network ID.
On the one hand, the IP of the k8s instance means: when the k8s cluster runs on a public cloud, a corresponding load balancer instance is automatically created, and the IP of the load balancer instance is returned for external access, wherein the IP is the IP of the k8s instance.
On one hand, a specific implementation flow of the chain code is shown in fig. 3, where the step of creating a federation chain network by using the BaaS chain code in S3 includes: inquiring the network configuration information based on the network ID, initializing a chain code and an initialization channel based on the network configuration information, acquiring organization information of the organization and node information of a node where the organization is located, uploading the organization information and the node information to the channel, adding the organization and the node into the channel, synchronizing cross-network configuration, starting chain code monitoring, and completing creation of a alliance chain network.
In this embodiment, after the creation of the federation chain network in the split deployment mode is completed, in order to ensure information security during split deployment, adjust access permissions of users in the network, and limit related requests depending on k8s, access permissions of users in the federation chain network to part of functions need to be shielded, the specific method is as follows:
adding an identifier of a deployment mode in a function authority table of a database, wherein the identifier of the deployment mode comprises a separated deployment mode and a non-separated deployment mode; setting the identifier of the deployment mode in the function authority table as a separate deployment mode, setting the access authority of the partial functions as shielded authority, increasing the judgment of the deployment mode when a user accesses the partial functions, and if the identifier of the deployment mode in the function authority table is the separate deployment mode, not returning. Wherein the partial functions include: the method comprises the steps of managing network instance configuration information, adding network configuration information, editing network configuration information, deleting network configuration information, checking network configuration information, joining a network, creating a network, uploading configuration information, editing cross-network configuration, stopping nodes and starting nodes.
After the step of shielding the access right to part of the functions in the alliance-link network, the method further comprises the following steps:
for the operation of acquiring the k8s used port, set to return error;
for the operation of obtaining the node state, setting to return running;
for the operation of checking the details of the network configuration information, the method is set to return an empty character string.
In addition, in terms of code logic, the separation deployment mode uses the original non-separation deployment mode for reference, and has partial coincidence with the non-separation deployment mode, and the method comprises the following steps:
under the non-separated deployment mode, uploading a network configuration file, creating the first half part of the alliance chain network and creating the second half part of the alliance chain network;
in the separated deployment mode, the process of generating the k8s resource configuration file corresponds to the uploading of the network configuration file in the non-separated deployment mode and the creation of the first half of the alliance link network; in the separation deployment mode, after the k8s resource configuration file is successfully created, taking the returned network ID and k8s instance IP as interfaces for parameter call of a starting chain code, and correspondingly creating the second half of the alliance chain network in the non-separation mode;
note that in the separate deployment mode, the creation block is constructed after the k8s client is created and initialized, and before the k8s resource configuration file is generated; and under the original non-separated deployment mode, establishing the creation block is carried out before initializing the chain code.
In this embodiment, the operations of generating the k8s resource configuration file, creating and starting the chain code performed at the front end are as follows:
1) generating a k8s resource configuration file;
the interface is defined as/separate/export K8sYaml, and the parameter types include network configuration file path and k8s instance IP, as follows:
1.{
"yampah"/home/centros/nfs _ data/create. yaml "// network profile path
3."k8s _ ends" [ "192.128.11.102", "192.168.11.183" ]// k8s example IP
4.}
When the creation is successful, the file is returned, no response message exists, and when the creation is failed, the error information is returned, as follows:
1.{
"code": 9016 "// response code
Message parameter illegal/response message
4.}
2) Creating chain codes
The interface is defined as/separate/setup public chain, and the parameter types include network ID and k8s instance IP
1.{
"config _ ID": 123456 "// network ID
3."k8s _ ends" [ "192.128.11.102", "192.168.11.183" ]// k8s example IP
4.}
Start chain code, no reply message, as follows:
1.{
"code": 200 "// response code
"message"// response message
4.}
Other embodiments of the present disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This specification is intended to cover any variations, uses, or adaptations of the specification following, in general, the principles of the specification and including such departures from the present disclosure as come within known or customary practice within the art to which the specification pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the specification being indicated by the following claims.
It will be understood that the present description is not limited to the precise arrangements that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof, which is limited only by the claims appended hereto.
Claims (10)
1. A federation chain separation deployment method is characterized by specifically comprising the following steps:
initializing BaaS;
responding to a request for organizing a split deployment alliance link network, acquiring a network configuration file, and reading network configuration information, wherein the network configuration file is stored in a readable directory of the BaaS;
checking an organization CA, checking port conflict, and acquiring organization information of the organization;
creating a k8s client based on the network configuration information, initializing, and constructing a creating block;
acquiring a path of the network configuration file in the BaaS and a k8s instance IP, calling an interface for generating a k8s resource configuration file in a separate deployment mode by using the path of the network configuration file in the BaaS and the k8s instance IP as parameters, creating a k8s resource configuration file, and returning a network ID;
calling an interface for starting a chain code by taking the network ID and the k8s instance IP as parameters;
and the BaaS starts the chain code and creates a alliance chain network.
2. A federation chain separation deployment method as claimed in claim 1 wherein the step of initializing BaaS comprises: defining a deployment mode as a separated deployment mode in the application configuration file of the BaaS, and starting the BaaS;
the deployment mode comprises a separated deployment mode and a non-separated deployment mode.
3. The federation chain separate deployment method of claim 1, wherein the step of creating a k8s resource configuration file and returning a network ID specifically comprises: and creating a resource object, generating and compressing the k8s resource configuration file based on the resource object to obtain a k8s resource configuration file compression package, returning the compression package, and returning the network ID.
4. The federation chain separation and deployment method of claim 1, wherein the BaaS starts a chain code, and the step of creating a federation chain network specifically comprises: inquiring the network configuration information based on the network ID, initializing a chain code and an initialization channel based on the network configuration information, acquiring organization information of the organization and node information of a node where the organization is located, uploading the organization information and the node information to the channel, adding the organization and the node into the channel, synchronizing cross-network configuration, starting chain code monitoring, and completing creation of a alliance chain network.
5. The federation chain separation deployment method of claim 1, further comprising, after completion of creation of the federation chain network: in the separate deployment mode, shielding access rights to a part of functions in the alliance chain network specifically includes: and setting the identifier of the deployment mode in the function authority table as a separate deployment mode, wherein the access authority of the partial functions is the shielded authority and is not returned.
6. A federation chain separation deployment method as claimed in claim 5 wherein the said partial functions include: the method comprises the steps of managing network instance configuration information, adding network configuration information, editing network configuration information, deleting network configuration information, checking network configuration information, joining a network, creating a network, uploading configuration information, editing cross-network configuration, stopping nodes and starting nodes.
7. The federation chain separation deployment method of claim 5, further comprising, after the step of masking access rights to partial functions in the federation chain network:
for the operation of acquiring the k8s used port, set to return error;
for the operation of obtaining the node state, setting to return running;
for the operation of checking the details of the network configuration information, the method is set to return an empty character string.
8. A federation chain split deployment system, comprising: the system comprises an application initialization module, an acquisition module, a verification module, a client creation module, a resource configuration file creation module and a chain code starting module;
the application initialization module initializes the BaaS;
the acquisition module is used for responding to a request for organizing and separately deploying a alliance link network, acquiring a network configuration file and reading network configuration information, wherein the network configuration file is stored in a readable directory of the BaaS;
the checking module is used for checking CA configuration, checking port conflict and acquiring organization information of the organization;
a client creating module, which creates a k8s client based on the network configuration information and initializes the client to construct a creating block;
a create resource profile module: acquiring a path of the network configuration file in the BaaS and a k8s instance IP, calling an interface for generating a k8s resource configuration file in a separate deployment mode by using the path of the network configuration file in the BaaS and the k8s instance IP as parameters, creating a k8s resource configuration file, and returning a network ID;
a starting chain code module, which takes the network ID and the k8s instance IP as parameters and calls an interface for starting chain codes; and the BaaS starts the chain code and creates a alliance chain network.
9. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.
10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the method of any one of claims 1 to 7 when executing the computer program.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111461192.2A CN114172804B (en) | 2021-12-01 | 2021-12-01 | Alliance chain separation deployment method, system, medium and electronic equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111461192.2A CN114172804B (en) | 2021-12-01 | 2021-12-01 | Alliance chain separation deployment method, system, medium and electronic equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114172804A true CN114172804A (en) | 2022-03-11 |
| CN114172804B CN114172804B (en) | 2024-03-01 |
Family
ID=80482415
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111461192.2A Active CN114172804B (en) | 2021-12-01 | 2021-12-01 | Alliance chain separation deployment method, system, medium and electronic equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114172804B (en) |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110113185A (en) * | 2019-04-18 | 2019-08-09 | 卓尔购电子商务(武汉)有限公司 | Method, system, storage medium and the device of a kind of rapid deployment alliance chain |
| CN111130841A (en) * | 2019-11-21 | 2020-05-08 | 深圳壹账通智能科技有限公司 | Block chain network deployment method, electronic device and computer readable storage medium |
| CN112689026A (en) * | 2020-12-07 | 2021-04-20 | 中国联合网络通信集团有限公司 | Block chain as service server and block chain sharing method |
-
2021
- 2021-12-01 CN CN202111461192.2A patent/CN114172804B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110113185A (en) * | 2019-04-18 | 2019-08-09 | 卓尔购电子商务(武汉)有限公司 | Method, system, storage medium and the device of a kind of rapid deployment alliance chain |
| CN111130841A (en) * | 2019-11-21 | 2020-05-08 | 深圳壹账通智能科技有限公司 | Block chain network deployment method, electronic device and computer readable storage medium |
| WO2021098140A1 (en) * | 2019-11-21 | 2021-05-27 | 深圳壹账通智能科技有限公司 | Blockchain network deployment method, electronic device, and computer-readable storage medium |
| CN112689026A (en) * | 2020-12-07 | 2021-04-20 | 中国联合网络通信集团有限公司 | Block chain as service server and block chain sharing method |
Non-Patent Citations (1)
| Title |
|---|
| 刘宏宇，梁秀波，吴俊涵: "基于Kubernetes 的Fabric 链码管理及高可用技术", 《计算机应用》, pages 957 - 961 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114172804B (en) | 2024-03-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108809722B (en) | Method, device and storage medium for deploying Kubernetes cluster | |
| CN110752947B (en) | K8s cluster deployment method and device, and deployment platform | |
| CN107291750B (en) | Data migration method and device | |
| CN111628886B (en) | Method, device and computer equipment for building blockchain network in private cloud environment | |
| CN113067895B (en) | Method for building block chain sub-network and block chain system | |
| CN114281253A (en) | Storage volume management method | |
| CN114363162B (en) | Block chain log generation method and device, electronic equipment and storage medium | |
| CN111935195B (en) | Distributed system management method, device, storage medium and distributed management system | |
| CN106161517B (en) | The method and apparatus for realizing cloud storage access by cloud file system | |
| CN110809051B (en) | Service data processing method and system | |
| CN114172804B (en) | Alliance chain separation deployment method, system, medium and electronic equipment | |
| CN114710350B (en) | Method and device for distributing callable resources, electronic equipment and storage medium | |
| CN115776501A (en) | Block chain system architecture, management method, electronic equipment and readable storage medium | |
| CN113259459B (en) | Block chain subnet operation state control method and block chain system | |
| CN113259466B (en) | Block chain subnet operation state control method and block chain system | |
| CN115617744A (en) | Mirror image warehouse access method, system and equipment | |
| CN115037757A (en) | Multi-cluster service management system | |
| CN114866560A (en) | Migration method and device for block chain nodes | |
| CN114880717A (en) | Data archiving method and device | |
| CN111290736B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN113590711A (en) | High-elasticity extensible multi-chain data hierarchical shared storage system and method | |
| CN114363349B (en) | Block chain sub-network starting method and device | |
| CN116909584B (en) | Deployment method, device, equipment and storage medium of space-time big data engine | |
| CN112019385B (en) | Cloud platform component deleting method, device, equipment and storage medium | |
| CN114095487B (en) | Remote task execution method, device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |