CN114465887A - Method and device for block chain configuration management based on git - Google Patents
Method and device for block chain configuration management based on git Download PDFInfo
- Publication number
- CN114465887A CN114465887A CN202111591157.2A CN202111591157A CN114465887A CN 114465887 A CN114465887 A CN 114465887A CN 202111591157 A CN202111591157 A CN 202111591157A CN 114465887 A CN114465887 A CN 114465887A
- Authority
- CN
- China
- Prior art keywords
- block chain
- configuration
- git
- chain configuration
- blockchain
- 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 63
- 239000003999 initiator Substances 0.000 claims abstract description 25
- 238000007726 management method Methods 0.000 claims abstract description 25
- 230000008569 process Effects 0.000 claims abstract description 17
- 230000004048 modification Effects 0.000 claims description 27
- 238000012986 modification Methods 0.000 claims description 27
- 230000000977 initiatory effect Effects 0.000 claims description 2
- 238000010586 diagram Methods 0.000 description 9
- 238000011144 upstream manufacturing Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 4
- 239000010979 ruby Substances 0.000 description 4
- 229910001750 ruby Inorganic materials 0.000 description 4
- 230000008859 change Effects 0.000 description 2
- 238000004590 computer program Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 238000010367 cloning Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect 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/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The embodiment of the specification discloses a block chain configuration management method based on git, which comprises the following steps: a block chain initiator creates a git warehouse main branch and initializes the block chain configuration; creating a hypervisor account for the blockchain; a block chain consensus node participant pulls the latest block chain configuration to create an account of the consensus node; the consensus node participant pulls the latest block chain configuration and sets key attribute parameters of the consensus node; the block chain super administrator pulls the latest block chain configuration to create a CA certificate; the consensus node draws the latest block chain configuration, creates a CA certificate of the consensus node and initiates a signature request; the block chain super manager processes the signature request of the consensus node; generating the blockchain configuration. The method utilizes git as a source code cooperation management tool, uses git in cooperation and management of configuration files of the block chain, and improves the accuracy and efficiency of block chain configuration.
Description
Technical Field
The present disclosure relates to the field of computer software technologies, and in particular, to a method and an apparatus for managing a blockchain configuration based on git, an electronic device, and a storage medium.
Background
The block chain configuration relates to a plurality of participants of the block chain, and due to the decentralized characteristic of the block chain, each node and the participants thereof generate a large amount of information interaction in the operation process of the block chain, and the block chain configuration is also modified correspondingly, so that the management of the block chain configuration is a multi-party cooperation scene. For example, in the running process of the block chain, the configuration of the block chain changes, a node exits when there is a new node, and changes in key attribute parameters such as an IP address, a port, and a domain of the node may occur. Then how to apply these changes, how to synchronize the changes to other nodes, how to log historical changes … … to address these needs is critical to accurately and efficiently completing blockchain configuration.
Disclosure of Invention
An object of the embodiments of the present specification is to provide a method, an apparatus, an electronic device, and a storage medium for deploying cloud native blockchain software in kubernets, which address the above problems.
In order to solve the above technical problem, the embodiments of the present specification are implemented as follows:
in a first aspect, a git-based block chain configuration management method is provided, wherein a git warehouse is created by a block chain initiator for storing block chain configuration; registering a git account by a block chain participant, wherein the operation authority of the git account on the git warehouse is set by the block chain initiator; the method comprises the following steps:
the block chain initiator creates a git warehouse main branch and initializes the block chain configuration, and submits the block chain configuration to the git warehouse;
creating a super administrator account of the blockchain, updating the blockchain configuration and submitting the blockchain configuration to the git warehouse;
a block chain consensus node participant pulls the latest block chain configuration, creates an account of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node participant pulls the latest block chain configuration, sets key attribute parameters of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the block chain super administrator pulls the latest block chain configuration, creates a CA certificate, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node draws the latest block chain configuration, creates a CA certificate of the consensus node and initiates a signature request, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the block chain super manager processes the signature request of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
and generating the block chain configuration so that the block chain participant pulls the latest block chain configuration to complete the corresponding node configuration.
In a second aspect, a git-based blockchain configuration management apparatus is provided, where a blockchain initiator creates a git repository for storing blockchain configurations; registering a git account by a block chain participant, wherein the operation authority of the git account on the git warehouse is set by the block chain initiator; the method comprises the following steps:
the block chain configuration initialization module is used for the block chain initiator to create a git warehouse main branch, initialize the block chain configuration and submit the block chain configuration to the git warehouse;
a blockchain manager module, configured to create a super manager account of the blockchain, update the blockchain configuration, and submit the updated blockchain configuration to the git repository;
a consensus node git account configuration module, wherein a block chain consensus node participant pulls the latest block chain configuration, creates an account of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
a consensus node parameter configuration module, wherein the consensus node participant pulls the latest block chain configuration, sets the key attribute parameters of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
a block chain administrator CA certificate configuration module, wherein the block chain super administrator pulls the latest block chain configuration, creates a CA certificate, updates the block chain configuration and submits the block chain configuration to the git warehouse;
a common node CA certificate configuration module, wherein the common node draws the latest block chain configuration, creates a CA certificate of the common node and initiates a signature request, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the block chain super manager processes the signature request of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
and the block chain configuration generating module is used for generating the block chain configuration so that the block chain participant pulls the latest block chain configuration to complete the corresponding node configuration.
In a third aspect, an electronic device is provided, including: a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to perform the method of the first aspect.
In a fourth aspect, a computer-readable storage medium is presented, storing one or more programs which, when executed by an electronic device comprising a plurality of application programs, cause the electronic device to perform the method of the first aspect.
The specification can achieve at least the following technical effects:
aiming at the characteristic that the block chain configuration is completed by multi-party cooperation, the invention adopts git as a cooperative management tool of the block chain configuration, after block chain participants submit respective information, the information can be merged to a git warehouse only by the examination of all the participants, and meanwhile, the block chain configuration submitted to the git warehouse is secretly set by combining with the information secrecy requirement, thereby improving the accuracy, the synchronism and the efficiency of the block chain configuration.
Drawings
In order to more clearly illustrate the embodiments of the present specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only some embodiments described in the present specification, and for those skilled in the art, other drawings can be obtained according to the drawings without any creative effort.
Fig. 1 is a schematic diagram of a method for managing a git-based block chain allocation according to an embodiment of the present disclosure.
Fig. 2 is a second schematic diagram of a git-based block chain allocation management method according to an embodiment of the present disclosure.
Fig. 3 is a third schematic diagram of a git-based block chain configuration management method according to an embodiment of the present disclosure.
Fig. 4 is a schematic diagram of a git-based blockchain allocation management apparatus according to an embodiment of the present disclosure.
Fig. 5 is a second schematic diagram of the git-based block chain allocation management apparatus according to the embodiment of the present disclosure.
Fig. 6 is a schematic structural diagram of an electronic device provided in an embodiment of the present specification.
Detailed Description
In order to make those skilled in the art better understand the technical solutions in the present specification, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only a part of the embodiments of the present specification, and not all of the embodiments. All other embodiments obtained by a person skilled in the art based on the embodiments in the present specification without any inventive step should fall within the scope of protection of the present specification.
A scheme of git-based blockchain configuration management according to the present specification is described in detail below by way of specific examples.
Key terms
git: the system is an open-source distributed version control system, and can effectively process the version management of the project from a very small project to a very large project at a high speed. The biggest difference between distributed versus centralized is that developers can submit to the local, each copying a complete Git repository on the local machine by cloning (Git clone). The GitHub is a website for wide developers to open own codes and also provides a payment function of a private warehouse, and version control software adopted by the GitHub is git. Similarly, GitLab is an open source project for a warehouse management system, and is a Web service built on the basis of Git as a code management tool. The basic Git workflow is: modifying the file in the workspace; selectively staging changes that you want to submit next, so that only the portion of the change is added to the staging area; and submitting the update, finding the file of the temporary storage area, and permanently storing the snapshot into the Git directory. If a file of a particular version is held in the Git directory, it belongs to the committed state. If the file is modified and placed in the scratch pad, the file belongs to a scratch pad state. If the modification has been made since the last check but has not been placed in the scratch pad, it is the modified state.
PR: i.e., Pull Request operation, can be considered as a distributed code examination merge tool, which is one of the most commonly used tools for git. Taking GitHub as an example, the basic operations of PR include: for a project developer to firstly Fork the project, changing the project into a project under a project developer GitHub; then creating a new branch after the item is locally located by using a command line clone; associating a remote repository; submitting the modification to the project of the remote project developer just before when the modification is made to the project; changes in the project developer fork project are submitted to the project of the main developer in a PR mode, and PR is completed.
Example one
Fig. 1 is a schematic diagram of a method for managing a block chain allocation based on git according to an embodiment of the present invention. It should be noted first that the blockchain configuration involves multiple participants and information interaction among each other, and the configuration of the chain is modified accordingly. Therefore, the method is a multi-party cooperative scenario, and the problems of the existing scheme can be well solved by using git management block chain configuration, and particularly, the following advantages of git are brought into play: (1) git can set authority, only allowing the participator to check and modify the warehouse of the storage chain configuration; (2) git pushes local modification to remote through pull/push command, safety and feedback; (3) git may review the modifications through the PR function, with one or more participants confirming that they can only be merged; (4) other participants can pull the latest configuration through git pull; (5) git itself may record the history of modifications, when and what modifications have been made by someone. Meanwhile, as the block chain is configured with sensitive information such as IP addresses, ports and the like, the risk of information leakage can be avoided by establishing a private git warehouse; configuration modification can be managed more conveniently through a graphical interface provided by gitlab, github and the like.
Based on the above analysis, the method of the embodiment of the present invention was performed according to the following procedure. Although the examples are described using GitHub as an example, the method of the present invention may be implemented by other platforms such as GitLab and the like without violating the scheme of the present invention. First, a git repository is created by the blockchain initiator for saving blockchain configurations. Secondly, registering git accounts by block chain participants respectively, wherein the operation authority of the git accounts on the git warehouse is set by the block chain initiator. Alternatively, git flow may be chosen, setting the main branch to allow merging only in the PR fashion, and requiring consent from all participants to do so. In addition, in one embodiment, since the blockchain configuration may involve sensitive information such as IP addresses and port numbers of the common node, the configuration tool cloud-config may be selected to generate confidential information and non-confidential information at the same time, and only the non-confidential information is submitted to the git repository through gitignore mechanism. After the preamble work is done, the method comprises the following steps:
step 101: and the block chain initiator creates a git warehouse main branch, initializes the block chain configuration and submits the block chain configuration to the git warehouse.
Bash
$git clone git@github.com:rink1969/chain-config-example.git
$cd chain-config-example
# Create directory Structure
$cloud-config init-chain
# some settings are made to the repository to prevent the inadvertent submission of some confidential information, which could cause information leakage
$echo"test-chain/accounts/*/">.gitignore
$echo"test-chain/ca_cert/key.pem">>.gitignore
$echo"test-chain/certs/*/key.pem">>.gitignore
$echo"test-chain-*">>.gitignore
$touch test-chain/accounts/.gitkeep
$touch test-chain/ca_cert/.gitkeep
$touch test-chain/certs/.gitkeep
Configuration of # initialization chain
$cloud-config init-chain-config
Initial configuration of # lifting chain
$git add.
$git push
Step 102: creating a super administrator account for the blockchain, updating the blockchain configuration, and submitting to the git repository.
PowerShell
$git clone git@github.com:rink1969/chain-config-example.git
$cd chain-config-example
# Create admin Branch and modify chain configuration
$git checkout-b admin
$cloud-config new-account
key_id:1,address:29e66df76b1d8b7a2cece994a2d3a8b7704a8281
$cloud-config set-admin--admin 29e66df76b1d8b7a2cece994a2d3a8b7704a8281
Submit (because the previous setting, gitignore, so will not submit the account information, only submit the configuration file modification)
$git diff
diff--git a/test-chain/chain_config.toml b/test-chain/chain_config.toml
index 5709e4b..975f78b 100644
---a/test-chain/chain_config.toml
+++b/test-chain/chain_config.toml
@@-29,7+29,7@@prevhash＝'0x0000000000000000000000000000000000000000000000000000000000000000'
timestamp＝1638081449922
[system_config]
-admin＝”
+admin＝'29e66df76b1d8b7a2cece994a2d3a8b7704a8281'
block_interval＝3
block_limit＝100
chain_id＝'63586a3c0255f337c77a777ff54f0040b8c388da04f23ecee6bfd4953a6512b4'
$git add.
$git commit-m"set admin"
$git push--set-upstream origin admin
Step 103: and pulling the latest block chain configuration by the block chain consensus node participant, creating an account of the consensus node, updating the block chain configuration and submitting the block chain configuration to the git warehouse.
Assuming that the blockchain has 2 consensus nodes, then the consensus node0 operates as follows:
Bash
$git clone git@github.com:rink1969/chain-config-example.git
$cd chain-config-example
# create node0 Branch and modify chain configuration
$git checkout-b node0
$cloud-config new-account
key_id:1,address:cfc8e87ae610452da9a24c87db2981f2e1f192fb
$cloud-config append-validator--validator cfc8e87ae610452da9a24c87db2981f2e1f192fb
Submit (because the previous setting, gitignore, so will not submit the account information, only submit the configuration file modification)
$git add.
$git commit-m"append node0"
$git push--set-upstream origin node0
Step 104: and the consensus node participant pulls the latest block chain configuration, sets key attribute parameters of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse. Optionally, the key attribute parameters of the consensus node are set to include an IP address, a port number, and a domain of the consensus node.
Taking the configuration of the node key parameters of the consensus node0 as an example:
Ruby
latest configuration of # Pull chain
$git checkout main
$git pull
# creation of New Branch and modification of chain configuration
$git checkout-b node0_append_node
$cloud-config append-node--node localhost:40000:node0
# commit IP Address, Port number, and Domain
$git commit-m"append node0 ip port and domain"
$git push--set-upstream origin node0_append_node
Similarly, the consensus node1 also performs the setting of the key attribute parameters. However, when a conflict occurs with a merge, the conflict needs to be resolved and resubmitted:
PowerShell
configuration of the chain in which # Pull Main Branch is newest
$git checkout main
$git pull
#rebase
$git checkout node1_append_node
$git rebase main
$git status
Interactive variable base operations are in progress; to 0206fd1
The last command is completed (1 command executed):
pick 0f2919a append node1 ip port and domain
no commands remain.
You are performing an operation that changes the branch 'node1_ apend _ node' to '0206fd 1'.
(resolving conflicts and then running "git base- -continue")
(skip this patch using "git base- -skip")
(use of "git base- -abort" to detect the original branch)
Non-merged path:
(use of "git restore- -staged < document > -" to cancel staging)
(use of "git add < file >. -." Mark solution)
Modification by two parties: test-chain/chain _ config
Modifications not yet added to the commit (using "git add" and/or "git commit-a")
# resolving conflicts and resubmitting
$git add.
$git push-f
Step 105: and the block chain super manager pulls the latest block chain configuration, creates a CA certificate, updates the block chain configuration and submits the block chain configuration to the git warehouse.
Ruby
Configuration of the chain in which # Pull Main Branch is newest
$git checkout main
$git pull
Creates a new branch and creates a CA certificate
$git checkout-b create_ca
$cloud-config create-ca
# submission
$git add.
$git commit-m"create ca"
$git push--set-upstream origin create_ca
Step 106: and the consensus node draws the latest block chain configuration, creates a CA certificate of the consensus node, initiates a signature request, updates the block chain configuration and submits the block chain configuration to the git warehouse.
Ruby
Configuration of # Pull Main Branch newest chain
$git checkout main
$git pull
# creation of a New Branch
$git checkout-b create_csr
Creates a certificate for the node and initiates a signing request
The domain parameter at this point is consistent with the domain at the time of apend-node
$cloud-config create-csr--domain node0
# submission
$git add.
$git commit-m"node0 create csr"
$git push--set-upstream origin create_csr
Step 107: and the block chain super manager processes the signature request of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse.
Ruby
Configuration of the chain in which # Pull Main Branch is newest
$git checkout main
$git pull
# creation of a New Branch
$git checkout-b sign_csr
# Process signature request
The domain parameter at this point is consistent with the domain at the time of apend-node
$cloud-config sign-csr--domain node0
$cloud-config sign-csr--domain node1
# submission
$git add.
$git commit-m"sign csr"
$git push--set-upstream origin sign_csr
Step 108: and generating the block chain configuration so that the block chain participant pulls the latest block chain configuration to complete the corresponding node configuration.
It should be noted that, referring to fig. 2, when the blockchain configuration is updated and submitted to the git repository, the method includes:
step 151: creating a corresponding branch for the modified block chain configuration;
step 152: initiating review of the modified blockchain configuration;
step 153: merging the corresponding branch to the primary branch after the completion of the review of the blockchain configuration modification by the blockchain participant.
Therefore, as can be seen from the above description of the method flow in the embodiment, the method of the present invention has only one configuration file on the primary branch, and in the process of configuring the blockchain and its common node, although the temporary branch is created, it is finally merged into the primary branch. Optionally, the blockchain participant pulls the latest blockchain configuration from the git warehouse master branch.
As shown in fig. 3, in another embodiment, a method for managing a block chain allocation based on git further includes:
step 109: when the block chain configuration is modified, pulling the latest block chain configuration, updating the block chain configuration after the corresponding modification is completed, and submitting the updated block chain configuration to the git warehouse;
step 110: and checking a modification record of the block chain configuration on the github or the gitlab, and backtracking a checking condition for modifying the block chain configuration by checking the checking record.
Example two
Fig. 4 is a schematic structural diagram of a block chain allocation management apparatus 400 based on git according to an embodiment of the present disclosure. Referring to fig. 4, in one embodiment a git-based blockchain configuration management apparatus, creates a git repository by the blockchain initiator for saving blockchain configurations; registering a git account by a block chain participant, wherein the operation authority of the git account on the git warehouse is set by the block chain initiator; the method comprises the following steps:
a block chain configuration initialization module 401, configured to create a git warehouse main branch and initialize the block chain configuration by the block chain initiator, and submit the block chain configuration to the git warehouse;
a blockchain administrator module 402, configured to create a super administrator account for the blockchain, update the blockchain configuration, and submit the updated blockchain configuration to the git repository;
a consensus node git account configuration module 403, wherein a block chain consensus node participant pulls the latest block chain configuration, creates an account of the consensus node, updates the block chain configuration, and submits the updated block chain configuration to the git repository;
a consensus node parameter configuration module 404, where the consensus node participant pulls the latest block chain configuration, sets the key attribute parameters of the consensus node, updates the block chain configuration, and submits the block chain configuration to the git warehouse;
a block chain administrator CA certificate configuration module 405, where the block chain super administrator pulls the latest block chain configuration, creates a CA certificate, updates the block chain configuration, and submits the block chain configuration to the git repository;
a consensus node CA certificate configuration module 406, where the consensus node pulls the latest block chain configuration, creates a CA certificate of the consensus node and initiates a signature request, updates the block chain configuration, and submits the block chain configuration to the git repository;
a signature request processing module 407, where the block chain hypervisor processes the signature request of the consensus node, updates the block chain configuration, and submits the block chain configuration to the git warehouse;
the block chain configuration generating module 408 generates the block chain configuration, so that the block chain participant pulls the latest block chain configuration to complete the corresponding node configuration.
As shown in fig. 5, in another embodiment, an apparatus 300 for managing a git-based blockchain allocation is further provided, which further includes:
and a block chain configuration updating module 409, configured to, when the block chain configuration is modified, pull the latest block chain configuration, update the block chain configuration after the corresponding modification is completed, and submit the updated block chain configuration to the git warehouse.
The block chain configuration modification record module 410 is configured to view modification records of the block chain configuration on the github or gitlab, and trace back a review condition for modifying the block chain configuration by viewing the review records.
It should be understood that the git-based blockchain configuration management apparatus according to the embodiment of the present disclosure may also perform the method performed by the git-based blockchain configuration management apparatus (or device) in fig. 1 to 3, and implement the functions of the git-based blockchain configuration management apparatus (or device) in the examples shown in fig. 1 to 3, which are not described herein again.
Example four
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present specification. Referring to fig. 6, at a hardware level, the electronic device includes a processor, and optionally further includes an internal bus, a network interface, and a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory, such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.
The processor, the network interface, and the memory may be connected to each other via an internal bus, which may be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, an EISA (Extended Industry Standard Architecture) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one double-headed arrow is shown in FIG. 6, but that does not indicate only one bus or one type of bus.
And the memory is used for storing programs. In particular, the program may include program code comprising computer operating instructions. The memory may include both memory and non-volatile storage and provides instructions and data to the processor.
The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs the computer program to form the shared resource access control device on the logic level. The processor is used for executing the program stored in the memory and is specifically used for executing the following operations:
creating a git repository by the blockchain initiator for saving blockchain configuration; registering a git account by a block chain participant, wherein the operation authority of the git account on the git warehouse is set by the block chain initiator; the method comprises the following steps:
the block chain initiator creates a git warehouse main branch and initializes the block chain configuration, and submits the block chain configuration to the git warehouse;
creating a super administrator account of the blockchain, updating the blockchain configuration and submitting the blockchain configuration to the git warehouse;
a block chain consensus node participant pulls the latest block chain configuration, creates an account of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node participant pulls the latest block chain configuration, sets key attribute parameters of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the block chain super manager pulls the latest block chain configuration, creates a CA certificate, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node draws the latest block chain configuration, creates a CA certificate of the consensus node and initiates a signature request, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the block chain super manager processes the signature request of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
and generating the block chain configuration so that the block chain participant pulls the latest block chain configuration to complete the corresponding node configuration.
The above-mentioned block chain allocation management method based on git according to the embodiments shown in fig. 1 to fig. 3 of the present specification can be applied to or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or instructions in the form of software. The Processor may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; but also Digital Signal Processors (DSPs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other Programmable logic devices, discrete Gate or transistor logic devices, discrete hardware components. The various methods, steps and logic blocks disclosed in the embodiments of the present specification may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present specification may be embodied directly in a hardware decoding processor, or in a combination of hardware and software modules in the decoding processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and a processor reads information in the memory and completes the steps of the method in combination with hardware of the processor.
Of course, besides the software implementation, the electronic device of the embodiment of the present disclosure does not exclude other implementations, such as a logic device or a combination of software and hardware, and the like, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or a logic device.
EXAMPLE five
Embodiments of the present specification also propose a computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a portable electronic device comprising a plurality of application programs, are capable of causing the portable electronic device to perform the method of the embodiments shown in fig. 1 to 3, and in particular to perform the method of:
creating a git repository by the blockchain initiator for saving blockchain configuration; registering a git account by a block chain participant, wherein the operation authority of the git account on the git warehouse is set by the block chain initiator; the method comprises the following steps:
the block chain initiator creates a git warehouse main branch and initializes the block chain configuration, and submits the block chain configuration to the git warehouse;
creating a super administrator account of the blockchain, updating the blockchain configuration and submitting the blockchain configuration to the git warehouse;
a block chain consensus node participant pulls the latest block chain configuration, creates an account of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node participant pulls the latest block chain configuration, sets key attribute parameters of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the block chain super administrator pulls the latest block chain configuration, creates a CA certificate, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node draws the latest block chain configuration, creates a CA certificate of the consensus node and initiates a signature request, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the block chain super manager processes the signature request of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
and generating the block chain configuration so that the block chain participant pulls the latest block chain configuration to complete the corresponding node configuration.
In short, the above description is only a preferred embodiment of the present disclosure, and is not intended to limit the scope of the present disclosure. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present specification shall be included in the protection scope of the present specification.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. One typical implementation device is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The embodiments in the present specification are described in a progressive manner, and the same and similar parts among the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, for the system embodiment, since it is substantially similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
Claims (11)
1. A git-based blockchain configuration management method is characterized in that a git warehouse is created by a blockchain initiator for storing blockchain configuration; registering a git account by a block chain participant, wherein the operation authority of the git account on the git warehouse is set by the block chain initiator; the method comprises the following steps:
the block chain initiator creates a git warehouse main branch and initializes the block chain configuration, and submits the block chain configuration to the git warehouse;
creating a super administrator account of the blockchain, updating the blockchain configuration and submitting the blockchain configuration to the git warehouse;
a block chain consensus node participant pulls the latest block chain configuration, creates an account of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node participant pulls the latest block chain configuration, sets key attribute parameters of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the block chain super administrator pulls the latest block chain configuration, creates a CA certificate, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node draws the latest block chain configuration, creates a CA certificate of the consensus node and initiates a signature request, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the block chain super manager processes the signature request of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
and generating the block chain configuration so that the block chain participant pulls the latest block chain configuration to complete the corresponding node configuration.
2. The method of claim 1, wherein the consensus node participant pulls the latest blockchain configuration from a git warehouse primary branch.
3. The method of claim 1, wherein the git account's operational rights to the git repository include selecting a particular way to review modifications to the blockchain configuration.
4. The method of claim 1, wherein setting the consensus node key attribute parameters comprises an IP address, a port number, and a domain of the consensus node.
5. The method of claim 1, wherein updating and submitting the blockchain configuration to a git repository comprises:
creating a corresponding branch for the modified block chain configuration;
initiating a review of the modified blockchain configuration;
merging the corresponding branch to the primary branch after the completion of the review of the blockchain configuration modification by the blockchain participant.
6. The method of claim 1, wherein the blockchain configuration submitted to the git repository is privacy set according to information privacy requirements.
7. The method of claim 1, further comprising:
when the block chain configuration is modified, pulling the latest block chain configuration, updating the block chain configuration after the corresponding modification is completed, and submitting the updated block chain configuration to the git warehouse;
and checking a modification record of the block chain configuration on the github or the gitlab, and backtracking a checking condition for modifying the block chain configuration by checking the checking record.
8. A git-based blockchain configuration management apparatus, wherein a git repository is created by a blockchain initiator for preserving blockchain configurations; registering a git account by a block chain participant, wherein the operation authority of the git account on the git warehouse is set by the block chain initiator; the method comprises the following steps:
the block chain configuration initialization module is used for the block chain initiator to create a git warehouse main branch, initialize the block chain configuration and submit the block chain configuration to the git warehouse;
a blockchain manager module, configured to create a super manager account of the blockchain, update the blockchain configuration, and submit the updated blockchain configuration to the git repository;
a consensus node git account configuration module, wherein a block chain consensus node participant pulls the latest block chain configuration, creates an account of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
a consensus node parameter configuration module, wherein the consensus node participant pulls the latest block chain configuration, sets the key attribute parameters of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
a block chain administrator CA certificate configuration module, wherein the block chain super administrator pulls the latest block chain configuration, creates a CA certificate, updates the block chain configuration and submits the block chain configuration to the git warehouse;
a common node CA certificate configuration module, wherein the common node draws the latest block chain configuration, creates a CA certificate of the common node and initiates a signature request, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the block chain super manager processes the signature request of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
and the block chain configuration generating module is used for generating the block chain configuration so that the block chain participant pulls the latest block chain configuration to complete the corresponding node configuration.
9. The apparatus of claim 8, further comprising:
the block chain configuration updating module is used for pulling the latest block chain configuration when the block chain configuration is modified, updating the block chain configuration after the corresponding modification is finished and submitting the updated block chain configuration to the git warehouse;
and the block chain configuration modification record module is used for checking the modification record of the block chain configuration on the github page and backtracking the checking condition of modifying the block chain configuration by checking the checking record.
10. An electronic device, comprising:
a processor; and
a memory arranged to store computer executable instructions that, when executed, cause the processor to perform the method of any of claims 1 to 7.
11. A computer readable storage medium, characterized in that the computer readable storage medium stores one or more programs that, when executed by an electronic device comprising a plurality of application programs, cause the electronic device to perform the method of any of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111591157.2A CN114465887B (en) | 2021-12-23 | 2021-12-23 | Block chain configuration management method and device based on git |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111591157.2A CN114465887B (en) | 2021-12-23 | 2021-12-23 | Block chain configuration management method and device based on git |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114465887A true CN114465887A (en) | 2022-05-10 |
| CN114465887B CN114465887B (en) | 2024-01-23 |
Family
ID=81407175
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111591157.2A Active CN114465887B (en) | 2021-12-23 | 2021-12-23 | Block chain configuration management method and device based on git |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114465887B (en) |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2018100149A4 (en) * | 2018-02-02 | 2018-03-08 | Keith Stewart Alistair Redenbach | Abcde |
| CN108964982A (en) * | 2018-06-13 | 2018-12-07 | 众安信息技术服务有限公司 | For realizing the method, apparatus and storage medium of the deployment of the multinode of block chain |
| CN109165944A (en) * | 2018-08-21 | 2019-01-08 | 北京京东金融科技控股有限公司 | Multiple party signatures authentication method, device, equipment and storage medium based on block chain |
| CN109815206A (en) * | 2018-12-25 | 2019-05-28 | 上海点对点科技有限公司 | A kind of distributed storage network based on block chain |
| CN110472881A (en) * | 2019-08-21 | 2019-11-19 | 重庆华医康道科技有限公司 | Based on the state machine workflow engine of block chain and the working method of distributed storage |
| CN111130841A (en) * | 2019-11-21 | 2020-05-08 | 深圳壹账通智能科技有限公司 | Block chain network deployment method, electronic device and computer readable storage medium |
| CN111245886A (en) * | 2019-11-29 | 2020-06-05 | 武汉烽火信息集成技术有限公司 | Multi-party collaboration system, method and storage medium based on block chain |
| CN111381863A (en) * | 2020-03-17 | 2020-07-07 | 成都创流科技有限责任公司 | APP transaction and automatic online method and system based on block chain technology |
| CN112118124A (en) * | 2020-08-03 | 2020-12-22 | 西安电子科技大学 | Block chain construction method, system, storage medium, computer equipment and application |
| CN112527357A (en) * | 2020-12-14 | 2021-03-19 | 中国平安人寿保险股份有限公司 | Service hot loading updating method and device, computer equipment and storage medium |
| US20210124760A1 (en) * | 2019-10-25 | 2021-04-29 | Accenture Global Solutions Limited | Automatic creation of blockchain network infrastructures |
| CN112882725A (en) * | 2021-01-22 | 2021-06-01 | 深圳市宝能投资集团有限公司 | Chain code management method and device based on Git, electronic equipment and storage medium |
| CN113268711A (en) * | 2021-05-25 | 2021-08-17 | 国网山东省电力公司电力科学研究院 | Transformer substation relay protection device software version management method based on Git and block chain |
| WO2021217868A1 (en) * | 2020-04-30 | 2021-11-04 | 平安科技（深圳）有限公司 | Git-based project version release method and apparatus, device, and medium |
| CN113626826A (en) * | 2021-07-29 | 2021-11-09 | 西安电子科技大学 | Intelligent contract security detection method, system, equipment, terminal and application |
| CN113673936A (en) * | 2021-08-31 | 2021-11-19 | 上海金融期货信息技术有限公司 | Block chain-based warehouse receipt full life cycle management method and system |
-
2021
- 2021-12-23 CN CN202111591157.2A patent/CN114465887B/en active Active
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2018100149A4 (en) * | 2018-02-02 | 2018-03-08 | Keith Stewart Alistair Redenbach | Abcde |
| CN108964982A (en) * | 2018-06-13 | 2018-12-07 | 众安信息技术服务有限公司 | For realizing the method, apparatus and storage medium of the deployment of the multinode of block chain |
| CN109165944A (en) * | 2018-08-21 | 2019-01-08 | 北京京东金融科技控股有限公司 | Multiple party signatures authentication method, device, equipment and storage medium based on block chain |
| CN109815206A (en) * | 2018-12-25 | 2019-05-28 | 上海点对点科技有限公司 | A kind of distributed storage network based on block chain |
| CN110472881A (en) * | 2019-08-21 | 2019-11-19 | 重庆华医康道科技有限公司 | Based on the state machine workflow engine of block chain and the working method of distributed storage |
| US20210124760A1 (en) * | 2019-10-25 | 2021-04-29 | Accenture Global Solutions Limited | Automatic creation of blockchain network infrastructures |
| CN111130841A (en) * | 2019-11-21 | 2020-05-08 | 深圳壹账通智能科技有限公司 | Block chain network deployment method, electronic device and computer readable storage medium |
| CN111245886A (en) * | 2019-11-29 | 2020-06-05 | 武汉烽火信息集成技术有限公司 | Multi-party collaboration system, method and storage medium based on block chain |
| CN111381863A (en) * | 2020-03-17 | 2020-07-07 | 成都创流科技有限责任公司 | APP transaction and automatic online method and system based on block chain technology |
| WO2021217868A1 (en) * | 2020-04-30 | 2021-11-04 | 平安科技（深圳）有限公司 | Git-based project version release method and apparatus, device, and medium |
| CN112118124A (en) * | 2020-08-03 | 2020-12-22 | 西安电子科技大学 | Block chain construction method, system, storage medium, computer equipment and application |
| CN112527357A (en) * | 2020-12-14 | 2021-03-19 | 中国平安人寿保险股份有限公司 | Service hot loading updating method and device, computer equipment and storage medium |
| CN112882725A (en) * | 2021-01-22 | 2021-06-01 | 深圳市宝能投资集团有限公司 | Chain code management method and device based on Git, electronic equipment and storage medium |
| CN113268711A (en) * | 2021-05-25 | 2021-08-17 | 国网山东省电力公司电力科学研究院 | Transformer substation relay protection device software version management method based on Git and block chain |
| CN113626826A (en) * | 2021-07-29 | 2021-11-09 | 西安电子科技大学 | Intelligent contract security detection method, system, equipment, terminal and application |
| CN113673936A (en) * | 2021-08-31 | 2021-11-19 | 上海金融期货信息技术有限公司 | Block chain-based warehouse receipt full life cycle management method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114465887B (en) | 2024-01-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| TWI737944B (en) | Block chain-based transaction execution method and device, and electronic equipment | |
| CN110400142B (en) | Data processing method, device and storage medium | |
| US11102003B2 (en) | Ledger-independent token service | |
| EP3591510A1 (en) | Method and device for writing service data in block chain system | |
| US20220004539A1 (en) | Privacy preserving architecture for permissioned blockchains | |
| TW201822033A (en) | Resource processing method and apparatus | |
| TW202008235A (en) | Transaction method and system based on centralized settlement and block chain storage | |
| CN112235278A (en) | Method and device for monitoring address information of trader and electronic equipment | |
| WO2022007548A1 (en) | Blockchain implementation to securely store information off-chain | |
| US10104163B1 (en) | Secure transfer of virtualized resources between entities | |
| CN114971827A (en) | Account checking method and device based on block chain, electronic equipment and storage medium | |
| US20220407707A1 (en) | Generative cryptogram for blockchain data managment | |
| US20220343323A1 (en) | Method and apparatus maintaining private data with consortium blockchain | |
| CN108710658B (en) | Data record storage method and device | |
| CN114465887B (en) | Block chain configuration management method and device based on git | |
| JP2024512256A (en) | Reducing transaction aborts within an execution-ordering-validation blockchain model | |
| CN115018499A (en) | Block chain-based digital certificate issuing method, device and system | |
| JP2023538497A (en) | editable blockchain | |
| CN110297625B (en) | Application processing method and device | |
| CN114266680A (en) | Block chain-based electronic contract signing method, device and system | |
| CN110290172B (en) | Container application cloning method and device, computer equipment and storage medium | |
| CN113949632A (en) | Dynamic node configuration method and device for block chain | |
| CN114579585A (en) | Block chain selective world state database | |
| CN113592645A (en) | Data verification method and device | |
| CN108632348B (en) | Service checking method and device |
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 |