Method, device and equipment for realizing cloud service by cloud-native unified control platform

Abstract

The application relates to the technical field of computers and discloses a method, device and equipment for realizing cloud services by a cloud native unified control platform, the method comprising the following steps: when a Kubernetes controller listens to the fact that a new deployment file is received in an open-source container orchestration platform cluster, the deployment file is parsed, at least one component included in the deployment file is acquired, operation and maintenance characteristic information corresponding to the component is acquired, the type of the component is identified according to the service type attribute of each component, and cloud services are realized through a cloud platform plug-in. The Kubernetes controller utilizes the self-defined plug-in capability to create cloud resources corresponding to the cloud services, and realizes the resource configuration and deployment required by the component. The automatic realization and deployment of the cloud service component enable the whole system to efficiently run applications, and improve the efficiency and flexibility of the system.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of computer, in particular to a method, device and equipment for realizing cloud service by cloud-native unified control platform. BACKGROUND

[0002] The open source container orchestration platform (Kubernetes, referred to as K8s) provides a declarative resource definition template, and developers need to be familiar with the complex resource configuration of Kubernetes to complete basic application deployment and configuration. In the complete life cycle of the application, a large number of operation and maintenance feature configurations are required, such as application gateway (Ingress), monitoring, dynamic scaling, traffic control, release strategy, underlying computing and storage resource creation, etc. Developers not only need to focus on business logic, but also need to be familiar with the functions of the configuration operation and maintenance layer, and even need to understand and complete the corresponding configuration for the infrastructure.

[0003] At the infrastructure level, although the application can run as a container on the Kubernetes cluster, the complexity of the computing resources is shielded by Kubernetes. With the deep embedding of the business system into the cloud foundation, the running and deployment of the application also relies on a large number of cloud product capabilities, such as cloud database, operation and maintenance monitoring capability, cloud gateway, identity and access management (IAM authentication and authorization), cloud hard disk, etc. The configuration of these cloud products also needs to be prepared in advance through additional manual settings or Terraform scripts. At the same time, in the multi-cloud deployment scenario, there are various differences in the products and configuration methods between different cloud vendors. SUMMARY

[0004] Therefore, the present application provides a method, device and equipment for realizing cloud service by cloud-native unified control platform, to solve the problem of separating the focus of developers and operation and maintenance personnel, and the differences in products and configuration methods between different cloud vendors in the multi-cloud deployment scenario.

[0005] In a first aspect, the present application provides a method for realizing cloud service by cloud-native unified control platform, which comprises: when it is listened that a new deployment file is received in an open source container orchestration platform cluster, parsing the deployment file to obtain at least one component included in the deployment file and operation and maintenance feature information corresponding to the component, wherein the deployment file is a file uploaded in the form of an open application model definition file;

[0006] According to the service type attribute of each component, the type of the component is identified, wherein the service type attribute is one of the plurality of operation and maintenance features;

[0007] When the at least one component is identified as a cloud service component based on the type of each component, each cloud service component and all operation and maintenance features corresponding to the cloud service component are respectively transmitted to a cloud platform plug-in corresponding to the cloud service component, so that the cloud service corresponding to the first cloud service component is realized by the first cloud platform plug-in using the operation and maintenance features corresponding to the first cloud service component, wherein the first cloud platform plug-in is a cloud platform plug-in corresponding to the first cloud service component, and the first cloud service component is any one of the at least one cloud service component.

[0008] The application provides a cloud-native unified control platform for realizing cloud services, which has the following advantages: an open source container orchestration platform controller receives a deployment file, parses the deployment file, obtains deployment operation and maintenance features corresponding to cloud service components in the deployment file, and transmits the operation and maintenance features to a cloud platform plug-in, which realizes cloud services required by an application using the operation and maintenance features. The application defines a specification and framework of an application model file, and defines a model of configuration and operation and maintenance, infrastructure-related, and cloud product configuration of an application layer. Developers focus on logical configuration of a business layer, operation and maintenance personnel configure operation and maintenance-related attributes, and an underlying IaaS provider provides corresponding cloud capability configuration, thereby reducing collaboration costs between different teams.

[0009] The Kubernetes controller realizes resource configuration and deployment of Kubernetes components, and cloud resources corresponding to cloud services are created by combining the Kubernetes custom plug-in capability, so that automatic implementation of cloud service components is realized, efficient operation of an application of the entire system is achieved, and system efficiency and flexibility are improved.

[0010] In an optional implementation, when the at least one component is identified as a cloud service component based on the type of each component, before each cloud service component and all operation and maintenance feature information corresponding to the cloud service component are respectively transmitted to a cloud platform plug-in corresponding to the cloud service component, the method further includes:

[0011] The operation and maintenance feature information corresponding to each cloud service component is converted into a cloud service object, which is used for subsequent transmission of the cloud service object to the cloud platform plug-in.

[0012] Specifically, converting all operation and maintenance characteristic information corresponding to each cloud service component into a cloud service object makes the management and maintenance of cloud services more simple and consistent, and greatly improves the portability of cloud service components and their corresponding operation and maintenance characteristic information. The cloud platform plug-in receives the cloud service object transmitted by the controller, converts the cloud service object into the parameter format required by the cloud platform, calls the corresponding application programming interface in the software development kit corresponding to the cloud platform, implements the cloud service corresponding to the cloud service component, and the cloud platform plug-in can uniformly manage and automate the configuration and deployment of cloud services, reducing the need for manual configuration, reducing the error rate, and improving efficiency. Through the cloud platform plug-in, the developer does not need to deeply understand the complexity of the cloud platform, so that the developer can focus more on the implementation of business logic. The cloud platform plug-in provides a consistent experience for different cloud platforms, making it easier to deploy and manage applications in a multi-cloud environment.

[0013] In an optional implementation, when at least one component is identified as a cloud service component based on the type of each component, after transmitting each cloud service component and all operation and maintenance characteristics corresponding to the cloud service component to the cloud platform plug-in corresponding to the cloud service component, the method further comprises:

[0014] Receiving access information corresponding to the cloud service fed back by at least one cloud platform plug-in.

[0015] Converting at least one access information into a target format, and storing it in a preset storage location in the open source container orchestration platform cluster for subsequent extraction of access information in the target format from the preset storage location to access the cloud service.

[0016] Specifically, after the cloud platform plug-in implements the cloud service corresponding to the cloud service component, it will return access information related to the cloud service, convert the access information into a target format and store it in a preset storage location, which can realize unified management and maintenance of cloud service access information and simplify access permission issues. And store the access information in the open source container orchestration platform cluster, which can easily expand the storage capacity and access control strategy according to actual needs to adapt to changing business needs. Extracting access information in the target format from the preset storage location to access the cloud service can ensure that these information can be accessed quickly and reliably when needed, improving the availability and reliability of cloud services.

[0017] In an optional implementation, before transmitting each cloud service component and all operation and maintenance characteristics corresponding to the cloud service component to the cloud platform plug-in corresponding to the cloud service component, the method further comprises:

[0018] Extracting the cloud platform plug-in corresponding to the cloud service component from the pre-built plug-in registry.

[0019] Specifically, different cloud platforms correspond to different cloud platform plugins, and the open source container orchestration platform cluster implements cloud services on the cloud platform through the cloud platform plugin. A plurality of cloud platform plugins are stored in a pre-built plugin registry. Before each cloud service component and all operation and maintenance features corresponding to the cloud service component are respectively transmitted to the cloud platform plugin corresponding to the cloud service component, the cloud platform plugin corresponding to the cloud service component needs to be extracted from the pre-built plugin registry. The pre-built plugin registry can reduce resource waste, because it is not necessary to build and maintain plugins for each cloud service component. And centralized management of the plugin registry makes it easier to update, maintain and monitor the cloud platform plugin, which helps to respond to problems in a timely manner.

[0020] In an optional implementation, when at least one component is identified as an open source container orchestration platform component based on each component type attribute, the open source container orchestration platform component includes:

[0021] The way of deploying and managing containers, the way of self-repairing, the way of key and configuration management, the way of application rollback, the application update policy, the way of log collection, the way of service discovery and load balancing, and the way of storage orchestration.

[0022] Specifically, by identifying the container orchestration platform component and its corresponding operation and maintenance feature information, automatic deployment, self-repairing, key and configuration management, etc. of containers can be realized, greatly improving the automation level of operation and maintenance. The self-repairing way and the application rollback mechanism can ensure quick recovery when a container or service has a problem, improving the flexibility and reliability of the system. The application update policy can help smoothly deploy new versions of applications, reducing service interruptions during the update process. The service discovery and load balancing mechanism can improve the availability and response speed of services, ensuring reasonable allocation of traffic. The storage orchestration way can optimize the use of storage resources, improve storage efficiency and data access speed. The above components realize the functions of automatic deployment and expansion of application programs, fault self-healing, dynamic allocation of resources, etc., greatly improving the operation and maintenance efficiency of applications.

[0023] In an optional implementation, when at least one component is identified as an open source container orchestration platform component based on each component type attribute, the method further includes:

[0024] Implementing open source container orchestration platform services according to the operation and maintenance feature information corresponding to each open source container orchestration platform component.

[0025] Specifically, the implementation of the open source container orchestration platform component is carried out according to the corresponding operation and maintenance characteristic information, the developer develops the application program, the operation and maintenance personnel configures the component related to the application program deployment and the operation and maintenance characteristic information related to the component implementation, and the open source container orchestration platform implements each operation and maintenance characteristic information. The developer focuses on the logical configuration at the business level, the operation and maintenance personnel configures the related operation and maintenance characteristic information, the open source container orchestration platform implements each operation and maintenance characteristic information, and the cooperation cost between different teams is reduced.

[0026] In an optional implementation, when the deployment file is updated in the pre-built deployment file library, the continuous deployment system extracts the latest deployment file from the component file library and transmits the latest deployment file to the open source container orchestration platform controller through the open source container orchestration platform interface.

[0027] Specifically, the continuous deployment system automatically monitors the pre-built deployment file storage warehouse, and as soon as a new deployment file is monitored, the extraction and forwarding process is started immediately, reducing manual intervention, accelerating the online speed of the new version application, and improving the deployment efficiency.

[0028] In a second aspect, the present application provides a device for implementing cloud services by a cloud-native unified control platform, which comprises:

[0029] The analysis module is configured to analyze the deployment file when a new deployment file is received in the open source container orchestration platform cluster, obtain at least one component included in the deployment file, and obtain the operation and maintenance characteristic information corresponding to the component, wherein the deployment file is a file uploaded in the form of an open application model definition file.

[0030] The identification module is configured to identify the type of each component according to the service type attribute of each component, wherein the service type attribute is one of the plurality of operation and maintenance characteristics.

[0031] The transmission module is configured to transmit each cloud service component and all operation and maintenance characteristic information corresponding to the cloud service component to the cloud platform plug-in corresponding to the cloud service component when at least one component is identified as a cloud service component based on the type of each component, so that the first cloud platform plug-in implements the cloud service corresponding to the first cloud service component by using the operation and maintenance characteristic information corresponding to the first cloud service component, wherein the first cloud platform plug-in is the cloud platform plug-in corresponding to the first cloud service component, and the first cloud service component is any one of the at least one cloud service component.

[0032] The device for implementing cloud services by a cloud-native unified control platform provided by the present application has the following advantages:

[0033] The open source container orchestration platform controller receives the deployment file, parses the deployment file, obtains the deployment and operation characteristics corresponding to the cloud service component in the deployment file, and then transmits the operation characteristics to the cloud platform plug-in. The cloud platform plug-in realizes the cloud service required by the application by using the operation characteristics. The scheme defines the specification and framework of the application model definition file, and uniformly defines the model of the configuration and operation of the application layer, the infrastructure-related cloud product configuration. The developers focus on the logical configuration of the business layer, the operation personnel configure the operation-related attributes, and the underlying IaaS provider provides the corresponding cloud capability configuration, reducing the collaboration cost between different teams.

[0034] The Kubernetes controller is used to realize the resource configuration and deployment required by the Kubernetes component, and the cloud service corresponding cloud resource is created by combining the Kubernetes custom plug-in capability, so that the automatic implementation of the cloud service component is realized, the efficient running of the application of the whole system is achieved, and the system efficiency and flexibility are improved.

[0035] In a third aspect, a computer device is provided, which comprises a memory and a processor, the memory and the processor are communicatively connected with each other, the memory stores computer instructions, and the processor executes the cloud service method of the cloud native unified control platform in the first aspect or any of the corresponding embodiments thereof by executing the computer instructions.

[0036] In a fourth aspect, a computer readable storage medium is provided, which stores computer instructions, and the computer instructions are used to make a computer execute the cloud service method of the cloud native unified control platform in the first aspect or any of the corresponding embodiments thereof.

[0037] In a fifth aspect, a computer program product is provided, which comprises computer instructions, and the computer instructions are used to make a computer execute the cloud service method of the cloud native unified control platform in the first aspect or any of the corresponding embodiments thereof. BRIEF DESCRIPTION OF DRAWINGS

[0038] In order to more clearly illustrate the specific embodiments of the present application or the technical solutions in the prior art, the drawings needed in the specific embodiments or prior art description will be briefly introduced below. Obviously, the drawings in the following description are some embodiments of the present application, and those skilled in the art can also obtain other drawings according to these drawings without creative labor.

[0039] Figure 1 is a flowchart of a cloud service method of a cloud native unified control platform provided by an embodiment of the present application;

[0040] Figure 2is a flowchart of another method for implementing cloud services by a cloud-native unified control platform according to an embodiment of the present application;

[0041] Figure 3 is a flowchart of still another method for implementing cloud services by a cloud-native unified control platform according to an embodiment of the present application;

[0042] Figure 4 is a timing diagram of a method for implementing cloud services by a cloud-native unified control platform according to an embodiment of the present application;

[0043] Figure 5 is a block diagram of a device structure for implementing cloud services by a cloud-native unified control platform according to an embodiment of the present application;

[0044] Figure 6 is a hardware structure diagram of a computer device according to an embodiment of the present application. DETAILED DESCRIPTION

[0045] To make the objectives, technical solutions, and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are some but not all of the embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present application.

[0046] Kubernetes provides a declarative resource definition template, and developers need to be familiar with the complex resource configuration of Kubernetes to complete basic application deployment and configuration. In the complete life cycle of an application, a large number of operation and maintenance features need to be configured, such as Ingress, monitoring, dynamic scaling, traffic control, release strategy, underlying computing and storage resource creation, etc. Developers cannot focus on business logic and also need to be familiar with the configuration of the operation and maintenance layer functions, and even need to understand and complete the corresponding configuration for the infrastructure.

[0047] At the infrastructure level, although the application can run as a container on the Kubernetes cluster, the complexity of the computing resources is shielded by Kubernetes, but as the business system is deeply embedded in the cloud infrastructure, the running and deployment of the application also relies on a large number of cloud product capabilities, such as cloud database, operation and maintenance monitoring capability, cloud gateway, IAM authentication and authorization, cloud hard disk, etc. The configuration of these cloud products also needs to be prepared in advance through additional manual settings or Terraform scripts. At the same time in the multi-cloud deployment scenario, there are various differences between the products and configuration methods of different cloud vendors.

[0048] To solve the above problems, the embodiment of the present application provides an embodiment of a cloud-native unified control platform for implementing cloud services. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system (computer device) including, for example, a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described herein can be executed in an order different from that shown.

[0049] When a developer wants to deploy his application in a Kubernetes cluster, he needs to formulate a detailed deployment file according to business requirements. The deployment file covers all components required for the application to be deployed in the Kubernetes cluster to achieve the desired running state and their corresponding operation and maintenance features. After formulating the detailed deployment file, the deployment file and / or the application package are uploaded to a pre-built deployment file library.

[0050] The continuous deployment system obtains the deployment file from the pre-built deployment file library and transmits it to the open source container orchestration platform cluster through the open source container orchestration platform interface.

[0051] When the open source container orchestration platform controller listens to the reception of a new deployment file in the open source container orchestration platform cluster, the embodiment provides a method for implementing cloud services by a cloud-native unified control platform, which can be used in the terminal device such as a mobile phone, a tablet computer, etc. Figure 1 is a flowchart of a method for implementing cloud services by a cloud-native unified control platform provided by the embodiment of the present application, as shown in Figure 1 The flowchart includes the following steps:

[0052] Step S101, the deployment file is parsed to obtain at least one component included in the deployment file and the operation and maintenance feature information corresponding to the component.

[0053] Specifically, the deployment file covers all components required for the application to be deployed in the Kubernetes cluster to achieve the desired running state and their corresponding operation and maintenance features, and the deployment file is formulated in the form of an open application model definition file.

[0054] Each service required for the deployment of the application is defined as a component in the open application model definition file, and the operation and maintenance features required for the implementation of each component are configured under each component. Among them, one component corresponds to one service, and the above-mentioned component includes a cloud service component and / or an open source container orchestration platform service component, and the cloud service component includes cloud service components in different cloud platforms.

[0055] Therefore, the newly received deployment file in the open source container orchestration platform cluster needs to be parsed to obtain the cloud service component and the operation and maintenance feature information corresponding thereto.

[0056] Step S102, identifying the type of each component according to the service type attribute of the component.

[0057] Specifically, each component has a service type attribute in the operation and maintenance characteristic information corresponding to the component, and the service type attribute indicates the type of the component. Therefore, the type of each component needs to be identified according to the service type attribute of the component.

[0058] Step S103, respectively transmitting each cloud service component and all operation and maintenance characteristic information corresponding to the cloud service component to the cloud platform plug-in corresponding to the cloud service component.

[0059] Specifically, after identifying at least one cloud service component according to the service type attribute, each cloud service component and all operation and maintenance characteristics corresponding to the cloud service component are transmitted to the cloud platform plug-in corresponding to the cloud service component. The first cloud platform plug-in uses the operation and maintenance characteristic information corresponding to the first cloud service component to implement the cloud service corresponding to the first cloud service component.

[0060] Among them, the first cloud platform plug-in is the cloud platform plug-in corresponding to the first cloud service component, and the first cloud service component is any one of the at least one cloud service component. The first cloud platform plug-in creates, queries, updates, and deletes cloud resources in the first cloud service component according to the above operation and maintenance characteristic information.

[0061] Specifically, the cloud service component includes a computing resource (Elastic Compute Service, ECS), a storage resource (such as a cloud database), an object storage service (Object Storage Service, OSS), a network resource, a load balancing (Server Load Balancer, SLB), an elastic public network IP (Elastic IP Address, EIP), a virtual private cloud (Virtual Private Cloud, VPC), etc.

[0062] The cloud native unified control platform provided in the embodiment implements the method for cloud service. After the open source container orchestration platform controller receives the deployment file, the deployment file is parsed. After obtaining the deployment operation and maintenance characteristics corresponding to the cloud service component in the deployment file, the operation and maintenance characteristics are transmitted to the cloud platform plug-in, and the cloud platform plug-in uses the operation and maintenance characteristics to implement the cloud service required by the application. The present scheme defines the specification and framework of the application model file by opening, and unifies the definition of the model of the configuration and operation and maintenance of the application layer, the infrastructure-related cloud product configuration. The developers focus on the logical configuration of the business layer, the operation and maintenance personnel configure the operation and maintenance related attributes, and the underlying IaaS provider provides the corresponding cloud capability configuration, thereby reducing the collaboration cost between different teams.

[0063] The Kubernetes component required resource configuration and deployment are realized by the Kubernetes controller, and the cloud service corresponding cloud resources are created by combining the Kubernetes custom plug-in capability, so as to realize the automation of the cloud service component, achieve the efficient operation of the whole system, and improve the system efficiency and flexibility.

[0064] In an optional embodiment, on the basis of the foregoing embodiment, when at least one component is identified as a cloud service component based on the type of each component, before each cloud service component and all operation and maintenance characteristic information corresponding to the cloud service component are respectively transmitted to the cloud platform plug-in corresponding to the cloud service component, the method further comprises:

[0065] Converting all operation and maintenance characteristic information corresponding to each cloud service component into a cloud service object for subsequent transmission of the cloud service object to the cloud platform plug-in.

[0066] Specifically, all operation and maintenance characteristic information corresponding to each cloud service component is converted into an object in a unified data structure, and the object is transmitted to the cloud platform plug-in, and the cloud platform plug-in realizes the cloud service corresponding to the cloud service component by using the object.

[0067] Converting all operation and maintenance characteristic information corresponding to each cloud service component into a cloud service object, and modularizing the operation and maintenance characteristic information not only makes the management and maintenance of the cloud service simpler and more consistent, but also greatly improves the portability of the cloud service component and the operation and maintenance characteristic information corresponding thereto.

[0068] In an optional embodiment, on the basis of the foregoing embodiment, the cloud platform plug-in realizes the cloud service corresponding to the cloud service component by using the object, and the specific implementation manner comprises:

[0069] Step a1, receiving the cloud service object, and converting the operation and maintenance characteristic information in the cloud service object into a parameter format required by the cloud platform to create a cloud service instance.

[0070] Step a2, transmitting the converted object to the software development kit corresponding to the cloud platform to implement the application programming interface of the cloud service, and realizing the cloud service corresponding to the cloud service component.

[0071] Specifically, the cloud platform plug-in receives the cloud service object transmitted by the controller, converts the cloud service object into a parameter format required by the cloud platform, calls the corresponding application programming interface in the corresponding software development kit of the cloud platform, implements the cloud service corresponding to the cloud service component, and can uniformly manage and automate the configuration and deployment of the cloud service, reduce the need for manual configuration, reduce the error rate, and improve the efficiency. Through the cloud platform plug-in, the developer does not need to deeply understand the complexity of the cloud platform, so that the developer can focus more on the implementation of the business logic. The cloud platform plug-in provides consistent experience for different cloud platforms, making it easier to deploy and manage applications in a multi-cloud environment.

[0072] In an optional embodiment, the mobile terminal such as a mobile phone, a tablet computer, etc. that can be used in the above, Figure 2 is a flowchart of a method for implementing cloud services by a cloud-native unified control platform provided by an embodiment of the present application. Based on any of the preceding embodiments, when at least one component is identified as a cloud service component based on the type of each component, each cloud service component and all operation and maintenance characteristics corresponding to the cloud service component are transmitted to the cloud platform plug-in corresponding to the cloud service component, and then, as shown in Figure 2 the flowchart includes the following steps:

[0073] Step S201, receiving access information corresponding to the cloud service fed back by at least one cloud platform plug-in.

[0074] Specifically, the cloud platform plug-in will feed back access information corresponding to the cloud service after implementing the cloud service by the above method. The access information includes instance attribute information such as cloud service instance identification information, a network address, and a storage address, and network configuration information.

[0075] Step S202, converting at least one access information into a target format.

[0076] Specifically, after the Kubernetes controller receives the above access information, it needs to convert the above access information into a format that can be recognized and processed by the Kubernetes cluster, so as to be stored in the storage resource object of the Kubernetes cluster.

[0077] Step S203, storing the access information converted into the target format into a preset storage location in the open source container orchestration platform cluster.

[0078] In one specific example, after successfully creating a cloud database instance, the access information of the cloud database returned by the cloud platform plugin is received, such as the instance ID and the internal network address. The controller converts the above access information into a pre-set target format and stores it in a resource object such as a Kubernetes cluster Secret or ConfigMap, so as to subsequently extract the target format access information from the storage location to access the cloud service.

[0079] Specifically, after the cloud platform plugin implements the cloud service corresponding to the cloud service component, it returns the access information related to the cloud service, converts the access information into a target format and stores it in a pre-set storage location, which can achieve unified management and maintenance of cloud service access information and simplify access permission issues. And storing access information in an open source container orchestration platform cluster can easily expand storage capacity and access control policies to adapt to changing business needs. Extracting target format access information from the pre-set storage location to access the cloud service can ensure that the information can be quickly and reliably accessed when needed, improving the availability and reliability of cloud services.

[0080] In an optional embodiment, based on any of the preceding embodiments, before transmitting each cloud service component and all operation and maintenance characteristics corresponding to the cloud service component to the cloud platform plugin corresponding to the cloud service component, the method further comprises:

[0081] Extracting the cloud platform plugin corresponding to the cloud service component from the pre-built plugin registry.

[0082] Specifically, for different cloud platforms, the open source container orchestration platform controller implements a pre-defined interface specification to create corresponding cloud platform plugins. After the cloud platform plugin is successfully created, it is registered in the plugin registry of the Kubernetes cluster. When an operation related to the cloud service component is needed, the cloud platform plugin corresponding to the cloud service component is found and loaded from the registry according to the service type attribute in the cloud service component.

[0083] Specifically, different cloud platforms correspond to different cloud platform plugins, and the open source container orchestration platform cluster implements cloud services on the cloud platform through the cloud platform plugin. Multiple cloud platform plugins are stored in a pre-built plugin registry. Before transmitting each cloud service component and all operation and maintenance characteristics corresponding to the cloud service component to the cloud platform plugin corresponding to the cloud service component, the cloud platform plugin corresponding to the cloud service component needs to be extracted from the pre-built plugin registry. The pre-built plugin registry can reduce resource waste, as there is no need to build and maintain plugins for each cloud service component. Centralized management of the plugin registry makes it easier to update, maintain and monitor cloud platform plugins, which helps to respond to problems in a timely manner.

[0084] In an optional embodiment, based on any of the preceding embodiments, the open source container orchestration platform component comprises:

[0085] a network routing configuration mode, a container deployment and management mode, a self-repair mode, a key and configuration mapping storage mode, a rollback mode, an application update strategy, a log collection mode, a service discovery and load balancing mode, and a storage orchestration mode.

[0086] Specifically, the Kubernetes controller can deploy, scale, and manage the application according to the open source container orchestration platform component in the deployment file.

[0087] Specifically, by identifying the container orchestration platform component and its corresponding operation and maintenance characteristic information, automatic deployment, self-repair, key and configuration management of the container can be realized, greatly improving the operation and maintenance automation level. The self-repair mode and the application rollback mechanism can ensure quick recovery when the container or service has a problem, improve the flexibility and reliability of the system, the application update strategy can help smoothly deploy new versions of the application, reduce service interruption during the update process, the service discovery and load balancing mechanism can improve the availability and response speed of the service, ensure reasonable allocation of traffic, and the storage orchestration mode can optimize the use of storage resources, improve storage efficiency and data access speed. The above components realize the functions of automatic deployment and scaling of application programs, fault self-healing, dynamic allocation of resources, etc., greatly improving the operation and maintenance efficiency of the application.

[0088] In an optional embodiment, based on any of the preceding embodiments, when at least one component is identified as an open source container orchestration platform component based on the component type attribute of each component, the method further comprises:

[0089] Implementing open source container orchestration platform services according to the operation and maintenance characteristic information corresponding to each open source container orchestration platform component.

[0090] Specifically, after the Kubernetes controller identifies at least one component as an open source container orchestration platform component based on the component type attribute, it implements resource application in the open source container orchestration platform according to the operation and maintenance characteristic information corresponding to each open source container orchestration platform component.

[0091] In a specific example, for a storage orchestration component, its operation and maintenance characteristic information includes a specified Kubernetes interface version, a storage type, a storage capacity, a recycling policy, an access mode, and the like. Among them, the storage type includes Persistent Volume (PV), Persistent Volume Claim (PVC), and StorageClass. The Kubernetes controller implements the storage orchestration component service according to the above operation and maintenance characteristic information in the deployment file.

[0092] Specifically, the implementation of the open source container orchestration platform component is carried out according to the corresponding operation and maintenance characteristic information. The application program is developed by the R&D personnel, the components related to the application program deployment and the operation and maintenance characteristic information related to the component implementation are configured by the operation and maintenance personnel, and the open source container orchestration platform implements each operation and maintenance characteristic information. The R&D personnel focus on the logical configuration at the business level, the operation and maintenance personnel configure the related operation and maintenance characteristic information, the open source container orchestration platform implements each operation and maintenance characteristic information, and the cooperation cost between different teams is reduced.

[0093] In an optional embodiment, on the basis of any of the foregoing embodiments, the deployment file is the latest deployment file extracted from the component file library and transmitted to the open source container orchestration platform controller through the open source container orchestration platform interface when the continuous deployment system listens to the pre-built deployment file library and finds that there is a file update.

[0094] Specifically, the continuous deployment system (Continuous Deployment, CD) regularly or under certain trigger conditions, listens to whether there is a file update in the pre-built deployment file library, obtains the application list uploaded by the R&D personnel from the pre-built deployment file library when there is a file update, and automatically submits the application list in the pre-built deployment file library to the Kubernetes cluster through the open source container orchestration platform interface. Among them, the application list contains an application package and / or a deployment file. The open source container orchestration platform controller only listens to and parses the latest deployment file in the application list.

[0095] Specifically, the continuous deployment system automatically listens to the pre-built deployment file storage repository, and as soon as a new deployment file is listened to, the extraction and forwarding process is started immediately, reducing manual intervention, accelerating the online speed of the new version application, and improving the deployment efficiency.

[0096] In an optional embodiment, on the basis of any of the preceding embodiments, when it is monitored that a new deployment file is received in the open source container orchestration platform cluster, the deployment file is parsed to obtain the index monitoring task components included in the deployment file and the operation and maintenance characteristic information corresponding to the components, and the corresponding index monitoring task components are implemented according to the operation and maintenance characteristic information. After the open source container orchestration platform controller implements the cloud service corresponding to the first cloud service component by using the operation and maintenance characteristic information corresponding to the first cloud service component for the first cloud platform plug-in, the open source container orchestration platform controller performs adaptive automatic adjustment on the basis of the cloud resource index data collected by the index monitoring task components.

[0097] Step c1, record the current resource configuration C(α j ) of the application, and set the weight coefficient α k of each business index, the resource adjustment threshold θ, and the resource adjustment step δ.

[0098] Step c2, periodically obtain the application-related business index value M(α j， , k).

[0099] Step c3, calculate the resource demand adjustment amount according to the algorithm formula.

[0100] Step c4, update the resource configuration of the application according to the calculated adjustment amount according to the resource adjustment formula.

[0101] Wherein, the resource demand adjustment amount formula is as follows:

[0102]

[0103] Wherein, C(α j ) is the number of CPU cores currently allocated to the application, the weight coefficient α k of each business index and the resource adjustment threshold θ and the resource adjustment step δ are set, and M(α j， , k) is the obtained related business index value.

[0104] In a specific example, the Cloud Controller obtains the CPU usage (cpu-usage) and memory usage (memory-usage) index values of the application from the system monitoring and alarm tool (Prometheus). For example, the CPU usage of the current web-server component is 60%, and the memory usage is 40%.

[0105] According to the algorithm formula, the resource demand adjustment amount is calculated. For CPU resource adjustment amount calculation:

[0106]

[0107] wherein, a1=0.6 (cpu-usage indicator weight), M(a j， , 1)=0.6 (acquired CPU usage), 0=0.5 (set CPU utilization threshold), d=0.1 (assumed resource adjustment step), C(a j ) is the number of CPU cores currently allocated to the application (assuming an initial number of 1 core). Then the CPU resource adjustment amount is calculated as:

[0108]

[0109] The new CPU core configuration can become C(a j )+AC(a j )=1.072, and the Cloud Controller adjusts the computing resources allocated to the web-server component by interacting with the cloud platform plugin, possibly increasing the CPU quota of a partial computing instance.

[0110] Next, the overall operation process of the above method of the present application will be described in the form of a specific example, and the overall process is as shown in Figure 3 .

[0111] The R&D personnel use the Kubevela CUE language configuration template to write an Open Application Model (OAM) application definition file according to the business requirements. The above OAM application definition file includes, for example, an Aliyun database component and an Aliyun database operation and maintenance trait.

[0112] The above OAM application definition file is uploaded to the Git repository, and the CD listens to whether there is a file update in the pre-built Git repository periodically or under certain trigger conditions. When there is a file update, the OAM application definition file uploaded by the R&D personnel is obtained from the Git repository, and the OAM application definition file is automatically submitted to the Kubernetes cluster through the open source container orchestration platform interface (Kubernetes API).

[0113] The open source container orchestration platform controller (Kubernetes operator) parses the OAM application definition file. When the OAM application definition file includes a Kubernetes service component, for example, Ingress (network routing), Service (key storage), Deployment (deployment and management of containers), Configmap (configuration mapping), Daemonset (process monitoring), and CR (custom resource) components. The Kubernetes API server in the Kubernetes operator implements the deployment of the Kubernetes component service according to the corresponding operation and maintenance characteristics.

[0114] When the OAM application definition file includes a cloud service component, the CloudController in the Kubernetes operator implements the creation and deployment of the cloud service according to the corresponding operation and maintenance characteristics. The following describes the implementation process of the cloud service component by taking the implementation of creating an Aliyun cloud database service as an example.

[0115] The Aliyun cloud database component includes custom cloud database name, cloud platform type to which the cloud database belongs, database type, storage capacity, and security group rules and other operation and maintenance characteristics. The above operation and maintenance characteristics are encapsulated into a CloudDatabaseSpecification object.

[0116] A developer customizes a serial peripheral interface (Serial Peripheral Interface, SPI for short) interface, for example, a CloudResourceProvider interface. The interface includes methods such as createCloudResource, deleteCloudResource, getCloudResourceStatus, and updateCloudResourceConfiguration.

[0117] Aliyun creates an Aliyun plug-in by implementing the above interface, and develops an AliyunCloudResourceProvider class to implement the CloudResourceProvider interface. The implementation process of the createCloudResource method is as follows:

[0118] Step d1, receiving the CloudDatabaseSpecification object.

[0119] Step d2, converting the CloudDatabaseSpecification object into the parameter format required by the Relational Database Service (RDS) of the Aliyun for creating a database instance;

[0120] Step d3, using the software development kit (Java SDK) of the Aliyun to call the application programming interface (API) of the RDS creation application;

[0121] Step d4, passing the converted parameters to the API interface;

[0122] Step d5, creating a cloud database instance in the Aliyun, and generating the corresponding Aliyun database resource.

[0123] After successfully creating the Aliyun cloud database, the cloud platform plug-in returns the access information of the Aliyun cloud database, and stores the above access information into a resource object such as a Kubernetes cluster secret (Secret) or configuration mapping (ConfigMap) after converting the above access information into a format that can be recognized and processed by the Kubernetes cluster.

[0124] In an optional embodiment, the cloud native unified control platform implements a timing diagram of a cloud service method as shown in Figure 4 The developer declares resource requirements, the Kubernetes cluster receives the above resource requirements, the Kubernetes API server implements a Kubernetes component service, the Cloud Controller receives a cloud service component, the Cloud Controller calls a cloud service creation interface through a cloud platform plug-in, and the cloud platform (Cloud Provide) creates a cloud resource. The cloud platform returns cloud resource access information after creating the cloud resource, and the Cloud Controller stores the access information into a resource object such as a secret (Secret) or configuration mapping (ConfigMap) after converting the above access information into a target format.

[0125] In this embodiment, a cloud native unified control platform device for implementing a cloud service is also provided, which is used to implement the above embodiments and preferred embodiments, and details are not repeated. As used below, the term “module” can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, hardware, or a combination of software and hardware is also possible and is contemplated.

[0126] This embodiment provides a cloud native unified control platform device for implementing a cloud service, as shown in Figure 5The apparatus includes an analysis module 501, an identification module 502, and a transmission module 503.

[0127] The analysis module 501 is configured to analyze a deployment file when a new deployment file is received in an open-source container orchestration platform cluster, to obtain at least one component included in the deployment file and operation and maintenance characteristic information corresponding to the component, and the deployment file is a file uploaded in the form of an open application model definition file.

[0128] The deployment file is the latest deployment file extracted from a deployment file library and transmitted to an open-source container orchestration platform controller through an open-source container orchestration platform interface when the continuous deployment system listens to file updates in the pre-built deployment file library.

[0129] The identification module 502 is configured to identify the type of each component according to a service type attribute of each component, and the service type attribute is one of the plurality of operation and maintenance characteristics.

[0130] When the at least one component is identified as an open-source container orchestration platform component based on the service type attribute of each component, the open-source container orchestration platform component includes:

[0131] a way of deploying and managing containers, a self-repairing way, a key and configuration management way, an application rollback way, an application update strategy, a log collection way, a service discovery and load balancing way, and a storage orchestration way.

[0132] The transmission module 503 is configured to, when the at least one component is identified as a cloud service component based on the type of each component, respectively transmit each cloud service component and all operation and maintenance characteristic information corresponding to the cloud service component to a cloud platform plug-in corresponding to the cloud service component, so that the first cloud platform plug-in implements a cloud service corresponding to the first cloud service component by using the operation and maintenance characteristic information corresponding to the first cloud service component, wherein the first cloud platform plug-in is a cloud platform plug-in corresponding to the first cloud service component, and the first cloud service component is any one of the at least one cloud service component.

[0133] In an optional embodiment, the apparatus further includes a processing module 504.

[0134] The processing module 504 is configured to convert all operation and maintenance characteristic information corresponding to each cloud service component into a cloud service object, for subsequent transmission of the cloud service object to the cloud platform plug-in.

[0135] In an optional embodiment, the apparatus further includes a receiving module 505.

[0136] The receiving module 505 is configured to receive access information corresponding to the cloud service fed back by the at least one cloud platform plug-in.

[0137] The processing module 504 is further configured to convert the at least one access information into a target format, and store the at least one access information into a preset storage location in the open source container orchestration platform cluster, so as to access the cloud service by extracting the access information in the target format from the preset storage location in the future.

[0138] In an optional embodiment, the processing module 504 is specifically configured to extract the cloud platform plug-in corresponding to the cloud service component from the pre-built plug-in registration table.

[0139] In an optional embodiment, the processing module 504 is specifically configured to implement the open source container orchestration platform service according to the operation and maintenance characteristic information corresponding to each open source container orchestration platform component.

[0140] The cloud native unified control platform implementation cloud service device in the embodiment is in the form of a functional module. The module herein refers to an application specific integrated circuit (ASIC), a processor and a memory executing one or more software or fixed programs, and / or other devices that can provide the above functions.

[0141] Further function descriptions of the above modules and units are the same as those of the corresponding embodiments, and will not be described here.

[0142] The cloud native unified control platform implementation cloud service device provided by the embodiment of the application includes an open source container orchestration platform controller. After receiving a deployment file, the open source container orchestration platform controller parses the deployment file. After obtaining deployment operation and maintenance characteristics corresponding to a cloud service component in the deployment file, the open source container orchestration platform controller transmits the operation and maintenance characteristics to a cloud platform plug-in. The cloud platform plug-in implements cloud services required by an application by using the operation and maintenance characteristics. The present scheme defines a specification and a framework of an application model file, and uniformly defines a model of configuration and operation and maintenance of an application layer, infrastructure-related cloud product configuration. A developer focuses on logical configuration at a business level, an operation and maintenance personnel configures properties related to operation and maintenance, and an underlying IaaS provider provides corresponding cloud capability configuration, thereby reducing collaboration costs between different teams.

[0143] The Kubernetes controller is used to implement resource configuration and deployment required by a Kubernetes component. In combination with a Kubernetes custom plug-in capability, the cloud native unified control platform implementation cloud service device creates cloud resources corresponding to cloud services, thereby achieving automatic implementation of cloud service components, efficient running of an application in the whole system, and the goals of improving system efficiency and flexibility.

[0144] The embodiment of the application further provides a computer device, Figure 6 is a structural schematic diagram of a computer device provided by an optional embodiment of the application, as Figure 6As shown, the computer device includes one or more processors 10, memory 20, and interfaces 30 for external devices such as a keyboard and a mouse and a disk drive. One or more of the interfaces 30 enable a user to interact with the computer device. In some embodiments, the interface 30 also includes an input device, such as a microphone, or output device, such as a speaker. Figure 6 The processor 10 is used in the description of some embodiments as an example.

[0145] The processor 10 can be a central processing unit, a network processor, or a combination thereof. The processor 10 can further include an integrated circuit. The integrated circuit can be an application specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device can be a complex programmable logic device, a field programmable logic device, a general array logic, or a combination thereof.

[0146] The memory 20 stores instructions that can be executed by the at least one processor 10 to cause the at least one processor 10 to perform the methods described above.

[0147] The memory 20 can include a program storage area and a data storage area. The program storage area can store an operating system, application programs, and program modules. The data storage area can store data used by the operating system and the application programs. The memory 20 can further include a high-speed random access memory (RAM), and can also include a non-volatile memory, such as at least one disk storage device, flash memory, or other non-volatile solid-state storage device. In some embodiments, the memory 20 can optionally include a remote memory accessible to the computer device through an external network. Examples of the network include, but are not limited to, the Internet, an enterprise intranet, a local area network, a mobile communication network, and a combination thereof.

[0148] The memory 20 can include a volatile memory, such as a random access memory (RAM), and a non-volatile memory, such as at least one disk storage device, flash memory, or other non-volatile solid-state storage device. The memory 20 can also include a combination of the above-mentioned types of storage.

[0149] The computer device also includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 can be connected by a bus or other means, Figure 6 The bus connection is taken as an example.

[0150] The input device 30 can receive inputted digital or character information, and generate key signal input related to user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a trackpad, a touchpad, a pointing stick, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 can include a display device, an auxiliary lighting device (e.g., an LED), a tactile feedback device (e.g., a vibration motor), etc. The display device includes but is not limited to a liquid crystal display, a light-emitting diode, a display, and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0151] The embodiments of the present application also provide a computer readable storage medium. The method provided by the embodiments of the present application can be implemented in hardware, firmware, or be implemented as computer code on a storage medium that can be recorded in a storage medium or downloaded from a network and stored in a local storage medium, so that the method described herein can be processed by such software using a general purpose computer, a special purpose processor, or programmable or special hardware. The storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk, or a solid state disk, etc. Further, the storage medium can also include a combination of the above-mentioned memories. It can be understood that the computer, the processor, the microprocessor controller, or the programmable hardware includes a storage component that can store or receive software or computer code, which, when accessed and executed by the computer, the processor, or the hardware, implements the method shown in the above embodiments.

[0152] Part of the present application can be applied as a computer program product, for example, computer program instructions, when executed by a computer, the operation of the computer can invoke or provide the method and / or technical solutions according to the present application. Those skilled in the art should understand that the form of computer program instructions in computer readable medium includes but is not limited to source file, executable file, installation package file, etc. Correspondingly, the way of computer program instructions executed by computer includes but is not limited to: the computer directly executes the instructions, or the computer executes the corresponding compiled program after compiling the instructions, or the computer reads and executes the instructions, or the computer executes the corresponding installed program after reading and installing the instructions. Here, the computer readable medium can be any available computer readable storage medium or communication medium accessible to the computer.

[0153] While embodiments of the application have been described in connection with the preferred embodiments of the various figures, those of ordinary skill in the art will appreciate that various modifications and changes can be made without departing from the spirit and scope of the application, and that such modifications and changes fall within the scope of the appended claims.

Claims

1. A method for implementing cloud services by a cloud-native unified control platform, characterized in that, The method is executed by an open source container orchestration platform controller, and the method comprises: When a new deployment file is received in an open source container orchestration platform cluster, the deployment file is parsed to obtain at least one component included in the deployment file and operation and maintenance characteristic information corresponding to the component, wherein the deployment file is a file uploaded in the form of an open application model definition file; The type of each component is identified according to a service type attribute of each component, wherein the service type attribute is one of the operation and maintenance characteristics; When at least one component is identified as a cloud service component based on the service type attribute of each component, each cloud service component and all operation and maintenance characteristic information corresponding to the cloud service component are transmitted to a cloud platform plug-in corresponding to the cloud service component, so that a first cloud platform plug-in implements a cloud service corresponding to a first cloud service component by using the operation and maintenance characteristic information corresponding to the first cloud service component, wherein the first cloud platform plug-in is a cloud platform plug-in corresponding to the first cloud service component, and the first cloud service component is any one of the at least one cloud service component.

2. The method of claim 1, wherein, Before each cloud service component and all operation and maintenance characteristic information corresponding to the cloud service component are transmitted to a cloud platform plug-in corresponding to the cloud service component when at least one component is identified as a cloud service component based on the type of each component, the method further comprises: All operation and maintenance characteristic information corresponding to each cloud service component is converted into a cloud service object, which is used to subsequently transmit the cloud service object to the cloud platform plug-in.

3. The method of claim 1, wherein, After each cloud service component and all operation and maintenance characteristic information corresponding to the cloud service component are transmitted to a cloud platform plug-in corresponding to the cloud service component when at least one component is identified as a cloud service component based on the service type attribute of each component, the method further comprises: Access information corresponding to a cloud service is fed back by at least one cloud platform plug-in and received; At least one piece of access information is converted into a target format, and is stored in a preset storage location in the open source container orchestration platform cluster, which is used to subsequently access the cloud service by extracting the access information in the target format from the preset storage location.

4. The method according to any one of claims 1 to 3, characterized in that, Before each cloud service component and all operation and maintenance characteristic information corresponding to the cloud service component are transmitted to a cloud platform plug-in corresponding to the cloud service component, the method further comprises: A cloud platform plug-in corresponding to the cloud service component is extracted from a pre-built plug-in registry.

5. The method according to any one of claims 1 to 3, characterized in that, When at least one component is identified as an open source container orchestration platform component based on the service type attribute of each component, the open source container orchestration platform component comprises: A way of deploying and managing containers, a way of self-repairing, a way of managing keys and configurations, a way of application rollback, an application update strategy, a way of log collection, a way of service discovery and load balancing, and a way of storage orchestration.

6. The method according to any one of claims 1 to 3, characterized in that, When at least one of the components is identified as an open-source container orchestration platform component based on a service type attribute of each of the components, the method further comprises: Implementing open-source container orchestration platform services according to the operation and maintenance characteristic information corresponding to each of the open-source container orchestration platform components.

7. The method according to any one of claims 1 to 3, characterized in that, The deployment file is the latest deployment file extracted from a pre-built deployment file library and transmitted to the open-source container orchestration platform controller through an open-source container orchestration platform interface when the continuous deployment system listens to the deployment file library for file updates.

8. An apparatus for implementing cloud services by a cloud-native unified control platform, the apparatus comprising: The device comprises: The parsing module is configured to parse the deployment file when a new deployment file is received in the open-source container orchestration platform cluster, obtain at least one component included in the deployment file, and obtain operation and maintenance characteristic information corresponding to the component, wherein the deployment file is an open application model definition file. The identification module is configured to identify the type of each component according to a service type attribute of each of the components, wherein the service type attribute is one of the operation and maintenance characteristics. The transmission module is configured to transmit each of the cloud service components and all operation and maintenance characteristic information corresponding to the cloud service components to a cloud platform plug-in corresponding to the cloud service components when at least one of the components is identified as a cloud service component based on the type of each of the components, so that the first cloud platform plug-in implements a cloud service corresponding to the first cloud service component using the operation and maintenance characteristic information corresponding to the first cloud service component, wherein the first cloud platform plug-in is a cloud platform plug-in corresponding to the first cloud service component, and the first cloud service component is any one of the at least one cloud service component.

9. A computer device, comprising: The device comprises: The memory and the processor are communicatively connected, the memory stores computer instructions, and the processor executes the computer instructions to implement the method for implementing cloud services of the cloud-native unified control platform according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores computer instructions for causing a computer to execute the method for implementing cloud services of the cloud-native unified control platform according to any one of claims 1 to 7.

Images