CN112486939A

CN112486939A - Public cloud-based Moosefs distributed file storage method, system, medium and device

Info

Publication number: CN112486939A
Application number: CN201910859543.1A
Authority: CN
Inventors: 吴新雷
Original assignee: Shanghai Qinggan Intelligent Technology Co Ltd
Current assignee: Shanghai Qinggan Intelligent Technology Co Ltd
Priority date: 2019-09-11
Filing date: 2019-09-11
Publication date: 2021-03-12

Abstract

The invention provides a public cloud-based Moosefs distributed file storage method, system, medium and device, wherein the method comprises the following steps: installing a management server in a public cloud; installing the data storage server in a public cloud, connecting with the management server and being used for being managed by the management server; and installing mounting software at the client to mount the data storage server managed by the management server. The invention discloses a public cloud-based Moosefs distributed file storage method, system, medium and device, which are used for providing a data storage server for a client and more conveniently sharing files.

Description

Public cloud-based Moosefs distributed file storage method, system, medium and device

Technical Field

The invention relates to the technical field of communication, in particular to a public cloud-based Moosefs distributed file storage method, system, medium and device.

Background

In the prior art, a network sharing file system such as NFS of a public cloud performs network sharing of files. Nfs (network File system), a network File system, is one of the File systems supported by FreeBSD, which allows sharing of resources among computers in a network. In the application of NFS, a client application of a local NFS can transparently read and write files located on a remote NFS server, just like accessing local files. The NFS system has at least two major components: an NFS server and several clients as shown in fig. 1. The client remotely accesses data residing on the NFS server via the TCP/IP network. Before the NFS server is formally enabled, some NFS parameters need to be configured according to actual environment and requirements. NFS performance is limited and not all public clouds provide this functionality. And NFS has many disadvantages, such as: a. the limitation is easy to have a single point of failure, and all the clients cannot access the server machine due to the fact that the server machine is down. b. NFS efficiency/performance is limited at high concurrency. c. The client does not use a user authentication mechanism, and data is transmitted through plaintext, so that the security is general (generally, the use in a local area network is recommended). data of nfs is in plaintext, and data integrity is not verified. e. When a plurality of machines mount the NFS server, the connection management and maintenance are troublesome.

Therefore, it is desirable to be able to solve the problem of limited performance of network shared file systems of public clouds.

Disclosure of Invention

In view of the foregoing disadvantages of the prior art, an object of the present invention is to provide a method, a system, a medium, and an apparatus for Moosefs distributed file storage based on a public cloud, which are used to solve the problem in the prior art that the performance of a network shared file system of the public cloud is limited.

In order to achieve the above objects and other related objects, the present invention provides a Moosefs distributed file storage method based on public cloud, comprising the following steps: installing a management server in a public cloud; installing the data storage server in a public cloud, connecting with the management server and being used for being managed by the management server; and mounting the address of the shared data disk on mounting software installed on the client.

In an embodiment of the present invention, the installing and managing server in the public cloud further includes: setting the address of the shared data disk and starting the management server.

In an embodiment of the present invention, the installing the data storage server in the public cloud further includes: setting a shared data disk, appointing a host computer for starting the management server, and starting the data storage server.

In order to achieve the above object, the present invention further provides a Moosefs distributed file storage system based on public cloud, including: the system comprises a management server installation module, a data storage server installation module and a mounted software installation module; the management server installation module is used for installing a management server in a public cloud; the data storage server installation module is used for installing the data storage server in a public cloud, is connected with the management server and is used for being managed by the management server; the mounting software installation module is used for mounting the address of the shared data disk on mounting software installed on the client.

In an embodiment of the present invention, the management server installation module is further configured to set an address of the shared data disk, and start the management server.

In an embodiment of the present invention, the data storage server installation module is further configured to set a shared data disk, designate a host that starts the management server, and start the data storage server.

To achieve the above object, the present invention further provides a computer readable storage medium, on which a computer program is stored, which when executed by a processor, implements any of the above public cloud-based Moosefs distributed file storage methods.

In order to achieve the above object, the present invention further provides a Moosefs distributed file storage apparatus based on public cloud, including: a processor and a memory; the memory is used for storing a computer program; the processor is connected with the memory and is used for executing a computer program stored by the memory so as to enable the public cloud-based Moosefs distributed file storage device to execute any one of the above public cloud-based Moosefs distributed file storage methods.

Finally, the invention also provides a public cloud-based Moosefs distributed file storage system, which comprises the public cloud-based Moosefs distributed file storage device and a client; the client is used for installing mounting software so as to mount the address of the shared data disk.

In an embodiment of the present invention, the client is a computer or a mobile intelligent terminal.

As described above, the Moosefs distributed file storage method, system, medium, and apparatus based on public cloud of the present invention have the following beneficial effects: has strong expansibility, high reliability and durability.

Drawings

FIG. 1 is a flowchart illustrating a public cloud based Moosefs distributed file storage method according to an embodiment of the present invention;

FIG. 2 is a schematic structural diagram of a public cloud-based Moosefs distributed file storage system according to an embodiment of the present invention;

FIG. 3 is a schematic structural diagram of a public cloud-based Moosefs distributed file storage apparatus according to an embodiment of the present invention;

FIG. 4 is a schematic structural diagram of a public cloud-based Moosefs distributed file storage system according to yet another embodiment of the present invention;

fig. 5 is a schematic structural diagram of a public cloud-based Moosefs distributed file storage system according to still another embodiment of the present invention.

Description of the element reference numerals

21 management server installation module

22 data storage server installation module

23 mount software installation module

31 processor

32 memory

Moosefs distributed file storage device of 41 public clouds

42 client

Moosefs distributed file storage device of 51 public cloud

52 first client

53 second client

Detailed Description

The embodiments of the present invention are described below with reference to specific embodiments, and other advantages and effects of the present invention will be easily understood by those skilled in the art from the disclosure of the present specification. The invention is capable of other and different embodiments and of being practiced or of being carried out in various ways, and its several details are capable of modification in various respects, all without departing from the spirit and scope of the present invention. It is to be noted that the features in the following embodiments and examples may be combined with each other without conflict.

It should be noted that the drawings provided in the following embodiments are only for illustrating the basic idea of the present invention, so that the components related to the present invention are only shown in the drawings rather than drawn according to the number, shape and size of the components in actual implementation, the type, quantity and proportion of the components in actual implementation can be changed freely, and the layout of the components can be more complicated.

The Moosefs distributed file storage method, system, medium and device based on the public cloud have strong expansibility.

As shown in fig. 1, in an embodiment, the method for storing Moosefs distributed files based on public cloud of the present invention includes the following steps:

and step S11, installing a management server in the public cloud.

Specifically, Moosefs is one of the sub-items of the OpenStack open source cloud computing item, called object storage, and provides strong extensibility, high reliability and durability, and the open source storage system under Linux is formally released by Gemius SA of polish corporation in 2008, 30/5. The file storage system can distribute and store files on different physical machines, and provides a transparent interface storage resource pool for the external. The method also has the characteristics of online expansion, file block-cutting storage, no single-point failure of nodes, high read-write efficiency and the like.

The Moosefs distributed file system is composed of a management Server (Master Server), a metadata log Server (Metalogger Server), a data storage Server (Chunk Server) and a Client (Client).

(1) A management server: the core component in the Moosefs system stores metadata of each file, and is responsible for read-write scheduling, space recovery, data copying among multiple chunk servers and the like of the files. Currently, Moosefs only supports one management server, and thus a single point of failure may occur. In order to solve the problem, a server with stable performance is needed to be used as the management server, so that the probability of single-point failure can be reduced.

(2) Metadata log server: and the backup node of the management server downloads files for storing the metadata, the update log and the session information from the management server to a local directory according to a specified period. When the management server fails, the relevant necessary information can be taken from the file of the server to recover the whole system.

In addition, the backup by using metadata is a conventional log backup means, which cannot perfectly take over the service in some cases, or causes data loss.

(3) A data storage server: the management server is responsible for connecting, listening to the scheduling of the management server, providing storage space and providing data transmission for the client, and Moosefs provides a manual assignment of the backup number of each directory. Assuming that the number is n, when we write a file to the system, the system will copy the sliced file blocks n times on different chunk servers. The increase of the spare amount does not affect the writing performance of the system, but can improve the reading performance and the availability of the system, which can be said to be a strategy for trading the storage capacity for the writing performance and the availability.

(4) A client: the Moosefmount mode is used for hooking a data storage server managed on a remote management server to a local directory through a Fuse kernel interface, and then the Moosefs file system can be used as if a local file is used.

Specifically, the management Server, that is, the Master Server, is installed in the public cloud.

Specifically, the installing and managing server in the public cloud further includes the following steps: setting the address of the shared data disk and starting the management server. Specifically, mfsesport.cfg is modified and the management server is started. Specifically, the following instructions are executed: the method comprises the following steps of/usr/local/mfs/sbin/mfssmaster start.

The Moosefs distributed file system is applied to the public cloud, so that the public cloud has the advantages of the Moosefs distributed file system.

And step S12, installing the data storage server in a public cloud, connecting with the management server, and managing by the management server.

Specifically, the installing the data storage Server in the public cloud is to install a Chunk Server.

Specifically, the installing and managing server in the public cloud further includes the following steps: setting the address of the shared data disk and starting the management server. Specifically, the shared data disk is set by modifying mfshdd. Specifically, the following instructions are executed: the start of the method is/usr/local/mfs/sbin/mfschunkserver.

And step S13, mounting the address of the shared data disk on the mounting software installed on the client.

Specifically, Fuse is installed at the client so as to mount the address of the shared data disk at the client. Namely, the address of the shared data disk of the Moosefs is mounted by the Fuse of the client as a local directory, so that network file sharing of the public cloud is realized. Specifically, the following instructions are executed: cd/mnt-

mkdir mfs

/usr/local/mfs/bin/mfsmount/mnt/mfs/-H 192.168.28.242。

Moosefs is described in detail below:

moosefs is an open-source semi-distributed file system under Linux. It is currently used by many enterprises. It is so widely used because of the following advantages: the installation and configuration are simple and convenient, the reliability is high (a plurality of copies of data are stored on a plurality of different servers), the capacity can be dynamically expanded by adding a new server or a hard disk, and the deleted data can be reserved within a certain time (similar to a recycle bin mechanism in windows, and the data retention time needs to be configured). The above advantages make it clear that Moosefs, although open-source, is functionally comparable to professional storage systems. We next learn specifically to install and configure Moosefs. The Moosefs distributed file system is applied to the public cloud, so that the public cloud has the advantages of the Moosefs distributed file system.

Moosefs file system structure: the whole file system comprises the following roles: the role of each role is as follows: 1. and the management server is responsible for management of each data storage server, file read-write scheduling, file space recovery and multi-node copy recovery. 2. And the metadata log server is responsible for backing up the change log file of the master server, and the file type is changelog _ ml. 3. And the data storage server is responsible for connecting the management server, listening to the scheduling of the management server, providing storage space and providing data transmission for the client. 4. The client side is connected with the data storage server managed on the remote management server through the Fuse kernel interface, and the shared file system and the local file system are used as same as each other.

Preparation work: preparing a server:

OS:Centos 5.8 x86_64

a management server: 192.168.0.201

Metadata log server: 192.168.0.202

A data storage server: 192.168.0.203

A data storage server: 192.168.0.204

A client: 192.168.0.205

Downloading an installation package:

wgethttp://pro.hit.gemius.pl/hitredir/id＝p4CVHPOzkVa0JJIK.m0Ee6dyHZEgoQb1KaiPmVK29EX.M7/url＝

moosefs.org/tl_files/mfscode/mfs-1.6.26.tar.gz

adding related users and user groups:

groupaddmfs

useradd-gmfsmfs-s/sbin/nologin

compile install Moosefs

The entire Moosefs installation is simple, with only the following steps.

tarzxvfmfs-1.6.26.tar.gz

cdmfs-1.6.26

./configure--prefix＝/usr/local/mfs--with-default-user＝mfs--with-default-group＝mfs

make

makeinstall

Note that the client part needs to see if Fuse is installed before installation. The no installation request is executed as follows:

yuminstallfuse

yuminstallfuse-devel

the configuration uses:

management server (192.168.0.201):

cfg configuration:

cd/usr/local/mfs/etc

cpmfsmaster.cfg.distmfsmaster.cfg

vim mfsmaster.cfg

cfg file content as follows,

the configuration with the # number is default configuration, and the configuration without the # number needs manual configuration.

USER operating mfssmaster with mfs #working _ USER #

GROUP of # WORKING _ GROUP ═ mfs running mfssmaster

# SYSLOG _ IDENT ═ mfssmaster is the identification of MasterServer in SYSLOG

Whether mlockall () is executed if # LOCK _ MEMORY ═ 0 to avoid mfssmaster process overflow

Priority of operation # NICE _ LEVEL 19

# EXPORTS _ FILENAME ═ usr/local/mfs/etc/mfsExports

#TOPOLOGY_FILENAME＝/usr/local/mfs/etc/mfstopology.cfg

DATA _ PATH/usr/local/mfs/var/mfs DATA storage PATH stores three types of files, change log, sessions, stats

Number of Change Log files of # BACK _ LOGS ═ 50 metadata

#BACK_META_KEEP_PREVIOUS＝1

300 delayed replication time # REPLICATIONS _ DELAY _ INIT

DELAY time for # REPLICATIONS _ DELAY _ DISCONNECT 3600ChunkServer to DISCONNECT replication

IP address monitored by # MATOML _ LISTEN _ HOST ═ metadata log server

# MATOML _ LISTEN _ PORT 9419 Port Address listened by metadata Log Server

IP address for ChunkServer connection # MATOCS _ LISTEN _ HOST ═ IP address

# MATOCS _ LISTEN _ PORT 9420 Port Address for ChunkServer connection

IP address for client attach connection # match _ LISTEN _ HOST ═ IP address

# MATOCL _ LISTEN _ PORT 9421 Port Address for client hook connection

#CHUNKS_LOOP_CPS＝100000

300CHUNKS LOOP frequency # CHUNKS _ LOOP _ TIME

#CHUNKS_SOFT_DEL_LIMIT＝10

#CHUNKS_HARD_DEL_LIMIT＝25

# CHUNKS _ WRITE _ REP _ LIMIT 2 the maximum number of CHUNKS copied to a chunk server in a cycle

# CHUNKS _ READ _ REP _ LIMIT 10 the maximum number of CHUNKS copied from a chunk server in a cycle

Client side hanging with 0 popup low version

#deprecated:

#CHUNKS_DEL_LIMIT-useCHUNKS_SOFT_DEL_LIMITinstead

#LOCK_FILE-locksystemhasbeenchanged,andthisoptionisusedonlyto

searchforoldlockfile

Cfg configuration:

cd/usr/local/mfs/etc

cpmfsmaster.cfg.distmfsmaster.cfg

vimmfsmaster.cfg

cfg file content is as follows:

each entry in the configuration file is divided into three parts, namely a client IP address, an attached directory and a permission owned by the client. The configuration of default tape # number is not productive.

*/rw,alldirs,maproot＝0

#192.168.1.0/24/rw,alldirs,maproot＝0,password＝passcode

#10.0.0.0-10.0.0.5/testrw,maproot＝nobody,password＝test

#10.1.0.0/255.255.0.0/publicrw,mapall＝1000:1000

#10.2.0.0/16/rw,alldirs,maproot＝0,mintrashtime＝2h30m,maxtrashtime＝2w

Copying the metadata file:

cd/usr/local/mfs/var/mfs/

mvmetadata.mfs.emptymetadata.mfs

commands related to the management server:

a start command: /usr/local/mfs/sbin/mfssmaster start

Safety stop command: perusr/local/mfs/sbin/mfssmaster-s

More help information: /usr/local/mfs/sbin/mfssmaster-h

Metadata log server (192.168.0.202):

cfg configuration:

cd/usr/local/mfs/etc

cpmfsmetalogger.cfg.distmfsmetalogger.cfg

vimmfsmetalogger.cfg

cfg files are as follows:

#WORKING_USER＝mfs

#WORKING_GROUP＝mfs

#SYSLOG_IDENT＝mfsmetalogger

#LOCK_MEMORY＝0

#NICE_LEVEL＝-19

#DATA_PATH＝/usr/local/mfs/var/mfs

#BACK_LOGS＝50

#BACK_META_KEEP_PREVIOUS＝3

# META _ DOWNLOAD _ FREQ is 24 metadata backup file DOWNLOAD request frequency, and is 24 hours by default.

#MASTER RECONNECTION DELAY＝5

MASTER _ HOST 192.168.0.201 IP modified to MasterServer is needed here

#MASTER_PORT＝9419

#MASTER_TIMEOUT＝60

#deprecated,toberemovedinMooseFS1.7

#LOCK_FILE＝/var/run/mfs/mfsmetalogger.lock

Commands related to the metadata log server:

a start command: usr/local/mfs/sbin/mfsmelogger start

Safety stop command: usr/local/mfs/sbin/mfsmelogger-s

More help information: usr/local/mfs/sbin/mfsmelogger-h

Data storage servers (192.168.0.203 and 192.168.0.203):

cfg configuration:

cd/usr/local/mfs/etc

cpmfschunkserver.cfg.distmfschunkserver.cfg

vimmfschunkserver.cfg

cfg files are as follows:

#WORKING_USER＝mfs

#WORKING_GROUP＝mfs

#SYSLOG_IDENT＝mfschunkserver

#LOCK_MEMORY＝0

#NICE_LEVEL＝-19

#DATA_PATH＝/usr/local/mfs/var/mfs

#MASTER_RECONNECTION_DELAY＝5

#BIND_HOST＝*

Name or address of MASTER _ HOST 192.168.0.201 metadata server, which may be a hostname or IP address

MASTER_PORT＝9420

#MASTER_TIMEOUT＝60

#CSSERV_LISTEN_HOST＝*

9422 this PORT is used for connection to other data storage servers, typically data replication.

Cfg is the location allocated to the disk space profile used by Moosefs.

#HDD_TEST_FREQ＝10

#deprecated,toberemovedinMooseFS1.7

#LOCK_FILE＝/var/run/mfs/mfschunkserver.lock

#BACK_LOGS＝50

#CSSERV_TIMEOUT＝5

Cfg configuration:

cd/usr/local/mfs/etc

cpmfshdd.cfg.distmfshdd.cfg

vimmfshdd.cfg

cfg file content is as follows:

/data

the upper/data is a Moosefs partition, and the owner of the partition needs to be changed to mfs.

chown–Rmfs.mfs/data

Commands associated with the data storage server:

a start command: /usr/local/mfs/sbin/mfschunkservtart

Safety stop command: usr/local/mfs/sbin/mfschunkserver-s

More help information: usr/local/mfs/sbin/mfschunkserver-h

Client (192.168.0.205):

creating a hanging point:

mkdir–p/data/mfs

moosefs mount command:

/usr/local/mfs/bin/mfsmount/data/mfs-H192.168.0.201

as shown in fig. 2, in an embodiment, the Moosefs distributed file storage system based on public cloud of the present invention includes a management server installation module 21, a data storage server installation module 22, and a mount software installation module 23.

The management server installation module 21 is configured to install a management server in a public cloud.

The data storage server installation module 22 is configured to install the data storage server in a public cloud, connect with the management server, and be managed by the management server.

The mount software installation module 23 is configured to mount the address of the shared data disk on mount software installed at the client.

mkdir mfs

/usr/local/mfs/bin/mfsmount/mnt/mfs/-H 192.168.28.242。

It should be noted that the division of the modules of the above system is only a logical division, and the actual implementation may be wholly or partially integrated into one physical entity, or may be physically separated. And these modules can be realized in the form of software called by processing element; or may be implemented entirely in hardware; and part of the modules can be realized in the form of calling software by the processing element, and part of the modules can be realized in the form of hardware. For example, the x module may be a processing element that is set up separately, or may be implemented by being integrated in a chip of the apparatus, or may be stored in a memory of the apparatus in the form of program code, and the function of the x module may be called and executed by a processing element of the apparatus. Other modules are implemented similarly. In addition, all or part of the modules can be integrated together or can be independently realized. The processing element described herein may be an integrated circuit having signal processing capabilities. In implementation, each step of the above method or each module above may be implemented by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.

For example, the above modules may be one or more integrated circuits configured to implement the above methods, such as: one or more Application Specific Integrated Circuits (ASICs), or one or more microprocessors (DSPs), or one or more Field Programmable Gate Arrays (FPGAs), among others. For another example, when one of the above modules is implemented in the form of a Processing element scheduler code, the Processing element may be a general-purpose processor, such as a Central Processing Unit (CPU) or other processor capable of calling program code. For another example, these modules may be integrated together and implemented in the form of a system-on-a-chip (SOC).

In an embodiment of the present invention, the present invention further includes a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements any one of the foregoing public cloud-based Moosefs distributed file storage methods.

Those of ordinary skill in the art will understand that: all or part of the steps for implementing the above method embodiments may be performed by hardware associated with a computer program. The aforementioned computer program may be stored in a computer readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.

As shown in fig. 3, in an embodiment, the public cloud-based Moosefs distributed file storage apparatus of the present invention includes: a processor 31 and a memory 32; the memory 32 is for storing a computer program; the processor 31 is connected to the memory 32, and is configured to execute a computer program stored in the memory 32, so that the public cloud-based Moosefs distributed file storage apparatus executes any one of the public cloud-based Moosefs distributed file storage methods.

Specifically, the memory 32 includes: various media that can store program codes, such as ROM, RAM, magnetic disk, U-disk, memory card, or optical disk.

Preferably, the Processor 31 may be a general-purpose Processor, including a Central Processing Unit (CPU), a Network Processor (NP), and the like; the Integrated Circuit may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Field Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic device, or discrete hardware components.

As shown in fig. 4, in an embodiment, the public cloud-based Moosefs distributed file storage system of the present invention includes the aforementioned public cloud Moosefs distributed file storage device 41 and the client 42.

The client 42 is used to install mounting software to mount the address of the shared data disk. The client side is connected with the data storage server managed on the remote management server through the Fuse kernel interface, and the shared file system and the local file system are used in the same effect. That is, the client shares the file of the data storage server managed on the management server through Fuse.

Specifically, the client is a computer or a mobile intelligent terminal.

As shown in fig. 5, in an embodiment, the public cloud-based Moosefs distributed file storage system of the present invention includes the aforementioned public cloud Moosefs distributed file storage device 51, a first client 52, and a second client 53.

The first client 52 and the second client 53 are used to install mount software to mount the address of the shared data disk.

Specifically, the client may set a preset number according to a requirement.

In summary, the Moosefs distributed file storage method, system, medium and apparatus based on the public cloud of the present invention have strong extensibility, high reliability and durability. Therefore, the invention effectively overcomes various defects in the prior art and has high industrial utilization value.

The foregoing embodiments are merely illustrative of the principles and utilities of the present invention and are not intended to limit the invention. Any person skilled in the art can modify or change the above-mentioned embodiments without departing from the spirit and scope of the present invention. Accordingly, it is intended that all equivalent modifications or changes which can be made by those skilled in the art without departing from the spirit and technical spirit of the present invention be covered by the claims of the present invention.

Claims

1. A Moosefs distributed file storage method based on public cloud is characterized by comprising the following steps:

installing a management server in a public cloud;

installing the data storage server in a public cloud, connecting with the management server and being used for being managed by the management server;

and mounting the address of the shared data disk on mounting software installed on the client.

2. The public cloud based Moosefs distributed file storage method according to claim 1, wherein said installing a management server in a public cloud further comprises the steps of: setting the address of the shared data disk and starting the management server.

3. The public cloud based Moosefs distributed file storage method according to claim 1, wherein said installing the data storage server in a public cloud further comprises the steps of: setting a shared data disk, appointing a host computer for starting the management server, and starting the data storage server.

4. A public cloud based Moosefs distributed file storage system, comprising: the system comprises a management server installation module, a data storage server installation module and a mounted software installation module;

the management server installation module is used for installing a management server in a public cloud;

the data storage server installation module is used for installing the data storage server in a public cloud, is connected with the management server and is used for being managed by the management server;

the mounting software installation module is used for mounting the address of the shared data disk on mounting software installed on the client.

5. The public cloud-based Moosefs distributed file storage system according to claim 1, wherein the management server installation module is further configured to set an address of a shared data disk and start a management server.

6. The public cloud based Moosefs distributed file storage system according to claim 1, wherein the data storage server installation module is further configured to set a shared data disk, designate a host that starts the management server, and start the data storage server.

7. A computer-readable storage medium on which a computer program is stored, the program, when executed by a processor, implementing the public cloud based Moosefs distributed file storage method according to any one of claims 1 to 3.

8. A public cloud based Moosefs distributed file storage, comprising: a processor and a memory;

the memory is used for storing a computer program;

the processor is connected with the memory and used for executing the computer program stored by the memory so as to enable the public cloud-based Moosefs distributed file storage device to execute the public cloud-based Moosefs distributed file storage method according to any one of claims 1 to 3.

9. A public cloud based Moosefs distributed file storage system, comprising the public cloud based Moosefs distributed file storage apparatus of claim 8 and a client;

the client is used for installing mounting software so as to mount the address of the shared data disk.

10. The public cloud-based Moosefs distributed file storage system according to claim 9, wherein the client is a computer or a mobile intelligent terminal.