Program deployment management method and device, equipment and storage medium
By processing the deployment specifications sent by the client to estimate resource consumption and determine the target deployment metric, the problem of not being able to understand application resource consumption in advance is solved, and the precise estimate of resource consumption and the improvement of deployment efficiency is achieved.
Patent Information
- Application Number
- CN202411871403.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-12-18
- Publication Date
- 2025-04-11
AI Technical Summary
When managing applications using orchestration deployment platforms, it is not possible to understand the precise resource consumption of applications in a specific environment in advance, resulting in wasted computing resources.
By getting the deployment specifications sent by the client, processing these specifications to estimate resource consumption, and determining target deployment metrics based on the estimated results, so that the application can be understood before its deployment.
It realizes that the application is fully informed of its resource consumption before it is deployed to the environment, avoids waste of computing resources, and improves deployment efficiency.
Smart Images

Figure CN119806548A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of distributed technology, and in particular to a program deployment management method, apparatus, device and storage medium. Background Art
[0002] In a distributed computing environment, orchestration deployment platforms and other automation platforms can help manage applications to reduce the burden on the business. The platform can receive deployment parameters, which are used to define the target deployment state of the application deployed to the environment. However, different applications consume different resources in different environments.
[0003] Currently, in the process of using an orchestration and deployment platform to manage applications, users do not need to manage and control cloud infrastructure, but need to control the upper-level application deployment and application hosting environment; however, before the application is deployed to the corresponding environment, it is impossible to understand the precise resource consumption of the application in the corresponding environment. The resource consumption in the corresponding environment can only be obtained after the application is deployed to the corresponding environment. Summary of the invention
[0004] In order to facilitate understanding of the precise resource consumption of an application in a corresponding environment before deploying the application to the corresponding environment, the present application provides a program deployment management method, apparatus, device and storage medium.
[0005] In a first aspect, the present application provides a program deployment management method, comprising:
[0006] Get the deployment specification sent by the client;
[0007] Processing the deployment specification to obtain a resource consumption estimate;
[0008] A target deployment metric is determined based on the resource consumption estimate.
[0009] Through the above implementation, the precise resource consumption of the application in the corresponding environment can be known in advance before the application is deployed in the corresponding environment.
[0010] Preferably, processing the deployment specification to obtain a resource consumption estimate includes:
[0011] The deployment specification is processed based on a preset mapping table to obtain a resource consumption estimate.
[0012] Through the above implementation, the resource consumption estimate corresponding to the deployment specification can be determined from the mapping table, thereby facilitating the estimation of the resource consumption corresponding to the deployment specification.
[0013] Preferably, the mapping table is used to map the historical resource consumption information of the deployment parameters in the deployment specification in different deployment environments.
[0014] Through the above implementation, by setting the mapping table, it is convenient to determine the historical resource consumption information of the deployment parameters in different deployment environments.
[0015] Preferably, the processing of the deployment specification based on a preset mapping table to obtain a resource consumption estimate includes:
[0016] The preset mapping table is traversed to obtain the resource consumption estimate corresponding to the deployment specification.
[0017] Through the above implementation, the resource consumption estimate is determined by traversing the mapping table, thereby facilitating the estimation of resource consumption based on the mapping table.
[0018] Preferably, the historical resource consumption information includes at least one of a memory consumption history value, a CPU consumption history value, and a disk consumption history value.
[0019] Through the above implementation, the specific content of historical resource consumption information is made public, thereby facilitating understanding of the estimated content of resource consumption.
[0020] Preferably, determining the target deployment metric based on the resource consumption estimate includes:
[0021] The initial deployment metric is adjusted to a target deployment metric based on the resource consumption estimate.
[0022] Through the above implementation, the initial deployment metric is adjusted according to the calculated resource consumption estimate, so that the initial deployment metric is adjusted to the target deployment metric corresponding to the resource consumption estimate.
[0023] In a second aspect, the present application provides a program deployment management device, comprising:
[0024] A specification acquisition module is used to obtain the deployment specifications sent by the client;
[0025] An estimation calculation module, used for processing the deployment specification to obtain a resource consumption estimation;
[0026] A metric determination module is used to determine a target deployment metric based on the resource consumption estimate.
[0027] Through the above implementation, the precise resource consumption of the application in the corresponding environment can be known in advance before the application is deployed in the corresponding environment.
[0028] In a third aspect, the present application provides a computer device, the computer device comprising a memory and a processor, the memory storing a computer program, and the processor implementing the steps in the above method when executing the computer program.
[0029] In a fourth aspect, the present application provides a computer-readable storage medium having a computer program stored thereon, which implements the steps in the above method when executed by a processor.
[0030] In a fifth aspect, the present application further provides a computer program product, wherein the computer program product comprises a computer program, and when the computer program is executed by a processor, the steps in any of the above method embodiments are implemented.
[0031] The above program deployment management method, apparatus, device and storage medium obtain the deployment specification sent by the client; process the deployment specification to obtain a resource consumption estimate; and determine the target deployment metric based on the resource consumption estimate. Through the above implementation, the precise resource consumption of the application in the corresponding environment can be understood in advance before the application is deployed in the corresponding environment.
[0032] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0033] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for use in the embodiments are briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present invention and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without creative work.
[0034] Figure 1 A flowchart of a program deployment management method provided in an embodiment of the present application;
[0035] Figure 2 A schematic diagram of the structure of a program deployment management device provided in an embodiment of the present application;
[0036] Figure 3 A schematic diagram of the structure of a computer device provided in an embodiment of the present application;
[0037] Figure 4 This is a diagram of the internal structure of a computer-readable storage medium provided in an embodiment of the present application. DETAILED DESCRIPTION
[0038] In order to make the purpose, technical solution and advantages of the present disclosure more clear, the present disclosure is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present disclosure and are not used to limit the present disclosure.
[0039] It should be noted that the terms "first", "second", etc. in the specification and claims of this article and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of this article described here can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, device, product or equipment that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or equipment.
[0040] In this article, the term "and / or" is only a description of the association relationship between related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the related objects before and after are in an "or" relationship.
[0041] Embodiment 1
[0042] Figure 1 A flowchart of a program deployment management method provided in Example 1 of this application, refer to Figure 1 The method may be performed by a device for performing the method, and the device may be implemented by software and / or hardware. The method includes:
[0043] S110. Obtain the deployment specification sent by the client.
[0044] Among them, before deploying the program to the corresponding environment, in order to facilitate the advance estimation of the resource consumption of the program in the environment to be deployed, so as to configure the corresponding computing resources in advance in a targeted manner, thereby avoiding the waste of computing resources; the deployment specification corresponding to the program can be sent to the server through the client first, wherein the deployment specification is used to characterize the deployment type and resource consumption of the program; exemplarily, the deployment type is "web service deployment", and the resource consumption is "deploying 3 copies consumes 15MB of memory space and 300MB of disk space"; the server obtains the deployment specification sent by the client.
[0045] Specifically, the server obtains the deployment specification sent by the client.
[0046] S120: Process the deployment specification to obtain a resource consumption estimate.
[0047] Among them, the deployment specification can further determine the resource consumption estimate corresponding to the deployment specification based on the deployment specification sent by the client; the resource consumption estimate is the estimated value of the resource consumption required by the program corresponding to the deployment specification in the environment estimated by the server. For example, the resource consumption estimate corresponding to "300MB of disk space" estimated by the server is "estimated to consume 10GB of disk space."
[0048] Specifically, the server estimates the resource consumption estimate corresponding to the deployment specification based on the deployment specification sent by the client.
[0049] S130: Determine a target deployment metric based on the resource consumption estimate.
[0050] Among them, the server can further determine the corresponding target deployment metric based on the resource consumption estimate. For example, when the resource consumption estimate is "estimated to consume 10GB of disk space", the target deployment metric determined by the server based on the resource consumption estimate is "consume 11GB of disk space".
[0051] Specifically, the server further generates a corresponding target deployment metric based on the resource consumption estimate, and then returns the generated resource consumption estimate and the target deployment metric to the client.
[0052] It should be noted that, in this embodiment, the deployment specification sent by the client is obtained; the deployment specification is processed to obtain a resource consumption estimate; and the target deployment metric is determined based on the resource consumption estimate. Through the above implementation, the precise resource consumption of the application in the corresponding environment can be known in advance before the application is deployed in the corresponding environment.
[0053] Embodiment 2
[0054] A program deployment management method is provided in Embodiment 2 of the present application. The method refines the “processing the deployment specification to obtain a resource consumption estimate” in Embodiment 1. It should be noted that for the parts not described in detail in this embodiment, reference may be made to the descriptions of other embodiments. The method includes:
[0055] S210: Obtain the deployment specification sent by the client.
[0056] S220: Process the deployment specification based on a preset mapping table to obtain a resource consumption estimate.
[0057] The mapping table is a data table preset in the server according to historical data, and is used to map out resource consumption estimates corresponding to the deployment specifications sent by the client.
[0058] Specifically, after receiving the deployment specification sent by the client, the server further searches for the resource consumption estimate corresponding to the deployment specification through a preset mapping table.
[0059] S230: Determine a target deployment metric based on the resource consumption estimate.
[0060] Embodiment 3
[0061] A program deployment management method is provided in Embodiment 3 of the present application. The method refines the "mapping table" in Embodiment 2. It should be noted that for the parts not described in detail in this embodiment, reference may be made to the descriptions of other embodiments. The method includes:
[0062] S310: Obtain the deployment specification sent by the client.
[0063] S320: Process the deployment specification based on a preset mapping table to obtain a resource consumption estimate.
[0064] It should be noted that the mapping table is used to map the historical resource consumption information of the deployment parameters in the deployment specification in different deployment environments.
[0065] Among them, the mapping table is used to map the deployment specifications with the corresponding historical resource consumption information, and the historical resource consumption information is the resource consumption of deploying the program corresponding to the deployment specification to different types of deployment environments in history; different types of deployment environments are multiple different computing environments, such as different sub-deployment environments; after receiving the deployment specifications sent by the client, the server can query the historical resource consumption information of the deployment specifications in different deployment environments from the above mapping table through the corresponding query statement.
[0066] Specifically, after receiving the deployment specification sent by the client, the server searches the mapping table for historical resource consumption information corresponding to the deployment specification in different deployment environments.
[0067] S330: Determine a target deployment metric based on the resource consumption estimate.
[0068] Embodiment 4
[0069] A program deployment management method provided in a fourth embodiment of the present application refines the "processing the deployment specification based on a preset mapping table to obtain a resource consumption estimate" in the third embodiment; it should be noted that for the parts not described in detail in this embodiment, reference may be made to the descriptions of other embodiments, and the method includes:
[0070] S410: Obtain the deployment specification sent by the client.
[0071] S420: traverse a preset mapping table to obtain a resource consumption estimate corresponding to the deployment specification.
[0072] The mapping table is used to map the historical resource consumption information of the deployment parameters in the deployment specification in different deployment environments.
[0073] In this embodiment, the server can specifically determine the resource consumption estimate corresponding to the deployment specification from the mapping table by traversing the mapping table. The resource consumption estimate is also the historical resource consumption information of the deployment parameters in the deployment environment.
[0074] Specifically, the server determines the resource consumption estimate corresponding to the deployment specification from the mapping table by traversing the mapping table.
[0075] S430: Determine a target deployment metric based on the resource consumption estimate.
[0076] Embodiment 5
[0077] A program deployment management method provided in Embodiment 5 of the present application refines the “historical resource consumption information” in Embodiment 3; it should be noted that for the parts not described in detail in this embodiment, reference may be made to the descriptions of other embodiments, and the method includes:
[0078] S510: Obtain the deployment specification sent by the client.
[0079] S520: Process the deployment specification based on a preset mapping table to obtain a resource consumption estimate.
[0080] The mapping table is used to map the historical resource consumption information of the deployment parameters in the deployment specification in different deployment environments.
[0081] It should be noted that the historical resource consumption information includes at least one of a memory consumption historical value, a CPU consumption historical value, and a disk consumption historical value.
[0082] The memory consumption historical value is the memory consumption value corresponding to the deployment parameter in the historical data, the CPU consumption historical value is the CPU consumption value corresponding to the deployment parameter in the historical data, and the disk consumption historical value is the disk consumption value corresponding to the deployment parameter in the historical data.
[0083] S530: Determine a target deployment metric based on the resource consumption estimate.
[0084] Embodiment 6
[0085] A program deployment management method is provided in Embodiment 6 of the present application. The method refines the “determining a target deployment metric based on the resource consumption estimate” in Embodiment 1. It should be noted that for the parts not described in detail in this embodiment, reference may be made to the descriptions of other embodiments. The method includes:
[0086] S610: Obtain the deployment specification sent by the client.
[0087] S620: Process the deployment specification to obtain a resource consumption estimate.
[0088] S630: Adjust the initial deployment metric to the target deployment metric based on the resource consumption estimate.
[0089] Among them, the initial deployment metric is the deployment metric before the client sends the corresponding deployment specification to the server; illustratively, before the client sends the deployment specification with the deployment type of "web service deployment" and the resource consumption of "deploying 3 copies consuming 15MB of memory space and 300MB of disk space", the initial deployment metric stored by the server at this time is "consuming 1GB of disk space". It is subsequently assumed that the resource consumption estimate determined is "estimated to consume 10GB of disk space", then the target deployment metric is "consuming 11GB of disk space".
[0090] Specifically, the client calculates the sum of the initial deployment metric and the resource consumption estimate to determine the target deployment metric, and then adjusts the deployment metric from the initial deployment metric to the target deployment metric.
[0091] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.
[0092] Embodiment 7
[0093] Based on the same inventive concept, this embodiment also provides a program deployment management device for implementing the program deployment management method involved above. The implementation solution provided by the device to solve the problem is similar to the implementation solution recorded in the above method, so the specific limitations in one or more program deployment management device embodiments provided below can refer to the limitations of the program deployment management method above, and will not be repeated here.
[0094] In this embodiment, Figure 2 As shown, a program deployment management device is provided, comprising:
[0095] A specification acquisition module is used to obtain the deployment specifications sent by the client;
[0096] An estimation calculation module, used for processing the deployment specification to obtain a resource consumption estimation;
[0097] A metric determination module is used to determine a target deployment metric based on the resource consumption estimate.
[0098] Each module in the above program deployment management device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.
[0099] It should be noted that, in this embodiment, the deployment specification sent by the client is obtained; the deployment specification is processed to obtain a resource consumption estimate; and the target deployment metric is determined based on the resource consumption estimate. Through the above implementation, the precise resource consumption of the application in the corresponding environment can be known in advance before the application is deployed in the corresponding environment.
[0100] In one embodiment, in processing the deployment specification to obtain a resource consumption estimate, the estimate calculation module is specifically used to:
[0101] The deployment specification is processed based on a preset mapping table to obtain a resource consumption estimate.
[0102] In one embodiment, in processing the deployment specification based on a preset mapping table to obtain a resource consumption estimate, the estimate calculation module is specifically used to:
[0103] The preset mapping table is traversed to obtain the resource consumption estimate corresponding to the deployment specification.
[0104] In one embodiment, in determining the target deployment metric based on the resource consumption estimate, the metric determination module is specifically configured to:
[0105] The initial deployment metric is adjusted to a target deployment metric based on the resource consumption estimate.
[0106] Embodiment 8
[0107] Figure 3A schematic diagram of the structure of a computer device 10 in an embodiment that can be used to implement the present application is shown. The device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.
[0108] like Figure 3 As shown, the device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the device 10 can also be stored. The processor 11, ROM 12 and RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.
[0109] A number of components in the device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0110] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a load balancing method for a multi-camera system.
[0111] In some embodiments, the load balancing method for a multi-camera system may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the load balancing method for a multi-camera system described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to perform the load balancing method for a multi-camera system in any other appropriate manner (e.g., by means of firmware).
[0112] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0113] The computer programs for implementing the methods of the present application may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer programs are executed by the processor, the functions / operations specified in the flow charts and / or block diagrams are implemented. The computer programs may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.
[0114] In the context of the present application, a computer readable storage medium may be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, device or equipment. A computer readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer readable storage medium may be a machine readable signal medium. A more specific example of a machine readable storage medium may include an electrical connection based on one or more lines, 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 of the foregoing.
[0115] To provide interaction with a user, the systems and techniques described herein can be implemented on a device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the device. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).
[0116] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.
[0117] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.
[0118] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this application can be executed in parallel, sequentially or in different orders, as long as the expected results of the technical solution of this application can be achieved, and this document is not limited here.
[0119] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.
[0120] Embodiment 9
[0121] In this embodiment, a computer readable storage medium is provided. Figure 4 As shown, a computer program is stored thereon, and when the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.
[0122] Embodiment 10
[0123] In this embodiment, a computer program product is provided, including a computer program. When the computer program is executed by a processor, the steps in the above method embodiments are implemented.
[0124] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this disclosure are all information and data authorized by the user or fully authorized by all parties.
[0125] Those skilled in the art can understand that all or part of the processes in the above-mentioned embodiment methods can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided by the present disclosure can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetoresistive random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided by the present disclosure may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited thereto. The processor involved in each embodiment provided by the present disclosure may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, etc., but are not limited thereto.
[0126] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0127] The above-described embodiments only express several implementation methods of the present disclosure, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present invention. It should be pointed out that, for a person of ordinary skill in the art, several modifications and improvements can be made without departing from the concept of the present disclosure, and these all belong to the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure shall be subject to the attached claims.
Claims
1. A program deployment management method, characterized in that: include: Get the deployment specification sent by the client; Processing the deployment specification to obtain a resource consumption estimate; A target deployment metric is determined based on the resource consumption estimate.
2. The method according to claim 1, characterized in that The processing of the deployment specification to obtain a resource consumption estimate includes: The deployment specification is processed based on a preset mapping table to obtain a resource consumption estimate.
3. The method according to claim 2, characterized in that The mapping table is used to map the historical resource consumption information of the deployment parameters in the deployment specification in different deployment environments.
4. The method according to claim 3, characterized in that The step of processing the deployment specification based on a preset mapping table to obtain a resource consumption estimate includes: The preset mapping table is traversed to obtain the resource consumption estimate corresponding to the deployment specification.
5. The method according to claim 3, characterized in that: The historical resource consumption information includes at least one of a memory consumption history value, a CPU consumption history value, and a disk consumption history value.
6. The method according to claim 1, characterized in that The determining of a target deployment metric based on the resource consumption estimate includes: The initial deployment metric is adjusted to a target deployment metric based on the resource consumption estimate.
7. A program deployment management device, characterized in that: The device comprises: A specification acquisition module is used to obtain the deployment specifications sent by the client; An estimation calculation module, used for processing the deployment specification to obtain a resource consumption estimation; A metric determination module is used to determine a target deployment metric based on the resource consumption estimate.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
Citation Information
Patent Citations
Application program deployment method and device, computer equipment and storage medium
CN117331569A
Managing deployments of software programs to distributed computing environments
US20220391185A1