CN110569212A

CN110569212A - File deployment method, system, storage medium and electronic equipment

Info

Publication number: CN110569212A
Application number: CN201910867239.1A
Authority: CN
Inventors: 蔡云云
Original assignee: Shenzhen Onething Technology Co Ltd
Current assignee: Shenzhen Onething Technology Co Ltd
Priority date: 2019-09-12
Filing date: 2019-09-12
Publication date: 2019-12-13

Abstract

The file deployment method provided by the application comprises the following steps: acquiring a deployment requirement; selecting target node equipment from a node equipment group according to the deployment requirement, wherein the node equipment group comprises node equipment of multiple equipment types; and deploying a target file on the target node device. According to the method and the device, appropriate node equipment can be selected to deploy the target file according to deployment requirements. On the basis, different deployment modes can be adopted according to different deployment requirements, the deployment capability of P2P is greatly improved, the flow guidance is flexibly controlled, and the service quality enjoyed by a customer in a CDN mode is improved. The application also discloses a file deployment system, an electronic device and a computer readable storage medium, which can also achieve the technical effects.

Description

File deployment method, system, storage medium and electronic equipment

Technical Field

The present application relates to the field of computer technologies, and in particular, to a file deployment method, a file deployment system, an electronic device, and a computer-readable storage medium.

background

The shared CDN needs to provide stable service by using fragmented and unstable node devices, and thus naturally needs to consider more factors and be compatible with more abnormal scenarios on the basis of a conventional CDN (using a relatively stable machine room server) to achieve the purpose of providing stable service.

However, the service mode, service capability and service quality of the multi-type Peer are poor, and a fragmented and unstable node device needs to be used for providing stable service.

Therefore, how to improve the stability of the node device for providing the service is a problem to be solved by those skilled in the art.

disclosure of Invention

the application aims to provide a file deployment method, a file deployment system, an electronic device and a computer readable storage medium, and improve the stability of providing services by node devices.

in order to achieve the above object, the present application provides a file deployment method, which has the following specific technical scheme:

acquiring a deployment requirement;

selecting target node equipment from a node equipment group according to the deployment requirement, wherein the node equipment group comprises node equipment of multiple equipment types;

And deploying a target file on the target node device.

The deployment demand comprises any one or combination of any several of type guidance demand, income demand and equipment selection demand;

deploying a target file on the target node device comprises:

when the deployment requirement comprises the type vector quantity requirement, deploying the target file to node equipment of a specified type according to a preset proportion;

when the deployment requirement comprises the income requirement, improving the flow corresponding to a target domain name, a target area or a target operator to which the target file belongs;

and when the deployment requirement comprises the equipment selection requirement, increasing the point selection weight of the target node equipment.

Wherein, the file deployment method further comprises:

Judging whether the deployment requirement comprises a heat file requirement or not;

If yes, determining a heat gradient corresponding to the heat file in the heat file requirement;

configuring a first deployment parameter for the heat file according to the heat gradient;

And deploying the heat file on the node equipment corresponding to the heat file according to the first deployment parameter.

Configuring a first deployment parameter for the heat file according to the heat gradient, wherein the configuring further comprises:

And setting corresponding second deployment parameters and third deployment parameters for the domain name and the operator to which the heat file belongs according to the heat gradient.

wherein configuring a first deployment parameter for the heat file according to the heat gradient comprises:

obtaining historical running amount data;

And configuring a first deployment parameter for the heat file according to the historical running amount data and the heat gradient.

Before the node device is selected according to the deployment requirement, the method further includes:

Acquiring performance parameters of the node equipment;

Determining the service performance of each node device according to the performance parameters;

Selecting target node equipment from the node equipment group according to the deployment requirement as follows:

And selecting target node equipment from the node equipment group according to the deployment requirement and the service performance.

wherein selecting a target node device from a node device group according to the deployment requirement comprises:

and selecting the target node equipment by adopting a minimum heap algorithm according to the deployment requirement.

To achieve the above object, the present application provides an electronic device, which includes a memory and a processor, wherein the memory stores a file deployment program executable on the processor, and the file deployment program, when executed by the processor, implements:

Acquiring a deployment requirement;

and deploying a target file on the target node device.

to achieve the above object, the present application provides a file deployment system, including:

the acquisition module is used for acquiring the deployment requirement;

the device selection module is used for selecting target node devices from a node device group according to the deployment requirement, wherein the node device group comprises node devices of various device types;

and the file deployment module is used for deploying the target file on the target node equipment.

to achieve the above object, the present application provides a computer-readable storage medium, on which a file deployment program is stored, and the file deployment program, when executed by a processor, implements the steps of the file deployment method as described above.

according to the scheme, the file deployment method provided by the application comprises the following steps: acquiring a deployment requirement; selecting target node equipment from a node equipment group according to the deployment requirement, wherein the node equipment group comprises node equipment of multiple equipment types; and deploying a target file on the target node device. According to the method and the device, appropriate node equipment can be selected to deploy the target file according to deployment requirements. On the basis, different deployment modes can be adopted according to different deployment requirements, the deployment capability of P2P is greatly improved, the flow guidance is flexibly controlled, and the service quality enjoyed by a customer in a CDN mode is improved.

The application also discloses a file deployment system, an electronic device and a computer readable storage medium, which can also achieve the technical effects.

drawings

in order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only some embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the drawings without creative efforts.

fig. 1 is a flowchart of a file deployment method disclosed in an embodiment of the present application;

FIG. 2 is a flowchart of another file deployment method disclosed in an embodiment of the present application;

FIG. 3 is a flowchart of another file deployment method disclosed in an embodiment of the present application;

FIG. 4 is a block diagram of a file deployment system disclosed in an embodiment of the present application;

fig. 5 is a block diagram of an electronic device disclosed in an embodiment of the present application;

fig. 6 is a block diagram of another electronic device disclosed in the embodiments of the present application.

Detailed Description

In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The terms "first," "second," "third," "fourth," and the like in the description and in the claims of the present application and in the drawings described above, if any, are used for distinguishing between similar elements and not necessarily for describing a particular sequential or chronological order. It will be appreciated that the data so used may be interchanged under appropriate circumstances such that the embodiments described herein may be practiced otherwise than as specifically illustrated or described herein. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

it should be noted that the description relating to "first", "second", etc. in the present invention is for descriptive purposes only and is not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include at least one such feature. In addition, technical solutions between various embodiments may be combined with each other, but must be realized by a person skilled in the art, and when the technical solutions are contradictory or cannot be realized, such a combination should not be considered to exist, and is not within the protection scope of the present invention.

In the prior art, under a shared CDN mode, a service mode, service capability, and service quality of multiple types of peers are poor, and a fragmented and unstable node device needs to be used to provide a stable service, but at present, deployment of the node device is not enough to ensure a sufficiently stable service, and thus, a benefit of a customer is not affected very much.

therefore, the embodiment of the application discloses a file deployment method, which improves the stability of providing services by node equipment.

Referring to fig. 1, a flowchart of a file deployment method disclosed in an embodiment of the present application is shown in fig. 1, and includes:

s101: acquiring a deployment requirement;

s102: selecting target node equipment from a node equipment group according to deployment requirements, wherein the node equipment group comprises node equipment of multiple equipment types;

S103: and deploying a target file on the target node device.

firstly, receiving a deployment requirement, and then selecting target node equipment according to the deployment requirement. The types of devices in the node device group are not limited herein, and may include, for example, a guest cloud, a modem, a router, a television box, a smart television, an IPFS mining machine, a NAS, a personal computer, a server, and the like.

Preferably, the deployment requirement may include any one or a combination of any several of a type guidance requirement, a profit requirement, and a device selection requirement. The adopted deployment modes are different according to different deployment requirements. However, it should be noted that the deployment schemes corresponding to the requirements do not conflict with each other.

When the deployment requirement comprises a type vector requirement, deploying the target file to the node equipment of the specified type according to a preset proportion;

when a client needs to deploy a target file on a node device of a specified type, the node device of the type is specified according to the deployment requirement, and then the target file of a specified domain name is deployed. It should be noted that, in this process, the deployment is performed according to a preset ratio. It will be readily appreciated that other client files or different files of the same client may be present on the node device of the specified type. When the target file is deployed specifically, the specific deployment object of the target file should be made clear, and then actual deployment is performed according to the deployment proportion. Common different types of node devices include guest-playing clouds and the like. Briefly, when the deployment requirement comprises a type guidance requirement, guidance is performed according to the equipment type to meet the type guidance requirement of the customer. Of course, the default type vector requirement of the present embodiment includes the type content that the client needs to specify.

When the deployment requirement includes a revenue requirement, the traffic corresponding to the target domain name, the target region, or the target operator to which the target file belongs is increased, that is, the round-trip traffic is actually performed on the traffic corresponding to the target domain name, the target region, or the target operator to which the target file belongs.

In order to protect the profit of the client, when the client has a profit demand, the node device adopted by the client when deploying the target file is required to be in the highest operation state, that is, the node device is fully run to provide the maximum service, so that the client obtains the maximum profit. Specifically, when performing circle point derivation, control is usually performed for domain name dimension or domain name-area-operator dimension, that is, traffic of some domain names or domain name-area-operators is led to the node device. In short, when there is a revenue demand, for a node device, when a domain name or a region corresponding to a target file, or a customer that an operator needs for the revenue, the node device should operate at the maximum load. Of course, other operators, for other domain names or other areas where revenue demand does not exist, need not require that the node device run full.

And when the deployment requirement comprises an equipment selection requirement, improving the point selection weight of the target node equipment.

in order to make the overall flow rate tend to a certain node device set, the point selection weight of the target node devices can be increased, so that the probability of selecting the target node devices is increased, and naturally, the overall shared flow rate of the target node devices is also increased.

when the deployment requirement comprises any combination of type-derived requirement, profit requirement and equipment selection requirement, each deployment mode has no conflict.

When the deployment requirement contains type derivative requirement and profit requirement, then when the target file is deployed, only the node devices of the specified type can be targeted and the devices are required to run full when the target file is deployed.

When the deployment requirement includes a type vector requirement and an equipment selection requirement, when the target file is deployed, only the node equipment of the specified type can be targeted, but different point selection weights may exist in the node equipment of the type. For example, assuming that when a guest cloud is designated and two guest clouds are required, there are three guest clouds (guest cloud a, guest cloud B, guest cloud C) and the point selection weights of guest cloud a, guest cloud B, and guest cloud C are 1, 10, and 100, respectively, the probability of selecting guest cloud C is the largest, the probability of guest cloud B is the second, and the probability of guest cloud a is the smallest when the target file is actually deployed.

When the deployment requirement includes a benefit requirement and an equipment selection requirement, different types of node equipment may exist when the target file is deployed, but all the node equipment has corresponding point selection weights, and the selected node equipment should operate at the maximum load when the target file of the customer is deployed.

When the deployment requirement simultaneously comprises a type-derived requirement, a profit requirement and an equipment selection requirement, only the node equipment of a specified type in the type-derived requirement can be selected when the target file is deployed, and meanwhile, the corresponding point selection weight is configured for the node equipment of the type, and the selected node equipment is operated at the maximum load when the target file of the client is deployed.

According to the method and the device, the appropriate node equipment is selected to deploy the target file according to the deployment requirement. When the type vector demand exists, the target file is deployed to the node equipment of the specified type according to the demand, and the type vector demand of the client is met. When there is a revenue demand, a round-robin derivative will be executed so that node devices run full to guarantee the revenue demand of the customer with the maximum capacity to provide service. When the equipment selection requirement exists, the point selection weight of the target node equipment is improved, the selection probability of the target node equipment is improved, and then the overall sharing flow of the node equipment is improved. The method and the device greatly improve the capability of P2P deployment, flexibly control flow guidance and improve the service quality enjoyed by customers in a CDN mode.

The embodiment of the application discloses a file deployment method, and compared with the previous embodiment, the embodiment further optimizes and supplements the technical scheme. Specifically, the method comprises the following steps:

referring to fig. 2, a flowchart of another file deployment method provided in the embodiment of the present application is shown in fig. 2, where the file deployment method further includes:

S201: judging whether the deployment requirement comprises a heat file requirement or not; if yes, entering S202;

files with different heat degrees may exist in the target file, and sometimes a client needs to adopt different deployment strategies for the target files with different heat degrees, and the requirement is a heat file requirement.

s202: determining a heat gradient corresponding to the heat file in the heat file requirement;

The heat gradient is a division gradient of the heat degree of the target file, and a specific division manner of the heat gradient is not limited herein. Usually, a corresponding heat value is generated according to the click rate or the browsing volume of the target file in unit time, and then the heat interval is judged according to the heat value to determine the corresponding heat gradient of the heat file.

s203: configuring a first deployment parameter for the heat file according to the heat gradient;

the first deployment parameter is used for controlling the deployment flow of the target file.

s204: and deploying the heat file on the node equipment corresponding to the heat file according to the first deployment parameter.

The first deployment parameters are typically deployment volume and deployment time. For example, when there is a high-heat file in the target file, after determining the deployment parameter in step S202, the high-heat file needs to be deployed by 100 parts, and the deployment time is 2 hours, the high-heat file is deployed according to the deployment parameter during actual deployment.

it is easy to understand that the first deployment parameter is not fixed and may be a real-time setting value, or a parameter obtained by comprehensive configuration according to the historical running amount data and the heat gradient. Of course, if the historical running amount data is needed, the historical running amount data may also need to be acquired by default. In addition, the optimal first deployment parameter can be determined even through simulation under lines by referring to the historical volume situation of the client, so as to achieve the optimal effect of flow control.

it should be noted that S201 is generally executed after step S103 in the previous embodiment. That is, in the previous embodiment, S102 may determine on which node device the target file is specifically deployed, and the present embodiment specifically describes how to deploy the target file, that is, the target file may be deployed according to the heat of the target file.

Preferably, the step of executing S203 may further include:

it should be noted that the first deployment parameter corresponds to the node device level, the second deployment parameter is for a different domain name, and the third deployment parameter is for a different operator. That is to say, different hotness files have corresponding first deployment parameters, different domain names have corresponding second deployment parameters, and different operators have corresponding third deployment parameters. And the actual deployment parameters of each specific heat file are obtained by synthesizing the three deployment parameters. Different hotness files may belong to the same domain name or the same operator, and effective deployment can be achieved only according to the first deployment parameter. But the deployment of the same heat file under different domain names is not excluded, and the second deployment parameter and the first deployment parameter should be synthesized to perform effective deployment at this time.

The embodiment of the application discloses a file deployment method, and compared with the previous embodiment, the embodiment further explains and optimizes the technical scheme. Specifically, the method comprises the following steps:

referring to fig. 3, a flowchart of another file deployment method provided in the embodiment of the present application may further include, based on the foregoing embodiments, before selecting the node device according to the deployment requirement in step S102:

s301: acquiring performance parameters of node equipment;

S302: determining the service performance of each node device according to the performance parameters;

the embodiment aims to monitor the performance of the node equipment so as to exclude Peer which does not meet the service condition from the selected range and avoid instability of the node equipment with unqualified performance when providing service.

The specific content of the performance parameter is not limited herein, and may be any parameter related to the service performance, including but not limited to storage performance, task allocation frequency, processor performance, node device heartbeat, and the like, and more specifically, the storage performance may include disk size, disk occupancy, and the like. And finally, obtaining the service performance of the node equipment capable of carrying the service currently according to the performance parameters. The "selecting a target node device from a node device group according to the deployment requirement" is specifically "selecting a target node device from a node device group according to the deployment requirement and the service performance". It should be noted that step S102 in the foregoing embodiment is from the perspective of deployment requirements, and service performance is an inherent attribute of a node device, and the embodiment of the present application aims to preferentially select a node device with better service performance as a target node device while meeting the deployment requirements, so as to improve the deployment performance of a file. Therefore, the deployment requirement and the service performance are not in conflict, and the effect of file deployment can be better.

and only when the service performance of the node equipment meets the preset service condition standard or threshold, adding the node equipment into the available equipment pool as the equipment to be selected.

It is easy to understand that, due to the particularity in the CDN mode, performance parameters of each node device often change, so that the performance monitoring process provided in this embodiment may be performed before the target file is to be deployed each time, which effectively prevents the node device with poor service performance from affecting the external service performance in the whole CDN mode, and meanwhile, may also serve the node device with excellent service performance as a key task or a special task in a centralized manner, so that the traffic is excessively smooth, and jitter when peers share the traffic is avoided.

Further, based on the above embodiments, the present embodiment may also perform balance control of the node devices. And when the node equipment is selected, selecting the node equipment by adopting a minimum heap algorithm.

and using a minimum heap algorithm to preferentially look up the node equipment from the heap with the minimum number of looked-up times, and adding the looked-up node equipment into the alternative heap. That is, the heap is divided according to the viewed times, and then the node devices are viewed from the heap with the smallest viewed times first, and the node devices are viewed according to the viewed times of the node devices. The method aims to relatively balance the selected times of each node device, avoid the phenomenon that some node devices are frequently in a service state, and meanwhile, some node devices are rarely used, so that the point selection is unbalanced, and the service efficiency is reduced. And the node equipment is selected through the minimum heap algorithm, so that the balance of point selection can be realized.

In the following, a file deployment system provided in an embodiment of the present application is introduced, and a file deployment system described below and a file deployment method described above may be referred to each other.

Referring to fig. 4, a structure diagram of a file deployment system provided in the embodiment of the present application is shown in fig. 3, and includes:

An obtaining module 100, configured to obtain a deployment requirement;

An equipment selection module 200, configured to select target node equipment from a node equipment group according to the deployment requirement, where the node equipment group includes node equipment of multiple equipment types;

a file deployment module 300, configured to deploy a target file on the target node device.

based on the above embodiment, as a preferred embodiment, the deployment requirement includes any one or a combination of any several of a type guidance requirement, a profit requirement, and an equipment selection requirement;

The file deployment module includes:

The first deployment unit is used for deploying the target file to node equipment of a specified type according to a preset proportion when the deployment requirement comprises the type vector quantity requirement;

The second deployment unit is used for increasing the flow corresponding to a target domain name, a target area or a target operator to which the target file belongs when the deployment demand contains the income demand;

and the third deployment unit is used for increasing the point selection weight of the target node equipment when the deployment requirement comprises the equipment selection requirement.

Based on the foregoing embodiment, as a preferred embodiment, the file deployment system may further include:

the judging module is used for judging whether the deployment requirement comprises a heat file requirement or not;

The heat determining module is used for determining the heat gradient corresponding to the heat file in the heat file requirement when the judging result of the judging module is yes;

the first parameter configuration module is used for configuring first deployment parameters for the heat file according to the heat gradient;

and the second parameter configuration module is used for setting corresponding second deployment parameters and third deployment parameters for the domain name and the operator to which the heat file belongs according to the heat gradient.

preferably, the first parameter configuration module may include:

a running amount data acquisition unit for acquiring historical running amount data;

And the first parameter configuration unit is used for configuring a first deployment parameter for the heat file according to the historical running amount data and the heat gradient.

a parameter obtaining module, configured to obtain a performance parameter of the node device;

A parameter obtaining module, configured to determine service performance of each node device according to the performance parameter;

the file deployment module 300 is specifically configured to select a node device according to the service performance of each node device and deploy the target file according to the deployment requirement.

Selecting the node device according to the deployment requirement, and deploying a target file on the node device includes:

selecting the node equipment by adopting a minimum heap algorithm according to the deployment requirement;

and deploying a target file on the node equipment.

The application also provides an electronic device, which can be a PC (Personal Computer), and also can be a smartphone, a tablet Computer, a palmtop Computer, a portable Computer, an intelligent router, an ore machine, a network storage device (playing guest cloud) terminal device. The electronic device may be a node constituting a CDN network or a blockchain network.

Referring to fig. 5, a block diagram of an electronic device provided in an embodiment of the present disclosure, as shown in fig. 5, may include a memory 11, a processor 12, and a bus 13.

the memory 11 includes at least one type of readable storage medium, which includes a flash memory, a hard disk, a multimedia card, a card type memory (e.g., SD or DX memory, etc.), a magnetic memory, a magnetic disk, an optical disk, and the like. The memory 11 may in some embodiments be an internal storage unit of the electronic device, for example a hard disk of the electronic device. The memory 11 may also be an external storage device of the electronic device in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a flash Card (FlashCard), and the like, which are provided on the electronic device. Further, the memory 11 may also include both an internal storage unit and an external storage device of the electronic device. The memory 11 may be used not only to store application software for installing the electronic device and various types of data, such as the code of the file deployment program 01, but also to temporarily store data that has been output or is to be output.

The processor 12 may be a Central Processing Unit (CPU), a controller, a microcontroller, a microprocessor or other data Processing chip in some embodiments, and is configured to execute program codes or process data stored in the memory 11, so as to implement the file deployment method provided in any of the above embodiments, for example, execute the file deployment program 01.

The bus 13 may be a Peripheral Component Interconnect (PCI) bus, an Extended Industry Standard Architecture (EISA) bus, or the like. The bus may be divided into an address bus, a data bus, a control bus, etc. For ease of illustration, only one thick line is shown in FIG. 5, but this is not intended to represent only one bus or type of bus.

On the basis of the above embodiment, as a preferred implementation, referring to fig. 6, the electronic device further includes:

and the input interface 14 is used for acquiring computer programs, parameters and instructions imported from the outside, and controlling and storing the computer programs, the parameters and the instructions into the memory 11 through the processor 12. The input interface 14 may be connected to an input device for receiving parameters or instructions manually input by a user. The input device may be a touch layer covered on a display screen, a button, a trackball or a touch pad arranged on a terminal housing, a Keyboard (Keyboard), a touch pad or a mouse.

a display unit 15 for displaying data processed by the processor 12 and for displaying a visualized user interface. The display unit 15 may be an LED display, a liquid crystal display, a touch-controlled liquid crystal display, an OLED (Organic Light-Emitting Diode) touch device, and the like.

And a network port 16 for performing communication connection with each external terminal device. The communication technology adopted by the communication connection can be a wired communication technology or a wireless communication technology, such as a mobile high definition link (MHL) technology, a Universal Serial Bus (USB), a High Definition Multimedia Interface (HDMI), a wireless fidelity (WiFi), a bluetooth communication technology, a low power consumption bluetooth communication technology, an ieee802.11 s-based communication technology, and the like.

while FIG. 6 shows only an electronic device having components 11-16 and file deployment program 01, those skilled in the art will appreciate that the architecture shown in FIG. 6 does not constitute a limitation of electronic devices, and may include fewer or more components than shown, or some components in combination, or a different arrangement of components.

In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product.

The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the invention to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that a computer can store or a data storage device, such as a server, a data center, etc., that is integrated with one or more available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other manners. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.

The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed to by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.

It should be noted that the above-mentioned numbers of the embodiments of the present invention are merely for description, and do not represent the merits of the embodiments. And the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, apparatus, article, or method that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, apparatus, article, or method. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, apparatus, article, or method that includes the element.

the above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.

Claims

1. a file deployment method, comprising:

acquiring a deployment requirement;

and deploying a target file on the target node device.

2. The file deployment method according to claim 1, wherein the deployment requirement comprises any one or a combination of any several of a type-derivative requirement, a profit requirement and a device selection requirement;

Deploying a target file on the target node device comprises:

3. the file deployment method of claim 1, further comprising:

4. The file deployment method according to claim 2, wherein configuring the first deployment parameter for the heat file according to the heat gradient further comprises:

5. The file deployment method of claim 2, wherein configuring the first deployment parameter for the heat file according to the heat gradient comprises:

obtaining historical running amount data;

6. The file deployment method of claim 1, wherein before selecting the node device according to the deployment requirement, further comprising:

acquiring performance parameters of the node equipment;

7. The file deployment method of claim 1, wherein selecting the target node device from the node device group according to the deployment requirement comprises:

8. An electronic device comprising a memory and a processor, the memory having stored thereon a file deployment program executable on the processor, the file deployment program when executed by the processor implementing:

acquiring a deployment requirement;

And deploying a target file on the target node device.

9. A file deployment system, comprising:

the acquisition module is used for acquiring the deployment requirement;

10. A computer-readable storage medium, having stored thereon a file deployment program which, when executed by a processor, implements the steps of the file deployment method of any one of claims 1 to 7.