Application change method and device for private cloud platform, equipment and medium

Abstract

The embodiment of the invention discloses an application change method and device for a private cloud platform, equipment and a medium, and aims at a target application program deployed on the private cloud platform based on historical resource use information and non-functional configuration information of the target application program and non-functional specification information of the private cloud platform. Determining target annotation content corresponding to the target application program; and when the functional change request corresponding to the target application program is detected, performing change processing on the target application program based on the target annotation content and the functional change request to obtain an updated changed application program, so that non-functional configuration maintenance of large-scale application programs can be realized more lightly, conveniently and safely, and the maintenance efficiency is improved. And the resource utilization rate and the configuration normalization of the cloud native cluster are improved.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to an application change method, device, equipment and medium for a private cloud platform. Background Art

[0002] Data center cloudification is the only way for the current digital transformation of the financial industry. As one of the current mainstream architectures, cloud native also needs to ensure the stability of financial applications on the basis of following cloud native specifications and responding to the call for green energy conservation. The extreme elasticity and fault self-healing capabilities of cloud native constitute the new technology foundation of the basic environment for the rapid digital transformation of enterprises. The widespread application of cloud native has gradually expanded the scale of cloud native clusters, and the importance of improving resource utilization and daily operation and maintenance convenience of large-scale cloud native clusters has become increasingly prominent. Generally speaking, due to the high confidentiality requirements of the financial industry, financial applications need to be deployed in private cloud platforms. For private cloud platforms, when the non-functional specification information of the private cloud platform changes, the non-functional configuration information of each application deployed in the private cloud platform also needs to be changed accordingly.

[0003] Currently, if you want to make non-functional configuration changes to an application deployed on a private cloud platform, the administrator must first notify the person in charge of the application, who will then edit the non-functional configuration change file and make non-functional configuration changes to the application through the non-functional configuration change file. The container corresponding to the application must then be restarted, and the changes will take effect.

[0004] However, the above method relies on manual notification information, which has the problem of cumbersome non-functional change process of application, uncertainty about whether the application will be adjusted and the specific adjustment amount, unreasonable resource allocation and poor configuration standardization, which leads to low resource utilization of cloud native clusters. On the other hand, restarting the container will affect business continuity. Summary of the invention

[0005] The present invention provides an application change method, device, equipment and medium for a private cloud platform, so as to realize non-functional configuration maintenance of large-scale application programs in a lighter, more convenient and safer way, and improve the resource utilization and configuration standardization of cloud native clusters.

[0006] In a first aspect, an embodiment of the present invention provides an application change method for a private cloud platform, the method comprising:

[0007] For a target application deployed on a private cloud platform, based on historical resource usage information of the target application, non-functional configuration information, and non-functional specification information of the private cloud platform, determine target annotation content corresponding to the target application;

[0008] When a functional change request corresponding to the target application is detected, the target application is changed based on the target annotation content and the functional change request to obtain an updated changed application.

[0009] In a second aspect, an embodiment of the present invention further provides an application change device for a private cloud platform, the device comprising:

[0010] An annotation content determination module is used to determine, for a target application deployed on a private cloud platform, a target annotation content corresponding to the target application based on historical resource usage information, non-functional configuration information, and non-functional specification information of the private cloud platform of the target application;

[0011] The application change module is used to, when a functional change request corresponding to the target application is detected, perform change processing on the target application based on the target annotation content and the functional change request to obtain an updated changed application.

[0012] In a third aspect, an embodiment of the present invention further provides an electronic device, the electronic device comprising:

[0013] one or more processors;

[0014] a storage device for storing one or more programs,

[0015] When one or more programs are executed by one or more processors, the one or more processors implement an application change method for a private cloud platform as described in any of the embodiments of the present invention.

[0016] In a fourth aspect, an embodiment of the present invention further provides a storage medium comprising computer executable instructions, which, when executed by a computer processor, are used to execute an application change method for a private cloud platform such as any one of the embodiments of the present invention.

[0017] The technical solution of the embodiment of the present invention, for the target application deployed on the private cloud platform, first determines the target annotation content corresponding to the target application based on the historical resource usage information, non-functional configuration information of the target application, and non-functional specification information of the private cloud platform, so that when a functional change request corresponding to the target application is detected, the target application is changed based on the target annotation content and the functional change request to obtain an updated changed application. The technical solution of this embodiment determines the target annotation content based on the historical resource usage information and non-functional configuration information of the target application and the non-functional specification information of the private cloud platform, so that when the target application needs to be functionally changed, the target application is automatically non-functionally changed according to the target annotation content, which can achieve non-functional configuration maintenance of large-scale applications in a lighter, more convenient and safer way, and improve the resource utilization and configuration standardization of cloud native clusters. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, the following briefly introduces the drawings required to describe the embodiments. Obviously, the drawings introduced are only drawings of a part of the embodiments to be described in the present invention, rather than all the drawings. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0019] Figure 1 A flowchart of a method for changing an application of a private cloud platform provided by an embodiment of the present invention;

[0020] Figure 2 A flowchart of a method for changing an application of a private cloud platform provided by an embodiment of the present invention;

[0021] Figure 3 A schematic diagram of the structure of an application change device for a private cloud platform provided by an embodiment of the present invention;

[0022] Figure 4 The present invention is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0023] The present invention will be further described in detail below in conjunction with the accompanying drawings and embodiments. It is to be understood that the specific embodiments described herein are only used to explain the present invention, rather than to limit the present invention. It should also be noted that, for ease of description, only parts related to the present invention, rather than all structures, are shown in the accompanying drawings.

[0024] Before introducing the embodiments of the present invention, the application scenarios of the embodiments of the present invention may be described first. This embodiment may be applicable to scenarios where changes are processed for applications deployed in private cloud platforms. Specifically, the widespread application of cloud native has led to the gradual expansion of the scale of cloud native clusters, and the importance of improving resource utilization and daily operation and maintenance convenience of large-scale cloud native clusters has become increasingly prominent. However, the model in which public cloud applications modify configurations at any time and constrain resource waste through metering and billing is not suitable for private cloud scenarios. The technical solution provided by the embodiments of the present invention aims to achieve non-functional configuration maintenance of large-scale private cloud native applications in a more lightweight, convenient and secure manner, and to improve resource utilization and configuration standardization of cloud native clusters.

[0025] Embodiment 1

[0026] Figure 1 A flow chart of an application change method for a private cloud platform provided in an embodiment of the present invention. This embodiment can be applied to scenarios in which changes are performed on application programs deployed in a private cloud platform. The method can be executed by an application change device for the private cloud platform. The device can be implemented in the form of software and / or hardware. The hardware can be an electronic device, such as a mobile terminal, a PC, or a server.

[0027] Before introducing this solution, the important concepts involved in the embodiment of the present invention can be explained first. In this embodiment, the private cloud platform is relative to the public cloud platform. There are significant differences between public cloud and private cloud in terms of ownership, accessibility, security, cost and customizability. Public cloud is provided by a third party and can be accessed by anyone. It is suitable for start-ups and individual users, with great price advantages, but relatively low security. Private cloud is owned and managed by the organization itself, and is limited to internal personnel. It is suitable for large enterprises and government agencies, with higher security, but higher cost. In terms of business scenarios and technical architecture, public cloud is usually oriented to external users, such as portals and video websites, while private cloud mainly serves the internal part of the enterprise, focusing on high availability and flexibility. Public cloud requires users to adjust their business according to the requirements of the provider to adapt to its services, while private cloud can be better compatible with the enterprise's own business. From the perspective of data security and operation and maintenance, private cloud provides higher data security and service quality, which is suitable for enterprises with high requirements for data security. Public cloud achieves security isolation through the host layer, and users do not need to operate and maintain it by themselves, and the cost is relatively low.

[0028] A private cloud platform is a cloud computing service model that is built for a single organization or customer. It provides the most effective control over data, security, and service quality, ensuring that the organization owns and controls the infrastructure and can deploy its own network and application services. A public cloud platform refers to cloud computing services provided by a third-party provider. Users can access and use these services through the Internet without owning or managing the underlying physical infrastructure. The core attribute of a public cloud platform is shared resource services. Users can access and use these resources anytime and anywhere through the Internet, usually paying on demand. In a public cloud platform, resource waste is generally restricted by metering and billing applications on it, and non-functional configurations need to be configured. Public clouds generally do not impose too many restrictions on applications on them; however, for specific applications, such as those in the financial field, they have the characteristics of high data security, so these applications are generally run on private cloud platforms. However, given the cloud-native characteristics, even if only non-functional configuration changes are made to applications in private cloud platforms, they need to restart the container to take effect, and restarting the container will affect business continuity.

[0029] Non-functional configuration in a cloud-native environment is different from functional configuration. Functional configuration refers to a series of settings for configuring and managing the functional requirements of an application during the development and deployment of a cloud-native application. Non-functional configuration refers to configurations that do not directly bring value to the business but are necessary for the normal operation and efficient management of the application.

[0030] More specifically, the specific contents of functional configuration include but are not limited to: Code baseline: The baseline code of the application is the basis for application development. Dependency management: Explicit and isolated dependencies ensure that each part of the application can be deployed and updated independently. Configuration management: Separate the configuration information and store it in the environment to avoid hard coding in the code, which is easy to manage and update. Backend service: Separate the basic backend components to ensure the decoupling of the application and the backend service. Build, release, and run: Strictly separate the build, release, and run processes to ensure that each stage is independent. Process management: Stateless service process to ensure that the service can be horizontally expanded. Port binding: Built-in port binding to ensure that the service can run independently. Concurrency: Increase concurrency through horizontal expansion of processes. Disposability: Quick startup and graceful exit to ensure the replaceability of services. Environment parity: The development environment and the production environment are parity to ensure the consistency of testing and deployment. Log management (Log): Logs are event streams for easy monitoring and debugging. Management tasks: Separate management tasks to ensure that management tasks do not affect service operation. These configurations ensure that applications can run efficiently and reliably in a cloud environment.

[0031] The specific contents of non-functional configuration include but are not limited to: High availability: ensure that the application can still operate normally in the face of hardware failures, network problems, etc., through automatic migration, load balancing and other technical means. Disaster recovery capability: ensure that the application can recover quickly when a disaster occurs, reducing business interruption time. Security: protect the application from external attacks and data leakage, and ensure the security of data transmission and storage. Operability: provide easy-to-manage and maintain interfaces and tools to reduce operation and maintenance costs and complexity. Ease of use: provide user-friendly interfaces and operating processes to improve user experience. Testability: provide automated testing tools and methods to ensure the quality and stability of the application. Gray release capability: gradually introduce new features or updates to reduce interference with existing services and ensure a smooth transition. These non-functional configurations are particularly important in cloud-native environments, because cloud-native architectures usually run in distributed environments and need to deal with complex system management and maintenance issues.

[0032] like Figure 1 As shown, the application change method of the private cloud platform includes:

[0033] S110. For a target application deployed on a private cloud platform, determine target annotation content corresponding to the target application based on historical resource usage information, non-functional configuration information, and non-functional specification information of the private cloud platform of the target application.

[0034] Among them, the target application refers to any application deployed in the private cloud platform. Historical resource usage information refers to the resource usage of the target application in the historical period. The historical resource usage information mainly includes historical computing resource usage and historical storage resource usage. Non-functional configuration information refers to the non-functional configuration data corresponding to the target application. For example, the specific form of the non-functional configuration information corresponding to the target application can be multiple non-functional configuration items and the specific data content under each non-functional configuration item. In actual applications, each non-functional configuration item and the specific data content under the corresponding configuration item can be recorded in the form of key-value pairs.

[0035] Among them, the non-functional specification information of the private cloud platform refers to the non-functional configuration specification information stipulated by the private cloud platform. The non-functional specification information can be an application non-functional configuration specification determined according to the private cloud platform specification. The non-functional specification information includes multiple non-functional configuration items and the available specific data content corresponding to each non-functional configuration item. Optionally, when the private cloud platform adds a new configuration specification and / or changes the configuration specification, the non-functional specification information of the private cloud platform is updated to obtain the updated non-functional specification information. In this embodiment, whenever the private cloud platform changes the platform specification, for example, when adding a new configuration specification item, adding a required content under a new configuration specification item, deleting a configuration specification item, deleting a required content under a configuration specification item, modifying the name of a configuration specification item, modifying the required content under a configuration specification item, etc., the non-functional specification information of the private cloud platform can be updated to obtain the updated non-functional specification information.

[0036] In this embodiment, annotation is a way to add metadata to the code, which is used to provide additional information or instructions for program elements (such as classes, methods, member variables, etc.), and this information or instructions is the annotation content. The annotation itself does not affect the actual logic of the code, but can be read by tools or frameworks and perform corresponding processing at compile time, class loading time or runtime. Annotations usually start with the @ symbol, followed by the name of the annotation and a pair of brackets, which can contain some parameters. The target annotation content refers to the annotation information content added for the target application.

[0037] It should be noted that a large number of applications can be deployed in the private cloud platform, and these applications are target applications. In this embodiment, the processing process for each target application is the same, and any one of the target applications is used as an example for exemplary description.

[0038] Specifically, the specific matters and methods for determining the target annotation content corresponding to the target application may include: for the target application, according to the preset timed task, at every preset time, the historical resource usage information and the actual resource allocation information of the target application in the past preset time can be determined once; if the difference between the historical resource usage information and the actual resource allocation information is too great, the resource configuration recommendation information corresponding to the target application can be determined according to the historical resource usage information, and the resource configuration recommendation information may specifically include: the recommended amount of computing resources and the recommended amount of storage resources. Similarly, according to the preset timed task, at every preset time, the non-functional configuration information of the target application and the non-functional specification information of the private cloud platform can be subjected to a normative inspection to determine whether the non-functional configuration information of the target application matches the non-functional specification information of the private cloud platform. If it does not match, the non-functional configuration information under the non-matching non-functional configuration item is modified and adapted according to the non-functional specification information of the private cloud platform to obtain the non-functional configuration change information; if it matches, the non-functional configuration change information will not be generated; thus, the resource configuration recommendation information and the non-functional configuration change information can be used as the target annotation content corresponding to the target application.

[0039] Exemplarily, for a target application A deployed in a private cloud platform, the historical resource usage information and actual resource allocation information of the target application A in the past 24 hours can be determined once every 24 hours. For example, the historical resource usage information includes: the computing resource usage sampling values ​​and storage resource usage sampling values ​​at N historical time points in the past 24 hours. The maximum value of each computing resource usage sampling value is 5 cores, and the maximum value of each storage resource usage sampling value is 10 gigabytes; the actual resource allocation information includes: the actual computing resource usage is 100 cores and the actual storage resource usage is 200 gigabytes. Based on this, the resource configuration recommendation information corresponding to the target application A can be determined based on the preset resource quantity recommendation algorithm and the historical resource usage information. The resource configuration recommendation information can specifically include: the computing resource recommendation is 10 cores and the storage resource recommendation is 20 gigabytes. Similarly, the non-functional configuration information of the target application A and the non-functional specification information of the private cloud platform can be subjected to a normative check every 24 hours to determine whether the non-functional configuration information matches the non-functional specification information. For example, Table 1 is an example table of non-functional configuration information representing target application A, and Table 2 is non-functional specification information representing a private cloud platform.

[0040] Table 1 Example of non-functional configuration information

[0041] Non-functional configuration item 1 Aaa Non-functional configuration item 2 0 Non-functional configuration item 3 nnnn Non-functional configuration item 4 jjjj

[0042] Table 2 Example of non-functional specification information

[0043] Non-functional configuration item 1 Aaa Non-functional configuration item 2 0 Non-functional configuration item 3 nnnn Non-functional configuration item 4 iiii Non-functional configuration item 5 X Non-functional configuration item 6 Y

[0044] As can be seen from Table 1 and Table 2, the non-functional configuration information lacks "non-functional configuration item 5: X" and "non-functional configuration item 6: Y" in the non-functional specification information; therefore, "non-functional configuration item 5: X" and "non-functional configuration item 6: Y" can be determined as non-functional configuration change information. The field content under non-functional configuration item 4 in the non-functional configuration information is: "jjjj", and the field content under non-functional configuration item 4 in the non-functional specification information is: "iiii", and "non-functional configuration item 4: jjjj changed to non-functional configuration item 4: iiii" can be determined as non-functional configuration change information. Based on this, "resource recommendation is 10 cores, storage resource recommendation is 20 gigabytes", "non-functional configuration item 5: X", "non-functional configuration item 6: Y" and "non-functional configuration item 4: jjjj changed to non-functional configuration item 4: iiii" can be used as the target annotation content corresponding to the target application.

[0045] S120. When a functional change request corresponding to a target application is detected, the target application is changed based on the target annotation content and the functional change request to obtain an updated changed application.

[0046] The functional change request is a request signal for changing the functional configuration of the target application program. The changed application program is an application program after synchronously changing the functional configuration and non-functional configuration of the target program.

[0047] Specifically, for the target application, when the service function of the target application needs to be changed or optimized, a request for a functional change request to the target application can be generated. When a functional change request corresponding to the target application is detected, the functional change request can be intercepted and the target annotation content corresponding to the target application can be pulled. Thus, according to the functional change configuration information carried in the functional change request and the resource configuration recommendation information and non-functional configuration change information in the target annotation content, the target application can be subjected to functional and non-functional synchronous change processing to obtain an updated changed application.

[0048] The technical solution of the embodiment of the present invention first determines the target annotation content corresponding to the target application deployed on the private cloud platform based on the historical resource usage information, non-functional configuration information of the target application, and non-functional specification information of the private cloud platform, so that when a functional change request corresponding to the target application is detected, the target application is changed based on the target annotation content and the functional change request to obtain an updated changed application. The technical solution of this embodiment determines the target annotation content based on the historical resource usage information and non-functional configuration information of the target application and the non-functional specification information of the private cloud platform, so that when the target application needs to be functionally changed, the target application is automatically non-functionally changed according to the target annotation content, which can achieve non-functional configuration maintenance of large-scale applications in a lighter, more convenient and safer way, and improve the resource utilization and configuration standardization of cloud native clusters.

[0049] Embodiment 2

[0050] Figure 2 This is a schematic diagram of a method for changing an application of a private cloud platform provided by an embodiment of the present invention. Based on the above embodiment, S110-S120 are further refined. The specific implementation method can refer to the technical solution of this embodiment. The technical terms that are the same or corresponding to the above embodiment are not repeated here.

[0051] like Figure 2 As shown, the method specifically comprises the following steps:

[0052] S210: Determine resource configuration recommendation information corresponding to the target application based on the actual resource allocation information and historical resource usage information of the target application.

[0053] In this embodiment, the actual resource allocation information refers to the resource usage actually allocated to the target application. The resource configuration recommendation information refers to the resource usage recommended for the target application. The actual resource allocation information specifically includes the actual allocation pre-occupancy value and the actual allocation upper limit value. Accordingly, the resource configuration recommendation information specifically may include: pre-occupancy value recommendation information and upper limit value recommendation information. Among them, the pre-occupancy value refers to the number of resources reserved or occupied in advance, and the pre-occupancy value ensures that these resources can be allocated to the target application when needed, thereby avoiding resource conflicts and waste. The upper limit value refers to the maximum value of the resources that the target application can use, which is a value that is theoretically achievable but difficult to achieve in practice. It can be understood that resources include computing resources and storage resources. Based on this, the actual resource allocation information may include: the actual allocation pre-occupancy value of computing resources, the actual allocation upper limit value of computing resources, the actual allocation pre-occupancy value of storage resources, and the actual allocation upper limit value of storage resources; the resource configuration recommendation information may include the actual allocation pre-occupancy value of computing resources, the upper limit value recommendation information of computing resources, the pre-occupancy value recommendation information of storage resources, and the upper limit value recommendation information of storage resources. It should be noted that the method for determining the resource configuration recommendation information of computing resources and storage resources is consistent, and the resources in the following embodiments can be computing resources or storage resources.

[0054] Among them, the historical resource usage information includes resource usage sampling values ​​at multiple historical time points within the historical preset time length. The resource usage sampling values ​​include computing resource usage sampling values ​​and storage resource usage sampling values. The historical preset time length can be within 1 day, 1 week, 1 month, etc. from the current moment, and the time length corresponding to the preset time length can be adjusted according to actual needs. Exemplarily, the time interval between each two adjacent historical time points is 1 minute, and the historical preset time length is 1 day, then the historical resource usage information may include 1440 computing resource usage sampling values ​​and 1440 storage resource usage sampling values.

[0055] In this embodiment, resource configuration recommendation information corresponding to the target application program may be determined according to the difference between the actual resource allocation information and the historical resource usage information.

[0056] Optionally, the specific implementation method of determining the resource configuration recommendation information corresponding to the target application may include the following steps:

[0057] S1. Arrange the resource usage sample values ​​contained in the historical resource usage information in ascending order, and determine the resource usage preset percentile value and the resource usage peak value according to the sorting result.

[0058] The preset percentile value of resource usage is the preset numerical percentile corresponding to the resource usage. For example, the preset numerical value may be 70%, 80%, 90%, 99%, etc. The value of the preset numerical value may be adjusted according to actual needs. Next, the preset numerical value of 99% is used as an example for explanation. At this time, the preset percentile value of resource usage can be expressed as the 99th percentile value of resource usage. The peak value of resource usage is the maximum value among the sampled values ​​of each resource usage.

[0059] Specifically, the N resource usage sample values ​​included in the historical resource usage information may be arranged in ascending order, so that the resource usage sample value ranked at the N×99% position is determined as the 99th percentile value of resource usage, and the maximum value among the N resource usage sample values ​​is determined as the resource usage peak value. In particular, if N×99% is in the form of decimal data, it may be rounded to the nearest integer.

[0060] S2. Determine the pre-occupancy value recommendation information corresponding to the target application based on the preset percentile value of resource usage and the actually allocated pre-occupancy value.

[0061] Specifically, if the value of the preset percentile of resource usage is greater than the actual allocated pre-occupancy value, the actual allocated pre-occupancy value is increased based on the first preset resource quantity adjustment rule to obtain the pre-occupancy value recommendation information corresponding to the target application; if the value of the preset percentile of resource usage is equal to the actual allocated pre-occupancy value, the actual allocated pre-occupancy value is determined as the pre-occupancy value recommendation information corresponding to the target application; if the value of the preset percentile of resource usage is less than the actual allocated pre-occupancy value, the actual allocated pre-occupancy value is reduced based on the second preset resource quantity adjustment rule to obtain the pre-occupancy value recommendation information corresponding to the target application. Among them, the preset resource quantity adjustment rule is a preset resource quantity adjustment method.

[0062] S3. Based on the resource usage peak value and the actual allocation upper limit value, determine the upper limit value recommendation information corresponding to the target application.

[0063] Specifically, the resource usage peak threshold can be determined based on the actual allocation upper limit value and the preset resource usage rate; if the resource usage peak value is greater than the resource usage peak threshold, the actual allocation upper limit value is increased based on the third preset resource quantity adjustment rule to obtain the upper limit value recommendation information corresponding to the target application; if the resource usage peak value is less than the resource usage peak threshold, the actual allocation upper limit value is reduced based on the fourth preset resource quantity adjustment rule to obtain the upper limit value recommendation information corresponding to the target application.

[0064] Exemplarily, the upper limit of the actual allocation of computing resources of the target application is 100 cores, and the preset resource usage rate is 80%, then the resource usage peak threshold is 80 cores. If the resource usage peak is greater than 80 cores, the upper limit of the actual allocation of computing resources can be increased, and the ratio between the resource usage peak and the increased upper limit of the actual allocation of computing resources is 80%. If the resource usage peak is less than 80 cores, the upper limit of the actual allocation of computing resources can be reduced, and the ratio between the resource usage peak and the reduced upper limit of the actual allocation of computing resources is 80%. Thus, the increased or reduced upper limit of the actual allocation of resources can be determined as the upper limit recommendation information corresponding to the target application.

[0065] In this embodiment, if the difference between the actual resource allocation information of the target application and the historical resource usage information is too large, it indicates that the actual resource allocation information of the target application is not reasonable, which may cause the problem of resource waste. Based on this, in this case, the computing resource allocation and storage resource allocation of the target application can be adjusted to obtain the resource configuration recommendation information corresponding to the target application. In this way, the resource utilization rate of the private cloud platform can be improved while ensuring the resource usage requirements of the target application.

[0066] S220 . Determine non-functional configuration change information corresponding to the target application based on the compliance result between the non-functional configuration information of the target application and the non-functional specification information.

[0067] The compliance result is used to indicate whether the non-functional configuration information of the target application is in compliance with the non-functional specification information of the private cloud platform. The compliance result may include non-compliant results and compliant results. The non-functional configuration change information is information content indicating that the non-functional configuration of the target application needs to be updated.

[0068] In this embodiment, the non-functional configuration information of the target application and the non-functional specification information of the private cloud platform can be subjected to a normative check to determine whether the non-functional configuration information matches the non-functional specification information. If they do not match, the non-functional configuration change information can be further determined, for example, the non-functional configuration change information that has been generated can be updated, or new non-functional configuration change information can be generated. If they match, the non-functional configuration change information will not be generated.

[0069] Specifically, based on the matching result between the non-functional configuration information of the target application and the non-functional specification information, a specific implementation method of determining the non-functional configuration change information corresponding to the target application may include:

[0070] (1) Perform compliance check on the non-functional configuration information of the target application and the non-functional specification information of the private cloud platform to determine the compliance results between the non-functional configuration information and the non-functional specification information.

[0071] In this embodiment, compliance inspection can be performed on the non-functional configuration information and the non-functional specification information, and the specific inspection contents of the compliance inspection can include: confirming whether the non-functional configuration information includes all the configuration items in the non-functional specification information, confirming whether the specific configuration fields under each configuration item in the non-functional configuration information meet the configuration requirements under the corresponding configuration item in the non-functional specification information, etc. If all inspection contents are passed, the compliance result is a compliant result; if at least one inspection content fails, the compliance result is a non-compliant result.

[0072] (2) If the compliance result is a non-compliant result, and the resource object corresponding to the target application does not include historical annotation content, then non-functional configuration change information corresponding to the target application is generated based on the field content under the mismatching items in the non-functional specification information and the non-functional configuration information.

[0073] (3) If the compliance result is a non-compliant result, and the resource object corresponding to the target application includes historical annotation content, the historical annotation content is updated according to the field content under the mismatching items in the non-functional specification information and the non-functional configuration information to obtain the non-functional configuration change information corresponding to the target application.

[0074] The historical annotation content represents the target annotation information determined before the current execution cycle.

[0075] In this embodiment, for the case where the compliance result is a non-compliant result, if the resource object corresponding to the target application does not include historical annotation content, then the non-functional configuration change information corresponding to the target application can be generated according to the field content under the mismatching items in the non-functional specification information and the non-functional configuration information. If the resource object corresponding to the target application includes historical annotation content, it indicates that the annotation information has been generated before, and at this time, it is sufficient to update the previous annotation information. Based on this, at this time, the historical non-functional configuration change information in the historical annotation content can be updated according to the field content under the mismatching items in the non-functional specification information and the non-functional configuration information, and the non-functional configuration change information corresponding to the target application can be obtained.

[0076] (4) If the matching result is a compliance result and the resource object corresponding to the target application includes historical annotation content, the historical annotation content is deleted.

[0077] In this embodiment, if the compliance result is a compliance result, it is not necessary to obtain non-functional configuration change information. In this case, if the resource object corresponding to the target application includes historical annotation content, these historical annotation contents can be deleted to avoid repeating the operation of performing non-functional changes on the target application.

[0078] S230: Generate target annotation content in the resource object of the target application based on the resource configuration recommendation information and the non-functional configuration change information.

[0079] In this embodiment, the resource configuration recommendation information and the non-functional configuration change information may be used as the target annotation information, and the target annotation information is added to the resource object of the target application, thereby generating the target annotation content.

[0080] S240: When a functional change request corresponding to a target application is detected, the functional change request is intercepted, and target annotation content corresponding to the target application is pulled.

[0081] In this embodiment, for the target application, when the service function of the target application needs to be changed or optimized, a request for functional change request to the target application can be generated. When the functional change request corresponding to the target application is detected, the functional change request can be intercepted and the target annotation content corresponding to the target application can be pulled.

[0082] S250: Write the target annotation content into the change configuration file carried in the functional change request to obtain the target change configuration file.

[0083] The target annotation content includes resource configuration recommendation information and non-functional configuration change information. The change configuration file is the configuration information file required to make functional changes to the target application. The target change configuration file is the configuration information file that adds the target annotation content to the change configuration file.

[0084] In this embodiment, the functional change request carries a change configuration file. After intercepting the functional change request and pulling the target annotation content, the target annotation content can be added to the configuration information file to obtain the target change configuration file.

[0085] For example, when the ApiServer receives a functional change request corresponding to the target application, the webhook can be triggered. At this time, the functional change request can be intercepted by the webhook, and the target annotation content of the target application can be pulled, and the change configuration file carried in the functional change request can be modified according to the target annotation content to obtain the target change configuration file.

[0086] S260: Based on the target change configuration file, perform functional and non-functional synchronous change processing on the target application.

[0087] In this embodiment, based on the target change configuration file, the target application can be synchronously changed functionally and non-functionally according to the functional configuration information, resource configuration recommendation information and non-functional configuration change information in the target change configuration file to finally obtain an updated changed application.

[0088] The technical solution of the embodiment of the present invention determines the resource configuration recommendation information corresponding to the target application based on the actual resource allocation information and historical resource usage information of the target application; determines the non-functional configuration change information corresponding to the target application based on the matching result between the non-functional configuration information of the target application and the non-functional specification information; generates target annotation content in the resource object of the target application based on the resource configuration recommendation information and the non-functional configuration change information; when a functional change request corresponding to the target application is detected, the functional change request is intercepted, and the target annotation content corresponding to the target application is pulled; the target annotation content is written into the change configuration file carried in the functional change request to obtain the target change configuration file; wherein the target annotation content includes the resource configuration recommendation information and the non-functional configuration change information; based on the target change configuration file, functional and non-functional synchronous change processing is performed on the target application. The technical solution provided in this embodiment determines the target annotation content based on the historical resource usage information and non-functional configuration information of the target application and the non-functional specification information of the private cloud platform. Therefore, when it is necessary to make functional changes to the target application, the functional and non-functional synchronous changes to the target application are automatically made according to the target annotation content. This enables non-functional configuration maintenance of large-scale applications to be more lightweight, convenient, and secure, and improves the resource utilization and configuration standardization of cloud native clusters.

[0089] Embodiment 3

[0090] Figure 3 This is a structural diagram of an application change device for a private cloud platform provided by an embodiment of the present invention. The device includes: an annotation content determination module 310 and an application program change module 320.

[0091] The annotation content determination module 310 is used to determine the target annotation content corresponding to the target application deployed on the private cloud platform based on the historical resource usage information, non-functional configuration information, and non-functional specification information of the target application and the private cloud platform;

[0092] The application change module 320 is used to, when a functional change request corresponding to the target application is detected, perform change processing on the target application based on the target annotation content and the functional change request to obtain an updated changed application.

[0093] Based on the above device, optionally, the annotation content determination module 310 includes:

[0094] A resource recommendation amount determination unit, configured to determine resource configuration recommendation information corresponding to the target application based on the actual resource allocation information of the target application and the historical resource usage information;

[0095] a non-functional information determining unit, configured to determine non-functional configuration change information corresponding to the target application based on a compliance result of the non-functional configuration information of the target application with the non-functional specification information;

[0096] The annotation content determination unit is used to generate target annotation content in the resource object of the target application based on the resource configuration recommendation information and the non-functional configuration change information.

[0097] Based on the above device, optionally, the resource configuration recommendation information includes: pre-occupancy value recommendation information and upper limit value recommendation information, the actual resource allocation information includes the actual allocation pre-occupancy value and the actual allocation upper limit value, the historical resource usage information includes the resource usage amount sampling values ​​at multiple historical time points within the historical preset time period, and the resource recommendation amount determination unit includes:

[0098] A resource usage information determination subunit, configured to arrange the resource usage sample values ​​contained in the historical resource usage information in ascending order, and determine a preset percentile value of resource usage and a peak value of resource usage according to the sorting result;

[0099] A pre-occupancy value recommendation value determination subunit, configured to determine the pre-occupancy value recommendation information corresponding to the target application based on the preset percentile value of resource usage and the actually allocated pre-occupancy value;

[0100] The upper limit recommendation value determination subunit is used to determine the upper limit recommendation information corresponding to the target application based on the resource usage peak value and the actual allocation upper limit value.

[0101] Based on the above device, optionally, the non-functional information determination unit includes:

[0102] A matching result determination subunit, used to match the non-functional configuration information of the target application with the non-functional specification information of the private cloud platform, and determine a matching result between the non-functional configuration information and the non-functional specification information;

[0103] A non-functional information determination subunit is used to generate non-functional configuration change information corresponding to the target application based on the field content under the mismatching items in the non-functional specification information and the non-functional configuration information if the compliance result is a non-compliant result and the resource object corresponding to the target application does not include historical annotation content; if the compliance result is a non-compliant result and the resource object corresponding to the target application includes historical annotation content, update the historical non-functional configuration change information in the historical annotation content based on the field content under the mismatching items in the non-functional specification information and the non-functional configuration information to obtain the non-functional configuration change information corresponding to the target application.

[0104] Based on the above device, optionally, the non-functional information determination unit is further used to delete the historical annotation content if the matching result is a compliance result and the resource object corresponding to the target application includes historical annotation content.

[0105] Based on the above device, optionally, the application program changing module 320 includes:

[0106] an annotation content pulling unit, configured to intercept the functional change request corresponding to the target application when a functional change request corresponding to the target application is detected, and pull the target annotation content corresponding to the target application;

[0107] A configuration file determining unit, configured to write the target annotation content into the change configuration file carried in the functional change request to obtain a target change configuration file; wherein the target annotation content includes resource configuration recommendation information and non-functional configuration change information;

[0108] The synchronous change unit is used to perform functional and non-functional synchronous change processing on the target application based on the target change configuration file.

[0109] Based on the above device, optionally, the application change device of the private cloud platform includes: a specification information update module;

[0110] The specification information updating module is used to update the non-functional specification information of the private cloud platform when the private cloud platform adds a new configuration specification and / or changes a configuration specification, so as to obtain updated non-functional specification information.

[0111] The technical solution of the embodiment of the present invention first determines the target annotation content corresponding to the target application deployed on the private cloud platform based on the historical resource usage information, non-functional configuration information of the target application, and non-functional specification information of the private cloud platform, so that when a functional change request corresponding to the target application is detected, the target application is changed based on the target annotation content and the functional change request to obtain an updated changed application. The technical solution of this embodiment determines the target annotation content based on the historical resource usage information and non-functional configuration information of the target application and the non-functional specification information of the private cloud platform, so that when the target application needs to be functionally changed, the target application is automatically non-functionally changed according to the target annotation content, which can achieve non-functional configuration maintenance of large-scale applications in a lighter, more convenient and safer way, and improve the resource utilization and configuration standardization of cloud native clusters.

[0112] The application change device for a private cloud platform provided in an embodiment of the present invention can execute the application change method for a private cloud platform provided in any embodiment of the present invention, and has functional modules and beneficial effects corresponding to the execution method.

[0113] It is worth noting that the various units and modules included in the above system are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of the functional units are only for the convenience of distinguishing each other, and are not used to limit the protection scope of the embodiments of the present invention.

[0114] Embodiment 4

[0115] Figure 4 The present invention is a schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. Figure 4 A block diagram of an exemplary electronic device 40 suitable for implementing exemplary embodiments of the present invention is shown. Figure 4 The electronic device 40 shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present invention.

[0116] like Figure 4 As shown, the electronic device 40 is in the form of a general computing device. The components of the electronic device 40 may include but are not limited to: one or more processors or processing units 401, a system memory 402, and a bus 403 connecting different system components (including the system memory 402 and the processing unit 401).

[0117] Bus 403 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor or a local bus using any of a variety of bus structures. For example, these architectures include but are not limited to Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus and Peripheral Component Interconnect (PCI) bus.

[0118] The electronic device 40 typically includes a variety of computer system readable media. These media can be any available media that can be accessed by the electronic device 40, including volatile and non-volatile media, removable and non-removable media.

[0119] System memory 402 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 404 and / or cache memory 405. Electronic device 40 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, storage system 406 may be used to read and write non-removable, non-volatile magnetic media ( Figure 4 not shown, usually called a "hard drive"). Although Figure 4 Not shown in the figure, a disk drive for reading and writing to a removable non-volatile disk (e.g., a "floppy disk"), and an optical disk drive for reading and writing to a removable non-volatile optical disk (e.g., a CD-ROM, a DVD-ROM, or other optical media) may be provided. In these cases, each drive may be connected to bus 403 via one or more data medium interfaces. Memory 402 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of various embodiments of the present invention.

[0120] A program / utility 408 having a set (at least one) of program modules 407 may be stored, for example, in memory 402, such program modules 407 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 may include an implementation of a network environment. Program modules 407 generally perform the functions and / or methods of the embodiments described herein.

[0121] The electronic device 40 may also communicate with one or more external devices 409 (e.g., keyboards, pointing devices, displays 810, etc.), may communicate with one or more devices that enable a user to interact with the electronic device 40, and / or may communicate with any device that enables the electronic device 40 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface 411. Furthermore, the electronic device 40 may also 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 a network adapter 412. As shown, the network adapter 412 communicates with other modules of the electronic device 40 via the bus 403. It should be understood that although Figure 4 Not shown, other hardware and / or software modules may be used in conjunction with the electronic device 40, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0122] The processing unit 401 executes various functional applications and page processing by running the programs stored in the system memory 402, such as implementing the application change method of the private cloud platform provided in the embodiment of the present invention.

[0123] Embodiment 5

[0124] An embodiment of the present invention further provides a storage medium including computer executable instructions, which are used to execute a method for changing an application of a private cloud platform when executed by a computer processor. The method includes:

[0125] For a target application deployed on a private cloud platform, determining a target annotation content corresponding to the target application based on historical resource usage information, non-functional configuration information, and non-functional specification information of the target application and the private cloud platform;

[0126] When a functional change request corresponding to the target application is detected, the target application is changed based on the target annotation content and the functional change request to obtain an updated changed application.

[0127] The computer storage medium of the embodiment of the present invention can adopt any combination of one or more computer-readable media. The computer-readable medium can be a computer-readable signal medium or a computer-readable storage medium. The computer-readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples (non-exhaustive list) of computer-readable storage media include: 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 of the above. In this document, a computer-readable storage medium can be any tangible medium containing or storing a program, which can be used by an instruction execution system, device or device or used in combination with it.

[0128] Computer-readable signal media may include data signals propagated in baseband or as part of a carrier wave, which carry computer-readable program code. Such propagated data signals may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. Computer-readable signal media may also be any computer-readable medium other than a computer-readable storage medium, which may send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0129] Program code embodied on a computer 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.

[0130] Computer program code for performing the operation of embodiments of the present invention may be written in one or more programming languages ​​or a combination thereof, including object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0131] Note that the above are only preferred embodiments of the present invention and the technical principles used. Those skilled in the art will understand that the present invention is not limited to the specific embodiments herein, and that various obvious changes, readjustments and substitutions can be made by those skilled in the art without departing from the scope of protection of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments, and may include more other equivalent embodiments without departing from the concept of the present invention, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. A method for changing an application of a private cloud platform, characterized in that: include: For a target application deployed on a private cloud platform, determining a target annotation content corresponding to the target application based on historical resource usage information, non-functional configuration information, and non-functional specification information of the target application and the private cloud platform; When a functional change request corresponding to the target application is detected, the target application is changed based on the target annotation content and the functional change request to obtain an updated changed application.

2. The method according to claim 1, characterized in that The determining of target annotation content corresponding to the target application based on historical resource usage information of the target application, non-functional configuration information, and non-functional specification information of the private cloud platform includes: Determining resource configuration recommendation information corresponding to the target application based on the actual resource allocation information of the target application and the historical resource usage information; Determining non-functional configuration change information corresponding to the target application based on a compliance result of the non-functional configuration information of the target application and the non-functional specification information; Based on the resource configuration recommendation information and the non-functional configuration change information, target annotation content is generated in the resource object of the target application.

3. The method according to claim 2, characterized in that The resource configuration recommendation information includes: pre-occupancy value recommendation information and upper limit value recommendation information, the actual resource allocation information includes the actual allocation pre-occupancy value and the actual allocation upper limit value, the historical resource usage information includes the resource usage sampling values ​​at multiple historical time points within a historical preset time period, and the resource configuration recommendation information corresponding to the target application is determined based on the actual resource allocation information of the target application and the historical resource usage information, including: Arrange the resource usage sample values ​​contained in the historical resource usage information in ascending order, and determine the resource usage preset percentile value and the resource usage peak value according to the sorting result; Determining pre-occupancy value recommendation information corresponding to the target application based on the preset percentile value of resource usage and the actually allocated pre-occupancy value; Based on the resource usage peak value and the actual allocation upper limit value, upper limit value recommendation information corresponding to the target application is determined.

4. The method according to claim 2, characterized in that: The determining, based on the compliance result of the non-functional configuration information of the target application and the non-functional specification information, the non-functional configuration change information corresponding to the target application comprises: Performing compliance check on the non-functional configuration information of the target application and the non-functional specification information of the private cloud platform to determine a compliance result between the non-functional configuration information and the non-functional specification information; If the compliance result is a non-compliant result, and the resource object corresponding to the target application does not include historical annotation content, then generating non-functional configuration change information corresponding to the target application according to the field content under the mismatching item in the non-functional specification information and the non-functional configuration information; If the compliance result is a non-compliant result, and the resource object corresponding to the target application includes historical annotation content, the historical non-functional configuration change information in the historical annotation content is updated according to the field content under the mismatching items between the non-functional specification information and the non-functional configuration information to obtain the non-functional configuration change information corresponding to the target application.

5. The method according to claim 4, characterized in that The method further comprises: If the matching result is a compliance result, and the resource object corresponding to the target application includes historical annotation content, the historical annotation content is deleted.

6. The method according to claim 1, characterized in that When a functional change request corresponding to the target application is detected, the target application is changed based on the target annotation content and the functional change request, including: When a functional change request corresponding to the target application is detected, the functional change request is intercepted, and the target annotation content corresponding to the target application is pulled; Writing the target annotation content into the change configuration file carried in the functional change request to obtain a target change configuration file; wherein the target annotation content includes resource configuration recommendation information and non-functional configuration change information; Based on the target change configuration file, functional and non-functional synchronous change processing is performed on the target application.

7. The method according to claim 1, characterized in that The method further comprises: When the private cloud platform adds a new configuration specification and / or changes a configuration specification, the non-functional specification information of the private cloud platform is updated to obtain updated non-functional specification information.

8. An application change device for a private cloud platform, characterized in that: The device includes: An annotation content determination module is used to determine, for a target application deployed on a private cloud platform, a target annotation content corresponding to the target application based on historical resource usage information, non-functional configuration information, and non-functional specification information of the private cloud platform of the target application; The application change module is used to, when a functional change request corresponding to the target application is detected, perform change processing on the target application based on the target annotation content and the functional change request to obtain an updated changed application.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can execute the application change method of the private cloud platform described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the application change method of the private cloud platform described in any one of claims 1-7 when executed.

Images