Method and device for resource management based on seismic operation characteristics in public cloud

Abstract

The present invention belongs to the field of geophysical exploration, and discloses a method and device for resource management based on seismic operation characteristics in a public cloud, the method comprising setting seismic operation characteristic information, defining the seismic operation characteristic information and instance type information on the cloud through a json format file; reading the seismic operation characteristic information and the instance type information on the cloud, and sending the seismic operation; releasing the seismic operation and applying for resources; acquiring resources and adding resources; and releasing resources. The present invention can quickly adapt the seismic operation to suitable resources in the public cloud platform, and dynamically scale the resources according to the amount of seismic operation, avoiding waiting and waste of resources, so that the seismic operation can be efficiently operated in the public cloud environment, and is suitable for processing seismic operations.

Description

Technical Field

[0001] The present invention relates to the field of geophysical exploration, and belongs to a technology for using and controlling seismic data processing operation resources in a public cloud environment. Specifically, it relates to a method and device for resource management based on seismic operation characteristics in a public cloud. Background Art

[0002] Seismic data processing is an important task in oil and gas exploration. Data collected in the field are processed by computer to guide subsequent geological interpretation and analysis. As the oil and gas exploration seismic data processing industry is rapidly developing in the direction of "high density, high precision, and intelligence", the seismic data that needs to be processed are numerous, with large amounts of data, complex calculations, and short cycles. There is a huge demand for computer computing power, which also increases computing costs.

[0003] When performing seismic data processing tasks, multiple independent tasks are carried out in parallel in the self-built data center and share resources. There is competition for resources, and it is impossible to dynamically scale resources according to the amount of seismic work. Resource waiting and waste are common. At the same time, there are hundreds of software modules used to process tasks, and each module has different computing and input-output characteristics (IO characteristics). Each processing task requires different amounts of resources and is configured with different CPUs, GPUs, memories, and disks, resulting in large performance differences. Therefore, the existing self-built data centers cannot efficiently cope with the increasingly complex seismic data processing tasks.

[0004] Compared with traditional self-built data centers, cloud computing platforms can provide virtual machines of various specifications and configurations, and easily expand resources to meet users' growing task processing needs in different scenarios. They can purchase cloud computing services based on actual needs, and have high availability to ensure the security and stability of user data and applications. They have been widely used in various industries. By increasing the application of public clouds, the digital transformation of oil and gas exploration and development business can be promoted, and the space for benefit mining can be effectively improved. Due to the above advantages of cloud computing, it is necessary to connect the existing task processing model with the cloud computing platform. Summary of the invention

[0005] In order to solve the above deficiencies in the prior art, the present invention aims to provide a method and device for resource management based on seismic operation characteristics in a public cloud, so as to quickly adapt suitable resources for seismic operations in a public cloud platform, and dynamically scale resources according to the amount of seismic operations to avoid waiting and waste of resources, so as to achieve the purpose of efficient operation of seismic operations in a public cloud environment.

[0006] To achieve the above-mentioned purpose, the technical scheme adopted by the present invention is as follows: a method for resource management based on seismic operation characteristics under a public cloud, comprising the following steps performed in sequence: S1, setting seismic operation characteristic information, defining the seismic operation characteristic information and the instance type information on the cloud through a json format file; S2, reading the seismic operation characteristic information and the instance type information on the cloud when sending the seismic operation, setting the queue information to which the seismic operation belongs according to the instance priority on the cloud and the model information contained in the seismic operation, and setting the seismic processing operation to be instance exclusive, and sending the seismic operation; S3, sorting the seismic operations to be released according to the priority, releasing the seismic operations that meet the release conditions, calling the public cloud interface according to the seismic operation resource requirements and the required instance type on the cloud, and applying for resources; S4, obtaining resources by calling the public cloud interface, and adding the resources to the instance information list on the cloud; S5, obtaining and traversing the instance list used by the seismic operation, deleting the corresponding instance in the instance information list on the cloud, and calling the public cloud interface at the same time to notify the public cloud platform to release resources.

[0007] As a limitation of the present invention: Step S1 specifically includes S11, generating a seismic operation characteristic information file, recording the characteristics of all seismic processing modules into the seismic operation characteristic information file for preservation; S12, generating a cloud instance type file, and saving the cloud instance type file into a file in json format; S13, scanning the seismic operation characteristic information file and the cloud instance type file, mapping the name of the cloud instance type file to the seismic operation queue name, and adding seismic operation running resource access control restrictions; S14, automatically synchronizing the seismic operation characteristic information file and the cloud instance type file manually modified by the user, and synchronously modifying the queue and resource access control restrictions.

[0008] As a limitation of the present invention: Step S2 specifically includes S21, user editing the seismic operation process; S22, reading the seismic operation feature information and the cloud instance type information, obtaining the best cloud instance type matching the seismic processing module and the cloud instance selection order rule information; S23, traversing all seismic processing modules used in the seismic operation process, finding the cloud instance type corresponding to each seismic processing module, and comparing the priority with the instance types corresponding to other modules in the seismic processing job, finding the cloud instance with the highest instance priority, and using the name of the cloud instance with the highest priority as the seismic operation queue name; S24, setting the exclusive flag of the seismic processing job to instance exclusive; S25, sending the seismic job.

[0009] As a limitation of the present invention: Step S3 specifically includes S31, obtaining information of all seismic operations to be released, and sorting the seismic operations to be released according to priority; S32, filtering the seismic operations that do not meet the release conditions; S33, releasing the seismic operations that meet the release conditions; S34, when the seismic operation is released, if the cloud instance resources required for the seismic operation have been successfully created, the seismic operation is released to the instance for running; if the cloud instance resources have not been successfully created, the interface provided by the public cloud is called according to the cloud instance resource information required for the seismic operation to apply for resources.

[0010] As a limitation of the present invention: Step S4 specifically includes calling the public cloud interface to query the instance resource information applied for the seismic operation in step S3, the resource information is the cloud instance information, and when the resources returned by the public cloud interface are not added to the cloud instance, the resources are added to the cloud instance information list.

[0011] As a limitation of the present invention: Step S5 specifically includes obtaining a list of running instances of seismic operations, traversing the list of instances used by seismic operations, deleting the instances running seismic operations from the list of instance information on the cloud, and calling a public cloud interface to notify the public cloud platform to release resources.

[0012] As a limitation of the present invention: a device for resource management based on seismic operation characteristics under a public cloud, including a seismic operation characteristic information setting module, which is used to set seismic operation characteristic information, and define the seismic operation characteristic information and cloud instance type information through a json format file; a seismic operation sending module, which is used to obtain seismic operations and send seismic operations; a seismic operation release and resource application module, which is used to release seismic operations sent by users, and call the interface provided by the public cloud to apply for resources; a resource acquisition and resource addition module, which is used to call the resource query interface provided by the public cloud, obtain resource information, and add resources to the cloud instance information list; a resource release module, which is used to obtain a list of running instances of seismic operations and notify the public cloud platform to release resources.

[0013] As a limitation of the present invention: a computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, the method for resource management based on seismic operation characteristics under the public cloud is implemented.

[0014] As a limitation of the present invention: a computer-readable storage medium stores a computer program for executing the method for resource management based on seismic operation characteristics in the public cloud.

[0015] Due to the adoption of the above technical solution, the beneficial effect achieved by the present invention compared with the prior art is that: by combining the characteristic information of the seismic operation when sending the seismic operation, calling the public cloud interface, creating the resources required for the seismic operation on the public cloud platform, releasing the seismic operation to run on the created resources, and after the seismic operation is completed, the public cloud platform releases the resources used by the seismic operation. Therefore, the above method can quickly adapt the seismic operation to the appropriate resources in the public cloud platform, ensure the optimal matching of seismic operation resources, and quickly assemble and invest computing resources that can process a large amount of exploration data; at the same time, according to the amount of seismic operation, it realizes dynamic scaling of resources, avoids waiting and waste of resources, so that the seismic operation can run efficiently in the public cloud environment, reduces computing costs, ensures economic benefits, and realizes the business needs of connecting seismic data processing with the public cloud, thereby more accurately describing the geological structure. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] The present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0017] Figure 1 This is a flow chart of Embodiment 1 of the present invention;

[0018] Figure 2 This is a flow chart of automatic feature synchronization in Example 1 of the present invention;

[0019] Figure 3 A flowchart of the seismic operation sent by Embodiment 1 of the present invention;

[0020] Figure 4 This is a flow chart of the seismic operation release of Example 1 of the present invention;

[0021] Figure 5 A flowchart of resources added in Example 1 of the present invention;

[0022] Figure 6 This is a flowchart of resource release in Example 1 of the present invention;

[0023] Figure 7 This is a flowchart of abnormal resource release in Example 1 of the present invention;

[0024] Figure 8 This is a structural block diagram of Embodiment 2 of the present invention;

[0025] Fig. 9 This is a schematic diagram of the structure of a computer device according to Embodiment 3 of the present invention. DETAILED DESCRIPTION

[0026] The preferred embodiments of the present invention are described below in conjunction with the accompanying drawings. It should be understood that the method and device for resource management based on seismic operation characteristics in a public cloud described herein are preferred embodiments, which are only used to illustrate and explain the present invention and do not constitute a limitation on the present invention.

[0027] Example 1

[0028] A resource management method based on seismic operation characteristics in a public cloud, such as Figure 1 As shown, the method comprises the following steps performed in sequence:

[0029] S1. Set the seismic operation feature information, and define the seismic operation feature information and cloud instance type information through a json format file;

[0030] S1 specifically includes the following steps:

[0031] S11, generating a seismic operation characteristic information file, recording the characteristics of all seismic processing modules into the seismic operation characteristic information file for storage;

[0032] Specifically, each seismic operation includes multiple seismic processing modules, and each record in the seismic operation feature information file includes three keywords, namely, the name of the seismic processing module, the best cloud instance type matched by the seismic processing module, and the number of concurrent seismic processing modules supported by the current IO bandwidth. Among them, the best cloud instance type matched by the seismic processing module contains three items, namely, CPU memory and GPU memory, local disk configuration information, and the number of concurrent seismic processing modules supported by the current IO bandwidth. Since the IO bandwidth on the cloud depends on the storage capacity and storage type occupied by the processed data, and the same seismic processing module has different IO requirements in different processing steps, when the data is rearranged, the domain is changed or the domain is unchanged, the difference in IO requirements is large. In order to ensure the concurrent efficiency of the module, it is necessary to mark the feature of the number of concurrent seismic processing modules supported by the IO bandwidth. The marked feature is saved as the first external file in json format, which records the best cloud instance type matched by the module. Therefore, the file in json format can be used to describe the best cloud instance type.

[0033] S12. Generate an instance type file on the cloud, and save the instance type file on the cloud to a file in json format;

[0034] Specifically, each record in the cloud instance type file includes two keywords, namely, the cloud instance type and the cloud instance priority, and the cloud instance type and the cloud instance priority are saved in an external json file. Since the seismic operation includes multiple seismic processing modules, the number of which can reach hundreds, it is necessary to determine the characteristics of the selected seismic processing module through the selection order rule of the cloud instance, and use it as the characteristics of the seismic operation. The selection order rule of the cloud instance includes two keywords, namely, the best cloud instance type and the cloud instance priority for the operation of the seismic processing module. If the seismic processing module in the seismic operation corresponds to different cloud instance types, the cloud instance type with the highest priority defined in the selection order rule of the cloud instance is selected as the instance type of the seismic operation. The selection order rule of the cloud instance is saved as a second external file in json format, which records the selection order rule of the cloud instance, so the selection order rule of the cloud instance can be described using a file in json format.

[0035] S13, scanning the seismic operation feature information file and the instance type file on the cloud, mapping the name of the instance type file on the cloud to the seismic operation queue name, and adding access control restrictions on seismic operation running resources;

[0036] Specifically, each seismic job belongs to a specific queue, and resource usage of the queue can be restricted. The mapping process is a prior art. When releasing a seismic job, the seismic job can only be released to run in a cloud instance type file with the same name as the seismic job queue. For example, a seismic job restricted to queue A can only use specific resources, so that the seismic job can only be released to run on the cloud instance applied for the seismic job, and will not be released to run on resources applied for other seismic jobs. Therefore, when releasing a seismic job, if the name of the seismic job is different from that of the seismic job queue, the seismic job will not be released.

[0037] S14. Automatically synchronize the seismic operation feature information file manually modified by the user and the instance type file on the cloud, and synchronously modify the queue and resource access control restrictions;

[0038] Specifically, by reading the instance type file on the cloud, obtaining the rule parameters of the instance on the cloud, using the rule name as the seismic job queue name, and automatically setting the seismic job running resource access control restrictions to limit the seismic job to run on the aforementioned seismic job queue. Figure 2As shown, the instance type file on the cloud is read to obtain the instance type information on the cloud, and the obtained instance information is traversed. During the traversal process, if the current instance type information is not added to the seismic operation queue, the seismic operation operation resource access control restriction is added to limit the seismic operation characteristics to the corresponding seismic operation queue until the instance information traversal is completed. When the user manually adjusts the seismic operation feature information file and the instance type file on the cloud in the actual production process, this step can also periodically scan the above files to see if the content has changed. If the content of the above files has changed, the seismic operation feature information file and the instance type file on the cloud modified by the user will be automatically synchronized and updated, and the modified information will be used to update the saved seismic operation queue name and seismic operation operation resource access control restriction.

[0039] S2. When sending a seismic job, read the seismic job feature information and the instance type information on the cloud, set the queue information to which the seismic job belongs according to the instance priority on the cloud and the information that the seismic job contains the seismic processing module, set the seismic processing job to be instance exclusive, and send the seismic job;

[0040] S2 specifically includes the following steps:

[0041] S21, user edits seismic operation process;

[0042] S22, reading the seismic operation feature information and the cloud instance type information, and obtaining the best cloud instance type and cloud instance selection order rule information matching the seismic processing module;

[0043] S23, traverse all seismic processing modules used in the seismic operation process, find the cloud instance type corresponding to each seismic processing module, compare the priority with the instance types corresponding to other modules in the seismic processing operation, find the cloud instance with the highest instance priority, and use the name of the cloud instance with the highest priority as the seismic operation queue name;

[0044] S24, setting the exclusive flag of the seismic processing job to instance exclusive;

[0045] S25, sending a seismic operation;

[0046] Specifically, Figure 3As shown, when the user sends a seismic operation, the seismic processing module feature information file is read to obtain the seismic operation feature information, the cloud instance information that is compatible with the seismic processing module is obtained, and the cloud instance type file is read to obtain the instance priority level. According to the seismic processing module list obtained in the seismic operation file, the multiple seismic processing modules that constitute the seismic operation are parsed. Through the best cloud instance type and the selection order rules of the cloud instance, the seismic operation queue is first set to the lowest level of resource features, the instance type with the lowest priority in the cloud instance type file is set for the current seismic operation, and then the seismic processing modules in the seismic operation are traversed. If the best cloud instance type corresponding to the seismic processing module can be obtained, the information of the best cloud instance type corresponding to the seismic processing module is compared with the best cloud instance type set in the current seismic job. When the seismic processing module feature is found to have a higher priority, the high-priority cloud instance type is set to the seismic job, and the queue feature of the seismic job is set to the feature of the current seismic processing module. After all seismic processing modules are traversed, the best cloud instance type for the seismic job is identified, and the exclusive flag in the seismic job is set to instance exclusive to ensure that only one seismic job is run in a cloud instance, and then the seismic job is sent. The sending of the seismic job is to collect the relevant parameters of the seismic job through commands or interfaces.

[0047] S3. Sort the seismic operations to be released according to their priorities, release the seismic operations that meet the release conditions, and call the public cloud interface to apply for resources according to the seismic operation resource requirements and the required cloud instance types;

[0048] S3 specifically includes the following steps:

[0049] S31, obtaining information of all seismic operations to be released, and sorting the seismic operations to be released according to priority;

[0050] Specifically, after obtaining the seismic operation information, all the seismic operations to be released are sorted by priority, and the seismic operations are released on a first-come, first-served basis. The longer the waiting time of the seismic operation, the higher its priority.

[0051] S32, filtering the seismic operations that do not meet the release conditions;

[0052] Specifically, there are two types of seismic operations that fail to meet the release conditions, which usually set other release conditions. One is that the user specifies the release time of the seismic operation. If the start time of the seismic operation has not arrived, the seismic operation will not be released; the other is that the current seismic operation depends on the completion of the previous seismic operation. When the previous seismic operation has not been completed, the seismic operation will not be released.

[0053] S33, releasing the seismic operation that has reached the release condition;

[0054] S34: When releasing the seismic operation, if the cloud instance resources required by the seismic operation have been successfully created, the seismic operation is released to the instance for running; if the cloud instance resources have not been successfully created, the interface provided by the public cloud is called according to the cloud instance resource information required by the seismic operation to apply for resources;

[0055] Specifically, determine whether the current seismic operation has applied for resources. If the current seismic operation has not applied for resources, call the interface provided by the public cloud to apply for resources for the current seismic operation; if the current seismic operation has applied for resources, and determine whether the time for applying for resources has reached the threshold through the recorded calling time of the public cloud resource application interface. If the time for applying for resources for the current seismic operation has reached the threshold, it is considered that the seismic operation resource application has failed, and continue to call the interface provided by the public cloud to apply for resources again for the current seismic operation; if resources have been applied for the current seismic operation and the applied resources have been added to the instance list, release the current seismic operation to the cloud instance for running.

[0056] Specifically, Figure 4 As shown, the seismic operation release process includes resource application. All seismic operations to be released are sorted according to priority, and the seismic operations in the release cycle are traversed to determine whether the seismic operation has applied for resources. If the seismic operation has not applied for resources, the public cloud interface is called to apply for resources for the seismic operation, wherein the parameters passed to the public cloud through the public cloud interface are the cloud instance type and the number of cloud instances. After receiving the request to apply for resource creation, the public cloud platform will create the resources required for the seismic operation. After calling the public cloud resource application interface, the seismic operation resource application time is marked in the seismic operation information, and the seismic operation is released by timing, and according to the seismic operation information, it is determined whether the seismic operation has applied for and obtained resources. If the seismic operation has applied for resources, and the resources have been obtained and created within the threshold time, the seismic operation is released to the cloud instance for operation; if the resources have not been obtained within the threshold time, the public cloud interface is called to apply for resources for the seismic operation again, and the seismic operation resource application time is marked until the current release cycle ends or the seismic operation traversal is completed. Among them, the application and acquisition of resources are asynchronous processes. The seismic operation can only be released after the seismic operation obtains the resources.

[0057] Furthermore, since the public cloud resource application and release interfaces called during the seismic operation release and resource application process are all asynchronous interfaces, in order to avoid anomalies in the seismic operation release and resource application, which may result in the seismic operation being unable to obtain resources or the seismic operation not being released, this embodiment also provides a method for detecting anomalies in the seismic operation release and resource application to reduce the cost of use.

[0058] The abnormal detection method for seismic operation release and resource application includes recording the time used to apply for resources in the seismic operation information after applying for resources for the seismic operation. In each seismic operation release cycle, the time used to apply for resources is detected. When the seismic operation does not obtain resources for a long time, it is considered that the resource application of the seismic operation has failed, and then resources will be applied for the seismic operation again. For seismic operations that are not released normally, such as Figure 7 As shown, by setting an idle time count for all resource instances, when the idle time of a resource instance reaches a certain threshold, it is considered that the earthquake operation has failed to be released, the information of this instance resource is deleted from the cloud instance list, and the public cloud platform is notified to release the resource instance. Among them, the idle time threshold of the instance resource is preferably 10 minutes.

[0059] S4. Obtain resources by calling the public cloud interface and add the resources to the instance information list on the cloud;

[0060] Specifically, Figure 5 As shown, by calling the public cloud interface, the instance resource information applied for the seismic operation in step S3 is queried. After the instance information applied is obtained, the instance information is traversed. If the instance is not added, the instance information is added to the cloud instance list until the instance information is traversed. In this step, the instance information specifically includes the cloud instance hardware information and the cloud instance type information. The cloud instance hardware information includes CPU memory, GPU memory, and shared disk information. Since resource acquisition and resource addition are asynchronous processes, and the cloud instance is created in the public cloud environment, it is necessary to regularly query whether the current public cloud has completed the creation of the cloud instance, and synchronize the created cloud instance to facilitate the addition of the cloud instance provided by the public cloud. In this embodiment, the instance information is obtained by regularly calling the instance query interface provided by the public cloud. If the instance returned by the public cloud instance query interface is not added to the cloud instance list, the instance is added to the cloud instance information list; if the returned instance has been added to the cloud instance, the returned instance will be ignored and skipped.

[0061] S5. Obtain and traverse the instance list used in the seismic operation, delete the corresponding instance in the instance information list on the cloud, and call the public cloud interface to notify the public cloud platform to release resources;

[0062] Specifically, Figure 6 As shown in the figure, when the earthquake operation is completed, the instance resources need to be released. Since the resource release is an asynchronous process, the abnormality of resource release needs to be detected. By obtaining the instance list used by the earthquake operation, traversing the instance list used by the earthquake operation, the instance running the earthquake operation is deleted from the instance list, that is, the instance information that has been traversed in the instance list is deleted, and the public cloud platform interface is called at the same time, and the public cloud platform is notified to release this instance until the instance list used by the earthquake operation is traversed, and then the resource release is completed through the public cloud platform. Among them, the instance is the cloud instance that has been created by the public cloud. In addition, to ensure that all resources can be released, by regularly traversing all instances in the current instance list, if it is found that there is no earthquake operation running for a long time, the resource release process will also be started, and the public cloud platform will be notified to release the instance resources.

[0063] Example 2

[0064] A resource management device based on seismic operation characteristics in a public cloud, such as Figure 8 As shown, including:

[0065] The earthquake operation characteristic information setting module is used to set the earthquake operation characteristic information and define the earthquake operation characteristic information and cloud instance type information through a json format file, specifically:

[0066] Generate a seismic operation feature information file, record the features of all seismic processing modules in the seismic operation feature information file for storage; generate a cloud instance type file, save the cloud instance type file in a json format file; scan the seismic operation feature information file and the cloud instance type file, map the name of the cloud instance type file to the seismic operation queue name, and add seismic operation running resource access control restrictions; automatically update the seismic operation feature information file and the cloud instance type file modified by the user.

[0067] The seismic job sending module is used to read the seismic job feature information and the cloud instance type information, set the seismic job queue name according to the cloud instance priority, and set the seismic processing module to instance exclusive to send the seismic job. Specifically:

[0068] The user edits the seismic operation process; reads the seismic operation feature information and cloud instance type information, and reads the best cloud instance type matching the seismic processing module and the cloud instance selection order rule; traverses all seismic processing modules used in the seismic operation process, finds the cloud instance type corresponding to each seismic processing module, compares it with the instance type of the seismic processing module, finds the cloud instance with the highest priority, and uses the name of the cloud instance with the highest priority as the seismic operation queue name; sets the exclusive flag of the seismic processing module to instance exclusive; and sends the seismic operation.

[0069] The seismic operation release and resource application module is used to sort the seismic operations to be released according to their priorities, release the seismic operations that meet the release conditions, and call the public cloud interface to apply for resources according to the seismic operation resource requirements and the required cloud instance types. Specifically:

[0070] Get the information of all earthquake jobs to be released, sort them by priority; filter the earthquake jobs that do not meet the release conditions; release the earthquake jobs that meet the release conditions; when releasing the earthquake job, if the cloud instance resources required by the earthquake job have been successfully created, release the earthquake job to the instance to run; if the cloud instance resources have not been successfully created, call the interface provided by the public cloud according to the cloud instance resource information required by the earthquake job to apply for resources.

[0071] The resource acquisition and resource addition module is used to call the public cloud interface to obtain resources and add resources to the instance information list on the cloud. Specifically:

[0072] By calling the public cloud interface, resource information is obtained for seismic operations. The resource information is the cloud instance information. When the resources returned by the public cloud interface are not added to the cloud instance, the resources are added to the cloud instance information list.

[0073] The resource release module is used to obtain the list of running instances of the seismic operation and notify the public cloud platform to release resources. Specifically:

[0074] Get the list of running instances of the seismic operation, traverse the list of instances used by the seismic operation, delete the instance running the seismic operation from the instance information list on the cloud, and call the public cloud interface to notify the public cloud platform to release resources.

[0075] Example 3

[0076] The electronic device of this embodiment includes a memory and a processor. The memory stores a computer program. The processor calls the computer program in the memory to execute a method of resource management based on seismic operation characteristics in a public cloud in Example 1. Fig. 9The schematic diagram of the structure of the electronic device provided in this embodiment, the electronic device may be a terminal device or a server. The terminal device may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (Portable Android Devices, PADs), portable multimedia players (Portable Media Players, PMPs), vehicle terminals (such as vehicle navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Fig. 9 The electronic device shown is only an example and should not bring any limitation to the functions and scope of use of the present embodiment.

[0077] like Fig. 9 As shown, the electronic device may include a processing device, such as a central processing unit, a graphics processing unit, etc., which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) or a program loaded from a storage device to a random access memory (RAM). In the RAM, various programs and data required for the operation of the electronic device are also stored. The processing device, ROM and RAM are connected to each other through a bus. The input device, output device, communication device and storage device are also connected to the bus through an I / O interface.

[0078] Typically, the following devices can be connected to the I / O interface: input devices such as touch screens, touch pads, keyboards, mice, cameras, microphones, accelerometers, gyroscopes, etc.; output devices such as liquid crystal displays (LCDs), speakers, vibrators, etc.; storage devices such as magnetic tapes, hard disks, etc.; and communication devices. Communication devices can allow electronic devices to communicate with other devices wirelessly or by wire to exchange data. Although Fig. 9 An electronic device having various devices is shown, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0079] Example 4

[0080] The computer-readable storage medium of this embodiment stores a computer program, and when the computer program is executed by the processor, it is used to implement a method for resource management based on seismic operation characteristics in a public cloud in Example 1. The computer-readable storage medium of this embodiment may be included in an electronic device, or may exist independently without being assembled into the electronic device.

[0081] The computer-readable storage medium of this embodiment may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or component, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that may be used by or in conjunction with an instruction execution system, device, or component.

[0082] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present disclosure, rather than to limit them. Although the present disclosure has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or replace some or all of the technical features therein by equivalents. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present disclosure.

Claims

1. A method for resource management based on seismic operation characteristics in a public cloud, characterized in that: The method comprises the following steps performed in sequence: S1. Generate an earthquake operation characteristic information file, record the characteristics of all earthquake processing modules into the earthquake operation characteristic information file for storage, wherein the characteristics of the earthquake processing module include three keywords, namely, the earthquake processing module name, the best cloud instance type matched by the earthquake processing module, and the number of earthquake processing module concurrency supported by the current IO bandwidth; generate a cloud instance type file, save the cloud instance type file into a json format file, wherein the cloud instance type file includes two keywords, namely, the cloud instance type and the cloud instance priority, and define the earthquake operation characteristic information and the cloud instance type information through the json format file; scan the earthquake operation characteristic information file and the cloud instance type file, map the name of the cloud instance type file to the earthquake operation queue name, and add earthquake operation operation resource access control restrictions; automatically synchronize the earthquake operation characteristic information file and the cloud instance type file manually modified by the user, and synchronously modify the queue and resource access control restrictions; S2. When sending an earthquake operation, the user edits the earthquake operation process; reads the earthquake operation feature information and the cloud instance type information, obtains the best cloud instance type matching the earthquake processing module and the cloud instance selection order rule information; traverses all earthquake processing modules used in the earthquake operation process, finds the cloud instance type corresponding to each earthquake processing module according to the cloud instance priority and the earthquake operation contains earthquake processing module information, compares the priority with the instance types corresponding to other modules in the earthquake processing operation, finds the cloud instance with the highest instance priority, uses the name of the cloud instance with the highest priority as the earthquake operation queue name, and sets the queue characteristics of the earthquake operation to the characteristics of the current earthquake processing module; sets the exclusive flag of the earthquake operation to instance exclusive; sends the earthquake operation; S3. Obtain the information of all earthquake operations to be released, and sort the earthquake operations to be released according to priority; filter out the earthquake operations that do not meet the release conditions, where the release conditions include that the earthquake operation release time specified by the user has not arrived, and the earthquake operation on which the current earthquake operation depends in the previous step has not been completed; release the earthquake operations that meet the release conditions, and call the public cloud interface to apply for resources according to the earthquake operation resource requirements and the required cloud instance type; when releasing the earthquake operation, if the earthquake operation has not applied for resources, call the interface provided by the public cloud to apply for resources for the current earthquake operation; if the earthquake operation has applied for the required cloud instance resources, and the resources have been obtained and created successfully within the threshold time, release the earthquake operation to the instance for running; if the cloud instance resources have not been created successfully within the threshold time, call the interface provided by the public cloud according to the cloud instance resource information required by the earthquake operation, apply for resources for the earthquake operation again, and mark the earthquake operation resource application time; S4. Obtain resources by calling the public cloud interface and add the resources to the instance information list on the cloud; S5. When the seismic operation is completed, obtain and traverse the cloud instance information list used by the seismic operation, delete the corresponding instance in the cloud instance information list, and call the public cloud interface at the same time to notify the public cloud platform to release resources. Periodically traverse all instances in the current instance list. If it is found that no seismic operation has been running for a long time, the public cloud platform will also be notified to release resources.

2. The method for resource management based on seismic operation characteristics in a public cloud according to claim 1, characterized in that: Step S4 specifically includes: By calling the public cloud interface, query the instance resource information applied for the seismic operation in step S3. The resource information is the instance information on the cloud. When the resources returned by the public cloud interface are not added to the instance on the cloud, add the resources to the instance information list on the cloud.

3. A resource management device based on seismic operation characteristics in a public cloud, characterized in that: include: The earthquake operation characteristic information setting module is used to generate an earthquake operation characteristic information file, record the characteristics of all earthquake processing modules into the earthquake operation characteristic information file for storage, wherein the characteristics of the earthquake processing module include three keywords, namely, the earthquake processing module name, the best cloud instance type matching the earthquake processing module, and the number of earthquake processing module concurrency supported by the current IO bandwidth; generate a cloud instance type file, save the cloud instance type file into a json format file, wherein the cloud instance type file includes two keywords, namely, the cloud instance type and the cloud instance priority, and define the earthquake operation characteristic information and the cloud instance type information through the json format file; scan the earthquake operation characteristic information file and the cloud instance type file, map the name of the cloud instance type file to the earthquake operation queue name, and add earthquake operation operation resource access control restrictions; automatically synchronize the earthquake operation characteristic information file and the cloud instance type file manually modified by the user, and synchronously modify the queue and resource access control restrictions; The seismic operation sending module is used to send seismic operations. The user edits the seismic operation process; reads the seismic operation feature information and the cloud instance type information, obtains the best cloud instance type matching the seismic processing module and the cloud instance selection order rule information; traverses all seismic processing modules used in the seismic operation process, finds the cloud instance type corresponding to each seismic processing module according to the cloud instance priority and the seismic operation contains seismic processing module information, compares the priority with the instance types corresponding to other modules in the seismic processing operation, finds the cloud instance with the highest instance priority, uses the name of the cloud instance with the highest priority as the name of the seismic operation queue, and sets the queue characteristics of the seismic operation to the characteristics of the current seismic processing module; sets the exclusive flag of the seismic operation to instance exclusive; and sends the seismic operation; The earthquake operation release and resource application module is used to obtain the information of all earthquake operations to be released, and sort the earthquake operations to be released according to priority; filter the earthquake operations that do not meet the release conditions, and the conditions that do not meet the release conditions include that the earthquake operation release time specified by the user has not arrived, and the earthquake operation on which the current earthquake operation depends in the previous step has not been completed; release the earthquake operation for the earthquake operation that meets the release conditions, and call the public cloud interface to apply for resources according to the earthquake operation resource requirements and the required cloud instance type; when the earthquake operation is released, if the earthquake operation has not applied for resources, call the interface provided by the public cloud to apply for resources for the current earthquake operation; if the earthquake operation has applied for the required cloud instance resources, and the resources are obtained and created successfully within the threshold time, release the earthquake operation to the instance for running; if the cloud instance resources are not created successfully within the threshold time, call the interface provided by the public cloud according to the cloud instance resource information required by the earthquake operation, apply for resources for the earthquake operation again, and mark the earthquake operation resource application time; Resource acquisition and resource addition modules are used to call the resource query interface provided by the public cloud, obtain resource information, and add resources to the instance information list on the cloud; The resource release module is used to obtain and traverse the cloud instance information list used by the seismic operation after the seismic operation is completed, delete the corresponding instance in the cloud instance information list, and call the public cloud interface to notify the public cloud platform to release resources.

4. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the method for resource management based on seismic operation characteristics in the public cloud as described in claim 1 or 2 is implemented.

5. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program for executing the method for resource management based on seismic operation characteristics in a public cloud as described in claim 1 or 2.

Images