CN111580953A

CN111580953A - Method and device for manufacturing scheduling simulation scene, storage medium and electronic equipment

Info

Publication number: CN111580953A
Application number: CN201910127991.2A
Authority: CN
Inventors: 徐新坤; 张伟伟; 鲍永成; 刘海锋
Original assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Jingdong Shangke Information Technology Co Ltd
Current assignee: Beijing Jingdong Century Trading Co Ltd; Beijing Jingdong Shangke Information Technology Co Ltd
Priority date: 2019-02-19
Filing date: 2019-02-19
Publication date: 2020-08-25

Abstract

The disclosure relates to a method and a device for manufacturing a scheduling simulation scene, a storage medium and an electronic device. The manufacturing method comprises the following steps: recording the node attribute of each node and the container attribute of each container in the real cluster at the same time through snapshot capture, and storing the node attribute and the container attribute; and recording event information for describing a real event which causes any one of the nodes and the containers in the real cluster to change after the snapshot is captured through the event record, and storing the event information. The node attributes and the container attributes are respectively used as initial parameters of each simulated node and each simulated container in the cloud platform scheduling simulation scene, and the event information is used as an event to be generated which is simulated in the cloud platform scheduling simulation scene. Therefore, the requirement of a test scheduling algorithm of the scheduling simulation system can be met, and the labor intensity of manual manufacturing of the cloud platform scheduling simulation scene is greatly reduced.

Description

Method and device for manufacturing scheduling simulation scene, storage medium and electronic equipment

Technical Field

The invention relates to a cloud platform simulation technology in general, and particularly relates to a method and a device for manufacturing a cloud platform scheduling simulation scene, a storage medium and electronic equipment.

Background

As virtualization technology evolves, more and more companies move their own online applications to the cloud platform. Container technology can be thought of as an operating system level virtualization. The original purpose is to reduce the performance overhead caused by virtualization technologies represented by the Hypervisor technology, and machine resources can be utilized at a finer granularity.

The cloud platform is provided with a computer Cluster (Cluster) on a physical layer, wherein the Cluster comprises a plurality of nodes, and the nodes are minimum computing hardware units. The containers are deployed in the computer cluster for unified management and external service provision.

The resource scheduling is an important problem to be solved by a container cluster management system, and the resource scheduling refers to selecting a node suitable for deploying a container from a plurality of nodes of a cluster through a certain rule for the container to be deployed.

When a resource scheduling algorithm needs to be debugged or evaluated, thousands of nodes are generally managed, so that it is difficult to separately establish a huge computer cluster for evaluating the resource scheduling algorithm in reality, and a cloud platform which provides services for customers cannot be used as a test platform, but the resource scheduling algorithm for testing can be performed on a scheduling simulation system.

When the scheduling simulation system tests the pressure measurement scheduling algorithm, a cloud platform scheduling simulation scene needs to be provided to simulate a scene of a cluster during real operation. However, in the prior art, a simple method for making a cloud platform scheduling simulation scene is not available, a large amount of simulation data needs to be made manually to simulate a cluster and events occurring in the cluster, and the workload is particularly heavy.

The above information disclosed in this background section is only for enhancement of understanding of the background of the invention and therefore it may contain information that does not constitute prior art that is already known to a person of ordinary skill in the art.

Disclosure of Invention

In this summary, concepts in a simplified form are introduced that are further described in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

One of the main objects of the present invention is to overcome at least one of the above drawbacks of the prior art, and to provide a method for making a cloud platform scheduling simulation scenario, which includes the following steps: recording the node attribute of each node and the container attribute of each container in the real cluster at the same time through snapshot capture, and storing the node attribute and the container attribute; and recording event information for describing a real event which causes any one of the nodes and the containers in the real cluster to change after the snapshot is captured through an event record, and storing the event information.

According to one embodiment of the invention, snapshot capturing is carried out once at preset time intervals, and a snapshot file used for recording information obtained by current snapshot capturing and capturing time of the current snapshot capturing is newly generated;

and newly generating an event file for recording the recorded event information after the snapshot is taken and before the snapshot is taken next time after the snapshot is taken each time.

According to one embodiment of the invention, the snapshot files are numbered continuously from small to large according to the sequence of the generation of the snapshot files, the event files are numbered continuously from small to large according to the sequence of the generation of the event files, and the initial values of the numbers of the snapshot files and the event files are the same.

According to one embodiment of the invention, the size of the capturing time recorded in the snapshot file is compared with the size of the specified time, the snapshot file with the capturing time not earlier than the specified time and the capturing time closest to the specified time and all event files with the number not less than that of the snapshot file are searched, and the event information recorded in the searched event files is written into one event file according to the sequence of the occurrence of the real events.

According to an embodiment of the present invention, the preset first time is earlier than the preset second time, the first snapshot file whose capturing time is not earlier than the first time and is closest to the first time, the second snapshot file whose capturing time is not earlier than the second time and is closest to the second time, and all event files whose numbers are not less than the first snapshot file and not more than the second snapshot file are found, and the event information recorded in the found event files is written into one event file according to the sequence of occurrence of the real events.

According to one embodiment of the invention, event information of real events which have been recorded is rewritten, deleted, and/or

And adding the event information of the simulation event into the recorded event information set.

According to an embodiment of the present invention, each piece of event information includes event occurrence time, event type, and event resource information; the event types comprise an adding container, a deleting container, an updating container, an adding node, a deleting node and an updating node.

According to one embodiment of the present invention, event information of a real event of which the recorded event type is an update container is deleted.

According to one embodiment of the present invention, the node attribute includes a node name, address information, node resource information, and node status information; the container attribute comprises a container name, container resource information and container state information; the event information further includes event resource information, which includes: node name, address information, node resource information and node state information of the node which changes due to occurrence of the event; and/or container name, container specification, and container status information for containers that change as a result of the occurrence of the event.

According to one embodiment of the present invention, the container resource information includes CPU resource information, memory resource information, and disk resource information of the container; the node resource information comprises CPU resource information, memory resource information and disk resource information of the node; the address information is an IP address of the node; the node state information is used for indicating whether the node is ready or not; the container state information comprises container working state information and container scheduling state information; the container working state information is used for indicating the container in any state of initialization, scheduling, creation completion, error fault and deletion; the container scheduling state information is used for indicating whether the container completes scheduling and the node to which the container is scheduled.

The invention also proposes a computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the above-mentioned production method.

The invention also proposes an electronic device comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the above-described fabrication method via execution of the executable instructions.

The invention also provides a device for manufacturing the cloud platform scheduling simulation scene, which further comprises: the snapshot capturing module is used for recording the node attribute of each node and the container attribute of each container in the real cluster at the same time through snapshot capturing; and the event recording module is used for recording event information for describing a real event which causes any one of the nodes and the containers in the real cluster to change after the snapshot is captured.

According to one embodiment of the invention, the making device comprises a timer module, a snapshot capturing module and an event recording module, wherein the timer module is used for sending a trigger signal to the snapshot capturing module and the event recording module at the same time at preset time intervals;

the event recording module newly generates an event file for recording event information of real events after receiving the current trigger signal and before receiving the next trigger signal.

According to an embodiment of the present invention, the system further includes an extracting module, configured to extract an event file including event information of all real events occurring within a preset time period, and a snapshot file whose capture time is not earlier than a start time of the time period and is closest to the start time.

According to an embodiment of the present invention, the system further includes a rewriting module, configured to rewrite, delete, and/or add event information of the simulation event to the recorded event information set.

According to the technical scheme, the manufacturing method has the advantages and positive effects that:

the node attribute, the container attribute and the event information obtained by snapshot capture can be obtained by adopting the manufacturing method in the real cloud parallel operation process. The node attribute and the container attribute can be respectively used as initial parameters of each simulated node and each simulated container in the cloud platform scheduling simulation scene, and the event information can be used as an event to be generated which is simulated in the cloud platform scheduling simulation scene. Therefore, the requirement of a test scheduling algorithm of the scheduling simulation system can be met, and the labor intensity of manual manufacturing of the cloud platform scheduling simulation scene is greatly reduced. Particularly, the situation simulated by the cloud platform scheduling simulation scene can be closer to the actual operation situation of the cloud platform, and the scheduling algorithm is more reasonable to evaluate by adopting the cloud platform scheduling simulation scene.

Drawings

Various objects, features and advantages of the present invention will become more apparent from the following detailed description of preferred embodiments of the invention, when considered in conjunction with the accompanying drawings. The drawings are merely exemplary of the invention and are not necessarily drawn to scale. In the drawings, like reference characters designate the same or similar parts throughout the different views. Wherein:

FIG. 1 is a flow diagram illustrating a method for making a cloud platform dispatch simulation scenario in accordance with an exemplary embodiment;

FIG. 2 is a flow diagram illustrating production of an original scene after a specified time of day in accordance with an exemplary embodiment;

FIG. 3 is a flow diagram illustrating production of an original scene for a specified time period in accordance with an exemplary embodiment;

FIG. 4 is a schematic diagram of an apparatus for manufacturing a cloud platform scheduling simulation scenario, according to an exemplary embodiment;

FIG. 5 is a schematic diagram of an electronic device shown in accordance with an exemplary embodiment;

FIG. 6 is a schematic diagram illustrating a computer-readable storage medium according to an example embodiment.

Detailed Description

Example embodiments will now be described more fully with reference to the accompanying drawings. Example embodiments may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of example embodiments to those skilled in the art.

Referring to fig. 1, fig. 1 is a flowchart of a method for manufacturing a cloud platform scheduling simulation scenario in this embodiment. By adopting the manufacturing method, the working intensity of manufacturing the cloud platform scheduling simulation scene is greatly reduced. The manufacturing method comprises original scene recording. The original scene recording is a process of recording data of a cloud platform which is running in reality to obtain an original scene. The original scene recording comprises the steps of taking snapshots of the cloud platform S101 and recording events of the cloud platform S102.

Taking a snapshot of the cloud platform S101 means recording a node attribute of each node and a container attribute of each container in a real cluster of the cloud platform at a certain time. A web crawler technique may be employed to crawl node attributes and container attributes from a database. The node attributes and the container attributes can be used as initial parameters of each node and each container simulated in the cloud platform scheduling simulation scenario, respectively.

The node attributes are parameters of the node. In this embodiment, the node attribute includes a node name, address information, node resource information, and node status information. The address information may be an IP address of the node. The node resource information comprises CPU resource information, memory resource information and disk resource information of the node. The CPU resource information may be recorded as the number of cores of the CPU, and is used to indicate the amount of resources of the CPU. The memory resource information may be recorded as the number of memories, and is used to indicate the size of the memories. The disk resource information may be recorded as the capacity of the disk, and is used to indicate the resource amount of the disk. The node status information may be recorded as "ready" or "not ready" to indicate whether the node is ready. The node attributes also include a node creation time.

The container attributes are parameters of the container. In this embodiment, the container attributes include a container name, container resource information, and container status information. The container resource information comprises CPU resource information, memory resource information and disk resource information of the container. The CPU resource information may be recorded as the number of cores of the CPU, and is used to indicate the amount of resources of the CPU. The memory resource information may be recorded as the number of memories, and is used to indicate the size of the memories. The disk resource information may be recorded as the capacity of the disk, and is used to indicate the resource amount of the disk. The container status information includes container operational status information and container scheduling status information. The container operating state information is used to indicate what state the container is in initialization, scheduling, creation complete, error failure, and deletion. The container scheduling state information is recorded as the node name of the node to which the container is scheduled or is empty, and is used for indicating whether the container completes scheduling and the node to which the container is scheduled.

The step S102 of recording an event on the cloud platform means that after snapshot capture is performed, event information corresponding to each real event that causes a change in transmission of any one of a node and a container in the real cluster is recorded. The event information is used to describe real events that cause any of the nodes and containers in the real cluster to send changes. The real event may be any one of an add container, a delete container, an update container, an add node, a delete node, and an update node. The event information includes the actual event occurrence time, the event type, and event resource information. The event occurrence time is the time when the event starts to occur. The event types include add container, delete container, update container, add node, delete node, and update node. The event resource information comprises node name, address information, node resource information and node state information of a node before change, which is changed due to the occurrence of the event, and/or container name, container specification and container state information of a container before change, which is changed due to the occurrence of the event.

Preferably, snapshot capture is performed at preset time intervals and a snapshot file is generated. The preset time interval may be any period of time of one hour, half day, one day and one week. The snapshot file is used for recording the information obtained by the current snapshot capture and the capture time of the current snapshot capture. And newly generating an event file after each snapshot capture, and recording the information obtained by the event record after the snapshot capture and before the snapshot capture next time into the newly generated event file.

The original scene is composed of a plurality of snapshot files and event files, each snapshot file corresponds to an event file generated after each snapshot file one to one, each snapshot file and the corresponding event file can form a new original scene, and one snapshot file and a plurality of event files continuously generated after the snapshot file can form a new original scene. Moreover, because the events on the real cloud platform are continuously recorded all the time, after the events are respectively stored in different event files, the recorded event information can be extracted while continuing the current event. In addition, the event information is stored by adopting a plurality of event files, so that the problem that the event files are too large to be read can be avoided.

Preferably, the snapshot files are numbered continuously from small to large according to the sequence of the snapshot file generation, the event files are numbered continuously from small to large according to the sequence of the event file generation, and the initial values of the numbers of the snapshot files and the event files are the same.

After the snapshot file and the event file are numbered, the snapshot file and the event file are more conveniently searched, and the snapshot file and the event file are more easily corresponded. And acquiring a snapshot file and an event file with the same number as the snapshot file, and taking the two files as new original scenes. Or acquiring a snapshot file with the number n, acquiring a plurality of event files with continuous numbers from n +1, and taking the snapshot file and the event files as new original scenes.

Preferably, referring to fig. 2, the original scene after the designated time may be created from the obtained original scene. Comparing the capturing time recorded in the snapshot file with the specified time, finding out the snapshot file with the capturing time not earlier than the specified time and the capturing time closest to the specified time and all event files with the numbers not less than the snapshot file, and writing the event information recorded in the found event files into one event file according to the sequence of the real events. The method comprises the following specific steps:

step S201: assigning i as a number initial value, and entering step S202;

step S202: judging whether the capturing time recorded in the snapshot file with the number i is earlier than a specified time, if so, then entering a step S203, otherwise, entering a step S205;

step S203: increasing the value of i by 1, and entering step S204;

step S204: judging whether the value of i is larger than the maximum value of the number of the snapshot file, if so, entering a step S206, otherwise, entering a step S202;

step S205: judging whether i is equal to the number initial value, if so, turning to the step S206, otherwise, entering the step S207;

step S206: prompting that the scene at the appointed moment cannot be found and stopping;

step S207: and extracting the snapshot file with the number of i-1, extracting the event files with the numbers from i-1 to the maximum number, and arranging the event information in the event files with the numbers from i-1 to the maximum number into one event file according to the occurrence sequence of the real events.

The event file and the snapshot file which are finally obtained according to the method are the original scene after the appointed time.

Preferably, referring to fig. 3, an original scene of a time period between the first time and the second time may also be made according to the obtained original scene. The preset first moment is earlier than the preset second moment. Finding out a first snapshot file with the recorded capturing time not earlier than the first time and closest to the first time, a second snapshot file with the capturing time not earlier than the second time and closest to the second time, and all event files with the serial numbers not less than the first snapshot file and not more than the second snapshot file, and writing the event information recorded in the found event files into one event file according to the sequence of the real events. The method comprises the following specific steps:

step S301: assigning i as a number initial value, and entering step S302;

step S302: judging whether the capturing time recorded in the snapshot file with the number i is earlier than a first moment, if so, then entering a step S303, and if not, entering a step S305;

step S303: increasing the value of i by 1, and proceeding to step S304;

step S304: judging whether the value of i is larger than the maximum value of the number of the snapshot file, if so, entering a step S305, otherwise, entering a step S302;

step S305: judging whether i is equal to the number initial value, if so, turning to the step S306, otherwise, entering the step S307;

step S306: prompting that the scene in the specified time period cannot be found and stopping;

step S307: assigning the value I as the maximum value of the serial number, and entering the step S308;

step S308: judging whether the capturing time recorded in the snapshot file with the number I is later than a second moment, if so, entering a step S309, otherwise, entering a step S311;

step S309: the value of I is decreased by 1, and the process proceeds to step S310;

step S310: judging whether the value of i is smaller than the initial value of the number of the snapshot file, if so, entering step S306, otherwise, entering step S308;

step S311: judging whether i is equal to the maximum number, if so, turning to the step S306, otherwise, entering the step S312;

step S312: and extracting the snapshot file with the number of I-1, and arranging the event information in the event files with the numbers of I-1 to I +1 into one event file according to the occurrence sequence of the real events.

In step S312, the snapshot file numbered I-1 is the first snapshot file, and the snapshot file numbered I +1 is the second snapshot file.

The event file and the snapshot file which are finally obtained according to the method are the original scenes of the time period from the first time to the second time.

Preferably, an original scene is specified, and the event file in the original scene is modified to obtain a simulated scene.

And rewriting and/or deleting the event information of the recorded real event. And modifying the event information of the real events in the event file to obtain simulated events needing to be simulated, and deleting the unnecessary event information to eliminate unnecessary simulated events.

And adding event information of the simulation event into the recorded event information set. And inserting event information of the simulation event to be simulated into the event file.

The original scene is modified on the basis of the original scene, the original scene is modified into the required simulation scene, and the workload is low. The simulation scene can be directionally created to be simulated.

Preferably, the converted scene may also be made from the obtained original scene. The conversion scenario is typically used to playback the real situation over a certain time period on the line, so the container after the specified point in time in the conversion scenario will be assumed to be unscheduled.

And deleting the event information of the real event of which the type is the updating container in the event file of the original scene, and forming a conversion scene by the deleted event file and the corresponding snapshot file.

Preferably, the transition scene after the preset time can also be made according to the original scene. The method comprises the following steps:

traversing all event information in the event file according to the sequence of event occurrence and writing the event information into a new event file, wherein the event information of real events which occur later than the preset time and have event types as update containers is not written in the process.

And taking the new event file and the snapshot file of the original scene as the conversion scene.

Referring to fig. 4, in the embodiment of the present example, a device 401 for making a cloud platform scheduling simulation scenario is further provided, and the device includes a snapshot capture module 411, an event recording module 412, a timer module 413, an extraction module 414, and a rewriting module 415.

The snapshot capture module 411 and the event recording module 412 are both connected to the real cluster of the cloud platform 402.

The snapshot capture module 411 is configured to record, through snapshot capture, a node attribute of each node and a container attribute of each container in the real cluster at the same time.

The event recording module 412 is configured to record event information describing a real event that causes a change in any one of a node and a container in the real cluster after the snapshot is captured.

The timer module 413 is connected to the snapshot capture module 411 and the event recording module 412, respectively. The timer module 413 sends a trigger signal to the snapshot capture module 411 and the event recording module 412 at preset time intervals.

The snapshot capture module 411 performs a snapshot capture and newly generates a snapshot file for recording information obtained by the current snapshot capture and capture time of the current snapshot capture when receiving the trigger signal.

The event recording module 412 newly generates an event file for recording event information of real events after receiving the current trigger signal and before receiving the next trigger signal when receiving the trigger signal.

The extracting module 414 is respectively connected to the snapshot capturing module 411 and the event recording module 412. The extracting module 414 is configured to extract an event file including event information of all real events occurring within a preset time period and a snapshot file whose capturing time is not earlier than the start time of the time period and is closest to the start time.

The rewrite module 415 is connected to the snapshot capture module 411 and the event record module 412 respectively. The rewriting module 415 is configured to rewrite, delete, and/or add event information of a simulation event to the recorded event information set.

In an exemplary embodiment of the present invention, an electronic device capable of implementing the method for manufacturing a cloud platform scheduling simulation scenario is further provided.

As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or program product. Thus, various aspects of the invention may be embodied in the form of: an entirely hardware embodiment, an entirely software embodiment (including firmware, microcode, etc.) or an embodiment combining hardware and software aspects that may all generally be referred to herein as a "circuit," module "or" system.

An electronic device 800 according to this embodiment of the invention is described below with reference to fig. 5. The electronic device 800 shown in fig. 5 is only an example and should not bring any limitations to the functionality and scope of use of the embodiments of the present invention.

As shown in fig. 5, the electronic device 800 is in the form of a general purpose computing device. The components of the electronic device 800 may include, but are not limited to: the at least one processing unit 810, the at least one memory unit 820, and a bus 830 that couples the various system components including the memory unit 820 and the processing unit 810.

Wherein the storage unit stores program code that is executable by the processing unit 810 to cause the processing unit 810 to perform steps according to various exemplary embodiments of the present invention as described in the above section "exemplary methods" of the present specification.

The storage unit 820 may include readable media in the form of volatile memory units such as a random access memory unit (RAM)8201 and/or a cache memory unit 8202, and may further include a read only memory unit (ROM) 8203.

The storage unit 820 may also include a program/utility 8204 having a set (at least one) of program modules 8205, such program modules 8205 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.

Bus 830 may be any of several types of bus structures including a memory unit bus or memory unit controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

The electronic device 800 may also communicate with one or more external devices 700 (e.g., keyboard, pointing device, bluetooth device, etc.), with one or more devices that enable a user to interact with the electronic device 600, and/or with any devices (e.g., router, modem, etc.) that enable the electronic device 800 to communicate with one or more other computing devices. Such communication may occur via an input/output (I/O) interface 650. Also, the electronic device 800 may communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the internet) via the network adapter 860. As shown, the network adapter 860 communicates with the other modules of the electronic device 800 via the bus 830. It should be appreciated that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the electronic device 600, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, among others.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

In an exemplary embodiment of the present disclosure, there is also provided a computer-readable storage medium having stored thereon a program product capable of implementing the above-described method of the present specification. In some possible embodiments, aspects of the invention may also be implemented in the form of a program product comprising program code means for causing a terminal device to carry out the steps according to various exemplary embodiments of the invention described in the above section "exemplary methods" of the present description, when said program product is run on the terminal device.

Referring to fig. 6, a program product 900 for implementing the above-described manufacturing method of the cloud platform scheduling simulation scenario according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program codes, and may be run on a terminal device, such as a personal computer. However, the program product of the present invention is not limited in this regard and, in the present document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

A computer readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

It should be noted that although in the above detailed description several modules or units of the device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functionality of two or more modules or units described above may be embodied in one module or unit, according to embodiments of the present disclosure. Conversely, the features and functions of one module or unit described above may be further divided into embodiments by a plurality of modules or units.

Moreover, although the steps of the methods of the present disclosure are depicted in the drawings in a particular order, this does not require or imply that the steps must be performed in this particular order, or that all of the depicted steps must be performed, to achieve desirable results. Additionally or alternatively, certain steps may be omitted, multiple steps combined into one step execution, and/or one step broken down into multiple step executions, etc.

Through the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein may be implemented by software, or by software in combination with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored in a non-volatile storage medium (which may be a CD-ROM, a usb disk, a removable hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which may be a personal computer, a server, a mobile terminal, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

Claims

1. A manufacturing method of a cloud platform scheduling simulation scene is characterized by comprising the following steps:

recording the node attribute of each node and the container attribute of each container in the real cluster at the same time through snapshot capture, and storing the node attribute and the container attribute;

and recording event information for describing a real event which causes any one of the nodes and the containers in the real cluster to change after the snapshot is captured through an event record, and storing the event information.

2. The production method according to claim 1, wherein snapshot capture is performed at preset time intervals and a snapshot file for recording information obtained by the current snapshot capture and capture time of the current snapshot capture is newly generated;

3. The production method according to claim 2, wherein the snapshot files are numbered consecutively from small to large in the order in which the snapshot files are generated, the event files are numbered consecutively from small to large in the order in which the event files are generated, and the starting values of the numbers of the snapshot files and the event files are the same.

4. The production method according to claim 3, wherein the size of the capture time recorded in the snapshot file is compared with the size of the specified time, the snapshot file whose capture time is not earlier than the specified time and whose capture time is closest to the specified time and all event files whose number is not less than that of the snapshot file are searched, and the event information recorded in the searched event files is written into one event file in the order in which the real events occur.

5. The production method according to claim 3, wherein the preset first time is earlier than a preset second time, a first snapshot file whose capturing time is not earlier than the first time and is closest to the first time, a second snapshot file whose capturing time is not earlier than the second time and is closest to the second time, and all event files whose numbers are not less than the first snapshot file and not more than the second snapshot file are searched, and the event information recorded in the searched event files is written into one event file in the order of occurrence of real events.

6. The production method according to claims 1 to 5, further comprising overwriting, deleting, and/or overwriting event information of the recorded real event

7. The production method according to any one of claims 1 to 5, wherein each piece of event information includes event occurrence time, event type, and event resource information;

the event types comprise an adding container, a deleting container, an updating container, an adding node, a deleting node and an updating node.

8. The production method according to claim 7, wherein the event information of the real event of which the recorded event type is the update container is deleted.

9. The method of manufacturing of claim 7, further comprising the node attributes including node name, address information, node resource information, and node status information;

the container attribute comprises a container name, container resource information and container state information;

the event information further includes event resource information, which includes:

node name, address information, node resource information and node state information of the node which changes due to occurrence of the event; and/or

A container name, a container specification, and container status information of the container that are changed due to the occurrence of the event.

10. The manufacturing method according to claim 9, wherein the container resource information includes CPU resource information, memory resource information, and disk resource information of the container;

the node resource information comprises CPU resource information, memory resource information and disk resource information of the node;

the address information is an IP address of the node;

the node state information is used for indicating whether the node is ready or not;

the container state information comprises container working state information and container scheduling state information;

the container working state information is used for indicating the container in any state of initialization, scheduling, creation completion, error fault and deletion;

the container scheduling state information is used for indicating whether the container completes scheduling and the node to which the container is scheduled.

11. The device for manufacturing the cloud platform scheduling simulation scene is characterized by comprising the following steps of:

the snapshot capturing module is used for recording the node attribute of each node and the container attribute of each container in the real cluster at the same time through snapshot capturing;

and the event recording module is used for recording event information for describing a real event which causes any one of the nodes and the containers in the real cluster to change after the snapshot is captured.

12. A computer-readable storage medium, on which a computer program is stored, the computer program, when being executed by a processor, implementing the production method according to any one of claims 1 to 10.

13. An electronic device, comprising:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform the method of any of claims 1-10 via execution of the executable instructions.