CN114489690A

CN114489690A - Distributed system deployment method and device, electronic equipment and storage medium

Info

Publication number: CN114489690A
Application number: CN202111495359.7A
Authority: CN
Inventors: 任俊龙; 张�浩; 王芳; 林文辉; 解军伟
Original assignee: Aisino Corp
Current assignee: Aisino Corp
Priority date: 2021-12-09
Filing date: 2021-12-09
Publication date: 2022-05-13

Abstract

The embodiment of the application provides a distributed system deployment method, a distributed system deployment device, electronic equipment and a storage medium, wherein the type of a CPU basic framework of a target storage device is determined based on identification information of the CPU basic framework of the target storage device, and can be accurately judged only according to a detection algorithm of the CPU basic framework in first script information.

Description

Distributed system deployment method and device, electronic equipment and storage medium

Technical Field

The present application relates to the field of information technology, and in particular, to a method and an apparatus for deploying a distributed system, an electronic device, and a storage medium.

Background

With The development of The information technology application innovation industry, The types of computer Central Processing Unit (CPU) infrastructures are becoming more abundant, such as an Advanced RISC Machine (ARM) architecture, an X86(The X86) architecture, a Microprocessor with Interlocked pipelined Microprocessor (MIPS) architecture, and The like; further, cloud computing applications developed based on the above-described various infrastructures are also increasing.

The cloud computing technology is a distributed computing mode based on the internet, and the implementation of the cloud computing technology needs the support of a whole set of technical architecture, and comprises the following steps: network, server, storage, virtualization, etc. With the gradual compatibility of the cloud computing technology with various CPU infrastructures such as an ARM architecture, an X86 architecture, and an MIPS architecture, the data processing result obtained by using the cloud computing technology needs to be stored in a distributed manner according to the type of the CPU infrastructure.

In the related art, the distributed storage system may be implemented in a cluster form based on a wireless communication technology, that is, storage devices adopting different types of CPU infrastructures are integrated, so as to implement storage resources that are deployed in a distributed form and can be dynamically expanded.

For distributed storage requirements, aiming at different types of CPU basic architectures, control equipment respectively carries out secret-free communication with each storage equipment according to Internet Protocol (IP) addresses of the storage equipment which are recorded in advance and need to carry out distributed storage, so that each storage equipment respectively builds a corresponding local source; secondly, each storage device downloads configuration files of all types of CPU basic architectures from the control device based on respective local sources; finally, each storage device screens out matched target configuration files from the obtained configuration files based on the type of the local CPU basic architecture and performs storage resource configuration; in this way, the control device and each storage device cooperate with each other to complete the deployment of the distributed storage system.

However, in the related art, the above method has the following disadvantages:

1. the profile distribution is inefficient.

The control device needs to perform secret-free communication with a large number of storage devices, and distributes configuration files of all types of CPU basic architectures to the storage devices respectively, so that when the number of the storage devices and the types of the CPU basic architectures are large, a large number of distribution operations can bring serious operation load to the control device; and if the distribution is not timely, the configuration of the storage resource is affected.

2. The operation and maintenance cost is high.

In the related technology, the control device performs secret-free communication with each storage device according to the pre-recorded IP addresses of each storage device which needs distributed storage, so that when the number of newly-added storage devices is large, the control device cannot distribute configuration files of all types of CPU basic architectures to the newly-added storage devices according to the pre-recorded IP addresses; therefore, the newly added storage device can only actively download the target configuration file from the network side and perform storage resource configuration, so that the deployment of the distributed storage system can be completed; thus, the deployment, operation and maintenance costs of the distributed storage system are significantly increased due to the existence of a large number of newly-added storage devices.

Disclosure of Invention

The application provides a distributed system deployment method, a distributed system deployment device, electronic equipment and a storage medium, which are used for issuing corresponding resource configuration files to storage equipment of different CPU basic architectures, so that the distribution efficiency of the resource configuration files is improved.

In a first aspect, an embodiment of the present application provides a method for deploying a distributed system, where the method includes:

and when the storage equipment to be deployed is determined to exist, acquiring the identification information of the CPU infrastructure of the storage equipment.

The type of the CPU infrastructure of the storage device is determined based on the identification information of the CPU infrastructure.

And acquiring a corresponding resource configuration file based on the type of the CPU infrastructure.

And sending the resource configuration file to the storage device so that the storage device completes the configuration of the storage resource based on the obtained resource configuration file.

In a second aspect, an embodiment of the present application further provides a distributed system deployment apparatus, where the apparatus includes:

the obtaining module is used for obtaining the identification information of the CPU basic framework of the storage device when the storage device to be deployed is determined to exist.

The processing module is used for determining the type of the CPU basic framework of the storage device based on the identification information of the CPU basic framework; and acquiring a corresponding resource configuration file based on the type of the CPU infrastructure.

And the communication module is used for sending the resource configuration file to the storage device so that the storage device completes the configuration of the storage resource based on the obtained resource configuration file.

In an optional embodiment, before acquiring the identification information of the CPU infrastructure of the storage device when it is determined that the storage device to be deployed exists, the acquisition module is further configured to:

and acquiring a preset original configuration file, and respectively modifying the original configuration file correspondingly based on the set CPU basic framework of each type to acquire a corresponding resource configuration file.

And respectively determining the CPU basic architectures of various types, and the file installation mode and the data compression mode which respectively correspond to the CPU basic architectures.

And respectively compressing the resource configuration files corresponding to the CPU basic architectures of various types by adopting corresponding data compression modes, and respectively generating target installation packages carrying the corresponding file installation modes based on the obtained compressed data packages.

In an optional embodiment, before obtaining the identification information of the CPU infrastructure of the storage device when it is determined that the storage device to be deployed exists, the processing module is further configured to:

and respectively setting detection algorithms corresponding to the CPU infrastructures of all types based on the set CPU infrastructures of all types.

And generating first script information by adopting a fusion processing mode based on various set detection algorithms.

When it is determined that the storage device to be deployed exists, and the identification information of the CPU infrastructure of the storage device is acquired, the processing module is specifically configured to:

and acquiring the IP address of the Internet protocol of the storage equipment by a Dynamic Host Configuration Protocol (DHCP).

And establishing communication connection with the storage device based on the obtained IP address.

Based on the communication connection, identification information of a CPU infrastructure of the storage device is acquired.

In an optional embodiment, when sending the resource configuration file to the storage device to enable the storage device to complete configuration of the storage resource based on the obtained resource configuration file, the communication module is specifically configured to:

and sending the resource configuration file to the storage equipment so that the storage equipment builds a corresponding local source based on a CPU infrastructure of the storage equipment, loads the resource configuration file through the local source, and configures corresponding storage resources based on a file installation mode recorded in the resource configuration file.

In a third aspect, an embodiment of the present application further provides an electronic device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, where the computer program, when executed by the processor, causes the processor to implement any one of the methods for distributed system deployment in the first aspect.

In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, the storage automation deployment method of the first aspect is implemented.

For technical effects brought by any one implementation manner in the second aspect to the fourth aspect, reference may be made to technical effects brought by a corresponding implementation manner in the first aspect, and details are not described here.

In the embodiment of the application, the type of the CPU infrastructure of the target storage device is analyzed based on the identification information of the CPU infrastructure of the target storage device, so that the corresponding resource configuration file is obtained according to the type of the CPU infrastructure of the target storage device, and the resource configuration file is sent to the target storage device. The type of the CPU infrastructure of the target storage device is analyzed based on the identification information of the CPU infrastructure of the target storage device, and the type of the CPU infrastructure of the target storage device can be accurately judged only according to the detection algorithm of the CPU infrastructure in the first script information.

Drawings

FIG. 1 is a diagram illustrating a system architecture to which embodiments of the present application are applicable;

FIG. 2 is a flowchart illustrating a method for generating a target installation package according to an embodiment of the present application;

FIG. 3 is a diagram illustrating an example of generating a configuration resource file provided by an embodiment of the present application;

fig. 4 is a flowchart illustrating a method for generating first script information according to an embodiment of the present application;

fig. 5 is a schematic diagram illustrating generation of first script information provided by an embodiment of the present application;

FIG. 6 is a flow chart illustrating a method for distributed system deployment according to an embodiment of the present application;

fig. 7 is a schematic diagram illustrating an IP address obtaining method provided by an embodiment of the present application;

fig. 8 is a schematic structural diagram illustrating a distributed system deployment apparatus provided by an embodiment of the present application;

fig. 9 schematically shows a structural diagram of an electronic device provided in an embodiment of the present application.

Detailed Description

In order to improve the efficiency of distributing the resource configuration file, in the embodiment of the application, the control device presets and stores the detection algorithm and the resource configuration file corresponding to each type of the CPU infrastructure, and determines the type of the CPU infrastructure of the target storage device based on the identification information of the CPU infrastructure of the target storage device, so as to send the corresponding resource configuration file to the target storage device.

In order to make the objects, technical solutions and advantages of the present application more clear, the present application will be further described in detail with reference to the accompanying drawings. The particular methods of operation in the method embodiments may also be applied to apparatus embodiments or system embodiments. It should be noted that "a plurality" is understood as "at least two" in the description of the present application. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. A is connected with B and can represent: a and B are directly connected and A and B are connected through C. In addition, in the description of the present application, the terms "first," "second," and the like are used for descriptive purposes only and are not intended to indicate or imply relative importance nor order to be construed.

For a better understanding of the embodiments of the present application, technical terms referred to in the embodiments of the present application will be described first below.

(1) The first installation package is installed on the control device. The first installation package is a set carrying an original configuration file. For convenience, the first installation package is described as an infrastructure installation package as an example.

(2) And the target installation package is generated by the control device. The target installation package is a collection of resource configuration files corresponding to a CPU infrastructure carrying the target storage device.

(3) The first script information is generated by the control device. The first script information specifically includes detection algorithms corresponding to the respective types of CPU infrastructures.

(4) And the second script information is sent out by the storage device. The second script information specifically includes identification information of a CPU infrastructure of the storage device. For convenience, the first script information is described as the shell script information as an example.

It should be noted that the naming manner of the technical terms described above is only an example, and the embodiment of the present application does not limit the naming manner of the technical terms described above.

The technical solutions in the embodiments of the present invention will be described clearly and completely with reference to the accompanying drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

Fig. 1 is a diagram illustrating a system architecture to which the embodiment of the present application is applicable, and as shown in fig. 1, the distributed system includes a control device 101 and storage devices (102a, 102 b). The control device 101 and the storage devices (102a, 102b) can exchange information in a wireless communication mode or a wired communication mode.

Illustratively, the control device 101 may communicate with the storage devices (102a, 102b) by accessing the network via short-range wireless communication, including, for example, wireless communication network technology (Wi-Fi).

The number of the control devices and the other devices is not limited in the embodiment of the present application, and fig. 1 only describes one control device as an example.

The control device 101 is configured to acquire identification information of a Central Processing Unit (CPU) infrastructure of the storage device when it is determined that the storage device to be deployed exists; determining the type of the CPU infrastructure of the storage device based on the identification information of the CPU infrastructure; acquiring a corresponding resource configuration file based on the type of the CPU infrastructure; and sending the resource configuration file to the storage device so that the storage device completes the configuration of the storage resource based on the obtained resource configuration file.

In some embodiments of the present application, the control device 101 may be a control device that installs an ansable installation package.

The storage device (102a, 102b) is a device that can provide voice and/or data connectivity to a user, including handheld devices, in-vehicle devices, etc. with wireless connectivity.

Illustratively, the storage device may be: the mobile internet device comprises a mobile phone, a tablet computer, a notebook computer, a palm computer, a Mobile Internet Device (MID), a wearable device, a Virtual Reality (VR) device, an Augmented Reality (AR) device, a wireless storage device in industrial control, a wireless storage device in unmanned driving, a wireless storage device in a smart grid, a wireless storage device in transportation safety, a wireless storage device in a smart city, or a wireless storage device in a smart home.

In some embodiments of the present application, the storage devices (102a, 102b) may be storage devices of different CPU infrastructures, which specifically include an ARM architecture, an X86 architecture, a MIPS architecture, and the like. It should be noted that, although the CPU infrastructures of the storage devices may be different, the building of the local source and the deployment of the distributed storage system Ceph cluster, that is, the configuration of the storage resource, may be performed.

Further, based on the system architecture, referring to fig. 2, in the embodiment of the present application, a generation process of the target installation package includes the following specific steps:

s201: and acquiring a preset original configuration file.

Specifically, when step S201 is executed, the control device first installs the first installation package locally, and then decompresses the first installation package by using a corresponding file decompression method according to the file format of the compressed file of the first installation package, so as to finally obtain the original configuration file.

For example, the compressed file format of the encrypted installation package is a Rochelle Archive (RAR) format, and the compressed file format of the encrypted installation package obtained by the control device is the RAR format. And then, the control device decompresses the encrypted installation package by adopting a decompression mode of RAR compressed files so as to ensure that the complete original configuration file is obtained from the encrypted installation package.

The raw configuration file refers to a resource configuration file used to complete distributed storage of data on the storage device. Optionally, the original configuration file is a resource configuration file of the distributed storage Ceph cluster. For example, the resource configuration file of a Ceph cluster in a computer at least includes a configuration file of a distributed Storage Monitor Ceph Monitor, a configuration file of a distributed Storage manager Ceph Managers, and a configuration file of a distributed Storage Object Storage Daemon (Ceph OSD), and further, when a control device performs distributed Storage on data and calls the configuration file in the Ceph cluster, a Metadata service is required to be relied on, so a configuration file of a distributed Storage Metadata Server (Ceph Metadata Server, Ceph MDS) is required.

The mapping used by the Ceph Monitor to maintain the Ceph cluster state includes Monitor mapping, Manager mapping, OSD mapping, MDS mapping, and hash-based data distribution (CRUSH) mapping. These mappings are the key cluster states required for the Ceph daemons to coordinate with each other; and also takes care of authentication between the management daemon and the computer. At least 3 Ceph monitors are typically required to achieve redundancy and high availability.

The Ceph Manager is used for tracking the running-time index and the current state of the Ceph cluster, including the storage utilization rate, the current performance index and the system load; a python-based module is also hosted to manage and publish Ceph cluster information, including a Web-based Ceph dashboard and a Representational State Transfer Application Programming Interface (REST API). At least 3 Ceph managers are usually required to achieve high availability.

The Ceph OSD is used to store data in the form of objects on the physical disks of each node in the cluster, handle data replication, recovery, rebalancing, and provide some monitoring information to the Ceph Monitor and Ceph Manager by checking heartbeat information of other Ceph OSD daemons. At least 3 Ceph OSDs are typically required to achieve redundancy and high availability.

The Ceph MDS is used for memory caching of metadata and quickens the access of the metadata; metadata of a file system is saved (names and inode numbers of subdirectories and subfiles are saved in an object); the Cephfs log is also saved and is used for restoring the metadata cache in the Ceph MDS; when the Ceph MDS is restarted, the metadata that was previously cached is loaded from the Ceph OSD in a replay manner.

The Ceph cluster stores data as an object in a logical storage pool, determines which Placement Group (PG) should contain the object using the CRUSH algorithm, and further calculates which Ceph OSD daemon should store the PG, thereby enabling dynamic expansion, rebalancing, and restoration of the Ceph cluster.

S202: after the preset original configuration file is obtained, the original configuration file is correspondingly modified based on the set CPU basic framework of each type, and a corresponding resource configuration file is obtained.

For convenience of description, in the embodiment of the present application, at least any one of the set CPU infrastructures of each type is taken as an example to perform relevant description, and the modification processes of the original configuration files of the CPU infrastructures of other types all adopt similar manners, which will not be described again.

Specifically, when step S202 is executed, the control device may determine what modification needs to be performed on the original configuration file based on preset CPU infrastructures of various types, and perform corresponding modification on the original resource configuration file to obtain a corresponding resource configuration file.

For example, referring to fig. 3, the preset CPU infrastructure specifically includes an ARM architecture, an X86 architecture, and a MIPS architecture, and the control device modifies the installation format of the original configuration file based on the acquired architecture information of the CPU infrastructure to respectively adapt to the CPU infrastructure, so as to obtain corresponding resource configuration files, such as a resource configuration file, an ARM, a resource configuration file, an X86, and a resource configuration file, an MIPS.

By adopting the method, the resource configuration files of various types of CPU basic architectures can be obtained, and it is assumed that the control device obtains 6 parts of original configuration files from the infrastructure installation package, that is, the original configuration files 1, 2, 3, 4, 5 and 6, the format of each original configuration file is modified according to the corresponding CPU basic architecture, and the distributed storage resource configuration can be completed on the storage device of the corresponding CPU basic architecture, and the generation conditions of the resource configuration files corresponding to the various types of CPU basic architectures are shown in table 1:

TABLE 1

As can be seen from the above table, the original configuration file 1, the original configuration file 2, the original configuration file 3, the original configuration file 4, the original configuration file 5, and the original configuration file 6 are based on a preset CPU infrastructure, and the format of the original configuration file is modified correspondingly, so as to obtain a corresponding resource configuration file. Taking original configuration file 1 as an example, aiming at the CPU basic framework of the ARM framework, the control device modifies the format of original configuration file 1 to generate a resource configuration file which can complete the configuration of distributed storage resources on the storage device of the ARM framework, ARM.1 and the like.

S203: after the corresponding resource configuration files are obtained, the CPU basic frameworks of various types, the corresponding file installation modes and the corresponding data compression modes are respectively determined.

Specifically, when step S203 is executed, the control device may determine which file installation manner and which data compression manner should be adopted by the corresponding resource configuration file based on preset CPU infrastructures of various types, respectively.

For example, there are three main file installation manners of the resource configuration file on the storage device, and specifically, the resource configuration file may include a Red Hat Package Manager (Red-Hat Package Manager, RPM), a Shell front-end Package Manager (Yellow dog update Modified, Yum), and a source code Package. In order to improve the installation speed of the file installation mode on the storage device and facilitate the installation of the resource configuration file, in the embodiment of the application, an RPM file installation mode is adopted. The data compression mode can be divided into instant compression and non-instant compression according to timeliness, wherein the instant compression is to convert a voice signal into a digital signal and simultaneously compress the digital signal and then transmit the digital signal through the Internet in real time, and the non-instant compression is performed only when needed and has no instantaneity. In this embodiment of the present application, the control device may compress the corresponding resource configuration files in advance according to the timeliness requirement of each resource configuration file. Still taking 6 resource configuration files, namely, resource configuration file.arm.1, resource configuration file.x 86.1, resource configuration file.mips.1, resource configuration file.arm.2, resource configuration file.x 86.2 and resource configuration file.mips.2 as examples, the timeliness requirements and data compression modes corresponding to each resource configuration file are shown in table 2:

TABLE 2

From the above table, the resource configuration file can determine the data compression mode for the corresponding resource configuration file according to the timeliness of the storage device for the resource configuration file requirement. Taking the resource configuration file ARM.1 as an example, if the storage device of the ARM architecture needs to obtain a compressed data packet of the corresponding resource configuration file in a short time, a data compression mode of instant compression is adopted; taking the resource configuration file X86.1 as an example, the storage device of the X86 architecture has no time requirement for obtaining the compressed data packet of the corresponding resource configuration file, and a non-immediate compression data compression mode is adopted.

S204: after determining the file installation mode and the data compression mode corresponding to each resource configuration file, respectively adopting the corresponding data compression mode to compress the resource configuration files corresponding to each type of CPU basic framework.

Specifically, when step S204 is executed, the control device first obtains a data compression mode corresponding to each resource configuration file, and then performs corresponding data compression processing on the resource configuration file, so as to finally obtain a corresponding compressed data packet.

For example, as shown in table 2, if it is known that the resource profile.mips.1 adopts an instant compression data compression method, it is known that a target storage device of the MIPS architecture needs to obtain the resource profile.mips.1 in a short time, and therefore, in the process of generating the resource profile.mips.1, data of the resource profile.mips.1 is compressed at the same time to generate a corresponding compressed data packet; if the resource configuration file is known, arm.2 adopts a non-immediate compression data compression mode, it can be known that there is no time requirement for the acquisition of the resource configuration file by the target storage device of the ARM architecture, therefore, the control device can generate the resource configuration file, arm.2, and then compress the data in the resource configuration file, arm.2, to generate a corresponding compressed data packet.

S205: and after the corresponding data compression modes are respectively compressed, respectively generating target installation packages carrying the corresponding file installation modes based on the obtained compressed data packages.

Specifically, when step S205 is executed, the control device first obtains a compressed data packet corresponding to each CPU infrastructure, determines which file compression and packaging manner should be adopted, packages the corresponding data compressed packet, and finally obtains a target installation packet corresponding to each CPU infrastructure.

For example, the data compression packet may specifically include ZLIB compression packet, ZIP compression packet, GZIP compression packet, 7Z compression packet, and RAR compression packet. In order to implement compression and packaging of compressed data packets with different formats and improve compression efficiency, in the embodiment of the present application, a ZIP compression and packaging manner is adopted. Still taking 6 parts of compressed data packets, namely, compressed data packet.arm.1, compressed data packet.x 86.1, compressed data packet mips.1, compressed data packet.arm.2, compressed data packet X86.2 and compressed data packet mips.2 as examples, the target installation packet corresponding to each compressed data packet is shown in table 3:

TABLE 3

According to the table, the compression data packet ARM.1, the compression data packet X86.1, the compression data packet MIPS.1, the compression data packet ARM.2, the compression data packet X86.2 and the compression data packet MIPS.2 are respectively based on the compression packaging mode of the control device, and the compression packaging is correspondingly performed on each compression data packet to obtain a corresponding target installation packet. For example, taking the compressed data packet arm.1 as an example, the control device compresses and packages the compressed data packet by adopting a ZIP compression and packaging manner, generates the target installation packet arm.1.zip, and so on.

Optionally, in a preferred embodiment of the present application, based on the above method steps, after the target installation packages corresponding to the respective types of CPU infrastructures are generated, the control device is further configured to generate the first script information, with reference to fig. 4, a generation process of the first script information includes the following specific steps:

s401: and respectively setting detection algorithms corresponding to the CPU infrastructures of all types based on the set CPU infrastructures of all types.

For convenience of description, in the embodiment of the present application, at least any one of the set CPU infrastructures of each type is taken as an example to perform relevant description, and the setting processes of the detection algorithms of the CPU infrastructures of other types all adopt similar manners, which will not be described again.

Specifically, in executing step S401, the control device may set a detection algorithm for detecting the identification information of the corresponding CPU infrastructure, respectively, based on the respective types of CPU infrastructures that are set.

Illustratively, the control device performs field matching on the identification information of the corresponding CPU infrastructure based on the set CPU infrastructure of each type, and matches the identification information of the CPU infrastructure of each type. In order to improve the efficiency of detecting the CPU infrastructure, the embodiment of the present application sets a detection algorithm for detecting the second script, that is, the identification information of the CPU infrastructure in the Shell script. Taking the Shell scripts of 3 types of CPU infrastructures, namely, the arm.shell script, the x86.shell script, and the mips.shell script as examples, script information and detection algorithms corresponding to each type of CPU infrastructure are shown in table 4:

TABLE 4

Shell script type	Shell script ARM	Shell script	Shell script
				Detecting algorithm type	Detection Algorithm ARM	Detection Algorithm X86	Detection Algorithm MIPS
The result of the detection	ARM architecture	X86 architecture	MIPS framework

As can be seen from the above table, the control device can match the field information of the CPU infrastructure in the corresponding Shell script respectively according to the detection algorithm of the identification information of each type of CPU infrastructure, and determine the type of the corresponding CPU infrastructure. For example, taking an arm.shell script as an example, the control device sets a detection algorithm based on a field of identification information of the CPU infrastructure in the Shell script of the ARM architecture.

S402: after the detection algorithms corresponding to the CPU basic architectures of all types are respectively set, the first script information is generated by adopting a fusion processing mode based on the set detection algorithms.

Specifically, when step S402 is executed, the control device determines which algorithm fusion mode should be used based on the detection algorithm of each type of CPU infrastructure, performs fusion processing on the detection algorithm of each type of CPU infrastructure, and obtains the first script information using the detection algorithm of the corresponding CPU infrastructure.

Illustratively, algorithm fusion modes of the detection algorithm on the control device mainly include six, specifically, a linear weighted fusion method, a cross fusion (Blending) method, a waterfall fusion method, a multi-different fusion method, a prediction fusion method and an additive fusion method. In order to meet the requirement that the control device detects the type of the CPU infrastructure of each storage device through the first script information, improve the detection speed of the CPU infrastructure of the target storage device, and ensure that the detection algorithms of each CPU infrastructure are independent of each other, in the embodiment of the present application, a predictive fusion method may be adopted.

For example, referring to fig. 5, a predictive fusion algorithm is adopted, and the detection algorithm ARM, the detection algorithm X86 and the detection algorithm MIPS in table 3 are fused to generate the first script information. It should be noted that, the control device may recommend a detection algorithm closest to the CPU infrastructure in the Shell script to the Shell script of the target storage device by using the first script information generated by the fusion algorithm. For example, the control device receives Shell scripts from an ARM architecture storage device, and recommends a detection algorithm.

S403: after the first-foot information is generated, on the basis of the first-foot information, respectively adopting detection algorithms corresponding to the CPU basic architectures of all types to detect the CPU basic architecture of the identification information of the CPU basic architecture of the storage device, and determining the type of the CPU basic architecture of the storage device.

Specifically, when step S403 is executed, after receiving the Shell script information of the target storage device, the control device first recommends a detection algorithm closest to the CPU infrastructure of the target storage device from the first script information, and then matches the field information of the CPU infrastructure in the Shell script information of the target storage device to obtain the identification information of the target storage device, so as to obtain the type of the CPU infrastructure of the target storage device.

Illustratively, taking a target storage device with an X86 architecture as an example, a control device receives an X86.shell script of the target storage device, and acquires field information in the X86.shell script; then, providing a detection algorithm for the field information in the X86.Shell script, and matching the field information in the X86.Shell script by X86; and finally, matching the field information containing the X86 architecture in the Shell script, and determining the type of the CPU infrastructure of the target storage device as the X86 architecture.

Further, based on the foregoing pre-operation processing, the control device generates resource configuration files corresponding to the respective types of CPU infrastructures, and first script information including detection algorithms of the respective types of CPU infrastructures, as shown in fig. 6, in an embodiment of the present application, a resource configuration file distribution process corresponding to a target storage device includes the following specific steps:

s601: and when the storage equipment to be deployed is determined to exist, acquiring the identification information of the CPU infrastructure of the storage equipment.

Specifically, when step S601 is executed, the control device first obtains an IP address of the target storage device through a Dynamic Host Configuration Protocol (DHCP), establishes a communication connection with the target storage device based on the IP address, and finally receives a Shell script carrying CPU infrastructure information and sent by the target storage device.

For example, referring to fig. 7, first, the target storage device sends a DHCP Discover message, that is, an IP address lease application message, to the control device 7 in a broadcast manner, indicating that the target storage device needs an IP address; subsequently, the control device still adopts a broadcasting mode to respond a DHCP Offer message to the target storage device, namely, an IP address lease providing message indicates that the control device can provide an IP address for the target storage device; further, the target storage device sends a DHCP Request message to the control device, wherein the DHCP Request message comprises an IP address applied by the target storage device; and finally, the control device sends a DHCP Ack message to the target storage device, wherein the DHCP Ack message comprises the IP address allocated by the target storage device and the effective duration of the IP address.

Further, after acquiring the IP address of the target storage device, the control device establishes network communication with the target storage device based on the IP address. Optionally, the control device configures each key for performing network communication with the storage device by using a Secure Shell protocol (SSH), so as to implement the secret-free communication. The SSH establishes a secure tunnel in the network to implement connection between the control device and the target storage device, thereby improving communication efficiency between the control device and the target storage device.

Further, after the control device establishes the secret-free communication with the target storage device, the Shell script which is sent by the target storage device and carries the identification information of the CPU infrastructure can be received.

S602: the type of the CPU infrastructure of the storage device is determined based on the identification information of the CPU infrastructure.

Specifically, when step S602 is executed, the control device may extract field information from the Shell script based on the Shell script received from the target storage device, where the field information includes identification information of a CPU infrastructure of the target storage device, and then match the field information according to a detection algorithm of the first script information to determine the type of the CPU infrastructure of the target storage device.

Illustratively, the control device predicts and recommends a detection algorithm closest to the CPU infrastructure of the target storage device from the first script information based on the Shell script of the target storage device, matches field information indicating the CPU infrastructure type in the Shell script, and finally determines the type of the CPU infrastructure of the target storage device. Taking the Shell scripts of 6 target storage devices, namely, the Shell script 1.ARM, the Shell script 2.X86, the Shell script 3.MIPS, the Shell script 4.ARM, the Shell script 5.X86 and the Shell script 6.MIPS as examples, the recommended detection algorithm and the detection result corresponding to each Shell script of each target storage device are shown in table 5:

TABLE 5

As can be seen from the above table, the control device may recommend, to shells of different target storage devices, a detection algorithm that is closest to the CPU infrastructure of the target storage device, respectively, according to the detection algorithm in the first script information, and then determine the type of the CPU infrastructure of the corresponding target storage device. For example, taking the Shell script 1.ARM as an example, the control device recommends a detection algorithm of an ARM infrastructure for the Shell script 1.ARM based on a detection algorithm of the first script information, and then matches field information in the Shell script 1.ARM according to the detection algorithm.

S603: and acquiring a corresponding resource configuration file based on the type of the CPU infrastructure.

For example, in executing step S603, the control device may configure a corresponding resource configuration file for the target storage device based on the obtained type of the CPU infrastructure of the target storage device. Taking 6 target storage devices, i.e. target storage device 1, target storage device 2, target storage device 3, target storage device 4, target storage device 5, and target storage device 6 as an example, the types of the CPU infrastructures and the resource configuration files corresponding to the respective target storage devices are shown in table 6:

TABLE 6

As can be seen from the above table, the control device can provide corresponding resource configuration files according to the types of the CPU infrastructures of the target storage devices. For example, taking the target storage device 1 as an example, the control device matches field information of the Shell script of the target storage device 1 through a detection algorithm of the first script, and determines that the CPU infrastructure of the target storage device 1 is an ARM architecture; and then, according to the ARM architecture of the target storage equipment 1, configuring the target installation package of the resource configuration file ARM.1 to the target storage equipment 1.

S604: and sending the resource configuration file to the storage device so that the storage device completes the configuration of the storage resource based on the obtained resource configuration file.

For convenience of description, in the embodiment of the present application, at least any one of the set CPU infrastructures of each type is taken as an example to perform relevant description, and the configuration processes of the storage resources of the CPU infrastructures of other types all adopt similar manners, which will not be described again.

Specifically, when step S604 is executed, the control device may send the corresponding target installation package to the target storage device, so that the target storage device establishes a corresponding local source based on its CPU infrastructure, loads a corresponding resource configuration file through the local source, and configures the corresponding storage resource based on the file installation manner recorded in the resource configuration file.

For example, after determining the CPU infrastructure of the target storage device, the control device sends the corresponding resource configuration file to the target storage device. Furthermore, after the storage device receives the corresponding target installation package, the storage device decompresses the target installation package by adopting a corresponding file decompression mode according to the file format of the compressed file of the target installation package to obtain a corresponding resource configuration file; then, based on the CPU basic structure of the local source, clearing the previous configuration file of the local source, reloading the configuration file of the corresponding local source, and completing the construction of the local source; and finally, executing the instruction for installing the resource configuration file at the local source, loading the corresponding resource configuration file, and completing the configuration of the storage resource of the target storage equipment. For example, as shown in table 6, if the target storage device 1 has received the resource configuration file, the target installation package of arm.1 is decompressed by using a ZIP decompression method to obtain a corresponding compressed data package; then, a ZIP decompression mode is adopted again to obtain a corresponding resource configuration file and RPM; further, clearing the previous configuration file of the local source, reloading the configuration file of the corresponding local source, further completing the construction of the local source, and storing the resource configuration file and the RPM in the local source; finally, executing the instruction for installing the resource configuration file at the local source, loading the corresponding resource configuration file, calling the storage resource of the target storage device 1, and finishing the deployment of the distributed storage system.

The distributed system deployment method provided by the embodiment of the application determines the type of the CPU infrastructure of the target storage device based on the identification information of the CPU infrastructure of the target storage device, and can accurately judge the type of the CPU infrastructure of the target storage device only according to the detection algorithm of the CPU infrastructure in the first script information.

Based on the same technical concept, the embodiment of the present application further provides a distributed system deployment apparatus, and the distributed system deployment apparatus can implement the above method flow of the embodiment of the present application.

Fig. 8 schematically illustrates a structural diagram of a distributed system deployment apparatus provided in an embodiment of the present application. As shown in fig. 8, the storage automation deployment apparatus includes: an acquisition module 801, a processing module 802, and a communication module 803, wherein:

an obtaining module 801, configured to obtain, when it is determined that a storage device to be deployed exists, identification information of a CPU infrastructure of the storage device.

A processing module 802, configured to determine a type of a CPU infrastructure of the storage device based on the identification information of the CPU infrastructure; and acquiring a corresponding resource configuration file based on the type of the CPU infrastructure.

The communication module 803 is configured to send the resource configuration file to the storage device, so that the storage device completes configuration of the storage resource based on the obtained resource configuration file.

In an optional embodiment, before acquiring the identification information of the CPU infrastructure of the storage device when it is determined that the storage device to be deployed exists, the acquiring module 801 is further configured to:

In an optional embodiment, before obtaining the identification information of the CPU infrastructure of the storage device when it is determined that the storage device to be deployed exists, the processing module 802 is further configured to:

When it is determined that there is a storage device to be deployed and identification information of a CPU infrastructure of the storage device is acquired, the processing module 802 is specifically configured to:

In an optional embodiment, when sending the resource configuration file to the storage device, so that the storage device completes configuration of the storage resource based on the obtained resource configuration file, the communication module 803 is specifically configured to:

It should be noted that, the distributed system deployment apparatus provided in the embodiment of the present application can implement all the method steps executed by the control device in the embodiment of the method, and can achieve the same technical effect, and details of the same parts and beneficial effects as those in the embodiment of the method are not described herein again.

Based on the same technical concept, the embodiment of the application also provides electronic equipment, and the electronic equipment can realize the method flows provided by the embodiments of the application. In one embodiment, the electronic device may be a server, a terminal device, or other electronic devices.

Fig. 9 schematically shows a structural diagram of an electronic device provided in an embodiment of the present application. As shown, the electronic device may include:

at least one processor 901 and a memory 902 connected to the at least one processor 901, in this embodiment, a specific connection medium between the processor 901 and the memory 902 is not limited in this application, and fig. 9 illustrates an example where the processor 901 and the memory 902 are connected through a bus 900. The bus 900 is shown in fig. 9 by a thick line, and the connection between other components is merely illustrative and not limited thereto. The bus 900 may be divided into an address bus, a data bus, a control bus, etc., and is shown with only one thick line in fig. 9 for ease of illustration, but does not represent only one bus or type of bus. Alternatively, the processor 901 may also be referred to as a controller, without limitation to name.

In the embodiment of the present application, the memory 902 stores instructions executable by the at least one processor 901, and the at least one processor 901 can execute one of the storage automation deployment methods discussed above by executing the instructions stored in the memory 902. The processor 901 may implement the functions of the respective modules in the apparatus shown in fig. 8.

The processor 901 is a control center of the apparatus, and may connect various parts of the entire control device by using various interfaces and lines, and perform various functions and process data of the apparatus by executing or executing instructions stored in the memory 902 and calling data stored in the memory 902, thereby performing overall monitoring of the apparatus.

In one possible design, the processor 901 may include one or more processing units, and the processor 901 may integrate an application processor, which mainly handles operating systems, user interfaces, application programs, and the like, and a modem processor, which mainly handles wireless communications. It will be appreciated that the modem processor described above may not be integrated into the processor 901. In some embodiments, the processor 901 and the memory 902 may be implemented on the same chip, or in some embodiments, they may be implemented separately on separate chips.

The processor 901 may be a general-purpose processor, such as a cpu (central processing unit), a digital signal processor, an application specific integrated circuit, a field programmable gate array or other programmable logic device, discrete gate or transistor logic, discrete hardware components, and may implement or perform the methods, steps, and logic blocks disclosed in the embodiments of the present application. A general purpose processor may be a microprocessor or any conventional processor or the like. The steps of a storage automation deployment method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor.

Memory 902, which is a non-volatile computer-readable storage medium, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules. The Memory 902 may include at least one type of storage medium, and may include, for example, a flash Memory, a hard disk, a multimedia card, a card-type Memory, a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Programmable Read Only Memory (PROM), a Read Only Memory (ROM), a charge Erasable Programmable Read Only Memory (EEPROM), a magnetic Memory, a magnetic disk, an optical disk, and so on. The memory 902 is any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to such. The memory 902 of the embodiments of the present application may also be circuitry or any other device capable of performing a storage function for storing program instructions and/or data.

The processor 901 is programmed to solidify the code corresponding to a storage automation deployment method described in the foregoing embodiments into the chip, so that the chip can execute the steps of a distributed system deployment method of the embodiment shown in fig. 6 when running. How to program the processor 901 is well known to those skilled in the art and will not be described herein.

Based on the same inventive concept, the present application also provides a storage medium storing computer instructions, which when executed on a computer, cause the computer to execute a distributed system deployment method as discussed above.

In some possible embodiments, the present application provides that the various aspects of a distributed system deployment method may also be implemented in the form of a program product comprising program code means for causing the control apparatus to carry out the steps of a distributed system deployment method according to various exemplary embodiments of the present application described above in the present specification, when the program product is run on an apparatus.

As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.

The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a server, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.

These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.

It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.

Claims

1.A method of distributed system deployment, the method comprising:

when the storage equipment to be deployed is determined to exist, acquiring identification information of a Central Processing Unit (CPU) infrastructure of the storage equipment;

determining the type of the CPU infrastructure of the storage device based on the identification information of the CPU infrastructure;

acquiring a corresponding resource configuration file based on the type of the CPU infrastructure;

and sending the resource configuration file to the storage device, so that the storage device completes the configuration of the storage resource based on the obtained resource configuration file.

2. The method of claim 1, wherein before obtaining the identification information of the CPU infrastructure of the storage device when determining that the storage device to be deployed exists, further comprising:

acquiring a preset original configuration file;

respectively and correspondingly modifying the original configuration file based on the set CPU basic framework of each type to obtain a corresponding resource configuration file;

respectively determining the CPU basic architectures of all types, and the corresponding file installation mode and data compression mode;

respectively compressing the resource configuration files corresponding to the CPU basic architectures of all types in a corresponding data compression mode;

and respectively generating target installation packages carrying corresponding file installation modes based on the obtained compressed data packages.

3. The method of claim 1, wherein before obtaining the identification information of the CPU infrastructure of the storage device when determining that the storage device to be deployed exists, further comprising:

respectively setting detection algorithms corresponding to the CPU basic architectures of all types based on the set CPU basic architectures of all types;

generating first script information by adopting a fusion processing mode based on various set detection algorithms;

and based on the first script information, respectively adopting detection algorithms corresponding to the CPU basic architectures of all types to detect the identification information of the CPU basic architecture of the storage device, and determining the type of the CPU basic architecture of the storage device.

4. The method of claim 1, wherein when it is determined that there is a storage device to be deployed, obtaining identification information of a CPU infrastructure of the storage device comprises:

acquiring an Internet Protocol (IP) address of the storage equipment by a Dynamic Host Configuration Protocol (DHCP);

establishing communication connection with the storage device based on the obtained IP address;

and acquiring the identification information of the CPU basic framework of the storage device based on the communication connection.

5. The method of claim 1, wherein sending the resource profile to the storage device to cause the storage device to complete configuration of storage resources based on the obtained resource profile comprises:

6. A distributed system deployment apparatus, the apparatus comprising:

the system comprises an acquisition module, a storage module and a management module, wherein the acquisition module is used for acquiring identification information of a Central Processing Unit (CPU) basic framework of the storage device when the storage device to be deployed is determined to exist;

the processing module is used for determining the type of the CPU basic framework of the storage device based on the identification information of the CPU basic framework; acquiring a corresponding resource configuration file based on the type of the CPU infrastructure;

and the communication module is used for sending the resource configuration file to the storage equipment so as to enable the storage equipment to complete the configuration of the storage resource based on the obtained resource configuration file.

7. The apparatus of claim 6, wherein prior to obtaining the identification information of the CPU infrastructure of the storage device when the storage device to be deployed is determined to exist, the obtaining module is further to:

acquiring a preset original configuration file, and respectively and correspondingly modifying the original configuration file based on the set CPU basic framework of each type to acquire a corresponding resource configuration file;

and respectively compressing the resource configuration files corresponding to the CPU basic architectures of all types in a corresponding data compression mode, and respectively generating target installation packages carrying the corresponding file installation modes on the basis of the obtained compressed data packages.

8. The apparatus of claim 6, wherein prior to obtaining identification information of a CPU infrastructure of the storage device when the storage device to be deployed is determined to exist, the processing module is further to:

when the storage device to be deployed is determined to exist and the identification information of the CPU infrastructure of the storage device is acquired, the processing module is specifically configured to:

9. The apparatus as claimed in claim 6, wherein, when said sending the resource profile to the storage device to enable the storage device to complete configuration of storage resources based on the obtained resource profile, the communication module is specifically configured to:

10. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, characterized in that the processor implements the distributed system deployment method as claimed in any one of claims 1 to 5 when executing the computer program.

11. A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the method according to any one of claims 1 to 5.