CN111506657A

CN111506657A - Method for deploying block chain node equipment

Info

Publication number: CN111506657A
Application number: CN202010310573.XA
Authority: CN
Inventors: 冯士乘
Original assignee: Tencent Technology Shenzhen Co Ltd
Current assignee: Tencent Technology Shenzhen Co Ltd
Priority date: 2020-04-17
Filing date: 2020-04-17
Publication date: 2020-08-07
Anticipated expiration: 2040-04-17
Also published as: CN111506657B

Abstract

The embodiment of the application provides a method for deploying block link point equipment. The block link point equipment deployment method can comprise the following steps: the electronic equipment acquires a node installation file, wherein the node installation file comprises a node installation package and a script of the node equipment; importing the target file in the node installation package into a file directory corresponding to the target file based on the script of the node equipment; modifying the environmental parameters in the node installation package into first target parameters based on the script of the node equipment; and operating the first target parameters and importing the target file of the file directory to realize that the electronic equipment is deployed as block link point equipment. By adopting the embodiment of the application, the electronic equipment is automatically deployed as the block chain node point equipment in the private chain network based on the script of the node equipment, so that the block chain node point equipment is effectively deployed.

Description

Method for deploying block chain node equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method for deploying block link point devices.

Background

The blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism and an encryption algorithm. Blockchains can be divided into public, alliance, and private chains.

Currently, block link point devices in private chain networks are deployed by installing a K8S tool in a central control machine and then operating the K8S tool to deploy electronic devices as block link point devices. However, the deployment of this block-linked dot device is always dependent on the central controller. Therefore, how to effectively deploy the blockchain node devices and construct the private chain network is very important for the development of the blockchain technology.

Disclosure of Invention

The embodiment of the application provides a method for deploying block chain link point equipment, which can realize the deployment of the block chain link point equipment in a private chain network and improve the deployment efficiency of the block chain link point equipment without depending on a K8S tool installed in a central control machine.

In a first aspect, an embodiment of the present application provides a method for block link point device deployment, where the method includes:

the electronic equipment acquires a node installation file, wherein the node installation file comprises a node installation package and a script of the node equipment;

the electronic equipment imports the target file in the node installation package into a file directory corresponding to the target file based on the script of the node equipment;

the electronic equipment modifies the environmental parameters in the node installation package into first target parameters based on the script of the node equipment;

the electronic equipment runs the first target parameter and imports a target file of the file directory to realize that the electronic equipment is deployed as block link point equipment.

In a second aspect, an embodiment of the present application provides an electronic device, which includes a memory and a processor. Wherein the memory is used for storing the computer program. A processor for invoking a computer program for performing the method of block-linked dot device deployment as described in the first aspect.

In a third aspect, embodiments of the present application provide a block link point deployment device, where the device has a function of implementing deployment of the block link point equipment described in the first aspect. The functions can be realized by hardware, and the functions can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the above-described functions.

In one implementation, the block link point deployment device includes a receiving module, an importing module, a modifying module, and an operating module. The receiving module is used for obtaining a node installation file, and the node installation file comprises a node installation package and a script of node equipment. And the import module is used for importing the target file in the node installation package into the file directory corresponding to the target file based on the script of the node equipment. And the modification module is used for modifying the environmental parameters in the node installation package into first target parameters based on the script of the node equipment. And the operation module is used for operating the first target parameter and importing the target file of the file directory so as to realize that the electronic equipment is deployed as block link point equipment.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium storing a computer program, the computer program comprising program instructions that, when executed by a processor, cause the processor to perform the functions of the block link node device deployment according to the first aspect.

Through the embodiment of the application, the electronic equipment can acquire the node equipment installation file and deploy the block chain node equipment based on the node installation package in the node installation file and the script of the node equipment. Compared with the block chain node equipment deployed based on a third party (a central control machine), the block chain node equipment deployment efficiency of the private chain network can be improved.

Drawings

In order to more clearly describe the technical solutions in the embodiments or background art of the present application, the drawings required to be used in the embodiments of the present application will be described below.

Fig. 1 is a block chain network according to an embodiment of the present disclosure;

fig. 2 is a schematic flow chart of a method for block link point device deployment according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a block link point deployment method provided by an embodiment of the present application;

fig. 4 is a schematic flowchart of a back-end as a service deployment provided in an embodiment of the present application;

fig. 5 is a schematic diagram of a method for back-end as-a-service deployment according to an embodiment of the present application;

fig. 6 is a schematic diagram of a foreground deployment method provided in an embodiment of the present application;

FIG. 7 is a schematic diagram of an interface provided by an embodiment of the present application;

FIG. 8 is a schematic structural diagram of a block link point deployment device provided by an embodiment of the present application;

fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.

Detailed Description

The embodiments of the present application will be described below with reference to the drawings.

With the advent of the information age, Blockchain (Blockchain) technology has been pursued in various fields by virtue of its advantages such as decentralization, distributed storage, and the like. The blockchain is essentially a decentralized database, which is a string of data blocks associated by using cryptography, each data block contains information of a batch of network transactions, and the information is used for verifying the validity (anti-counterfeiting) of the information and generating the next block. The blockchain may include a blockchain underlying platform, a platform product services layer, and an application services layer.

The block chain underlying platform can comprise processing modules such as user management, basic service, intelligent contract and operation monitoring. The user management module is responsible for identity information management of all blockchain participants, and comprises public and private key generation maintenance (account management), key management, user real identity and blockchain address corresponding relation maintenance (authority management) and the like, and under the authorization condition, the user management module supervises and audits the transaction condition of certain real identities and provides rule configuration (wind control audit) of risk control; the basic service module is deployed on all block chain node equipment and used for verifying the validity of the service request, recording the service request to storage after consensus on the valid request is completed, for a new service request, the basic service firstly performs interface adaptation analysis and authentication processing (interface adaptation), then encrypts service information (consensus management) through a consensus algorithm, transmits the service information to a shared account (network communication) completely and consistently after encryption, and performs recording and storage; the intelligent contract module is responsible for registering and issuing contracts, triggering the contracts and executing the contracts, developers can define contract logics through a certain programming language, issue the contract logics to a block chain (contract registration), call keys or other event triggering and executing according to the logics of contract clauses, complete the contract logics and simultaneously provide the function of upgrading and canceling the contracts; the operation monitoring module is mainly responsible for deployment, configuration modification, contract setting, cloud adaptation in the product release process and visual output of real-time states in product operation, such as: alarm, monitoring network conditions, monitoring node equipment health status, and the like.

A blockchain network is a distributed system formed by at least one blockchain node device connected by means of network communication. Referring to fig. 1, fig. 1 is a schematic diagram illustrating an architecture of a blockchain network according to an embodiment of the present disclosure. The block chain network is composed of a plurality of block chain node devices, and the block chain node devices are electronic devices. As shown in fig. 1, the blockchain network is composed of an electronic device 101, an electronic device 102, an electronic device 103, and an electronic device 104. The electronic device may include a PC (Personal Computer), a PDA (tablet), a cell phone, a smart wearable device, a server, and the like. That is, building a blockchain network requires deploying at least one electronic device as a blockchain link point device. The block chain node point devices can be communicated with each other, and the block chain node point devices can also be communicated with the outside, so that information interaction is realized.

With the continuous development of the blockchain, the blockchain gradually evolves into a public chain, a federation chain, and a private chain. The public chain refers to a blockchain in which anyone can enter a blockchain network at any time to read data, send data or compete for accounting. A federation chain refers to a chain of blocks where several organizations or enterprises participate together in management. The private chain is a block chain with certain centralized control, the writing right of the account book of the private chain is controlled by a certain organization or organization, and the access and the use of data have strict authority management.

Currently, a block link point device in a private chain network is deployed by installing a K8S tool in a Central control system (Central control system), and deploying an electronic device as the block link point device by controlling a K8S tool. The central control machine can control other devices, and realize resource sharing, video and audio transmission, mutual monitoring and the like. The K8S tool is a conventional tool for deploying blockchain node devices. Therefore, the deployment of the block chain node point equipment of the traditional private chain network depends on the central control machine, and if one machine room to be deployed does not have the central control machine, the block chain node point equipment of the private chain network cannot be deployed, so that the deployment efficiency is low.

Among them, the private chain network can be understood as a scenario described below. For example, 10 computers in a computer room are deployed as blockchain link point devices, and a blockchain network formed by 10 blockchain node devices is controlled by an organization or a mechanism, then 10 blockchain node devices form a private chain network. The private chain network defines read and write data permissions, such as defining write data permissions of a device to the private chain network.

In order to deploy electronic devices as block-link point devices in a private chain network, efficient deployment of block-link point devices is achieved. The embodiment of the application provides a method for deploying block chain node equipment, which comprises the following steps: the electronic equipment acquires a node installation file, wherein the node installation file comprises a node installation package and a script of the node equipment; the electronic equipment imports the target file in the node installation package into a file directory corresponding to the target file based on the script of the node equipment; the electronic equipment modifies the environmental parameters in the node installation package into first target parameters based on the script of the node equipment; the electronic equipment runs the first target parameter and imports a target file of the file directory to realize that the electronic equipment is deployed as block link point equipment.

According to the embodiment of the application, the electronic equipment processes the node installation package based on the acquired script of the node equipment, and the electronic equipment can be automatically deployed as block chain node equipment. Compared with the traditional private chain network that the deployment of the block chain node equipment depends on the central control machine, the block chain node equipment deployment can improve the deployment efficiency of the block chain node equipment of the private chain network.

Referring to fig. 2, fig. 2 is a block link point device deployment method provided in the embodiment of the present application, which includes, but is not limited to, the following steps:

step S201: and acquiring the node installation file.

The node installation file comprises a node installation package and a script of the node device. In detail, the node installation file includes: the method comprises the steps of installing a file package on a DataPkg.

In one implementation, an electronic device may receive a node installation file via a transmission interface. For example, the electronic device may receive the node installation file through, for example, a usb port.

In one implementation, the electronic device downloads the node installation file via a download address of the node installation file. The download address may be a download link for downloading the node installation file, or a web page address for downloading the node installation file, or a two-dimensional code image for downloading the node installation file, or the like. For example, the node installation file may be obtained by inputting a download link in a browser installed in the electronic device, searching for and downloading the node installation file. For another example, a web page address capable of downloading the node installation file is input in a browser installed in the electronic device, and after a web page corresponding to the web page address is opened, the node installation file is downloaded in the web page. For another example, the two-dimensional code stored or displayed by the electronic device is scanned by the electronic device, and the node device installation file is directly downloaded.

In one implementation, an electronic device local storage node installs a file. And when the block chain node equipment is triggered to be deployed, the electronic equipment is deployed based on the stored node installation file. For example, the electronic device decompresses a locally stored node device installation file, and deploys the electronic device as a block link node device based on the decompressed file.

Step S202: and importing the target file in the node installation package into a file directory corresponding to the target file based on the script of the node equipment.

A script is a plain text stored program that controls an electronic device to perform a series of specified operations. For example, the script includes a path of each target file, and the function of the path indicates an address of a file directory corresponding to the target file, so that the target file can be imported into the file directory corresponding to the target file according to the path of the target file. Therefore, by adopting the scripts of the node equipment, each process in the node installation package can be controlled to automatically and orderly deploy without manual operation.

As mentioned above, the process of importing the target file in the node installation package into the file directory corresponding to the target file can be understood as a process of initializing the target file in the node installation package, initialization is a preparation before the system runs, for example, a variable is assigned as a default value, and a control is set as a default state, and the like.

In one implementation, the electronic device initializing the directory structure based on the script of the node device may be understood as a process of building a file directory corresponding to the target file based on the target file. Specifically, the electronic device decompresses the node installation package to obtain a plurality of target files; the electronic equipment builds a file directory of the target file indicated by the path based on the path of the target file in the script of the node equipment. The file directory may be divided into a first-level directory, a second-level directory, a multi-level directory, and the like. The multi-level directory can be used for storing different types and different functions of target files in a classified mode.

In an implementation manner, the target file is a system environment variable file, and the manner of importing, by the electronic device, the target file in the node installation package into the file directory corresponding to the target file based on the script of the node device may be: the electronic equipment imports the preset variable in the system environment variable file into a file directory indicated by the path of the system environment variable file based on the path of the system environment variable file in the script of the node equipment. For example, the system environment is a java environment, and the electronic device allocates relevant variables of java to the/etc/profile directory based on a path of the java environment in the script of the node device.

In an implementation manner, the target file is a preset database file, and the manner of importing, by the electronic device, the target file in the node installation package into the file directory corresponding to the target file based on the script of the node device may be: the electronic equipment imports the preset database file into a file directory indicated by the path of the preset database file based on the path of the preset database file in the script of the node equipment. For example, the preset database file includes the base table structure data of the nnodeweb and each service, and the electronic device imports the base table structure data of the nnodeweb and each service into the file directory.

As described above, before the electronic device imports the preset database file into the file directory indicated by the path of the preset database file based on the path of the preset database file in the script of the node device, the electronic device further installs a preset database mysql (structured query language, relational database management system) based on the preset database file; and the electronic equipment establishes connection between the preset address of the preset database and the target address of the path indication of the preset database file in the script of the node equipment. Further, data can be acquired by the target address. For example, based on a preset database file, a preset database is installed and started; establishing connection between a preset address (h127.0.0.1-boot-root) and a target address (127.0.0.1), and displaying that the connection is successful; and importing the nnodeweb and database table structure data of each service and the like into a file directory based on the target address.

According to the method and the device, the target file is initialized, the environment variable is set, and the like, so that preparation work is made for the subsequent deployment of other processes.

Step S203: and modifying the environment parameter in the node installation package into a first target parameter based on the script of the node equipment.

It is to be understood that modifying the environmental parameter may be modifying a configuration file. A configuration file (configurationfile) is a computer program for which parameters and initial settings can be configured.

In one implementation manner, the environment parameters include a first environment parameter and a second environment parameter, and the manner of modifying the environment parameters in the node installation package into the first target parameters based on the script of the node device may be: the electronic equipment modifies the first environment parameter into an identifier of a back-end service; and the electronic equipment modifies the second environment parameter into a network card address of the electronic equipment. The configuration file may be/data/ispace/etc/nodagentsrv. The first environment parameter may be a value of the base _ addr field. The second environment parameter is the value of the interface _ name field. In detail, the electronic device modifies the value of the base _ addr field in the/data/ispace/etc/nodagentsrv.lua file into a backend namely service backend domain name (if the backend namely service has no backend domain name, the value is modified into the IP address of the device where the backend namely service is located); and the electronic equipment takes the value knee of the interface _ name field in the/data/ispace/etc/NodeAgentSrv.

Optionally, if the electronic device is not connected to an external network, the value of the need _ outer _ ip field in the/data/ispace/etc/nodagaentsrv.

Step S204: and operating the first target parameters and importing the target file of the file directory to realize that the electronic equipment is deployed as block link point equipment.

As described above, after the electronic device completes the deployment of each process, the electronic device runs the first target parameter and the target file of the imported file directory to perform the restart proxy service, wherein the restart proxy service can be performed through ① cd/data/ispace/agent, ② killall-9NodeAgentSrv, ③./NodeAgentSrv.

In one implementation, after the electronic device runs the first target parameter and imports the target file of the file directory, the electronic device logs in a preset database; and the electronic equipment imports the preset file in the node installation package into a preset database. For example, the electronic device imports a preset file api-cfg.

According to the embodiment of the application, each service process in the node installation package is automatically deployed based on the script of the node equipment, so that the electronic equipment is deployed as block chain node equipment in a private chain network, and the deployment efficiency of the block chain node equipment is improved.

As described above, the process of the electronic device deploying the electronic device as a block link point device based on the script of the node device can be referred to fig. 3, and fig. 3 is a schematic diagram of a method for block link point deployment according to an embodiment of the present disclosure. Wherein, step 301: the electronic equipment runs the script of the node equipment; step 302: the electronic equipment modifies the configuration file; step 303: restarting the proxy service by the electronic equipment; step 304: the electronic equipment logs in a preset database. The configuration file is/data/ispace/etc/NodeAgentSrv.lua.

The following is a detailed description of the various steps in the deployment of an electronic device as a block-link point device.

In an implementation mode, the method for initializing the target file in the node installation package by the electronic equipment based on the script of the node equipment comprises ① building a file directory corresponding to the target file in the node installation package by the electronic equipment according to the script of the node equipment, ② adding relevant parameters in a system environment variable (java environment) to a file directory (/ etc/profile) corresponding to the system environment variable file based on the path of the target file in the script of the node equipment by the electronic equipment, and ③ leading the preset database file (mysql) to the file directory indicated by the path of the preset database file based on the path of the target file in the script of the node equipment by the electronic equipment.

Optionally, before the electronic device imports the preset database file (mysql) into the file directory indicated by the path of the preset database file based on the path of the target file in the script of the node device, the electronic device may install and start the preset database (mysql); the electronic equipment establishes connection between a preset address (h127.0.0.1-boot-root) of a preset database and a target address (127.0.0.1) of a path indication of a preset database file in a script of the node equipment; and the electronic equipment leads the first library table structure into a preset database through the target address.

In detail, the electronic device initializing the target file in the node installation package mainly includes three parts of initialization. In one aspect, an electronic device initializes a directory structure. For example, the electronic device decompresses the installation package and constructs a file directory corresponding to the target file; the electronic equipment initializes a preset database file configuration. On the other hand, the electronic device initializes a system environment variable file. For example, the electronic device allocates java related variables to/etc/profile. In yet another aspect, the electronic device initializes a preset database file. For example, the electronic device starts a preset database; 127.0.0.1 connection is added to the electronic equipment, so that the effect that mysql-h127.0.0.1-uroot-root connection of the electronic equipment can be successfully achieved; the electronic device imports the nnodeweb and the database table structure data of each service and the like.

In one implementation, a method for an electronic device to modify an environmental parameter in a node installation package may include: the electronic equipment modifies the value of a first environment parameter in the environment parameters into a back-end service identifier; and the electronic equipment modifies the value of the second environment parameter into a network card address of the electronic equipment. Optionally, if the environment of the electronic device does not have an extranet, the value of the need _ outer _ ip field is changed to 0. Wherein, the first environment parameter is a base _ addr field. The backend as a service identifier is a baas background domain name. The second environment parameter is interface _ name field. The network card address of the electronic equipment is the network card name, and the network card name is acquired by ifconfig.

Specifically, the electronic device may modify the value of the base _ addr field to a base background domain name (if there is no domain name, the IP address of the base is changed); the electronic device may change the value of the interface _ name field to the network card name.

Therefore, the electronic device modifies the value of the first environment parameter into the identifier of the back-end service, and modifies the value of the second environment parameter into the network card name of the electronic device. After the electronic device is deployed as the block link point device, the block link point device can perform data transmission and processing through the identifier of the back-end service and the network card name of the electronic device.

In one implementation, the electronic device may restart proxy services via cd/data/ispace/agent, killall-9 nodagentsrv, and/nodagentsrv.

In one implementation, the electronic device logs in a preset database and imports an interface program api _ cfg.

As previously described, the electronic device may be automatically deployed as a block link point device through the various steps described in the embodiment shown in fig. 2. Further, if it is desired to deploy block link point devices having a higher authority level than the common block link point devices, the back-end as-a-service deployment may be performed after the block link point devices are deployed. And then the block chain link point equipment with management authority is obtained through deployment. The block link point device has the management authority, which means that the block link point device can control the authority of the block chain node devices in the block chain network to which the block link point device belongs except the block link point device. Referring to fig. 4, fig. 4 is a schematic flowchart of a backend-as-a-service deployment provided by an embodiment of the present application, where the method may include, but is not limited to, the following steps:

step S401: and acquiring a back-end service installation package and a back-end service script.

The method for acquiring the back-end service installation package and the back-end service script by the electronic device and the process type for acquiring the node installation file by the electronic device may specifically refer to the implementation process described in step S201, which are not described herein again.

The back-end as-a-service installation package includes: mysql-5.7.20.tar. gz and init _ mysql.sh (optional), nbaas. sql (bas database structure), insert _ nbaas _ data. sh (bas insert mysql database data script), etc. tar. gz (bas required configuration file), nbaasrv (bas start binary file), deploy _ nbaas. sh (bas install script). The electronic equipment can automatically execute the operation of deploying the back-end service according to the script of the back-end service.

Step S402: and importing the target file in the back-end service installation package into a file directory corresponding to the target file based on the back-end service script.

In one implementation mode, the electronic equipment leads a second base table structure in a back-end service installation package into a database table management system; and the electronic equipment modifies the first preset address in the second library table structure into a first target address of the electronic equipment, and modifies the second preset address in the second library table structure into a second target address of the electronic equipment. For example, the second table structure is a t _ node table, the first preset address is a Fouter _ IP, the second preset address is a Finner _ IP, the first destination address is an external network IP address corresponding to the electronic device, and the second destination address is an internal network IP address corresponding to the electronic device. The foregoing steps are then: modifying the value of the Fouter _ IP into an external network IP address corresponding to the electronic equipment; the value of Finner _ IP is modified to the intranet IP address.

Step S403: and modifying the environment parameters in the back-end service installation package based on the back-end service script to obtain second target parameters.

In an implementation manner, the manner of modifying the environment parameter in the backend as a service installation package based on the backend as a service script to obtain the second target parameter may be: and the electronic equipment modifies the environmental parameters in the back-end service installation package into a second target address of the electronic equipment. For example, the target file where the environment parameter is located is/data/ispace/etc/nbaaassrv.lua, the environment parameter is a value of mem _ cfg _ IP, and the second target address is an intranet IP address of the device where the back end is served. The steps are as follows: and modifying the value of mem _ cfg _ IP in the/data/ispace/etc/NBaaasSrv.

Step S404: and operating the second target parameter to realize the electronic equipment to be deployed as the block link point equipment.

According to the embodiment of the application, based on the back-end service-as-a-service installation package and the back-end service-as-a-service script, the electronic equipment can be deployed as the block chain node equipment with the management authority, and management of other block chain node equipment in a block chain network to which the block chain node equipment belongs is facilitated.

As described above, referring to fig. 5, a specific implementation process of an electronic device to deploy the electronic device as a block chain node device with management authority based on a script of a back-end service and a back-end service installation package, where fig. 5 is a schematic diagram of a method for deploying the back-end service according to an embodiment of the present application. Wherein, step 501: the electronic equipment runs a preset database file and initializes the preset database; step 502: the electronic equipment leads the base table structure and the data into a preset database which is served at the back end; step 503: the electronic equipment runs the script inserted into the data function to acquire the number of the electronic equipment to be deployed; step 504: the electronic equipment modifies a preset database of the back-end instant service; step 505: the electronic equipment runs a script of a back-end instant service; step 506: the electronic equipment installs cache software; step 507: the electronic device modifies the environmental parameter. It is understood that the execution order of steps 501 to 507 may be changed, and the embodiment of the present application is not limited thereto.

The following is a detailed description of the various steps of back-end as-a-service deployment.

In one implementation, the electronic device runs a back-end, i.e., service, script, and the electronic device initializes a preset database file. The process of initializing the preset database by the electronic device may be as follows: the electronic equipment decompresses a preset compressed file to obtain a first target folder; the electronic equipment imports a first target folder into a first target file; the electronic equipment writes the preset function into the preset configuration directory. The preset is bas _ web.tar.gz, the first target file is a web folder, the first target file is/data/ispace/nbaas, the second preset function is nbaas _ nginx.conf, the preset configuration directory is conf.d, and the default is/etc/nginx/conf.d.

Specifically, the electronic device decompresses the baas _ web.tar.gz to obtain a web folder; the electronic equipment puts the web under/data/ispace/nbaas; the electronic equipment installs nginx according to an installation instruction yum install nginx; the electronic device places nbaas _ nginx. conf under the nginx configuration directory conf.d.

In one implementation, after the electronic device runs the first preset function and initializes the first preset function, the number of the at least one electronic device to be deployed is also obtained. Specifically, the electronic device determines the number of at least one electronic device to be deployed; the electronic equipment generates an insertion data function according to the quantity; the electronic device runs an insert data function.

Optionally, the manner for the electronic device to acquire the number of the electronic devices to be deployed may be: and when the electronic equipment runs the inserting data function, displaying the display area on the display interface. Accordingly, the user may input the number of at least one electronic device to be deployed by entering the number in the display area. Wherein, the display area may be an input box, and then the user may directly input the number of the at least one electronic device to be deployed through the input box. Alternatively, the display area may present an identifier representing the number of the plurality of at least one electronic devices to be deployed, and the user may select the identifier so that the electronic device determines the number of the at least one electronic devices to be deployed. For example, the a flag indicates that the number of the at least one electronic device to be deployed is 2, and the B flag indicates that the number of the at least one electronic device to be deployed is 21, the user may select the a flag, so that the electronic device determines that the number of the at least one electronic device to be deployed is 2.

In one implementation, a method for an electronic device to modify a preset database of a back-end as-a-service may include: and the electronic equipment modifies the first preset address in the second library table structure into a first target address of the electronic equipment, and modifies the second preset address in the second library table structure into a second target address of the electronic equipment. The second base table structure comprises a t _ node table, the first preset address is Fouter _ IP, the second preset address is Finner _ IP, the first target address is an external network IP address of the electronic equipment, and the second target address is an internal network IP address of the electronic equipment.

In detail, the electronic device may modify the value of Fouter _ IP in the t _ node table in the Baas preset database to the external network IP address of the electronic device, and modify the value of Finner _ IP in the t _ node table in the Baas preset database to the internal network IP address of the electronic device.

Therefore, the electronic device modifies the address of the t _ node table in the preset database of the back-end instant service into the external network IP address or the internal network IP address of the electronic device. After the electronic device is deployed as the block link point device, the block link point device may obtain data in the preset database which is served at the back end directly based on the external network IP address or the internal network IP address, and then deploy the preset database which is served at the back end as the database of the block link point device.

In one implementation, a method for an electronic device to install caching software based on back-end as-a-service may include: the electronic equipment installs the cache software based on the installation command; and the electronic equipment modifies the third preset address in the target code into a second target address based on the operation command. The cache software can be memcached, the target code can be memcached-d-m1024-u root-l 172.16.0.4-P11211-c 1024-P/tmp/memcached, the third preset address can be 172.16.0.4, and the second target address can be an intranet IP address of a machine where the bas is located.

In detail, the electronic device runs an installation command yum install memcached, and installs the memcached; and the electronic agency runs an operation command, and replaces the 172.16.0.4 address in the memcached-d-m1024-u root-l 172.16.0.4-P11211-c 1024-P/tmp/memcached.

In one implementation, the electronic device may also modify the configuration file. In detail, the electronic device modifies/data/ispace/etc/NBaaasSrv.lua, and modifies the value of mem _ cfg _ IP to the intranet IP address of the machine where the baas is located.

The electronic equipment of the embodiment of the application adopts the script of the back-end service, deploys the back-end service based on the back-end service installation package, and can be automatically deployed as the block link point equipment with the management authority in the private chain network.

The method for deploying the block chain node equipment provided by the application further comprises foreground deployment besides the background deployment. The foreground deployment can be divided into the foreground deployment of a back-end service management platform and the premise deployment of a node equipment management platform. Referring to fig. 6, fig. 6 is a method for foreground deployment of a block link point device according to an embodiment of the present application, where the method includes, but is not limited to, the following steps:

step S601: the electronic equipment deploys the back end, namely the foreground of the service management platform.

The installation file of the foreground of the back-end service management platform comprises a back-end service foreground installation package and a nginx configuration file required by the back-end service. Specifically, the electronic device decompresses the baas _ web.tar.gz to obtain a web folder, and puts the web under/data/ispace/nbaas; the electronic equipment installs nginx based on an installation program yum install nginx; the electronic device places nbaas _ nginx. conf under the nginx configuration directory conf.d.

Step S602: and the electronic equipment deploys the block chain node equipment management platform foreground.

The installation file of the foreground of the block chain node device management platform comprises an nginx configuration file required by the block chain node device. Specifically, the electronic device installs nginx based on an installer yum install nginx; the electronic device places websrv _ nginx. conf under the nginx configuration directory conf.d.

Therefore, the deployment of the block chain node equipment is integrally completed by deploying the foreground and the background of the back-end service as well as the foreground and the background of the block chain nodes.

The electronic equipment can be deployed as block link point equipment through the embodiment. After the block link point device is deployed, the foreground can be authenticated, logged in, and the like, or a detection mechanism can be used to check whether some processes in the deployment process of the background are completed. For example, it may check whether the blockchain node device is successfully deployed, check whether the backend, i.e., service, is successfully deployed, start a chain flow, and check whether the chain is successfully created.

Based on the completion of the deployment of the block link point devices, several viewing operations to the foreground or the background are described in detail below.

In one implementation, a validation use of the foreground can be made. Wherein, the foreground comprises a Baas management foreground and a node management foreground. Specifically, the Baas management foreground is authenticated by accessing the outer network IP of Baas, for example, 16002 for Baas. Specifically, the node management foreground is authenticated by accessing the node extranet IP, for example, the extranet IP of the node is 16004.

In one implementation, the tile chain node device may be logged in with a default username and a default password. For example, the default user name is tend @ qq.com, and the default password is admin @ 123.

It will be appreciated that modifications may be made to the username and password. Optionally, the manner of modifying the user name may be: and replacing the Femail value in the t _ mch table in the preset database (BaaS background corresponds to the nbaas library, and the node background corresponds to the nnodeweb library) with a new user name. Optionally, the manner of modifying the password may be: and replacing Fpasssd fields and Fpasssd 2 fields in a t _ mch table in a preset database (BaaS background corresponds to the nbaas library, and node background corresponds to the nnodeweb library) with sha1 values corresponding to the new password.

For example, to modify the password admin @123 to change @456 may be accomplished by replacing sha1(change @456) with e2c90ed7d5dcc7fed953e00bbab39f183885a29 e; fpasssw field and Fpasssw 2 field values of the t _ mch table in the database are replaced by e2c90ed7d5dcc7fed953e00bbab39f183885a29 e.

In one implementation, it may be checked whether the blockchain node device deployment was successful. Specifically, whether ispace, software and trustsql folders exist under the data/directory can be detected; whether mysql-h127.0.0.1-uroot-proot can be connected or not; after mysql is connected, whether the show databases have nnodeweb or not is judged; iss _ db, digit _ asset _ db library; whether the ps-ef | grep NodeAgentSrv has a process or not; whether ps-ef | grep DigitAssetService has a process; whether ps-ef | grep ISSService has a process. If the detection is passed, the block chain node equipment can be considered to be successfully deployed.

In one implementation, it may be checked whether the back-end as-a-service deployment was successful. Specifically, it can be detected whether ps-ef | grep NBaasSrv has a process; whether the ps-ef | grep memcache has a process or not; whether mysql-h127.0.0.1-uroot-proot can be connected or not; register mysql, check if select from t _ mch has a value, select from t _ chain has a value, select from t _ node checks if Fmodify _ time is the current time.

In one implementation, a blockchain process may be initiated, and in particular, an interface call interface may be logged, and then a blockchain may be initiated, where the interface call interface may be logged through an L ogin interface, and the blockchain call interface may be initiated through a StartChain interface, as shown in fig. 7, fig. 7 is a schematic diagram of an interface provided by an embodiment of the present application.

Optionally, the method for logging in the interface call interface may include: uneme (corresponding to the field of fe mail in the database nbaas.t _ mch table, default value "tend @ qq.com"); timestamp (available at https:// tool. lu/timestamp); pwd 2; (ii) a weakpasswd; pwd (the value calculated by sha1 for the "diameter | timeframe | passsword" string, where diameter and timeframe correspond to the values in diameter and timeframe described above, respectively, and passsword corresponds to the Fpassswd field in the database nbaas.t _ mch table, where the default value of Fpassswd field may be "23 d42f5f3f66498b2c8ff4c20b8c5ac826e 47146").

Optionally, the block chain is started in a manner that: let the value of chain _ id be "ch _ tencent _ prchain".

In one implementation, after the blockchain is started, whether the blockchain is successfully created can be checked. Specifically, it is possible to check whether the Fmodify _ time is the current time and to check whether the value of the state in the Fstatics field is 2 by the program select from t _ chain _ node.

In one implementation, data may be written to the blockchain if the blockchain creation is complete. Specifically, different business operations are performed by calling an upper application service interface. For example, the calling mode may be http:// { node _ ip: node _ port }/{ interface }, where node _ ip is an external network ip of a node (if the service of the service is an internal network ip), node _ port is a port corresponding to the service, and interface is an interface name to be called under the corresponding service, and parameters are sent in a post mode. At present, in an automation deployment, two services including digital assets and information sharing are included, wherein the digital assets mainly include scenarios such as issuing, transferring, and cashing. The information sharing mainly comprises scenes such as addition, inquiry and the like.

It will be appreciated that many problems are faced in performing block-linked point device deployment, a few of which may arise, to name a few.

For example, when verifying whether the block chain is successfully started, it is found that the value of the state in the Fstatics field is 3, which indicates that the common port at the bottom layer of each node is not communicated, and it is required to ensure that the nodes can ping communication and the ports 15900 to 17000 can telnet communication.

As another example, if the value of state in the Fstatics field is always 0, then the following operations may be performed: determining whether the start chain operation has been completed; entering a node/data/trustql/ch _ tencent _ prchain directory, and checking whether wrapper.log has 'Unable to start JVM'; if there is the above problem, check the lowest of the/etc/profile, and see if there is one

JAVA_HOME＝/data/software/jdk1.8.0；

CLASSPATH＝$JAVA_HOME/lib/、PATH＝$PATH:$JAVA_HOME/bin；

export PATH JAVA_HOME CLASSPATH；

PATH＝$PATH:/data/software/mysql-5.7.20:/data/software/mysql-5.7.20/bin；

export PATH；

If not, adding is needed; checking each block link point device, and executing: source/etc/profile, cd/data/trustql/ch _ tencent _ prchain/bin,/trustql start.

As another example, if after restarting the server, mysql is found not to be connected, then/data/software/mysql-5.7.20/bin/mysql ld may be executed.

As another example, a method of viewing a log. Under the configuration file/data/ispace/etc., log _ sys, log _ app and log _ sql in the configuration file of each service correspond to log configuration options, and the higher the level is (1-5), the more the printing information is. Log files run logs under directory/data/ispace/xxx on each service binary.

As can be seen, after the background deployment and foreground deployment of the block chain node device described in connection with the embodiment of the present application are successful, the problems that may be faced by each process operation and when the block chain node device is used are checked. The detection of each link of block chain node point equipment deployment can be realized, and the successful deployment of the electronic equipment as the block chain node point equipment is ensured.

Referring to fig. 8, fig. 8 is a schematic structural diagram of a block link point deployment apparatus 80 according to an embodiment of the present disclosure, where the block link point deployment apparatus 80 is used to execute steps executed by an electronic device in the method embodiment corresponding to fig. 2 and fig. 4, and the block link point deployment apparatus 80 may include a receiving module 801, an importing module 802, a modifying module 803, and an operating module 804. Each module in the block link point deployment device 80 is specifically configured to:

a receiving module 801, configured to obtain a node installation file, where the node installation file includes a node installation package and a script of a node device;

an import module 802, configured to import the target file in the node installation package into a file directory corresponding to the target file based on the script of the node device;

a modifying module 803, configured to modify an environmental parameter in the node installation package into a first target parameter based on the script of the node device;

the running module 803 is configured to run the first target parameter and the target file of the imported file directory, so as to implement deployment of the electronic device as a block link point device.

In one implementation manner, before importing, based on the script of the node device, the target file in the node installation package into the file directory corresponding to the target file, the import module 802 is further configured to: the electronic equipment decompresses the node installation package to obtain a target file;

the electronic equipment builds a file directory of the target file indicated by the path based on the path of the target file in the script of the node equipment.

In one implementation, the target file is a system environment variable file;

the import module 802 is specifically configured to, when importing the target file in the node installation package into the file directory corresponding to the target file based on the script of the node device:

the electronic equipment imports the preset variable in the system environment variable file into a file directory indicated by the path of the system environment variable file based on the path of the system environment variable file in the script of the node equipment.

In one implementation, the target file is a preset database file;

the electronic equipment imports the preset database file into a file directory indicated by the path of the preset database file based on the path of the preset database file in the script of the node equipment.

In one implementation manner, the importing module 802 is further configured to, before presetting a path of the database file in the script based on the node device and importing the preset database file into the file directory indicated by the path of the preset database file, further:

installing a preset database based on a preset database file;

establishing connection between a preset address of a preset database and a target address of a path indication of a preset database file in a script of node equipment;

and importing the first library table structure into a preset database through the target address.

In one implementation, the environmental parameters include a first environmental parameter and a second environmental parameter;

the modification module 803, when modifying the environmental parameter included in the node installation package to be the first target parameter based on the script of the node device, is further configured to:

modifying the first environment parameter into an identifier of the back-end service;

and modifying the second environment parameter into a network card address of the electronic equipment.

In one implementation, after executing the first target parameter and the target file of the import file directory, the executing module 804 is further configured to:

logging in a preset database;

and importing the preset file in the node installation package into a preset database.

In one implementation, after the running module 804 runs the first target parameter and the target file of the import file directory, the receiving module 801 is further configured to:

acquiring a back-end service installation package and a back-end service script;

an import module 802, configured to import, based on a back-end as-a-service script, a target file in a back-end as-a-service installation package into a file directory corresponding to the target file;

a modifying module 803, configured to modify, based on the script of the back-end service-as-a-service, the environment parameter in the back-end service-as-a-service installation package to obtain a second target parameter;

an operation module 804, configured to operate the second target parameter, so as to implement deployment of the electronic device as the block link point device, where the electronic device deployed as the block link point device has a management right, and the management right indicates that the block link node device has a right to manage node devices in a block link network to which the block link node device belongs, except for the block link point device.

In one implementation, when importing the file directory corresponding to the target file into the backend service installation package based on the script of the backend service, the import module 802 is further configured to:

importing a second library table structure in the back-end service installation package into a preset database;

and modifying the first preset address of the second library table structure into a first target address of the electronic equipment, and modifying the second preset address in the second library table structure into a second target address of the electronic equipment.

In one implementation, when modifying the environment parameter in the backend as a service installation package based on the script of the backend as a service, the modifying module 803 is specifically configured to:

and modifying the environment parameters in the back-end service installation package into a second target address of the electronic equipment.

It should be noted that details that are not mentioned in the embodiment corresponding to fig. 8 and specific implementation manners of the steps executed by each module may refer to the embodiments shown in fig. 2 and fig. 4 and the foregoing details, and are not described again here.

Referring to fig. 9, fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure. The electronic device 90 comprises a processor 901, a memory 902 and a communication interface 903, wherein the processor 901 and the memory 902 are connected by one or more communication buses.

The processor 901 is configured to support the electronic device to execute the corresponding functions of the electronic device in the methods described in fig. 2 and fig. 4. The processor 901 may be a Central Processing Unit (CPU), a Network Processor (NP), a hardware chip, or any combination thereof.

The memory 902 is used to store program codes and the like. The Memory 902 may include volatile Memory (volatile), such as Random Access Memory (RAM); the Memory 902 may also include a non-volatile Memory (non-volatile Memory), such as a Read Only Memory (ROM), a flash Memory (flash Memory), a Hard Disk Drive (HDD) or a Solid State Drive (SSD); the memory 902 may also comprise a combination of the above-described types of memory.

In the embodiment of the present application, the electronic device 90 includes a plurality of interfaces, wherein an interface for transmitting data and an interface for receiving data may not be the same interface.

The processor 901 may call program code stored in the memory 902 to perform the following operations:

a communication interface 903, configured to obtain a node installation file, where the node installation file includes a node installation package and a script of a node device;

a processor 901, configured to import an object file in a node installation package into a file directory corresponding to the object file based on a script of a node device;

modifying the environmental parameters in the node installation package into first target parameters based on the script of the node equipment;

and operating the first target parameters and importing the target file of the file directory to realize that the electronic equipment is deployed as block link point equipment.

In one implementation, before importing the target file in the node installation package into the file directory corresponding to the target file based on the script of the node device, the processor 901 is further configured to: the electronic equipment decompresses the node installation package to obtain a target file;

In one implementation, the target file is a system environment variable file;

when importing the target file in the node installation package into the file directory corresponding to the target file based on the script of the node device, the processor 901 is specifically configured to:

In one implementation, the target file is a preset database file;

In one implementation, before the processor 901 presets a path of the database file in the script based on the node device and imports the preset database file into the file directory indicated by the path of the preset database file, the processor is further configured to:

installing a preset database based on a preset database file;

the processor 901, when modifying the environment parameter included in the node installation package to be the first target parameter based on the script of the node device, is further configured to:

In one implementation, the processor 901, after running the first target parameter and importing the target file of the file directory, is further configured to:

logging in a preset database;

In one implementation, after the processor 901 runs the first target parameter and the target file of the import file directory, the communication interface 903 is further configured to:

a processor 901, configured to import an object file in a backend as a service installation package into a file directory corresponding to the object file based on a backend as a service script;

modifying the environment parameters in the back-end service installation package based on the back-end service script to obtain second target parameters;

and operating the second target parameter to realize that the electronic equipment is deployed as the block chain node equipment, wherein the electronic equipment deployed as the block chain node equipment has management authority, and the management authority indicates that the block chain node equipment has authority to manage node equipment except the block chain node equipment in a block chain network to which the block chain node equipment belongs.

In one implementation, when importing a file directory corresponding to an object file into a backend service-as-a-service installation package based on a script of the backend service, the processor 901 is further configured to:

In one implementation, when modifying the environment parameter in the backend as a service installation package based on the script of the backend as a service, the processor 901 is specifically configured to:

Further, the processor 901 may also cooperate with the memory 902 to execute operations corresponding to the electronic device in the method embodiments shown in fig. 2 and fig. 4, which may specifically refer to the description in the method embodiments and are not described herein again.

Embodiments of the present application further provide a computer-readable storage medium, which can be used to store a computer program used by the electronic device in the embodiments shown in fig. 2 and fig. 4, and which contains a program designed for executing the electronic device in the embodiments described above.

The computer readable storage medium includes, but is not limited to, flash memory, hard disk, solid state disk.

The embodiment of the present application further provides a computer program product, and when the computer program product is executed by a computer device, the method for deploying block link point devices designed for electronic devices in the foregoing embodiments of fig. 2 and 4 may be executed.

There is also provided in an embodiment of the present application a chip, including a processor and a memory, where the memory is used to store a computer program, the processor is used to call and run the computer program from the memory, and the computer program is used to implement the method in the above method embodiment.

Those of ordinary skill in the art would appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

The computer instructions may be stored on or transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center via a wired (e.g., coaxial, fiber optic, digital subscriber line (DS L)) or wireless (e.g., infrared, wireless, microwave, etc.) manner.

The above description is only for the specific embodiments of the present invention, but the scope of the present invention is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present invention, and all the changes or substitutions should be covered within the scope of the present invention. Therefore, the protection scope of the present invention shall be subject to the protection scope of the appended claims.

Claims

1. A method of block link point device deployment, the method comprising:

the method comprises the steps that electronic equipment obtains a node installation file, wherein the node installation file comprises a node installation package and a script of node equipment;

and the electronic equipment runs the first target parameter and imports a target file of the file directory to realize that the electronic equipment is deployed as block link point equipment.

2. The method according to claim 1, wherein before the electronic device imports the target file in the node installation package into the file directory corresponding to the target file based on the script of the node device, the method further comprises:

the electronic equipment decompresses the node installation package to obtain the target file;

and the electronic equipment constructs a file directory of the target file indicated by the path based on the path of the target file in the script of the node equipment.

3. The method of claim 2, wherein the target file is a system environment variable file;

the electronic device imports the target file in the node installation package into the file directory corresponding to the target file based on the script of the node device, and the method comprises the following steps:

and the electronic equipment imports the preset variable in the system environment variable file into a file directory indicated by the path of the system environment variable file based on the path of the system environment variable file in the script of the node equipment.

4. The method of claim 2, wherein the target file is a predetermined database file;

and the electronic equipment imports the preset database file into a file directory indicated by the path of the preset database file based on the path of the preset database file in the script of the node equipment.

5. The method according to claim 4, wherein the electronic device, based on the path of the preset database file in the script of the node device, before importing the preset database file into the file directory indicated by the path of the preset database file, further comprises:

the electronic equipment installs the preset database based on the preset database file;

the electronic equipment establishes connection between a preset address of the preset database and a target address indicated by a path of the preset database file in the script of the node equipment;

and the electronic equipment leads a first library table structure into the preset database through the target address.

6. The method of claim 1, wherein the environmental parameters comprise a first environmental parameter and a second environmental parameter;

the electronic device modifies the environmental parameter in the node installation package into a first target parameter based on the script of the node device, and the method comprises the following steps:

the electronic equipment modifies the first environment parameter into an identifier of a back-end service;

and the electronic equipment modifies the second environment parameter into a network card address of the electronic equipment.

7. The method of claim 1, wherein after the electronic device runs the first target parameter and imports the target file of the file directory, further comprising:

the electronic equipment logs in the preset database;

and the electronic equipment imports a preset file in the node installation package into the preset database.

8. The method of claim 1, wherein after the electronic device runs the first target parameter and imports the target file of the file directory, further comprising:

the electronic equipment acquires a back-end service installation package and a back-end service script;

the electronic equipment imports the target file in the back-end service installation package into a file directory corresponding to the target file based on the back-end service script;

the electronic equipment modifies the environmental parameters in the back-end service installation package based on the back-end service script to obtain second target parameters;

and the electronic equipment runs the second target parameter to realize that the electronic equipment is deployed as block chain node point equipment, wherein the electronic equipment deployed as the block chain node point equipment has management authority which indicates that the block chain node equipment has authority for managing node equipment in a block chain network to which the block chain node equipment belongs, except the block chain node point equipment.

9. The method according to claim 8, wherein the importing, by the electronic device, the file directory corresponding to the target file into the target file in the backend-as-a-service installation package based on the backend-as-a-service script comprises:

the electronic equipment leads a second library table structure in the back-end service installation package into the preset database;

and the electronic equipment modifies the first preset address in the second base table structure into the first target address of the electronic equipment and modifies the second preset address in the second base table structure into the second target address of the electronic equipment.

10. The method of claim 8, wherein the electronic device modifies the environment parameters in the back-end service-as-installed package based on the back-end service-as-installed script, comprising:

and the electronic equipment modifies the environmental parameters in the back-end service installation package into the second target address of the electronic equipment.